From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nick Urbanik <nicku@vtc.edu.hk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Single P4, many IDE PCI cards == trouble??
Date: 29 Aug 2003 15:38:17 +0100 [thread overview]
Message-ID: <1062167896.27561.4.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <3F4F5C9A.5BAA1542@vtc.edu.hk>
On Gwe, 2003-08-29 at 15:00, Nick Urbanik wrote:
> Is there _anyone_ who is using a number of ATA133 IDE disks (>=6), each on
> its own IDE channel, on a number of PCI IDE cards, and doing so
The most I know of is 8, and that was one of the people who found the
shared IRQ/IDE race cases that 2.4.21 or so fixed.
> > A freeze in an IRQ handler would cause that kind of thing, turning on
> > the NMI watchdog might get you a trace in such a failure case - and
> > that would help.
>
> If the NMI count is positive in /proc/interrupts, and I have nmi_watchdog=2
> in /proc/cmdline, does that mean that the NMI watchdog is turned on? If
nmi watchdog trigger failure would indicate hardware problems in just
about any situation I can imagine. The nmi is just that -not maskable-
by software.
next prev parent reply other threads:[~2003-08-29 14:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 0:49 Single P4, many IDE PCI cards == trouble?? Nick Urbanik
2003-08-29 9:50 ` Alan Cox
2003-08-29 14:00 ` Nick Urbanik
2003-08-29 14:22 ` lk
2003-08-29 14:38 ` Alan Cox [this message]
2003-08-29 21:14 ` Erik Andersen
2003-08-30 3:46 ` Nick Urbanik
2003-09-08 6:13 ` Mike Fedyk
2003-09-08 17:20 ` Joel Jaeggli
2003-08-29 15:13 ` Valdis.Kletnieks
2003-08-31 12:43 ` Hans-Peter Jansen
2003-08-31 15:46 ` joe briggs
2003-08-31 23:41 ` Nick Urbanik
2003-09-01 6:01 ` many IDE PCI cards "spurious 8259a" irq15(SMBus nforce2) Resident Boxholder
2003-09-01 7:51 ` Alan Cox
2003-09-01 10:14 ` IDE PCI cards IOAPIC " Resident Boxholder
2003-09-06 12:44 ` Single P4, many IDE PCI cards == trouble?? Steve Bromwich
2003-10-22 16:36 Alex Finch
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=1062167896.27561.4.camel@dhcp23.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nicku@vtc.edu.hk \
/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;
as well as URLs for NNTP newsgroup(s).