From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: kris <kris.buggenhout@skynet.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problems with Seagate 120 GB drives when mutlwrite = 16
Date: Sun, 19 Oct 2003 19:08:14 +0200 [thread overview]
Message-ID: <200310191908.14369.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <1066578892.3091.11.camel@borg-cube.lan>
On Sunday 19 of October 2003 17:54, kris wrote:
> Hi,
Hi,
> I have noticed some problems with recent large drives, connected to a
> variety of controllers.
>
> I tested with nforce ide controller, a CMD649 based controller and an
> Intel 870 cghipset. all have same or similar symptoms.
>
> Linux 2.4.22 kernel : (Linux borg-cube 2.4.22-xfs #2 SMP Tue Oct 7
> 20:53:04 CEST 2003 i686 unknown)
>
> Oct 6 15:52:12 borg-cube kernel: hdg: dma_timer_expiry: dma status ==
> 0x21
> Oct 6 15:52:22 borg-cube kernel: hdg: timeout waiting for DMA
> Oct 6 15:52:22 borg-cube kernel: hdg: timeout waiting for DMA
> Oct 6 15:52:22 borg-cube kernel: hdg: status error: status=0x58 {
> DriveReady SeekComplete DataRequest }
> Oct 6 15:52:22 borg-cube kernel:
> Oct 6 15:52:22 borg-cube kernel: hdg: drive not ready for command
> Oct 6 15:52:22 borg-cube kernel: hdg: status timeout: status=0xd0 {
> Busy }
> Oct 6 15:52:22 borg-cube kernel:
> Oct 6 15:52:22 borg-cube kernel: hdg: no DRQ after issuing WRITE
> Oct 6 15:52:22 borg-cube kernel: ide3: reset: success
>
> same in 2.4.20 ( kernel from Suse)
>
> 2.6.0-test6 :
>
> Oct 9 09:43:09 borg-cube kernel: hdg: dma_timer_expiry: dma status ==
> 0x21
> Oct 9 09:43:18 borg-cube kernel:
> Oct 9 09:43:19 borg-cube kernel: hdg: DMA timeout error
> Oct 9 09:43:19 borg-cube kernel: hdg: dma timeout error: status=0x58 {
> DriveReady SeekComplete DataRequest }
> Oct 9 09:43:19 borg-cube kernel:
> Oct 9 09:43:19 borg-cube kernel: hdg: status timeout: status=0xd0 {
> Busy }
> Oct 9 09:43:19 borg-cube kernel:
> Oct 9 09:43:19 borg-cube kernel: hdg: no DRQ after issuing MULTWRITE
> Oct 9 09:43:20 borg-cube kernel: ide3: reset: success
>
> same in 2.6.0-test8
>
> so behaviour is consistent.
>
> I can avoid this with either turning off dma access or disabling the
> multwrite ( hdparm -m0 /dev/hdg)
>
> is this a known bug, or should I file one ?
Error message is known, but fact that disabling PIO multiwrite cures
it is new, so please fill bugzilla entry.
Thanks!!
--bartlomiej
next prev parent reply other threads:[~2003-10-19 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 15:54 kris
2003-10-19 17:08 ` Bartlomiej Zolnierkiewicz [this message]
2003-10-24 13:33 ` kris
2003-10-25 7:23 ` Mark B
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=200310191908.14369.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=kris.buggenhout@skynet.be \
--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
all inboxes | Powered by JetHome®