From: Guenter Roeck <guenter.roeck-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>
To: Jonathan Nieder <jrnieder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Arnaud Patard
<arnaud.patard-dQbF7i+pzddAfugRpC6u6w@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Roman Mamedov <rm-pzoh41kZ4TQvJsYlp49lxw@public.gmane.org>,
Manuel Roeder <manuel_roeder-Mmb7MZpHnFY@public.gmane.org>,
Michael Ott <michael-rB2af1Vdh+fddJNmlsFzeA@public.gmane.org>,
Rodolfo Giometti <giometti-k2GhghHVRtY@public.gmane.org>,
Mauro Barella <mbarella-RSoB1PSltFvQT0dZR+AlfA@public.gmane.org>
Subject: Re: [2.6.37 -> 2.6.38 regression] "mv64xxx: I2C bus locked, block: 1, time_left: 0" every few seconds
Date: Sat, 7 Jan 2012 16:45:02 -0800 [thread overview]
Message-ID: <20120108004502.GA20549@ericsson.com> (raw)
In-Reply-To: <20120101073255.GA2402-E4JsH6yu/ca99If2fRKg35Ea+QML8DWm@public.gmane.org>
On Sun, Jan 01, 2012 at 01:32:55AM -0600, Jonathan Nieder wrote:
> 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.
>
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
WARNING: multiple messages have this Message-ID (diff)
From: guenter.roeck@ericsson.com (Guenter Roeck)
To: linux-arm-kernel@lists.infradead.org
Subject: [2.6.37 -> 2.6.38 regression] "mv64xxx: I2C bus locked, block: 1, time_left: 0" every few seconds
Date: Sat, 7 Jan 2012 16:45:02 -0800 [thread overview]
Message-ID: <20120108004502.GA20549@ericsson.com> (raw)
In-Reply-To: <20120101073255.GA2402@elie.hsd1.il.comcast.net>
On Sun, Jan 01, 2012 at 01:32:55AM -0600, Jonathan Nieder wrote:
> 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.
>
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
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Arnaud Patard <arnaud.patard@rtp-net.org>,
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>,
Rodolfo Giometti <giometti@linux.it>,
Mauro Barella <mbarella@vds-it.com>
Subject: Re: [2.6.37 -> 2.6.38 regression] "mv64xxx: I2C bus locked, block: 1, time_left: 0" every few seconds
Date: Sat, 7 Jan 2012 16:45:02 -0800 [thread overview]
Message-ID: <20120108004502.GA20549@ericsson.com> (raw)
In-Reply-To: <20120101073255.GA2402@elie.hsd1.il.comcast.net>
On Sun, Jan 01, 2012 at 01:32:55AM -0600, Jonathan Nieder wrote:
> 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.
>
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
next prev parent reply other threads:[~2012-01-08 0:45 UTC|newest]
Thread overview: 10+ 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
[not found] ` <20120101073255.GA2402-E4JsH6yu/ca99If2fRKg35Ea+QML8DWm@public.gmane.org>
2012-01-08 0:45 ` Guenter Roeck [this message]
2012-01-08 0:45 ` Guenter Roeck
2012-01-08 0:45 ` Guenter Roeck
2012-01-30 20:44 ` Roman Mamedov
2012-01-30 20:44 ` Roman Mamedov
2012-01-30 20:44 ` Roman Mamedov
2012-01-30 20:53 ` Roman Mamedov
2012-01-30 20:53 ` 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=20120108004502.GA20549@ericsson.com \
--to=guenter.roeck-izefyvvap7pwk0htik3j/w@public.gmane.org \
--cc=arnaud.patard-dQbF7i+pzddAfugRpC6u6w@public.gmane.org \
--cc=giometti-k2GhghHVRtY@public.gmane.org \
--cc=jrnieder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=manuel_roeder-Mmb7MZpHnFY@public.gmane.org \
--cc=mbarella-RSoB1PSltFvQT0dZR+AlfA@public.gmane.org \
--cc=michael-rB2af1Vdh+fddJNmlsFzeA@public.gmane.org \
--cc=rm-pzoh41kZ4TQvJsYlp49lxw@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.