Hi,

We are using embedded linux. Recently we have upgraded our kernel from 2.6.29 to 2.6.37.After upgrading the custom driver (provided by infineon for 2.6.29) the functionality is not working, kernel hangs and getting watchdog reboot.
After stopping watchdog also we are not getting any info why / where the hang is happening.

Can some one suggest any clue about this.

Thanks & Regards,
Arul.

There are multiple things possible, I'd start with ioctl handling. It has changed somewhere around this range of versions.

Do you have the source code of the driver?

Hi Mara,

Thanks for your reply. Yes, we have the source code. we have changed the ioctl to unlocked_ioctl.
Now the problem seems to be in interrupt, If the interrupt assignment number is not correct, no hang happen. So we feel that the kernel hangs while getting or processing interrupt.. but we are not getting any clue where and why it's happening.

Regards,
Arul.

There's a difference between ioctl and unlocked_ioctl. In the new one, you need to add synchronization yourself. Look if it is not the case of a race condition between the unlocked_ioctl and the interrupt.

I found the route cause for the problem.
The kernel hang due to the following new change in kernel 2.6.37
Request irq() changed with request_threaded_irq with added parameter for the thread ptr.
Bydefault, the kernel isr routine will re-enable the interrupt after processing the user isr routine.
The default behavior of kernel re-enabling interrupt giving problem for our driver and kernel hangs due to multiple interrupts.

For threaded irq, which don’t want to re-enable the interrupt after the isr, we need to pass a parameter IRQF_ONESHOT in request_irq().
After adding the IRQF_ONESHOT in request_irq() our kernel hang issue resolved.

Thanks.