[Hewlett-Packard HP TouchSmart tx2 Notebook PC] suspend/resume failure [non-free: fglrx]

Bug #362242 reported by Ryan
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Suspend has been failing lately with resume to a blinking white cursor (when opening the laptop lid from suspend).

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: Hewlett-Packard HP TouchSmart tx2 Notebook PC
NonfreeKernelModules: fglrx
Package: linux-image-2.6.28-11-generic 2.6.28-11.41
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=cf378b06-0657-4fee-b3f0-2807d06bd372 ro quiet nosplash resume=/dev/mapper/swap i8042.reset
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.41-generic
SourcePackage: linux
Tags: resume suspend
Title: [Hewlett-Packard HP TouchSmart tx2 Notebook PC] suspend/resume failure [non-free: fglrx]
UserGroups:

Revision history for this message
Ryan (carbonfreeze) wrote :
Revision history for this message
Robert Cotey (coteyr) wrote :

There is a problem with the default BIOS and suspending the laptop it's not linux related. I was able to get around this error by upgrading to the newest BIOS from HP. I have a tx2 1025dx. Running 2.6.28.9-custom (nothing is the custom but touchscreen driver modifications)

I do not know if this helps, but I thought I would let you know what I found.

Revision history for this message
Ryan (carbonfreeze) wrote :

I updated the bios from F2 to F12 and the issue still exists.

Revision history for this message
Ryan (carbonfreeze) wrote :

Additional behavior: When resuming from suspend, sometimes I don't even get a blinking cursor (only backlight on).

Revision history for this message
Andres Mujica (andres.mujica) wrote :

Hi Ryan

 Thanks for your report, as you reported this bug a while ago we need your help with this tests, so we can work on this issue.

1. Can you confirm this issue exists with the most recent Karmic Koala 9.10 Alpha release? ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/

2. If the issue remains with Karmic, it would be great to then also test the latest upstream mainline kernel available. This will allow additional upstream developers to examine it. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds

3. Finally, if you can take a look at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume and provide answers to the questions mentioned under the "Information Gathering" section that would be great.

Thank you so much, and sorry for the late reply.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Vikram Dhillon (dhillon-v10) wrote :

Can you confirm this issue exists with the most recent Karmic Koala 9.10 Alpha release. ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/ . If the issue remains with Karmic it would be great to then also test the latest upstream mainline kernel available. This will allow additional upstream developers to examine this issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds .

Finally, if you could also take a look at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume and provide answers to the questions ment,ioned under the "Information Gathering" section that would be great.

Thanks,
Vikram

Revision history for this message
Ryan (carbonfreeze) wrote :

I have tested with Karmic after upgrading from Jaunty via do-release-upgrade. Karmic up to date as of 10-02-2009.

I recently upgraded the BIOS to F21 firmware revision, this did not seem to have an effect on this issue.

I am still having this problem, I tested with pm-suspend and the KDE4 shutdown menu.

Of the 3 times I invoked suspend with pm-suspend from a virtual terminal (not from within X), 2 times the laptop failed to resume.

Of the 6 times I invoked suspend from the KDE4 shutdown menu, the laptop failed to resume once.

After enabling no_console_suspend I was able to briefly watch the output of pm-suspend before the system entered suspend mode. I noticed in all 3 cases that there appears to be a segfault or kernel oops that occurs just before the machine sleeps. I attempted to invoke 'pm-suspend > logfile' but after restarting the file is always empty (even if wake from suspend is successful).

Revision history for this message
Ryan (carbonfreeze) wrote :

Additionally, when fglrx is removed and the laptop is configured to use the RadeonHD driver, wake from suspend has worked approximately 40 times with only one failure to resume (which I believe was due to using Karmic in an alpha state, I have not experienced a failure to resume with radeonhd in atleast a week).

Revision history for this message
Ryan (carbonfreeze) wrote :

Did the machine break while going to sleep or waking up?

During resume from suspend the system goes through an initial wakeup period of approximately 4 seconds when hard disk activity can be seen, the display backlight turns on but the user is not returned to X. Hard disk activity due to running applications (indexing, etc) can be seen after resume, but the user cannot input any commands to the system. The user is unable to switch virtual terminals, restart X or restart/power down the system using the soft-shutdown via powerbutton. The powerbutton must be held to shutdown the system.

