* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
@ 2014-02-11 9:54 ` Jürgen Fuchsberger
2014-02-11 19:24 ` Guenter Roeck
` (17 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Jürgen Fuchsberger @ 2014-02-11 9:54 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 3657 bytes --]
Hi,
On 02/11/2014 08:32 AM, Juerg Haefliger wrote:
> Hi Juergen,
>
> You're likely to get better help by contacting the LM sensors mailing
> list (cc'ed). I've been out of it for a bit.
Thanks!
>
>
>> Dear Juerg,
>>
>> I keep getting Errors of this kind:
>>
>> Feb 10 09:51:09 wegc203094 kernel: [ 156.372033] dme1737 1-002c: Read
>> from register 0x6d failed! Please report to the driver maintainer.
>> Feb 10 09:53:09 wegc203094 kernel: [ 276.472043] dme1737 1-002c: Read
>> from register 0x69 failed! Please report to the driver maintainer.
>
> Can you post all messages from the driver from the time it was loaded?
Feb 10 09:48:47 wegc203094 kernel: [ 8.368070] i2c i2c-1: Found a
DME1737 chip at 0x2c (rev 0x8a).
Feb 10 09:48:47 wegc203094 kernel: [ 8.384103] dme1737 1-002c:
Optional features: pwm3=no, pwm5=no, pwm6=no, fan3=no, fan4=no, fan5=no,
fan6=no.
Feb 10 09:4
> What's the model of the machine you're using?
Hmm, unfortunately I don't know. Is there a way to find out without
opening the server? (I mean by sw-tools?)
> What do you get when running the sensors-detect script?
~ % sensors
dme1737-i2c-1-2c
Adapter: SMBus nForce2 adapter at 2e00
5VSB: +1.41 V (min = +4.50 V, max = +5.50 V) ALARM
Vcore: +0.00 V (min = +0.00 V, max = +2.99 V) ALARM
+3.3V: +3.31 V (min = +2.97 V, max = +3.63 V)
+5V: +1.52 V (min = +4.50 V, max = +5.50 V) ALARM
+12V: +12.24 V (min = +10.81 V, max = +13.19 V)
3VSB: +3.31 V (min = +2.97 V, max = +3.63 V)
Vbat: +3.01 V (min = +2.70 V, max = +3.30 V)
fan1: 0 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
temp1: FAULT (low = -127.0°C, high = +127.0°C) ALARM
SIO Temp: +40.3°C (low = -127.0°C, high = +127.0°C)
temp3: FAULT (low = -127.0°C, high = +127.0°C) ALARM
cpu0_vid: +0.763 V
emc6d103-i2c-1-2d
Adapter: SMBus nForce2 adapter at 2e00
in0: +0.13 V (min = +0.00 V, max = +3.32 V)
Vcore: +0.17 V (min = +0.00 V, max = +2.99 V)
+3.3V: +3.29 V (min = +2.97 V, max = +3.63 V)
+5V: +5.09 V (min = +4.50 V, max = +5.50 V)
+12V: +12.15 V (min = +0.00 V, max = +15.94 V)
fan1: 0 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 13267 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
temp1: +39.1°C (low = -127.0°C, high = +127.0°C)
M/B Temp: +35.0°C (low = -127.0°C, high = +127.0°C)
temp3: +34.8°C (low = -127.0°C, high = +127.0°C)
cpu0_vid: +1.550 V
emc6d103-i2c-1-2e
Adapter: SMBus nForce2 adapter at 2e00
in0: +1.82 V (min = +0.00 V, max = +3.32 V)
Vcore: +1.06 V (min = +0.00 V, max = +2.99 V)
+3.3V: +3.29 V (min = +2.97 V, max = +3.63 V)
+5V: +5.09 V (min = +4.50 V, max = +6.64 V)
+12V: +12.11 V (min = +0.00 V, max = +15.94 V)
fan1: 0 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
temp1: +40.4°C (low = -127.0°C, high = +127.0°C)
M/B Temp: +35.6°C (low = -127.0°C, high = +127.0°C)
temp3: FAULT (low = -127.0°C, high = +127.0°C) ALARM
cpu0_vid: +1.550 V
Best,
Juergen
>>
>> uname -a
>> Linux wegc203094 3.2.0-4-686-pae #1 SMP Debian 3.2.54-2 i686 GNU/Linux
>>
>> Best,
>> Jürgen
>>
--
| Jürgen Fuchsberger, M.Sc.
| Wegener Center for Climate and Global Change
| University of Graz
| Brandhofgasse 5, A-8010 Graz, Austria
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
2014-02-11 9:54 ` Jürgen Fuchsberger
@ 2014-02-11 19:24 ` Guenter Roeck
2014-02-12 8:52 ` Jürgen Fuchsberger
` (16 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Guenter Roeck @ 2014-02-11 19:24 UTC (permalink / raw)
To: lm-sensors
On Tue, Feb 11, 2014 at 10:54:55AM +0100, Jürgen Fuchsberger wrote:
> Hi,
>
> On 02/11/2014 08:32 AM, Juerg Haefliger wrote:
> > Hi Juergen,
> >
> > You're likely to get better help by contacting the LM sensors mailing
> > list (cc'ed). I've been out of it for a bit.
>
> Thanks!
> >
> >
> >> Dear Juerg,
> >>
> >> I keep getting Errors of this kind:
> >>
> >> Feb 10 09:51:09 wegc203094 kernel: [ 156.372033] dme1737 1-002c: Read
> >> from register 0x6d failed! Please report to the driver maintainer.
> >> Feb 10 09:53:09 wegc203094 kernel: [ 276.472043] dme1737 1-002c: Read
> >> from register 0x69 failed! Please report to the driver maintainer.
> >
> > Can you post all messages from the driver from the time it was loaded?
>
> Feb 10 09:48:47 wegc203094 kernel: [ 8.368070] i2c i2c-1: Found a
> DME1737 chip at 0x2c (rev 0x8a).
> Feb 10 09:48:47 wegc203094 kernel: [ 8.384103] dme1737 1-002c:
> Optional features: pwm3=no, pwm5=no, pwm6=no, fan3=no, fan4=no, fan5=no,
> fan6=no.
> Feb 10 09:4
>
>
> > What's the model of the machine you're using?
> Hmm, unfortunately I don't know. Is there a way to find out without
> opening the server? (I mean by sw-tools?)
>
If this is a PC, "sudo dmidecode" might tell you a lot.
> > What do you get when running the sensors-detect script?
>
> ~ % sensors
>
>
sensors-detect, not sensors ;-).
Anyway, can you provide the output of "sudo i2cdump -y -f 1 0x2c" ?
That might actually help more.
Also, are the errors persistent or sporadic ?
Thanks,
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
2014-02-11 9:54 ` Jürgen Fuchsberger
2014-02-11 19:24 ` Guenter Roeck
@ 2014-02-12 8:52 ` Jürgen Fuchsberger
2014-02-12 9:37 ` Juerg Haefliger
` (15 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Jürgen Fuchsberger @ 2014-02-12 8:52 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1.1: Type: text/plain, Size: 2889 bytes --]
On 02/11/2014 08:24 PM, Guenter Roeck wrote:
> On Tue, Feb 11, 2014 at 10:54:55AM +0100, Jürgen Fuchsberger wrote:
>> Hi,
>>
>> On 02/11/2014 08:32 AM, Juerg Haefliger wrote:
>>> Hi Juergen,
>>>
>>> You're likely to get better help by contacting the LM sensors mailing
>>> list (cc'ed). I've been out of it for a bit.
>>
>> Thanks!
>>>
>>>
>>>> Dear Juerg,
>>>>
>>>> I keep getting Errors of this kind:
>>>>
>>>> Feb 10 09:51:09 wegc203094 kernel: [ 156.372033] dme1737 1-002c: Read
>>>> from register 0x6d failed! Please report to the driver maintainer.
>>>> Feb 10 09:53:09 wegc203094 kernel: [ 276.472043] dme1737 1-002c: Read
>>>> from register 0x69 failed! Please report to the driver maintainer.
>>>
>>> Can you post all messages from the driver from the time it was loaded?
>>
>> Feb 10 09:48:47 wegc203094 kernel: [ 8.368070] i2c i2c-1: Found a
>> DME1737 chip at 0x2c (rev 0x8a).
>> Feb 10 09:48:47 wegc203094 kernel: [ 8.384103] dme1737 1-002c:
>> Optional features: pwm3=no, pwm5=no, pwm6=no, fan3=no, fan4=no, fan5=no,
>> fan6=no.
>> Feb 10 09:4
>>
>>
>>> What's the model of the machine you're using?
>> Hmm, unfortunately I don't know. Is there a way to find out without
>> opening the server? (I mean by sw-tools?)
>>
> If this is a PC, "sudo dmidecode" might tell you a lot.
>
OK, thanks. Looks like it's a Tyan S2932/S2932-E/S2932-SI board. I
attached the dmidecode info.
>>> What do you get when running the sensors-detect script?
>>
>> ~ % sensors
>>
>>
> sensors-detect, not sensors ;-).
>
> Anyway, can you provide the output of "sudo i2cdump -y -f 1 0x2c" ?
> That might actually help more.
Debian package lm-sensors does not provide i2cdump so I did sensors-detect:
Driver `to-be-written':
* ISA bus, address 0xca8
Chip `IPMI BMC KCS' (confidence: 8)
Driver `dme1737':
* Bus `SMBus nForce2 adapter at 2e00'
Busdriver `i2c_nforce2', I2C address 0x2c
Chip `dme1737' (confidence: 6)
Driver `lm85':
* Bus `SMBus nForce2 adapter at 2e00'
Busdriver `i2c_nforce2', I2C address 0x2d
Chip `emc6d103' (confidence: 6)
* Bus `SMBus nForce2 adapter at 2e00'
Busdriver `i2c_nforce2', I2C address 0x2e
Chip `emc6d103' (confidence: 6)
Note: there is no driver for IPMI BMC KCS yet.
Check http://www.lm-sensors.org/wiki/Devices for updates.
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
dme1737
lm85
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
Do you want to add these lines automatically to /etc/modules? (yes/NO)
Unloading i2c-dev... OK
Unloading cpuid... OK
>
> Also, are the errors persistent or sporadic ?
>
Persistent, current messages contains 703 error lines.
Juergen.
[-- Attachment #1.1.2: dmidecode.txt --]
[-- Type: text/plain, Size: 19798 bytes --]
# dmidecode 2.11
SMBIOS 2.5 present.
62 structures occupying 2502 bytes.
Table at 0x000FC480.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 'V2.05 '
Release Date: 06/04/2009
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 1024 kB
Characteristics:
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
LS-120 boot is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Targeted content distribution is supported
BIOS Revision: 8.14
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: empty
Product Name: empty
Version: empty
Serial Number: empty
UUID: 00020003-0004-0005-0006-000700080009
Wake-up Type: Power Switch
SKU Number: empty
Family: empty
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: TYAN Computer Corporation
Product Name: S2932/S2932-E/S2932-SI
Version: empty
Serial Number: empty
Asset Tag: empty
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: empty
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
Handle 0x0003, DMI type 3, 21 bytes
Chassis Information
Manufacturer: empty
Type: Desktop
Lock: Not Present
Version: empty
Serial Number: empty
Asset Tag: empty
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0
Handle 0x0004, DMI type 4, 40 bytes
Processor Information
Socket Designation: CPU 1
Type: Central Processor
Family: Quad-Core Opteron
Manufacturer: AMD
ID: 23 0F 10 00 FF FB 8B 17
Signature: Family 16, Model 2, Stepping 3
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
HTT (Multi-threading)
Version: Quad-Core AMD Opteron(tm) Processor 2346 HE
Voltage: 1.5 V
External Clock: 200 MHz
Max Speed: 1800 MHz
Current Speed: 1800 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: 0x0005
L2 Cache Handle: 0x0006
L3 Cache Handle: 0x0007
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Core Count: 4
Core Enabled: 4
Characteristics:
64-bit capable
Handle 0x0005, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1-Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Varies With Memory Address
Location: Internal
Installed Size: 512 kB
Maximum Size: 512 kB
Supported SRAM Types:
Pipeline Burst
Installed SRAM Type: Pipeline Burst
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Data
Associativity: 4-way Set-associative
Handle 0x0006, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2-Cache
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Varies With Memory Address
Location: Internal
Installed Size: 2048 kB
Maximum Size: 2048 kB
Supported SRAM Types:
Pipeline Burst
Installed SRAM Type: Pipeline Burst
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 4-way Set-associative
Handle 0x0007, DMI type 7, 19 bytes
Cache Information
Socket Designation: L3-Cache
Configuration: Enabled, Not Socketed, Level 3
Operational Mode: Varies With Memory Address
Location: Internal
Installed Size: 2048 kB
Maximum Size: 2048 kB
Supported SRAM Types:
Pipeline Burst
Installed SRAM Type: Pipeline Burst
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 4-way Set-associative
Handle 0x0008, DMI type 4, 40 bytes
Processor Information
Socket Designation: CPU 2
Type: Central Processor
Family: Other
Manufacturer:
ID: 00 00 00 00 00 00 00 00
Version:
Voltage: 3.3 V 2.9 V
External Clock: Unknown
Max Speed: 2000 MHz
Current Speed: Unknown
Status: Unpopulated
Upgrade: ZIF Socket
L1 Cache Handle: 0x0009
L2 Cache Handle: 0x000A
L3 Cache Handle: 0x000B
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Characteristics: None
Handle 0x0009, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1-Cache
Configuration: Disabled, Not Socketed, Level 1
Operational Mode: Unknown
Location: Internal
Installed Size: 0 kB
Maximum Size: 0 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x000A, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2-Cache
Configuration: Disabled, Not Socketed, Level 2
Operational Mode: Unknown
Location: Internal
Installed Size: 0 kB
Maximum Size: 0 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x000B, DMI type 7, 19 bytes
Cache Information
Socket Designation: L3-Cache
Configuration: Disabled, Not Socketed, Level 3
Operational Mode: Unknown
Location: Internal
Installed Size: 0 kB
Maximum Size: 0 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: PS2Mouse
External Connector Type: PS/2
Port Type: Mouse Port
Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: PS/2
Port Type: Keyboard Port
Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2
Internal Connector Type: None
External Reference Designator: USB1
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2
Internal Connector Type: None
External Reference Designator: USB2
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J4A1
Internal Connector Type: None
External Reference Designator: LPT 1
External Connector Type: DB-25 male
Port Type: Parallel Port ECP/EPP
Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A1
Internal Connector Type: None
External Reference Designator: COM A
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6A1
Internal Connector Type: None
External Reference Designator: Audio Mic In
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6A1
Internal Connector Type: None
External Reference Designator: Audio Line In
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6B1 - AUX IN
Internal Connector Type: On Board Sound Input From CD-ROM
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Audio Port
Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6B2 - CDIN
Internal Connector Type: On Board Sound Input From CD-ROM
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Audio Port
Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6J2 - PRI IDE
Internal Connector Type: On Board IDE
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0017, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6J1 - SEC IDE
Internal Connector Type: On Board IDE
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0018, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J4J1 - FLOPPY
Internal Connector Type: On Board Floppy
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0019, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9H1 - FRONT PNL
Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1B1 - CHASSIS REAR FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2F1 - CPU FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J8B4 - FRONT FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9G2 - FNT USB
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6C3 - FP AUD
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x001F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9G1 - CONFIG
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0020, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J8C1 - SCSI LED
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0021, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9J2 - INTRUDER
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0022, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9G4 - ITP
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0023, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2H1 - MAIN POWER
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0024, DMI type 9, 13 bytes
System Slot Information
Designation: AGP
Type: 32-bit AGP 4x
Current Usage: In Use
Length: Short
ID: 0
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Handle 0x0025, DMI type 9, 13 bytes
System Slot Information
Designation: PCI1
Type: 32-bit PCI
Current Usage: Available
Length: Short
ID: 1
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Handle 0x0026, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Enabled
Description: To Be Filled By O.E.M.
Handle 0x0027, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Abbreviated
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x0028, DMI type 15, 55 bytes
System Event Log
Area Length: 1008 bytes
Header Start Offset: 0x1810
Data Start Offset: 0x1810
Access Method: General-purpose non-volatile data functions
Access Address: 0x0002
Status: Valid, Not Full
Change Token: 0x00000000
Header Format: No Header
Supported Log Type Descriptors: 9
Descriptor 1: Single-bit ECC memory error
Data Format 1: Multiple-event handle
Descriptor 2: Multi-bit ECC memory error
Data Format 2: Multiple-event handle
Descriptor 3: Parity memory error
Data Format 3: Multiple-event
Descriptor 4: I/O channel block
Data Format 4: Multiple-event
Descriptor 5: POST error
Data Format 5: POST results bitmap
Descriptor 6: PCI parity error
Data Format 6: Multiple-event handle
Descriptor 7: PCI system error
Data Format 7: Multiple-event handle
Descriptor 8: System limit exceeded
Data Format 8: Multiple-event system management
Descriptor 9: OEM-specific
Data Format 9: POST results bitmap
Handle 0x0029, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: Single-bit ECC
Maximum Capacity: 8 GB
Error Information Handle: Not Provided
Number Of Devices: 8
Handle 0x002A, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x00127FFFFFF
Range Size: 4736 MB
Physical Array Handle: 0x0029
Partition Width: 1
Handle 0x002B, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0029
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 72 bits
Size: 2048 MB
Form Factor: DIMM
Set: None
Locator: DIMM0
Bank Locator: BANK0
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Manufacturer: Manufacturer0
Serial Number: SerNum0
Asset Tag: AssetTagNum0
Part Number: PartNum0
Handle 0x002C, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x002B
Memory Array Mapped Address Handle: 0x002A
Partition Row Position: 1
Handle 0x002D, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0029
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 72 bits
Size: 2048 MB
Form Factor: DIMM
Set: None
Locator: DIMM1
Bank Locator: BANK1
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Manufacturer: Manufacturer1
Serial Number: SerNum1
Asset Tag: AssetTagNum1
Part Number: PartNum1
Handle 0x002E, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FFFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x002D
Memory Array Mapped Address Handle: 0x002A
Partition Row Position: 1
Handle 0x002F, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0029
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM2
Bank Locator: BANK2
Type: Unknown
Type Detail: Unknown
Speed: Unknown
Manufacturer: Manufacturer2
Serial Number: SerNum2
Asset Tag: AssetTagNum2
Part Number: PartNum2
Handle 0x0030, DMI type 126, 19 bytes
Inactive
Handle 0x0031, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0029
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM3
Bank Locator: BANK3
Type: Unknown
Type Detail: Unknown
Speed: Unknown
Manufacturer: Manufacturer3
Serial Number: SerNum3
Asset Tag: AssetTagNum3
Part Number: PartNum3
Handle 0x0032, DMI type 126, 19 bytes
Inactive
Handle 0x0033, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0029
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM4
Bank Locator: BANK4
Type: Unknown
Type Detail: Unknown
Speed: Unknown
Manufacturer: Manufacturer4
Serial Number: SerNum4
Asset Tag: AssetTagNum4
Part Number: PartNum4
Handle 0x0034, DMI type 126, 19 bytes
Inactive
Handle 0x0035, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0029
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM5
Bank Locator: BANK5
Type: Unknown
Type Detail: Unknown
Speed: Unknown
Manufacturer: Manufacturer5
Serial Number: SerNum5
Asset Tag: AssetTagNum5
Part Number: PartNum5
Handle 0x0036, DMI type 126, 19 bytes
Inactive
Handle 0x0037, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0029
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM6
Bank Locator: BANK6
Type: Unknown
Type Detail: Unknown
Speed: Unknown
Manufacturer: Manufacturer6
Serial Number: SerNum6
Asset Tag: AssetTagNum6
Part Number: PartNum6
Handle 0x0038, DMI type 126, 19 bytes
Inactive
Handle 0x0039, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0029
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM7
Bank Locator: BANK7
Type: Unknown
Type Detail: Unknown
Speed: Unknown
Manufacturer: Manufacturer7
Serial Number: SerNum7
Asset Tag: AssetTagNum7
Part Number: PartNum7
Handle 0x003A, DMI type 126, 19 bytes
Inactive
Handle 0x003B, DMI type 32, 20 bytes
System Boot Information
Status: No errors detected
Handle 0x003C, DMI type 38, 18 bytes
IPMI Device Information
Interface Type: KCS (Keyboard Control Style)
Specification Version: 2.0
I2C Slave Address: 0x10
NV Storage Device: Not Present
Base Address: 0x0000000000000CA8 (I/O)
Register Spacing: 32-bit Boundaries
Handle 0x003D, DMI type 127, 4 bytes
End Of Table
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (2 preceding siblings ...)
2014-02-12 8:52 ` Jürgen Fuchsberger
@ 2014-02-12 9:37 ` Juerg Haefliger
2014-02-12 10:10 ` Jürgen Fuchsberger
` (14 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Juerg Haefliger @ 2014-02-12 9:37 UTC (permalink / raw)
To: lm-sensors
On Wed, Feb 12, 2014 at 9:52 AM, Jürgen Fuchsberger <
juergen.fuchsberger@uni-graz.at> wrote:
>
>
>
> On 02/11/2014 08:24 PM, Guenter Roeck wrote:
> > On Tue, Feb 11, 2014 at 10:54:55AM +0100, Jürgen Fuchsberger wrote:
> >> Hi,
> >>
> >> On 02/11/2014 08:32 AM, Juerg Haefliger wrote:
> >>> Hi Juergen,
> >>>
> >>> You're likely to get better help by contacting the LM sensors mailing
> >>> list (cc'ed). I've been out of it for a bit.
> >>
> >> Thanks!
> >>>
> >>>
> >>>> Dear Juerg,
> >>>>
> >>>> I keep getting Errors of this kind:
> >>>>
> >>>> Feb 10 09:51:09 wegc203094 kernel: [ 156.372033] dme1737 1-002c:
Read
> >>>> from register 0x6d failed! Please report to the driver maintainer.
> >>>> Feb 10 09:53:09 wegc203094 kernel: [ 276.472043] dme1737 1-002c:
Read
> >>>> from register 0x69 failed! Please report to the driver maintainer.
> >>>
> >>> Can you post all messages from the driver from the time it was loaded?
> >>
> >> Feb 10 09:48:47 wegc203094 kernel: [ 8.368070] i2c i2c-1: Found a
> >> DME1737 chip at 0x2c (rev 0x8a).
> >> Feb 10 09:48:47 wegc203094 kernel: [ 8.384103] dme1737 1-002c:
> >> Optional features: pwm3=no, pwm5=no, pwm6=no, fan3=no, fan4=no,
fan5=no,
> >> fan6=no.
> >> Feb 10 09:4
> >>
> >>
> >>> What's the model of the machine you're using?
> >> Hmm, unfortunately I don't know. Is there a way to find out without
> >> opening the server? (I mean by sw-tools?)
> >>
> > If this is a PC, "sudo dmidecode" might tell you a lot.
> >
> OK, thanks. Looks like it's a Tyan S2932/S2932-E/S2932-SI board. I
> attached the dmidecode info.
>
> >>> What do you get when running the sensors-detect script?
> >>
> >> ~ % sensors
> >>
> >>
> > sensors-detect, not sensors ;-).
> >
> > Anyway, can you provide the output of "sudo i2cdump -y -f 1 0x2c" ?
> > That might actually help more.
>
> Debian package lm-sensors does not provide i2cdump so I did
sensors-detect:
i2cdump is provided by the i2c-tools package.
...Juerg
> Driver `to-be-written':
> * ISA bus, address 0xca8
> Chip `IPMI BMC KCS' (confidence: 8)
>
> Driver `dme1737':
> * Bus `SMBus nForce2 adapter at 2e00'
> Busdriver `i2c_nforce2', I2C address 0x2c
> Chip `dme1737' (confidence: 6)
>
> Driver `lm85':
> * Bus `SMBus nForce2 adapter at 2e00'
> Busdriver `i2c_nforce2', I2C address 0x2d
> Chip `emc6d103' (confidence: 6)
> * Bus `SMBus nForce2 adapter at 2e00'
> Busdriver `i2c_nforce2', I2C address 0x2e
> Chip `emc6d103' (confidence: 6)
>
> Note: there is no driver for IPMI BMC KCS yet.
> Check http://www.lm-sensors.org/wiki/Devices for updates.
>
> To load everything that is needed, add this to /etc/modules:
> #----cut here----
> # Chip drivers
> dme1737
> lm85
> #----cut here----
> If you have some drivers built into your kernel, the list above will
> contain too many modules. Skip the appropriate ones!
>
> Do you want to add these lines automatically to /etc/modules? (yes/NO)
>
> Unloading i2c-dev... OK
> Unloading cpuid... OK
>
>
>
> >
> > Also, are the errors persistent or sporadic ?
> >
> Persistent, current messages contains 703 error lines.
>
> Juergen.
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (3 preceding siblings ...)
2014-02-12 9:37 ` Juerg Haefliger
@ 2014-02-12 10:10 ` Jürgen Fuchsberger
2014-02-12 10:33 ` Juerg Haefliger
` (13 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Jürgen Fuchsberger @ 2014-02-12 10:10 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 3882 bytes --]
On 02/12/2014 10:37 AM, Juerg Haefliger wrote:
>
>
>
> On Wed, Feb 12, 2014 at 9:52 AM, Jürgen Fuchsberger
> <juergen.fuchsberger@uni-graz.at
> <mailto:juergen.fuchsberger@uni-graz.at>> wrote:
>>
>>
>>
>> On 02/11/2014 08:24 PM, Guenter Roeck wrote:
>> > On Tue, Feb 11, 2014 at 10:54:55AM +0100, Jürgen Fuchsberger wrote:
>> >> Hi,
>> >>
>> >> On 02/11/2014 08:32 AM, Juerg Haefliger wrote:
>> >>> Hi Juergen,
>> >>>
>> >>> You're likely to get better help by contacting the LM sensors mailing
>> >>> list (cc'ed). I've been out of it for a bit.
>> >>
>> >> Thanks!
>> >>>
>> >>>
>> >>>> Dear Juerg,
>> >>>>
>> >>>> I keep getting Errors of this kind:
>> >>>>
>> >>>> Feb 10 09:51:09 wegc203094 kernel: [ 156.372033] dme1737 1-002c:
> Read
>> >>>> from register 0x6d failed! Please report to the driver maintainer.
>> >>>> Feb 10 09:53:09 wegc203094 kernel: [ 276.472043] dme1737 1-002c:
> Read
>> >>>> from register 0x69 failed! Please report to the driver maintainer.
>> >>>
>> >>> Can you post all messages from the driver from the time it was loaded?
>> >>
>> >> Feb 10 09:48:47 wegc203094 kernel: [ 8.368070] i2c i2c-1: Found a
>> >> DME1737 chip at 0x2c (rev 0x8a).
>> >> Feb 10 09:48:47 wegc203094 kernel: [ 8.384103] dme1737 1-002c:
>> >> Optional features: pwm3=no, pwm5=no, pwm6=no, fan3=no, fan4=no,
> fan5=no,
>> >> fan6=no.
>> >> Feb 10 09:4
>> >>
>> >>
>> >>> What's the model of the machine you're using?
>> >> Hmm, unfortunately I don't know. Is there a way to find out without
>> >> opening the server? (I mean by sw-tools?)
>> >>
>> > If this is a PC, "sudo dmidecode" might tell you a lot.
>> >
>> OK, thanks. Looks like it's a Tyan S2932/S2932-E/S2932-SI board. I
>> attached the dmidecode info.
>>
>> >>> What do you get when running the sensors-detect script?
>> >>
>> >> ~ % sensors
>> >>
>> >>
>> > sensors-detect, not sensors ;-).
>> >
>> > Anyway, can you provide the output of "sudo i2cdump -y -f 1 0x2c" ?
>> > That might actually help more.
>>
>> Debian package lm-sensors does not provide i2cdump so I did
> sensors-detect:
>
> i2cdump is provided by the i2c-tools package.
>
ah, thanks.
Did not work:
sudo i2cdump -y -f 1 0x2c
No size specified (using byte-data access)
Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': No such file or
directory
Juergen.
>> Driver `to-be-written':
>> * ISA bus, address 0xca8
>> Chip `IPMI BMC KCS' (confidence: 8)
>>
>> Driver `dme1737':
>> * Bus `SMBus nForce2 adapter at 2e00'
>> Busdriver `i2c_nforce2', I2C address 0x2c
>> Chip `dme1737' (confidence: 6)
>>
>> Driver `lm85':
>> * Bus `SMBus nForce2 adapter at 2e00'
>> Busdriver `i2c_nforce2', I2C address 0x2d
>> Chip `emc6d103' (confidence: 6)
>> * Bus `SMBus nForce2 adapter at 2e00'
>> Busdriver `i2c_nforce2', I2C address 0x2e
>> Chip `emc6d103' (confidence: 6)
>>
>> Note: there is no driver for IPMI BMC KCS yet.
>> Check http://www.lm-sensors.org/wiki/Devices for updates.
>>
>> To load everything that is needed, add this to /etc/modules:
>> #----cut here----
>> # Chip drivers
>> dme1737
>> lm85
>> #----cut here----
>> If you have some drivers built into your kernel, the list above will
>> contain too many modules. Skip the appropriate ones!
>>
>> Do you want to add these lines automatically to /etc/modules? (yes/NO)
>>
>> Unloading i2c-dev... OK
>> Unloading cpuid... OK
>>
>>
>>
>> >
>> > Also, are the errors persistent or sporadic ?
>> >
>> Persistent, current messages contains 703 error lines.
>>
>> Juergen.
>>
--
| Jürgen Fuchsberger, M.Sc.
| Wegener Center for Climate and Global Change
| University of Graz
| Brandhofgasse 5, A-8010 Graz, Austria
| phone: +43-316-380-8438
| web: www.wegcenter.at/wegenernet
| www.wegenernet.org
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (4 preceding siblings ...)
2014-02-12 10:10 ` Jürgen Fuchsberger
@ 2014-02-12 10:33 ` Juerg Haefliger
2014-02-12 11:07 ` Jürgen Fuchsberger
` (12 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Juerg Haefliger @ 2014-02-12 10:33 UTC (permalink / raw)
To: lm-sensors
On Wed, Feb 12, 2014 at 11:10 AM, Jürgen Fuchsberger <
juergen.fuchsberger@uni-graz.at> wrote:
>
>
>
> On 02/12/2014 10:37 AM, Juerg Haefliger wrote:
> >
> >
> >
> > On Wed, Feb 12, 2014 at 9:52 AM, Jürgen Fuchsberger
> > <juergen.fuchsberger@uni-graz.at
> > <mailto:juergen.fuchsberger@uni-graz.at>> wrote:
> >>
> >>
> >>
> >> On 02/11/2014 08:24 PM, Guenter Roeck wrote:
> >> > On Tue, Feb 11, 2014 at 10:54:55AM +0100, Jürgen Fuchsberger wrote:
> >> >> Hi,
> >> >>
> >> >> On 02/11/2014 08:32 AM, Juerg Haefliger wrote:
> >> >>> Hi Juergen,
> >> >>>
> >> >>> You're likely to get better help by contacting the LM sensors
mailing
> >> >>> list (cc'ed). I've been out of it for a bit.
> >> >>
> >> >> Thanks!
> >> >>>
> >> >>>
> >> >>>> Dear Juerg,
> >> >>>>
> >> >>>> I keep getting Errors of this kind:
> >> >>>>
> >> >>>> Feb 10 09:51:09 wegc203094 kernel: [ 156.372033] dme1737 1-002c:
> > Read
> >> >>>> from register 0x6d failed! Please report to the driver maintainer.
> >> >>>> Feb 10 09:53:09 wegc203094 kernel: [ 276.472043] dme1737 1-002c:
> > Read
> >> >>>> from register 0x69 failed! Please report to the driver maintainer.
> >> >>>
> >> >>> Can you post all messages from the driver from the time it was
loaded?
> >> >>
> >> >> Feb 10 09:48:47 wegc203094 kernel: [ 8.368070] i2c i2c-1: Found a
> >> >> DME1737 chip at 0x2c (rev 0x8a).
> >> >> Feb 10 09:48:47 wegc203094 kernel: [ 8.384103] dme1737 1-002c:
> >> >> Optional features: pwm3=no, pwm5=no, pwm6=no, fan3=no, fan4=no,
> > fan5=no,
> >> >> fan6=no.
> >> >> Feb 10 09:4
> >> >>
> >> >>
> >> >>> What's the model of the machine you're using?
> >> >> Hmm, unfortunately I don't know. Is there a way to find out without
> >> >> opening the server? (I mean by sw-tools?)
> >> >>
> >> > If this is a PC, "sudo dmidecode" might tell you a lot.
> >> >
> >> OK, thanks. Looks like it's a Tyan S2932/S2932-E/S2932-SI board. I
> >> attached the dmidecode info.
> >>
> >> >>> What do you get when running the sensors-detect script?
> >> >>
> >> >> ~ % sensors
> >> >>
> >> >>
> >> > sensors-detect, not sensors ;-).
> >> >
> >> > Anyway, can you provide the output of "sudo i2cdump -y -f 1 0x2c" ?
> >> > That might actually help more.
> >>
> >> Debian package lm-sensors does not provide i2cdump so I did
> > sensors-detect:
> >
> > i2cdump is provided by the i2c-tools package.
> >
> ah, thanks.
>
> Did not work:
>
> sudo i2cdump -y -f 1 0x2c
> No size specified (using byte-data access)
> Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': No such file or
> directory
try:
sudo modprobe i2c-dev
> Juergen.
> >> Driver `to-be-written':
> >> * ISA bus, address 0xca8
> >> Chip `IPMI BMC KCS' (confidence: 8)
> >>
> >> Driver `dme1737':
> >> * Bus `SMBus nForce2 adapter at 2e00'
> >> Busdriver `i2c_nforce2', I2C address 0x2c
> >> Chip `dme1737' (confidence: 6)
> >>
> >> Driver `lm85':
> >> * Bus `SMBus nForce2 adapter at 2e00'
> >> Busdriver `i2c_nforce2', I2C address 0x2d
> >> Chip `emc6d103' (confidence: 6)
> >> * Bus `SMBus nForce2 adapter at 2e00'
> >> Busdriver `i2c_nforce2', I2C address 0x2e
> >> Chip `emc6d103' (confidence: 6)
> >>
> >> Note: there is no driver for IPMI BMC KCS yet.
> >> Check http://www.lm-sensors.org/wiki/Devices for updates.
> >>
> >> To load everything that is needed, add this to /etc/modules:
> >> #----cut here----
> >> # Chip drivers
> >> dme1737
> >> lm85
> >> #----cut here----
> >> If you have some drivers built into your kernel, the list above will
> >> contain too many modules. Skip the appropriate ones!
> >>
> >> Do you want to add these lines automatically to /etc/modules? (yes/NO)
> >>
> >> Unloading i2c-dev... OK
> >> Unloading cpuid... OK
> >>
> >>
> >>
> >> >
> >> > Also, are the errors persistent or sporadic ?
> >> >
> >> Persistent, current messages contains 703 error lines.
> >>
> >> Juergen.
> >>
>
> --
> | Jürgen Fuchsberger, M.Sc.
> | Wegener Center for Climate and Global Change
> | University of Graz
> | Brandhofgasse 5, A-8010 Graz, Austria
> | phone: +43-316-380-8438
> | web: www.wegcenter.at/wegenernet
> | www.wegenernet.org
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (5 preceding siblings ...)
2014-02-12 10:33 ` Juerg Haefliger
@ 2014-02-12 11:07 ` Jürgen Fuchsberger
2014-02-12 11:54 ` Guenter Roeck
` (11 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Jürgen Fuchsberger @ 2014-02-12 11:07 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1.1: Type: text/plain, Size: 4960 bytes --]
On 02/12/2014 11:33 AM, Juerg Haefliger wrote:
>
>
>
> On Wed, Feb 12, 2014 at 11:10 AM, Jürgen Fuchsberger
> <juergen.fuchsberger@uni-graz.at
> <mailto:juergen.fuchsberger@uni-graz.at>> wrote:
>>
>>
>>
>> On 02/12/2014 10:37 AM, Juerg Haefliger wrote:
>> >
>> >
>> >
>> > On Wed, Feb 12, 2014 at 9:52 AM, Jürgen Fuchsberger
>> > <juergen.fuchsberger@uni-graz.at
> <mailto:juergen.fuchsberger@uni-graz.at>
>> > <mailto:juergen.fuchsberger@uni-graz.at
> <mailto:juergen.fuchsberger@uni-graz.at>>> wrote:
>> >>
>> >>
>> >>
>> >> On 02/11/2014 08:24 PM, Guenter Roeck wrote:
>> >> > On Tue, Feb 11, 2014 at 10:54:55AM +0100, Jürgen Fuchsberger wrote:
>> >> >> Hi,
>> >> >>
>> >> >> On 02/11/2014 08:32 AM, Juerg Haefliger wrote:
>> >> >>> Hi Juergen,
>> >> >>>
>> >> >>> You're likely to get better help by contacting the LM sensors
> mailing
>> >> >>> list (cc'ed). I've been out of it for a bit.
>> >> >>
>> >> >> Thanks!
>> >> >>>
>> >> >>>
>> >> >>>> Dear Juerg,
>> >> >>>>
>> >> >>>> I keep getting Errors of this kind:
>> >> >>>>
>> >> >>>> Feb 10 09:51:09 wegc203094 kernel: [ 156.372033] dme1737 1-002c:
>> > Read
>> >> >>>> from register 0x6d failed! Please report to the driver maintainer.
>> >> >>>> Feb 10 09:53:09 wegc203094 kernel: [ 276.472043] dme1737 1-002c:
>> > Read
>> >> >>>> from register 0x69 failed! Please report to the driver maintainer.
>> >> >>>
>> >> >>> Can you post all messages from the driver from the time it was
> loaded?
>> >> >>
>> >> >> Feb 10 09:48:47 wegc203094 kernel: [ 8.368070] i2c i2c-1: Found a
>> >> >> DME1737 chip at 0x2c (rev 0x8a).
>> >> >> Feb 10 09:48:47 wegc203094 kernel: [ 8.384103] dme1737 1-002c:
>> >> >> Optional features: pwm3=no, pwm5=no, pwm6=no, fan3=no, fan4=no,
>> > fan5=no,
>> >> >> fan6=no.
>> >> >> Feb 10 09:4
>> >> >>
>> >> >>
>> >> >>> What's the model of the machine you're using?
>> >> >> Hmm, unfortunately I don't know. Is there a way to find out without
>> >> >> opening the server? (I mean by sw-tools?)
>> >> >>
>> >> > If this is a PC, "sudo dmidecode" might tell you a lot.
>> >> >
>> >> OK, thanks. Looks like it's a Tyan S2932/S2932-E/S2932-SI board. I
>> >> attached the dmidecode info.
>> >>
>> >> >>> What do you get when running the sensors-detect script?
>> >> >>
>> >> >> ~ % sensors
>> >> >>
>> >> >>
>> >> > sensors-detect, not sensors ;-).
>> >> >
>> >> > Anyway, can you provide the output of "sudo i2cdump -y -f 1 0x2c" ?
>> >> > That might actually help more.
>> >>
>> >> Debian package lm-sensors does not provide i2cdump so I did
>> > sensors-detect:
>> >
>> > i2cdump is provided by the i2c-tools package.
>> >
>> ah, thanks.
>>
>> Did not work:
>>
>> sudo i2cdump -y -f 1 0x2c
>> No size specified (using byte-data access)
>> Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': No such file or
>> directory
>
> try:
> sudo modprobe i2c-dev
>
now it worked (see attached file).
>
>> Juergen.
>> >> Driver `to-be-written':
>> >> * ISA bus, address 0xca8
>> >> Chip `IPMI BMC KCS' (confidence: 8)
>> >>
>> >> Driver `dme1737':
>> >> * Bus `SMBus nForce2 adapter at 2e00'
>> >> Busdriver `i2c_nforce2', I2C address 0x2c
>> >> Chip `dme1737' (confidence: 6)
>> >>
>> >> Driver `lm85':
>> >> * Bus `SMBus nForce2 adapter at 2e00'
>> >> Busdriver `i2c_nforce2', I2C address 0x2d
>> >> Chip `emc6d103' (confidence: 6)
>> >> * Bus `SMBus nForce2 adapter at 2e00'
>> >> Busdriver `i2c_nforce2', I2C address 0x2e
>> >> Chip `emc6d103' (confidence: 6)
>> >>
>> >> Note: there is no driver for IPMI BMC KCS yet.
>> >> Check http://www.lm-sensors.org/wiki/Devices for updates.
>> >>
>> >> To load everything that is needed, add this to /etc/modules:
>> >> #----cut here----
>> >> # Chip drivers
>> >> dme1737
>> >> lm85
>> >> #----cut here----
>> >> If you have some drivers built into your kernel, the list above will
>> >> contain too many modules. Skip the appropriate ones!
>> >>
>> >> Do you want to add these lines automatically to /etc/modules? (yes/NO)
>> >>
>> >> Unloading i2c-dev... OK
>> >> Unloading cpuid... OK
>> >>
>> >>
>> >>
>> >> >
>> >> > Also, are the errors persistent or sporadic ?
>> >> >
>> >> Persistent, current messages contains 703 error lines.
>> >>
>> >> Juergen.
>> >>
>>
>> --
>> | Jürgen Fuchsberger, M.Sc.
>> | Wegener Center for Climate and Global Change
>> | University of Graz
>> | Brandhofgasse 5, A-8010 Graz, Austria
>> | phone: +43-316-380-8438
>> | web: www.wegcenter.at/wegenernet <http://www.wegcenter.at/wegenernet>
>> | www.wegenernet.org <http://www.wegenernet.org>
>>
--
| Jürgen Fuchsberger, M.Sc.
| Wegener Center for Climate and Global Change
| University of Graz
| Brandhofgasse 5, A-8010 Graz, Austria
| phone: +43-316-380-8438
| web: www.wegcenter.at/wegenernet
| www.wegenernet.org
[-- Attachment #1.1.2: i2cdump.txt --]
[-- Type: text/plain, Size: 1241 bytes --]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
20: 36 00 c0 3a c4 80 27 80 ff ff ff ff ff ff ff ff 6.?:??'?........
30: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 5c 8a ..............\?
40: 0f db c0 20 ad d3 00 ff ad d3 ad d3 ad d3 81 7f ??? ??..????????
50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 cb ????........bbb?
60: cb cb e0 00 80 80 80 80 80 80 64 64 64 44 40 00 ???.??????dddD@.
70: ff ff ff 09 09 09 09 09 09 00 00 00 40 00 ec 10 ...??????...@.??
80: 7e a4 0e 00 d3 00 87 74 e0 00 4d 4d 0b 0b 0d 00 ~??.?.?t?.MM???.
90: 04 04 04 04 0c 0c 0c 5a f1 c0 af ad d3 9d c0 00 ???????Z???????.
a0: 00 00 0c 00 02 ff ff 0b 0b fe ff fe ff ff ff ff ..?.?..???.?....
b0: ff 00 00 00 00 00 28 28 0e 0e 0f 0f 00 00 00 00 ......((????....
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (6 preceding siblings ...)
2014-02-12 11:07 ` Jürgen Fuchsberger
@ 2014-02-12 11:54 ` Guenter Roeck
2014-02-12 12:05 ` Jean Delvare
` (10 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Guenter Roeck @ 2014-02-12 11:54 UTC (permalink / raw)
To: lm-sensors
T24gMDIvMTIvMjAxNCAwMzowNyBBTSwgSsO8cmdlbiBGdWNoc2JlcmdlciB3cm90ZToKPiBpMmNk
dW1wLnR4dAo+Cj4KPiAgICAgICAwICAxICAyICAzICA0ICA1ICA2ICA3ICA4ICA5ICBhICBiICBj
ICBkICBlICBmICAgIDAxMjM0NTY3ODlhYmNkZWYKPiAwMDogMDAgMDAgMDAgMDAgMDAgMDAgMDAg
MDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgICAgLi4uLi4uLi4uLi4uLi4uLgo+IDEwOiAwMCAw
MCAwMCAwMCAwMCAwMCAwMCAwMCAwMCAwMCAwMCAwMCAwMCAwMCAwMCAwMCAgICAuLi4uLi4uLi4u
Li4uLi4uCj4gMjA6IDM2IDAwIGMwIDNhIGM0IDgwIDI3IDgwIGZmIGZmIGZmIGZmIGZmIGZmIGZm
IGZmICAgIDYuPzo/Pyc/Li4uLi4uLi4KPiAzMDogZmYgZmYgZmYgMDAgMDAgMDAgMDAgMDAgMDAg
MDAgMDAgMDAgMDAgMDAgNWMgOGEgICAgLi4uLi4uLi4uLi4uLi5cPwo+IDQwOiAwZiBkYiBjMCAy
MCBhZCBkMyAwMCBmZiBhZCBkMyBhZCBkMyBhZCBkMyA4MSA3ZiAgICA/Pz8gPz8uLj8/Pz8/Pz8/
Cj4gNTA6IDgxIDdmIDgxIDdmIGZmIGZmIGZmIGZmIGZmIGZmIGZmIGZmIDYyIDYyIDYyIGNiICAg
ID8/Pz8uLi4uLi4uLmJiYj8KPiA2MDogY2IgY2IgZTAgMDAgODAgODAgODAgODAgODAgODAgNjQg
NjQgNjQgNDQgNDAgMDAgICAgPz8/Lj8/Pz8/P2RkZERALgo+IDcwOiBmZiBmZiBmZiAwOSAwOSAw
OSAwOSAwOSAwOSAwMCAwMCAwMCA0MCAwMCBlYyAxMCAgICAuLi4/Pz8/Pz8uLi5ALj8/Cj4gODA6
IDdlIGE0IDBlIDAwIGQzIDAwIDg3IDc0IGUwIDAwIDRkIDRkIDBiIDBiIDBkIDAwICAgIH4/Py4/
Lj90Py5NTT8/Py4KPiA5MDogMDQgMDQgMDQgMDQgMGMgMGMgMGMgNWEgZjEgYzAgYWYgYWQgZDMg
OWQgYzAgMDAgICAgPz8/Pz8/P1o/Pz8/Pz8/Lgo+IGEwOiAwMCAwMCAwYyAwMCAwMiBmZiBmZiAw
YiAwYiBmZSBmZiBmZSBmZiBmZiBmZiBmZiAgICAuLj8uPy4uPz8/Lj8uLi4uCj4gYjA6IGZmIDAw
IDAwIDAwIDAwIDAwIDI4IDI4IDBlIDBlIDBmIDBmIDAwIDAwIDAwIDAwICAgIC4uLi4uLigoPz8/
Py4uLi4KPiBjMDogMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAg
MDAgICAgLi4uLi4uLi4uLi4uLi4uLgo+IGQwOiAwMCAwMCAwMCAwMCAwMCAwMCAwMCAwMCAwMCAw
MCAwMCAwMCAwMCAwMCAwMCAwMCAgICAuLi4uLi4uLi4uLi4uLi4uCj4gZTA6IDAwIDAwIDAwIDAw
IDAwIDAwIDAwIDAwIDAwIDAwIDAwIDAwIDAwIDAwIDAwIDAwICAgIC4uLi4uLi4uLi4uLi4uLi4K
PiBmMDogMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgMDAgICAg
Li4uLi4uLi4uLi4uLi4uLgoKVGhhdCBsb29rcyBub3JtYWwgZm9yIHRoZSBjaGlwIGFzIGZhciBh
cyBJIGNhbiBzZWUsIGFuZCB0aGVyZSBhcmUKbm8gZXJyb3JzLgoKV29uZGVyIGlmIHRoZSBjaGlw
IG1heSBoYXZlIHRpbWluZyByZXN0cmljdGlvbnMgYW5kIG5vdCByZXNwb25kCnRvIHF1ZXJpZXMg
dW5kZXIgc29tZSBjaXJjdW1zdGFuY2VzIChlZyBpZiByZWdpc3RlcnMgYXJlIHJlYWQKdG9vIHF1
aWNrbHkgYmFjay10by1iYWNrKS4gVW5mb3J0dW5hdGVseSBJIGRvbid0IHNlZW0gdG8gYmUgYWJs
ZQp0byBmaW5kIGEgZGF0YXNoZWV0IGZvciBpdC4gRG9lcyBhbnlvbmUgaGF2ZSBvbmUsIGJ5IGFu
eSBjaGFuY2UgPwoKVGhhbmtzLApHdWVudGVyCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18KbG0tc2Vuc29ycyBtYWlsaW5nIGxpc3QKbG0tc2Vuc29yc0Bs
bS1zZW5zb3JzLm9yZwpodHRwOi8vbGlzdHMubG0tc2Vuc29ycy5vcmcvbWFpbG1hbi9saXN0aW5m
by9sbS1zZW5zb3Jz
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (7 preceding siblings ...)
2014-02-12 11:54 ` Guenter Roeck
@ 2014-02-12 12:05 ` Jean Delvare
2014-02-12 14:24 ` Guenter Roeck
` (9 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Jean Delvare @ 2014-02-12 12:05 UTC (permalink / raw)
To: lm-sensors
On Wed, 12 Feb 2014 03:54:44 -0800, Guenter Roeck wrote:
> On 02/12/2014 03:07 AM, Jürgen Fuchsberger wrote:
> > i2cdump.txt
> >
> >
> > 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
> > 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > 20: 36 00 c0 3a c4 80 27 80 ff ff ff ff ff ff ff ff 6.?:??'?........
> > 30: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 5c 8a ..............\?
> > 40: 0f db c0 20 ad d3 00 ff ad d3 ad d3 ad d3 81 7f ??? ??..????????
> > 50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 cb ????........bbb?
> > 60: cb cb e0 00 80 80 80 80 80 80 64 64 64 44 40 00 ???.??????dddD@.
> > 70: ff ff ff 09 09 09 09 09 09 00 00 00 40 00 ec 10 ...??????...@.??
> > 80: 7e a4 0e 00 d3 00 87 74 e0 00 4d 4d 0b 0b 0d 00 ~??.?.?t?.MM???.
> > 90: 04 04 04 04 0c 0c 0c 5a f1 c0 af ad d3 9d c0 00 ???????Z???????.
> > a0: 00 00 0c 00 02 ff ff 0b 0b fe ff fe ff ff ff ff ..?.?..???.?....
> > b0: ff 00 00 00 00 00 28 28 0e 0e 0f 0f 00 00 00 00 ......((????....
> > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>
> That looks normal for the chip as far as I can see, and there are
> no errors.
The board supports IPMI. I would guess that the errors happen when the
native driver and IPMI attempt to access the SMBus at the same time.
As usual, my recommendation is to either use IPMI or native drivers but
not mix.
> Wonder if the chip may have timing restrictions and not respond
> to queries under some circumstances (eg if registers are read
> too quickly back-to-back). Unfortunately I don't seem to be able
> to find a datasheet for it. Does anyone have one, by any chance ?
I do have it, and Juerg does as well, but at least I am not allowed to
share it. I'll be happy to answer any question though.
--
Jean Delvare
Suse L3 Support
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (8 preceding siblings ...)
2014-02-12 12:05 ` Jean Delvare
@ 2014-02-12 14:24 ` Guenter Roeck
2014-02-13 6:39 ` Jürgen Fuchsberger
` (8 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Guenter Roeck @ 2014-02-12 14:24 UTC (permalink / raw)
To: lm-sensors
On 02/12/2014 04:05 AM, Jean Delvare wrote:
> On Wed, 12 Feb 2014 03:54:44 -0800, Guenter Roeck wrote:
>> On 02/12/2014 03:07 AM, Jürgen Fuchsberger wrote:
>>> i2cdump.txt
>>>
>>>
>>> 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
>>> 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>> 20: 36 00 c0 3a c4 80 27 80 ff ff ff ff ff ff ff ff 6.?:??'?........
>>> 30: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 5c 8a ..............\?
>>> 40: 0f db c0 20 ad d3 00 ff ad d3 ad d3 ad d3 81 7f ??? ??..????????
>>> 50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 cb ????........bbb?
>>> 60: cb cb e0 00 80 80 80 80 80 80 64 64 64 44 40 00 ???.??????dddD@.
>>> 70: ff ff ff 09 09 09 09 09 09 00 00 00 40 00 ec 10 ...??????...@.??
>>> 80: 7e a4 0e 00 d3 00 87 74 e0 00 4d 4d 0b 0b 0d 00 ~??.?.?t?.MM???.
>>> 90: 04 04 04 04 0c 0c 0c 5a f1 c0 af ad d3 9d c0 00 ???????Z???????.
>>> a0: 00 00 0c 00 02 ff ff 0b 0b fe ff fe ff ff ff ff ..?.?..???.?....
>>> b0: ff 00 00 00 00 00 28 28 0e 0e 0f 0f 00 00 00 00 ......((????....
>>> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>
>> That looks normal for the chip as far as I can see, and there are
>> no errors.
>
> The board supports IPMI. I would guess that the errors happen when the
> native driver and IPMI attempt to access the SMBus at the same time.
>
Yes, that would explanin the problem.
> As usual, my recommendation is to either use IPMI or native drivers but
> not mix.
>
Agreed.
Guenter
>> Wonder if the chip may have timing restrictions and not respond
>> to queries under some circumstances (eg if registers are read
>> too quickly back-to-back). Unfortunately I don't seem to be able
>> to find a datasheet for it. Does anyone have one, by any chance ?
>
> I do have it, and Juerg does as well, but at least I am not allowed to
> share it. I'll be happy to answer any question though.
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (9 preceding siblings ...)
2014-02-12 14:24 ` Guenter Roeck
@ 2014-02-13 6:39 ` Jürgen Fuchsberger
2014-02-13 7:26 ` Guenter Roeck
` (7 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Jürgen Fuchsberger @ 2014-02-13 6:39 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 2037 bytes --]
On 02/12/2014 03:24 PM, Guenter Roeck wrote:
> On 02/12/2014 04:05 AM, Jean Delvare wrote:
>> On Wed, 12 Feb 2014 03:54:44 -0800, Guenter Roeck wrote:
>>> On 02/12/2014 03:07 AM, Jürgen Fuchsberger wrote:
>>>> i2cdump.txt
>>>>
>>>>
>>>> 0 1 2 3 4 5 6 7 8 9 a b c d e f
>>>> 0123456789abcdef
>>>> 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>> 20: 36 00 c0 3a c4 80 27 80 ff ff ff ff ff ff ff ff 6.?:??'?........
>>>> 30: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 5c 8a ..............\?
>>>> 40: 0f db c0 20 ad d3 00 ff ad d3 ad d3 ad d3 81 7f ??? ??..????????
>>>> 50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 cb ????........bbb?
>>>> 60: cb cb e0 00 80 80 80 80 80 80 64 64 64 44 40 00 ???.??????dddD@.
>>>> 70: ff ff ff 09 09 09 09 09 09 00 00 00 40 00 ec 10 ...??????...@.??
>>>> 80: 7e a4 0e 00 d3 00 87 74 e0 00 4d 4d 0b 0b 0d 00 ~??.?.?t?.MM???.
>>>> 90: 04 04 04 04 0c 0c 0c 5a f1 c0 af ad d3 9d c0 00 ???????Z???????.
>>>> a0: 00 00 0c 00 02 ff ff 0b 0b fe ff fe ff ff ff ff ..?.?..???.?....
>>>> b0: ff 00 00 00 00 00 28 28 0e 0e 0f 0f 00 00 00 00 ......((????....
>>>> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>
>>> That looks normal for the chip as far as I can see, and there are
>>> no errors.
>>
>> The board supports IPMI. I would guess that the errors happen when the
>> native driver and IPMI attempt to access the SMBus at the same time.
>>
> Yes, that would explanin the problem.
>
>> As usual, my recommendation is to either use IPMI or native drivers but
>> not mix.
>>
> Agreed.
>
OK, how can I choose which driver to use?
Juergen.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (10 preceding siblings ...)
2014-02-13 6:39 ` Jürgen Fuchsberger
@ 2014-02-13 7:26 ` Guenter Roeck
2014-02-13 7:32 ` Jean Delvare
` (6 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Guenter Roeck @ 2014-02-13 7:26 UTC (permalink / raw)
To: lm-sensors
On 02/12/2014 10:39 PM, Jürgen Fuchsberger wrote:
>
>
> On 02/12/2014 03:24 PM, Guenter Roeck wrote:
>> On 02/12/2014 04:05 AM, Jean Delvare wrote:
>>> On Wed, 12 Feb 2014 03:54:44 -0800, Guenter Roeck wrote:
>>>> On 02/12/2014 03:07 AM, Jürgen Fuchsberger wrote:
>>>>> i2cdump.txt
>>>>>
>>>>>
>>>>> 0 1 2 3 4 5 6 7 8 9 a b c d e f
>>>>> 0123456789abcdef
>>>>> 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>>> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>>> 20: 36 00 c0 3a c4 80 27 80 ff ff ff ff ff ff ff ff 6.?:??'?........
>>>>> 30: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 5c 8a ..............\?
>>>>> 40: 0f db c0 20 ad d3 00 ff ad d3 ad d3 ad d3 81 7f ??? ??..????????
>>>>> 50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 cb ????........bbb?
>>>>> 60: cb cb e0 00 80 80 80 80 80 80 64 64 64 44 40 00 ???.??????dddD@.
>>>>> 70: ff ff ff 09 09 09 09 09 09 00 00 00 40 00 ec 10 ...??????...@.??
>>>>> 80: 7e a4 0e 00 d3 00 87 74 e0 00 4d 4d 0b 0b 0d 00 ~??.?.?t?.MM???.
>>>>> 90: 04 04 04 04 0c 0c 0c 5a f1 c0 af ad d3 9d c0 00 ???????Z???????.
>>>>> a0: 00 00 0c 00 02 ff ff 0b 0b fe ff fe ff ff ff ff ..?.?..???.?....
>>>>> b0: ff 00 00 00 00 00 28 28 0e 0e 0f 0f 00 00 00 00 ......((????....
>>>>> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>>> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>>> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>>> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>>
>>>> That looks normal for the chip as far as I can see, and there are
>>>> no errors.
>>>
>>> The board supports IPMI. I would guess that the errors happen when the
>>> native driver and IPMI attempt to access the SMBus at the same time.
>>>
>> Yes, that would explanin the problem.
>>
>>> As usual, my recommendation is to either use IPMI or native drivers but
>>> not mix.
>>>
>> Agreed.
>>
> OK, how can I choose which driver to use?
>
Good question. Maybe Jean knows; I am just guessing.
Do you have any IPMI packages installed ?
Can you disable IPMI in the BIOS ?
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (11 preceding siblings ...)
2014-02-13 7:26 ` Guenter Roeck
@ 2014-02-13 7:32 ` Jean Delvare
2014-02-17 14:33 ` Jürgen Fuchsberger
` (5 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Jean Delvare @ 2014-02-13 7:32 UTC (permalink / raw)
To: lm-sensors
Hi Jürgen,
On Thu, 13 Feb 2014 07:39:04 +0100, Jürgen Fuchsberger wrote:
> >> The board supports IPMI. I would guess that the errors happen when the
> >> native driver and IPMI attempt to access the SMBus at the same time.
> >
> > Yes, that would explanin the problem.
>
> >> As usual, my recommendation is to either use IPMI or native drivers but
> >> not mix.
> >
> > Agreed.
>
> OK, how can I choose which driver to use?
In your case, the native drivers are i2c-nforce2, dme1737 and lm85, and
the native tool is "sensors". The IPMI driver would be ipmi-si if I
remember correctly, and its tool is "ipmitool" or equivalent (there are
several IPMI packages out there, I don't know which ones are available
to you.) If you have a BMC card in the machine, that card would be
accessing the monitoring chips over IPMI as well so it will happen even
without any driver loaded.
If you want to use IPMI (and if you have a BMC this is the only safe
option), blacklist i2c-nforce2 and delete your lm_sensors configuration
file (typically /etc/sysconfig/lm_sensors on a sysconfig-based system,
might be different on your distributions, e.g. on Debian you'd just
delete the relevant modules from /etc/modules.) Then load ipmi-si and
use ipmitool or whatever IPMI tool you have installed.
If you don't have a BMC and want to use native access, uninstall every
package related to IPMI, make sure no service related to IPMI is
started, and if there are still ipmi modules listed in "lsmod" after
thatn blacklist them. I am not too familiar with IPMI so I can't tell
more, sorry.
Another note as far as native access is concerned: Tyan offers a
configuration file for your board:
ftp://ftp.tyan.com/software/lms/2932.sensors.conf
A few things caught my eye:
* They mention the SMSC SCH5017, not DME1737. This points us to this
old support ticket:
http://www.lm-sensors.org/ticket/2265
Juerg, there was a question for you in that ticket, which was never
answered.
* They surprisingly do not configure the chip at I2C address 0x2c,
which is supposed to be the SMSC chip.
* They configure the chips at 0x2d and 0x2e as adm1027/lm85 but they
are now detected as emc6d103, which we properly support. The
configuration file would have to be adjusted to the proper chip names.
--
Jean Delvare
Suse L3 Support
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (12 preceding siblings ...)
2014-02-13 7:32 ` Jean Delvare
@ 2014-02-17 14:33 ` Jürgen Fuchsberger
2014-02-17 14:42 ` Juerg Haefliger
` (4 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Jürgen Fuchsberger @ 2014-02-17 14:33 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 1689 bytes --]
On 02/13/2014 08:32 AM, Jean Delvare wrote:
> Hi Jürgen,
>
> On Thu, 13 Feb 2014 07:39:04 +0100, Jürgen Fuchsberger wrote:
>>>> The board supports IPMI. I would guess that the errors happen when the
>>>> native driver and IPMI attempt to access the SMBus at the same time.
>>>
>>> Yes, that would explanin the problem.
>>
>>>> As usual, my recommendation is to either use IPMI or native drivers but
>>>> not mix.
>>>
>>> Agreed.
>>
>> OK, how can I choose which driver to use?
>
> In your case, the native drivers are i2c-nforce2, dme1737 and lm85, and
> the native tool is "sensors". The IPMI driver would be ipmi-si if I
> remember correctly, and its tool is "ipmitool" or equivalent (there are
> several IPMI packages out there, I don't know which ones are available
> to you.) If you have a BMC card in the machine, that card would be
> accessing the monitoring chips over IPMI as well so it will happen even
> without any driver loaded.
>
> If you want to use IPMI (and if you have a BMC this is the only safe
> option), blacklist i2c-nforce2 and delete your lm_sensors configuration
> file (typically /etc/sysconfig/lm_sensors on a sysconfig-based system,
> might be different on your distributions, e.g. on Debian you'd just
> delete the relevant modules from /etc/modules.) Then load ipmi-si and
> use ipmitool or whatever IPMI tool you have installed.
OK, where should I blacklist i2c-nforce2?
impitool does not work:
wegc203094:/etc# ipmitool sensor
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No
such file or directory
Get Device ID command failed
Unable to open SDR for reading
Best,
Juergen
>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (13 preceding siblings ...)
2014-02-17 14:33 ` Jürgen Fuchsberger
@ 2014-02-17 14:42 ` Juerg Haefliger
2014-02-17 14:49 ` Jürgen Fuchsberger
` (3 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Juerg Haefliger @ 2014-02-17 14:42 UTC (permalink / raw)
To: lm-sensors
On Mon, Feb 17, 2014 at 3:33 PM, Jürgen Fuchsberger <
juergen.fuchsberger@uni-graz.at> wrote:
>
>
>
> On 02/13/2014 08:32 AM, Jean Delvare wrote:
> > Hi Jürgen,
> >
> > On Thu, 13 Feb 2014 07:39:04 +0100, Jürgen Fuchsberger wrote:
> >>>> The board supports IPMI. I would guess that the errors happen when
the
> >>>> native driver and IPMI attempt to access the SMBus at the same time.
> >>>
> >>> Yes, that would explanin the problem.
> >>
> >>>> As usual, my recommendation is to either use IPMI or native drivers
but
> >>>> not mix.
> >>>
> >>> Agreed.
> >>
> >> OK, how can I choose which driver to use?
> >
> > In your case, the native drivers are i2c-nforce2, dme1737 and lm85, and
> > the native tool is "sensors". The IPMI driver would be ipmi-si if I
> > remember correctly, and its tool is "ipmitool" or equivalent (there are
> > several IPMI packages out there, I don't know which ones are available
> > to you.) If you have a BMC card in the machine, that card would be
> > accessing the monitoring chips over IPMI as well so it will happen even
> > without any driver loaded.
> >
> > If you want to use IPMI (and if you have a BMC this is the only safe
> > option), blacklist i2c-nforce2 and delete your lm_sensors configuration
> > file (typically /etc/sysconfig/lm_sensors on a sysconfig-based system,
> > might be different on your distributions, e.g. on Debian you'd just
> > delete the relevant modules from /etc/modules.) Then load ipmi-si and
> > use ipmitool or whatever IPMI tool you have installed.
>
> OK, where should I blacklist i2c-nforce2?
>
> impitool does not work:
> wegc203094:/etc# ipmitool sensor
> Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No
> such file or directory
Did you try to load the ipmi driver(s)? What do you get in the logs?
...Juerg
> Get Device ID command failed
> Unable to open SDR for reading
>
> Best,
> Juergen
>
> >
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (14 preceding siblings ...)
2014-02-17 14:42 ` Juerg Haefliger
@ 2014-02-17 14:49 ` Jürgen Fuchsberger
2014-02-17 15:55 ` Jean Delvare
` (2 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Jürgen Fuchsberger @ 2014-02-17 14:49 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 1520 bytes --]
On 02/17/2014 03:42 PM, Juerg Haefliger wrote:
>
> impitool does not work:
> wegc203094:/etc# ipmitool sensor
> Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No
> such file or directory
Did you try to load the ipmi driver(s)? What do you get in the logs?
>
Feb 17 11:05:51 wegc203094 kernel: [ 8.828554] ipmi message handler
version 39.2
Feb 17 11:05:51 wegc203094 kernel: [ 8.836419] IPMI System Interface
driver.
Feb 17 11:05:51 wegc203094 kernel: [ 8.836494] ipmi_si: probing via
SMBIOS
Feb 17 11:05:51 wegc203094 kernel: [ 8.836501] ipmi_si: SMBIOS: io
0xca8 regsize 1 spacing 4 irq 0
Feb 17 11:05:51 wegc203094 kernel: [ 8.836507] ipmi_si: Adding
SMBIOS-specified kcs state machine
Feb 17 11:05:51 wegc203094 kernel: [ 8.836517] ipmi_si: Trying
SMBIOS-specified kcs state machine at i/o address 0xca8, slave address
0x20, irq 0
Feb 17 11:05:51 wegc203094 kernel: [ 8.971823] ipmi_si ipmi_si.0:
Found new BMC (man_id: 0x0019fd, prod_id: 0x0b74, dev_id: 0x20)
Feb 17 11:05:51 wegc203094 kernel: [ 8.971845] ipmi_si ipmi_si.0:
IPMI kcs interface initialized
> ...Juerg
>
>
> > Get Device ID command failed
> > Unable to open SDR for reading
> >
> > Best,
> > Juergen
> >
> > >
> >
--
| Jürgen Fuchsberger, M.Sc.
| Wegener Center for Climate and Global Change
| University of Graz
| Brandhofgasse 5, A-8010 Graz, Austria
| phone: +43-316-380-8438
| web: www.wegcenter.at/wegenernet
| www.wegenernet.org
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (15 preceding siblings ...)
2014-02-17 14:49 ` Jürgen Fuchsberger
@ 2014-02-17 15:55 ` Jean Delvare
2014-02-18 7:25 ` Juerg Haefliger
2014-02-18 7:36 ` Jürgen Fuchsberger
18 siblings, 0 replies; 20+ messages in thread
From: Jean Delvare @ 2014-02-17 15:55 UTC (permalink / raw)
To: lm-sensors
Hallo Jürgen,
On Mon, 17 Feb 2014 15:33:18 +0100, Jürgen Fuchsberger wrote:
> On 02/13/2014 08:32 AM, Jean Delvare wrote:
> > In your case, the native drivers are i2c-nforce2, dme1737 and lm85, and
> > the native tool is "sensors". The IPMI driver would be ipmi-si if I
> > remember correctly, and its tool is "ipmitool" or equivalent (there are
> > several IPMI packages out there, I don't know which ones are available
> > to you.) If you have a BMC card in the machine, that card would be
> > accessing the monitoring chips over IPMI as well so it will happen even
> > without any driver loaded.
> >
> > If you want to use IPMI (and if you have a BMC this is the only safe
> > option), blacklist i2c-nforce2 and delete your lm_sensors configuration
> > file (typically /etc/sysconfig/lm_sensors on a sysconfig-based system,
> > might be different on your distributions, e.g. on Debian you'd just
> > delete the relevant modules from /etc/modules.) Then load ipmi-si and
> > use ipmitool or whatever IPMI tool you have installed.
>
> OK, where should I blacklist i2c-nforce2?
Add the following statement to any .conf file under /etc/modprobe.d:
blacklist i2c-nforce2
> impitool does not work:
> wegc203094:/etc# ipmitool sensor
> Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No
> such file or directory
> Get Device ID command failed
> Unable to open SDR for reading
I can't help with that, sorry, I don't know much about IPMI.
--
Jean Delvare
Suse L3 Support
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (16 preceding siblings ...)
2014-02-17 15:55 ` Jean Delvare
@ 2014-02-18 7:25 ` Juerg Haefliger
2014-02-18 7:36 ` Jürgen Fuchsberger
18 siblings, 0 replies; 20+ messages in thread
From: Juerg Haefliger @ 2014-02-18 7:25 UTC (permalink / raw)
To: lm-sensors
On Mon, Feb 17, 2014 at 4:55 PM, Jean Delvare <jdelvare@suse.de> wrote:
>
> Hallo Jürgen,
>
> On Mon, 17 Feb 2014 15:33:18 +0100, Jürgen Fuchsberger wrote:
> > On 02/13/2014 08:32 AM, Jean Delvare wrote:
> > > In your case, the native drivers are i2c-nforce2, dme1737 and lm85,
and
> > > the native tool is "sensors". The IPMI driver would be ipmi-si if I
> > > remember correctly, and its tool is "ipmitool" or equivalent (there
are
> > > several IPMI packages out there, I don't know which ones are available
> > > to you.) If you have a BMC card in the machine, that card would be
> > > accessing the monitoring chips over IPMI as well so it will happen
even
> > > without any driver loaded.
> > >
> > > If you want to use IPMI (and if you have a BMC this is the only safe
> > > option), blacklist i2c-nforce2 and delete your lm_sensors
configuration
> > > file (typically /etc/sysconfig/lm_sensors on a sysconfig-based system,
> > > might be different on your distributions, e.g. on Debian you'd just
> > > delete the relevant modules from /etc/modules.) Then load ipmi-si and
> > > use ipmitool or whatever IPMI tool you have installed.
> >
> > OK, where should I blacklist i2c-nforce2?
>
> Add the following statement to any .conf file under /etc/modprobe.d:
>
> blacklist i2c-nforce2
>
> > impitool does not work:
> > wegc203094:/etc# ipmitool sensor
> > Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No
> > such file or directory
> > Get Device ID command failed
> > Unable to open SDR for reading
$ modprobe ipmi_si
$ modprobe ipmi_devintf
> I can't help with that, sorry, I don't know much about IPMI.
> --
> Jean Delvare
> Suse L3 Support
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] Kernel errors for dme1737
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
` (17 preceding siblings ...)
2014-02-18 7:25 ` Juerg Haefliger
@ 2014-02-18 7:36 ` Jürgen Fuchsberger
18 siblings, 0 replies; 20+ messages in thread
From: Jürgen Fuchsberger @ 2014-02-18 7:36 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 2362 bytes --]
On 02/18/2014 08:25 AM, Juerg Haefliger wrote:
>
>
>
> On Mon, Feb 17, 2014 at 4:55 PM, Jean Delvare <jdelvare@suse.de
> <mailto:jdelvare@suse.de>> wrote:
>>
>> Hallo Jürgen,
>>
>> On Mon, 17 Feb 2014 15:33:18 +0100, Jürgen Fuchsberger wrote:
>> > On 02/13/2014 08:32 AM, Jean Delvare wrote:
>> > > In your case, the native drivers are i2c-nforce2, dme1737 and
> lm85, and
>> > > the native tool is "sensors". The IPMI driver would be ipmi-si if I
>> > > remember correctly, and its tool is "ipmitool" or equivalent
> (there are
>> > > several IPMI packages out there, I don't know which ones are available
>> > > to you.) If you have a BMC card in the machine, that card would be
>> > > accessing the monitoring chips over IPMI as well so it will happen
> even
>> > > without any driver loaded.
>> > >
>> > > If you want to use IPMI (and if you have a BMC this is the only safe
>> > > option), blacklist i2c-nforce2 and delete your lm_sensors
> configuration
>> > > file (typically /etc/sysconfig/lm_sensors on a sysconfig-based system,
>> > > might be different on your distributions, e.g. on Debian you'd just
>> > > delete the relevant modules from /etc/modules.) Then load ipmi-si and
>> > > use ipmitool or whatever IPMI tool you have installed.
>> >
>> > OK, where should I blacklist i2c-nforce2?
>>
>> Add the following statement to any .conf file under /etc/modprobe.d:
>>
>> blacklist i2c-nforce2
>>
>> > impitool does not work:
>> > wegc203094:/etc# ipmitool sensor
>> > Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No
>> > such file or directory
>> > Get Device ID command failed
>> > Unable to open SDR for reading
>
> $ modprobe ipmi_si
> $ modprobe ipmi_devintf
>
Thanks! This worked.
Juergen.
>> I can't help with that, sorry, I don't know much about IPMI.
>
>
>> --
>> Jean Delvare
>> Suse L3 Support
>>
>> _______________________________________________
>> lm-sensors mailing list
>> lm-sensors@lm-sensors.org <mailto:lm-sensors@lm-sensors.org>
>> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
--
| Jürgen Fuchsberger, M.Sc.
| Wegener Center for Climate and Global Change
| University of Graz
| Brandhofgasse 5, A-8010 Graz, Austria
| phone: +43-316-380-8438
| web: www.wegcenter.at/wegenernet
| www.wegenernet.org
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread