From: Vojtech Pavlik <vojtech@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ken Brownfield <ken@irridia.com>,
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: Wed, 20 Mar 2002 17:10:51 +0100 [thread overview]
Message-ID: <20020320171051.A19871@ucw.cz> (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:
> > We're seeing this with Tyan 2410s and Seagate drives. I think Tyan just
> > can't get DMA right. Luckily we mainly lost docs or man pages before we
> > disabled DMA, although losing the rpm database sucked. MDMA2 seems okay
> > but we haven't tested it long enough to form a lasting impression.
> > I'm actually patching the ServerWorks driver to honor the CONFIG flag,
> > since even with hdparm there is a narrow risk to the fs during the boot
> > process before DMA is disabled.
>
> I can confirm problems with serverworks OSB4 and UDMA. With UDMA and
> a seagate disk you see 4 bytes repeat from one transfer into the next
> shuffling all the data up 4 bytes (which since it includes inode and
> metadata is *messy*). Current 2.4 has detect code that sometimes traps this
> and panics to avoid fs death.
>
> With MWDMA all was fine.
>
> 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.
It seems like Daniela Engert found this problem too:
--------------------------------------------------------------------------------
Vendor
| Device
| | Revision ATA ATAPI ATA66 ATA133
| | | south/host bridge id PIO DMA PIO DMA ATA33 | ATA100| Docs
| | | | south/host bridge rev. 32bit | 32bit | | | | | avail
| | | | | | | | | | | | | |
v v v v v v v v v v v v v v
0x1166 ServerWorks
0x0211 OSB4 x x ? ? x - - - x
0x0212 CSB5
< 0x92 x x ? ? x x - - -
>= 0x92 x x ? ? x x x - -
known bugs:
- OSB4: at least some chip revisions can't do Ultra DMA mode 1 and above
- CSB5: no host side cable type detection.
--------------------------------------------------------------------------------
--
Vojtech Pavlik
SuSE Labs
prev parent reply other threads:[~2002-03-20 16:11 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 ` Filesystem Corruption (ext2) on Tyan S2462, 2xAMD1900MP, 2.4.17SMP (RH7.2) Ken Brownfield
2002-03-20 1:56 ` Alan Cox
2002-03-20 16:10 ` Vojtech Pavlik [this message]
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=20020320171051.A19871@ucw.cz \
--to=vojtech@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ken@irridia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.