From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: andre@linux-ide.org (Andre Hedrick)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
ken@irridia.com (Ken Brownfield),
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
Date: Wed, 20 Mar 2002 01:53:59 +0000 (GMT) [thread overview]
Message-ID: <E16nVId-0000yr-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.10.10203191726290.525-100000@master.linux-ide.org> from "Andre Hedrick" at Mar 19, 2002 05:29:39 PM
> I am in their lab trying to reproduce the error and I have found some docs
> which could help address the error of the 4byte FIFO issue in the engine.
> It looks fixable on paper.
Andre - if you want the info I have from the previous stuff I was involved
in I can strip out customer company info and send it on.
> As for the AMD driver, who knows which version is in that kernel.
2.4.18 has a very old one
2.4.18-ac has the Andre/AMD updated one, but not the further updates.
(eg it turns off SWDMA on more chipsets than it needs to)
Alan
next prev parent reply other threads:[~2002-03-20 1:38 UTC|newest]
Thread overview: 16+ 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 ` Alan Cox [this message]
2002-03-20 2:36 ` Filesystem Corruption (ext2) on Tyan S2462, 2xAMD1900MP, 2.4.17SMP 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
[not found] <no.id>
2002-03-19 20:27 ` Filesystem Corruption (ext2) on Tyan S2462, 2xAMD1900MP, 2.4.17SMP Barry K. Nathan
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=E16nVId-0000yr-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).