[lm-sensors] sensors-detect hangs while scaning PIIX4

[lm-sensors] sensors-detect hangs while scaning PIIX4

[Peter Welzien]

Hello everyone. I'm having troubles getting lm_sensors to work. My dist is
Gentoo 2006.1, gentoo-kernel 2.6.18-r6, the motherboard is a Gigabyte
GA-6???? something. I can lookup the exact model if you like. lm_sensors
2.10.1

The problems is that the computer hangs if I run sensors-detect and select
to scan the SMBus PIIx4 adapter. It completly stops responding and I have
to reset it.

sensors-detect also reports:
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0xdf0e

If I load the it87 module the computer also hangs.

Below is the output from sensors-detect:

# sensors-detect revision 4171 (2006-09-24 03:37:01 -0700)

We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-piix4' for device 0000:00:0f.0: ServerWorks OSB4 South Bridge

We will now try to load each adapter module in turn.
Module `i2c-piix4' already loaded.

Next adapter: SMBus PIIX4 adapter at 0580
Do you want to scan it? (YES/no/selectively): n

Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM78-J' at 0x290...     No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No
Probing for `Winbond W83627HF' at 0x290...                  No
Probing for `Silicon Integrated Systems SIS5595'...         No
Probing for `VIA VT82C686 Integrated Sensors'...            No
Probing for `VIA VT8231 Integrated Sensors'...              No
Probing for `AMD K8 thermal sensors'...                     No
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0xdf0e
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'...                                      No
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No

Sorry, no sensors were detected.

lspci:

00:00.0 Host bridge: Broadcom CNB20LE Host Bridge (rev 06)
00:00.1 Host bridge: Broadcom CNB20LE Host Bridge (rev 06)
00:05.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg
NIC (rev 01)
00:07.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro
100] (rev 08)
00:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro
100] (rev 08)
00:09.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
00:0f.0 ISA bridge: Broadcom OSB4 South Bridge (rev 50)
00:0f.1 IDE interface: Broadcom OSB4 IDE Controller
00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 04)

Does anybody have an idea what might be wrong?

-- 
/Peter Welzien

[lm-sensors] sensors-detect hangs while scaning PIIX4

[Jean Delvare]

Hi Peter,

On Sat, 27 Jan 2007 20:49:13 +0100 (CET), Peter Welzien wrote:
> Hello everyone. I'm having troubles getting lm_sensors to work. My dist is
> Gentoo 2006.1, gentoo-kernel 2.6.18-r6, the motherboard is a Gigabyte
> GA-6???? something. I can lookup the exact model if you like. lm_sensors
> 2.10.1

Yes, please lookup the exact model.

