From: Chris Wedgwood <cw@f00f.org>
To: Rodrigo Ventura <yoda@isr.ist.utl.pt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems with 2.4.7 and VIA IDE
Date: Sun, 29 Jul 2001 03:44:52 +1200 [thread overview]
Message-ID: <20010729034452.A2685@weta.f00f.org> (raw)
In-Reply-To: <lxvgkddrsh.fsf@pixie.isr.ist.utl.pt> <lxn15pdr5p.fsf@pixie.isr.ist.utl.pt>
In-Reply-To: <lxn15pdr5p.fsf@pixie.isr.ist.utl.pt>
On Sat, Jul 28, 2001 at 04:12:02PM +0100, Rodrigo Ventura 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 }
bad IDE cable?
I also have errors from the ethernet devices, e.g.
eth0: Transmit error, Tx status register 82.
Probably a duplex mismatch. See Documentation/networking/vortex.txt
^^^^^^^^^^^^^^^^^^^^^^^^^^
look |
--cw
next prev parent reply other threads:[~2001-07-28 15:44 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 [this message]
2001-07-30 14:22 ` Rodrigo Ventura
2001-07-28 16:22 ` Alan Cox
2001-07-29 4:11 ` Josh McKinney
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=20010729034452.A2685@weta.f00f.org \
--to=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yoda@isr.ist.utl.pt \
/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