You are not logged in.
Pages: 1
I updated my Lenovo V110-15AST today and recieved the 4.19.1 update.
After clicking shutdown, the laptop's screen turns off, but the caps lock flashes.
The other issue also is that that now my laptop won't enter suspend and screen goes blank.
journalctl -k -b -1 https://hastebin.com/rotidocuvu.coffeescript
Last edited by ukbeast89 (2018-11-18 00:38:00)
Offline
Welcome to the arch linux forums ukbeast89. Were any other packages updates at the same time as linux-zen? The log does not contain the kernel panic.
Does the issue also occur with linux 4.19.1?
Offline
Hello, and thank you for welcoming me.
The panic happened on vanilla, so I thought it maybe a package issue or something, tried with zen and got the same issue.
I also thought it might be the new default IO scheduler and switched it to kyber, still issues.
4.19.2 has been released from staging and so I'm going to try that.
Offline
You could also try scsi_mod.use_blk_mq=0.
Offline
You could also try scsi_mod.use_blk_mq=0.
Thank you for the suggestions.
I have tried adding that to my boot flag and still have the issue.
GRUB_CMDLINE_LINUX_DEFAULT="quiet scsi_mod.use_blk_mq=0 resume=UUID=E7AC-EE3F"
journalctl for 4.19.2-arch1 https://hastebin.com/yeheveqiqe.coffeescript
Offline
Some of the lines from the journal appear truncated ending in >
I would suggest removing the quiet option and try systemctl halt (not sure if on a laptop the screen will still remain on but if it does you should be able to see the output of the panic)
Offline
I have found out the issue!
It was due to a change in AMDgpu display code (I don't know which 4.19 revision though)
I just add amdgpu.dc=0 to my kernel, and suspend shutdown works!
What is the downside of disabling the Display code?
Last edited by ukbeast89 (2018-11-18 00:48:48)
Offline
No downside if with display core disabled you have all the functionality you need.
If you wanted to use display core then you could check linux 4.20-rc3 or amd-staging-drm-next to see if the issue has already been resolved upstream or bisect 4.18 to 4.19 to find the bad commit then report that upstream.
Offline
Pages: 1