public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Joshua Wise <joshua-NtISFavHD68j5TC/SZClsA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Source of buzzing determined for hp tc1100
Date: Mon, 06 Dec 2004 15:28:23 -0800	[thread overview]
Message-ID: <41B4EB17.5010702@root.org> (raw)
In-Reply-To: <41B4E721.1040601-NtISFavHD68j5TC/SZClsA@public.gmane.org>

Joshua Wise wrote:
> Hi all,
> 
> Okay, so I have determined the source of the buzzing for the hp tc1100, 
> and I have a list of conditions to be met for the buzzing to show up. I 
> determined the following mostly by observation. To determine which ACPI 
> modules were causing issues, I whipped up a GOK keyboard to use pen 
> input to determine the problem-causer. I will make that keyboard 
> available on request.
> 
> So, without further ado, here are the conditions to be met:
>   * The system must be idle/
>   * The system must be undocked from the USB keyboard base.
>   * The system must be unplugged from 18VDC power.
>   * The processor module must be loaded.
> 
> If all of the above conditions are met, the system will emit a buzzing 
> from the CPU fan area. (Sometimes the system must be throttled above 75% 
> for the buzzing to occur.)
> 
> Has anyone any insight?

This is a faq, the answer is C3.

-- 
Nate


-------------------------------------------------------
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://productguide.itmanagersjournal.com/

  parent reply	other threads:[~2004-12-06 23:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 23:11 Source of buzzing determined for hp tc1100 Joshua Wise
     [not found] ` <41B4E721.1040601-NtISFavHD68j5TC/SZClsA@public.gmane.org>
2004-12-06 23:28   ` Nate Lawson [this message]
     [not found]     ` <41B4EB17.5010702-Y6VGUYTwhu0@public.gmane.org>
2004-12-06 23:54       ` Joshua Wise
     [not found]         ` <41B4F13B.6060304-NtISFavHD68j5TC/SZClsA@public.gmane.org>
2004-12-07  3:43           ` Jeff Pitman
     [not found]             ` <200412071143.13460.symbiont-tdrK/OAtAx2ELgA04lAiVw@public.gmane.org>
2004-12-07 15:42               ` Nate Lawson
2004-12-06 23:28   ` Jeff Pitman
     [not found]     ` <200412070728.57179.symbiont-tdrK/OAtAx2ELgA04lAiVw@public.gmane.org>
2004-12-07  0:00       ` Joshua Wise

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=41B4EB17.5010702@root.org \
    --to=nate-y6vguytwhu0@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=joshua-NtISFavHD68j5TC/SZClsA@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