From: Dave Jones <davej@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: clockevents_program_event WARN_ON preventing boot.
Date: Tue, 30 Apr 2013 17:20:07 -0400 [thread overview]
Message-ID: <20130430212007.GB18598@redhat.com> (raw)
I have a machine that crashes instantly on boot up on Linus'
post-3.9 tree. (8c55f1463c1fd318d5e785f02b80bcc32176d342)
By booting with boot_delay=100, I was able to take a photo
and capture the top of the trace. (For some reason, larger boot
delay parameters seem to make it take forever before printing
even a single character, which made this a pain to debug).
The WARN_ON it prints right before locking up is this in clockevents_program_event
208 if (unlikely(expires.tv64 < 0)) {
209 WARN_ON_ONCE(1);
210 return -ETIME;
211 }
booting with maxcpus=1 avoids the problem.
I'm still trying to get a complete stack trace, though it's painful
due to the above reason.
Dave
next reply other threads:[~2013-04-30 21:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 21:20 Dave Jones [this message]
2013-04-30 21:37 ` clockevents_program_event WARN_ON preventing boot Dave Jones
2013-05-02 10:37 ` Thomas Gleixner
2013-05-02 15:46 ` Dave Jones
2013-05-02 17:56 ` Yinghai Lu
2013-05-02 19:58 ` Thomas Gleixner
2013-05-02 20:54 ` Yinghai Lu
2013-05-02 21:19 ` Thomas Gleixner
2013-05-02 21:36 ` Yinghai Lu
2013-05-02 22:49 ` Thomas Gleixner
2013-05-03 14:49 ` Dave Jones
2013-05-03 18:32 ` Thomas Gleixner
2013-05-03 20:10 ` Dave Jones
2013-05-04 5:03 ` Yinghai Lu
2013-05-05 6:21 ` [tip:timers/urgent] tick: Use zalloc_cpumask_var for allocating offstack cpumasks tip-bot for Thomas Gleixner
2013-05-05 9:17 ` tip-bot for Thomas Gleixner
2013-05-05 12:49 ` tip-bot for Thomas Gleixner
2013-05-05 14:15 ` tip-bot for Thomas Gleixner
2013-05-10 13:24 ` clockevents_program_event WARN_ON preventing boot Josh Boyer
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=20130430212007.GB18598@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).