From: Craig Bradney <cbradney@zip.com.au>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Josh McKinney <forming@charter.net>, linux-kernel@vger.kernel.org
Subject: Re: Catching NForce2 lockup with NMI watchdog
Date: Fri, 05 Dec 2003 18:05:01 +0100 [thread overview]
Message-ID: <1070643901.3962.10.camel@athlonxp.bradney.info> (raw)
In-Reply-To: <1070633973.4100.23.camel@athlonxp.bradney.info>
Having just had another hang.. I tried booting with nmi-watchdog=1 and
then with 2.
I am currently running from the boot with 2 selected.
In my current dmesg I have these which dont normally appear and didnt
appear in the boot with 1 set.
Any ideas?
hda: IRQ probe failed (0xfffffcfa)
hdb: IRQ probe failed (0xfffffcfa)
hdb: IRQ probe failed (0xfffffcfa)
Craig
On Fri, 2003-12-05 at 15:19, Craig Bradney wrote:
> I'm getting those in dmesg too...
>
> ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> ...trying to set up timer (IRQ0) through the 8259A ... failed.
> ...trying to set up timer as Virtual Wire IRQ... failed.
> ...trying to set up timer as ExtINT IRQ... works.
>
>
> Do you really think this could be the problem?
>
> If so, any ideas why I am relatively lucky to not have the crashes
> people are having? 5.5 days, then 5 hours, and now Im up to 17 hours...
> with a decent amount of use combined with idle time.
>
> Craig
>
>
> On Fri, 2003-12-05 at 13:14, Mikael Pettersson wrote:
> > Josh McKinney writes:
> > > On approximately Fri, Dec 05, 2003 at 08:40:58AM +0100, Mikael Pettersson wrote:
> > > > Jesse Allen writes:
> > > > > Hi,
> > > > >
> > > > > I have a NForce2 board and can easily reproduce a lockup with grep on an IDE
> > > > > hard disk at UDMA 100. The lockup occurs when both Local APIC + IO-APIC are
> > > > > enabled. It was suggested to me to use NMI watchdog to catch it. However, the
> > > > > NMI watchdog doesn't seem to work.
> > > > >
> > > > > When I set the kernel parameter "nmi_watchdog=1" I get this message in
> > > > > /var/log/syslog:
> > > > > Dec 4 20:10:30 tesore kernel: ..MP-BIOS bug: 8254 timer not connected to
> > > > > IO-APIC
> > > > > Dec 4 20:10:30 tesore kernel: timer doesn't work through the IO-APIC -
> > > > > disabling NMI Watchdog!
> > > > >
> > > > > "nmi_watchdog=2" seems to work at first, In /var/log/messages:
> > > > > Dec 4 20:13:11 tesore kernel: testing NMI watchdog ... OK.
> > > > > but it still locks up.
> > > >
> > > > The NMI watchdog can only handle software lockups, since it relies on
> > > > the CPU, and for nmi_watchdog=1 the I/O-APIC + bus, still running.
> > > > Hardware lockups result in, well, hardware lockups :-(
> > >
> > > So does this confirm that the lockups with nforce2 chipsets and apic
> > > is actually a hardware problem after all?
> >
> > Confirm with very high probability. There may be quirks in nVidia's
> > chipset that we (unlike their Windoze drivers) don't know about.
> >
> > Ask nVidia for detailed chipset documentation. Then maybe we can fix this.
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-12-05 17:05 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 4:54 Catching NForce2 lockup with NMI watchdog Jesse Allen
2003-12-05 7:40 ` Mikael Pettersson
2003-12-05 8:33 ` Josh McKinney
2003-12-05 12:14 ` Mikael Pettersson
2003-12-05 14:19 ` Craig Bradney
2003-12-05 17:05 ` Craig Bradney [this message]
2003-12-05 18:11 ` Josh McKinney
2003-12-05 8:58 ` Mike Fedyk
2003-12-05 12:06 ` Mikael Pettersson
2003-12-08 2:20 ` Bob
2003-12-09 14:21 ` Maciej W. Rozycki
2003-12-09 16:35 ` Bob
2003-12-10 13:41 ` Maciej W. Rozycki
2003-12-12 16:01 ` bill davidsen
2003-12-12 16:47 ` Maciej W. Rozycki
2003-12-12 16:57 ` Richard B. Johnson
2003-12-12 17:21 ` Maciej W. Rozycki
2003-12-13 5:16 ` Bill Davidsen
2003-12-15 13:23 ` Maciej W. Rozycki
2003-12-12 22:27 ` George Anzinger
2003-12-15 13:13 ` Maciej W. Rozycki
2003-12-15 21:42 ` George Anzinger
2003-12-16 13:37 ` Maciej W. Rozycki
2003-12-16 13:57 ` Richard B. Johnson
2003-12-16 15:47 ` Maciej W. Rozycki
2003-12-16 16:44 ` Richard B. Johnson
2003-12-16 16:50 ` Maciej W. Rozycki
2003-12-16 17:26 ` George Anzinger
2003-12-16 20:54 ` Maciej W. Rozycki
2003-12-16 21:53 ` George Anzinger
2003-12-17 14:03 ` Maciej W. Rozycki
2003-12-05 19:11 Allen Martin
2003-12-05 20:18 ` cheuche+lkml
2003-12-05 20:34 ` Prakash K. Cheemplavam
2003-12-05 21:02 ` Mike Fedyk
2003-12-05 20:55 ` Jesse Allen
2003-12-06 3:20 ` Jesse Allen
2003-12-05 20:36 ` Jesse Allen
2003-12-05 22:55 ` Mike Fedyk
2003-12-05 23:11 ` Craig Bradney
2003-12-05 20:56 Allen Martin
2003-12-05 22:41 b
2003-12-07 19:58 Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered Ian Kumlien
2003-12-08 2:07 ` Ross Dickson
2003-12-09 18:12 ` Catching NForce2 lockup with NMI watchdog Ian Kumlien
2003-12-09 22:04 ` Craig Bradney
2003-12-09 23:13 ` Ian Kumlien
2003-12-10 6:14 ` Bob
2003-12-10 7:51 ` Craig Bradney
2003-12-13 3:56 Ross Dickson
2003-12-15 13:16 ` Maciej W. Rozycki
2003-12-17 18:14 Ross Dickson
2003-12-17 21:41 ` George Anzinger
2003-12-17 21:48 ` George Anzinger
2003-12-18 1:30 ` Ross Dickson
2003-12-18 14:32 ` Maciej W. Rozycki
2003-12-19 4:17 ` Ross Dickson
2003-12-19 15:35 ` Maciej W. Rozycki
2003-12-18 14:04 ` Maciej W. Rozycki
2003-12-18 14:22 ` Craig Bradney
2003-12-19 5:38 ` Ross Dickson
2003-12-19 10:36 ` Craig Bradney
2003-12-19 4:06 ` Ross Dickson
2003-12-19 15:33 ` Maciej W. Rozycki
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=1070643901.3962.10.camel@athlonxp.bradney.info \
--to=cbradney@zip.com.au \
--cc=forming@charter.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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).