mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rich Wohlstadter" <rwohlsta@watson.wustl.edu>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Marcelo Tosatti" <marcelo.tosatti@cyclades.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Bartlomiej Zolnierkiewicz" <b.zolnierkiewicz@elka.pw.edu.pl>
Subject: Re: dma problems with Serverworks CSB5 chipset
Date: Tue, 3 Aug 2004 13:47:06 -0500 (CDT)	[thread overview]
Message-ID: <54073.10.0.1.211.1091558826.squirrel@10.0.1.211> (raw)
In-Reply-To: <1091554289.3898.5.camel@localhost.localdomain>

> On Maw, 2004-08-03 at 19:08, Marcelo Tosatti wrote:
>> ServerWorks OSB4/5 chipsets are known to not work reliably with the
>> Linux
>> IDE code. AFAIK its a hardware problem which we dont correctly work
>> around.
>>
>> Have you tried disabling DMA?
>>
>> Bart and Alan are IDE experts, they can probably give you more useful
>> information.
>
> CSB5 is reliable, rock solidly so in my experience. OSB4 was the older
> interface with problems. Are these systems SMP, what disks are you using
> and in what IDE mode ?
>

Yep, they are SMP(IBM blades with 2 Xeon 2.4Ghz).  The blades use 1
little 40g laptop drive( TOSHIBA MK4019GAXB ).  The drive is running UDMA
mode 4.  Here is the output of /proc/ide/svwks:

                             ServerWorks OSB4/CSB5/CSB6

                            ServerWorks CSB5 Chipset (rev 93)
------------------------------- General Status
---------------------------------
--------------- Primary Channel ---------------- Secondary Channel
-------------
                 enabled                          enabled
--------------- drive0 --------- drive1 -------- drive0 ---------- drive1
------
DMA enabled:    yes              yes             no                no
UDMA enabled:   yes              yes             no                no
UDMA enabled:   4                4               0                 0
DMA enabled:    2                2               2                 2
PIO  enabled:   4                4               ?                 ?

Let me know if you need any other specifics and thanks in advance for any
advice.

Rich


  reply	other threads:[~2004-08-03 18:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 17:38 Richard Wohlstadter
2004-08-03 18:08 ` Marcelo Tosatti
2004-08-03 17:31   ` Alan Cox
2004-08-03 18:47     ` Rich Wohlstadter [this message]
2004-08-08 18:09     ` Torbjörn Olander
2004-08-23 18:59       ` Torbjörn Olander

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=54073.10.0.1.211.1091558826.squirrel@10.0.1.211 \
    --to=rwohlsta@watson.wustl.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /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®