Re: [sata_sil] kernel 2.6.17(-mm2) test - timeout issue

["Martin Ammermüller" <tenco@gmx.de>]

[-- Attachment #1: Type: text/plain, Size: 2133 bytes --]

Am Sonntag, den 25.06.2006, 12:06 +0900 schrieb Tejun Heo:
> Failed commands are retried several times, so no data was lost in your 
> case.  If data gets lost, you'll see more error messages from higher 
> layers (SCSI, FS).

With high disk I/O and a 2.6.18-rc1 kernel i get these errors (depending
upon the work i do, up to several times a day):

ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x400000 action 0x2 frozen
ata1.00: (BMDMA stat 0x20)
ata1.00: tag 0 cmd 0xc8 Emask 0x2 stat 0x58 err 0x0 (HSM violation)
ata1: soft resetting port
ata1: port is slow to respond, please be patient
ata1: port failed to respond (30 secs)
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ATA: abnormal status 0xD8 on port 0xDCA18087
ATA: abnormal status 0xD8 on port 0xDCA18087
ATA: abnormal status 0xD8 on port 0xDCA18087
ATA: abnormal status 0xD8 on port 0xDCA18087
ATA: abnormal status 0xD8 on port 0xDCA18087
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.00: revalidation failed (errno=-5)
ata1: failed to recover some devices, retrying in 5 secs
ata1: hard resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/100
ata1: EH complete
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back

> Anyways, if your harddisk is doing this regularly, 
> your hardware is faulty.  Maybe the connection between the controller 
> and the disk is the problem or the disk itself.

I did not get those errors with Windows XP and i am not the only one who
has problems running this particular laptop model with a linux kernel.
Ok, to be honest, there's actually only one person i know of which
bothered enough about exactly the same errors to send me an e-mail (he
discovered at least one of my messages to this list). But in my
experience there are almost always others getting the same error, but
which remain silent.

Anyway, i will try to probe the device with smartmontools.

Regards,
Martin Ammermüller

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 191 bytes --]