From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Samuel Flory <sflory@rackable.com>, linux-kernel@vger.kernel.org
Cc: gibbs@scsiguy.com
Subject: Re: File system corruption under 2.4.21-pre5-ac1
Date: Mon, 31 Mar 2003 19:26:27 +0000 [thread overview]
Message-ID: <112820000.1049138786@caspian.scsiguy.com> (raw)
In-Reply-To: <3E88EA79.2060301@rackable.com>
> I'm seeing filesystem corruption on a number of intel SE7501wv2's under
> 2.4.21-pre5-ac1. The systems are running Cerberus (ctcs). They fail the
> kcompile, and memtst tests.
Are you running the aic79xx driver version embedded in that kernel version
or the latest from my site?
http://people.FreeBSD.org/~gibbs/linux/SRC/
--
Justin
next prev parent reply other threads:[~2003-04-01 2:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 1:25 File system corruption under 2.4.21-pre5-ac1 Samuel Flory
2003-03-31 19:26 ` Justin T. Gibbs [this message]
2003-04-01 18:11 ` Samuel Flory
-- strict thread matches above, loose matches on Subject: below --
2003-04-01 8:46 Martin Knoblauch
2003-04-01 20:23 ` Samuel Flory
2003-04-02 7:14 ` Martin.Knoblauch
2003-04-02 0:44 ` Justin T. Gibbs
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=112820000.1049138786@caspian.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sflory@rackable.com \
/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