From: Marcelo Tosatti <mtosatti@redhat.com>
To: Tharindu Rukshan Bamunuarachchi <btharindu@gmail.com>
Cc: x86@kernel.org, kvm@vger.kernel.org
Subject: Re: WARNING: at arch/x86/kernel/apic/apic.c:1238 setup_local_APIC+0x169/0x24b()
Date: Mon, 23 Aug 2010 18:21:58 -0300 [thread overview]
Message-ID: <20100823212158.GD32690@amt.cnet> (raw)
In-Reply-To: <AANLkTimEmkY_T-sd8JMhYUrstnqmHroWrVfus=2GDd+4@mail.gmail.com>
On Tue, Aug 17, 2010 at 07:09:36PM +0100, Tharindu Rukshan Bamunuarachchi wrote:
> hi,
>
> I got following message after booting 2.6.35 on KVM.
> Should I report this to QEMU user list ? Any clue on debugging ?
>
> However VM works fine even with message.
>
> cheers
> tharindu
Please provide host hardware information (/proc/cpuinfo), full qemu
command line and full dmesg of guest.
>
>
> [ 0.184000] Setting APIC routing to flat
> [ 0.188000] ------------[ cut here ]------------
> [ 0.192000] WARNING: at arch/x86/kernel/apic/apic.c:1238
> setup_local_APIC+0x169/0x24b()
> [ 0.196000] Hardware name: Bochs
> [ 0.200000] Pid: 1, comm: swapper Not tainted 2.6.35-tinux+ #85
> [ 0.204000] Call Trace:
> [ 0.204000] [<ffffffff8103e0b5>] warn_slowpath_common+0x75/0xb0
> [ 0.208000] [<ffffffff8103e1b5>] warn_slowpath_null+0x15/0x20
> [ 0.212000] [<ffffffff816b8f84>] setup_local_APIC+0x169/0x24b
> [ 0.216000] [<ffffffff81696f59>] native_smp_prepare_cpus+0x322/0x3ff
> [ 0.220000] [<ffffffff81691ce5>] kernel_init+0x57/0x1bd
> [ 0.220000] [<ffffffff81003b84>] kernel_thread_helper+0x4/0x10
> [ 0.224000] [<ffffffff81691c8e>] ? kernel_init+0x0/0x1bd
> [ 0.228000] [<ffffffff81003b80>] ? kernel_thread_helper+0x0/0x10
> [ 0.232000] ---[ end trace 4eaa2a86a8e2da22 ]---
> [ 0.240000] alloc irq_desc for 33 on node 0
> [ 0.240000] alloc kstat_irqs on node 0
> [ 0.240000] alloc irq_desc for 35 on node 0
> [ 0.240000] alloc kstat_irqs on node 0
> [ 0.240000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
> [ 0.280000] CPU0: Intel QEMU Virtual CPU version 0.12.3 stepping 03
> [ 0.400000] NMI watchdog failed to create perf event on cpu0:
> ffffffffffffffed
> [ 0.412000] Booting Node 0, Processors #1 Ok.
> [ 0.052000] ------------[ cut here ]------------
> [ 0.052000] WARNING: at arch/x86/kernel/apic/apic.c:1238
> setup_local_APIC+0x169/0x24b()
> [ 0.052000] Hardware name: Bochs
> [ 0.052000] Pid: 0, comm: kworker/0:0 Tainted: G W 2.6.35-tinux+ #85
> [ 0.052000] Call Trace:
> [ 0.052000] [<ffffffff8103e0b5>] warn_slowpath_common+0x75/0xb0
> [ 0.052000] [<ffffffff8103e1b5>] warn_slowpath_null+0x15/0x20
> [ 0.052000] [<ffffffff816b8f84>] setup_local_APIC+0x169/0x24b
> [ 0.052000] [<ffffffff816b8621>] start_secondary+0x113/0x257
> [ 0.052000] ---[ end trace 4eaa2a86a8e2da23 ]---
> [ 0.528000] NMI watchdog failed to create perf event on cpu1:
> ffffffffffffffed
> [ 0.536000] Brought up 2 CPUs
> [ 0.540000] Total of 2 processors activated (2490.36 BogoMIPS).
next prev parent reply other threads:[~2010-08-23 23:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 18:09 WARNING: at arch/x86/kernel/apic/apic.c:1238 setup_local_APIC+0x169/0x24b() Tharindu Rukshan Bamunuarachchi
2010-08-23 21:21 ` Marcelo Tosatti [this message]
2010-08-24 3:14 ` Tharindu Rukshan Bamunuarachchi
2010-08-24 13:22 ` Marcelo Tosatti
2010-08-24 15:11 ` Tharindu Rukshan Bamunuarachchi
2010-08-24 15:41 ` Tharindu Rukshan Bamunuarachchi
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=20100823212158.GD32690@amt.cnet \
--to=mtosatti@redhat.com \
--cc=btharindu@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=x86@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.