On Thu, Jul 12, 2012 at 03:52:17PM +0200, Kay Sievers wrote:
> On Thu, Jul 12, 2012 at 2:54 AM, Dave Jones <[email protected]> wrote:
> > On Mon, Jul 09, 2012 at 08:48:51PM +0200, Kay Sievers wrote:
>
> > > It looks fine here with the above mentioned patch:
> >
> > Now that that patch is in Linus tree, I've hit what's probably a different
> > case.
> > Look at the modules list in this oops..
> >
> > [10016.460020] BUG: soft lockup - CPU#1 stuck for 22s!
> > [trinity-child1:24295]
> > [10016.470008] rose<4>[10016.470008] ip_set_bitmap_ipmac<4>[10016.470008]
>
> > 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).
>
> It's the output of 'dmesg' you pasted, right?
Yes.
> I tried to force all sorts of racy print_modules() calls, and kept
> your trinity tool from git for hours, it looks all fine here:
>
> Can you easily reproduce the issue you pasted? If, could you give me
> the /dev/kmsg output?
I've seen it a few times, always with the soft lockup trace.
You might be able to trigger it using scripts/load-all-modules.sh
from trinity.git. (Assuming you have a lot of modules built, I'm
still trying to track down which one seems to be responsible).
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
