anyone?
----- Original Message -----
From: <[email protected]>
To: <[email protected]>
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 [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
No answer for you but I've gotten this message also and was hoping
someone would know what/why...
Thus spake Steven Adams ([email protected]):
> anyone?
> ----- Original Message -----
> From: <[email protected]>
> To: <[email protected]>
> 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 [email protected]
> > 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 [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
:wq!
---------------------------------------------------------------------------
Robert L. Harris | GPG Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
Life is not a destination, it's a journey.
Microsoft produces 15 car pileups on the highway.
Don't stop traffic to stand and gawk at the tragedy.
It means DMA got disabled!
It also means improper exit from the FSM.
Andre Hedrick
LAD Storage Consulting Group
On Thu, 6 Nov 2003, Steven Adams wrote:
> anyone?
> ----- Original Message -----
> From: <[email protected]>
> To: <[email protected]>
> 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 [email protected]
> > 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 [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Yeh im getting more of them..
Anyone know any reason why it would happen?
>
>
> No answer for you but I've gotten this message also and was hoping
> someone would know what/why...
>
>
> Thus spake Steven Adams ([email protected]):
>
>> anyone?
>> ----- Original Message -----
>> From: <[email protected]>
>> To: <[email protected]>
>> 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 [email protected]
>> > 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 [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>
> :wq!
> ---------------------------------------------------------------------------
> Robert L. Harris | GPG Key ID: E344DA3B
> @ x-hkp://pgp.mit.edu
> DISCLAIMER:
> These are MY OPINIONS ALONE. I speak for no-one else.
>
> Life is not a destination, it's a journey.
> Microsoft produces 15 car pileups on the highway.
> Don't stop traffic to stand and gawk at the tragedy.
I do not have time to pause and trace/fix the mess.
However if you both can kindly finger the last kernel when you did not
have this error, it will help constrain the pain.
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Wed, 5 Nov 2003, Robert L. Harris wrote:
>
>
> No answer for you but I've gotten this message also and was hoping
> someone would know what/why...
>
>
> Thus spake Steven Adams ([email protected]):
>
> > anyone?
> > ----- Original Message -----
> > From: <[email protected]>
> > To: <[email protected]>
> > 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 [email protected]
> > > 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 [email protected]
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> :wq!
> ---------------------------------------------------------------------------
> Robert L. Harris | GPG Key ID: E344DA3B
> @ x-hkp://pgp.mit.edu
> DISCLAIMER:
> These are MY OPINIONS ALONE. I speak for no-one else.
>
> Life is not a destination, it's a journey.
> Microsoft produces 15 car pileups on the highway.
> Don't stop traffic to stand and gawk at the tragedy.
>
Well i only just started getting them and i started with 2.4.20 and
upgraded to 2.4.21 about 6weeks or so ago (or when it came out)
Started gettig errors about 4-5days ago..
Ive seen alot of other ppl with the same error on early kernels..
Any idea what it is
>
> I do not have time to pause and trace/fix the mess.
> However if you both can kindly finger the last kernel when you did not
> have this error, it will help constrain the pain.
>
> Cheers,
>
> Andre Hedrick
> LAD Storage Consulting Group
>
> On Wed, 5 Nov 2003, Robert L. Harris wrote:
>
>>
>>
>> No answer for you but I've gotten this message also and was hoping
>> someone would know what/why...
>>
>>
>> Thus spake Steven Adams ([email protected]):
>>
>> > anyone?
>> > ----- Original Message -----
>> > From: <[email protected]>
>> > To: <[email protected]>
>> > 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
>> [email protected]
>> > > 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 [email protected]
>> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>> :wq!
>> ---------------------------------------------------------------------------
>> Robert L. Harris | GPG Key ID: E344DA3B
>> @ x-hkp://pgp.mit.edu
>> DISCLAIMER:
>> These are MY OPINIONS ALONE. I speak for no-one else.
>>
>> Life is not a destination, it's a journey.
>> Microsoft produces 15 car pileups on the highway.
>> Don't stop traffic to stand and gawk at the tragedy.
>>
I went from 2.4.16 to 2.4.21-rc2-ac1. Unfortunately the machines in
question are production and it'll be about 3 weeks of testing before I
can change them again.
Thus spake [email protected] ([email protected]):
> Well i only just started getting them and i started with 2.4.20 and
> upgraded to 2.4.21 about 6weeks or so ago (or when it came out)
>
> Started gettig errors about 4-5days ago..
>
> Ive seen alot of other ppl with the same error on early kernels..
>
> Any idea what it is
>
> >
> > I do not have time to pause and trace/fix the mess.
> > However if you both can kindly finger the last kernel when you did not
> > have this error, it will help constrain the pain.
> >
> > Cheers,
> >
> > Andre Hedrick
> > LAD Storage Consulting Group
> >
> > On Wed, 5 Nov 2003, Robert L. Harris wrote:
> >
> >>
> >>
> >> No answer for you but I've gotten this message also and was hoping
> >> someone would know what/why...
> >>
> >>
> >> Thus spake Steven Adams ([email protected]):
> >>
> >> > anyone?
> >> > ----- Original Message -----
> >> > From: <[email protected]>
> >> > To: <[email protected]>
> >> > 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
> >> [email protected]
> >> > > 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 [email protected]
> >> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >> Please read the FAQ at http://www.tux.org/lkml/
> >>
> >> :wq!
> >> ---------------------------------------------------------------------------
> >> Robert L. Harris | GPG Key ID: E344DA3B
> >> @ x-hkp://pgp.mit.edu
> >> DISCLAIMER:
> >> These are MY OPINIONS ALONE. I speak for no-one else.
> >>
> >> Life is not a destination, it's a journey.
> >> Microsoft produces 15 car pileups on the highway.
> >> Don't stop traffic to stand and gawk at the tragedy.
> >>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
:wq!
---------------------------------------------------------------------------
Robert L. Harris | GPG Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
Life is not a destination, it's a journey.
Microsoft produces 15 car pileups on the highway.
Don't stop traffic to stand and gawk at the tragedy.