Bug 18970

Summary: Several ways of suspending in different DEs freeze the system, but the pm-suspend command works fine
Product: Mageia Reporter: Yves Guillemot <yc.guillemot>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: mageia, marja11, nicolas.salguero, tmb, yc.guillemot
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: System log when freeze occurs, then reboot after power down and power up

Description Yves Guillemot 2016-07-17 16:46:41 CEST
Created attachment 8199 [details]
System log when freeze occurs, then reboot after power down and power up

Description of problem:
When trying to Logout -> Suspend from LXDE, the whole system freezes.
The only way to restart is to force a powerdown.

Hardware:
Laptop HP Compaq nx6110
Intel Celeron M - 1400 MHz - 768 MB

Version-Release number of selected component (if applicable):
lxde-common 0.99.1-8.mga6
mageia-lxde-config-Default 0.6.4-3.mga6
task-lxde 3-17.mga6
task-lxde-minimal 3-17.mga6

How reproducible:
Every time I try to suspend the system.

Steps to Reproduce:
1. Log in LXDE desktop
2. Select Logout -> Suspend from the menu (or from the logout icon in the panel)

The screen freezes.
The mouse cursor is no more visible.
Keyboard and mouse are dead.

Attachments:
System log. The system freezes at the beginning (ten first lines).
When rebooting, the log show several stack traces which may or may not be related to the problem.
Comment 1 Marja Van Waes 2016-07-18 07:31:21 CEST
@ Yves

Doe this also happen with a new user?

And with a different Desktop environment?


@ Nicolas

Not yet assigning to you, because I'm not sure it has anything to do with LXDE/LXDM

However, feel free to look into it :-)

Keywords: (none) => NEEDINFO
CC: (none) => marja11, nicolas.salguero

Comment 2 Yves Guillemot 2016-07-18 13:11:55 CEST
Doe this also happen with a new user?
Yes

With a different Desktop environment?

From a menu entry: I didn't find any menu with the suspend option in Gnome,
IceWM and OpenBox.

Closing the laptop lid:
   - From LXDE, IceWM and OpenBox: the system freezes
   - From Gnome:
       - At first glance, suspend seems working: all is stopped,
         except the power on light which is flashing.
       - But pressing the power on button doesn't restart the session:
            - screen remains blank
            - fan is working
            - disk activity light is on but remains infinitely on
            - nothing more happens: power down needed

   - From LXDM and XDM screen: as from LXDE desktop
   - From GDM screen: as from Gnome desktop

Using the pm-suspend command (after installing the pm-utils package):
   - Suspend and resume from suspend work fine from the four desktops.

Having the pm-utils package installed doesn't fix the initial problem
(there is no change when using the menu or closing the lid whatever the
desktop is).

CC: (none) => yc.guillemot

Comment 3 Nicolas Salguero 2016-07-18 16:47:15 CEST
Hi,

Regarding LXDE, I can confirm that lxsession does not use pm-suspend but calls, via D-BUS, systemd to do the "suspend" action.  That is what you get when you do "Logout -> Suspend".

When closing the laptop lid, I do not know what is involved.

When I tried in my Cauldron Virtualbox VM, I had no problem to suspend and then resume so I think it is a problem with the hardware (the system log seems to indicate that there is an issue with i915/drm).

Why there is no problem using the pm-suspend command is also beyond my understanding.

I really think this bug needs people with good skills in kernel/ACPI/suspend problems, which is not my case, sadly (but it is a good opportunity to improve my knowledge).

Best regards,

Nico.
Comment 4 Marja Van Waes 2016-07-18 18:17:21 CEST
Thanks for all the feedback.

CC'ing our systemd and kernel maintainers, who'll understand more.

Btw, does "kernel: [drm] RC6 disabled, disabling runtime PM support" mean anything significant? I saw that in the attachment for bug 18961 (about battery being drained after suspending), too.

Keywords: NEEDINFO => (none)
CC: (none) => mageia, tmb
Summary: Trying to Logout -> Suspend from LXDE freezes the whole system => Several ways of suspending in different DEs freeze the system, but the pm-suspend command works fine

Comment 5 Marja Van Waes 2017-04-19 10:25:57 CEST
@ Yves

Is this bug still valid, or did it get fixed?

Keywords: (none) => NEEDINFO

Comment 6 Marja Van Waes 2017-05-09 23:44:28 CEST
(In reply to Marja van Waes from comment #5)
> @ Yves
> 
> Is this bug still valid, or did it get fixed?

Does this problem still exist?
Comment 7 Yves Guillemot 2017-05-10 23:33:50 CEST
The problem still exists.

It occurs on a twelve years old computer.

I recently tried to reinstall Mageia 4 on a free partition of this computer.
The installation apparently succeeded but, when booting Mageia 4, a message beginning with the following sentence is displayed : "Sorry, but there has been a problem starting your graphical display".

Before Mageia 6 was installed, several versions of Mandriva and the versions 1 to 4 of Mageia were run on this same PC without any similar problem (in fact, without any problem).

So I presume that some failure recently occurs on this hardware and, in such a situation, there is probably no bug.

Even if there is a bug, considering the old age of the only computer where it appears, it may likely be ignored.

Thanks to everyone involved in this bug report.
I apologize for the time you have lost with this false issue.
Comment 8 Marja Van Waes 2017-05-11 13:05:46 CEST
Thanks for the feedback, Yves, and thanks for having tested a fresh install with an old Mageia version that worked fine on this hardware before.

I agree that the hardware very likely started to fail.

However, even if that means this bug will be closed as invalid, please do not stop filing bug reports. It can be hard to find out whether something is a bug in Mageia, in the BIOS or in the hardware. 
I had hit bug 12549 when I was helping QA team to test the Mageia 4 isos before they got released, but had not reported it, because I thought it was an "only me" issue, and I feared wasting the time of our developers and isobuilders with an invalid bug report. 
However, I achieved the opposite: it cost them more time, because the problem affected so many users that Mageia 4.1 had to be released to solve it.

Status: NEW => RESOLVED
Resolution: (none) => INVALID