suspend resume works but leads to disk i/o errors

Bug #400687 reported by AndrewCreer
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

On a compaq presario CG60 AMD
with
Linux bendigo 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 22:12:12 UTC 2009 x86_64 GNU/Li

I do a suspend and resume works but some disk access is broken. It seems the disk is mounted as read only

my repeatable debug cycle is

before the suspend i login on VT1 (cntrl-alt-f1) and then do a
sudo bash
echo 1 >/sys/power/pm_trace
then cntrl f7 to do a suspend from the gnome-panel menu

then i press the power button to resume and type dmesg >dmesg.txt
I get
dmesg.txt : read only file system

I did the same suspend -resume cycle with a mounted usb drive and I could save dmesg.txt

The offending section says
[ 1052.581339] PM: Finishing wakeup.
[ 1052.581340] Restarting tasks ... <6>sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_
OK
[ 1052.604034] end_request: I/O error, dev sda, sector 523083018
[ 1052.604129] Buffer I/O error on device sda5, logical block 58824825
[ 1052.604220] lost page write due to I/O error on sda5
[ 1052.604240] sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[ 1052.604242] end_request: I/O error, dev sda, sector 523083258
[ 1052.604330] Buffer I/O error on device sda5, logical block 58824855
[ 1052.604422] lost page write due to I/O error on sda5
[ 1052.604425] Buffer I/O error on device sda5, logical block 5882485

I'll attache the whole dmesg.txt file, and lspci output.
I am sure that other information will be required.

Thanks in advance
Andrew

Revision history for this message
AndrewCreer (andrewcreer) wrote :
Revision history for this message
AndrewCreer (andrewcreer) wrote :
Revision history for this message
JeSTeR7 (cblocker) wrote :

I get this exact same thing on resume from standby. I'm on Karmic AMD64

Revision history for this message
J.D. (fungs) wrote :

I get the same error on standard suspend to RAM (S3) over kernel when resuming once in a while. The error messages can thus not be written to disk any more.

This is on Karmic AMD64 using a Western Digital WD-WMAVU02433xx hard disk.

Revision history for this message
John McT (jmct1) wrote :

I have the same problem. I vote for further investigation.

Revision history for this message
Philip Muškovac (yofel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in the linux kernel.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi AndrewCreer,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, run the following command from a Terminal (Applications->Accessories->Terminal) it will automatically gather and attach updated debug information to this report.

apport-collect -p linux 400687

Also, please be sure to take a look at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume . If you can provide any additional information outlined there it would be much appreciated.

Additionally, if you could try to reproduce this with the upstream mainline kernel that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Thanks in advance.

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

tags: added: kernel-suspend
tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
AndrewCreer (andrewcreer) wrote :

Hi I feel a bit bad, but the problem was fixed a few kernel versions ago.
I am now using 2.6.31-20-generic #57-Ubuntu SMP Mon Feb 8 09:02:26 UTC 2010 x86_64 GNU/Linux

Not sure of etiquete. Should I close this bug when others seem to have the same problem?

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

AndrewCreer,
     As you are the original reporter, I am closing this issue as Fix Released. If the others that have marked this bug as sffecting them are still experiencing it, then this is an indication that they have encountered a different issue and would need to report a new bug for that.

Thanks!

~JFo

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.