From: Dave Jones <davej@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: clockevents_program_event WARN_ON preventing boot.
Date: Thu, 2 May 2013 11:46:21 -0400 [thread overview]
Message-ID: <20130502154621.GA23990@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1305021234510.3972@ionos>
On Thu, May 02, 2013 at 12:37:26PM +0200, Thomas Gleixner wrote:
> > On a second machine, I'm seeing an oops even earlier. As soon as I
> > exit grub, I get a blinking cursor. If I boot with earlyprintk=vga
> > I can see..
> >
> > Call Trace:
> > <IRQ>
> > tick_check_oneshot_broadcast
> > tick_check_idle
> > irq_enter
> > do_IRQ
> > common_interrupt
> > <EOI>
> > x86_64_start_reservations
> > x86_64_start_kernel
> > RIP: clockevents_set_mode+0x18
> >
> > Matching up the Code: line of the trace with the disassembly I see..
> >
> > if (dev->mode != mode) {
> > 4c8: 39 77 38 cmp %esi,0x38(%rdi)
> >
> >
>
> diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c
> index 61d00a8..db9da73 100644
> --- a/kernel/time/tick-broadcast.c
> +++ b/kernel/time/tick-broadcast.c
> @@ -475,7 +475,8 @@ void tick_check_oneshot_broadcast(int cpu)
> if (cpumask_test_cpu(cpu, tick_broadcast_oneshot_mask)) {
> struct tick_device *td = &per_cpu(tick_cpu_device, cpu);
>
> - clockevents_set_mode(td->evtdev, CLOCK_EVT_MODE_ONESHOT);
> + if (td)
> + clockevents_set_mode(td->evtdev, CLOCK_EVT_MODE_ONESHOT);
> }
> }
>
td must be non-null, because this doesn't change anything.
a clue: If I disable CONFIG_SLUB_DEBUG, or even boot with slub_debug=- then it boots fine.
I'll bisect.
Dave
next prev parent reply other threads:[~2013-05-02 15:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 21:20 clockevents_program_event WARN_ON preventing boot Dave Jones
2013-04-30 21:37 ` Dave Jones
2013-05-02 10:37 ` Thomas Gleixner
2013-05-02 15:46 ` Dave Jones [this message]
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=20130502154621.GA23990@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).