On Sunday, 3 June 2007 23:20, Olaf Dietsche wrote:
Rafael J. Wysocki [EMAIL PROTECTED] writes:
Second, you can use PM_TRACE (Documentation/power/s2ram.txt) to find the
place where it really fails.
First I augmented my minimal config kernel with some TRACE_RESUME()s:
---
On Thu, May 17, 2007 at 06:35:48PM -0400, Len Brown wrote:
Yes, SuSE enables polling mode by default, but that is just
distro specific value add that should eventually be fixed.
I will do that for openSUSE FACTORY.
--
Stefan Seyfried
QA / RD Team Mobile Devices| Any
On Tue, May 22, 2007 at 11:06:36AM +0200, Pavel Machek wrote:
We need to ignore trip point updates from BIOS, and we need to poll
thermals when use overrides trip points. That's expected. Plus I've
yet to see platform actually updating the trip points.
Thinkpad 600, whenever a trip point is
Hi!
According to the SYSTEM V APPLICATION BINARY INTERFACE,
Intel386 Architecture:
ecx and edx: Scratch registers have no specified role in the standard calling
sequence. Functions do not have to preserve their values for the
caller.
Thanks for confirming.
On Mon 2007-06-04 11:02:01, Stefan Seyfried wrote:
On Thu, May 17, 2007 at 06:35:48PM -0400, Len Brown wrote:
Yes, SuSE enables polling mode by default, but that is just
distro specific value add that should eventually be fixed.
I will do that for openSUSE FACTORY.
Well, I still
On Thu 2007-05-31 22:46:11, Len Brown wrote:
On Monday 21 May 2007 08:11, Pavel Machek wrote:
On Thu 2007-05-17 18:42:43, Len Brown wrote:
Something similar happened to me on XE3, yes.
(Actual values were different; BIOS specified critical temperature at
cca 95C, but hw killed
On Sat, 2007-06-02 at 01:15 -0400, Len Brown wrote:
From: Thomas Renninger [EMAIL PROTECTED]
For users with active thermal trip points, they need
the fan's name, rather than its address, to understand
where to look to observe and control fan state.
Signed-off-by: Thomas Renninger [EMAIL
