FS#58516 - System unresponsible (kernel panic?) after resume from suspend
Attached to Project:
Arch Linux
Opened by Zhao Rui (renyuneyun) - Wednesday, 09 May 2018, 09:48 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 10 December 2019, 11:06 GMT
Opened by Zhao Rui (renyuneyun) - Wednesday, 09 May 2018, 09:48 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 10 December 2019, 11:06 GMT
|
Details
Description:
The system becomes unresponsible after resuming from suspend. This may happen (almost) immediately, or with a little delay (e.g. I can open a webpage). The system works without any problem as long as I don't put it to suspend; it may sometimes not encounter this problem after resume. (And of course, it used to work well, but I don't exactly remember which kernel version had it had this problem. But it should be within one or two months.) Sometimes, when the system becomes unresponsible, the light of my "Caps Lock" key blinks, and this (if I'm correct) indicates there is a kernel panic. I happen to observe some information (similar to a kernel panic info) printed to tty2 (when I switched to tty2 immediately after resume), but I didn't take a photo of it. Additional info: For what I tried, this happens on these packages (but I don't remember at what point this first happens [i.e. my test is incomplete]): linux 4.16.{3,5,6,7} linux-lts 4.14.39-2 (linux 4.16.7-1 and linux-lts 4.14.39-2 are the latest version in the repo at this point.) My laptop model is Dell XPS 13 9343. Boot parameters are: `root=MYROOT rw rootflags=subvol=ROOT_SUBVOL pcie_aspm=force` I attached the output of `journalctl | grep kernel`, with some irrelevant information removed (e.g. after rebooting). Starting from 10:04:04, there are many errors with traces. Steps to reproduce: 1. Put the laptop to suspend mode 2. Wake it up 3. Wait for a few seconds |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Tuesday, 10 December 2019, 11:06 GMT
Reason for closing: Not a bug
Additional comments about closing: Likely swap it not accessible
Tuesday, 10 December 2019, 11:06 GMT
Reason for closing: Not a bug
Additional comments about closing: Likely swap it not accessible
But not sure if this is the key spot.