Ticket #846 (closed task)

Opened 9 years ago

Ali1535 bus hang (tkt 803 cont'd) (Examined/Solved - lm_sensors 2.6.2 Linux 2.4.17-UP)

Reported by: contact Owned by: somebody
Priority: minor Milestone:
Component: hardware Version:
Keywords: Cc:

Description

Hi,

Here are the missing error messages, which is the problem. There tons in

kern.log / dmesg so i just paste a few blocks.

i2c-core.o: client [W83782D chip] registered to adapter [SMBus ALI1535 adapter

at e800](pos. 0).

i2c-core.o: client [W83782D subclient] registered to adapter [SMBus ALI1535

adapter at e800](pos. 1).

i2c-core.o: client [W83782D subclient] registered to adapter [SMBus ALI1535

adapter at e800](pos. 2).

i2c-ali1535.o: Error: command never completed

i2c-ali1535.o: Error: command never completed

i2c-ali1535.o: Resetting entire SMB Bus to clear busy condition (08)

i2c-ali1535.o: Error: device error

i2c-ali1535.o: Error: command never completed

i2c-ali1535.o: Resetting entire SMB Bus to clear busy condition (08)

i2c-ali1535.o: Resetting entire SMB Bus to clear busy condition (08)

i2c-ali1535.o: Error: device error

i2c-ali1535.o: Error: command never completed

i2c-ali1535.o: Resetting entire SMB Bus to clear busy condition (08)

i2c-ali1535.o: SMBus reset failed! (0x08) - controller or device on bus is

probably hung

i2c-core.o: driver unregistered: W83781D sensor driver

i2c-core.o: i2c core module version 2.6.2 (20011118)

i2c-ali1535.o version 2.6.2 (20011118)

i2c-core.o: adapter SMBus ALI1535 adapter at e800 registered as adapter 0.

i2c-ali1535.o: ALI1535 SMBus Controller detected and initialized

i2c-proc.o version 2.6.2 (20011118)

w83781d.o version 2.6.2 (20011118)

i2c-core.o: driver W83781D sensor driver registered. --- This is unfortunately somewhat common with ALI chips

which seem to be not too forgiving about other devices

on the bus.

You can try and figure out if the problem is from accessing

a specific device on the bus which is hanging the bus,

or what triggers the problem.

If the problem is cleared by removing and reinserting the 1535 module

then perhaps the driver could do a better job of error recovery.

If you figure it out any more send us email and reference your

ticket number.

MDS 2/1/02

Note: See TracTickets for help on using tickets.