Bug 23686 - kernel 4.18.12 and newer hang on shutdown or hibernate
Summary: kernel 4.18.12 and newer hang on shutdown or hibernate
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: High critical
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-14 06:52 CEST by Ethan Merritt
Modified: 2020-08-16 21:47 CEST (History)
6 users (show)

See Also:
Source RPM: kernel-4.18.14-1.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Ethan Merritt 2018-10-14 06:52:51 CEST
Description of problem:

machine hangs hard on shutdown or hibernate.  Cold restart required to recover.  I see the same hang on explicit "shutdown" or "reboot" from the command line and on shutdown or reboot or hibernate widgets from the desktop menu.  Also when I close the laptop lid, which is most annoying.

No obvious hints in the system log.

"suspend" does work (as indicated by power status lights on the laptop) but then the system hangs hard on resume.  It is not 100% clear to me whether this is the same problem or a separate one.

EFI laptop Intel i5-6200U


Version-Release number of selected component (if applicable)

First saw this with 4.18.12   
Still happening with 4.18.14
I have retreated to using 4.18.7 (kernel-desktop-4.18.7-1.mga7) which works fine, but I do not have versions between 4.18.7 and 4.18.12 installed currently so I cannot test them easily.


How reproducible:  100%


Steps to Reproduce:
1.  Boot system
2.  Try to shutdown or reboot or hibernate
3.
Comment 1 Morgan Leijström 2018-10-15 23:03:57 CEST
I would believe the hang on resuming from suspend is a separate problem.
I get it on mga6 with desktop and server 4.14.76-1 but not linus 4.14.76-1, see Bug 23687, maybe a hint ?

CC: (none) => fri

Marja Van Waes 2018-10-16 19:55:43 CEST

Assignee: bugsquad => kernel
CC: (none) => marja11

Comment 2 Morgan Leijström 2018-10-16 23:32:41 CEST
Please try to see if kernel-linus solves at least the resume problem, it did on my Thinkpad T400.  ( kernel-linus-4.18.14-1 )
 
This laptop was OK with cauldron when i last used it a half year ago- Now i updated it and found this machine have the same resume problem on at least Mageia kernel-desktop-4.18.14-2

(but it do not experience the shut down problem you describe)

Maybe this bug should be split in two, i let the kernel maintainer decide.
Comment 3 François Andriot 2018-10-20 11:14:30 CEST
Hello, I have the same problem on Mageia 6, not cauldron ...

I have 2 laptops that were updated from kernel-desktop-4.14.70-2.mga6-1-1.mga6 to kernel-desktop-4.18.12-1.mga6-1-1.mga6 (no intermediate version).

When I close the lid, it goes to sleep => OK
But when opening the led, hard freeze...
I had no problem with 4.14.x kernel, it started with 4.18.12 kernel for me.

CC: (none) => albator78

Comment 4 Morgan Leijström 2018-10-20 20:42:59 CEST
@Francois: if you want to experiment further, i would guess that for you also
kernel-desktop/server/tmb-4.14.76-1 freeze on resume, but not linus-4.14.76-1 ?
And also that any linus-4.18.x works?
Comment 5 François Andriot 2018-10-20 22:09:05 CEST
Hello, you are correct: kernel-linus-4.14.76-1 works fine, but kernel-desktop-4.14.76-1 freezes on resume.

Regarding the 4.18 version, I don't find any kernel-linus 4.18 in Mageia 6, and I don't want to switch to cauldron.
Comment 6 Morgan Leijström 2018-10-21 01:03:22 CEST
Ah... yes i see too there is no krenel-linus 4.18 backported.

@Francois: it seems your findings are coherent with the findings in Bug 23687, follow the development there.
Comment 7 aguador 2018-11-13 12:57:16 CET
This now appears in Mageia 6 with the 4.18.12 kernel. Recovery is fine from 4.14.78, but not from the newer kernel, which requires a cold restart.

CC: (none) => waterbearer54

Comment 8 Rémi Verschelde 2018-11-16 09:42:19 CET
This was fixed by Thomas in Cauldron with kernel-4.18.16-2.mga7. See relevant thread on dev mailing list: https://ml.mageia.org/l/arc/dev/2018-10/msg00001.html

The same patch should be backported to Mageia 6's kernel. I believe it's this commit: http://svnweb.mageia.org/packages?view=revision&revision=1323438

CC: (none) => tmb
Version: Cauldron => 6

Rémi Verschelde 2018-11-16 09:42:37 CET

Priority: Normal => High

Comment 9 Thomas Backlund 2018-11-16 10:37:27 CET
Actually, kernel-4.18.16-2.mga6 has been in backports_testing since oct 22.

I just havent assigned it to QA (and I wont as I need to do some other updates to 4.18 backport first..)

but for those that dont want to wait you can install the testing one
Comment 10 aguador 2018-11-16 11:50:50 CET
Actually, I just checked and it was not there, at least not on my mirror (ftp.free.fr). Installed kernel-4.18.16-2.mga6 which works like a charm!
Comment 11 Aurelien Oudelet 2020-08-16 21:47:49 CEST
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Status: NEW => RESOLVED
CC: (none) => ouaurelien
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.