Comment 105 for bug 370173

Now I'm really angry. Yesterday my computer went shutdown because of overheating. I was running some virtual machine and after cooling down and starting it again, it didn't want to start againg, because filesystem in it is corrupted. I've lost many hours of work which can be fortunately done again.

I'm wondering why isn't this bug marked CRITICAL yet and why assigned team is Ubuntu Laptop Team. It seems they aren't active there so I suggest to change the team and marking it CRITICAL already!

Here you are my log when computer runs at 2 GHz/both cores:
------------------------------------------------------------------------
acpitz-virtual-0
Adapter: Virtual device
temp1: +65.0°C (crit = +256.0°C)
temp2: +64.0°C (crit = +108.0°C)
temp3: +51.0°C (crit = +105.0°C)
temp4: +36.1°C (crit = +108.0°C)
temp5: +80.0°C (crit = +110.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0: +66.0°C (high = +100.0°C, crit = +100.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +65.0°C (high = +100.0°C, crit = +100.0°C)
------------------------------------------------------------------------

Please compare it to my powersave states (above), pasted again:
------------------------------------------------------------------------
acpitz-virtual-0
Adapter: Virtual device
temp1: +50.0°C (crit = +256.0°C)
temp2: +48.0°C (crit = +108.0°C)
temp3: +47.0°C (crit = +105.0°C)
temp4: +34.5°C (crit = +108.0°C)
temp5: +50.0°C (crit = +110.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0: +49.0°C (high = +100.0°C, crit = +100.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +49.0°C (high = +100.0°C, crit = +100.0°C)
------------------------------------------------------------------------