From: Len Brown <len.brown@intel.com>
To: Robert Fendt <fendt@physik.uni-dortmund.de>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: peculiar problem with 2.6, 8139too + ACPI
Date: 20 May 2004 21:16:32 -0400 [thread overview]
Message-ID: <1085102192.12349.508.camel@dhcppc4> (raw)
In-Reply-To: <20040521015314.7001a9e9.fendt@physik.uni-dortmund.de>
On Thu, 2004-05-20 at 19:53, Robert Fendt wrote:
> On 17 May 2004 14:24:42 -0400
> differing network topologies.
probably not important, just shows that this is timing dependent.
System must be quiet enough that it gets into idle.
> > Does
> > cat /proc/acpi/processor/CPU0/power
> > show any C3 usage?
>
> Yes, if I read this correctly, it does. BTW, seemingly pretty much the same on AC or battery.
>
> betazed:~# cat /proc/acpi/processor/CPU1/power
> active state: C2
> default state: C1
> bus master activity: ffffffff
> states:
> C1: promotion[C2] demotion[--] latency[000] usage[00000010]
> *C2: promotion[C3] demotion[C1] latency[001] usage[00025200]
> C3: promotion[--] demotion[C2] latency[101] usage[00024564]
>
Please verify that the problem goes away when you exclude the
acpi/processor module (CONFIG_ACPI_PROCESSOR) from the system.
With the recent spate of C3 issues, we should make an easier way to
disable C3 until it is fixed...
thanks,
-Len
next prev parent reply other threads:[~2004-05-21 1:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615FB5FE@hdsmsx403.hd.intel.com>
2004-05-15 1:36 ` peculiar problem with 2.6, 8139too + ACPI Len Brown
2004-05-15 23:30 ` Robert Fendt
2004-05-17 10:30 ` Robert Fendt
2004-05-17 18:24 ` Len Brown
2004-05-17 19:10 ` Jeff Garzik
2004-05-20 23:53 ` Robert Fendt
2004-05-21 1:16 ` Len Brown [this message]
2004-05-27 13:45 ` Robert Fendt
2004-05-14 13:28 Robert Fendt
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=1085102192.12349.508.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=fendt@physik.uni-dortmund.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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