From: Christopher Swingley <cswingle@iarc.uaf.edu>
To: linux-kernel@vger.kernel.org
Subject: Kernel freeze: 2.6.10 SMP, Promise TX4, software RAID
Date: Thu, 6 Jan 2005 08:26:11 -0900 [thread overview]
Message-ID: <20050106172611.GA22820@iarc.uaf.edu> (raw)
Greetings!
I've recently had the same problem with two different systems while
trying to upgrade the RAID drives. Both systems are dual processor
Pentium machines (one a Dual Xeon, one a dual PIII), and both have new
Promise TX4 cards to support new SATA drives. I'm using the 2.6.10
kernel software RAID-5.
I can create the array, but when I try to put a filesystem on it using
'mkfs.ext3', the system inevitably hangs and 'ataXX: command timeout'
appears on the console before it's completely locked up (no
Ctrl-Alt-SysReq, no caps lock, etc.). The timeouts do not happen on the
same ata interface each time, so I don't think it's the controllers or
the drives.
On one system I finally just replaced the motherboard with a single
processor K7 board and the whole thing has been running well for about a
week now. On the other system (the Xeon box), 'noapic' passed to the
kernel has allowed me to actually put a filesystem on the newly created
RAID. I can't remember if I tried 'noapic' on the first system because
I was trying so many different things.
Now I'm a bit nervous about both systems and I'm wondering what the
appropriate solution is (just use 'noapic', get newer motherboards,
don't use SMP, etc.)? Is there a patch that's reported to fix this, or
are these problems due to insufficient support for SATA controllers on
the older motherboards I've tried?
I'm happy to provide any details, if it might help.
Thanks,
Chris
--
Christopher S. Swingley email: cswingle@iarc.uaf.edu (work)
Intl. Arctic Research Center cswingle@gmail.com (personal)
University of Alaska Fairbanks www.frontier.iarc.uaf.edu/~cswingle/
reply other threads:[~2005-01-06 17:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050106172611.GA22820@iarc.uaf.edu \
--to=cswingle@iarc.uaf.edu \
--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
all inboxes | Powered by JetHome®