public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Machowinski <scotch-cGBD8117FJM@public.gmane.org>
To: pumpkin-Mmb7MZpHnFY@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: C2, C3 and bus master activity
Date: Wed, 20 Jul 2005 01:00:03 +0200	[thread overview]
Message-ID: <42DD85F3.9050300@tzi.de> (raw)
In-Reply-To: <200507192359.56553.pumpkin-Mmb7MZpHnFY@public.gmane.org>

pumpkin wrote:
> Hello
> 
> I tested this by removing kernel/driver/usb/* and rebuilding initrd (just to 
> be sure). It did not change anything for console (still 50:50 between C2 and 
> C3) and made Xorg crash pretty hard.
> 
> Do you think removing all the other external buses (Firewire, ethernet, 
> WLAN ,..) would change something ? 
> 
Sometimes an active WLAN driver causes bus master activity...
You also should not use an USB Mouse...

And by the way, what's wrong with 50:50 C2 C3 ?
This seems pretty normal to me.

> Could cpufreqd be part of the problem ?
> 
> Thanks,
> 
> On Tuesday 19 July 2005 22:18, Bob Lees wrote:
> 
>>Hi
>>
>>In a word USB.  I don't fully understand why, but if I disable USB then
>>both my laptops will go into C3 or C4, with USB enabled stays in C2.
>>
>>Laptops are Compaq EVO 800c and IBM T42p both running SUSE 9.3 with a stock
>>SuSE kernel 2.6.11-suse modified
>>
>>Bob
>>


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

  parent reply	other threads:[~2005-07-19 23:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 18:50 C2, C3 and bus master activity pumpkin
     [not found] ` <200507192050.28343.pumpkin-Mmb7MZpHnFY@public.gmane.org>
2005-07-19 20:18   ` Bob Lees
     [not found]     ` <200507192118.37528.bob-l+PWtdWbHAsG2Il/BtU0GPXRex20P6io@public.gmane.org>
2005-07-19 21:59       ` pumpkin
     [not found]         ` <200507192359.56553.pumpkin-Mmb7MZpHnFY@public.gmane.org>
2005-07-19 23:00           ` Janosch Machowinski [this message]
     [not found]             ` <42DD85F3.9050300-cGBD8117FJM@public.gmane.org>
2005-07-20 17:21               ` pumpkin
     [not found]                 ` <200507201921.43576.pumpkin-Mmb7MZpHnFY@public.gmane.org>
2005-07-20 19:29                   ` pumpkin
     [not found]                     ` <42DEB3E8.6080601@tzi.de>
     [not found]                       ` <42DEB3E8.6080601-cGBD8117FJM@public.gmane.org>
2005-07-21 17:31                         ` pumpkin
2005-07-21 16:08                 ` Volker Braun
2005-07-20 19:05       ` Johan Vromans
     [not found]         ` <m23bq98fir.fsf-KjnUIgV0B0bak1Ioo/c9IoRWq/SkRNHw@public.gmane.org>
2005-07-20 19:31           ` Bob Lees
     [not found]             ` <200507202031.38488.bob-l+PWtdWbHAsG2Il/BtU0GPXRex20P6io@public.gmane.org>
2005-07-20 19:56               ` Janosch Machowinski
2005-07-21  5:24       ` Pavel Machek

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=42DD85F3.9050300@tzi.de \
    --to=scotch-cgbd8117fjm@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=pumpkin-Mmb7MZpHnFY@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