"mv64xxx: I2C bus locked, block: 1, time_left: 0" every few seconds
A message that is not in the archive (sent off-list or not yet received): 20120101042401.4bef017e@natsu
Hi,
Roman Mamedov wrote[1]:
Quoted 4 lines
This bug is still present for me in the latest kernel version in Debian testing (3.1.6).
The last properly working kernel version seems to be:
[...]
Quoted 1 line
And the problem occurs since:
[...]
Thanks. Arnaud, any hints? To summarize:
- Michael Ott reported with Debian kernel 2.6.38-3 (which is closely based on stable v2.6.38.2):
syslog tell me every few seconds: i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
- Manuel Roeder reported the same and found that upstream v2.6.38 triggers the problem and v2.6.37.6 does not.
- Roman Mamedov finds the bug present in Debian 3.1.6-1 (which is closely based on stable v3.1.6) and Debian 2.6.37-2 (based on stable v2.6.37.2) but not Debian 2.6.37-1 (based on mainline v2.6.37).
The regression range described above seems a little inconsistent to me, so maybe there's something more going on.
Jonathan
Quoted 23 lines · Jonathan Nieder
Hi,
Roman Mamedov wrote[1]:
Quoted 4 lines
This bug is still present for me in the latest kernel version in Debian testing (3.1.6).
The last properly working kernel version seems to be:
[...]
Quoted 1 line
And the problem occurs since:
[...]
Thanks. Arnaud, any hints? To summarize:
- Michael Ott reported with Debian kernel 2.6.38-3 (which is closely based on stable v2.6.38.2):
syslog tell me every few seconds: i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0- Manuel Roeder reported the same and found that upstream v2.6.38 triggers the problem and v2.6.37.6 does not.
Quoted 8 lines
- Roman Mamedov finds the bug present in Debian 3.1.6-1 (which is closely based on stable v3.1.6) and Debian 2.6.37-2 (based on stable v2.6.37.2) but not Debian 2.6.37-1 (based on mainline v2.6.37).
The regression range described above seems a little inconsistent to me, so maybe there's something more going on.
Points to commit eda6bee6c7e67b5bd17bdbced0926f5687f686d5 (i2c-mv64xxx: send repeated START between messages in xfer). Maybe you can back it out and see if it makes a difference.
Guenter
Quoted 14 lines · On Sat, 7 Jan 2012 16:45:02 -0800 Guenter Roeck <[email protected]>…
Quoted 14 lines
- Michael Ott reported with Debian kernel 2.6.38-3 (which is closely based on stable v2.6.38.2):
syslog tell me every few seconds: i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0- Manuel Roeder reported the same and found that upstream v2.6.38 triggers the problem and v2.6.37.6 does not.
- Roman Mamedov finds the bug present in Debian 3.1.6-1 (which is closely based on stable v3.1.6) and Debian 2.6.37-2 (based on stable v2.6.37.2) but not Debian 2.6.37-1 (based on mainline v2.6.37).
Quoted 5 lines
Quoted 3 lines
The regression range described above seems a little inconsistent to me, so maybe there's something more going on.
Points to commit
eda6bee6c7e67b5bd17bdbced0926f5687f686d5(i2c-mv64xxx: send repeated START between messages in xfer). Maybe you can back it out and see if it makes a difference.
Hello,
I have just confirmed that the problem still occurs in the current 3.2.2, and is indeed solved by rolling-back the referred commit.
Should be noted that beside the "I2C bus locked" messages in dmesg, the described problem manifested itself in the inability to read the temperature sensor value or adjust the fan speed on the D-Link DNS-323. On all problematic kernels the built-in fan of DNS-323 does not rotate and this risks overheating the device and disks installed in it.
Thanks.
Signature · 15 lines
With respect, Roman ~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Stallman had a printer, with code he could not see. So he began to tinker, and set the software free." -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120131/959fd43a/attachment.sig>
Quoted 25 lines · On Tue, 31 Jan 2012 02:44:29 +0600 Roman Mamedov <[email protected]> wrote:
Quoted 14 lines · On Sat, 7 Jan 2012 16:45:02 -0800 Guenter Roeck <[email protected]>…
Quoted 14 lines
- Michael Ott reported with Debian kernel 2.6.38-3 (which is closely based on stable v2.6.38.2):
syslog tell me every few seconds: i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0- Manuel Roeder reported the same and found that upstream v2.6.38 triggers the problem and v2.6.37.6 does not.
- Roman Mamedov finds the bug present in Debian 3.1.6-1 (which is closely based on stable v3.1.6) and Debian 2.6.37-2 (based on stable v2.6.37.2) but not Debian 2.6.37-1 (based on mainline v2.6.37).
Quoted 5 lines
Quoted 3 lines
The regression range described above seems a little inconsistent to me, so maybe there's something more going on.
Points to commit
eda6bee6c7e67b5bd17bdbced0926f5687f686d5(i2c-mv64xxx: send repeated START between messages in xfer). Maybe you can back it out and see if it makes a difference.Hello,
Quoted 7 lines
I have just confirmed that the problem still occurs in the current 3.2.2, and is indeed solved by rolling-back the referred commit.
Should be noted that beside the "I2C bus locked" messages in dmesg, the described problem manifested itself in the inability to read the temperature sensor value or adjust the fan speed on the D-Link DNS-323. On all problematic kernels the built-in fan of DNS-323 does not rotate and this risks overheating the device and disks installed in it.
Also if anyone decides to further debug this, I should note that once a 'problematic' kernel has booted once on the device, a full power-off seems to be required, before a 'good' kernel can work properly. Without this, even a working kernel will manifest the same problem, it looks like something in the hardware gets locked-up hard and stays that way even across reboots. If someone's unaware of this, it can completely foil any attempt at git bisecting.
Signature · 15 lines
With respect, Roman ~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Stallman had a printer, with code he could not see. So he began to tinker, and set the software free." -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120131/ec3de644/attachment-0001.sig>