From: Dave Jones <davej@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Yinghai Lu <yinghai@kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: clockevents_program_event WARN_ON preventing boot.
Date: Fri, 3 May 2013 16:10:37 -0400 [thread overview]
Message-ID: <20130503201037.GA17652@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1305032015060.2990@ionos>
On Fri, May 03, 2013 at 08:32:58PM +0200, Thomas Gleixner wrote:
> On Fri, 3 May 2013, Dave Jones wrote:
> > On Fri, May 03, 2013 at 12:49:20AM +0200, Thomas Gleixner wrote:
> >
> > > I'm fundamentally confused and Daves observation about slub debug does
> > > not make it less confusing.
> > >
> > > It'd be nice if you could add some more instrumentation or bisect the
> > > issue.
> >
> > Here's what I ended up with..
> > b352bc1cbc29134a356b5c16ee2281807a7b984e is the first bad commit
> > commit b352bc1cbc29134a356b5c16ee2281807a7b984e
> > Author: Thomas Gleixner <tglx@linutronix.de>
> > Date: Tue Mar 5 14:25:32 2013 +0100
> >
> > tick: Convert broadcast cpu bitmaps to cpumask_var_t
> >
> > Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> > Link: http://lkml.kernel.org/r/20130306111537.366394000@linutronix.de
> > Cc: Rusty Russell <rusty@rustcorp.com.au>
> >
>
> I bet you have CONFIG_CPUMASK_OFFSTACK enabled.
>
> /me is a moron and rumages for a brown paperbag.
>
> Patch below.
Works for me.
Tested-by: Dave Jones <davej@redhat.com>
next prev parent reply other threads:[~2013-05-03 20:10 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
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 [this message]
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=20130503201037.GA17652@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.