From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: linux-kernel@vger.kernel.org
Subject: IDE Promise hang on 2.4.19-pre2.
Date: Tue, 25 Jun 2002 14:51:39 +0200 (MEST) [thread overview]
Message-ID: <200206251251.OAA11370@cave.bitwizard.nl> (raw)
Hi,
We just test-installed a Promise controller in a machine, and tried to
get it probed. Turns out that crashed the machine.
/root# lspci -v -s 00:09.0
00:09.0 Unknown mass storage controller: Promise Technology, Inc. 20268 (rev 02) (prog-if 85)
Subsystem: Promise Technology, Inc. 20268
Flags: bus master, 66Mhz, slow devsel, latency 32, IRQ 9
I/O ports at e000 [size=8]
I/O ports at d800 [size=4]
I/O ports at d400 [size=8]
I/O ports at d000 [size=4]
I/O ports at c800 [size=16]
Memory at fb000000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at <unassigned> [disabled] [size=16K]
Capabilities: [60] Power Management version 1
We then went into the bios (install video card, grab a monitor,
etcetc.) and told it to assign interrupts automatically, rather than
IRQ9 for all slots....
So then the VGA card, ethernet card, scsi card all got assigned
different IRQs than 9.
Now when we insmod the IDE, the machine doesn't crash.
Hypothesis: The Promise driver enables IRQs on the chip first, then
grabs its IRQ. This leads to an interrupt storm, provided that any
other device is using that IRQ.
This is on our testing machine:
Pentium PRO 150.
96Mb RAM.
Linux-2.4.19-pre2.
We've got our system running. We only have the hardware for a day, so
we're running our tests, and won't have time to test stuff (like
upgrading the kernel. Sorry)
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
reply other threads:[~2002-06-25 12:52 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=200206251251.OAA11370@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--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®