[gutsy] notebook with Intel ICH8 chipset fails to resume

[Alex Wauck]

I just got a HP dv2500t, and for the most part, things work fine. Suspending the notebook is fairly quick. However, upon resuming, I see only a terminal (X is still running, and I can switch to it), and it spits out several buffer I/O errors from my hard disk controller. The result is that I cannot access anything on the hard disk. I can't even do a clean shutdown because it can't read /sbin/reboot or /sbin/shutdown. I haven't tried any other distributions yet, so I don't know if this is an issue with Linux in general. The exact disk controller is:
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)

I'm quite comfortable with Linux internals and C, so if someone would like me to dig deeper, I would be happy to.

[Matthew Garrett (mjg59)]

This may be fixed with the next kernel upload, but it would help if you could provide the full error logs - if you run the dmesg command immediately before suspend, it should still be in the cache on resume.

[Alex Wauck (awauck)]

Since I can't write to disk and have no network connection on resume, I can't save the logs. However, the relevant section appears to be this:
sd 2:0:0:0: [sda] Starting disk
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: _GTF unexpected object type 0x1
ata3.00: revalidation failed (errno=-22)
ata3.00: limiting speed to UDMA/100:PIO3
ata3: failed to recover some devices, retrying in 5 secs
ata3: port is slow to respond, please be patient (Status 0x80)
ata3: COMRESET failed (errno=-16)
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: _GTF unexpected object type 0x1
ata3.00: ACPI on devcfg failed the second time, disabling (errno=-22)
ata3.00: revalidation failed (errno=1)
ata3.00: disabled
sd 2:0:0:0: [sda] START_STOP FAILED
sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK

The following then repeats, probably every time anything attempts to access the disk:
sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sda, sector XXXXXXXXXX

EXT3 then freaks out because it can't read the disk, so it remounts the filesystem read-only (which, of course, doesn't really help).

[Alex Wauck (awauck)]

The 2.6.22-13 kernel update fixed it. Great work!

[jeanseb (jeanseb-valette)]

I got similar problem with last kernel (2.6.22-14-generic) when i try to burn CD with arson (calling cdrdao) .

[66579.413464] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[66579.413477] ata1.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x2a data 61152 out
[66579.413480] res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[66584.451511] ata1: port is slow to respond, please be patient (Status 0xd0)
[66589.433604] ata1: device not ready (errno=-16), forcing hardreset
[66589.433611] ata1: soft resetting port
[66589.921563] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x2)
[66589.921570] ata1.00: revalidation failed (errno=-5)
[66589.921575] ata1: failed to recover some devices, retrying in 5 secs
[66594.923521] ata1: soft resetting port
[66595.399706] ata1.00: failed to IDENTIFY (device reports invalid type, err_mask=0x0)
[66595.399712] ata1.00: revalidation failed (errno=-22)
[66595.399718] ata1.00: limiting speed to UDMA/25:PIO3
[66595.399720] ata1: failed to recover some devices, retrying in 5 secs
[66600.401422] ata1: soft resetting port
[66600.877601] ata1.00: failed to IDENTIFY (device reports invalid type, err_mask=0x0)
[66600.877608] ata1.00: revalidation failed (errno=-22)
[66600.877613] ata1.00: disabled
[66600.877617] ata1: failed to recover some devices, retrying in 5 secs
[66606.051526] ata1.01: configured for UDMA/33
[66606.051552] ata1: EH complete

[Leann Ogasawara (leannogasawara)]

Hi jeanseb,

Care to open a new bug report as it seems you are experiencing a different bug than the original reporter. Also the original reporter commented this this issue was regarding Suspend/Resume and was fixed in Gutsy. Note that the Hardy Heron 8.04 release just came out so you'll want to test against this latest release which contain an updated version of the kernel. If the issue you see still exists, you'll want to open your new report against the "linux" package since beginning with the Hardy release kernel bugs are now reported against the "linux" package, not linux-source-2.6.xx. In the new bug report you'll also want to include the debugging information as outlined here - https://wiki.ubuntu.com/KernelTeamBugPolicies . Hope that helps. Thanks.