From: Russell King <rmk@arm.linux.org.uk>
To: Florian Hinzmann <f.hinzmann@hamburg.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andre Hedrick <andre@linux-ide.org>,
linux-kernel@vger.kernel.org,
Jan-Hinnerk Reichert <jan-hinnerk_reichert@hamburg.de>
Subject: Re: DMA problems w/ PIIX3 IDE, 2.4.20-pre4-ac2
Date: Mon, 16 Sep 2002 16:32:06 +0100 [thread overview]
Message-ID: <20020916163206.B23094@flint.arm.linux.org.uk> (raw)
In-Reply-To: <XFMail.20020916162624.f.hinzmann@hamburg.de>; from f.hinzmann@hamburg.de on Mon, Sep 16, 2002 at 04:26:24PM +0200
On Mon, Sep 16, 2002 at 04:26:24PM +0200, Florian Hinzmann wrote:
>
> On 16-Sep-2002 Alan Cox wrote:
> > On Mon, 2002-09-16 at 12:17, Florian Hinzmann wrote:
> >> kernel: hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
> >> kernel: hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=97567071, high=5, lo
> >> kernel: hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
> >
> > Which is the drive reporting a physical media error
>
> Which seems to exist only while using the named combinations of DMA access
> and kernel versions. While using i.e. 2.4.19 without DMA I can access the same data,
> dd the whole disk to /dev/null or run badblock checks without finding
> any physical media errors.
Let me get this straight. If you run this exact procedure, what happens?
1. start with DMA turned on
2. dd the whole disk to /dev/null
3. disable DMA
4. dd the whole disk to /dev/null
5. re-enable DMA
6. dd the whole disk to /dev/null
7. disable DMA
8. dd the whole disk to /dev/null
Are you saying that steps 2 and 6 produce a sectoridnotfound error, while
step 4 and 8 works without problem?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-09-16 15:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-14 14:35 DMA problems w/ PIIX3 IDE, 2.4.20-pre4-ac2 Jan-Hinnerk Reichert
2002-09-14 22:40 ` Andre Hedrick
2002-09-16 11:17 ` Florian Hinzmann
2002-09-16 12:33 ` Alan Cox
2002-09-16 14:26 ` Florian Hinzmann
2002-09-16 14:46 ` Alan Cox
2002-09-16 15:29 ` Florian Hinzmann
2002-09-16 16:13 ` Jan-Hinnerk Reichert
2002-09-16 16:19 ` Daniela Engert
2003-04-22 8:16 ` problem solved - late answer.. (was: Re: DMA problems w/ PIIX3 IDE, 2.4.20-pre4-ac2) Florian Hinzmann
2002-09-16 15:32 ` Russell King [this message]
2002-09-16 8:58 ` DMA problems w/ PIIX3 IDE, 2.4.20-pre4-ac2 Florian Hinzmann
-- strict thread matches above, loose matches on Subject: below --
2002-09-04 9:47 Florian Hinzmann
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=20020916163206.B23094@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=f.hinzmann@hamburg.de \
--cc=jan-hinnerk_reichert@hamburg.de \
--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