On Wed, 2009-06-17 at 03:23 +0100, Ben Hutchings wrote: > The actual upstream fix appears to be this: > > commit b845b517b5e3706a3729f6ea83b88ab85f0725b0 > Author: Peter Zijlstra <firstname.lastname@example.org> > Date: Fri Aug 8 21:47:09 2008 +0200 > > printk: robustify printk > > Avoid deadlocks against rq->lock and xtime_lock by deferring the klogd > wakeup by polling from the timer tick. > > This applies successfully to 2.6.26 and doesn't seem to be dependent on > any intervening changes. It's not clear to me whether there are other > cases in 2.6.26 where a printk() could trigger this deadlock. If not > then I'd rather go with the simple workaround for this one case. I found one other place: arch/alpha/kernel/time.c:timer_interrupt() -> arch/alpha/kernel/time.c:set_rtc_mmss() -> printk() Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity.
Description: This is a digitally signed message part