On Thu, Jul 12, 2012 at 06:47:57PM +0200, Kay Sievers wrote:
> > > > Also, I have no idea how the hell the 'Modules linked in:' line (9th
> > line) ended up being printed /after/ the
> > > > module listing began (2nd line).
>
> They do not belong together. The second line is just another call to
> the same print_modules() done from:
> arch/x86/kernel/dumpstack_64.c :: show_regs()
>
> While we already called print_modules() a few cycles earlier from:
> kernel/watchdog :: watchdog_timer_fn()
ah, derp. Good spotting.
> Hmm, it does not trigger your pattern. I tried adding an rmmod in that
> loop, but that crashes after a few seconds. Some modules are just not
> meant to be removed. :)
yeah, that's bothersome. TTBOMK, we've never survived a 'load all
modules/unload all modules' ever.
> I forced the watchdog to trigger by setting the timeout to 1s, but all
> looks still fine:
>
> Could it possibly be that we get some sort of corruption somewhere
> else while running trinity and load modules?
I suppose anything is possible, but it's surprisingly consistent.
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
