Colin King wrote:
> Thanks Dan. After some digging around I suspect this problem occurs
> because the device shares an interrupt line with other devices and the
> interrupt handler for this driver is trying to handle and interrupt
> before the rest of the driver is fully initialised, which leads to the
> oops.
>
> Which version is your current kernel so that I can build one with some
> debug to verify my assumption?
>
2.6.31-5-generic
- Dan
Colin King wrote:
> Thanks Dan. After some digging around I suspect this problem occurs
> because the device shares an interrupt line with other devices and the
> interrupt handler for this driver is trying to handle and interrupt
> before the rest of the driver is fully initialised, which leads to the
> oops.
>
> Which version is your current kernel so that I can build one with some
> debug to verify my assumption?
>