From: Craig Bradney <cbradney@zip.com.au>
To: Ian Kumlien <pomac@vapor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Catching NForce2 lockup with NMI watchdog - found?
Date: Sun, 07 Dec 2003 11:32:49 +0100 [thread overview]
Message-ID: <1070793169.2079.10.camel@athlonxp.bradney.info> (raw)
In-Reply-To: <1070756987.1987.7.camel@big.pomac.com>
On Sun, 2003-12-07 at 01:29, Ian Kumlien wrote:
> On Sun, 2003-12-07 at 01:20, Craig Bradney wrote:
> > On Sat, 2003-12-06 at 20:33, Ian Kumlien wrote:
> > > Hi, i'm now running this patch and it survived my grep in /usr/src.
> > >
> > > It's mainly a correction of the apic patch and the ACPI halt disconnect
> > > patch that was originally done for 2.6...
> >
> > Correction? how so? code looks the same, although the line numbers are
> > completely different for mpparse.c and at that location there is
> > different code. (Havent checked the disconnect)
>
> this is for 2.4.23 =)
duh.. ok :)
> > Or do u just mean combination of the two patches?
>
> Combination + for 2.4.23
>
> > > I'll get back to you about uptime, but i think this is it...
> >
> > Why do you think the disconnect is also related? (given some are just
> > running the APIC patch and having (less/)no issues?
>
> Since i had issues with just the apic patch, as stated in my mail.
oic.. sorry.. must have missed that.
>
> > > Although i would prefer a not so workaroundish approach =)
> >
> > 23 hrs now..
>
> I'm at 5:06 and thats a record for it running with apic.
1d 9h here now..
I remembered I also dont have preempt still, but I am happy with it if
it stays like this. The next time I need to reboot (or get a hang), I'll
recompile with preempt it and try again.
Craig
next prev parent reply other threads:[~2003-12-07 10:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-06 19:33 Catching NForce2 lockup with NMI watchdog - found? Ian Kumlien
2003-12-07 0:20 ` Craig Bradney
2003-12-07 0:29 ` Ian Kumlien
2003-12-07 10:32 ` Craig Bradney [this message]
2003-12-07 14:54 ` Ian Kumlien
-- 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 2:08 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
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=1070793169.2079.10.camel@athlonxp.bradney.info \
--to=cbradney@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pomac@vapor.com \
/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).