From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH arm: initial TI-Nspire support]
Date: Mon, 8 Apr 2013 23:29:07 +0200 [thread overview]
Message-ID: <201304082329.08105.arnd@arndb.de> (raw)
In-Reply-To: <op.wu8ng3wyu7prd4@fabians-laptop.fritz.box>
On Monday 08 April 2013, Fabian Vogt wrote:
> 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?
I think it's legal to call printk in that case, but the message will
not be printed until you reach the console_unlock()
> 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.
Unfortunately, lockdep does not help with console_lock, since that
is a weird semaphore variant, not a standard mutex or spinlock.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: "Fabian Vogt" <fabian@ritter-vogt.de>
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>
Subject: Re: [RFC PATCH arm: initial TI-Nspire support]
Date: Mon, 8 Apr 2013 23:29:07 +0200 [thread overview]
Message-ID: <201304082329.08105.arnd@arndb.de> (raw)
In-Reply-To: <op.wu8ng3wyu7prd4@fabians-laptop.fritz.box>
On Monday 08 April 2013, Fabian Vogt wrote:
> 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?
I think it's legal to call printk in that case, but the message will
not be printed until you reach the console_unlock()
> 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.
Unfortunately, lockdep does not help with console_lock, since that
is a weird semaphore variant, not a standard mutex or spinlock.
Arnd
next prev parent reply other threads:[~2013-04-08 21:29 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 9:01 [RFC PATCH arm: initial TI-Nspire support] Daniel Tang
2013-04-04 9:01 ` Daniel Tang
2013-04-04 11:12 ` Arnd Bergmann
2013-04-04 11:12 ` Arnd Bergmann
2013-04-06 0:26 ` Daniel Tang
2013-04-06 0:26 ` Daniel Tang
2013-04-06 11:51 ` Arnd Bergmann
2013-04-06 11:51 ` Arnd Bergmann
2013-04-06 12:00 ` Daniel Tang
2013-04-06 12:00 ` Daniel Tang
2013-04-06 13:24 ` Arnd Bergmann
2013-04-06 13:24 ` Arnd Bergmann
2013-04-07 0:06 ` Daniel Tang
2013-04-07 0:06 ` Daniel Tang
2013-04-07 3:56 ` Daniel Tang
2013-04-07 3:56 ` Daniel Tang
2013-04-07 21:23 ` Arnd Bergmann
2013-04-07 21:23 ` Arnd Bergmann
2013-04-08 11:33 ` Daniel Tang
2013-04-08 11:33 ` Daniel Tang
2013-04-08 19:16 ` Fabian Vogt
2013-04-08 19:16 ` Fabian Vogt
2013-04-08 19:38 ` Arnd Bergmann
2013-04-08 19:38 ` Arnd Bergmann
2013-04-08 20:06 ` Fabian Vogt
2013-04-08 20:06 ` Fabian Vogt
2013-04-08 21:29 ` Arnd Bergmann [this message]
2013-04-08 21:29 ` Arnd Bergmann
2013-04-09 5:59 ` Daniel Tang
2013-04-09 5:59 ` Daniel Tang
2013-04-09 11:23 ` Linus Walleij
2013-04-09 11:23 ` Linus Walleij
2013-04-09 12:01 ` Pawel Moll
2013-04-09 12:01 ` Pawel Moll
2013-04-09 12:05 ` Linus Walleij
2013-04-09 12:05 ` Linus Walleij
2013-04-09 13:51 ` Russell King - ARM Linux
2013-04-09 13:51 ` Russell King - ARM Linux
2013-04-07 14:32 ` Arnd Bergmann
2013-04-07 14:32 ` Arnd Bergmann
2013-04-09 11:14 ` Linus Walleij
2013-04-09 11:14 ` Linus Walleij
2013-04-09 11:39 ` Daniel Tang
2013-04-09 11:39 ` Daniel Tang
2013-04-09 11:58 ` Linus Walleij
2013-04-09 11:58 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201304082329.08105.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.