From: Fengguang Wu <fengguang.wu@intel.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: boot hang on CONFIG_FB_VGA16
Date: Sun, 24 Jun 2012 05:21:38 +0000 [thread overview]
Message-ID: <20120624052138.GA6965@localhost> (raw)
Hi,
I can reproduce this easily when running CONFIG_FB_VGA16=y kernels
inside KVM. Older kernels like 3.2, 3.3, 3.4 don't have these warning
messages, but just randomly hang during boot.
I'm not sure if this is a relevant problem, but anyway, here is the
bug report.
INFO: rcu_sched self-detected stall on CPU { 1} (t\x15003 jiffies)
Pid: 8, comm: kworker/1:0 Not tainted 3.5.0-rc3-wl+ #11
Call Trace:
<IRQ> [<ffffffff810a1e35>] __rcu_pending+0xc2/0x3c3
[<ffffffff8107a1bc>] ? tick_nohz_handler+0xd5/0xd5
[<ffffffff810a3052>] rcu_check_callbacks+0x9d/0x149
[<ffffffff81061b01>] ? sched_clock_cpu+0xbb/0xcc
[<ffffffff8103db27>] update_process_times+0x3e/0x72
[<ffffffff8107a228>] tick_sched_timer+0x6c/0x95
[<ffffffff81061b21>] ? local_clock+0xf/0x3c
[<ffffffff810537d3>] __run_hrtimer+0xcf/0x1d1
[<ffffffff810541c6>] hrtimer_interrupt+0xc6/0x191
[<ffffffff817bc52a>] smp_apic_timer_interrupt+0x86/0x99
[<ffffffff817bb51c>] apic_timer_interrupt+0x6c/0x80
<EOI> [<ffffffff81030a8c>] ? console_unlock+0x21b/0x2c5
[<ffffffff813304a1>] ? update_attr.isra.1+0x8a/0x8a
[<ffffffff8132b7a7>] fb_flashcursor+0x114/0x123
[<ffffffff81048529>] process_one_work+0x238/0x45c
[<ffffffff8104848c>] ? process_one_work+0x19b/0x45c
[<ffffffff8132b693>] ? get_color+0xfd/0xfd
[<ffffffff8104876e>] process_scheduled_works+0x21/0x2f
[<ffffffff810488f5>] worker_thread+0x179/0x240
Thanks,
Fengguang
reply other threads:[~2012-06-24 5:21 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=20120624052138.GA6965@localhost \
--to=fengguang.wu@intel.com \
--cc=FlorianSchandinat@gmx.de \
--cc=adaplas@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).