[TOSHIBA TOSHIBA NB205] hibernate/resume failure

Bug #428671 reported by emory
46
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Hibernate function doesn't work, upon forced shutdown due to system hang (by holding down power button) it tries to resume but hangs, failing.

Splash gives me a message saying it's resuming from hibernation but never works, requiring another hard power off.

Appears to work fine with s2disk in Jaunty, will be trying to implement same fix in Karmic and if it fails will update here.

ProblemType: KernelOops
Annotation: This occured during a previous hibernate and prevented it from resuming properly.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: emory 3354 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0440000 irq 22'
   Mixer name : 'Realtek ALC272'
   Components : 'HDA:10ec0272,1179ff6e,00100001'
   Controls : 10
   Simple ctrls : 6
Date: Sat Sep 12 19:16:59 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
HibernationDevice: RESUME=UUID=6c54972e-5fe9-473e-a481-fd2f20b22828
InterpreterPath: /usr/bin/python2.6
MachineType: TOSHIBA TOSHIBA NB205
Package: linux-image-2.6.31-10-generic 2.6.31-10.30~lp389040oga1
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: root=UUID=443e288e-f337-4cc7-aa3c-571251b69422 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-10.30~lp389040oga1-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-10-generic N/A
 linux-firmware 1.16
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: resume hibernate ubuntu-unr
Title: [TOSHIBA TOSHIBA NB205] hibernate/resume failure
Uname: Linux 2.6.31-10-generic i686
UserGroups:

WpaSupplicantLog:

dmi.bios.date: 04/07/2009
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.20
dmi.board.name: KAVAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV1.20:bd04/07/2009:svnTOSHIBA:pnTOSHIBANB205:pvrPLL20U-00201D:rvnTOSHIBA:rnKAVAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: TOSHIBA NB205
dmi.product.version: PLL20U-00201D
dmi.sys.vendor: TOSHIBA

Revision history for this message
emory (emoryl) wrote :
Revision history for this message
emory (emoryl) wrote :

s2disk doesn't work either. having a problem uploading that crash log however, sorry.

in jaunty i can use s2disk via changing the script in /usr/lib/hal as discussed in this thread:

http://ubuntuforums.org/showthread.php?t=1215665

these steps in Karmic (or via `sudo s2disk`) results in a hibernate that i cannot recover from, or a crash on hibernate that made my capslock key flash.

i have my capslock key mapped as a control key in the gnome keyboard panel, not via xmodmap.

i'm using a generic kernel built by Leann in this bug report and subsequent discussion related to getting audio working on the NB205:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/389040

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi emory,

If you can, try and see if either of the following may help with gathering additional info. First, take a look at
https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume . It contains some additional debug tips that my help. Also, the linux-crashdump package has been provided to help capture the contents of a Kernel Oops/Panic, especially in the event of a sudden system freeze/lockup. It may help here if you are experiencing a kernel panic. You will first need to install the linux-crashdump package, the apport-retrace package, and then reboot the system.

sudo apt-get install apport-retrace linux-crashdump
sudo reboot

Once installed and rebooted, try to hibernate/resume to reproduce the lock up. Upon the next reboot, run the following command from a Terminal (Applications->Accessories->Terminal):

sudo apport-retrace -s -R /var/crash/linux-image*-.crash > /tmp/crash.log

This collects the contents of the Kernel Oops/Panic and writes it to a file, "crash.log", in your /tmp directory. Please attach the resulting "crash.log" file to this bug report.

Thanks in advance!

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joey Stanford (joey) wrote :

I don't get a linux crash, I get something else which can't be traced:

joey@boofalo:~$ sudo apport-retrace -s -R /var/crash/susres.2009-10-07_16\:56\:16.739969.crash > /tmp/crash.log
report file does not contain required fields: CoreDump Package ExecutablePath

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Incomplete → Triaged
tags: added: regression-potential
Revision history for this message
Andy Whitcroft (apw) wrote :

If you are getting a flashing caps lock then this highly likely a kernel panic. You may get more information if you boot with no_console_suspend on the kernel command line, and then perform the hibernate from VT-1 via pm-hibernate. Please report any output from this here. Thanks.

Revision history for this message
Joey Stanford (joey) wrote :

Hi Andy,

No flashing caps lock.

Performed as recommended, no console output prior to the power down. Console not preserved on resume (failed to resume so it booted as normal). Same style crash log (attached).

tags: added: regression-release
removed: regression-potential
tags: added: karmic
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
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.