Re: [RFC PATCH arm: initial TI-Nspire support]
From: Fabian Vogt
Date: Mon Apr 08 2013 - 16:05:23 EST
On Monday 08 April 2013, Fabian Vogt wrote:
The latest kernel it seems to get stuck at
console_lock() in do_register_framebuffer (drivers/video/fbmem.c:1655)
if the LCD-controller is enabled. (Early printk and serial console works
fine)
CONFIG_NO_HZ is not activated, it works completely.
Could this be a kernel bug or is this an issue with our timer
configuration?
This usually happens when the console driver or anything it uses
calls a function that does a printk(), which means you get a recursive
call into the console code and try to get the same lock again.
Yes, I've heard that before, but than it would work/not work independently
of NO_HZ. Can printk's be executet within console_lock() ..
console_unlock() blocks?
If not, it could be fb_notifier_call_chain, too, but that wouldn't be
likely at all.
I also tried spinlock/mutex debugging and soft lockup detection,
but neither of them outputs anything.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/