Comment 79 for bug 22336

I have the same problem:

Laptop: IBM T41p
Ubuntu: Dapper works perfectly/Edgy gives Critical Temperature Reached messages in kern.log and halt with T ~= 94 C
Upgrade procedure from Dapper: /home kept, format and install of /
Good point: acpi kicks in and protect my hardware!
Bad point: CPU freq + throttling would be better.

Here are some infos about the system:

loa@cargo:~ $ cat /proc/acpi/thermal_zone/THM0/trip_points
critical (S5): 93 C
passive: 89 C: tc1=8 tc2=5 tsp=600 devices=0xdff4d338

loa@cargo:~ $ cat /proc/acpi/thermal_zone/THM0/polling_frequency
<polling disabled>

- This is strange, I echo 2 into it and got:

# echo 2 > /proc/acpi/thermal_zone/THM0/polling_frequency
# cat /proc/acpi/thermal_zone/THM0/polling_frequency
polling frequency: 2 seconds

# cat /proc/acpi/processor/CPU/info
processor id: 0
acpi id: 1
bus mastering control: yes
power management: yes
throttling control: yes
limit interface: yes

If I do a dmesg | grep -i acpi I have the following strange stuff:

 ACPI: Looking for DSDT ... not found!

So I suppose that the DSDT shipped with Edgy is broken but was ok with Dapper. Where is it possible to get the Dapper DSDT? I could test it and see if it is effectively the problem.

I am attaching the dmesg I have. My kernel etc... are all out of the box from Edgy.