From: idalton@ferret.phonewave.net
To: Frank de Lange <frank@unternet.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.3: still experiencing APIC-related hangs
Date: Fri, 30 Mar 2001 08:32:39 -0800 [thread overview]
Message-ID: <20010330083239.A3410@ferret.phonewave.net> (raw)
In-Reply-To: <20010330143224.A23427@unternet.org>
In-Reply-To: <20010330143224.A23427@unternet.org>; from frank@unternet.org on Fri, Mar 30, 2001 at 02:32:24PM +0200
On Fri, Mar 30, 2001 at 02:32:24PM +0200, Frank de Lange wrote:
> Hi'all,
>
> Subject says it all: 2.4.3 (unpatchaed) is still causing the dreaded
> APIC-related hangs on SMP BX systems (Abit BP-6, maybe Gigabyte). I still need
> to apply one of Maciej's patches to get rid of these hangs. The source comments
> in arc/i386/kernel/apic.c ("If focus CPU is disabled then the hang goes away")
> are incorrect, as the hang does not go away by simply disabling focus CPU. The
> only way for me to get rid of the hangs is to apply patch-2.4.1-io_apic-46
> (which does the LEVEL->EDGE->LEVEL triggered trick to 'free' the IO_APIC). I've
> been running with this patch for quite some time now, and have not experienced
> any problems with it. Maybe it it time to include it in the main kernel,
> perhaps as a configurable option ("BROKEN_IO_APIC")?
>
> Maciej, did you submit the patch to Linus? It really seems to solve the
> (occurence of the) problems with these boards...
Where is this patch found? I am not seeing it so far on kernel.org.
-- Ferret
next prev parent reply other threads:[~2001-03-30 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-30 12:32 Frank de Lange
2001-03-30 16:06 ` Maciej W. Rozycki
2001-03-30 16:32 ` idalton [this message]
2001-03-30 16:36 ` Frank de Lange
2001-04-09 21:22 ` Kurt Garloff
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=20010330083239.A3410@ferret.phonewave.net \
--to=idalton@ferret.phonewave.net \
--cc=frank@unternet.org \
--cc=linux-kernel@vger.kernel.org \
/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®