linux-kernel - Re: [lm-sensors] [PATCH] k10temp: temperature sensor for AMD Family 10h/11h CPUs

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]

Date:	Fri, 20 Nov 2009 11:44:50 +0100
From:	Jean Delvare <khali@...ux-fr.org>
To:	Serge Belyshev <belyshev@...ni.sinp.msu.ru>
Cc:	Clemens Ladisch <clemens@...isch.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, lm-sensors@...sensors.org
Subject: Re: [lm-sensors] [PATCH] k10temp: temperature sensor for AMD Family
  10h/11h CPUs

On Fri, 20 Nov 2009 10:22:50 +0000, Serge Belyshev wrote:
> 
> > +All these processors have a sensor, but on older revisions of Family 10h
> > +processors, the sensor returns inconsistent values (erratum 319). The driver
> > +refuses to load with these revisions (DR-BA, DR-B2, DR-B3: some Embedded
> > +Opterons on Socket F; and Quad-Core Opteron, Phenom Triple/Quad-Core, and
> > +Athon Dual-Core on Socket AM2+). All later revisions (RB-C2, BL-C2, DA-C2,
> > +RB-C3, HY-D0) work fine; see the list above.
> 
> Please note that erratum actually states that the sensor only "may report
> inconsistent values.", not that it is always broken.  As evident by my
> own experience (tested with a userspace application), it actually works
> perfectly on all B3 stepping processors that I have.

We don't care that 5% of the CPU have working sensors. 95% [1] of
theses CPUs have broken sensors and their users will ask us for help
and we are fed up with this. So all these CPUs are blacklisted, period.

> > +static bool __devinit has_erratum_319(void)
> > +{
> > +	/*
> > +	 * Erratum 319: The thermal sensor of older Family 10h processors
> > +	 *              (B steppings) is unreliable.
> > +	 */
> > +	return boot_cpu_data.x86 == 0x10 && boot_cpu_data.x86_model <= 2;
> > +}
> ...
> > +	if (has_erratum_319()) {
> > +		dev_err(&pdev->dev,
> > +			"unreliable CPU thermal sensor; monitoring disabled\n");
> > +		err = -ENODEV;
> > +		goto exit;
> > +	}
> 
> So, please provide an alternative for those who have a working sensor on a
> revision B processor and want to use it.

The alternative already exists: you can rebuild the driver yourself
without this check.

Or yet another alternative: become the maintainer of the hwmon
subsystem, and do lm-sensors user support for a couple years. Then you
will be allowed to decide what goes in.

And yet another one: instead of asking others to solve your very own
problem, why don't you try and solve it yourself? I'm sure Clemens
would welcome patches to his driver.

Thank you very much.

[1] Yes these numbers are totally made up. There is no reliable way to
tell a broken sensor from a working one anyway.

-- 
Jean Delvare
--
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/