Hi Greg, >> After applying the patch from the thread above, I get a new break at: >> >> Program received signal SIGTRAP, Trace/breakpoint trap. >> 0x40022e9a in timer_interrupt (irq=68, dummy=0x0, regs=0xe4a0) at >> arch/m68knommu/kernel/time.c:54 >> 54 update_process_times(user_mode(regs)); >> (gdb) >> >> I have worked quite a bit with the 20071107 patch, and with that patch >> applied everything seems to work very nicely. So, basically, should I >> stop chasing my tail any further, because I noted Greg has reworked a >> lot of the interrupt handling code since 20070130? > >My gut feeling is "yes, no need to keep chasing". I am not aware of >any follow on problems after switching to the generic interrupts >framework in later kernels. But then again, it probably hasn't had >enough general testing yet - since it is not in a kernel in a >"normal" dist release yet.
I actually found the issue last week. It's caused by the regs pointer not being given a valid value in the timer interrupt function in arch/m68knommu/kernel/time.c, due to the general change of how the regs pointer is handled in the later kernel versions. The regs pointer was fixed in a patch from you February 2007-02-09. When applying this patch, everything works perfectly. No more "spurious" FLASH accesses casuing problems with the dq6 polling. :) I.e. if applying the http://mailman.uclinux.org/pipermail/uclinux-dev/2007-February/042053.ht ml patch, and then also the regs pointer patch (git.infradead.org), then the 20070130 works OK (as far as I can tell). So now I definitely close this case. Thanks for your comments. Regards, Martin _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
