Well i never encountered this, but i would guess it has to do with two devices sharing the same IRQ's. Thus u get a resource collision since both drivers try to communicate via the same IRQ. You should load one of the drivers for one of those devices passing it a IRQ= flag, to assign it another IRQ. Look through /proc to see what devices are in IRQ conflict.
HTH
-NSKL
|