Hi Mike, Antonio & all, > I narrowed the problem down. > In the following scenario, the OOPS occurs: > CONFIG_I2C=y > CONFIG_FB_NVIDIA=y > CONFIG_FB_NVIDIA_I2C=y > > If CONFIG_I2C is changed to build as a module, no crash occurs. Hardly relevant, since this means CONFIG_FB_NVIDIA!=y as well. > If CONFIG_FB_NVIDIA_I2C is not set, no crash occurs. > If CONFIG_FB_NVIDIA is changed to build as a module, no crash occurs. I guess the driver won't auto-load, so you should try to modprobe it afterwards. Maybe it'll crash as well then. Mike, can you please provide a decoded oops? There's not much we can do without that. I wonder if this problem could be related to this one: http://bugme.osdl.org/show_bug.cgi?id=4347 This too is a bit-banging I2C adapter, part of a framebuffer driver (savage there instead of nv here). Antonio, any idea? You wrote both drivers recently. I'm rather ignorant when it comes to IRQs so I'm not sure I can really help. Thanks, -- Jean Delvare
