From: Josh McKinney <forming@home.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Problems with 2.4.7 and VIA IDE
Date: Sat, 28 Jul 2001 23:11:24 -0500 [thread overview]
Message-ID: <20010728231123.A6128@home.com> (raw)
In-Reply-To: <E15QWqv-0007qf-00@the-village.bc.nu>
In-Reply-To: <E15QWqv-0007qf-00@the-village.bc.nu>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
On approximately Sat, Jul 28, 2001 at 05:22:09PM +0100, Alan Cox wrote:
> > This is sort of a continuation of my last msg. I tried a rpm
> > -Va on one xterm and a tar cf /dev/null / on another, and I got
> > another dma error:
> >
> > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> BadCRC is normally a cable error, but I'm suspicious that its also one of
> the things caused by PCI bus problems on the VIA stuff
I am running the same chipset and used to see these sort of problems in
the early 2.3pre and 2.4 days, but have not seen a BadCRC error for a long
time.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-07-29 4:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-28 14:58 Problems with 2.4.7 and VIA IDE Rodrigo Ventura
2001-07-28 15:12 ` Rodrigo Ventura
2001-07-28 15:44 ` Chris Wedgwood
2001-07-30 14:22 ` Rodrigo Ventura
2001-07-28 16:22 ` Alan Cox
2001-07-29 4:11 ` Josh McKinney [this message]
2001-07-29 16:30 ` Glenn C. Hofmann
2001-07-30 14:18 ` Rodrigo Ventura
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=20010728231123.A6128@home.com \
--to=forming@home.com \
--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