public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Joshua Wise <joshua-NtISFavHD68j5TC/SZClsA@public.gmane.org>
To: Nate Lawson <nate-Y6VGUYTwhu0@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 18:54:35 -0500	[thread overview]
Message-ID: <41B4F13B.6060304@joshuawise.com> (raw)
In-Reply-To: <41B4EB17.5010702-Y6VGUYTwhu0@public.gmane.org>

> This is a faq, the answer is C3.

Hrm. I looked in the Intel FAQ linked off of the ACPI.sf.net page, and 
didn't find anything there.

I then googled for acpi c3 noise, which gave me some information about 
Thinkpads and sound card noise, but the noise occurs regardless of 
soundcard-osity. In fact, it seems to be coming from near the CPU fan.

I did do a quick test, though. I did a while true; do sleep 1; cat 
/proc/acpi/processor/CPU0/power; done .

While the system is connected to the USB keyboard, the it will never go 
into C3 state, and bus master activity is always ffffffff.

When the system is disconnected, it will stay in C3 state most of the time.

However, when I connect AC power, the buzzing goes away, but the system 
still spends most of its time in C3 state.

I'm willing to believe that the battery's power supply in combination 
with some CPU supply element causes buzzing, and that the [more|less] 
filtered DC supply does not cause this buzzing. This begs the question, 
though - is there really a power savings advantage to C3? Am I missing 
out on something when I am not in C3 state? Will the device run 
noticably cooler/have noticably longer battery life when C3 state is 
enabled?

I have also noticed that C1 state is rarely entered on this device - 
only 10 usage units over about two hours of uptime. The machine feels a 
bit latent otherwise... I'm not certain whether this is due to the lack 
of C1 state usage, or whether this should just be attributed to the fact 
that the machine is a bit underpowered.

joshua


-------------------------------------------------------
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:54 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
     [not found]     ` <41B4EB17.5010702-Y6VGUYTwhu0@public.gmane.org>
2004-12-06 23:54       ` Joshua Wise [this message]
     [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=41B4F13B.6060304@joshuawise.com \
    --to=joshua-ntisfavhd68j5tc/szclsa@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=nate-Y6VGUYTwhu0@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