linux-kernel - Re: [lm-sensors] bad temperature values from w83781d in 2.6.22

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070809035642.GE3584@jupiter.solarsys.private>
Date:	Wed, 8 Aug 2007 23:56:42 -0400
From:	"Mark M. Hoffman" <mhoffman@...htlink.com>
To:	Joerg Sommrey <jo@...mrey.de>, LKML <linux-kernel@...r.kernel.org>,
	lm-sensors <lm-sensors@...sensors.org>
Subject: Re: [lm-sensors] bad temperature values from w83781d in 2.6.22

Hi Joerg:

* Joerg Sommrey <jo@...mrey.de> [2007-08-08 17:17:16 +0200]:
> Hi Mark,
> 
> just to eliminate as many impacts as possible, I did:
> - reinstall the unmodified sensors.conf from Tyan's support page
> - power off before rebooting
> 
> A call to "sensors -s" is done without errors in all cases.
> The module parameters I use currently with both kernels:
> 
> options w83781d force_w83782d=0,0x2d force_subclients=0,0x2d,0x48,0x49
> options w83627hf force_addr=0x0c00
> 
> When I first realized the problem, I didn't use w83627hf yet.  Results
> are the same when w83781d is used as driver for w83627hf.
> Parameters in that case just from Tyan:
> 
> options w83781d force_w83782d=0,0x2d force_subclients=0,0x2d,0x48,0x49 force_w83627hf=0,0x2c force_subclients=0,0x2c,0x4a,0x4b init=0
> 
> "My" i2cdump doesn't accept an -y option, maybe a Debianism.  Results
> see below.

Newer i2cdump skips the 5-second warning when given -y, that's all.

> ### 2.6.21 ###############################
> Script started on Wed Aug  8 16:53:10 2007
> bear:~/hwmon# i2cdump 0 0x2d b 0 0x4e

(snip tons of results)

Thanks for sending all that.  I see one bug clearly, and I'm pretty close to
seeing the other one.  But for tonight, I need sleep.

In the meantime, please try this command as root, against the newer kernel,
*after* you've done 'sensors -s':

	# i2cset -f 0 0x2d 0x5d 0x0e b

Wait > 2 seconds for the hardware to update itself, then run 'sensors' again.
I'm pretty sure you'll see the correct temps.

Regards,

-- 
Mark M. Hoffman
mhoffman@...htlink.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/