From: Mike Wright <mike.wright@mailinator.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: trace in dmesg
Date: Wed, 29 Jun 2011 10:49:58 -0700 [thread overview]
Message-ID: <4E0B65C6.2060106@mailinator.com> (raw)
Hi all,
I'm (finally, yeah!!!) running xen-4.1.1 with linux-3.0.0-rc5 in
runlevel 5 and so far seems indistinguishable from bare metal.
However, this is in dmesg, and I wonder if it is important.
[ 0.014109] ------------[ cut here ]------------
[ 0.014144] WARNING: at arch/x86/xen/enlighten.c:714
xen_apic_write+0x1a/0x1c()
[ 0.014149] Hardware name: GA-890GPA-UD3H
[ 0.014152] Modules linked in:
[ 0.014158] Pid: 1, comm: swapper Not tainted 3.0.0-rc4 #1
[ 0.014163] Call Trace:
[ 0.014170] [<ffffffff8104ce8e>] warn_slowpath_common+0x85/0x9d
[ 0.014177] [<ffffffff8104cec0>] warn_slowpath_null+0x1a/0x1c
[ 0.014182] [<ffffffff81003450>] xen_apic_write+0x1a/0x1c
[ 0.014188] [<ffffffff81018caa>] apic_write.clone.15+0x1b/0x1d
[ 0.014193] [<ffffffff81019567>] perf_events_lapic_init+0x1c/0x1e
[ 0.014200] [<ffffffff81b6311f>] init_hw_perf_events+0xd86/0xeff
[ 0.014206] [<ffffffff8104e984>] ? set_cpu_present+0x1a/0x2a
[ 0.014211] [<ffffffff81b62399>] ? check_bugs+0x2d/0x2d
[ 0.014217] [<ffffffff81002190>] do_one_initcall+0x7f/0x137
[ 0.014223] [<ffffffff81b59c3e>] kernel_init+0x93/0x157
[ 0.014229] [<ffffffff81048230>] ? schedule_tail+0x31/0x65
[ 0.014235] [<ffffffff81485b64>] kernel_thread_helper+0x4/0x10
[ 0.014241] [<ffffffff81484c63>] ? int_ret_from_sys_call+0x7/0x1b
[ 0.014248] [<ffffffff8147e721>] ? retint_restore_args+0x5/0x6
[ 0.014253] [<ffffffff81485b60>] ? gs_change+0x13/0x13
[ 0.014261] ---[ end trace a7919e7f17c0a725 ]---
Thanks for your attention,
Mike Wright
next reply other threads:[~2011-06-29 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 17:49 Mike Wright [this message]
2011-06-30 15:00 ` trace in dmesg Konrad Rzeszutek Wilk
2011-06-30 16:18 ` Mike Wright
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=4E0B65C6.2060106@mailinator.com \
--to=mike.wright@mailinator.com \
--cc=xen-devel@lists.xensource.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.