From: Martin Aspeli <optilude@gmx.net>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Chris Wright <chrisw@osdl.org>
Subject: Re: Horrible ordeals with ACPI, APIC and HIGHMEM (2.6.0-test* and -ac kernels)
Date: Thu, 09 Oct 2003 23:14:03 +0100 [thread overview]
Message-ID: <oprwsqppse9y0cdf@mail.gmx.net> (raw)
In-Reply-To: <20031009145839.A18072@build.pdx.osdl.net>
> fixes acpi pci link allocation which could pick a bad irq causing an
> interrupt storm. typical symptom was hang on boot.
Well, the hang only occurs when Local APIC was enabled. If Local APIC is
taken out of the kernel, it boots, but events/0 starts eating my entire
CPU and the fan is constantly on. I can't tell whether this is because
events/0 is eating my CPU and hence it's running hot, or if it's
(partially) unrelated.
I'm still a little lost as to what Local APIC does (apart from being an
interrupt controller) or how it's related to ACPI (apart from obvious
puns), or indeed whether or not my Penium-M has one.
You say stray ACPI events could cause keventd to chew CPU. It does seem
likely. What would cause a runaway ACPI event? How would I stop one (apart
from acpi=off, of course, which leaves me IRQ less).
Conversely, I suppose - is it possible to give IRQs to my sound card and
the four or five other unidentified pieces of hardware that get no IRQ at
boot, manually even? I'm a little worried this may leave me fan-less,
although the BIOS seems to be turning the fan on sometimes if I boot with
acpi=off.
>> And why do things run like a 286 when I enable HIGHMEM?
> I don't know, it shouldn't.
I most whole-heartedly agree!
Thank you for all your help!
Martin
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
prev parent reply other threads:[~2003-10-09 22:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 18:50 Horrible ordeals with ACPI, APIC and HIGHMEM (2.6.0-test* and -ac kernels) Martin Aspeli
2003-10-09 21:05 ` Chris Wright
2003-10-09 21:26 ` Martin Aspeli
2003-10-09 21:58 ` Chris Wright
2003-10-09 22:14 ` Martin Aspeli [this message]
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=oprwsqppse9y0cdf@mail.gmx.net \
--to=optilude@gmx.net \
--cc=chrisw@osdl.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