From: Andrew Morton <andrewm@uow.edu.au>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ingo Molnar <mingo@chiara.elte.hu>,
Manfred Spraul <manfred@colorfullife.com>,
Frank de Lange <frank@unternet.org>,
Martin Josefsson <gandalf@wlug.westbo.se>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.4.1, 2.4.2-pre3: APIC lockups
Date: Wed, 14 Feb 2001 22:38:25 +1100 [thread overview]
Message-ID: <3A8A6E31.ED24B54F@uow.edu.au> (raw)
In-Reply-To: <Pine.GSO.3.96.1010213203553.1931A-100000@delta.ds2.pg.gda.pl>
"Maciej W. Rozycki" wrote:
>
> Hi,
>
> After performing various tests I came to the following workaround for
> APIC lockups which people observe under IRQ load, mostly for networking
> stuff.
Works fine on the dual-PII. No "Aieee!!!" messages at all.
After sending a few gigs across the ethernet, running
irq-whacker:
mnm:/usr/src/cptimer> cat /proc/interrupts
CPU0 CPU1
0: 77613 61869 IO-APIC-edge timer
1: 253 258 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
8: 0 1 IO-APIC-edge rtc
9: 0 0 XT-PIC acpi
12: 0 0 IO-APIC-edge PS/2 Mouse
17: 5104855 3919759 IO-APIC-level eth0
18: 2334 2313 IO-APIC-level ide2
NMI: 139418 139418
LOC: 139403 139402
ERR: 221
MIS: 5299867
And without irq-whacker:
mnm:/home/morton> cat /proc/interrupts
CPU0 CPU1
0: 55384 70899 IO-APIC-edge timer
1: 2 3 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
8: 0 1 IO-APIC-edge rtc
9: 0 0 XT-PIC acpi
12: 0 0 IO-APIC-edge PS/2 Mouse
17: 2554705 2554064 IO-APIC-level eth0
18: 1814 1812 IO-APIC-level ide2
NMI: 126220 126220
LOC: 126202 126201
ERR: 35
MIS: 0
Tell me, please: what tradeoffs are involved in this patch?
Obviously it works around a pretty fatal problem, but
what are we giving away?
Oh: and thanks :)
-
next prev parent reply other threads:[~2001-02-14 11:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 20:13 Maciej W. Rozycki
2001-02-13 22:18 ` Manfred Spraul
2001-02-13 23:20 ` Frank de Lange
2001-02-14 11:38 ` Andrew Morton [this message]
2001-02-14 12:29 ` Maciej W. Rozycki
2001-02-14 17:30 ` Roeland Th. Jansen
2001-02-14 17:41 ` Roeland Th. Jansen
2001-02-14 17:47 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A8A6E31.ED24B54F@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=frank@unternet.org \
--cc=gandalf@wlug.westbo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=manfred@colorfullife.com \
--cc=mingo@chiara.elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®