Description of problem: Since upgrade to Mageia 4, system crashes when waking up from suspend. When closing the laptop (Asus Zenbook UX32VD), the system is suspended. When opening the laptop, last screen appears but it fozen. Must hard reboot the laptop. logs shows nothing since suspend : [root@localhost]#journalctl -b-1 -a --no-pager | tail -750 [...] févr. 05 17:23:28 localhost.localdomain sensord[838]: Chip: nouveau-pci-0100 févr. 05 17:23:28 localhost.localdomain sensord[838]: Adapter: PCI adapter févr. 05 17:23:28 localhost.localdomain sensord[838]: Error getting sensor data: nouveau/#0: Can't read févr. 05 17:23:28 localhost.localdomain sensord[838]: sensor read error (-1) févr. 05 17:24:13 localhost.localdomain kernel: ACPI: \_SB_.PCI0: Bus check notify on _handle_hotplug_event_root févr. 05 17:24:13 localhost.localdomain systemd-logind[766]: Lid closed. févr. 05 17:24:18 localhost.localdomain systemd-logind[766]: Delay lock is active but inhibitor timeout is reached. févr. 05 17:24:18 localhost.localdomain systemd[1]: Starting Sleep. févr. 05 17:24:18 localhost.localdomain systemd[1]: Reached target Sleep. févr. 05 17:24:18 localhost.localdomain systemd[1]: Starting Suspend... févr. 05 17:24:18 localhost.localdomain systemd-sleep[10960]: Suspending system... Problem doesn't appear when booting with old kernel 3.10.24 Version-Release number of selected component (if applicable): Linux kernel 3.12.8 How reproducible: Always reproductible Steps to Reproduce: 1.Boot on kernel 3.12.8 2.Suspend 3.Try to wake up Reproducible: Steps to Reproduce:
CC: (none) => tmb
Is this still valid with current kernel?
CC: (none) => olivier
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is 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 4'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. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 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/
Status: NEW => RESOLVEDResolution: (none) => OLD