x60 - spontaneous thermal shutdown
Hi!
x60 shut down after quite a while of uptime, in period of quite heavy load:
Sep 4 23:33:01 amd kernel: ACPI: Critical trip point Sep 4 23:33:01 amd kernel: Critical temperature reached (128 C), shutting down. Sep 4 23:33:01 amd shutdown[32585]: shutting down for system halt Sep 4 23:34:42 amd init: Switching to runlevel: 0
I do not think cpu reached 128C, as I still have my machine... Did anyone else see that?
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Hi,
Quoted 5 lines · Pavel Machek
Hi!
x60 shut down after quite a while of uptime, in period of quite heavy load:
Quoted 7 lines
Sep 4 23:33:01 amd kernel: ACPI: Critical trip point Sep 4 23:33:01 amd kernel: Critical temperature reached (128 C), shutting down. Sep 4 23:33:01 amd shutdown[32585]: shutting down for system halt Sep 4 23:34:42 amd init: Switching to runlevel: 0I do not think cpu reached 128C, as I still have my machine... Did anyone else see that?
Could this be in any way related to the (in)famous Random Shutdown issues on a little too many Apple MacBooks?
(since the x60 incidentally just happens to be Core Duo architecture, too)
Those Random Shutdown issues at least in several cases appear to happen due to trouble with the temperature sensor or mainboard issues. Thermal management is in quite some trouble there, judging from the rather diverse aspects of machine shutdown failure... (fan not working, CPU overheating, NOT overheating but shutting down directly after boot, ...)
There's nothing like rushing out immature hardware to unsuspecting consumers...
Andreas Mohr
Hi!
Quoted 8 lines
Quoted 8 lines
x60 shut down after quite a while of uptime, in period of quite heavy load:
Sep 4 23:33:01 amd kernel: ACPI: Critical trip point Sep 4 23:33:01 amd kernel: Critical temperature reached (128 C), shutting down. Sep 4 23:33:01 amd shutdown[32585]: shutting down for system halt Sep 4 23:34:42 amd init: Switching to runlevel: 0
Quoted 7 lines
Quoted 2 lines
I do not think cpu reached 128C, as I still have my machine... Did anyone else see that?
Could this be in any way related to the (in)famous Random Shutdown issues on a little too many Apple MacBooks?
(since the x60 incidentally just happens to be Core Duo architecture, too)
Well, but those macbooks were really overheating, no? This seems like sensor failure, because I do not think cpu had 128 Celsius, without going through 100 Celsius, first.
Quoted 6 lines
Those Random Shutdown issues at least in several cases appear to happen due to trouble with the temperature sensor or mainboard issues. Thermal management is in quite some trouble there, judging from the rather diverse aspects of machine shutdown failure... (fan not working, CPU overheating, NOT overheating but shutting down directly after boot, ...)
I had fan working at the time of shutdown, and machine was able to boot immediately afterwards. That means that 128 celsius was sensor error.
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Hi,
Quoted 3 lines · Pavel Machek
Well, but those macbooks were really overheating, no? This seems like sensor failure, because I do not think cpu had 128 Celsius, without going through 100 Celsius, first.
No, in several cases it was a problem with a broken/damaged sensor cable. But it seems there are a number of different problems with thermal management, a non-working sensor cable only being (albeit a significant) one of those.
Google "MacBook random shutdown" will provide tons of information.
Quoted 3 lines
I had fan working at the time of shutdown, and machine was able to boot immediately afterwards. That means that 128 celsius was sensor error.
Let's hope people get that braindamage resolved, either via BIOS updates (hmm, but probably not helpful in case of ACPI?) or by shipping/repairing into working hardware (an astonishing amount of people already had their 2nd or 3rd non-working repair).
Andreas Mohr
Quoted 14 lines
Quoted 6 lines
Quoted 6 lines
Sep 4 23:33:01 amd kernel: ACPI: Critical trip point Sep 4 23:33:01 amd kernel: Critical temperature reached (128 C), shutting down. Sep 4 23:33:01 amd shutdown[32585]: shutting down for system halt Sep 4 23:34:42 amd init: Switching to runlevel: 0Quoted 7 lines
Quoted 2 lines
I do not think cpu reached 128C, as I still have my machine... Did anyone else see that?
Could this be in any way related to the (in)famous Random Shutdown issues on a little too many Apple MacBooks?
(since the x60 incidentally just happens to be Core Duo architecture, too)
Quoted 7 lines
Well, but those macbooks were really overheating, no? This seems like sensor failure, because I do not think cpu had 128 Celsius, without going through 100 Celsius, first.
I had fan working at the time of shutdown, and machine was able to boot immediately afterwards. That means that 128 celsius was sensor error.
If it was near 128 C for some time, the plastic case the mainboard is housed in would have been extremely hot and one would have probably burned his fingers.
Jan Engelhardt
Quoted 5 lines · Pavel Machek
Hi!
x60 shut down after quite a while of uptime, in period of quite heavy load:
Quoted 7 lines
Sep 4 23:33:01 amd kernel: ACPI: Critical trip point Sep 4 23:33:01 amd kernel: Critical temperature reached (128 C), shutting down. Sep 4 23:33:01 amd shutdown[32585]: shutting down for system halt Sep 4 23:34:42 amd init: Switching to runlevel: 0I do not think cpu reached 128C, as I still have my machine... Did anyone else see that?
my usual suspect: use ec_intr=0. I have seen this rather often on HP machines. I attributed it to "communication problems with embedded controller" and ec_intr=0 seemed to help somehow. But then, this was some kernel versions ago and i did not encounter it recently.
Signature · 7 lines
Stefan Seyfried \ "I didn't want to write for pay. I QA / R&D Team Mobile Devices \ wanted to be paid for what I write." SUSE LINUX Products GmbH, Nürnberg \ -- Leonard Cohen - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 11 lines · Stefan Seyfried
Quoted 10 lines · Pavel Machek
Hi!
x60 shut down after quite a while of uptime, in period of quite heavy load:
Sep 4 23:33:01 amd kernel: ACPI: Critical trip point Sep 4 23:33:01 amd kernel: Critical temperature reached (128 C), shutting down. Sep 4 23:33:01 amd shutdown[32585]: shutting down for system halt Sep 4 23:34:42 amd init: Switching to runlevel: 0
Quoted 4 lines
Quoted 2 lines
I do not think cpu reached 128C, as I still have my machine... Did anyone else see that?
my usual suspect: use ec_intr=0.
Is this a kernel command line parameter?
I'm having some suspend/resume related problems on HPC 6325 now, and they seem to be related to the embedded controller.
Greetings,
Rafael
Signature · 2 lines
You never change things by fighting the existing reality. R. Buckminster Fuller
Quoted 12 lines · Rafael J. Wysocki
Quoted 11 lines · Stefan Seyfried
Quoted 10 lines · Pavel Machek
Hi!
x60 shut down after quite a while of uptime, in period of quite heavy load:
Sep 4 23:33:01 amd kernel: ACPI: Critical trip point Sep 4 23:33:01 amd kernel: Critical temperature reached (128 C), shutting down. Sep 4 23:33:01 amd shutdown[32585]: shutting down for system halt Sep 4 23:34:42 amd init: Switching to runlevel: 0
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
I do not think cpu reached 128C, as I still have my machine... Did anyone else see that?
my usual suspect: use ec_intr=0.
Is this a kernel command line parameter?
yes.
seife@susi:~> dmesg | grep "^ACPI: EC"
ACPI: EC polling mode.
seife@susi:~> cat /proc/cmdline
root=/dev/hda5 vga=0x317 sysrq=yes resume=/dev/hda1 splash=silent showopts ec_intr=0
with ec_intr=1 (default), you'll get "ACPI: EC interrupt mode."
Quoted 2 lines
I'm having some suspend/resume related problems on HPC 6325 now, and they seem to be related to the embedded controller.
Well, polling mode is always on my "things to try"-list for those unspecified ACPI failures :-)
Signature · 7 lines
Stefan Seyfried QA / R&D Team Mobile Devices | "Any ideas, John?" SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out." - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html