linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: ken@irridia.com (Ken Brownfield)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	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 01:56:23 +0000 (GMT)	[thread overview]
Message-ID: <E16nVKx-0000zB-00@the-village.bc.nu> (raw)
In-Reply-To: <20020319193333.C15811@asooo.flowerfire.com> from "Ken Brownfield" at Mar 19, 2002 07:33:33 PM

> 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

That was a merge error from way back - now fixed (2.4.19pre) 

> 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?

I wish I knew. If I did I'd slap a "no seagate UDMA" check in that driver
pronto.

> As to whether they can reproduce it... I'm not holding my breath for
> them to try.

They tried. They asked a lot of questions and while they failed I'm certain
the actually did try. While we've had some problems with serverworks
(notably no ECC docs which for some enterprise customers is a showstopper)
in general they are very co-operative nowdays, although they do like NDA's
and the like first.

Alan

  reply	other threads:[~2002-03-20  1:40 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 [this message]
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=E16nVKx-0000zB-00@the-village.bc.nu \
    --to=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 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).