From: Prarit Bhargava <prarit@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
athorlton@sgi.com, CAI Qian <caiqian@redhat.com>
Subject: Re: BUG: tick device NULL pointer during system initialization and shutdown
Date: Tue, 25 Jun 2013 19:50:23 -0400 [thread overview]
Message-ID: <51CA2CBF.70404@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306241551020.4013@ionos.tec.linutronix.de>
On 06/24/2013 09:57 AM, Thomas Gleixner wrote:
> On Tue, 18 Jun 2013, Prarit Bhargava wrote:
>
>> Similar panics reported during bringup here:
>>
>> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-May/166205.html
>> http://lkml.org/lkml/2013/5/8/342
>>
>> I've seen this a few times on 3.10 based kernels.
>>
>> [ 175.842027] Disabling non-boot CPUs ...
>> [ 475.827017] BUG: unable to handle kernel NULL pointer dereference at
>> 0000000000000048
>
> That looks like a stale bit in tick_broadcast_force_mask.
>
> Does the patch below fix it?
>
Thomas,
Thanks for the patch.
The reproducibility appears to be quite low. I'm seeing this roughly 1 time
every six hours of continuous system reboots. I'm testing right now with your
patch. I'll update the thread in a couple of days...
P.
next prev parent reply other threads:[~2013-06-25 23:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 18:46 BUG: tick device NULL pointer during system initialization and shutdown Prarit Bhargava
2013-06-24 13:57 ` Thomas Gleixner
2013-06-25 23:50 ` Prarit Bhargava [this message]
2013-06-26 11:05 ` Thomas Gleixner
2013-06-27 17:04 ` Prarit Bhargava
2013-06-28 10:52 ` Thomas Gleixner
2013-07-01 13:07 ` Prarit Bhargava
2013-07-01 13:30 ` Thomas Gleixner
2013-07-01 15:41 ` Paul E. McKenney
2013-07-08 13:04 ` Prarit Bhargava
2013-07-02 12:31 ` [tip:timers/core] tick: Make oneshot broadcast robust vs. CPU offlining tip-bot for Thomas Gleixner
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=51CA2CBF.70404@redhat.com \
--to=prarit@redhat.com \
--cc=athorlton@sgi.com \
--cc=caiqian@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