I can reproduce it, with both i2c-i801 and i2c-parport, so it's notrelated to a specific driver. I'm currently performing a bisection on2.6.17-rc4-mm1 to try and isolate the culprit. It seems to point togregkh-driver-*. i2c patches are innocent for sure, including Kumar'sones.