kernel 4.15.0-151 tends to freeze after having been suspended

Bug #1938430 reported by Benno Schulenberg
This bug report is a duplicate of:  Bug #1938013: 4.15.0-151 is freezing various CPUs. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

When I tried to suspend my system today for the second time, 'systemctl suspend' was hanging -- having no effect. (Yesterday I had a full system freeze, which took two reboots to recover from. Such a freeze never happened before, so I immediately suspected kernel 4.15.0-151-generic, which was running for the first time, having been installed the day before.) The system now refusing to go to sleep made me look in the log files, and I saw this in syslog:

 kernel: [ 602.301844] BUG: unable to handle kernel paging request at ffff9fdd3248d5ad
 kernel: [ 602.301861] IP: css_release_work_fn+0xa9/0x1a0
 kernel: [ 602.301864] PGD 3b799067 P4D 3b799067 PUD 0
 kernel: [ 602.301869] Oops: 0000 [#1] SMP PTI

The complete relevant fragment of the syslog file is attached.

As the system is not working properly now (systemctl not doing its job, gedit taking fifteen seconds to save a file, 'su -' hanging...), I will reboot now, and tomorrow will go back to kernel 4.15.0-147-generic, which gave me no troubles.

Revision history for this message
Benno Schulenberg (bennoschulenberg) wrote :
summary: - BUG: unable to handle kernel paging request after 'systemctl suspend'
+ kernel 4.15.0-151 tends to freeze after having been suspended
Revision history for this message
Benno Schulenberg (bennoschulenberg) wrote :

This morning I still booted into 4.15.0-151 (to give it one more chance), then put the system into suspension after half an hour or so, and when I tried to wake it up a little later, the screen stayed blank -- no response to any keystroke, not to Ctrl+Alt+F1/F2/F3 either: frozen. Rebooting into 4.15.0-147 went fine, but there is no log of the freeze: just a block of some two thousand zero bytes in syslog. I have now put this 147 kernel to sleep twice, and it has woken up both times without a problem, and no suspicious message in syslog.

Where can I see what the differences are between 4.15.0-147 and 151?

Revision history for this message
Benno Schulenberg (bennoschulenberg) wrote :

It seems that this is a duplicate of bug #1938013.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.