From: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
To: Andrej Prsa <andrej.prsa-zs/Xt9NzJtxxh+DGd0HQrg@public.gmane.org>
Cc: ACPI Support
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: HP/Compaq NC6120 ACPI problems
Date: Thu, 17 Mar 2005 12:48:24 -0700 [thread overview]
Message-ID: <1111088904.11380.36.camel@eeyore> (raw)
In-Reply-To: <20050317200052.686d683f.andrej.prsa-zs/Xt9NzJtxxh+DGd0HQrg@public.gmane.org>
On Thu, 2005-03-17 at 20:00 +0100, Andrej Prsa wrote:
> The symptoms are as follows: computer starts fine, but within 20-30
> seconds it gradually slows down to the point where it can no longer be
> used - it takes 5 minutes to start the terminal. The fan doesn't work,
> so the machine overheats. Using 'top' shows that 55% of CPU power is
> consumed by kacpid.
Take a look at /proc/interrupts a couple times, and see if there's
a device that's spewing interrupts.
> A totally unreliable and probably a misleading thought is that
> PCI interrupts are messed up without ACPI; this assumption is based
> on the fact that the system hangs prior to the statement:
>
> ACPI: PCI interrupt 0000:02:06.2[C] -> GSI 22 (level, low) -> IRQ 217
>
> in dmesg (which occurs if ACPI is left on). When ACPI is turned off,
> the fan works normally and there is no overheating whatsoever.
Try booting with "pci=routeirq". If that makes a difference,
please post the dmesg log and output of "lspci". If you can
also capture the dmesg log without "pci=routeirq", that would
also be useful.
> I also tried recompiling the 2.6.11.4 kernel and fiddling with
> ACPI settings, but the result is kernel panic with VFS related problem
> (although I created ramdisk by hand and I'm sure everything else is ok).
You can avoid the hassle of a ramdisk by building the drivers
and filesystems you need static (instead of as modules).
Bjorn
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-17 19:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 19:00 HP/Compaq NC6120 ACPI problems Andrej Prsa
[not found] ` <20050317200052.686d683f.andrej.prsa-zs/Xt9NzJtxxh+DGd0HQrg@public.gmane.org>
2005-03-17 19:48 ` Bjorn Helgaas [this message]
2005-03-17 20:56 ` Andrej Prsa
[not found] ` <20050317215635.1c788c09.andrej.prsa-zs/Xt9NzJtxxh+DGd0HQrg@public.gmane.org>
2005-03-17 21:13 ` Kristoffer Sjoberg
2005-03-18 0:05 ` Matthew Garrett
2005-03-18 18:23 ` Andrej Prsa
[not found] ` <20050318192300.629e2148.andrej.prsa-zs/Xt9NzJtxxh+DGd0HQrg@public.gmane.org>
2005-03-19 3:19 ` Matthew Garrett
2005-03-19 9:35 ` Andrej Prsa
[not found] ` <20050319103550.2cd6bd9d.andrej.prsa-zs/Xt9NzJtxxh+DGd0HQrg@public.gmane.org>
2005-03-19 22:13 ` Stefan Seyfried
2005-03-20 23:46 ` Matthew Garrett
2005-03-21 10:40 ` Andrej Prsa
[not found] ` <20050321114014.38a548d4.andrej.prsa-zs/Xt9NzJtxxh+DGd0HQrg@public.gmane.org>
2005-03-21 12:33 ` Matthew Garrett
2005-03-29 15:15 ` Andrej Prsa
2005-03-31 20:27 ` Pavel Machek
[not found] ` <20050331202724.GB609-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
2005-04-01 22:08 ` Stefan Seyfried
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=1111088904.11380.36.camel@eeyore \
--to=bjorn.helgaas-vxdhtt5mjny@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrej.prsa-zs/Xt9NzJtxxh+DGd0HQrg@public.gmane.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