From: Nicholas Petreley <nicholas@petreley.com>
To: Kirill Kozmin <kozkir-8@student.luth.se>
Cc: Andre Hedrick <andre@linux-ide.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: VIA686b chipset and dma_intr errors, and 3c905B errors
Date: Mon, 26 Mar 2001 14:28:58 -0800 [thread overview]
Message-ID: <20010326142858.A664@petreley.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10103161041040.14210-100000@master.linux-ide.org> <3AB93A75.D18A78EE@student.luth.se>
In-Reply-To: <3AB93A75.D18A78EE@student.luth.se>; from kozkir-8@student.luth.se on Thu, Mar 22, 2001 at 12:34:13AM +0100
>
> Ok, now its clear that I have a big troubles with hardware.
> I compiled kernel 2.2.18+IDE_patches with support for VIA chipset and still get
> errors of type:
>
> kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> before these kernel reports a long string of messages
>
I got those errors on a brand new IBM ATA100 drive. I
exchanged it for a new one which worked fine for a couple
of weeks, but now the new one is beginning to give me the
same errors. I've noticed a rash of people reporting these
errors since 2.4.x. Is it really that the new kernel is
simply better at reporting bad drives? Or is there
something else going on with the kernel? (Or are IBM
drives just crappy?)
Here's a portion of the messages I'm getting...
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error}
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=48973752, sector=1854944
end_request: I/O error, dev 03:08 (hda), sector 1854944
asus a7v/kt133
IDE is Via 686b
By the way, my 3c905B went bahooties since about ac21 I
think. I was under the impression that Alan backed out of
the suspected changes for ac23 but the problem remained. I
replaced it with an eepro100, but I don't know if it's the
card or what.
-Nick
--
**********************************************************
Nicholas Petreley Caldera Systems - LinuxWorld/InfoWorld
nicholas@petreley.com - http://www.petreley.com - Eph 6:12
**********************************************************
.
next prev parent reply other threads:[~2001-03-26 22:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 16:22 VIA686A chipset crash under 2.4.2-ac20 kozkir-8
2001-03-16 18:11 ` Andre Hedrick
2001-03-16 18:23 ` Re[2]: " kozkir-8
2001-03-16 18:42 ` Andre Hedrick
2001-03-16 19:03 ` Kirill Kozmin
2001-03-16 19:38 ` Andre Hedrick
2001-03-16 19:50 ` VIA686B + 2.2.18 (was: VIA686A chipset crash under 2.4.2-ac20) William Park
2001-03-20 18:39 ` Andre Hedrick
2001-03-21 23:34 ` VIA686A chipset crash under 2.4.2-ac20 Kirill Kozmin
2001-03-26 22:28 ` Nicholas Petreley [this message]
2001-03-27 4:19 ` VIA686b chipset and dma_intr errors, and 3c905B errors Nicholas Petreley
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=20010326142858.A664@petreley.com \
--to=nicholas@petreley.com \
--cc=andre@linux-ide.org \
--cc=kozkir-8@student.luth.se \
--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