From: Greg KH <greg@kroah.com>
To: Zack Winkles <winkie@linuxfromscratch.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: I2C sensors error (Re: 2.6.1-mm5)
Date: Tue, 20 Jan 2004 16:34:34 -0800 [thread overview]
Message-ID: <20040121003434.GC5472@kroah.com> (raw)
In-Reply-To: <20040120191040.2e1b46a9.winkie@linuxfromscratch.org>
On Tue, Jan 20, 2004 at 07:10:40PM -0500, Zack Winkles wrote:
> Yo,
>
> As usual, I've upgraded to the latest -mm, but to my dismay, my
> temperature sensors are no longer reporting sane values. For example,
> my motherboard usually reports about 31C, but now never moves up or down
> from 210C. My CPU, likewise, hovers at 210C, but sometimes moves up or
> down in what appears to be units of 11.
>
> I'm positive in the correctness of my /sys value parsing (latest gkrellm
> drop with lm_sensors values stuck in), so that's a non-issue. The
> modules I'm using are i2c_viapro and w83781d, and of course their
> dependencies. My logs report no errors from the kernel, or any user
> space apps/libs of relevance.
Please make sure you have the latest version of lmsensors. A few things
have changed in the latest i2c driver code that makes this necessary (we
don't initialize chips from the kernel anymore, which might be what you
are seeing.)
If that still doesn't work, please post this to the sensors mailing list
(address is in the MAINTAINERS file.)
thanks,
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2004-01-21 0:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 8:05 2.6.1-mm5 Andrew Morton
2004-01-20 10:51 ` 2.6.1-mm5 dies booting, possibly network related Helge Hafting
2004-01-20 11:14 ` 2.6.1-mm5 Christoph Hellwig
2004-01-20 16:37 ` 2.6.1-mm5 Andrew Morton
2004-01-20 11:35 ` 2.6.1-mm5 Christoph Hellwig
2004-01-20 13:45 ` [PATCH] missing space in printk message (was Re: 2.6.1-mm5) Sean Neakums
2004-01-20 13:54 ` Vojtech Pavlik
2004-01-20 14:09 ` Sean Neakums
2004-01-20 16:08 ` 2.6.1-mm5 (compile stats) John Cherry
2004-01-20 21:57 ` Adrian Bunk
2004-01-20 22:15 ` John Cherry
2004-01-20 22:27 ` Adrian Bunk
2004-01-20 22:50 ` John Cherry
2004-01-20 18:30 ` 2.6.1-mm5 Mike Fedyk
2004-01-20 18:36 ` 2.6.1-mm5 Andrew Morton
2004-01-21 0:10 ` I2C sensors error (Re: 2.6.1-mm5) Zack Winkles
2004-01-21 0:34 ` Greg KH [this message]
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=20040121003434.GC5472@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=winkie@linuxfromscratch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox