From: Chris Webb <chris@arachsys.com>
To: linux-kernel@vger.kernel.org
Cc: Jens Axboe <jens.axboe@oracle.com>
Subject: Re: WARNING: at arch/x86/kernel/smp.c:117
Date: Fri, 11 Sep 2009 23:07:16 +0100 [thread overview]
Message-ID: <20090911220716.GK751@arachsys.com> (raw)
In-Reply-To: <20090831204349.GE12579@kernel.dk>
Jens Axboe <jens.axboe@oracle.com> writes:
> I get this on every reboot/kexec/halt:
>
> WARNING: at arch/x86/kernel/smp.c:117 native_smp_send_reschedule+0x51/0x60()
I'm also seeing this following a system halt on the released 2.6.31 kernel
running in a qemu-kvm virtual machine, although there's no warning during
reboot there:
WARNING: at arch/x86/kernel/smp.c:117 native_smp_send_reschedule+0x25/0x51()
Hardware name:
Modules linked in:
Pid: 5256, comm: init Not tainted 2.6.31-elastic-lon-p #1
Call Trace:
<IRQ> [<ffffffff812509b4>] ? vgacon_set_cursor_size+0xfd/0x109
[<ffffffff8106220e>] warn_slowpath_common+0x77/0x8f
[<ffffffff81062235>] warn_slowpath_null+0xf/0x11
[<ffffffff8103ecb6>] native_smp_send_reschedule+0x25/0x51
[<ffffffff810540bd>] resched_task+0x63/0x65
[<ffffffff81058275>] resched_cpu+0x4a/0x5e
[<ffffffff810820c0>] ? tick_sched_timer+0x0/0x94
[<ffffffff8105e2ac>] scheduler_tick+0x182/0x232
[<ffffffff810820c0>] ? tick_sched_timer+0x0/0x94
[<ffffffff8106c3ba>] update_process_times+0x52/0x62
[<ffffffff8108212a>] tick_sched_timer+0x6a/0x94
[<ffffffff81079db1>] __run_hrtimer+0x52/0x86
[<ffffffff8107a8e7>] hrtimer_interrupt+0xf1/0x15b
[<ffffffff8103fb3b>] smp_apic_timer_interrupt+0x13/0x20
[<ffffffff8102ca23>] apic_timer_interrupt+0x13/0x20
<EOI> [<ffffffff81237517>] ? delay_tsc+0x38/0xd1
[<ffffffff81237425>] ? __delay+0xa/0xc
[<ffffffff81237464>] ? __const_udelay+0x3d/0x3f
[<ffffffff8103ed97>] ? native_smp_send_stop+0x51/0x79
[<ffffffff8103e811>] ? native_machine_shutdown+0x49/0x60
[<ffffffff8103e53e>] ? native_shutdown+0xa/0xc
[<ffffffff8103e608>] ? native_machine_halt+0x9/0x12
[<ffffffff8103e590>] ? machine_halt+0xa/0xc
[<ffffffff81071612>] ? kernel_halt+0x26/0x28
[<ffffffff8107174a>] ? sys_reboot+0xe6/0x152
[<ffffffff810bfce1>] ? handle_mm_fault+0x34e/0x6e1
[<ffffffff814b816f>] ? page_fault+0x1f/0x30
[<ffffffff81234623>] ? __up_read+0x9c/0xa5
[<ffffffff8107a9ff>] ? up_read+0x9/0xb
[<ffffffff81046483>] ? do_page_fault+0x230/0x260
[<ffffffff814b816f>] ? page_fault+0x1f/0x30
[<ffffffff8102bf6b>] ? system_call_fastpath+0x16/0x1b
Is this likely to be a harmless warning or indicative of a more serious
problem with this kernel version (or config)?
Cheers,
Chris.
prev parent reply other threads:[~2009-09-11 22:07 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
2009-09-11 22:07 ` Chris Webb [this message]
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=20090911220716.GK751@arachsys.com \
--to=chris@arachsys.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.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.