From: Thomas Gleixner <tglx@linutronix.de>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: clockevents_program_event WARN_ON preventing boot.
Date: Thu, 2 May 2013 23:19:02 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1305022304370.2891@ionos> (raw)
In-Reply-To: <CAE9FiQXpV451xTzAJyNdC-+-oqF9v8Cy5evcNOHKFffERw2SwA@mail.gmail.com>
On Thu, 2 May 2013, Yinghai Lu wrote:
> On Thu, May 2, 2013 at 12:58 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
>
> >
> > The check should be:
> >
> > if (td->evtdev && tick_device_is_functional(td->evtdev))
>
> still happens.
>
> [ 3.457866] checking TSC synchronization [CPU#0 -> CPU#10]: passed.
> [ 3.460806] SMP alternatives: lockdep: fixing up alternatives
> [ 3.464282] ------------[ cut here ]------------
> [ 3.464297] WARNING: at kernel/time/clockevents.c:209
> clockevents_program_event+0x3b/0x100()
I didn't expect it to fix the warning, I just wanted to prevent the
crash which Dave decoded. Though the warning and the crash have
probably the same root cause...
> [ 3.464300] Modules linked in:
> [ 3.464306] CPU: 10 PID: 0 Comm: swapper/10 Not tainted
> 3.9.0-yh-08066-g1252014-dirty #1537
> [ 3.464308] Hardware name: Oracle Corporation unknown /
> , BIOS 11016600 05/17/2011
> [ 3.464327] 0000000000000009 ffff88203e203ed8 ffffffff82091022
> ffff88203e203f18
> [ 3.464343] ffffffff81088990 ffff88203e203f08 80000000003d08ff
> 80000000003d08ff
> [ 3.464359] 000000000000000a ffff881027557fd8 0000000000000000
> ffff88203e203f28
> [ 3.464361] Call Trace:
> [ 3.464379] <IRQ> [<ffffffff82091022>] dump_stack+0x19/0x1b
> [ 3.464392] [<ffffffff81088990>] warn_slowpath_common+0x70/0xa0
> [ 3.464395] [<ffffffff810889da>] warn_slowpath_null+0x1a/0x20
> [ 3.464399] [<ffffffff810e312b>] clockevents_program_event+0x3b/0x100
> [ 3.464403] [<ffffffff810e35ec>] tick_handle_periodic+0x4c/0x80
Now, that's really odd.
next = ktime_add(dev->next_event, tick_period);
clockevents_program_event(dev, next, false);
and next.tv64 is < 0 !?!
Can you please apply the following debug patch and provide the output?
Thanks,
tglx
diff --git a/kernel/time/clockevents.c b/kernel/time/clockevents.c
index c6d6400..b4d9622 100644
--- a/kernel/time/clockevents.c
+++ b/kernel/time/clockevents.c
@@ -207,6 +207,8 @@ int clockevents_program_event(struct clock_event_device *dev, ktime_t expires,
if (unlikely(expires.tv64 < 0)) {
WARN_ON_ONCE(1);
+ printk_once(KERN_INFO "expires %llx, dev->next %llx\n",
+ expires.tv64, dev->next_event.tv64);
return -ETIME;
}
next prev parent reply other threads:[~2013-05-02 21:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 21:20 Dave Jones
2013-04-30 21:37 ` 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 [this message]
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=alpine.LFD.2.02.1305022304370.2891@ionos \
--to=tglx@linutronix.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yinghai@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
Powered by JetHome