Messages in this thread | | | Date | Wed, 14 Apr 2004 00:24:16 -0400 | From | really bensoo_at_soo_dot_com <> | Subject | Re: IO-APIC on nforce2 |
| |
i must add that i've been using your patches for the nForce chipset since they first appeared on this mailing list, and while they've all helped this box to last a bit longer between lockups none of them cured it. Once the IO-APIC code was compiled in and the Athlon idle powersaving turned on it would inevitabley lock up in a day or two.
This incorrect result from the mismatch between your 2.6.3 patches and the current IO-APIC code is the first time this box seems to be free from lockup.
b
On Tue, Apr 13, 2004 at 05:18:24PM -0400, really bensoo_at_soo_dot_com wrote: > My irq0 says XT-PIC. i'm not complaining, box's still > very stable and since the last post i've burned a few > DVDs on it while running the file share client and > playing music. > > cat /proc/interrupts > > CPU0 > 0: 759809583 XT-PIC timer > 1: 382279 IO-APIC-edge i8042 > 2: 0 XT-PIC cascade > 8: 1 IO-APIC-edge rtc > 9: 0 IO-APIC-level acpi > 12: 6386931 IO-APIC-edge i8042 > 14: 2117474 IO-APIC-edge ide0 > 15: 5575006 IO-APIC-edge ide1 > 201: 6425958 IO-APIC-level EMU10K1 > 209: 167929203 IO-APIC-level eth0 > NMI: 0 > LOC: 759718637 > ERR: 0 > MIS: 0 - 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/
| |