public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: WARNING: at arch/x86/kernel/smp.c:117 native_smp_send_reschedule+0x51/0x60()
Date: Tue, 1 Sep 2009 22:31:05 +0200	[thread overview]
Message-ID: <20090901203105.GH12579@kernel.dk> (raw)
In-Reply-To: <20090901143942.GA5394@hack>

On Tue, Sep 01 2009, Américo Wang wrote:
> On Mon, Aug 31, 2009 at 10:43:49PM +0200, Jens Axboe wrote:
> >Hi,
> >
> >I get this on every reboot/kexec/halt:
> >
> >WARNING: at arch/x86/kernel/smp.c:117 native_smp_send_reschedule+0x51/0x60()
> >Modules linked in: raid0 md_mod loop hid_apple usbhid mptsas mptscsih
> >mptbase scsi_transport_sas ehci_hcd uhci_hcd usbcore nls_base igb sg
> >sr_mod cdrom
> >Pid: 6998, comm: halt Not tainted 2.6.31-rc8 #105
> >Call Trace:
> > <IRQ>  [<ffffffff81023d38>] ? lapic_next_event+0x18/0x20
> > [<ffffffff810233e1>] ? native_smp_send_reschedule+0x51/0x60
> > [<ffffffff8104e7e8>] warn_slowpath_common+0x78/0xd0
> > [<ffffffff8104e84f>] warn_slowpath_null+0xf/0x20
> > [<ffffffff810233e1>] native_smp_send_reschedule+0x51/0x60
> > [<ffffffff81037ae8>] resched_task+0x68/0x80
> > [<ffffffff81041165>] resched_cpu+0x75/0x90
> > [<ffffffff8104a1db>] scheduler_tick+0x25b/0x290
> > [<ffffffff8105b8b6>] update_process_times+0x56/0x70
> > [<ffffffff81076cb6>] tick_sched_timer+0x66/0xc0
> > [<ffffffff81076c50>] ? tick_sched_timer+0x0/0xc0
> > [<ffffffff8106c351>] __run_hrtimer+0x51/0xc0
> > [<ffffffff8106d0a5>] hrtimer_interrupt+0xd5/0x1c0
> > [<ffffffff81024938>] smp_apic_timer_interrupt+0x68/0xa0
> > [<ffffffff8100ca23>] apic_timer_interrupt+0x13/0x20
> > <EOI>  [<ffffffff81028ffb>] ? x2apic_send_IPI_allbutself+0x9b/0xb0
> > [<ffffffff810234ac>] ? native_smp_send_stop+0x4c/0x90
> > [<ffffffff81022dfe>] ? native_machine_shutdown+0x5e/0x90
> > [<ffffffff81022a66>] ? native_machine_power_off+0x26/0x30
> > [<ffffffff81022a7a>] ? machine_power_off+0xa/0x10
> > [<ffffffff810619d4>] ? kernel_power_off+0x34/0x40
> > [<ffffffff81061cba>] ? sys_reboot+0x13a/0x210
> > [<ffffffff8105e83e>] ? group_send_sig_info+0x6e/0x90
> > [<ffffffff8105e8b0>] ? kill_pid_info+0x50/0xa0
> > [<ffffffff8105eb95>] ? sys_kill+0xa5/0x200
> > [<ffffffff8106d289>] ? up_read+0x9/0x10
> > [<ffffffff8102ede9>] ? do_page_fault+0x1a9/0x310
> > [<ffffffff8100bf6b>] ? system_call_fastpath+0x16/0x1b
> >
> 
> Hmm, maybe some race condition happens...
> 
> Add Ingo into Cc:.
> 
> Your .config and dmesg are appreciated.

I'll send in the .config tomorrow when the box is up again, but
unfortunately I cannot post a full dmesg from this box. If there's
anything specific you want to look, I can post that. Otherwise I'll
probably try poking at this a bit, when some idle time appears.

-- 
Jens Axboe


  reply	other threads:[~2009-09-01 20:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31 20:43 WARNING: at arch/x86/kernel/smp.c:117 native_smp_send_reschedule+0x51/0x60() Jens Axboe
2009-09-01  0:44 ` Kelly Bowa
2009-09-01  6:30   ` Jens Axboe
2009-09-01 14:39 ` Américo Wang
2009-09-01 20:31   ` Jens Axboe [this message]
2009-09-11 22:07 ` WARNING: at arch/x86/kernel/smp.c:117 Chris Webb

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=20090901203105.GH12579@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=xiyou.wangcong@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox