public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: HP/Compaq NC6120 ACPI problems
Date: Mon, 21 Mar 2005 12:33:31 +0000	[thread overview]
Message-ID: <1111408412.8136.233.camel@tyrosine> (raw)
In-Reply-To: <20050321114014.38a548d4.andrej.prsa-zs/Xt9NzJtxxh+DGd0HQrg@public.gmane.org>

On Mon, 2005-03-21 at 11:40 +0100, Andrej Prsa wrote:

> I see; please let me know when you get any additional information and of
> course if there's anything I can do to help! If it's not too much
> trouble, could you (or anyone else of course) please explain what
> exactly does this setpci do?

The setpci sets a register that allows the GPE to fire again. The BIOS
ought to be doing it itself - I've reported it to HP.

> Intriguingly, I recompiled the kernel with ACPI support built in (in
> contrast to having a modular ACPI support) and this time kacpid
> doesn't overload the processor and the fan is working!

Ah. That /may/ fit with my observations from suspend to disk - the
hardware seems unhappy if Linux and the hardware disagree about the fan
state. My suspicion is that if there's a thermal trip event between
Linux switching the hardware to ACPI mode and the fan module being
loaded, you'll get the "mad kacpid" behaviour. I'd strongly recommend
having the fan module built in - there's the risk of hardware damage
otherwise.

> > Warning - there'll be huge amounts of it. Really huge amounts. The
> > stuff we're interested in is whatever appears after kacpid has begun
> > taking up all the processor time.
> 
> Please find the messages.gz file at (3.1MB compressed size!):
> 
> 	http://www.fiz.uni-lj.si/~prsa/messages.gz
> 
> (sorry for the enormous size (~50MB uncompressed), but I didn't want to
> cut out anything relevant!) The start of the messages file is the start
> of kacpid going crazy.

Great, thanks! I'll take a look at this later on. When I traced it on
the 6220, I found that it seemed to be related to a thermal zone event,
which would fit with observations.

-- 
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org



-------------------------------------------------------
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

  parent reply	other threads:[~2005-03-21 12:33 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
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 [this message]
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=1111408412.8136.233.camel@tyrosine \
    --to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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