-
Notifications
You must be signed in to change notification settings - Fork 15
Linux 6.4.6 #267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux 6.4.6 #267
Conversation
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:
|
Just got another one:
So I guess it waits for me to say something optimistic, then it really gives me the business. |
@leviport providing Intel with logs here might help: https://gitlab.freedesktop.org/drm/intel/-/issues/8421 |
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. |
|
There was a problem hiding this 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.
Coming from the reddit announcement of the new kernel release.
|
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
|
@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. |
Supersedes #266
Required by pop-os/amd64-microcode#2