Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered
From: Ian Kumlien (pomac_at_vapor.com)
Date: 12/07/03
- Previous message: Ralf Dreibrodt: "Performance-Problem (CPU) since 2.4.23"
- Maybe in reply to: Ross Dickson: "Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered"
- Next in thread: Jesse Allen: "Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered"
- Reply: Jesse Allen: "Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered"
- Reply: Ross Dickson: "Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: linux-kernel@vger.kernel.org Date: Sun, 07 Dec 2003 20:58:47 +0100
> I have monitored list and know my nforce2 experiences have been
> common.
Hell yeah =)
> When I enabled either apic or io-apic in kern config, lockups came
> hard and fast. Particularly bad under hard disk load. Heaps of lost
> ints on irq7 in apic and ioapic mode. Lockups disappeared when I
> lowered the ide hda udma speed to mode 3 with hdparm so I went looking
> for answers which now follow.
Good job =)
> There are three parts to this email.
> a) apic mods.
> Lockups are due to too fast an apic acknowledge of apic timer int.
> Apic hard locked up the system - no nmi debug available.
> Fixed it by introducing a delay of at least 500ns into
> smp_apic_timer_interrupt() just prior to ack_APIC_irq().
I find this really odd... It works just fine...
As did disabling whats now active ie:
'Halt Disconnect and Stop Grant Disconnect' bit is enabled.
So it seems like these are the two most important factors, at least from
where i stand. Both enabled me to actually use my machine with IO-APIC.
(1, disabling Halt Disconnect and Stop Grand Disconnect bit or 2, Add a
delay on the irq ack.)
Anyone that has any clues?
> b) io-apic mods
> So I have fixed it too (tested on both my epox and albatron MOBOs).
> Firstly I found 8254 connected directly to pin 0 not pin 2 of io-apic.
> I have modified check_timer() in io_apic.c to trial connect pin and
> test for it after the existing test for connection to io-apic.
Good job, i wonder if it could be more generalized and integrated with
the rest of the code (i haven't even checked the rest of the code, but
this seemed separated).
One thing though, I get a lot more NMI's now than with nmi_watchdog=2...
NMI: 85520
LOC: 85477
I usually had a 3 figure number by now... but.. =)
> c) ide driver mods
Cool..
I applied all patches and it survived my grep test so i think it works.
-- Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
-
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/
- application/pgp-signature attachment: This is a digitally signed message part
- Previous message: Ralf Dreibrodt: "Performance-Problem (CPU) since 2.4.23"
- Maybe in reply to: Ross Dickson: "Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered"
- Next in thread: Jesse Allen: "Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered"
- Reply: Jesse Allen: "Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered"
- Reply: Ross Dickson: "Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]