linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Kumlien <pomac@vapor.com>
To: Craig Bradney <cbradney@zip.com.au>
Cc: ross@datscreative.com.au, linux-kernel@vger.kernel.org,
	recbo@nishanet.com
Subject: Re: Catching NForce2 lockup with NMI watchdog
Date: Wed, 10 Dec 2003 00:13:24 +0100	[thread overview]
Message-ID: <1071011604.1670.16.camel@big.pomac.com> (raw)
In-Reply-To: <1071007478.5293.11.camel@athlonxp.bradney.info>

[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]

On Tue, 2003-12-09 at 23:04, Craig Bradney wrote:
> On Tue, 2003-12-09 at 19:12, Ian Kumlien wrote:
> > Bob wrote:
> > > Using a patch that fixes a number of people's nforce2
> > > lockups while enabling io-apic edge timer, I can now
> > > use nmi_watchdog=2 but not =1
> > 
> > Why regurgitate patches that are outdated, Personally i find int
> > outdated after Ross made his patches available and they DO enable
> > nmi_watchdog=1. (I have seen the old patches mentioned more than once,
> > if something better comes along, please move to that instead.)
> > 
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=107080280512734&w=2
> > 
> > Anyways, Is there anyway to detect if the cpu is "disconnected" or, is
> > there anyway to see when the kernel sends it's halts that triggers the
> > disconnect? (or is it automagic?)
> > 
> > If there was a way to check, then thats all thats needed, all delays can
> > be removed and the code can be more generalized.
> > 
> > (Since doubt that this is apic torment. It's more apic trying to talk to
> > a disconnected cpu... (which both approaches hints at imho))
> 
> Have these patches been submitted for review for inclusion into the main
> kernel?

No, there is no final patch in anyway, there are just dodgy workarounds.
I just deem this better with working nmi_watchdog=1

> I'm still running the old IO-APIC patch (Uptime 3d 20h) and having no
> issues whatsoever.

They fix the same problem.. 

> Are all of the patches at that address you provide necessary? 

nope, but they are all nforce2 related.

> What do the IDE ones claim to fix? I have had no real issue with IDE at
> all.. being able to burn CDs, DVDs, use my ATA133 drive for hdparm,
> greps, compilation, and general use.....

it's just a cleanup afair.

Anyways, I think that if we find someway to detect cpu disconnect, then
we just need that "detection" prior to the apic ack... 
(just a guess though)

-- 
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 --]

  reply	other threads:[~2003-12-09 23:13 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-07 19:58 Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered Ian Kumlien
2003-12-07 20:59 ` Jesse Allen
2003-12-07 20:56   ` Ian Kumlien
2003-12-08  2:07 ` Ross Dickson
2003-12-08  2:23   ` Ian Kumlien
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 [this message]
2003-12-10  1:20       ` NForce2 and AMD, disconnect Ian Kumlien
2003-12-10  6:14       ` Catching NForce2 lockup with NMI watchdog Bob
2003-12-10  7:51         ` Craig Bradney
  -- strict thread matches above, loose matches on Subject: below --
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
2003-12-13  3:56 Ross Dickson
2003-12-15 13:16 ` Maciej W. Rozycki
2003-12-05 22:41 b
2003-12-05 20:56 Allen Martin
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  4:54 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
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

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=1071011604.1670.16.camel@big.pomac.com \
    --to=pomac@vapor.com \
    --cc=cbradney@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=recbo@nishanet.com \
    --cc=ross@datscreative.com.au \
    /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).