From: Roman Mamedov <email@example.com>
To: Roman Mamedov <firstname.lastname@example.org>
Cc: Guenter Roeck <email@example.com>,
Jonathan Nieder <firstname.lastname@example.org>,
Arnaud Patard <email@example.com>,
Manuel Roeder <firstname.lastname@example.org>,
Michael Ott <email@example.com>,
Rodolfo Giometti <firstname.lastname@example.org>,
Mauro Barella <email@example.com>
Subject: Re: [2.6.37 -> 2.6.38 regression] "mv64xxx: I2C bus locked, block: 1, time_left: 0" every few seconds
Date: Tue, 31 Jan 2012 02:53:29 +0600 [thread overview]
Message-ID: <20120131025329.30e73a3f@natsu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2266 bytes --]
On Tue, 31 Jan 2012 02:44:29 +0600
Roman Mamedov <firstname.lastname@example.org> wrote:
> On Sat, 7 Jan 2012 16:45:02 -0800
> Guenter Roeck <email@example.com> wrote:
> > > - Michael Ott reported with Debian kernel 2.6.38-3 (which is closely
> > > based on stable v126.96.36.199):
> > >
> > > 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 v188.8.131.52 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 v184.108.40.206) 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.
> 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.
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-01-30 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120101042401.4bef017e@natsu>
2012-01-01 7:32 ` [2.6.37 -> 2.6.38 regression] "mv64xxx: I2C bus locked, block: 1, time_left: 0" every few seconds Jonathan Nieder
2012-01-08 0:45 ` Guenter Roeck
2012-01-30 20:44 ` Roman Mamedov
2012-01-30 20:53 ` Roman Mamedov [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).