Hi Andrew, Miles, > > Andrew, this command causes the Oops for me: > > > > [EMAIL PROTECTED]:/sys/class/i2c-adapter/i2c-1# ls > > ./ ../ device@ > > [EMAIL PROTECTED]:/sys/class/i2c-adapter/i2c-1# ls -l > > Segmentation fault > > What device is that, and which driver is handling it?
If I am allowed a wild guess here... Isn't by any chance i2c-1 one the the 3 i2c adapters exported by the nvidiafb driver, which we know isn't playing nicely with the i2c core? To me, it is simply a different expression of the same bug Miles hit some days ago when loading the i2c-dev or eeprom modules [1]. Miles, do you have the same problem with i2c-0 and i2c-2, or only i2c-1? Can you please confirm that with CONFIG_FB_NVIDIA_I2C unset, the oops vanishes? [1] http://archives.andrew.net.au/lm-sensors/msg29974.html Thanks, -- Jean Delvare - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
