From: zhonghua <kezh@cetcmotor.com>
To: linux-fbdev@vger.kernel.org
Subject: Kernel blocked at register_framebuffer because console_block
Date: Fri, 29 Jan 2016 09:05:00 +0000 [thread overview]
Message-ID: <56AB2B3C.5040608@cetcmotor.com> (raw)
Hell all,
I have a booting problem because the drm driver register a new
framebuffer device after created it. Im not sure if the system blocked
or crashed, because there were no message output after its internal call
to console_lock. I tried marked the booting sequence, and found the
problem at: down(&console_sem);
and in its internal line is: sem->count--; Im not sure why? The fb
device is a dpi device, if I register another device, such as hdmi, it
would be OK.
reply other threads:[~2016-01-29 9:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56AB2B3C.5040608@cetcmotor.com \
--to=kezh@cetcmotor.com \
--cc=linux-fbdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox