Recurring random freezes with 2.6.0-test9

Recurring random freezes with 2.6.0-test9

[Andrew S. Johnson]

I have 2.4.22 running fine on this box, before and after
trying 2.6.0-test9.  What happens is that I can use the
box for a few minutes, then it locks up hard for no apparent
reason.  The hard drive light comes on and stays on,
sysrq is unresponsive, and no response via ethernet.
This has happened everytime I've used -test9 (about
4-6 times).  The kernel is compiled for K7 (Athlon).

I have support for IDE disk, VIA vt82c686b, HPT370A,
and PDC20269 compiled in.  There is nothing in any
log file that hints of trouble.  Here's part of syslog, FWIW:

kernel: PCI: Probing PCI hardware
kernel: PCI: Probing PCI hardware (bus 00)
kernel: Disabling VIA memory write queue (PCI ID 0305, rev 03): [55] 89 & 1f -> 09
kernel: pty: 256 Unix98 ptys configured
kernel: RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
kernel: hda: Maxtor 94610U6, ATA DISK drive
kernel: Using anticipatory io scheduler
kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
kernel: hdc: HL-DT-ST RW/DVD GCC-4480B, ATAPI CD/DVD-ROM drive
kernel: ide1 at 0x170-0x177,0x376 on irq 15
kernel: hde: Maxtor 6Y160P0, ATA DISK drive
kernel: ide2 at 0xbc00-0xbc07,0xc002 on irq 11
kernel: HPT37X: using 33MHz PCI clock
kernel: hdi: MAXTOR 4K080H4, ATA DISK drive
kernel: ide4 at 0xdc00-0xdc07,0xe002 on irq 11
kernel: hda: max request size: 128KiB
kernel: hde: max request size: 1024KiB
kernel: hdi: max request size: 128KiB
kernel: EXT2-fs warning (device hda5): ext2_fill_super: mounting ext3 filesystem as ext2
kernel:
kernel: VFS: Mounted root (ext2 filesystem) readonly.
kernel: sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
kernel: blk: queue dfe10400, I/O limit 4095Mb (mask 0xffffffff)
kernel: blk: queue dfe02400, I/O limit 4095Mb (mask 0xffffffff)
kernel: blk: queue dfdf7800, I/O limit 4095Mb (mask 0xffffffff)

Is there anything else I can provide that would be useful?
Is there anything I can turn on to get more info when this happens?

Andy Johnson

hda: no DRQ after issuing WRITE

[steve]

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

Re: Recurring random freezes with 2.6.0-test9

[Mike Fedyk]

On Tue, Nov 04, 2003 at 08:29:38PM -0600, Andrew S. Johnson wrote:
> I have 2.4.22 running fine on this box, before and after
> trying 2.6.0-test9.  What happens is that I can use the
> box for a few minutes, then it locks up hard for no apparent
> reason.  The hard drive light comes on and stays on,
> sysrq is unresponsive, and no response via ethernet.
> This has happened everytime I've used -test9 (about
> 4-6 times).  The kernel is compiled for K7 (Athlon).

I get something similar, but it takes a few days.

This is with 2.6.0-test6-mm4 #2 SMP Mon Oct 6 02:32:09 PDT 2003

I've been meaning to update for a while now... :-/

Re: no DRQ after issuing WRITE

[Steven Adams]

anyone?
----- Original Message ----- 
From: <steve@drifthost.com>
To: <linux-kernel@vger.kernel.org>
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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: no DRQ after issuing WRITE

[Robert L. Harris]

[-- Attachment #1: Type: text/plain, Size: 2832 bytes --]



No answer for you but I've gotten this message also and was hoping
someone would know what/why...


Thus spake Steven Adams (steve@drifthost.com):

> anyone?
> ----- Original Message ----- 
> From: <steve@drifthost.com>
> To: <linux-kernel@vger.kernel.org>
> 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@vger.kernel.org
> > 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@vger.kernel.org
> 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.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: no DRQ after issuing WRITE

[steve]

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 (steve@drifthost.com):
>
>> anyone?
>> ----- Original Message -----
>> From: <steve@drifthost.com>
>> To: <linux-kernel@vger.kernel.org>
>> 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@vger.kernel.org
>> > 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@vger.kernel.org
>> 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.

Re: no DRQ after issuing WRITE

[Andre Hedrick]

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: <steve@drifthost.com>
> To: <linux-kernel@vger.kernel.org>
> 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@vger.kernel.org
> > 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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

Re: no DRQ after issuing WRITE

[Andre Hedrick]

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 (steve@drifthost.com):
> 
> > anyone?
> > ----- Original Message ----- 
> > From: <steve@drifthost.com>
> > To: <linux-kernel@vger.kernel.org>
> > 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@vger.kernel.org
> > > 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@vger.kernel.org
> > 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.
> 

Re: no DRQ after issuing WRITE

[steve]

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 (steve@drifthost.com):
>>
>> > anyone?
>> > ----- Original Message -----
>> > From: <steve@drifthost.com>
>> > To: <linux-kernel@vger.kernel.org>
>> > 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@vger.kernel.org
>> > > 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@vger.kernel.org
>> > 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.
>>

Re: no DRQ after issuing WRITE

[Robert L. Harris]

[-- Attachment #1: Type: text/plain, Size: 4753 bytes --]



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 steve@drifthost.com (steve@drifthost.com):

> 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 (steve@drifthost.com):
> >>
> >> > anyone?
> >> > ----- Original Message -----
> >> > From: <steve@drifthost.com>
> >> > To: <linux-kernel@vger.kernel.org>
> >> > 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@vger.kernel.org
> >> > > 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@vger.kernel.org
> >> > 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 majordomo@vger.kernel.org
> 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.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]