From: Len Brown <len.brown@intel.com>
To: knobi@knobisoft.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Two problems after upgrade tto 2.4.26
Date: 24 Apr 2004 22:50:46 -0400 [thread overview]
Message-ID: <1082861443.3160.18.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615F981B@hdsmsx403.hd.intel.com>
On Fri, 2004-04-23 at 04:22, Martin Knoblauch wrote:
Re: keyboard/mouse instability with ACPI enabled starting in 2.4.26
> >Does /proc/interrupts show any acpi events?
> >Did it in 2.4.23?
> >
> Len,
>
> some ACPI Interrupts:
>
> cat /proc/interrupts
> CPU0
> 0: 31464 XT-PIC timer
> 1: 570 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 3: 5 XT-PIC HiSax
> 8: 2 XT-PIC rtc
> 9: 1197 XT-PIC acpi
> 10: 1695 XT-PIC eth0, usb-uhci, Texas Instruments
> PCI1420, Texas Instruments PCI1420 (#2)
> 12: 5460 XT-PIC PS/2 Mouse
> 14: 18052 XT-PIC ide0
> 15: 11 XT-PIC ide1
kill acpid and
# cat /proc/acpi/event
to see what the events are.
We we are working on a GPE issue related to spurious
ACPI interrupts right now, but I'd actually expect
2.4.26 to get _fewer_ acpi interrupts than 2.4.25, not more.
Re: fan running more
it would be interesting if you notice a temperature difference
between the releases in /proc/acpi/thermal...
eg.
cat /proc/acpi/thermal_zone/THRM/temperature
temperature: 37 C
FAN isn't always controlled by ACPI. If it is, you'll see it
in the dmesg like this:
ACPI: Power Resource [PFAN] (off)
In either case, it may be that we're running hotter (say idle
isn't working right), or we're running the fan more often by mistake.
For idle, you can compare the /proc/acpi/processor/CPU0/power
file in the two releases to see if one release is getting into
a deeper power-saving state than the other.
Eg, this centrino box isn't getting into C3 because USB is active.
cat /proc/acpi/processor/CPU0/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[00370077]
C3: promotion[--] demotion[C2] latency[085]
usage[00000000]
cheers,
-Len
next parent reply other threads:[~2004-04-25 2:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F981B@hdsmsx403.hd.intel.com>
2004-04-25 2:50 ` Len Brown [this message]
2004-04-26 10:04 ` Two problems after upgrade tto 2.4.26 Martin Knoblauch
2004-04-23 8:22 Martin Knoblauch
[not found] <A6974D8E5F98D511BB910002A50A6647615F936B@hdsmsx403.hd.intel.com>
2004-04-22 3:08 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2004-04-20 11:09 Martin Knoblauch
2004-04-16 11:18 Martin Knoblauch
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=1082861443.3160.18.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=knobi@knobisoft.de \
--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 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.