All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Prarit Bhargava <prarit@redhat.com>
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: Fri, 28 Jun 2013 12:52:02 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1306281250270.4013@ionos.tec.linutronix.de> (raw)
In-Reply-To: <51CC708B.7040605@redhat.com>

On Thu, 27 Jun 2013, Prarit Bhargava wrote:
> On 06/26/2013 07:05 AM, Thomas Gleixner wrote:
> > Subject: tick: Make oneshot broadcast robust vs. CPU offlining
> > From: Thomas Gleixner <tglx@linutronix.de>
> > Date: Wed, 26 Jun 2013 12:17:32 +0200
> > 
> > In periodic mode we remove offline cpus from the broadcast propagation
> > mask. In oneshot mode we fail to do so. This was not a problem so far,
> > but the recent changes to the broadcast propagation introduced a
> > constellation which can result in a NULL pointer dereference.
> > 
> 
> Unfortunately this patch causes an NMI watchdog during system shutdown.  Most of
> the CPUs are in start_secondary+0x254/0x256.

Huch. Did the warning in the broadcast code trigger before that?
 
Thanks,

	tglx

  reply	other threads:[~2013-06-28 10:52 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
2013-06-26 11:05     ` Thomas Gleixner
2013-06-27 17:04       ` Prarit Bhargava
2013-06-28 10:52         ` Thomas Gleixner [this message]
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=alpine.DEB.2.02.1306281250270.4013@ionos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=athorlton@sgi.com \
    --cc=caiqian@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prarit@redhat.com \
    /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.