Messages in this thread | | | Date | Mon, 08 Dec 2003 03:13:55 -0500 | From | Bob <> | Subject | Re: Catching NForce2 lockup with NMI watchdog - found |
| |
The athcool patch seemed to work as far as patch reported, but there were undef and unused problems on compile so I don't have that in right now. The timer patch is in.
http://www.kernel.org/pub/linux/kernel/people/bart/2.6.0-test11-bart1/broken-out/nforce2-apic.patch
Patch succeeded in giving me the ioapic-edge timer, then lilo append="nmi_watchdog=1" did not work but =2 did get NMI ticks as shown below.
cat /proc/interrupts
CPU0 0: 617651 IO-APIC-edge timer 1: 868 IO-APIC-edge i8042 2: 0 XT-PIC cascade 8: 1 IO-APIC-edge rtc 9: 0 IO-APIC-level acpi 12: 8736 IO-APIC-edge i8042 14: 22 IO-APIC-edge ide0 15: 24 IO-APIC-edge ide1 16: 92853 IO-APIC-level 3ware Storage Controller, yenta, yenta 17: 2793 IO-APIC-level eth0 21: 0 IO-APIC-level NVidia nForce2 NMI: 122 LOC: 617511 ERR: 0 MIS: 0
Does the kernel opt "user HPET timer" relate to io-apic-edge timer? Does the kernel opt "hangcheck timer relate" to nmi_watchdog? Does the kernel opt "ACPI, Processor (c2) (c3 states)" relate to the cmos/bios "processor disconnect" option and athcool patch?
kernel 2.6.0-test11, pre-emptive, apic, lapic, acpi, anticipatory scheduling not deadline scheduling, cpu and fsb clock 1:1 333mhz, amd xp3000+ and high-performance settings(CAS2) other than 1:1 fsb/ram which is slow for the ram, 41C - 48C cpu temp, MSI K7N2 mboard.
My system was stable already(apic, lapic, pre-empt) after a bios update which stopped all irq storm and crashes except "IRQ7 disabled" and "spurious 8259A interrupts" possibly related to the XT-PIC timer running when the other was expected due to apic and lapic and acpi and kernel opt 'use HPET timer" all being on. Turning on onboard ethernet set off the irq7 and 8259a errs so I have not been using onboard eth. USB did not work. I can now test the timer patch with the onboard ethernet, forcedeth driver, usb, and the "nvidia" X driver, which was crashing linux so I had to use "nv". Those items are where my stability frontier is.
-Bob
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |