On 2/1/07, Steven Scholz <steven.scholz@xxxxxxxxxxxxx> wrote:
Hi all,
I am seeing kernel messages like
[ 1284.480000] hda: status timeout: status=0xd0 { Busy }
[ 1284.480000] ide: failed opcode was: unknown
[ 1284.480000] hda: no DRQ after issuing MULTWRITE_EXT
[ 1284.490000] ide0: unexpected interrupt, status=0x80, count=1
[ 1284.830000] ide0: reset: success
with a 2.5" Seagate ST940813AM on my embedded ARM system (linux 2.6.14, no
IDE controller. HDD registers just memory mapped).
HDD is used in PIO4 with MultSect=16.
What exactly does that mean? Only that the HDD is to slow to answer this
request with 100ms (WAIT_DRQ=(HZ/10))?
And will the request issued again after the reset of the drive?
Some old posting mentions that disabling "multi sector write" would help.
But I did not find any references to why this would solve the problem.
Is it a bug of this special HDD? Or a kernel problem?
Do you see this on every multiblock PIO write? Or just occasionally?
-
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
