Re: no DRQ after issuing WRITE

[Steven Adams]

anyone?
----- Original Message ----- 
From: <steve@xxxxxxxxxxxxx>
To: <linux-kernel@xxxxxxxxxxxxxxx>
Sent: Wednesday, November 05, 2003 2:05 PM
Subject: hda: no DRQ after issuing WRITE


> Hey guys,
>
> i keep getting things like this in my dmesg
>
> ============================================
> hda: status timeout: status=0xd0 { Busy }
>
> hda: no DRQ after issuing WRITE
> ide0: reset: success
> hda: status timeout: status=0xd0 { Busy }
>
> hda: no DRQ after issuing WRITE
> ide0: reset: success
> =============================================
>
> From hdparm
> ============================================
> /dev/hda:
>
>  Model=IC35L080AVVA07-0, FwRev=VA4OA52A, SerialNo=VNC402A4CBRJLA
>  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
>  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=52
>  BuffType=DualPortCache, BuffSize=1863kB, MaxMultSect=16, MultSect=off
>  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=160836480
>  IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
>  PIO modes:  pio0 pio1 pio2 pio3 pio4
>  DMA modes:  mdma0 mdma1 mdma2
>  UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
>  AdvancedPM=yes: disabled (255) WriteCache=enabled
>  Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1:  2 3 4 5
> =================================================
>
> Ive searched high and low to try find out what this means, all ive found
> it people keep saying its all different kinds of things..
>
> I was wondering if this means my hdd is drying or is ti a setting?
>
> Thanks guys,
> Steve
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/