From: Arnd Bergmann <arnd@arndb.de>
To: "Fabian Vogt" <fabian@ritter-vogt.de>
Subject: Re: [RFC PATCH arm: initial TI-Nspire support]
Date: Mon, 8 Apr 2013 21:38:15 +0200
User-Agent: KMail/1.12.2 (Linux/3.8.0-16-generic; KDE/4.3.2; x86_64; ; )
Cc: "Daniel Tang" <dt.tangr@gmail.com>, linux-arm-kernel@lists.infradead.org,
        linux@arm.linux.org.uk, "Lionel Debroux" <lionel_debroux@yahoo.fr>,
        linux-kernel@vger.kernel.org,
        "Linus Walleij" <linus.walleij@linaro.org>
References: <6FE4B33E-A503-4A75-AEED-831CB2C06D83@gmail.com> <896CB251-17FC-4327-BA4E-A8FD9ED1BEC7@gmail.com> <op.wu8k5pwqu7prd4@fabians-laptop.fritz.box>
In-Reply-To: <op.wu8k5pwqu7prd4@fabians-laptop.fritz.box>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <201304082138.15875.arnd@arndb.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 833
Lines: 19

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/