On Tue, Feb 13, 2001 at 09:13:10PM +0100, Maciej W. Rozycki wrote:
> Please test it extensively, as much as you can, before I submit it for
> inclusion. If you ever get "Aieee!!! Remote IRR still set after unlock!"
> message, please report it to me immediately -- it means the code failed.
ok, so far so good.
> There is also an additional debugging/statistics counter provided in
> /proc/cpuinfo that counts interrupts which got delivered with its trigger
> mode mismatched. Check it out to find if you get any misdelivered
> interrupts at all.
currently attacking the box with a flood ping. I used a pristine 2.4.1.
to be sure I didn't leave stuff and applied the patch.
observations -- system doesn't crash; usually I had to use disable focus
processor -- else it fails.
other observations -- approx 6000 ints from the ne2k card/sec.
MIS shows approx 1% that goes wrong with a ping flood.
CPU0 CPU1
0: 35345 36195 IO-APIC-edge timer
1: 1632 1534 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
3: 826 832 IO-APIC-edge serial
4: 4 4 IO-APIC-edge serial
5: 12213 12201 IO-APIC-edge soundblaster
8: 0 1 IO-APIC-edge rtc
14: 3079 2906 IO-APIC-edge ide0
15: 3 3 IO-APIC-edge ide1
18: 69 85 IO-APIC-level BusLogic BT-930
19: 1758280 1758266 IO-APIC-level eth0
NMI: 71480 71480
LOC: 71459 71456
ERR: 3
MIS: 15814
good work !
--
Grobbebol's Home | Don't give in to spammers. -o)
http://www.xs4all.nl/~bengel | Use your real e-mail address /\
Linux 2.2.16 SMP 2x466MHz / 256 MB | on Usenet. _\_v
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
