From: Owl <owl@umail.ru>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] coretemp output changed after loading acpi_cpufreq
Date: Wed, 09 Feb 2011 14:04:57 +0000 [thread overview]
Message-ID: <4D529F09.9060200@umail.ru> (raw)
In-Reply-To: <4D526303.6060506@umail.ru>
09.02.2011 13:19, Jean Delvare пишет:
> On Wed, 09 Feb 2011 12:48:51 +0300, Owl wrote:
> > gentoo ~ # uname -a
> > Linux gentoo 2.6.36-gentoo-r7 #1 SMP Fri Jan 14 14:34:23 MSK 2011 i686
> > Intel(R) Atom(TM) CPU N550 @ 1.50GHz GenuineIntel GNU/Linux
> >
> > gentoo ~ # sensors
> > coretemp-isa-0000
> > Adapter: ISA adapter
> > Core 0: +18.0°C (crit = +100.0°C)
> >
> > coretemp-isa-0001
> > Adapter: ISA adapter
> > Core 1: +22.0°C (crit = +100.0°C)
> >
> > gentoo ~ # modprobe acpi_cpufreq
> > gentoo ~ # sensors
> > coretemp-isa-0000
> > Adapter: ISA adapter
> > Core 0: +37.0°C (crit = +100.0°C)
> >
> > coretemp-isa-0001
> > Adapter: ISA adapter
> > Core 1: +41.0°C (crit = +100.0°C)
> >
> > It's normal?
>
> Definitely not.
>
> > I think, second output is much closer to BIOS values.
>
> This reminds me of
> https://bugzilla.kernel.org/show_bug.cgi?id\x17291
>
> That case was a little different (problem was reportedly introduced by
> cpuidle drivers, rather than solved by cpufreq) but both share the fact
> that apparently digital thermal sensors in Intel CPUs are very
> sensitive to the CPU state. The root cause may be the same.
>
> Len, any idea how to investigate and hopefully fix this?
Additional info, maybe it help:
dmesg: http://codepad.org/2CXxLyLv
kernel config: http://codepad.org/vBsXFiXM
lsmod: http://codepad.org/NY7SixKo
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2011-02-09 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 9:48 [lm-sensors] coretemp output changed after loading acpi_cpufreq Owl
2011-02-09 10:19 ` Jean Delvare
2011-02-09 14:04 ` Owl [this message]
2011-02-09 16:06 ` Philip Pokorny
2011-02-09 17:12 ` Owl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D529F09.9060200@umail.ru \
--to=owl@umail.ru \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.