From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Thomas Herrmann <ollo.diab-Mmb7MZpHnFY@public.gmane.org>
Cc: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: RE: K7 CPU disconnect & system lock
Date: Mon, 19 Jan 2004 22:43:42 +0100 [thread overview]
Message-ID: <20040119214342.GC380@elf.ucw.cz> (raw)
In-Reply-To: <21180.1074446641-oa/r6l4+J3Zmcu3hnIyYJQ@public.gmane.org>
Hi!
> the K7 cpu disconnect feature is a power save mode, where the CPU
> disconnects from the north bridge and goes into sleep mode. Any interrupt will wake-up
> the CPU which then needs to connect to the north bridge again to transfer
> data. While CPU disconnect enabled the idle temperature of the CPU drops from
> around 52C to 27C on my systems. On certain systems this feature can be enabled
> via BIOS, but there is also a tool called "athcool" which sets the
> configuration register.
>
> I have attached the requested logs. As you will see while acpi=off certain
> devices (like USB) are not available due to no IRQ routing. All devices work
> fine with acpi enabled.
I believe that was traced to hw problem, see kernel list for nforce2
info.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-19 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 17:24 K7 CPU disconnect & system lock Thomas Herrmann
[not found] ` <21180.1074446641-oa/r6l4+J3Zmcu3hnIyYJQ@public.gmane.org>
2004-01-19 21:43 ` Pavel Machek [this message]
2004-01-20 10:11 ` Thomas Herrmann
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=20040119214342.GC380@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=ollo.diab-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