public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Grebinskiy <v_lkm@list.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: Catching NForce2 lockup with NMI watchdog - found
Date: Sat, 06 Dec 2003 10:35:42 -0500	[thread overview]
Message-ID: <3FD1F74E.3010105@list.ru> (raw)
In-Reply-To: <200312061411.37795.bzolnier@elka.pw.edu.pl>

I hope you nailed the problem! I applied the "timer APIC-IO-edge" change 
and "athcool off" patch and the box seemed to be working with APIC/LAPIC 
(for the first time) !!! The board is the Leadtek K7nCR18G-Pro, BIOS 
9/30/2003, kernel 2.6.0-test11 and Debian/Sid (all debug turned on, 
preempt off).

The box used to lock up in seconds when running "md5sum bigfile" unless 
booted with "noapic nolapic". Now it survived parallel read from two 
drives + "ping -f router" + glxgears (with nvidia video driver). I'll 
keep testing it for a while.

Vladimir

lspci:
00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) 
(rev a2)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev a2)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev a2)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev a2)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev a2)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev a2)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3)
00:05.0 Multimedia audio controller: nVidia Corporation nForce 
MultiMedia audio [Via VT82C686B] (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 
Audio Controler (MCP) (rev a1)
00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:0d.0 FireWire (IEEE 1394): nVidia Corporation nForce2 FireWire (IEEE 
1394) Controller (rev a3)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev a2)
01:09.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] 
(rev 6c)
03:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 
- nForce GPU] (rev a3)

Interrupts:


*         CPU0
  0:    2865299    IO-APIC-edge  timer
  1:       3017    IO-APIC-edge  i8042
  2:          0          XT-PIC  cascade
  8:          4    IO-APIC-edge  rtc
  9:          0   IO-APIC-level  acpi
 12:      13046    IO-APIC-edge  i8042
 14:     223268    IO-APIC-edge  ide0
 15:         49    IO-APIC-edge  ide1
 16:     616405   IO-APIC-level  nvidia
 17:    2333041   IO-APIC-level  eth0
 20:      22450   IO-APIC-level  ohci_hcd
 21:       2621   IO-APIC-level  NVidia nForce2
 22:          0   IO-APIC-level  ohci_hcd
NMI:          0
LOC:    2864269
ERR:          0
MIS:          0




  parent reply	other threads:[~2003-12-06 15:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
2003-12-06  8:18   ` Catching NForce2 lockup with NMI watchdog - found cheuche+lkml
2003-12-06 11:22     ` Julien Oster
2003-12-08  3:34       ` Bob
2003-12-08  8:13         ` Bob
2003-12-06 12:24     ` Prakash K. Cheemplavam
2003-12-06 13:11       ` [PATCH] " Bartlomiej Zolnierkiewicz
2003-12-06 15:10         ` Prakash K. Cheemplavam
2003-12-06 15:37           ` Craig Bradney
2003-12-06 15:35         ` Vladimir Grebinskiy [this message]
2003-12-08  3:25     ` Bob
2003-12-08  3:18       ` Bartlomiej Zolnierkiewicz

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=3FD1F74E.3010105@list.ru \
    --to=v_lkm@list.ru \
    --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