panasonic toughbook cf-y5 suspend / resume failure

Bug #350711 reported by discord
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Jaunty by discord

Bug Description

Information Gathering

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

Please indicate in the bug whether it is a sleep or wakeup failure and how you determined this.

resume failure, the computer began to resume then it locked up

Is it reproducible?

Yes, everytime I suspend / resume

Did it work before?

Has this sleep type (suspend or hibernate) ever worked in the past. If it has whch kernel release did it work on?

Yes, it worked in ubuntu 8.10 with every kernel available.

Please indicate in the bug whether it worked, and if so include the contents of /proc/version_signature from that release (or the Ubuntu version number if you do not have it).

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: Matsushita Electric Industrial Co.,Ltd. CF-Y5LWFZZBM
Package: linux-image-2.6.28-11-generic 2.6.28-11.38
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=bdfc2bdf-e356-4dd1-b5eb-ebc061b85820 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: [Matsushita Electric Industrial Co.,Ltd. CF-Y5LWFZZBM] suspend/resume failure
UserGroups:

Revision history for this message
discord (colin.williams) wrote :
Revision history for this message
discord (colin.williams) wrote :

Upgraded to a more recent kernel, no more failings...

Changed in linux (Ubuntu):
status: New → Fix Released
Revision history for this message
discord (colin.williams) wrote :

sometimes it just won't resume, other times it works :(

Changed in linux (Ubuntu):
status: Fix Released → New
Revision history for this message
ekingery (pj-mfc) wrote :

I have the same problem with the released version of 9.04. Let me know if I can assist with testing. The 'test-suspend' script did not report a bug, but it looks like this bug is the same issue I'm running into on my Panasonic CF-Y5. It worked before upgrading to 9.04.

Linux 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

Revision history for this message
discord (colin.williams) wrote :

I think it has something to do with the hard disk after resume. here is possibly relevant dmesg output from a recent resume

[23069.000101] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[23069.000163] ata1.00: cmd c8/00:08:2f:c7:99/00:00:00:00:00/ea tag 0 dma 4096 in
[23069.000164] res 40/00:80:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[23069.000267] ata1.00: status: { DRDY }
[23074.040119] ata1: link is slow to respond, please be patient (ready=0)
[23079.024120] ata1: device not ready (errno=-16), forcing hardreset
[23079.024136] ata1: soft resetting link
[23079.206526] ata1.00: configured for UDMA/100
[23079.206544] ata1: EH complete

I've been getting alot of kernel panics recently a few minutes after resume

Revision history for this message
discord (colin.williams) wrote :

It seems that at resume or after a second resume I get the following

ata1:SRST failed (errno=-16)
[17284.30070] sd 0:0:0:0: [sda] Resukt: hostbyts=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[17284.300087] EXT3-FS error (device sda2): ext3_get_inode_loc : unable to read inode block - inode=3459968,block=1382828

The system cannot write to the disk after this and it is quite possibly be what is causing the kernel panics. I cannot shutdown or run any programs after this.

Revision history for this message
^_Pepe_^ (jose-angel-fernandez-freire) wrote :

This bug was reported a while ago and there hasn't been any activity in
it recently. We were wondering if this is still an issue? Can you try
with the latest Karmic 9.10 release of Ubuntu? ISO CD images are
available from http://cdimage.ubuntu.com/releases/ .

If the issue remains, could you run the following command from a
Terminal (Applications->Accessories->Terminal) while running Karmic. It
will automatically gather and attach updated debug information to this
report.

apport-collect -p linux 350711

Thanks in advance

tags: added: jaunty
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
discord (colin.williams) wrote :

This bug is not an issue anymore

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
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.