All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
To: Lorenzo Colitti <lorenzo-Z4WAQ3j+MphBDgjK7y7TUQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI thermal event causes brief freeze
Date: Fri, 25 Feb 2005 11:34:25 +0100	[thread overview]
Message-ID: <421EFF31.9060002@suse.de> (raw)
In-Reply-To: <421E6D6C.2090906-Z4WAQ3j+MphBDgjK7y7TUQ@public.gmane.org>

Lorenzo Colitti wrote:
> Hi,
> 
> since I upgraded to kernel 2.6.11-rc4, every time there is a thermal 
> event my machine (HP/compaq NC6000) freezes for about 1 second. Audio 
> stutters and pretty much everything, including the mouse pointer, stops 
> dead for a bit.

Have you enabled ACPI_DEBUG?
If yes, try again without.

> 
> This did not happen with a similarly configured vanilla 2.6.9 kernel.

ACPI_DEBUG is incredibly slow since 2.6.11-rc2-bk10.
> 
> It's pretty irritating. Is there anything I can do to debug this?

You probably solve this by not debugging :)

       Thomas


-------------------------------------------------------
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-02-25 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-25  0:12 ACPI thermal event causes brief freeze Lorenzo Colitti
     [not found] ` <421E6D6C.2090906-Z4WAQ3j+MphBDgjK7y7TUQ@public.gmane.org>
2005-02-25 10:34   ` Thomas Renninger [this message]
     [not found]     ` <421EFF31.9060002-l3A5Bk7waGM@public.gmane.org>
2005-02-25 13:48       ` Lorenzo Colitti
2005-02-25 15:30   ` 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=421EFF31.9060002@suse.de \
    --to=trenn-l3a5bk7wagm@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=lorenzo-Z4WAQ3j+MphBDgjK7y7TUQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.