> The problems is that the computer hangs if I run sensors-detect and select
> to scan the SMBus PIIx4 adapter. It completly stops responding and I have
> to reset it.
> 
> sensors-detect also reports:
> Trying family `ITE'...                                      Yes
> Found unknown chip with ID 0xdf0e

Strange, this really doesn't look like a regular ITE chip ID. Probably
a misdetection. Can you visually search for the Super-I/O chip on your
motherboard?

> 
> If I load the it87 module the computer also hangs.

In 2.6.18, the it87 driver does only probe one SMBus address (0x2d), I
guess this probing is hanging the computer just as sensors-detect.
Could be that you have a special chip at this address, or that just
sending anything on the SMBus locks it. Most probably, loading about
any i2c chip driver would lock the system too.

Whatever your Super-I/O chip is, it certainly isn't compatible with the
it87 driver anyway.

> 
> Below is the output from sensors-detect:
> 
> # sensors-detect revision 4171 (2006-09-24 03:37:01 -0700)
> 
> We can start with probing for (PCI) I2C or SMBus adapters.
> Do you want to probe now? (YES/no):
> Probing for PCI bus adapters...
> Use driver `i2c-piix4' for device 0000:00:0f.0: ServerWorks OSB4 South Bridge
> 
> We will now try to load each adapter module in turn.
> Module `i2c-piix4' already loaded.
> 
> Next adapter: SMBus PIIX4 adapter at 0580
> Do you want to scan it? (YES/no/selectively): n
> 
> Do you want to scan the ISA I/O ports? (YES/no):
> Probing for `National Semiconductor LM78' at 0x290...       No
> Probing for `National Semiconductor LM78-J' at 0x290...     No
> Probing for `National Semiconductor LM79' at 0x290...       No
> Probing for `Winbond W83781D' at 0x290...                   No
> Probing for `Winbond W83782D' at 0x290...                   No
> Probing for `Winbond W83627HF' at 0x290...                  No
> Probing for `Silicon Integrated Systems SIS5595'...         No
> Probing for `VIA VT82C686 Integrated Sensors'...            No
> Probing for `VIA VT8231 Integrated Sensors'...              No
> Probing for `AMD K8 thermal sensors'...                     No
> Probing for `IPMI BMC KCS' at 0xca0...                      No
> Probing for `IPMI BMC SMIC' at 0xca8...                     No
> 
> Do you want to scan for Super I/O sensors? (YES/no):
> Probing for Super-I/O at 0x2e/0x2f
> Trying family `ITE'...                                      Yes
> Found unknown chip with ID 0xdf0e
> Trying family `National Semiconductor'...                   No
> Trying family `SMSC'...                                     No
> Trying family `VIA/Winbond/Fintek'...                       No
> Probing for Super-I/O at 0x4e/0x4f
> Trying family `ITE'...                                      No
> Trying family `National Semiconductor'...                   No
> Trying family `SMSC'...                                     No
> Trying family `VIA/Winbond/Fintek'...                       No
> 
> Sorry, no sensors were detected.
> 
> lspci:
> 
> 00:00.0 Host bridge: Broadcom CNB20LE Host Bridge (rev 06)
> 00:00.1 Host bridge: Broadcom CNB20LE Host Bridge (rev 06)
> 00:05.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg
> NIC (rev 01)
> 00:07.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro
> 100] (rev 08)
> 00:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro
> 100] (rev 08)
> 00:09.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
> 00:0f.0 ISA bridge: Broadcom OSB4 South Bridge (rev 50)
> 00:0f.1 IDE interface: Broadcom OSB4 IDE Controller
> 00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 04)
> 
> Does anybody have an idea what might be wrong?

Just odd hardware, most probably.

First of all, do you have a reason to think that this motherboard has
hardware monitoring features? Do you see them in the BIOS or using a
different OS? It seems to be a rather old model, it wouldn't be all
that surprising that it simply doesn't support hardware monitoring.

Try using i2cdetect to scan the SMBus. If even that locks the bus, it's
probably the SMBus itself which doesn't work. Did you pass specific
parameters to the i2c-piix4 driver? Are there messages in the logs when
the i2c-piix4 driver is loaded?

You should look for BIOS updates, too.

-- 
Jean Delvare

[lm-sensors] sensors-detect hangs while scaning PIIX4

[Peter Welzien]

Since my last message doesn't seem to have reached the list, I send
another one.

> Yes, please lookup the exact model.

It's a Gigabyte GA-6ETXDR.

> Strange, this really doesn't look like a regular ITE chip ID. Probably
> a misdetection. Can you visually search for the Super-I/O chip on your
> motherboard?

Gigabyte says on their homepage
(http://www.gigabyte.com.tw/Products/Networking/Products_Spec.aspx?ProductID™2)
that the Super I/O chip is a NS97317. On the chip itself is printed
PC97317 and some other text. Let me know if you also need the rest of the
text.

> First of all, do you have a reason to think that this motherboard has
> hardware monitoring features? Do you see them in the BIOS or using a
> different OS? It seems to be a rather old model, it wouldn't be all
> that surprising that it simply doesn't support hardware monitoring.

I can get the temperature of both CPUs as well as fan speeds in the BIOS.

> Try using i2cdetect to scan the SMBus. If even that locks the bus, it's
> probably the SMBus itself which doesn't work. Did you pass specific
> parameters to the i2c-piix4 driver? Are there messages in the logs when
> the i2c-piix4 driver is loaded?

I didn't pass any parameters to the module. When it loads the only message
in the log is a line saying that the module is loaded and an address. I
don't have access to the computer right now, but I can get the exact
message tonight if you need it.

-- 
/Peter Welzien

[lm-sensors] sensors-detect hangs while scaning PIIX4

[Jean Delvare]

Hi Peter,

On Mon, 29 Jan 2007 11:28:52 +0100 (CET), Peter Welzien wrote:
> Since my last message doesn't seem to have reached the list, I send
> another one.

Yeah, that's what happens when you reply to me only ;)

> > Yes, please lookup the exact model.
> 
> It's a Gigabyte GA-6ETXDR.
> 
> > Strange, this really doesn't look like a regular ITE chip ID. Probably
> > a misdetection. Can you visually search for the Super-I/O chip on your
> > motherboard?
> 
> Gigabyte says on their homepage
> (http://www.gigabyte.com.tw/Products/Networking/Products_Spec.aspx?ProductID™2)
> that the Super I/O chip is a NS97317. On the chip itself is printed
> PC97317 and some other text. Let me know if you also need the rest of the
> text.

This chip doesn't embed hardware monitoring features. This was already
discussed on the list:
  http://lists.lm-sensors.org/pipermail/lm-sensors/2003-March/002059.html
I checked the datasheet once again and indeed there is no mention of
any kind of voltage, temperature or fan speed monitoring.

> > First of all, do you have a reason to think that this motherboard has
> > hardware monitoring features? Do you see them in the BIOS or using a
> > different OS? It seems to be a rather old model, it wouldn't be all
> > that surprising that it simply doesn't support hardware monitoring.
> 
> I can get the temperature of both CPUs as well as fan speeds in the BIOS.

OK, so the board must have a hardware monitoring chip. Maybe on the
SMBus which you can't get to work at the moment.

> > Try using i2cdetect to scan the SMBus. If even that locks the bus, it's
> > probably the SMBus itself which doesn't work. Did you pass specific
> > parameters to the i2c-piix4 driver? Are there messages in the logs when
> > the i2c-piix4 driver is loaded?
> 
> I didn't pass any parameters to the module. When it loads the only message
> in the log is a line saying that the module is loaded and an address. I
> don't have access to the computer right now, but I can get the exact
> message tonight if you need it.

It might help, yes. Please make sure there is no complaint about an
"illegal interrupt configuration". Please also provide a dump of the
PCI config registers of the device. You can obtain such a dump using
"lspci -xxx".

Then we need to figure out what exactly is locking your system. As I
asked before, please try i2cdetect on the SMBus (typically "i2cdetect
0") and see if it locks too. You may additionally try "i2cdetect -r 0"
and "i2cdetect -q 0". If these commands lock your system, note how much
is written on your screen each time before the system locks.

-- 
Jean Delvare

[lm-sensors] sensors-detect hangs while scaning PIIX4

[Peter Welzien]

>> Since my last message doesn't seem to have reached the list, I send
>> another one.

> Yeah, that's what happens when you reply to me only ;)

I'm sorry about that. I didn't notice that the reply-to wasn't set to the
list.

>> I didn't pass any parameters to the module. When it loads the only
>> message in the log is a line saying that the module is loaded and an
>> address. I don't have access to the computer right now, but I can get
>> the exact message tonight if you need it.

> It might help, yes. Please make sure there is no complaint about an
> "illegal interrupt configuration". Please also provide a dump of the
> PCI config registers of the device. You can obtain such a dump using
> "lspci -xxx".

dmesg says:
piix4_smbus 0000:00:0f.0: Found 0000:00:0f.0 device

lspci -xxx:
00:00.0 Host bridge: Broadcom CNB20LE Host Bridge (rev 06)
00: 66 11 09 00 06 01 00 62 06 00 00 06 08 40 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 04 06 80 14 00 eb 00 00 00 4b
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 80 2a 00 af c0 0f ff 1f 01 1e 81 00 44 44 44 44
80: 00 20 00 00 20 40 00 00 40 60 00 00 60 80 00 00
90: 55 0a 29 10 0d 4f fe 44 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: fb e6 dc 6f fe ac 1b be b8 7d fb ff ff fd f3 ff
c0: 20 fc af fe 00 fc 0f fc 00 04 00 00 0d 07 00 48
d0: 00 b0 fc df 00 10 00 00 00 00 00 00 01 80 10 93
e0: 04 00 00 2b 00 00 00 00 b2 00 00 00 00 00 00 00
f0: 00 00 00 40 00 00 00 00 00 00 00 00 60 01 00 00

00:00.1 Host bridge: Broadcom CNB20LE Host Bridge (rev 06)
00: 66 11 09 00 07 00 00 02 06 00 00 06 08 10 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 01 01 04 00 00 00 00 0b 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: b0 fe bf fe 10 fc 1f fc 00 00 00 00 0d 07 00 00
d0: 00 e0 fc ef 00 00 00 00 00 00 00 00 01 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 08 00 00 00 00 00 00 00 00 61 01 00 00

00:0f.0 ISA bridge: Broadcom OSB4 South Bridge (rev 50)
00: 66 11 00 02 07 00 00 02 50 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 66 11 00 02
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: f0 33 00 00 00 00 00 00 07 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 01 00 00 00 0f c1 20 00 00 00 00 00 00 00 00 00
70: 01 40 08 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 81 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 01 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

(I've deleted the NICs, graphics card, IDE and USB-bus)

> Then we need to figure out what exactly is locking your system. As I
> asked before, please try i2cdetect on the SMBus (typically "i2cdetect
> 0") and see if it locks too. You may additionally try "i2cdetect -r 0"
> and "i2cdetect -q 0". If these commands lock your system, note how much
> is written on your screen each time before the system locks.

i2cdetect 0:
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/0.
I will probe address range 0x03-0x77.
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
[locks up]

i2cdetect -r 0:
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/0 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
[locks up]

i2cdetect -q 0:
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/0 using quick write commands.
I will probe address range 0x03-0x77.
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
[locks up]

I did also try i2cdetect -l with following result:
i2c-0   smbus           SMBus PIIX4 adapter at 0580             Non-I2C
SMBus adapter

-- 
/Peter Welzien

[lm-sensors] sensors-detect hangs while scaning PIIX4

[Peter Welzien]

>>> Since my last message doesn't seem to have reached the list, I send
>>> another one.
>
>> Yeah, that's what happens when you reply to me only ;)
>
> I'm sorry about that. I didn't notice that the reply-to wasn't set to the
> list.
>
>>> I didn't pass any parameters to the module. When it loads the only
>>> message in the log is a line saying that the module is loaded and an
>>> address. I don't have access to the computer right now, but I can get
>>> the exact message tonight if you need it.
>
>> It might help, yes. Please make sure there is no complaint about an
>> "illegal interrupt configuration". Please also provide a dump of the
>> PCI config registers of the device. You can obtain such a dump using
>> "lspci -xxx".
>
> dmesg says:
> piix4_smbus 0000:00:0f.0: Found 0000:00:0f.0 device
>
> lspci -xxx:
> 00:00.0 Host bridge: Broadcom CNB20LE Host Bridge (rev 06)
> 00: 66 11 09 00 06 01 00 62 06 00 00 06 08 40 80 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 00 00 00 00 00 00 04 06 80 14 00 eb 00 00 00 4b
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 80 2a 00 af c0 0f ff 1f 01 1e 81 00 44 44 44 44
> 80: 00 20 00 00 20 40 00 00 40 60 00 00 60 80 00 00
> 90: 55 0a 29 10 0d 4f fe 44 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: fb e6 dc 6f fe ac 1b be b8 7d fb ff ff fd f3 ff
> c0: 20 fc af fe 00 fc 0f fc 00 04 00 00 0d 07 00 48
> d0: 00 b0 fc df 00 10 00 00 00 00 00 00 01 80 10 93
> e0: 04 00 00 2b 00 00 00 00 b2 00 00 00 00 00 00 00
> f0: 00 00 00 40 00 00 00 00 00 00 00 00 60 01 00 00
>
> 00:00.1 Host bridge: Broadcom CNB20LE Host Bridge (rev 06)
> 00: 66 11 09 00 07 00 00 02 06 00 00 06 08 10 80 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 00 00 00 00 01 01 04 00 00 00 00 0b 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: b0 fe bf fe 10 fc 1f fc 00 00 00 00 0d 07 00 00
> d0: 00 e0 fc ef 00 00 00 00 00 00 00 00 01 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 08 00 00 00 00 00 00 00 00 61 01 00 00
>
> 00:0f.0 ISA bridge: Broadcom OSB4 South Bridge (rev 50)
> 00: 66 11 00 02 07 00 00 02 50 00 01 06 00 00 80 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 66 11 00 02
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: f0 33 00 00 00 00 00 00 07 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 01 00 00 00 0f c1 20 00 00 00 00 00 00 00 00 00
> 70: 01 40 08 00 00 00 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 81 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 01 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
>
> (I've deleted the NICs, graphics card, IDE and USB-bus)
>
>> Then we need to figure out what exactly is locking your system. As I
>> asked before, please try i2cdetect on the SMBus (typically "i2cdetect
>> 0") and see if it locks too. You may additionally try "i2cdetect -r 0"
>> and "i2cdetect -q 0". If these commands lock your system, note how much
>> is written on your screen each time before the system locks.
>
> i2cdetect 0:
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c/0.
> I will probe address range 0x03-0x77.
> Continue? [Y/n]
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> [locks up]
>
> i2cdetect -r 0:
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c/0 using read byte commands.
> I will probe address range 0x03-0x77.
> Continue? [Y/n]
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> [locks up]
>
> i2cdetect -q 0:
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c/0 using quick write commands.
> I will probe address range 0x03-0x77.
> Continue? [Y/n]
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> [locks up]
>
> I did also try i2cdetect -l with following result:
> i2c-0   smbus           SMBus PIIX4 adapter at 0580             Non-I2C
> SMBus adapter
>
> --
> /Peter Welzien
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors at lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>

Does anybody have a clue what might be wrong? Or anything else that I can
try?

-- 
/Peter Welzien

[lm-sensors] sensors-detect hangs while scaning PIIX4

[Peter Welzien]

>>>> I didn't pass any parameters to the module. When it loads the only
>>>> message in the log is a line saying that the module is loaded and an
>>>> address. I don't have access to the computer right now, but I can get
>>>> the exact message tonight if you need it.
>>
>>> It might help, yes. Please make sure there is no complaint about an
>>> "illegal interrupt configuration". Please also provide a dump of the
>>> PCI config registers of the device. You can obtain such a dump using
>>> "lspci -xxx".
>>
>> dmesg says:
>> piix4_smbus 0000:00:0f.0: Found 0000:00:0f.0 device
>>
>> lspci -xxx:
>> 00:00.0 Host bridge: Broadcom CNB20LE Host Bridge (rev 06)
>> 00: 66 11 09 00 06 01 00 62 06 00 00 06 08 40 80 00
>> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 40: 00 00 00 00 00 00 04 06 80 14 00 eb 00 00 00 4b
>> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 70: 80 2a 00 af c0 0f ff 1f 01 1e 81 00 44 44 44 44
>> 80: 00 20 00 00 20 40 00 00 40 60 00 00 60 80 00 00
>> 90: 55 0a 29 10 0d 4f fe 44 00 00 00 00 00 00 00 00
>> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> b0: fb e6 dc 6f fe ac 1b be b8 7d fb ff ff fd f3 ff
>> c0: 20 fc af fe 00 fc 0f fc 00 04 00 00 0d 07 00 48
>> d0: 00 b0 fc df 00 10 00 00 00 00 00 00 01 80 10 93
>> e0: 04 00 00 2b 00 00 00 00 b2 00 00 00 00 00 00 00
>> f0: 00 00 00 40 00 00 00 00 00 00 00 00 60 01 00 00
>>
>> 00:00.1 Host bridge: Broadcom CNB20LE Host Bridge (rev 06)
>> 00: 66 11 09 00 07 00 00 02 06 00 00 06 08 10 80 00
>> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 40: 00 00 00 00 01 01 04 00 00 00 00 0b 00 00 00 00
>> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> c0: b0 fe bf fe 10 fc 1f fc 00 00 00 00 0d 07 00 00
>> d0: 00 e0 fc ef 00 00 00 00 00 00 00 00 01 00 00 00
>> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> f0: 00 00 00 08 00 00 00 00 00 00 00 00 61 01 00 00
>>
>> 00:0f.0 ISA bridge: Broadcom OSB4 South Bridge (rev 50)
>> 00: 66 11 00 02 07 00 00 02 50 00 01 06 00 00 80 00
>> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 20: 00 00 00 00 00 00 00 00 00 00 00 00 66 11 00 02
>> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 40: f0 33 00 00 00 00 00 00 07 00 00 00 00 00 00 00
>> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 60: 01 00 00 00 0f c1 20 00 00 00 00 00 00 00 00 00
>> 70: 01 40 08 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 90: 81 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> d0: 00 00 01 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
>>
>> (I've deleted the NICs, graphics card, IDE and USB-bus)
>>
>>> Then we need to figure out what exactly is locking your system. As I
>>> asked before, please try i2cdetect on the SMBus (typically "i2cdetect
>>> 0") and see if it locks too. You may additionally try "i2cdetect -r 0"
>>> and "i2cdetect -q 0". If these commands lock your system, note how much
>>> is written on your screen each time before the system locks.
>>
>> i2cdetect 0:
>> WARNING! This program can confuse your I2C bus, cause data loss and
>> worse!
>> I will probe file /dev/i2c/0.
>> I will probe address range 0x03-0x77.
>> Continue? [Y/n]
>>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>> [locks up]
>>
>> i2cdetect -r 0:
>> WARNING! This program can confuse your I2C bus, cause data loss and
>> worse!
>> I will probe file /dev/i2c/0 using read byte commands.
>> I will probe address range 0x03-0x77.
>> Continue? [Y/n]
>>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>> [locks up]
>>
>> i2cdetect -q 0:
>> WARNING! This program can confuse your I2C bus, cause data loss and
>> worse!
>> I will probe file /dev/i2c/0 using quick write commands.
>> I will probe address range 0x03-0x77.
>> Continue? [Y/n]
>>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>> [locks up]
>>
>> I did also try i2cdetect -l with following result:
>> i2c-0   smbus           SMBus PIIX4 adapter at 0580             Non-I2C
>> SMBus adapter
>>
>> --
>> /Peter Welzien
>>
>> _______________________________________________
>> lm-sensors mailing list
>> lm-sensors at lm-sensors.org
>> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

I've noticed that the computer also hangs if I try SpeedFan 4.31 on
Windows XP with the same motherboard. It hangs when scanning the SMBus. If
I disable SMBus scanning the computer doesn't hang (but don't show any
info).

-- 
/Peter Welzien

[lm-sensors] sensors-detect hangs while scaning PIIX4

[Jean Delvare]

Hi Peter,

On Tue, 6 Feb 2007 14:08:20 +0100 (CET), Peter Welzien wrote:
> I've noticed that the computer also hangs if I try SpeedFan 4.31 on
> Windows XP with the same motherboard. It hangs when scanning the SMBus. If
> I disable SMBus scanning the computer doesn't hang (but don't show any
> info).

Sorry, it really looks like a hardware problem so I don't think there's
anything I can do to help you. As I suggested before, try upgrading the
BIOS to the latest version available. If it doesn't help, your best
chance is to report the problem to the board manufacturer, but as this
is an old board, odds are they won't give it a damn.

-- 
Jean Delvare

[lm-sensors] sensors-detect hangs while scaning PIIX4

[Peter Welzien]

> Sorry, it really looks like a hardware problem so I don't think there's
> anything I can do to help you. As I suggested before, try upgrading the
> BIOS to the latest version available. If it doesn't help, your best
> chance is to report the problem to the board manufacturer, but as this
> is an old board, odds are they won't give it a damn.

I am using the latest bios. And yes, the board is quite old so I'm going
to drop this subject. It's too bad, I would've really liked it to work.
Well, well.

Thanks for the time taken trying to help me.

-- 
/Peter Welzien