Is it reproducible?

When running FGLRX driver in Jaunty and Karmic wake from suspend fails approximately 20%.

Did it work before?

Not with FGLRX, but with RadeonHD suspend has failed to resume once with Karmic alpha (out of ~40 suspend cycles).

Do you end up with flashing caps-lock or similar?

Only during one failure to resume when running Jaunty with FGLRX, most failures simply provide the user with a black screen and an unresponsive system.

cat /proc/cmdline

root=UUID=cf378b06-0657-4fee-b3f0-2807d06bd372 ro quiet nosplash resume=/dev/mapper/swap i8042.reset no_console_suspend

cat /etc/initramfs-tools/conf.d/resume

RESUME=/dev/mapper/swap

Other information

It seems to happen on both battery and charger connected conditions. System uses encrypted /var /home and swap partitions.

Revision history for this message
Damiön la Bagh (kat-amsterdam) wrote :

I am experiencing the exact same issue.
I am at a training and if I leave my laptop sitting, close the top, or just work on it for a long time the
Capslock starts blinking and the keyboard and touchpad are unresponsive.

When I suspend and resume after resuming I also do not have any keyboard and touchpad.
The touchscreen works intermittently.
Running Karmic 9.10 2.6.31-18-generic
on the original out of the box F.03 BIOS

I tried to update the BIOS to F.25 with WINE but the BIOS upgrade Utility fails.
How did you manage to update the BIOS???

Revision history for this message
Ryan (carbonfreeze) wrote :

In Lucid (up to date as of 3/11/10):

Running radeonhd driver, with F25 BIOS, this issue seems to be back. Again, about 20% of the time I suspend, I get a blinking white cursor on the screen when the laptop is resuming from suspend.

Revision history for this message
Robert Cotey (coteyr) wrote : Re: [Bug 362242] Re: [Hewlett-Packard HP TouchSmart tx2 Notebook PC] suspend/resume failure [non-free: fglrx]

I do not think this is related to the video driver. I get the same error if
I am running fglrx or an opensource driver (usually the generic one for
testing). This may however be an upstream bug, I will install
a vanilla kernel this weekend and see if the problem persists.

Thanks
Robert Cotey
(813) 421-4338
<email address hidden>

On Thu, Mar 11, 2010 at 12:44 PM, Ryan <email address hidden> wrote:

> In Lucid (up to date as of 3/11/10):
>
> Running radeonhd driver, with F25 BIOS, this issue seems to be back.
> Again, about 20% of the time I suspend, I get a blinking white cursor on
> the screen when the laptop is resuming from suspend.
>
> --
> [Hewlett-Packard HP TouchSmart tx2 Notebook PC] suspend/resume failure
> [non-free: fglrx]
> https://bugs.launchpad.net/bugs/362242
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Incomplete
>
> Bug description:
> Suspend has been failing lately with resume to a blinking white cursor
> (when opening the laptop lid from suspend).
>
> ProblemType: KernelOops
> Annotation: This occured during a previous suspend and prevented it from
> resuming properly.
> Architecture: amd64
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/share/apport/apportcheckresume
> Failure: suspend/resume
> InterpreterPath: /usr/bin/python2.6
> MachineType: Hewlett-Packard HP TouchSmart tx2 Notebook PC
> NonfreeKernelModules: fglrx
> Package: linux-image-2.6.28-11-generic 2.6.28-11.41
> ProcAttrCurrent: unconfined
> ProcCmdLine: root=UUID=cf378b06-0657-4fee-b3f0-2807d06bd372 ro quiet
> nosplash resume=/dev/mapper/swap i8042.reset
> ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
> ProcEnviron: PATH=(custom, no user)
> ProcVersionSignature: Ubuntu 2.6.28-11.41-generic
> SourcePackage: linux
> Tags: resume suspend
> Title: [Hewlett-Packard HP TouchSmart tx2 Notebook PC] suspend/resume
> failure [non-free: fglrx]
> UserGroups:
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/362242/+subscribe
>

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.