So it’s Friday and I’m working my way through writing a clients system monitoring and performance report and my bl**dy laptop keeps shutting down. Now it’s been doing this for a while and I thought nothing of it and blamed it on some cr*ppy software conflict until today.
During the latest shutdown I caught a glimpse of the words ‘critical’ and ‘temperature’, sure enough a ‘grep itical /var/log/syslog’ gives me:
Jul 6 12:39:16 mgr kernel: [ 9162.759875] ACPI: Critical trip point
Jul 6 12:39:16 mgr kernel: [ 9162.759910] Critical temperature reached (103 C), shutting down.
Jul 6 15:16:55 mgr kernel: [ 9365.281878] ACPI: Critical trip point
Jul 6 15:16:55 mgr kernel: [ 9365.281911] Critical temperature reached (103 C), shutting down.
Jul 6 16:02:47 mgr kernel: [ 2700.882027] ACPI: Critical trip point
Jul 6 16:02:47 mgr kernel: [ 2700.882062] Critical temperature reached (103 C), shutting down.
Fan-bl**dy-tastic, looks like the client report is going on ice along with my laptop. Now I know I’ve been busy, but I can hardly turn round to the client and tell them that working on their analysis and reporting has caused my laptop to go into a thermal or should that be thermite meltdown mode.
If anyone has any ideas how I can prevent my ageing, decrepit chassis (note: that’s the laptop chassis, not mine) from going into a terminal crash and burn, please let me know. I must be the only person I can think of who could possibly be looking for an ‘under-clockers’ forum to save my sorry skin from client wrath.
System monitoring – Munin – Critical temperature – Temperature Monitoring with Munin – now theres a thought. Well at least I’ve got some more content for the system monitoring section of the client’s report, happy days.