From: Vojtech Pavlik <vojtech@suse.cz>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: "Gryaznova E." <grev@namesys.botik.ru>,
martin@dalecki.de, Linux Kernel <linux-kernel@vger.kernel.org>,
Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>
Subject: Re: IDE problem: linux-2.5.17
Date: Fri, 24 May 2002 00:45:46 +0200 [thread overview]
Message-ID: <20020524004546.E27005@ucw.cz> (raw)
In-Reply-To: <3CECF59B.D471F505@namesys.botik.ru> <3CECFC5B.3030701@evision-ventures.com>
On Thu, May 23, 2002 at 04:27:39PM +0200, Martin Dalecki wrote:
>
> > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> Since this error can be expected to be quite common.
> Its an installation error. I will just make the corresponding
> error message more intelliglible to the average user:
>
> hda: checksum error on data transfer occurred!
>
> Would have hinted you propably directly at what's wrong.
There is a routine in the IDE code to decrease transfer speed in case of
these problems. And it is there for a good reason - many (namely UDMA66)
mainboards have incorrectly wired IDE traces and can never achieve full
UDMA speeds, and there is no way to know.
For that I've also created UDMA_SLOW, which is even slower than UDMA_0
(16.6 MB/sec), which still has CRC protection, and needs even less
physical bandwidth than PIO4.
--
Vojtech Pavlik
SuSE Labs
prev parent reply other threads:[~2002-05-23 22:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 13:58 IDE problem: linux-2.5.17 Gryaznova E.
2002-05-23 14:17 ` Martin Dalecki
2002-05-23 17:48 ` Gryaznova E.
2002-05-23 18:03 ` Tomas Szepe
2002-05-23 18:44 ` Andre Hedrick
2002-05-23 17:49 ` Martin Dalecki
2002-05-23 19:11 ` Andre Hedrick
2002-05-23 19:13 ` Andre Hedrick
2002-05-24 15:05 ` Alan Cox
2002-05-23 22:40 ` Vojtech Pavlik
2002-05-23 18:07 ` Martin Dalecki
2002-05-23 22:42 ` Vojtech Pavlik
2002-05-23 22:37 ` Vojtech Pavlik
2002-05-23 14:27 ` Martin Dalecki
2002-05-23 15:39 ` [reiserfs-dev] " Oleg Drokin
2002-05-23 14:44 ` Martin Dalecki
2002-05-23 16:00 ` Oleg Drokin
2002-05-23 22:52 ` Vojtech Pavlik
2002-05-23 21:47 ` Lionel Bouton
2002-05-23 22:55 ` Vojtech Pavlik
2002-05-24 0:23 ` Lionel Bouton
2002-05-24 1:04 ` Andre Hedrick
2002-05-24 5:56 ` Vojtech Pavlik
2002-05-24 8:53 ` Lionel Bouton
2002-05-24 4:53 ` Oleg Drokin
2002-05-23 22:50 ` Vojtech Pavlik
2002-05-24 11:03 ` Martin Dalecki
2002-05-24 13:15 ` Vojtech Pavlik
2002-05-24 12:15 ` Martin Dalecki
2002-05-24 13:20 ` Vojtech Pavlik
2002-05-24 13:40 ` Martin Dalecki
2002-05-24 14:54 ` Vojtech Pavlik
2002-05-23 15:52 ` Tomas Szepe
2002-05-23 16:02 ` Oleg Drokin
2002-05-23 22:45 ` Vojtech Pavlik [this message]
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=20020524004546.E27005@ucw.cz \
--to=vojtech@suse.cz \
--cc=Reiserfs-Dev@namesys.com \
--cc=dalecki@evision-ventures.com \
--cc=grev@namesys.botik.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
/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