On Sat, Aug 6, 2011 at 00:32, Michael Schmitz <[email protected]> wrote: > there is a pattern to this - most of the times the watchdog fires when the > IDE interface is probed. In that case we have TSR=0x3, ISR=0x3 (need to > look up what that means in the driver headers). > > Other times, it is either the floppy interface getting probed, or in one > case, the mouse. The TSR is different there (0x5). > > It appears interrupts from the card get lost when other drivers disable > interrupts for too long. I'd go back to a version of the kernel before we > moved to the genirq framework (that was at the end of May this year). If > that still works, bisect from there (man git-bisect) to find the approximate > commit that broke Amiga ethernet. > > If you cannot use git-bisect, I'd have to build kernels for you to test > again and again until we find the last one that works - quite slow a > procedure but it might be the only thing. > > Geert: is the genirq change simple to back out, just for tests?
The genirq conversion is not complete, and not yet on the master branch. So it's unrelated. > On 05/08/11 23:53, Tuomas Vainikka wrote: >> >> On 08/04/2011 11:45 PM, Michael Schmitz wrote: >>> >>> On Fri, Aug 5, 2011 at 4:59 AM, Tuomas Vainikka >>> <[email protected]> wrote: >>>> >>>> Hello, >>>> >>>> The other network drivers were previously compiled as modules, and I >>>> only >>>> had apne built-in. >>>> Now I removed the other drivers being built in any way, but I still get >>>> an >>>> error: >>> >>> Is there a way to get timestamps logged with each of the entries in >>> the call trace below (i.e. could we rig some profiling code for that)? >>> Would be interesting to know where exactly the kernel was spinning >>> when the watchdog fired. But maybe that's obvious to someone. >>> >>> Are there potential deadlocks with printk called from softirq context >>> (I think not ...)? What is the message printed immediately after the >>> trace? >> >> I've attached full dmesg outputs from ten sequential boots with the kernel >> config. >> You can see that the trace can happen any time, or not at all. >>> >>> Last - has anyone ever tried to bisect this? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
