Re: Hard LOCKUP with (maybe scheduler/tick related?)

From: Sebastian Färber
Date: Mon Jan 31 2011 - 09:21:33 EST

Hi Don,

> Your attached 'crash' details had another stacktrace first.  That one
> shows the nmi_watchdog triggering because a spin_lock is spinning forever
> in 'd_real_path'.  I couldn't find that code in any upstream tree, then
> again I was too lazy to clone the stable trees.  So I don't know what the
> exact problem is, but if you look through the git history of and
> revert things that relate to 'd_real_path', you can probably workaround
> the problem for now, until someone who knows that stuff better than me can
> give you a better answer.

Thanks for the pointer. The 'd_real_path' function is part of
grsecurity, i'll see if they
can help :-)


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at