All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob <recbo@nishanet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Catching NForce2 lockup with NMI watchdog - found?
Date: Sun, 07 Dec 2003 22:12:59 -0500	[thread overview]
Message-ID: <3FD3EC3B.6080803@nishanet.com> (raw)
In-Reply-To: <1070672114.2759.8.camel@big.pomac.com>

Ian Kumlien wrote:

>           CPU0
>  0:     267486    IO-APIC-edge  timer
>  1:       9654    IO-APIC-edge  keyboard
>  2:          0          XT-PIC  cascade
>  8:          1    IO-APIC-edge  rtc
>  9:          0   IO-APIC-level  acpi
> 14:      28252    IO-APIC-edge  ide0
> 15:        103    IO-APIC-edge  ide1
> 16:     251712   IO-APIC-level  eth0
> 17:      90632   IO-APIC-level  EMU10K1
> 19:     415529   IO-APIC-level  nvidia
> 20:          0   IO-APIC-level  usb-ohci
> 21:        153   IO-APIC-level  ehci_hcd
> 22:      58257   IO-APIC-level  usb-ohci
>NMI:        479
>LOC:     265875
>ERR:          0
>MIS:          0
>
note I have only PIC timer....

           CPU0      
  0:  244393560          XT-PIC  timer
  1:      31963    IO-APIC-edge  i8042
  2:          0          XT-PIC  cascade
  8:          1    IO-APIC-edge  rtc
  9:          0   IO-APIC-level  acpi
 12:     251884    IO-APIC-edge  i8042
 14:         22    IO-APIC-edge  ide0
 15:         24    IO-APIC-edge  ide1
 16:    4290216   IO-APIC-level  3ware Storage Controller, yenta, yenta
 17:    5929405   IO-APIC-level  eth0
 21:          0   IO-APIC-level  NVidia nForce2
NMI:          0
LOC:  244378698
ERR:          0
MIS:          6


  parent reply	other threads:[~2003-12-08  2:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-06  0:55 Catching NForce2 lockup with NMI watchdog - found? 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 [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  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-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=3FD3EC3B.6080803@nishanet.com \
    --to=recbo@nishanet.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.