From: Jonathan Nieder <jrnieder@gmail.com>
To: Arnaud Patard <arnaud.patard@rtp-net.org>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Roman Mamedov <rm@romanrm.ru>,
Manuel Roeder <manuel_roeder@gmx.de>,
Michael Ott <michael@king-coder.de>
Subject: [2.6.37 -> 2.6.38 regression] "mv64xxx: I2C bus locked, block: 1, time_left: 0" every few seconds
Date: Sun, 1 Jan 2012 01:32:55 -0600 [thread overview]
Message-ID: <20120101073255.GA2402@elie.hsd1.il.comcast.net> (raw)
In-Reply-To: <20120101042401.4bef017e@natsu>
Hi,
Roman Mamedov wrote[1]:
> 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:
[...]
> 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
[1] http://bugs.debian.org/622325
next parent reply other threads:[~2012-01-01 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120101042401.4bef017e@natsu>
2012-01-01 7:32 ` Jonathan Nieder [this message]
2012-01-08 0:45 ` Guenter Roeck
2012-01-30 20:44 ` Roman Mamedov
2012-01-30 20:53 ` Roman Mamedov
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120101073255.GA2402@elie.hsd1.il.comcast.net \
--to=jrnieder@gmail.com \
--cc=arnaud.patard@rtp-net.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel_roeder@gmx.de \
--cc=michael@king-coder.de \
--cc=rm@romanrm.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
all inboxes | Powered by JetHome®