Suspend fails since Kernel 5.3.0-26

[pryan]

Hi,
I'm running Linux Mint Cinnamon 19.3 64-bit on an old desktop (ASUS P7P55D mobo, Core i5 750, 4GB RAM, ancient GeForce 9800GT using nouveau drivers).

Last night I was prompted to upgrade my kernel from 5.0.0-37 to 5.3.0-26, and since then I can't suspend. When I try, the screen goes blank and the monitor powers off, the keyboard (wired, USB) appears to power off, but the PC doesn't power-off and fans keep spinning. At this point, alt-sysreq-REISUB has no effect (that I can see anyway) and I am forced to hold the power-button to force power-off.

I note that there are a few other recent posts (both here, and Ubuntu related posts) regarding suspend/resume using different desktops where Kernel 5.3.0-26 seems to be a common factor, albeit, other people seem to have problems with resume rather than suspend.

NOTE: I have booted using the older, correctly working, kernel... but otherwise everything should be accurate!

Code: Select all

$ inxi -Fxz
System:    Host: kafka Kernel: 5.0.0-37-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.4.8 
           Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic 
Machine:   Type: Desktop Mobo: ASUSTeK model: P7P55D v: Rev 1.xx serial: <filter> BIOS: American Megatrends 
           v: 2101 date: 10/20/2011 
CPU:       Topology: Quad Core model: Intel Core i5 750 bits: 64 type: MCP arch: Nehalem rev: 5 L2 cache: 8192 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21398 
           Speed: 1204 MHz min/max: 1200/2668 MHz Core speeds (MHz): 1: 1204 2: 1204 3: 1204 4: 1204 
Graphics:  Device-1: NVIDIA G92 [GeForce 9800 GT] driver: nouveau v: kernel bus ID: 01:00.0 
           Display: x11 server: X.Org 1.19.6 driver: nouveau unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: NV92 v: 3.3 Mesa 19.2.1 direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k5.0.0-37-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK M4A785/P7P55 
           driver: r8169 v: kernel port: c800 bus ID: 02:00.0 
           IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.93 TiB used: 962.57 GiB (48.7%) 
           ID-1: /dev/sda vendor: PNY model: CS900 120GB SSD size: 111.79 GiB temp: 33 C 
           ID-2: /dev/sdb vendor: Western Digital model: WD20EZRZ-00Z5HB0 size: 1.82 TiB temp: 27 C 
Partition: ID-1: / size: 21.87 GiB used: 15.23 GiB (69.6%) fs: ext4 dev: /dev/sda1 
           ID-2: /home size: 87.53 GiB used: 8.25 GiB (9.4%) fs: ext4 dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 36.0 C mobo: N/A gpu: nouveau temp: 42 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 236 Uptime: 41m Memory: 3.85 GiB used: 1.19 GiB (30.9%) Init: systemd runlevel: 5 Compilers: 
           gcc: 7.4.0 Shell: bash v: 4.4.20 inxi: 3.0.32

[gittiest personITW]

Hi,
Was there any particular reason you went for 5.0/5.3 rather than 4.15?

[pryan]

No reason at all! I originally installed from Mint 19.1 media and have upgraded through 19.2 to 19.3. I believe (but correct me if I'm wrong) that this was the default kernel; I'm typically pretty conservative with my installation choices!

[Schultz]

I would delete the 5.3 kernel and install the latest 4.15 as gittiest personITW suggests. The 5.0 kernel series is not a long term support kernel (support for it ends this February) whereas the 4.15 series is LTS and is supported till April 2023.

[it-place]

Hi,

if you're uninstalling the release kernel 4.15.0-20 after updating to a newer kernel 4.15.x, the package linux-kernel-generic will also be uninstalled. Without this package your system will stay on 4.15 automatically: viewtopic.php?f=46&t=308941

Best Regards - Oliver

[pryan]

Thanks everyone thus far!

I've got a bunch of kernels installed it turns out:

Code: Select all

$ dpkg --list | grep linux-image
ii  linux-image-4.15.0-20-generic      4.15.0-20.21          amd64    Signed kernel image generic
rc  linux-image-4.15.0-50-generic      4.15.0-50.54          amd64    Signed kernel image generic
rc  linux-image-4.15.0-51-generic      4.15.0-51.55          amd64    Signed kernel image generic
rc  linux-image-4.15.0-52-generic      4.15.0-52.56          amd64    Signed kernel image generic
rc  linux-image-4.15.0-54-generic      4.15.0-54.58          amd64    Signed kernel image generic
rc  linux-image-4.15.0-55-generic      4.15.0-55.60          amd64    Signed kernel image generic
rc  linux-image-4.15.0-58-generic      4.15.0-58.64          amd64    Signed kernel image generic
rc  linux-image-4.15.0-60-generic      4.15.0-60.67          amd64    Signed kernel image generic
rc  linux-image-4.15.0-62-generic      4.15.0-62.69          amd64    Signed kernel image generic
rc  linux-image-4.15.0-64-generic      4.15.0-64.73          amd64    Signed kernel image generic
rc  linux-image-4.15.0-65-generic      4.15.0-65.74          amd64    Signed kernel image generic
rc  linux-image-4.15.0-66-generic      4.15.0-66.75          amd64    Signed kernel image generic
rc  linux-image-4.15.0-69-generic      4.15.0-69.78          amd64    Signed kernel image generic
rc  linux-image-4.15.0-70-generic      4.15.0-70.79          amd64    Signed kernel image generic
rc  linux-image-4.15.0-72-generic      4.15.0-72.81          amd64    Signed kernel image generic
ii  linux-image-4.15.0-74-generic      4.15.0-74.84          amd64    Signed kernel image generic
ii  linux-image-5.0.0-32-generic       5.0.0-32.34~18.04.2   amd64    Signed kernel image generic
ii  linux-image-5.0.0-37-generic       5.0.0-37.40~18.04.1   amd64    Signed kernel image generic
ii  linux-image-5.3.0-26-generic       5.3.0-26.28~18.04.1   amd64    Signed kernel image generic
ii  linux-image-generic                4.15.0.74.76          amd64    Generic Linux kernel image
ii  linux-image-generic-hwe-18.04      5.3.0.26.95           amd64    Generic Linux kernel image

According to Update Manager, 4.15.0-74 is the supported 4.15.* version. If I boot using that image, should I then "apt-get purge linux-image-5.0.0.32-generic" (and the other 5.x versions)? And should I also purge "linux-image-generic-hwe-18.04"?

@it-place - I checked the thread you linked; I *do* have an installed "linux-kernel-generic" package:

Code: Select all

$ dpkg --list | grep linux-kernel-generic
ii  linux-kernel-generic               5.0.0-32              all      The Linux kernel.

..should I remove this also?

[smurphos]

Boot into 4.15.0-74 via grub, confirm all your hardware is working OK and then open Update Manager > View > Linux Kernels, and select all the 5.0 and 5.3 kernels plus all the the 4.15 kernels below 4.15.0-72 for removal. You should be left just with the two kernels and future updates will be to the 4.15 series only.

Whilst in Update manager set up the automatic maintenance up option via Edit > Preferences > Automation. This will automatically clear out older kernels in future saving you (significant) storage space.

[it-place]

You don't have to unistall the package linux-kernel-generic on your own. It should be gone automatically if you've removed kernel 5.0.0-32.

[pryan]

Perfect - thanks to everyone for helping me sort this out!!

[akred3]

Hello,
FYI, I ran with the same issue and seems that the 5.3.X series generate this kind of problem in our Linux Mint version (I don't encounter this on 5.0.X)
Anyway, I have done the same steps as you to solve my problem, so thank you

[SilenceIsG0lden]

I know this is technically a newbie question, but I can't post it there referencing the previous exchanges in this topic. So please bear with me.

I have suspend (+ hibernation) problems, NEVER had any Linux Mint version before my current 19.3 (cinnamon). My output is this:

Code: Select all

~$ dpkg --list | grep linux-image
ii  linux-image-5.0.0-32-generic               5.0.0-32.34~18.04.2                              amd64        Signed kernel image generic
ii  linux-image-5.3.0-46-generic               5.3.0-46.38~18.04.1                              amd64        Signed kernel image generic
ii  linux-image-5.3.0-51-generic               5.3.0-51.44~18.04.2                              amd64        Signed kernel image generic
ii  linux-image-generic-hwe-18.04              5.3.0.51.104                                     amd64        Generic Linux kernel image

I never purposefully chose to install any kernel, just went with the recommended updates. As I understand it now, if I delete all those listed above that are NOT 5.0.0, in other words keep only the very first one, I would be set and my suspend would be working again, correct?

I don't understand how I go about deleting the other kernels. Can anyone give me a hint? Point me to a tutorial? I don't want to end up with a non-functioning system. Is there anything else I need to consider? Like some programs potentially not working correctly because they are looking for something in the newer kernels?

Thanks a lot in advance!!

[smurphos]

I never purposefully chose to install any kernel, just went with the recommended updates. As I understand it now, if I delete all those listed above that are NOT 5.0.0, in other words keep only the very first one, I would be set and my suspend would be working again, correct?

Possibly - these types of issues with kernels tend to be quite hardware specific. I.e the majority of users are doing just fine with the 5.3 kernel, but a subset with specific CPU's or motherboards are having problems. But still trying different kernel series when they are available is a valid troubleshooting step.

I don't understand how I go about deleting the other kernels. Can anyone give me a hint? Point me to a tutorial? I don't want to end up with a non-functioning system. Is there anything else I need to consider? Like some programs potentially not working correctly because they are looking for something in the newer kernels?

Thanks a lot in advance!!

So the easiest way to manage kernels is via Update Manager. Open it then View > Linux Kernels. From here you can install alternative kernels, and remove kernels (except for the one you are currently booted into too). To boot into an alternative kernel for testing you need to access the Grub menu at boot - all alternative kernels are listed as Advanced options in Grub. If you've not set yourself up to show Grub automatically this is normally via holding shift during boot (escape on some hardware). If you find a working kernel. whilst booted into it you can then remove any later kernels via Update Manager to make it the default.

Bear in mind that of all the kernels available only the latest in the 4.15.0.x series and the latest in the 5.3.0.x series are fully patched for known security issues so if neither of those fix your issue, but an older one does, plan on testing new kernel releases as they come out.

If you want to set grub to show automatically on every boot then run this command to open the relevant config file in a terminal based text editor with elevated privileges

Code: Select all

sudoedit /etc/default/grub

Change these lines

Code: Select all

GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0

to

Code: Select all

GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=5

Then Ctrl-X, Y, Enter to save.
Then in the terminal run

Code: Select all

sudo update-grub

[SilenceIsG0lden]

Thank you very much, smurphos, for your detailed help! It's very appreciated, and I will add it to my personal help files.

Just last week, though, I received an update for something related to LAN connections and suspension -- I had a lot of work that day and only clicked to install the updates, missing to jot down the details for this forum post. However, the short description alongside the update made me hope that things might change. And, indeed: once I tested suspend and even hibernation, my machine came back and was online! Yay!

Now there's just the quirk remaining that apparently it can only be coming back from suspend for a limited number of times or while being suspended/in hibernation for a limited number of hours, because at one point I come back and the network cable has been (virtually) unplugged again. Haven't had an opportunity to fully observe and document it.

Long story short: I'll hold off messing with my kernel(s). But, good to know how to do it.

UPDATE June 01: I don't know what exactly happened, but more updates came in and now it seems to be fixed completely (at least for me). The most amazingly awesome thing happened this morning: I had put my Linux into hibernation on Saturday, then on Sunday needed to boot into Win7. I was preparing to have no network on resuming from hibernation when I booted into Linux this morning, but was so pleasantly surprised I did a little dance. (In these utterly depressing times, every little positive thing counts.) Linux came back without any problems, like I had never left it in the first place, networking working and all! Thank you!!

Little aside: ready to ditch Win7 even more now, since the April updates caused the shut-down process to take about 5-10 minutes. (Couldn't stay in the room to wait, or I'd have gone mental.)