Re: hwmon: (adm1021) Clarify documentation regarding Xeon processors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 04/10/2011 12:08 AM, Jean Delvare wrote:
> Hi Darren,
> 
> On Sat, 09 Apr 2011 16:15:45 -0700, Darren Hart wrote:
>> On 04/09/2011 01:39 PM, Guenter Roeck wrote:
>>> On Sat, Apr 09, 2011 at 12:31:56PM -0400, Jean Delvare wrote:
>>>> Recent Xeon processor thermal sensors are supported by the coretemp
>>>> driver and not the adm1021 driver. Only one old generation of Xeon
>>>> processors (the first Netburst ones) are supported by the adm1021
>>>> driver.
>>
>> In addition to changing the kernel config help, is there a way to avoid
>> loading this driver for non netburst type CPUs? Someway to blacklist
>> later CPUs from using this driver? Seems this would make sensors-detect
>> and such behave better.
> 
> This is all the other way around. The adm1021 driver doesn't auto-load
> on PC systems. The way it usually goes is that sensors-detect will
> detect a compatible device, and it will set the adm1021 driver to be
> loaded when the lm_sensors service is started. The adm1021 driver, in
> turn, tries to detect compatible devices, and bind to them if found.
> 
> So the problem boils down to two related issues:
> * The sensors-detect script seemingly misdetected a device on your
>   system.
> * The adm1021 got loaded and misdetected the same device.
> Which is expected as in general sensors-detect has the same detection
> code as hwmon drivers on the kernel side.
> 
> That being said, this can only be fixed if you provide the full output
> of sensors-detect on your system after unloading all hwmon drivers
> (stopping the lm_sensors service sometimes do, but not always, depends
> on the distribution) and a dump of the misdetected device. This will
> confirm the misdetection and hopefully offer a way to avoid it.

This system is really throwing me for a loop. After returning from ELC I
powered it back up and have been completely unable to get sensors to
read anything from w83795 or ipmi-si even. Running sensors-detect
(without any hwmon modules loaded) finds only ipmi-si and w83627ehf, but
sensors only reports on w83627ehf).

I have attached the typescript of the sensors-detect session, but it
isn't very interesting. If I stumble across another odd set modules
detected, I'll report back to the list.

/me scratches head...

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Attachment: typescript
Description: Binary data

_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux