From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Steven Timm <timm@fnal.gov>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Serverworks OSB4 in impossible state.
Date: 04 Jun 2002 01:29:08 +0100 [thread overview]
Message-ID: <1023150548.23874.99.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.31.0206031234370.12103-100000@boxer.fnal.gov>
On Mon, 2002-06-03 at 18:40, Steven Timm wrote:
> Serverworks OSB4 in impossible state.
> Disable UDMA or if you are using Seagate then try switching disk types
> on this controller. Please report this event to osb4-bug@ide.cabal.tm
> OSB4: continuing might cause disk corruption.
>
> This is the only one of 60 machines thus configured that has
> had the error thus far.
>
> Two points:
> 1) The E-mail address in that kernel debug message doesn't exist.
> E-mail bounces back from it.
Oops I'll go fix that small detail. It should have been forwarded to me.
> 2) What is causing the hang and are there any hopes to
> fix it in software this time? Last year when I came to the kernel
> list with problems very similar, the consensus was that this
> is actually broken hardware in the OSB4 chipset...but obviously
> it is possible for at least some kernels to run quasi-normally
> on this hardware... what changed between 2.4.9 and 2.4.18 so
> it doesn't anymore?
The code traps out when it sees the I/O complete and it turns out that
the DMA engine flags say the engine is still running. In this state we
kill the box because we know the next I/O will be written 4 bytes skewed
with the last 4 bytes of the previous I/O apparently repeated at the
start.
I took it up with the Serverworks guys at the time, but they were not
able to duplicate the problem and provide advice. Since we could verify
this across an entire rendering farm it was clearly not a weird one off
bug. It also doesn't appear to be a Linux bug (but maybe one day I'll be
proved wrong).
If you drop the drives to MWDMA2 you'll see only slightly lower
performance and solid behaviour
Alan
next prev parent reply other threads:[~2002-06-03 23:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 17:40 Steven Timm
2002-06-04 0:29 ` Alan Cox [this message]
2002-06-03 18:11 ` kwijibo
2002-06-10 15:52 Martin Wilck
2002-06-10 16:41 ` Daniela Engert
2002-06-11 7:22 ` Martin Wilck
2002-06-11 7:45 ` Daniela Engert
2002-06-11 8:37 ` Martin Wilck
2002-06-11 11:25 ` Martin Wilck
2002-06-11 21:27 ` Chris Wedgwood
2002-06-12 7:24 ` Martin Wilck
2002-06-13 11:50 ` Daniela Engert
2002-06-13 11:59 ` Martin Wilck
2002-06-13 12:04 ` Daniela Engert
2002-06-13 18:27 ` rico-linux-kernel
2002-06-12 8:58 ` Alan Cox
2002-06-12 8:47 ` Martin Wilck
2002-06-12 9:14 ` Alan Cox
[not found] <20020613112932.C2B8C10A1B@mail.medav.de>
2002-06-13 12:52 ` Martin Wilck
[not found] <1030002761.32380.27.camel@pluto.unixpac.com.au>
2002-08-22 8:35 ` ServerWorks " Martin Wilck
2002-08-22 8:51 ` Andre Hedrick
2002-08-22 12:02 ` Martin Wilck
2002-08-22 16:45 ` Tomas Szepe
2002-08-22 17:48 ` Andre Hedrick
2002-08-22 17:59 ` Alan Cox
2002-08-22 18:14 ` Tomas Szepe
2002-08-22 17:58 ` Alan Cox
2002-08-22 18:58 ` Martin Wilck
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=1023150548.23874.99.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=timm@fnal.gov \
/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
all inboxes | Powered by JetHome®