[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#622325: linux-image-2.6.38-2-orion5x: Problem With I2C

found 622325 linux-2.6/3.1.8-2

Roman Mamedov wrote:
> Jonathan Nieder <jrnieder@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 now upgraded to linux-image-3.1.0-1-orion5x (3.1.8-2) from testing.
> According to http://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.1.8
> it has the "rtc: m41t80: Workaround broken alarm functionality" patch included.
> However, it does not solve the problem. The messages continue to appear:

Great.  Please let upstream know by replying-to-all on the other
side thread[1].

Were you able to try backing out eda6bee6c7 (i2c-mv64xxx: send
repeated START between messages in xfer) as Guenter suggested?  It
works like this:

1. Build a stock upstream kernel:

 apt-get install git build-essential
 git clone \
 cd linux
 cp /boot/config-$(uname -r) .config; # stock configuration
 make localmodconfig; # minimal configuration
 make deb-pkg; # can use -j<n> to build faster if you have multiple cores
 dpkg -i ../<name of package>; # install the resulting package
 ... test test test ...

If at this point it works, the bug was fixed or upstream or it is a
Debian-specific or configuration-specific problem.  Yay!

2. Back out the patch and compare results:

 git revert eda6bee6c7
 make deb-pkg; # perhaps with -j<n>
 dpkg -i ../<name of package>; # install the resulting package
 ... test test test ...

Many thanks, and hope that helps.


[1] http://thread.gmane.org/gmane.linux.kernel/1234150

Reply to: