From: Ken Brownfield <ken@irridia.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: m.knoblauch@TeraPort.de,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Filesystem Corruption (ext2) on Tyan S2462, 2xAMD1900MP, 2.4.17SMP (RH7.2)
Date: Tue, 19 Mar 2002 19:33:33 -0600 [thread overview]
Message-ID: <20020319193333.C15811@asooo.flowerfire.com> (raw)
In-Reply-To: <20020319190211.B15811@asooo.flowerfire.com> <E16nUx8-0000w4-00@the-village.bc.nu>
On Wed, Mar 20, 2002 at 01:31:46AM +0000, Alan Cox wrote:
| I can confirm problems with serverworks OSB4 and UDMA. With UDMA and
[...]
Thanks. This also points out that I mistakenly said DMA rather than
UDMA. Someone else mentioned to me that MDMA worked for them as well.
It would have been "fine" if the serverworks driver didn't leave UDMA on
when it's off by default in the CONFIG. At least then you would be
making the choice to specifically enable UDMA at your own risk...
| This was observed across a large number of boxes in a rendering farm so its
| not a one off flawed box, and across two board vendors. I reported it to
| serverworks who were interested but couldnt reproduce it in their lab.
Quite possible. I'm only seeing this on ServerWorks mobos with IDE as
primary (vs SCSI). I heard third-hand via a FreeBSD post that it's an
OSB4 issue effecting them as well. Are Seagates a requirement for the
issues?
As to whether they can reproduce it... I'm not holding my breath for
them to try.
Thanks much for the info,
--
Ken.
ken@irridia.com
next prev parent reply other threads:[~2002-03-20 1:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-19 18:42 Filesystem Corruption (ext2) on Tyan S2462, 2xAMD1900MP, 2.4.17SMP (RH7.2) Martin Knoblauch
2002-03-20 1:02 ` Ken Brownfield
2002-03-20 1:31 ` Alan Cox
2002-03-20 1:29 ` Andre Hedrick
2002-03-20 1:41 ` Ken Brownfield
2002-03-20 2:01 ` Alan Cox
2002-03-20 1:53 ` Filesystem Corruption (ext2) on Tyan S2462, 2xAMD1900MP, 2.4.17SMP Alan Cox
2002-03-20 2:36 ` Andre Hedrick
2002-03-20 10:32 ` Alan Cox
2002-03-20 10:04 ` Martin Knoblauch
2002-03-20 15:27 ` Re[2]: " Nerijus Baliunas
2002-03-20 15:49 ` Alan Cox
2002-03-20 1:33 ` Ken Brownfield [this message]
2002-03-20 1:56 ` Filesystem Corruption (ext2) on Tyan S2462, 2xAMD1900MP, 2.4.17SMP (RH7.2) Alan Cox
2002-03-20 16:10 ` Vojtech Pavlik
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=20020319193333.C15811@asooo.flowerfire.com \
--to=ken@irridia.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=m.knoblauch@TeraPort.de \
/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