linux-kernel - Re: [RFC PATCH arm: initial TI-Nspire support]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201304082138.15875.arnd@arndb.de>
Date:	Mon, 8 Apr 2013 21:38:15 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	"Fabian Vogt" <fabian@...ter-vogt.de>
Cc:	"Daniel Tang" <dt.tangr@...il.com>,
	linux-arm-kernel@...ts.infradead.org, linux@....linux.org.uk,
	"Lionel Debroux" <lionel_debroux@...oo.fr>,
	linux-kernel@...r.kernel.org,
	"Linus Walleij" <linus.walleij@...aro.org>
Subject: Re: [RFC PATCH arm: initial TI-Nspire support]

On Monday 08 April 2013, Fabian Vogt wrote:
> The latest kernel it seems to get stuck at
> console_lock() in 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.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/