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

Bug#622325: DNS323 RTC-M41T80 starting with Kernel 2.6.38-orion5x (still there in 2.6.38.2) / seems to be introduced with RTC-REWORK



The formerly found bug seems to be introduced with the RTC-rework starting with kernel 2.6.38.
It seems to be NOT a bug of I2C- or LM75-driver! 
The bug starts with kernel 2.6.38 and is still there in 2.6.38.2.

Kernel 2.6.37.6 runs fine!!!! No RTC-bug here!!!

[   18.270364] i2c /dev entries driver
[   18.274728] rtc-m41t80 0-0068: chip found, driver version 0.05
[   18.280955] m41t80: dev (254:0)
[   18.281012] rtc-m41t80 0-0068: rtc core: registered m41t80 as rtc0
[   20.280626] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   20.287144] rtc-m41t80 0-0068: Can't clear HT bit
[   20.292139] rtc-m41t80: probe of 0-0068 failed with error -5
[   22.290615] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   22.297153] lm75: probe of 0-0048 failed with error -110
[   24.300623] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   26.300925] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   28.300905] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   30.300636] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   32.300906] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   34.300844] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   36.300648] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0

regards Manuel Roeder - manuel.roeder(at)web.de





Reply to: