I’m running Fedora 34 (recently upgraded from 32) with Cinnamon as a desktop, on a Dell XPS 15 9550, using NVIDIA drivers, and booting from an external SSD attached via USB-C. Software and firmware are fully up-to-date.
Mostly, things work fine. But although i can suspend the machine, it never successfully resumes from suspension. This was true on 32 as well. I also boot this machine into Ubuntu 18.04, and there, suspend and resume works fine.
I commented about this on an earlier thread, but i thought i would post more details, since it’s still happening.
I did a little test just now, which went as follows:
- 19:20 boot, then log in
- 19:23 suspend
- 19:25 try to resume by pressing the power button
- 19:26 decide that the resumption has failed, and turn off by holding down the power button
- 19:27 boot, then log in
- 19:29 shut down
After that, i booted up again to make this post. At this point, in terms of journalctl boot offset, the 19:20 boot is at offset -2, and 19:27 is at offset -1.
When suspending, the window manager shut down, leaving a console message on the screen, before powering down:
[ 160.027319] __common_interrupt: 5.33 No irq handler for vector
When resuming, the machine got as far as a console showing two messages:
[ 160.027319] __common_interrupt: 5.33 No irq handler for vector [ 172.592381] __common_interrupt: 5.33 No irq handler for vector
I have no idea if this is significant. I can see that these messages were printed during the 19:20 boot, and not 19:27 or the current one:
$ journalctl -o short-monotonic -b -2 | fgrep '__common_interrupt: 5.33 No irq handler for vector' [ 160.027319] rife kernel: __common_interrupt: 5.33 No irq handler for vector [ 172.592381] rife kernel: __common_interrupt: 5.33 No irq handler for vector $ journalctl -o short-monotonic -b -1 | fgrep '__common_interrupt: 5.33 No irq handler for vector' $ journalctl -o short-monotonic -b 0 | fgrep '__common_interrupt: 5.33 No irq handler for vector' $
I have posted the output of
journalctl -o short-iso-precise -b $offset for both boots, and of
sudo lshw as a gist.
After booting, and before suspending, i made a manual entry into the system log using the logger utility; each of the messages is prefixed with “hear ye”, to make it easy to recognise.
It’s clear from the log that the machine is starting to resume, and making a lot of progress. Seconds after i try to resume, the log says:
2021-06-26T19:25:07.619726+0100 rife systemd-sleep: System resumed.
And then there’s lots of other stuff, mostly to do with the network. But i never see my desktop again.
Does anyone have any idea what the problem might be? Or, more likely, does anyone have any idea how i could investigate further?
EDIT: I wondered if i just wasn’t waiting long enough for the resume to complete, so after making this post, i tried a suspend and resume, and then went off to fix my roof. The machine made no more progress than in the test above.