Skip to contentSkip to conversation

"ATA: abnormal status" after wakeup from STR

DISCUSSION Pavel Troller 1 participant 2 messages Feb 28, 2006 ACPI

lore
Share & tools
lore
#0 lore raw

Hi!
I'm observing a problem on two different motherboards from MSI, one equipped
with VIA chipset (for Athlon) and the other with Intel (for P-4). The problem, however, looks the same.
When awaking from STR, at the whole end, there appears:
Restarting tasks...<4>ATA: abnormal status 0x80 on port 0xE907 abnormal status 0x80 on port 0xE907
abnormal status 0x80 on port 0xE907
done
ata1: command 0x35 timeout, stat 0x50 hosts_stat 0x1
The system then continues to operate with no visible damage.
In /proc/ioports I see the IO port assigned to libata. The system uses a SATA
disk, so it's related.
The timeout mentioned in the message is something about 30 seconds. The time
to wake up from STR is very long due to this.
I have the following questions:
1) Is it safe to operate the system after such an event ? Is the SATA iface
in sane state and is it able to work reliably ?
2) Is there a known method to fix the problem now ? I've read something about
SATA patches but didn't experiment with anything yet. Would you recommend me to try something ?
With regards, Pavel Troller

P.S. I forgot to say, it's on 2.6.15.4.

#1 lore raw
Quoted 23 lines

Hi!
I'm observing a problem on two different motherboards from MSI, one equipped
with VIA chipset (for Athlon) and the other with Intel (for P-4). The problem, however, looks the same.
When awaking from STR, at the whole end, there appears:
Restarting tasks...<4>ATA: abnormal status 0x80 on port 0xE907 abnormal status 0x80 on port 0xE907
abnormal status 0x80 on port 0xE907
done
ata1: command 0x35 timeout, stat 0x50 hosts_stat 0x1
The system then continues to operate with no visible damage.
In /proc/ioports I see the IO port assigned to libata. The system uses a SATA
disk, so it's related.
The timeout mentioned in the message is something about 30 seconds. The time
to wake up from STR is very long due to this.
I have the following questions:
1) Is it safe to operate the system after such an event ? Is the SATA iface
in sane state and is it able to work reliably ?
2) Is there a known method to fix the problem now ? I've read something about
SATA patches but didn't experiment with anything yet. Would you recommend me to try something ?
With regards, Pavel Troller

Quoted 1 line

P.S. I forgot to say, it's on 2.6.15.4.

Hi!
Replying to myself with new information:
I've just tried 2.6.16-rc5 and results are much worse - the disk is dead. On resume, the following occurs:

ATA: abnormal status 0x80 on port 0xE907
ATA: abnormal status 0x80 on port 0xE907
ATA: abnormal status 0x80 on port 0xE907
ata1: qc timeout (cmd 0xef)
ata1: failed to set xfermode, disabled
ata1: dev 0 configured for UDMA/133
Restarting tasks...<6>sd 0:0:0:0: SCSI error: return code = 0x40000
end_request: I/O error, dev sda, sector 6511
sd 0:0:0:0: SCSI error: return code = 0x40000
end_request: I/O error, dev sda, sector 6519
sd 0:0:0:0: SCSI error: return code = 0x40000
end_request: I/O error, dev sda, sector 6527
Buffer I/O error on device sda1, logical block 808
lost page write due to I/O error on sda1
Aborting journal on device sda1.

With regards, Pavel Troller