* Arnaud Ebalard a...@natisbad.org [2013-06-25 22:52]:
Either wait for 3.11 or pick 4243fa0bad551b8c8d4ff7104e8fd557ae848845
(I2C: mv64xxx: fix race between FSM/interrupt and process context)
from my for-next branch. (Note the other patches from Russell,
probably all worth to pick).
Hi guys,
While debugging a similar mv64xxx i2c bus lock on a Netgear ReadyNAS 102
NAS (based on a Marvell Armada 370 SoC), I ended up on #622325 bug
report. Reverting eda6bee6c7 makes the issue disappear for me and also
for Simon (in Cc:) for another Marvell-based NAS with the same i2c
controller
* Roman Mamedov r...@romanrm.ru [2012-01-31 02:38]:
Were you able to try backing out eda6bee6c7 (i2c-mv64xxx: send
repeated START between messages in xfer) as Guenter suggested?
I have finally managed to do that, and indeed, this problem is solved by
rolling-back that commit. The same
On Mon, 23 Jan 2012 14:27:50 -0600
Jonathan Nieder jrnie...@gmail.com wrote:
Were you able to try backing out eda6bee6c7 (i2c-mv64xxx: send
repeated START between messages in xfer) as Guenter suggested?
I have finally managed to do that, and indeed, this problem is solved by
rolling-back that
On Sun, 1 Jan 2012 01:42:36 -0600
Jonathan Nieder jrnie...@gmail.com wrote:
This bug is still present for me in the latest kernel version in
Debian testing (3.1.6).
Passed upstream. But now I notice that there has been some upstream
work in this area recently (v3.2-rc7~23^2~1, rtc:
found 622325 linux-2.6/3.1.8-2
quit
Roman Mamedov wrote:
Jonathan Nieder jrnie...@gmail.com wrote:
Passed upstream. But now I notice that there has been some upstream
work in this area recently (v3.2-rc7~23^2~1, rtc: m41t80: Workaround
broken alarm functionality, 2011-12-12).
[...]
I have
On Mon, 23 Jan 2012 14:27:50 -0600
Jonathan Nieder jrnie...@gmail.com wrote:
Were you able to try backing out eda6bee6c7 (i2c-mv64xxx: send
repeated START between messages in xfer) as Guenter suggested? It
works like this:
Hello,
If this had been a regular x86 machine I would have done this
Roman Mamedov wrote:
Jonathan Nieder jrnie...@gmail.com wrote:
Were you able to try backing out eda6bee6c7 (i2c-mv64xxx: send
repeated START between messages in xfer) as Guenter suggested? It
works like this:
[...]
If this had been a regular x86 machine I would have done this long ago :)
On Sun, 1 Jan 2012 01:42:36 -0600
Jonathan Nieder jrnie...@gmail.com wrote:
Passed upstream. But now I notice that there has been some upstream
work in this area recently (v3.2-rc7~23^2~1, rtc: m41t80: Workaround
broken alarm functionality, 2011-12-12).
Please test v3.2-rc7 from
severity 622325 important
quit
Roman Mamedov wrote:
Unfortunately I can't try that kernel easily at the moment, as there
doesn't seem to be an orion5x variant of the package in
experimental.
Oh, right.[1] Let's wait to hear what the developers come up with, then.
Thanks,
Jonathan
[1]
Hi again,
Roman Mamedov wrote:
This bug is still present for me in the latest kernel version in
Debian testing (3.1.6).
Passed upstream. But now I notice that there has been some upstream
work in this area recently (v3.2-rc7~23^2~1, rtc: m41t80: Workaround
broken alarm functionality,
Hi,
It should be fixed the 2.6.39 kernel uploaded to unstable. Can you test it,
please ?
Thanks,
Arnaud
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Package: linux-2.6
Version: 2.6.38-3
Severity: normal
syslog tell me every few seconds:
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
I found a mailing list entry here but no result:
http://comments.gmane.org/gmane.linux.ports.arm.kernel/111480
-- Package-specific info:
**
* Michael Ott mich...@king-coder.de [2011-04-12 09:00]:
syslog tell me every few seconds:
i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
I found a mailing list entry here but no result:
http://comments.gmane.org/gmane.linux.ports.arm.kernel/111480
Can one of you bisect the
14 matches
Mail list logo
