linux-kernel - Re: swsusp and suspend2 like to overheat my laptop

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200608091415.51226.rjw@sisk.pl>
Date:	Wed, 9 Aug 2006 14:15:51 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Pavel Machek <pavel@....cz>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Suspend2-devel@...ts.suspend2.net, linux-pm@...l.org,
	ncunningham@...uxmail.org
Subject: Re: swsusp and suspend2 like to overheat my laptop

On Wednesday 09 August 2006 13:58, Pavel Machek wrote:
> Hi!
> 
> > > Okay, can you try to leave it up for a week or two (no suspends, no
> > > poweroffs) and see what happens?
> > 
> > I've had this laptop running for a couple of months without shutting down
> > and it doesn't have a problem.  The only time that I do shut it down
> 
> Ok.
> 
> > > > > P4 has thermal protection, so you are actually safe.
> > > >
> > > > Yeah, but still, the keyboard gets pretty hot too, and I'm actually more
> > > > worried about damaging something that is close by than damaging the CPU
> > > > itself.
> > >
> > > If you damage something, machine was misdesigned in the first place.
> > 
> > agreed, but you never know ;)  This laptop is currently my lifeline :)
> 
> You'd have good reason to get new one.
> 
> > > cat we get contents of /proc/acpi/thermal*/*/* ?
> > 
> > I'm running after a poweroff (left it running over night in the hotel, and
> > I'm still in the hotel).
> > 
> > $ grep . /proc/acpi/thermal_zone/THRM/*
> > /proc/acpi/thermal_zone/THRM/cooling_mode:<setting not supported>
> > /proc/acpi/thermal_zone/THRM/cooling_mode:cooling mode: passive
> > /proc/acpi/thermal_zone/THRM/polling_frequency:<polling disabled>
> > /proc/acpi/thermal_zone/THRM/state:state:                   ok
> > /proc/acpi/thermal_zone/THRM/temperature:temperature:             48 C
> > /proc/acpi/thermal_zone/THRM/trip_points:critical (S5):           88 C
> > /proc/acpi/thermal_zone/THRM/trip_points:passive:                 81 C: tc1=4 tc2=3 tsp=100 devices=0xcf6c2338
> > 
> > Note thermal_zone/THRM was finished with bash tab completion so they are
> > the only things that match the above glob expr.
> 
> Ok, so it is the bios doing temperature control up-to 81C. At 81C,
> linux should start cooling it, and at 88C, linux should shutdown. At
> little higher temperature, hardware should emergency shutdown.
> 
> > > How s2ram works would be useful info.
> > 
> > No idea.
> 
> Well, try it :-). suspend.sf.net.
> 
> > It does look like something isn't setting up the ACPI power properly on
> > resume, and that the CPU is probably in a busy loop while the machine is
> > idle.  Just a guess.
> 
> Fan is not controlled by ACPI. But we may be saving some memory we
> should not save, or something like that.

If it's a P4, we rather don't, because the ACPI tables should be above the
last pfn in the normal zone.  Still, Steven please send your dmesg after a
fresh boot.

Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/