Suspend / Resume broken HP dv8000 2.6.27

[markginter24]

Intrepid Ibex, AMD64bit processor, kernel 2.6.27-8-generic

The laptop suspends. When attempting to resume, the harddrive light stays solid, the laptop backlight does not turn back on and the keyboard does not respond.

Fedora 9 properly suspends/resumes. Opensuse 11.1 beta 5 properly suspends/resumes (s2ram -f) so it is possible for the laptop to suspend/resume properly.

[peter swain (swine)]

confirmed: I'm seeing exactly the same problem with resume on dv8000.
Keyboard unresponsive on resume (and touchpad too, I seem to recall).
Intrepid with kernel 2.6.27-11.27

A long shot -- Could it be related to the keyboard repeats, missing keystrokes & re-ordered keystrokes I see on this box - perhaps low-level kbd hw is screwy, and suspend/resume totally curdles interface state? Does anyone else see that, or is that a different issue just affecting my dv8000?

[Leann Ogasawara (leannogasawara)]

Hi Guys,

Care to test and confirm if this issue remains with the most recent pre-release of Jaunty 9.04 (currently Alpha4) - http://cdimage.ubuntu.com/releases/jaunty/ . It contains a newer 2.6.28 based kernel. You should be able to test suspend via a LiveCD. Please let us know your results.

[peter swain (swine)]

Thanx! confirmed fixed with jaunty-9.04-alpha4.
LiveCD wasn't useful - this laptop has 2 disks & I have swap on LVM, which it can't see.
Forcing install of 2.6.28 didn't help either, still no kbd on resume.
But upgrade of whole OS to jaunty-a4 solved it!
So it may not just be a kernel issue, but it's fixed.

[markginter24 (mark-hanoverbeacon)]

I still cannot suspend/resume in Jaunty. In Intrepid if I use the fglrx driver it will suspend/resume - but the xorg-ati driver does not suspend resume.

When I tried suspend/resume in Jaunty - once it rebooted it did this auto bug report thing and the bug is reported

here:https://bugs.launchpad.net/bugs/333377

[Leann Ogasawara (leannogasawara)]

Thanks markginter24. I'm going to actually mark this bug a duplicate of the newer bug 333377 as it contains a little bit more debug info against the newer release. Please continue to track this bug at that report. Thanks.