Hi,
yes this was AHCI. NCQ was enabled. I forgot to mention kernel version:
2.6.26-1-amd64 (Debian Lenny)
So here is my test:
Enabled AHCI in BIOS.
[ 0.000000] Command line: root=/dev/md1 ro libata.force=noncq
[ 0.000000] Kernel command line: root=/dev/md1 ro libata.force=noncq
[...]
[ 3.237941] ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps
0x3f impl SATA mode
[ 3.238000] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo
pmp pio slum part
Ah, NCQ still activated.
/sys/block/sdc/device/queue_depth shows 31.
I guess NCQ still activated even with libata.force=noncq ?
Now here is my second test:
Disabled AHCI in BIOS.
ata_piix is used now. Did some IO, can't force any freezes.
In the meantime I found topics like this:
http://forums.seagate.com/stx/board/message?board.id=ata_drives&thread.id=2879&view=by_date_ascending&page=1
This looks like a firmware bug. I think I should contact Seagate ;) or
any other ideas?
Bye
Tejun Heo wrote:
Hello,
Thomas Jackowski wrote:
This is /dev/sdc. /dev/sdd and /dev/sde is the same model with the same
Firmware. I'm using a RAID5 on these 3 HDDs.
Because of the Seagate Firmware Bug I had to upgrade the firmware from
'SD15' to 'SD1A'. The upgrade was successful.
Before the upgrade there were no problems, after the upgrade I have
trouble like this:
...
[14144.875931] ata4.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0
Timeout on IDENTIFY.
[507139.744602] ata5.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0
[507453.049519] ata4.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0
and two timeouts on CHK_POWER.
ahci, right? Given that the problem appeared after firmware update,
it seems to indicate firmware problem. Does libata.force=noncq make
any difference?
--
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
