From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yegor Yefremov Subject: Re: PCA9564: "bus is not idle" issue Date: Tue, 30 Mar 2010 15:16:36 +0200 Message-ID: References: <20100317135223.GD4153@pengutronix.de> <20100318091917.GA27165@pengutronix.de> <20100329163149.41df7f10@hyperion.delvare> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <20100329163149.41df7f10-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Jean Delvare Cc: Wolfram Sang , linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-i2c@vger.kernel.org >> >> If I don't redirect syslog to a remote host I get i2c fail. So here you are: >> > >> > Thanks! >> > >> > [...] >> > >> >> As far as I can tell the last transaction lacks "=== STOP" state. >> > >> > Yes. The bus-status being 0x58 instead of 0xf8 says that, too. I wanted to >> > check if there is something flaky before. Will have a look, but will probably >> > be the weekend. You said it does not appear when you use 2.6.26, right? >> >> Right. Either it is so seldom, that I don't notice it or it doesn't >> occur. But with 2.6.33 it is really frequent. > > Any progress on this? If this is a regression, we want to fix it > quickly. I'm not really further. But I use a workaround for my system by just using this revision: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.33.y.git;a=commit;h=eff9ec95efaaf6b12d230f0ea7d3c295d3bc9d57. With revision i2c is working quite stable. Regards, Yegor