public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: WARNING: at kernel/cpu/idle.c:96
Date: Thu, 2 May 2013 16:06:54 +0200	[thread overview]
Message-ID: <20130502140654.GA509@x4> (raw)
In-Reply-To: <alpine.LFD.2.02.1305021557030.3972@ionos>

On 2013.05.02 at 15:58 +0200, Thomas Gleixner wrote:
> On Thu, 2 May 2013, Markus Trippelsdorf wrote:
> > On 2013.05.02 at 12:43 +0200, Thomas Gleixner wrote:
> > > On Tue, 30 Apr 2013, Markus Trippelsdorf wrote:
> > > 
> > > > Just booted todays git tree and got the following warning:
> > > > 
> > > > ------------[ cut here ]------------
> > > > WARNING: at kernel/cpu/idle.c:96 cpu_startup_entry+0x14d/0x160()
> > > > Hardware name: System Product Name
> > > > Pid: 0, comm: swapper/2 Not tainted 3.9.0-03462-gab86e97-dirty #424
> > > > Call Trace:
> > > > smpboot: Booting Node   0, Processors  #1 #2
> > > >  [<ffffffff8105b7c0>] ? warn_slowpath_common+0x60/0xa0
> > > >  [<ffffffff8108c26d>] ? cpu_startup_entry+0x14d/0x160
> > > > ---[ end trace 40a24a5550891913 ]---
> > > 
> > > Fix below.
> > 
> > Unfortunately the fix doesn't work:
> 
> Moo. I missed amd_e400_idle() returning early w/o enabling interrupts.

This fixes the issue. Thanks.

-- 
Markus

  reply	other threads:[~2013-05-02 14:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30 15:52 WARNING: at kernel/cpu/idle.c:96 Markus Trippelsdorf
2013-05-02 10:43 ` Thomas Gleixner
2013-05-02 11:30   ` Markus Trippelsdorf
2013-05-02 13:58     ` Thomas Gleixner
2013-05-02 14:06       ` Markus Trippelsdorf [this message]
2013-05-07 14:04         ` Borislav Petkov
2013-05-07 14:32       ` [tip:x86/urgent] x86: Fix idle consolidation fallout 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=20130502140654.GA509@x4 \
    --to=markus@trippelsdorf.de \
    --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