From: <steve@drifthost.com>
To: <Robert.L.Harris@rdlg.net>
Cc: <steve@drifthost.com>, <linux-kernel@vger.kernel.org>
Subject: Re: no DRQ after issuing WRITE
Date: Thu, 6 Nov 2003 15:10:10 +1100 (EST) [thread overview]
Message-ID: <1951.61.88.244.7.1068091810.squirrel@mail.drifthost.com> (raw)
In-Reply-To: <20031106032133.GD19875@rdlg.net>
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.
next prev parent reply other threads:[~2003-11-06 4:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 2:29 Recurring random freezes with 2.6.0-test9 Andrew S. Johnson
2003-11-05 3:05 ` hda: no DRQ after issuing WRITE steve
2003-11-05 23:42 ` Steven Adams
2003-11-06 3:21 ` Robert L. Harris
2003-11-06 4:10 ` steve [this message]
2003-11-06 4:13 ` Andre Hedrick
2003-11-06 5:21 ` steve
2003-11-06 23:27 ` Robert L. Harris
2003-11-06 4:11 ` Andre Hedrick
2003-11-05 4:26 ` Recurring random freezes with 2.6.0-test9 Mike Fedyk
[not found] <OJ0u.30g.5@gated-at.bofh.it>
[not found] ` <OJMR.41A.9@gated-at.bofh.it>
[not found] ` <OKSD.5oD.5@gated-at.bofh.it>
2003-12-15 11:08 ` no DRQ after issuing WRITE Daniel Lux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1951.61.88.244.7.1068091810.squirrel@mail.drifthost.com \
--to=steve@drifthost.com \
--cc=Robert.L.Harris@rdlg.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome