From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Andreas Steinmetz <ast@domdv.de>, piotr@member.fsf.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Promise PDC20269 (Ultra133 TX2) + Software RAID
Date: Wed, 4 Feb 2004 23:06:54 +0100 [thread overview]
Message-ID: <200402042306.54046.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <4021628D.5030805@domdv.de>
On Wednesday 04 of February 2004 22:22, Andreas Steinmetz wrote:
> Pedro Larroy wrote:
> > On Tue, Feb 03, 2004 at 02:08:31PM +1030, Ryan Verner wrote:
> >>And the machine is randomly locking up, and of course, on reboot, the
> >>raid array is rebuilt. Ouch. Any clues as to why? I'm sure the hard
> >>drive hasn't failed as it's brand new; I suspect a chipset
> >>compatibility problem or something.
> >>
> >>R
> >
> > I have similar issues with 20269. I have two cards on one box doing sw
> > raid5 on 6 ide drives. It only runs stably with 2.4.19
> > It has been many months since I assembled that box, and I've tried
> > kernels from 2.4.20-ac, 2.5.x, 2.6.2 and all hang after some time
> > running.
> >
> > I remember that pdcs also hanged a dual processor box.
>
> In my case (see my mail to lkml today) I do suspect concurrent disk
> access and IO-APIC to be the culprit. If you're using an IO-APIC try
> booting with either "noapic" or "hdx=serialize" where hdx is one of the
> disks of your controller card.
Try "noapic" first, "hdx=serialize" will kill you RAID performance.
---bart
next prev parent reply other threads:[~2004-02-04 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 3:38 Ryan Verner
2004-02-03 6:12 ` Ryan Verner
2004-02-03 8:47 ` Pasi Kärkkäinen
2004-02-03 9:07 ` Gunnlaugur Thor Briem
2004-02-04 20:46 ` Pedro Larroy
2004-02-04 21:22 ` Andreas Steinmetz
2004-02-04 22:06 ` Bartlomiej Zolnierkiewicz [this message]
2004-02-04 22:41 ` Pedro Larroy
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=200402042306.54046.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=piotr@member.fsf.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
all inboxes | Powered by JetHome®