From: Ian Kumlien <pomac@vapor.com>
To: Craig Bradney <cbradney@zip.com.au>
Cc: linux-kernel@vger.kernel.org, AMartin@nvidia.com
Subject: Re: Catching NForce2 lockup with NMI watchdog - found?
Date: Sat, 06 Dec 2003 16:58:15 +0100 [thread overview]
Message-ID: <1070726295.1995.40.camel@big.pomac.com> (raw)
In-Reply-To: <1070724815.13016.16.camel@athlonxp.bradney.info>
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
On Sat, 2003-12-06 at 16:33, Craig Bradney wrote:
> On Sat, 2003-12-06 at 15:42, Ian Kumlien wrote:
> Its a pity that as Bart said, those numbers dont reflect any sort of
> revision as that might lead to a conclusion about why it happens on some
> and not others.
Yeah i saw that aswell...
> > Btw, i have UDMA100 disks.. 2 disks on primary and 2 cdroms on
> > secondary... I dunno if this could make any difference..
>
> 1 ata133 primary master and dvdrw and cdrom on secondary here.
I'm just wondering if it could be a relation to the disk aswell or so..
> > Good luck =)
>
> You too :)
Heh, thanks =)
Now, about this ACPI powersave thing, wouldn't that be enabled in
windows aswell? So wouldn't this workaround be something that $other_os
doesn't have to do.
(In general i have always had to hack windows into not crashing when
linux worked and doing it the other way around without a real fix dosn't
sound that nice in my ears.. =P)
It would be interesting to hear from nvidia about nmi_watchdog... Since
nmi_watchdog with the 'not-done-correctly' APIC patch claims that nmi is
stalled/locked/doesn't work... If nvidia states that this *should* work,
then we have something to go on.
Also, if Allen Martin (nvidia) could go trough the proc/interrupts and
tell us if something is wrong, like the XT-PIC on timer. Or just give us
a correct listing, since noone had io-apic-edge on timer before afair.
--
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-06 15:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-06 2:08 Catching NForce2 lockup with NMI watchdog - found? Ian Kumlien
2003-12-06 13:36 ` Craig Bradney
2003-12-06 13:47 ` Bartlomiej Zolnierkiewicz
2003-12-06 14:42 ` Ian Kumlien
2003-12-06 15:33 ` Craig Bradney
2003-12-06 15:58 ` Ian Kumlien [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-09 22:57 merged in bk5 " b
2003-12-10 4:48 ` Bob
2003-12-08 3:21 Ross Dickson
2003-12-08 11:36 ` Craig Bradney
2003-12-08 13:34 ` Ross Dickson
2003-12-08 17:40 ` Bob
2003-12-06 19:33 Ian Kumlien
2003-12-07 0:20 ` Craig Bradney
2003-12-07 0:29 ` Ian Kumlien
2003-12-07 10:32 ` Craig Bradney
2003-12-07 14:54 ` Ian Kumlien
2003-12-06 1:58 Ian Kumlien
2003-12-06 0:55 Ian Kumlien
2003-12-06 1:52 ` Craig Bradney
2003-12-06 4:00 ` Mike Fedyk
2003-12-06 8:23 ` Josh McKinney
2003-12-08 3:12 ` Bob
2003-12-05 20:56 Catching NForce2 lockup with NMI watchdog Allen Martin
2003-12-05 23:49 ` Catching NForce2 lockup with NMI watchdog - found? Prakash K. Cheemplavam
2003-12-05 23:55 ` Prakash K. Cheemplavam
2003-12-06 0:15 ` Craig Bradney
2003-12-06 0:21 ` Prakash K. Cheemplavam
2003-12-06 0:37 ` Craig Bradney
2003-12-08 3:08 ` Bob
2003-12-08 3:06 ` Bartlomiej Zolnierkiewicz
2003-12-08 3:03 ` Bob
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=1070726295.1995.40.camel@big.pomac.com \
--to=pomac@vapor.com \
--cc=AMartin@nvidia.com \
--cc=cbradney@zip.com.au \
--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;
as well as URLs for NNTP newsgroup(s).