From: Roger Luethi <rl@hellgate.ch>
To: Grant Coady <Grant.Coady@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??
Date: Sun, 14 Aug 2005 14:12:55 +0200 [thread overview]
Message-ID: <20050814121255.GA2695@k3.hellgate.ch> (raw)
In-Reply-To: <54nnf1tv8722aq6med3mlr4mvg7nli0r09@4ax.com>
> @@ -31,7 +31,7 @@
> #define APC_BPORT_REG 0x30
>
> #define APC_REGMASK 0x01
> -define APC_BPMASK 0x03
> +#define APC_BPMASK 0x03
Color me skeptical. I've seen some weird bit flips and data corruption;
"paramters" to "paramEters" I could buy. But data corruption that
_inserts_ a hash mark a the beginning of a line of a header file? What
are the odds?
> Today disabled onboard via-rhine and used Intel pro/100 + e100 driver,
> several source trees unpacked identically, running 2.6.12.4 or 2.4.31-hf3
While that seems to point to the Rhine as the possible cause, I can't
see how any driver could possibly be involved in this.
Roger
next prev parent reply other threads:[~2005-08-14 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 23:43 Via-Rhine NIC, Via SATA or reiserfs broken, how to tell?? Grant Coady
2005-08-12 10:43 ` Vladimir V. Saveliev
2005-08-12 12:19 ` Grant Coady
2005-08-12 14:21 ` Masoud Sharbiani
2005-08-12 22:13 ` Grant Coady
2005-08-14 9:12 ` Resolved?: " Grant Coady
2005-08-14 12:12 ` Roger Luethi [this message]
2005-08-14 20:13 ` Grant Coady
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=20050814121255.GA2695@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=Grant.Coady@gmail.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