All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: timm@fnal.gov (Steven Timm)
Cc: linux-kernel@vger.kernel.org
Subject: Re: DMA problem (?) w/2.4.6-xfs and ServerWorks OSB4 Chipset
Date: Thu, 27 Sep 2001 23:55:33 +0100 (BST)	[thread overview]
Message-ID: <E15mk45-0005Li-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.31.0109271622520.28262-100000@snowball.fnal.gov> from "Steven Timm" at Sep 27, 2001 04:34:31 PM

> 2.4.7-ac2 patch level and not having any lock-ups with ultraDMA.
> My question--there was a new file "serverworks.c" inserted in the
> 2.4.6 ac patches.  Does anyone know if that made it into the kernel
> and supposedly fixed the problem?  (My guess is that it has *not*

Short answer is "it should"

Long answer "I have been chasing a specific problem with OSB4, seagate
drives and UDMA corruption. We can reliably reproduce it and see it on one
set of machines. Serverworks cannot reproduce it elsewhere"

So unless your box when running current -ac starts spewing messages about
DMA completions seeming broken - it should work. I only mention this
because you write:

> We have seen quite a difference on systems that are otherwise
> the same (Supermicro 370DLE w/serverworks OSB4 LE chipset) by swapping
> different models of hard disk drives.  With some types of drive
> (Seagate) we
> observe massive corruption of the file system but nothing reported
> in /var/log/messages or on the console.  Currently we see hda
> timeouts (but only on about 10 systems over the course of 2 months)
> which hang the machine but after a reboot things are fine (Western
> Digital).

I would thus be very interested if the current -ac "hardware just did
something impossibly stupid" trap is hit.

Alan

  reply	other threads:[~2001-09-27 22:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-27 21:34 DMA problem (?) w/2.4.6-xfs and ServerWorks OSB4 Chipset Steven Timm
2001-09-27 22:55 ` Alan Cox [this message]
2001-09-28 14:53   ` Steven Timm
2001-09-28 15:04     ` Alan Cox
2001-10-04 15:20   ` Benjamin S. Scarlet
  -- strict thread matches above, loose matches on Subject: below --
2001-09-30 20:37 Marvin Justice
2001-09-30 20:50 ` Alan Cox
2001-09-30 21:08   ` Marvin Justice
2001-09-30 21:45     ` Alan Cox
2001-10-01 15:04   ` Steven Timm
2001-10-01 15:10     ` Mark Hahn
2001-10-01 15:23       ` Steven Timm
2001-10-01 14:59 ` Steven Timm
2001-10-12 20:31 DMA problem (?) w/2.4.6-xfs and Serverworks " Steven Timm
2001-10-12 21:12 ` Alan Cox

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=E15mk45-0005Li-00@the-village.bc.nu \
    --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 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.