On Sat, Jul 14, 2007 at 01:18:18AM +0200, JusTiCe8 wrote: > Package: lm-sensors > Version: 1:2.10.3-1+b1 > Severity: important > > *** Please type your report below this line *** > > After upgrading lm-sensors: > libsensors3 1:2.10.3-1 -> 1:2.10.3-1+b1 > lm-sensors 1:2.10.3-1 -> 1:2.10.3-1+b1 > sensord 1:2.10.3-1 -> 1:2.10.3-1+b1 > > sensors command is stuck (process status is D+) for more than one minute > and can't read w83782d chip data: > w83782d-i2c-0-2d > Adapter: SMBus AMD766 adapter at 80e0 > chs1 Fan: 0 RPM (min = 0 RPM, div = 128) > chs2 Fan: 0 RPM (min = 0 RPM, div = 128) > chs3 Fan: 0 RPM (min = 0 RPM, div = 128) (beep) > VRM2 Temp: -1°C (high = -1°C, hyst = -1°C) sensor = > transistor > CPU1 Temp: +0.0°C (high = +0°C, hyst = +0°C) sensor = > transistor > CPU0 Temp: +0.0°C (high = +0°C, hyst = +0°C) sensor = > transistor (beep) > alarms: > beep_enable: > Sound alarm enabled > > w83627hf-isa-0c00 > Adapter: ISA adapter > CPU1 Fan: 1360 RPM (min = 998 RPM, div = 8) > CPU2 Fan: 168750 RPM (min = 998 RPM, div = 8) > VRM1 Temp: +48°C (high = +50°C, hyst = +45°C) sensor = > transistor ALARM > AGP Temp: +54.0°C (high = +52°C, hyst = +47°C) sensor = > transistor ALARM > DDR Temp: +48.0°C (high = +52°C, hyst = +47°C) sensor = > transistor > vid: +1.650 V (VRM Version 9.0) > alarms: Chassis intrusion detection ALARM > beep_enable: > Sound alarm disabled > > > previous release was ok and work as expected. Nothing special show in > changelog. > The running kernel is the same, with same modules, as used with older > release before upgrade. >
Have you tried to downgrade to the old version to make sure the problem comes from there? There is no code change between the two versions, so I found the problem a bit strange. Also could you please try to run "strace sensors" to see where it hangs? -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `- people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
