I have a linux-2.6.17.11 source tree that has configs for two boards. One has an 8241 and the other has an 8541. The kernel code works fine on the 8241, but appears to lock up in my custom driver in the 8541 when interrupts are enabled.
What I see happening, based on using a BDI to go/halt after the apparent lockup is that the kernel is spinning around in routines like kernel/irq/handle.c:__do_IRQ and an associated arch/powerpc/kernel/irq.c. It looks like the interrupt, which should be level triggered and at this point, is probably continuously asserted is causing the kernel to spin in a tight loop and be incapable of doing printk's out the serial port at 115200. This leads to a few questions: 1. I can see most everything comes from arch/ppc, but do_IRQ comes from arch/powerpc. Is that OK? 2. What is the most straightforward way to slow down a tight loop like this slow enough so I can printk what is happening. 3. What might be the likely scenarios leading to such a despicable state. Charles Krinke _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
