Bug 601462

Summary:	Laptop locks solid on close lid event
Product:	[openSUSE] openSUSE 11.3	Reporter:	Carlos Robinson <carlos.e.r>
Component:	Basesystem	Assignee:	Holger Macht <hmacht>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None
Version:	Milestone 5
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 11.3
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Carlos Robinson 2010-04-30 16:40:36 UTC

See Bug 597595 - System fails to hibernate, more details are there.

This is a compaq presario CQ61-330SS (SMOLT profile
<http://www.smolts.org/client/show/pub_2c303e01-12a6-44f6-8128-f8df1d7ce080>)

oS is 11.3 M5 i586 (as x64 has been reported to be broken and not installable).

Not upgrading to M6 because I want it to be x64 and I'm waiting for your feedback on these two bugs.

Video is Intel GM45. If this chipset is confirmed to be buggy in 11.3, I'll have to abandon testing 11.3 completely.


On close lid (ie, s2ram) in gnome crashes (locks solid) the machine, with text mode messages (See attachment (id=358025)).

If I close the lid while in text mode machine does not suspend to ram, it
simply powers off the backlight, it seems (power led remains on, wifi led
blinks).

Comment 1 Holger Macht 2010-05-04 07:40:39 UTC

So you have the system configured to suspend to RAM when closing the LID? Does suspend to RAM work when triggered manuallY? It's completely fine that suspend to RAM is not executrd when in text mode, because your desktop session is not active in that case.

Comment 2 Carlos Robinson 2010-05-04 08:55:12 UTC

(In reply to comment #1)
> So you have the system configured to suspend to RAM when closing the LID?

AFAIK, I have the default gnome power management prefereces, which are "suspend" when lid is closed. Te result is that it crashes solid. Locks.

> Does
> suspend to RAM work when triggered manuallY?

I'll try.
[...]

It refuses, unknown machine. I have to dump the output to a usb stick, then bring over to this (windows) machine. Hold on...

Minas-Anor:~ # s2ram
Machine is unknown.
This machine can be identified by:
    sys_vendor   = "Hewlett-Packard"
    sys_product  = "Compaq Presario CQ61 Notebook PC"
    sys_version  = "Rev 1"
    bios_version = "F.14"
See http://en.opensuse.org/S2ram for details.

If you report a problem, please include the complete output above.
If you report success, please make sure you tested it from both X and
the text console and preferably without proprietary drivers.
Minas-Anor:~ # 


So I force it. It switches to text mode and it freezes, no messages. Keyboard is dead, even the shift leds keys do not respond. I have to power cycle it.

After reboot, there is nothing in var/log/messages, and pm-suspend is not from today.


Notice that in 11.2, closing the lid and back works fine, or almost: touchpad dies (Bug 585186).

> It's completely fine that suspend
> to RAM is not executrd when in text mode, because your desktop session is not
> active in that case.

Ok.

It should be configurable systemwide, IMO. Suppose nobody is logged in, or text mode, battery dies... no hibernation, crash.


Notice that, as I have some free time now, I intend to install the M6 release fresh in this same partition, from the DVD. It will be x64, now it is i586 (M5, not updated). I'll wait half an hour.

Comment 3 Holger Macht 2010-05-04 10:18:24 UTC

(In reply to comment #2)
> (In reply to comment #1)
> > So you have the system configured to suspend to RAM when closing the LID?
> 
> AFAIK, I have the default gnome power management prefereces, which are
> "suspend" when lid is closed. Te result is that it crashes solid. Locks.
> 
> > Does
> > suspend to RAM work when triggered manuallY?
> 
> I'll try.
> [...]
> 
> It refuses, unknown machine. I have to dump the output to a usb stick, then
> bring over to this (windows) machine. Hold on...

Hm, that's strange. You have intel graphics and that should be auto-detected to being able to resume the display.
 
> So I force it. It switches to text mode and it freezes, no messages. Keyboard
> is dead, even the shift leds keys do not respond. I have to power cycle it.
> 
> After reboot, there is nothing in var/log/messages, and pm-suspend is not from
> today.

Please attach your /var/log/pm-suspend after a failed suspend to RAM (from the battery applet).

> > It's completely fine that suspend
> > to RAM is not executrd when in text mode, because your desktop session is not
> > active in that case.
> 
> Ok.
> 
> It should be configurable systemwide, IMO. Suppose nobody is logged in, or text
> mode, battery dies... no hibernation, crash.

If nobody is logged in, you're in gdm, or kdm which should do session management fine. BTW. You're using KDE4 or GNOME?
 
> Notice that, as I have some free time now, I intend to install the M6 release
> fresh in this same partition, from the DVD. It will be x64, now it is i586 (M5,
> not updated). I'll wait half an hour.

Yes, you can also try with M6 first, sometimes such problems go away automagically ;-)

Comment 4 Carlos Robinson 2010-05-14 06:26:07 UTC

(In reply to comment #3)
> (In reply to comment #2)

> > It refuses, unknown machine. I have to dump the output to a usb stick, then
> > bring over to this (windows) machine. Hold on...
> Hm, that's strange. You have intel graphics and that should be auto-detected to
> being able to resume the display.

True.

> > So I force it. It switches to text mode and it freezes, no messages. Keyboard
> > is dead, even the shift leds keys do not respond. I have to power cycle it.
> > 
> > After reboot, there is nothing in var/log/messages, and pm-suspend is not from
> > today.
> Please attach your /var/log/pm-suspend after a failed suspend to RAM (from the
> battery applet).

Ok, rebooting to factory... [] Clicking right or left on the battery applet does not offer any option to suspend or hibernate - remember, this laptop is not listed, not officially "suspendable". But... AH, I forgot: I have reformated and installed M6-x64, and now "close lid" succeeds.

Machine is still "unknown" to s2ram, though.

> > > It's completely fine that suspend
> > > to RAM is not executrd when in text mode, because your desktop session is not
> > > active in that case.
> > 
> > Ok.
> > 
> > It should be configurable systemwide, IMO. Suppose nobody is logged in, or text
> > mode, battery dies... no hibernation, crash.
> If nobody is logged in, you're in gdm, or kdm which should do session
> management fine. BTW. You're using KDE4 or GNOME?

Gnome only.

I have gnome on test systems, and both on "production" systems if space allows (kde3).

Which reminds me, that the gdm login in this machine is incomplete: the main dialog does not offer any option to halt, reboot or hibernate. There is a battery applet which doesn't have any clickable command, except "preferences".


> > Notice that, as I have some free time now, I intend to install the M6 release
> > fresh in this same partition, from the DVD. It will be x64, now it is i586 (M5,
> > not updated). I'll wait half an hour.
> Yes, you can also try with M6 first, sometimes such problems go away
> automagically ;-)

It did :-)

Comment 5 Holger Macht 2010-05-17 07:10:26 UTC

(In reply to comment #4)
> Ok, rebooting to factory... [] Clicking right or left on the battery applet
> does not offer any option to suspend or hibernate - remember, this laptop is
> not listed, not officially "suspendable". But... AH, I forgot: I have
> reformated and installed M6-x64, and now "close lid" succeeds.

Great, so this bug is no longer present.

> Machine is still "unknown" to s2ram, though.

That's completely fine. s2ram will always show your system as unknown as long as it has no whitelist entry for it, which it hasn't, because intel graphics should be autodetected. This Autodetection is done by pm-utils, not by s2ram.

> > Yes, you can also try with M6 first, sometimes such problems go away
> > automagically ;-)
> 
> It did :-)

Good ;-)