>> >> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
