linux-kernel - Re: Dell Latitude E6440 & i8k

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>] [day] [month] [year] [list]

Date:	Sun, 18 May 2014 00:54:17 +0200
From:	Pali Rohár <pali.rohar@...il.com>
To:	Guenter Roeck <linux@...ck-us.net>, linux-kernel@...r.kernel.org
Subject: Re: Dell Latitude E6440 & i8k

On Friday 16 May 2014 21:11:17 you wrote:
> Hi Pali,
> 
> On Fri, 16 May 2014 20:37:41 +0200, Pali Rohár wrote:
> > Hello,
> > 
> > on Dell Latitude E6440 driver i8k reporting total nonsense
> > values
> 
> That's kind of excessive wording, the output isn't that bad.
> 
> > $ sensors
> > i8k-virtual-0
> > Adapter: Virtual device
> > Right Fan:   93450 RPM
> > CPU:          +57.0°C
> > temp2:        +57.0°C
> > temp3:        +40.0°C
> > temp4:       +127.0°C
> > 
> > Right Fan and temp4 are for sure incorrect.
> 
> Driver is reverse-engineered so this is best effort and some
> tweaking may be needed.
> 
> > Value temp4 is always 127 and is never changing, but value
> > for Right Fan is increasing when fan is more noisy. So it
> > looks like value for Right Fan is not correctly normalized
> > or multiplier is incorrect.
> > 
> > And name "Right" is incorrect too. Fan is on left side of
> > this notebook, not right as reported by driver.
> > 
> > It is possible to fix these problems?
> 
> Load the i8k driver with fan_mult=1.
> 
> Add the following to /etc/sensors.d/i8k.conf:
> 
> chip "i8k-virtual-0"
> 
>    label fan2 "Left Fan"
>    ignore temp4

I have some new info about temp4.

When I read value from temp4 for first time it reports (possible) 
correct value:

$ cat /sys/class/hwmon/hwmon2/temp4_input
49000

But every next call it returns 127000 which is incorrect.

So this looks like bug in BIOS or incorrect usage of SMM call...

Do you know if there is any way to extract BIOS SMM code? Or it 
is something which is not possible to do from OS/kernel side?

-- 
Pali Rohár
pali.rohar@...il.com

Download attachment "signature.asc " of type "application/pgp-signature" (199 bytes)