From: Manfred Spraul <manfred@colorfullife.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ingo Molnar <mingo@chiara.elte.hu>,
Andrew Morton <andrewm@uow.edu.au>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.4.0, 2.4.0-ac12: APIC lock-ups
Date: Mon, 29 Jan 2001 21:40:19 +0100 [thread overview]
Message-ID: <3A75D533.7F3F4019@colorfullife.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1010129182851.29329A-100000@delta.ds2.pg.gda.pl>
"Maciej W. Rozycki" wrote:
>
> I'll implement an 82489DX update in a few days, but for now I'd like
> everyone interested to test the following patch as much as possible. It
> applies to 2.4.0, 2.4.0-ac12 and 2.4.1-pre11 cleanly.
>
I'm not totally convinced that this fixes all problems:
No lockup, and but a slightly increased packet loss: every few minutes a
block of 5-10 packets is lost. Cpu load is low (~30%), I'm running 3
concurrent bw_tcp, the io apic computer is the 'server'.
IIRC my original patch caused a far higher packet loss, perhaps because
it's slower? (you wrote something about 2 r/w accesses).
Are you sure that this really fixed the bug?
Remember that switching the 'trigger mode' bit will revive the io apic.
It's possible that
* the io apic still locks up.
* but now {en,dis}able_irq() switches the 'trigger mode' bit, and thus
resets the io apic after a few msec --> a few lost packets.
It's far better than before, but I assume the bug is hidden, not fixed.
I'll make additional tests.
Send the patch to Linus - it makes ne2k cards usable with 2.4+io apic.
--
Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-29 20:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 18:46 [patch] 2.4.0, 2.4.0-ac12: APIC lock-ups Maciej W. Rozycki
2001-01-29 20:40 ` Manfred Spraul [this message]
2001-01-30 11:20 ` Maciej W. Rozycki
2001-02-01 0:58 ` Andrew Morton
2001-02-02 12:08 ` Maciej W. Rozycki
2001-02-02 18:12 ` Gérard Roudier
2001-02-02 22:17 ` Manfred Spraul
2001-02-03 10:28 ` Gérard Roudier
2001-02-03 14:44 ` [test patch] reliable apic lockup with one enable/disable_irq() Manfred
2001-02-05 10:32 ` [patch] 2.4.0, 2.4.0-ac12: APIC lock-ups Maciej W. Rozycki
2001-02-03 12:14 ` Manfred Spraul
2001-02-05 11:38 ` Maciej W. Rozycki
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=3A75D533.7F3F4019@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--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