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] [day] [month] [year] [list]
Message-Id: <200704161758.45943.dkukawka@suse.de>
Date:	Mon, 16 Apr 2007 17:58:45 +0200
From:	Danny Kukawka <dkukawka@...e.de>
To:	Pavel Machek <pavel@....cz>
Cc:	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
	Stefan Seyfried <seife@...e.de>
Subject: Re: [PATCH] ACPI: more verbose thermal zone shutdown message

On Sonntag, 15. April 2007, Pavel Machek wrote:
> Hi!
> 
> > while debug some strange termal shutdowns I wrote this patch to get more 
> > information in /var/log/messages about the reason for the shutdown. I 
> > think this would be useful in general.
> > 
> > Danny
> > 
> > From: Danny Kukawka <dkukawka@...e.de>
> > Subject: ACPI: more verbose thermal zone shutdown message
> > 
> > add more information to acpi thermal zone shutdown message for easier
> > debugging
> > 
> > Signed-off-by: Danny Kukawka <dkukawka@...e.de>
> 
> Yes, please.
[..]
> Why two printks with same info, and why is one of them WARNING and
> second EMERG?

I think this is  what happen and why there are currently two messages:

* if the temperature is really critical you get (now) this:
----------------
kernel: Critical trip point (102 C) reached on Thermalzone [THM]
kernel: Critical temperature reached (150 C on [THM] with trip point set to: 
102 C), shutting down.
----------------

* and if something send a critical temp event to the thermal zone you get:
----------------
kernel: Critical temperature reached (42 C on [THM] with trip point set to: 
102 C), shutting down.
----------------

Maybe we can delete the first one, since you get now also from second 
message the information if the temperature was really critical or if 
there was an other reason for the shutdown, but in the past this was
IMO needed to differ.

Danny
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