Re: IO-APIC on nforce2 [PATCH]

[Ross Dickson <ross@datscreative.com.au>]

On Thursday 15 April 2004 07:01, Christian Kröner wrote:
> > Just would like to add that if we cannot get Maciej's 8259 ack patch
> > back into the distro then we need an if statement in the check_timer()
> > to turn off timer_ack for nforce2 or Christian might get his hi-load back
> > and certainly nmi_debug=1 won't work.
> >
> > e.g. for 2.4.26-rc2 io_apic.c line 1613 or 2.6.5 line 2180
> >       if (pin1 != -1) {
> >               /*
> >                * Ok, does IRQ0 through the IOAPIC work?
> >                */
> > +             if(acpi_skip_timer_override)
> > +                     timer_ack=0;
> >               unmask_IO_APIC_irq(0);
> >
> 
> Also on mainline 2.6.5 this if-statement doesn't seem to be necessary. Len's 
> patch worked on this kernel as well, setting the timer interrupt to 
> IO-APIC-edge and there is no strange hi-load anymore too.
> 

Good that your hi-load is fixed just by routing the timer through io-apic.

Could you try the "nmi_watchdog=1" kernel arg please.

You should get a message in your boot log as to whether it works
also cat /proc/interrupts to see if it stops. 
Wouldn't hurt to try "nmi_watchdog=2" either.
I had a situation where "nmi_watchdog=2" tested ok in boot log
but halted after 23 interrupts.


> thanks, christian.
> 
> 
>