public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@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: Fri, 18 Mar 2005 00:05:18 +0000	[thread overview]
Message-ID: <1111104319.8136.182.camel@tyrosine> (raw)
In-Reply-To: <20050317215635.1c788c09.andrej.prsa-zs/Xt9NzJtxxh+DGd0HQrg@public.gmane.org>

On Thu, 2005-03-17 at 21:56 +0100, Andrej Prsa wrote:

> Observational update: it does *NOT* gradually slow down, it slows down
> *instantly* after 2-3 minutes of running; the time of kacpid blowup is
> somewhat arbitrary, it sometimes happens even before the boot-up is
> complete. If I was to make another wild guess, it might be connected
> with the fan - when the computer is cool, the blowup occurs later, if it
> is warm, it occurs sooner. Is it possible that the call to turn the fan
> on is triggering this kacpid blowup? How does one go about to test this?

Ah, right - I've seen similar behaviour on a range of HPs (inluding the
6120). Try using 
http://bugzilla.kernel.org/attachment.cgi?id=4516&action=view and see if
it makes a difference.
-- 
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-18  0:05 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 [this message]
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=1111104319.8136.182.camel@tyrosine \
    --to=mjg59-1xo5oi07kqx4cg9nei1l7q@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