From: Jeremy Fitzhardinge <jeremy@goop.org>
To: v.tolstov@selfip.ru
Cc: xen-devel@lists.xensource.com
Subject: Re: xen 2.6.32.x 686 pae, error after migration
Date: Mon, 22 Nov 2010 10:32:31 -0800 [thread overview]
Message-ID: <4CEAB73F.9030207@goop.org> (raw)
In-Reply-To: <1290341950.26628.3.camel@mobile>
On 11/21/2010 04:19 AM, Vasiliy G Tolstov wrote:
> Hello. Now i'm try to build 686 kernel with pae and check migration.
> After successeful migration process i found error im messages:
>
> Nov 21 12:10:22 21-390 kernel: Pid: 0, comm: swapper Not tainted
> 2.6.32.25 #5
It was printing a warning message, but unfortunately the actual warning
was cut off. Could you reproduce it and try to catch the full output?
Thanks,
J
> Nov 21 12:10:22 21-390 kernel: Call Trace:
> Nov 21 12:10:22 21-390 kernel: [<c106af53>] ? __lock_acquire+0x517/0xbd6
> Nov 21 12:10:22 21-390 kernel: [<c103e2d3>] warn_slowpath_common
> +0x65/0x95
> Nov 21 12:10:22 21-390 kernel: [<c103e315>] warn_slowpath_null+0x12/0x15
> Nov 21 12:10:22 21-390 kernel: [<c106af53>] __lock_acquire+0x517/0xbd6
> Nov 21 12:10:22 21-390 kernel: [<c105e9ca>] ? sched_clock_cpu
> +0x130/0x144
> Nov 21 12:10:22 21-390 kernel: [<c1006bab>] ? xen_force_evtchn_callback
> +0xf/0x14
> Nov 21 12:10:22 21-390 kernel: [<c11a278b>] ? debug_object_deactivate
> +0x9c/0xc7
> Nov 21 12:10:22 21-390 kernel: [<c1006bab>] ? xen_force_evtchn_callback
> +0xf/0x14
> Nov 21 12:10:22 21-390 kernel: [<c104bf9e>] ? run_timer_softirq
> +0x14b/0x23d
> Nov 21 12:10:22 21-390 kernel: [<c1007278>] ? check_events+0x8/0xc
> Nov 21 12:10:22 21-390 kernel: [<c1068800>] ? trace_hardirqs_off+0xb/0xd
> Nov 21 12:10:22 21-390 kernel: [<c105ea1d>] ? cpu_clock+0x3f/0x5b
> Nov 21 12:10:22 21-390 kernel: [<c1301bd9>] ? _spin_unlock_irqrestore
> +0x3d/0x51
> Nov 21 12:10:22 21-390 kernel: [<c106b6a6>] lock_acquire+0x94/0xb1
> Nov 21 12:10:22 21-390 kernel: [<c104bf84>] ? run_timer_softirq
> +0x131/0x23d
> Nov 21 12:10:22 21-390 kernel: [<c104bfd0>] run_timer_softirq
> +0x17d/0x23d
> Nov 21 12:10:22 21-390 kernel: [<c104bf84>] ? run_timer_softirq
> +0x131/0x23d
> Nov 21 12:10:22 21-390 kernel: [<ee2daf1b>] ? mld_ifc_timer_expire
> +0x0/0x217 [ipv6]
> Nov 21 12:10:22 21-390 kernel: [<c1044bff>] __do_softirq+0xbc/0x16f
> Nov 21 12:10:22 21-390 kernel: [<c1044cf0>] do_softirq+0x3e/0x63
> Nov 21 12:10:22 21-390 kernel: [<c1044e0b>] irq_exit+0x3a/0x6d
> Nov 21 12:10:22 21-390 kernel: [<c11f2961>] xen_evtchn_do_upcall
> +0x2a/0x35
> Nov 21 12:10:22 21-390 kernel: [<c1009c9b>] xen_do_upcall+0x7/0xc
> Nov 21 12:10:22 21-390 kernel: [<c10023a7>] ? hypercall_page
> +0x3a7/0x100a
> Nov 21 12:10:22 21-390 kernel: [<c1006c40>] ? xen_safe_halt+0x12/0x1f
> Nov 21 12:10:22 21-390 kernel: [<c100440b>] xen_idle+0x3b/0x4c
> Nov 21 12:10:22 21-390 kernel: [<c100836e>] cpu_idle+0x53/0x6d
> Nov 21 12:10:22 21-390 kernel: [<c12f88ef>] cpu_bringup_and_idle
> +0x12/0x14
> Nov 21 12:10:22 21-390 kernel: ---[ end trace d07739eb8e0a6b21 ]---
>
> Domu config in attached file. (commit
> 481bd8e6b8dafed2ea445e8cde2abbbb95b49ec1
> )
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2010-11-22 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 12:19 xen 2.6.32.x 686 pae, error after migration Vasiliy G Tolstov
2010-11-22 18:32 ` Jeremy Fitzhardinge [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=4CEAB73F.9030207@goop.org \
--to=jeremy@goop.org \
--cc=v.tolstov@selfip.ru \
--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.