I've tried ubuntu 11.04 beta 2 and have problem with my notebook (lenovo y560) being overheated. When I boot 10.10, /proc/acpi/fan is present, but when I boot 11.04 >>> ls /proc/acpi/ gives >>> ac_adapter battery button event wakeup From BootDmesg: [ 6.337757] ACPI: Invalid active0 threshold [ 6.343184] thermal LNXTHERM:00: registered as thermal_zone0 [ 6.343187] ACPI: Thermal Zone [TZ00] (79 C) Hello Complete log files available in the linked Launchpad report. Thanks Fabio
(In reply to comment #0) > I've tried ubuntu 11.04 beta 2 and have problem with my notebook (lenovo > y560) > being overheated. When I boot 10.10, /proc/acpi/fan is present, but when I > boot > 11.04 > >>> ls /proc/acpi/ > gives > >>> ac_adapter battery button event wakeup > please attach the output of "grep . /sys/class/thermal/*/*" in both 10.10 and 11.04 > > From BootDmesg: > > [ 6.337757] ACPI: Invalid active0 threshold > [ 6.343184] thermal LNXTHERM:00: registered as thermal_zone0 > [ 6.343187] ACPI: Thermal Zone [TZ00] (79 C) > can you see this message in 10.10?
> Name (_AC0, Zero) Indeed, the DSDT contains an invalid active trip point, which is a BIOS bug. The linux complaint is correct, indeed, we should really highlight it with [Firmware Bug]. The question is if Linux has somehow started to get confused by this, when it didn't in the past. > Name (_TC1, Zero) > Name (_TC2, Zero) > Name (_TSP, Zero) These suggest that this BIOS isn't fully baked -- is it a production level BIOS? Is there an update available? When /proc/acpi/fan was present, what was in it? Looking at the tables, it seems that it should be empty back when it existed, and we deleted it entirely in 2.6.38) and we deleted it entirely in 2.6.37) Can you describe the failure in more detail? What does it take to over-heat the laptop. Can you hear the fan spinning. Is the sound and the ability of the laptop to overheat changed if you boot the old kernel?
Created attachment 55572 [details] Result of rep . /sys/class/thermal/*/* in 10.10
Created attachment 55582 [details] Result of grep . /sys/class/thermal/*/* in 11.04
this doesn't seem to be an ACPI regression. how do you reproduce the overheating problem in 11.04? can you reproduce it in 10.10 in the same way? please attach the output of command "sensors“ in both 10.10 and 11.04
Created attachment 55642 [details] Output of sensors in 10.04
There is no "sensors" command in live cd of 11.04. Also I updated to the latest bios, and output of grep . /sys/class/thermal/*/* changed a little /sys/class/thermal/thermal_zone0/temp:71000 (was 73000) - how do you reproduce the overheating problem in 11.04? It just get overheated while working in normal way (testing unity, browsing, installing packages) - can you reproduce it in 10.10 in the same way? It never overheated in 10.10 (May be I should mentioned this earlier, I'm using linux mint 10, sorry for inconvenience).
Also /proc/acpi/fan is empty in 10.10. But ls /proc/acpi gives different results in 10.10 and 11.04 (see attachment).
Created attachment 55652 [details] ls /proc/acpi in 10.10
Created attachment 55662 [details] result of ls /proc/acpi in 11.04
Created attachment 55672 [details] Output of sensors in 11.04
I think this issue is resolved. I installed release of 11.04 and it works fine without overheating for about a day. I have a feeling, that the problem was somehow connected with opensource video drivers (but I'm not sure, may be bios update fixed it). Thanks.
okay. All the /proc/acpi/fan and /sys/class/thermal difference will not cause the overheating problem because they actually did not work in 10.10 neither. Bug closed as the problem doesn't exist in 11.04. Please feel free to re-open it if the problem can be reproduced again.
I think, There is some problem again I'm attaching output of dmesg and mcelog.
Created attachment 56322 [details] dmesg > dmesg.out
Created attachment 56332 [details] mcelog > mcelog.out
It's great that the kernel bugzilla is back. Can you please verify if the problem still exists in the latest upstream kernel?
bug closed as there is no response from the bug reporter. please feel free to reopen it if the problem still exists in the latest upstream kernel.