From: Florian Hinzmann <f.hinzmann@hamburg.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: andre@linux-ide.org, linux-kernel@vger.kernel.org,
jan-hinnerk_reichert@hamburg.de
Subject: problem solved - late answer.. (was: Re: DMA problems w/ PIIX3 IDE, 2.4.20-pre4-ac2)
Date: Tue, 22 Apr 2003 10:16:07 +0200 [thread overview]
Message-ID: <20030422101607.6bf1c30e.f.hinzmann@hamburg.de> (raw)
In-Reply-To: <1032187595.1285.13.camel@irongate.swansea.linux.org.uk>
Hello!
Quite some months ago I raised some questions, got some answers and
continued working silently until my problem was solved. While digging
the archives for yet another IDE problem today I realized I did
not send any message to you guys nor to the list afterwards.
Just in case someone is interested or cares still:
1) Sorry for not sending a "problem solved" mail when it was solved
2) My box is running smoothly again. It was neither a kernel issue
nor a hardware problem with the disks. Different kernel versions
did behave differently, but the cause of it all seems to be a broken
CPU (or broken jumper settings).
Installing a new CPU made all problems go away. And the box is
rock solid with or without IDE-DMA turned on.
Regards
Florian
P.S: A little block quoted below in case someone wants to remember what
this was about:
On 16 Sep 2002 15:46:35 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Mon, 2002-09-16 at 15:26, 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.
> >
> > 2.4.19 should complain, too, if there is a physical error indeed, right?
>
> The "sectoridnotfound" return is from the drive. That makes it very hard
> to believe it isnt a physical error
>
--
Florian Hinzmann private: f.hinzmann@hamburg.de
Debian: fh@debian.org
PGP Key / ID: 1024D/B4071A65
Fingerprint : F9AB 00C1 3E3A 8125 DD3F DF1C DF79 A374 B407 1A65
next prev parent reply other threads:[~2003-04-22 8:04 UTC|newest]
Thread overview: 12+ 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 ` Florian Hinzmann [this message]
2002-09-16 15:32 ` Russell King
2002-09-16 8:58 ` 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=20030422101607.6bf1c30e.f.hinzmann@hamburg.de \
--to=f.hinzmann@hamburg.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--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
all inboxes | Powered by JetHome®