public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Torbjörn Olander" <tosse@wlug.westbo.se>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: dma problems with Serverworks CSB5 chipset
Date: Sun, 08 Aug 2004 20:09:17 +0200	[thread overview]
Message-ID: <1091988557.769.18.camel@iota> (raw)
In-Reply-To: <1091554289.3898.5.camel@localhost.localdomain>

I'm having the same problems here with linux 2.6.8-rc2 kernel here with
an Intel SAI2 dual SMP P3 motherboard with Serverworks Serverset III LE
chipset and CSB5 southbridge.

I run one WDC WD400BB-00DEA0 as master on each channel with SW RAID1 for
system. To even get DMA working I had to add
append="ide0=ata66 ide1=ata66"
in my lilo config. The system works fine with low load on the disks, but
if I copy greater amounts of data from a local SW RAID5 array I get the
same DMA timeout error and often it locks up completely.

If i disable DMA with hdparm the system works fine.

/proc/ide/svwks output:
(DMA disabled with hdparm)

                             ServerWorks OSB4/CSB5/CSB6

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



On Tue, 2004-08-03 at 19:31, Alan Cox wrote:
> 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 ?
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-- 
Med vänliga hälsningar / Best regards
Torbjörn Olander
tosse@wlug.westbo.se


  parent reply	other threads:[~2004-08-08 18:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 17:38 dma problems with Serverworks CSB5 chipset Richard Wohlstadter
2004-08-03 18:08 ` Marcelo Tosatti
2004-08-03 17:31   ` Alan Cox
2004-08-03 18:47     ` Rich Wohlstadter
2004-08-08 18:09     ` Torbjörn Olander [this message]
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=1091988557.769.18.camel@iota \
    --to=tosse@wlug.westbo.se \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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