Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

mmstick
Copy link
Member

@mmstick mmstick commented Jul 26, 2023

Supersedes #266

Required by pop-os/amd64-microcode#2

@mmstick mmstick requested review from a team July 26, 2023 14:30
@leviport
Copy link
Member

leviport commented Jul 27, 2023

I've been running this on my oryp9 with a USB-C docking monitor since yesterday. The freezing problem seems far less prevalent, but I did see one freeze just a little bit ago. This time, the freeze was preceded by applications slowing down and feeling "choppy" for a few minutes, before the external display froze completely, then the built-in display froze a little bit after that. I'll continue to test and see if that was just a one-off.

Edit, output from the freeze looks pretty much the same as before:

Jul 27 14:08:14 levioryx kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Jul 27 14:08:14 levioryx kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out
Jul 27 14:08:24 levioryx kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out
Jul 27 14:08:34 levioryx kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Jul 27 14:08:34 levioryx kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out
Jul 27 14:08:45 levioryx kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out

@leviport
Copy link
Member

Just got another one:

Jul 27 17:35:51 levioryx kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe B (start=27225 end=27226) time 123 us, min 1415, max 1439, scanline start 1411, end 1441
Jul 27 17:36:34 levioryx kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe B (start=34185 end=34186) time 126 us, min 1415, max 1439, scanline start 1412, end 1441
Jul 27 17:37:28 levioryx kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe B (start=43217 end=43218) time 228 us, min 1415, max 1439, scanline start 1389, end 1443
Jul 27 17:37:47 levioryx kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out
Jul 27 17:37:57 levioryx kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Jul 27 17:37:57 levioryx kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out
Jul 27 17:38:07 levioryx kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Jul 27 17:38:07 levioryx kernel: i915 0000:00:02.0: [drm] *ERROR* [PLANE:82:plane 1B] commit wait timed out

So I guess it waits for me to say something optimistic, then it really gives me the business.

@jackpot51
Copy link
Member

@leviport providing Intel with logs here might help: https://gitlab.freedesktop.org/drm/intel/-/issues/8421

@XV-02
Copy link

XV-02 commented Jul 28, 2023

As an addendum - I'm seeing what I'd call inconsistent behaviour on systems when upgrading to 6.4.6.

On Mira R3 w/ a discrete Radeon RX 5700, I initially saw issues with system shutdown (it was hanging at the point when KVM is busy stopping) as well as the Wifi just disappearing on boots after the initial OS install. But I couldn't replicate the issue either across several reinstalls.

On the Pang12 I use as a work machine, installing it seems to have interfered at some level with detection of hot plug events for displays. I disconnected an HDMI display, and the system was under the impression that it was still attached. I manually switched to single display mode, but even after that, I could switch back to join-displays despite no external display. On a reboot, it failed to detect a display being plugged in and stubbornly stayed in single display mode. This was not an issue after switching into COSMIC and then returning to Pop on Wayland. I need to this more though.

The Slack desktop app seems not to work with the new kernel. While not part of our checklist, it is notable. Web-Slack works fine, as does VSCodium. So not sure what the disconnect is. Did grab the journal logs, though I've not looked at them yet.
646Journal.log

@pktiuk
Copy link

pktiuk commented Jul 31, 2023

6.4.7 is already out

Copy link
Member

@leviport leviport left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this has some pretty big security fixes, I'm going to approve it for release despite the known freezing regression. We can work on a fix for that further down the line. The rest of our testing went well.

For anyone who starts experiencing freezes, I've found that switching to TTY3 and back to TTY2 usually fixes it, but it takes a good ~20 seconds before it switches to TTY3. Sometimes I need to hit Ctrl + Alt + F3 multiple times. But it eventually switches, and my desktop is unstuck once I switch back to TTY2.

I also wasn't able to reproduce this issue with a USB-C to DisplayPort cable, so a minor adjustment in setup should bring relief, if the freezing becomes too infuriating.

@mmstick mmstick merged commit 723b3c3 into master Aug 3, 2023
@mmstick mmstick deleted the linux-6.4.6_jammy branch August 3, 2023 16:01
@imfulee
Copy link

imfulee commented Aug 8, 2023

Coming from the reddit announcement of the new kernel release.
As someone who didn't know how to switch from tty3 to tty2, I'm adding a comment here for anyone that doesn't know the exact steps.

  • Ctrl + Alt + F3 to switch to tty3
  • Ctrl + Alt + F2 to switch to tty2

@Cod3Bende4
Copy link

I am using latest 6.4.6 still facing same issues. When i shut down the computer, my screen goes black, keypad lights also goes off. But to start the computer again when i click power button, it does not boots up so i have to long press the power button to initiate a restart. It means my computer never shut down properly. I think this issue should be reopened.

Let me know if you need any additional info

Linux pop-os 6.4.6-76060406-generic #202307241739~1694621917~22.04~ac5e1a8 SMP PREEMPT_DYNAMIC Wed S x86_64 x86_64 x86_64 GNU/Linux

@leviport
Copy link
Member

@Cod3Bende4 This is a pull request, not an issue. It cannot be reopened. Open an issue if there is a bug that needs to be tracked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants