Bug#742512: linux: kernel 3.13 breaks fan cooling on HP 6830S laptop fine
reassign 742512 linux
retitle 742512 linux: kernel 3.13 breaks fan cooling on HP 6830S laptop
found 742512 linux/3.13.4-1
forwarded 742512 https://bugzilla.kernel.org/show_bug.cgi?id=717
thanks
On Fri, Mar 28, 2014 at 04:21:15PM +0100, MERLIN Philippe wrote:
> Le mardi 25 mars 2014, 23:55:44 Aurelien Jarno a écrit :
> > On Mon, Mar 24, 2014 at 05:30:56PM +0100, merlin wrote:
> > > Package: lm-sensors
> > > Version: 1:3.3.4-2
> > > Severity: important
> > >
> > > Dear Maintainer,
> > >
> > >
> > > When i move to linux 3.13-1 i remark that the fan of my computer HP
> > > 6830S
> > > work by in blow and when i observe the temperature given by sensors the
> > > temperature are very high so it's must be critical for the computer.
> >
> > > sensors :
> > lm-sensors doesn't control the fan, it only display the temperatures
> > returned by the sensors. Have you configured fancontrol to control the
> > fan or did you leave the BIOS of you computer handling that (which is
> > fine if it worked with 3.12)?
> Thanks for your answer.
> For the Bios i can't answer at your question, I do'nt see in the Bios HP
> anything about leaving kernel control the fan.
> fancontrol was never configured because pwmconfig does not work, so fancontrol
> is installed but not configured. At start there is a message saying that
> fancontrol is not started because not configured.
> I observe in 3.12 the fan works smoothly and in an continuous way, in 3.13 by
> in blow.
> in 3.12 the temp6 indicator given by sensors evolves during the session and
> the speed of the fan also.
> in 3.13 the temp6 indicator doe's not evolve during the session and kept the
> value of start low if the computer is cold and high if the computer is hot at
> start and then the fan works continuously.
> With these observation i think that the temp6 indicator is very important for
> the speed of the fan.
> Do you think i must remove fancontrol ?
If you don't use fancontrol and that just switch from kernel 3.12 to
3.13 causes this issue, it is definitely a kernel issue. It is very
likely to be the following upstream bug:
https://bugzilla.kernel.org/show_bug.cgi?id=71711
I am therefore reassigning the bug to the linux package.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: