Re: no DRQ after issuing MULTWRITE_EXT ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello.

Steven Scholz wrote:

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

   Looks like a spurious interrupt... Is your IDE IRQ shared with other devices?

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))?

Doubt it. The old ATA standard specified the maximum DRQ assertion time of 20 ms.

And will the request issued again after the reset of the drive?

   It should be.

MBR, Sergei
-
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

[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux