HDD connection error after suspend to ram

Bug #371732 reported by nameiner on 2009-05-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

After a Suspend to Ram the system wakes up but is unusable. It comes up with some error messages from the notification widget, but these are following errors and not the cause of it.
This is a SATA system, I don't have that problem on my IDE system.
After switching to a virtual console I can't login but see the following error messages over and over again:

ata1: exception Emask 0x10 Sact 0x0 Serr 0x4000000 action 0xe frozen
ata1: irq_stat 0x00000040, connection status changed
ata1: SError: { DevExch }
ata2: exception Emask 0x10 Sact 0x0 Serr 0x4000000 action 0xe frozen
ata2: irq_stat 0x00000040, connection status changed
ata2: SError: { DevExch }

System info:
HP dv4-1120us, 4GB Ram, 250GB SATA HDD
Kubuntu 9.04 64bit installed with WIBU under Windows Vista 64bit
Kernel Version: 2.6.27-11-generic

nameiner (nameiner) wrote :
Jonas Norlander (jonorland) wrote :

I can verify that I also get that or a very similar error when I resume from hibernate or suspend to ram.
When I resume my system is almost unresponsive and the console is filled with this error.

I have two harddrives in my PC, i'm not sure which drives give the error but I think it's the Maxtor drive.
Model Family: Seagate Barracuda ES
Device Model: ST3320620NS
Serial Number: 9QF7XM0P
Firmware Version: 3.AEG
User Capacity: 320 072 933 376 bytes

Model Family: Maxtor DiamondMax 10 family (SATA/300)
Device Model: Maxtor 6V300F0
Serial Number: V600DM9G
Firmware Version: VA111630
User Capacity: 300 090 728 448 bytes

Motherboard: ASUS M2N-SLI DELUXE ACPI BIOS Revision 1502

nameiner (nameiner) wrote :

I have a Western Digital WDC WD2500BEVS-60UST0. That means it is not a HDD model/manufacturer specific problem.
I attached my hdparm output.

nameiner (nameiner) wrote :

I can't test if it also happens for Suspend to Disk, since my WIBU-Installation only offers 256MB of swap which leads to a message stating that there is not enough such swap space to suspend to disk.

description: updated
nameiner (nameiner) wrote :

I just upgraded my BIOS and the problem is gone. The system is responding and I can login on a console. The HDD is obviously detected/reconnected correctly. I can work with the applications that were open and can open new applications as well.

kurt belgrave (trinikrono) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
Since you are no longer affected by this bug, i am closing the bug report

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers