Comment 32 for bug 114312

Hi Leann,

see comments inline:
On Friday 14 December 2007 22:12:17 Leann Ogasawara wrote:
> Hi Diego,
>
> Can you just clarify a few things for me. Are you experiencing this
> issue when you don't Suspend/Resume or only after you Suspend/Resume?
> Your original description doesn't mention anything about Suspend/Resume
> being related. If it is, can you update the description? This can be
> done be selecting the "Edit description/tags" link in the "Actions"
> section on the left side of this page.
Lets start by saying that I upgraded to 7.10 and 2.6.22-14-generic 64bit, so
everything I say is from memory. :)

In the kernels available in 7.04 (2.6.20-15), I could not suspend to ram at
all. However, when I suspended to disk, on I resume the fan control did not
work *at all* causing the computer to overheat.

> Regarding being able to test Suspend/Resume from the LiveCD, yes that is
> possible. Testing Hibernation from the LiveCD however is not possible.
The problem did not happen when I suspended to ram, since I was not able to
suspend to ram on that kernel. Is it possible to hibernate from a LiveCD
using an existsing swap parititon...? maybe that can help.

Just to keep you calm, on this kernel:
Linux pinky 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64
GNU/Linux

I can suspend to disk, and resume without any heat related problems. I can
also suspend to ram (with some limitations), which again do not cause any
heat related problems.

I managed to get *one* single time a problem with heat, which was caused by
the linux-sensors to get stuck at 70c, while the real temperare was low. This
caused the fan to work even when the machine was cold.

 A few other people claim that 2.6.22-14 on 7.10 fixes the heat/fan control
problem. There are some other known issues with this machine, which are all
documented here:
https://wiki.ubuntu.com/LaptopTestingTeam/Lenovo3000N100_0768

However, there is another person susbcribed to this bug which claims to have
this fan control problem even with 2.6.22-14. it is unknown why on his system
(same machine, same SW) he can reproduce the problem while others cannot.

> Also, regarding the status of this bug report. Please leave it as
> "Incomplete" against the 'linux' task. That indicates to us that we
> still need more information regarding this report. Ie. we still need
> feedback if the Hardy kernel resolves this issue or not. To learn more
> about bug report status please refer to:
> https://wiki.ubuntu.com/Bugs/Status . Once we gather the appropriate
> information, we'll be sure to update the Status/Importance accordingly
> and assign this the appropriate team. Thanks!
ok, I will do it. However, since most of the users susbcribed to this bug are
already running 7.10, as soon as 8.04 is out I will close, no matter what
(unsupported distro, and no users, hence invalid). I will not change it's
state to invalid until 8.04 is out or a verified fix exists, even tough that
page states that a bug with no additional information for 4 weeks needs to be
closed.

Thanks for your attention, even tough late (2 distros later...) you are
helping. Don't worry, we know you have a lot of work ;-)