On Mon, 31 Mar 2008, Mark Lord wrote:
Mmm.. the one Tomas Lund has is on what appears to be AHCI (ICH9R).
Yes, indeed:
# lspci -v -nn -s 00:1f.2
00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA AHCI Controller [8086:2922] (rev 02) (prog-if 01 [AHCI 1.0])
Subsystem: Super Micro Computer Inc Unknown device [15d9:d180]
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 379
I/O ports at 1c30 [size=8]
I/O ports at 1c24 [size=4]
I/O ports at 1c28 [size=8]
I/O ports at 1c20 [size=4]
I/O ports at 18e0 [size=32]
Memory at d8601000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/4 Enable+
Capabilities: [70] Power Management version 3
Capabilities: [a8] #12 [0010]
Capabilities: [b0] #13 [0306]
(dmesg output available at http://tlund.pp.se/envy4_dmesg.txt)
Tomas, if you move the "problem drive" to another port, does the error
follow the drive, or stay with the same port?
(Hopefully you can try that)
Yes, the drive has already been moved, and the problem did indeed move
with the drive. However, I am currently stressing the drives by copying
large amounts of files, in paralel sessions, and issuing "sync" every 30
seconds, and I have not seen the error since Mar 28 18:17 (current time
here is Apr 1 09:10).
The system does not have any data on it yet, and I am not really in a
hurry to get it into production. Willing to try anything to track this
problem down.
//tlund
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
