public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baldur Norddahl <bbn-linux-kernel@clansoft.dk>
To: Mike Dresser <mdresser_l@windsormachine.com>
Cc: Baldur Norddahl <bbn-linux-kernel@clansoft.dk>,
	linux-kernel@vger.kernel.org
Subject: Re: IDE/raid performance
Date: Wed, 17 Apr 2002 16:00:45 +0200	[thread overview]
Message-ID: <20020417140045.GC27648@dark.x.dtu.dk> (raw)
In-Reply-To: <20020417125838.GA27648@dark.x.dtu.dk> <Pine.LNX.4.33.0204170940310.29775-100000@router.windsormachine.com>

Quoting Mike Dresser (mdresser_l@windsormachine.com):
> On Wed, 17 Apr 2002, Baldur Norddahl wrote:
> 
> > Hi,
> >
> > I have been doing some simple benchmarks on my IDE system. It got 12 disks
> > and a system disk. The 12 disks are organized in two raids like this:
> 
> What is the exact hardware configuration of the system, besides the disk?
> CPU/Motherboard/etc?

Motherboard: Tyan Tiger MPX S2466N
Chipset: AMD 760MPX
CPU: Dual Athlon MP 1800+ 1.53 GHz                                              
Two Promise Technology UltraDMA133 TX2 controllers
Two Promise Technology UltraDMA100 TX2 controllers
Matrox G200 AGP video card.
1 GB registered DDR RAM

> > hdq: dma_intr: bad DMA status (dma_stat=35)
> > hdq: dma_intr: status=0x50 { DriveReady SeekComplete }
> > hdq: dma_intr: bad DMA status (dma_stat=35)
> > hdq: dma_intr: status=0x50 { DriveReady SeekComplete }
> > hdt: dma_intr: bad DMA status (dma_stat=75)
> > hdt: dma_intr: status=0x50 { DriveReady SeekComplete }
> 
> I'd take a look at the cable on hdq and hdt.  Try replacing it, and see
> what happens.

It happens randomly for all disks on the promise controllers. Never for the
system disk on hda (on the motherboard buildin controller). The above was
just a random snippet from dmesg, there is alot more of the same spam.

> Also, with 12 hd's, dual cpu's, etc, what kind of power supply are you
> using?

It is a 350W powersupply. I wanted something bigger, but couldn't get it for
sane prices. I can't rule out that it is overloaded of course. If it is, I
haven't seen any other symptoms, the system is rock stable so far.

Baldur

  reply	other threads:[~2002-04-17 14:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 12:58 IDE/raid performance Baldur Norddahl
2002-04-17 13:43 ` Mike Dresser
2002-04-17 14:00   ` Baldur Norddahl [this message]
2002-04-17 15:15     ` nick
2002-04-17 15:48       ` Alan Cox
2002-04-17 17:27         ` Jeff V. Merkey
2002-04-17 17:47           ` Kent Borg
2002-04-17 17:48             ` nick
2002-04-17 23:26             ` Mike Fedyk
2002-04-18  6:47               ` Andre Hedrick
2002-04-18  7:41               ` Helge Hafting
2002-04-18 21:22                 ` Mike Fedyk
2002-04-17 17:36       ` Baldur Norddahl
2002-04-17 17:41         ` Mike Dresser
2002-04-17 17:46         ` nick
2002-04-17 22:35         ` dean gaudet
2002-04-17 23:52           ` Alan Cox
2002-04-17 20:36       ` Kurt Garloff
2002-04-21 19:01         ` Pavel Machek
2002-04-18 15:51       ` Bill Davidsen
2002-04-18 18:33         ` Mike Galbraith
2002-04-17 15:09 ` Bill Davidsen
2002-04-17 18:38 ` Andre Hedrick
2002-04-17 22:44 ` Lincoln Dale
2002-04-18  0:38   ` Mike Fedyk

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=20020417140045.GC27648@dark.x.dtu.dk \
    --to=bbn-linux-kernel@clansoft.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdresser_l@windsormachine.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