From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Keir (Xen.org)" <keir@xen.org>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [xen-unstable bisection] complete test-i386-i386-pair
Date: Mon, 24 Oct 2011 15:42:41 +0100 [thread overview]
Message-ID: <20133.31073.66208.784286@mariner.uk.xensource.com> (raw)
In-Reply-To: <E1RIL73-0004qU-9L@woking.xci-test.com>
xen.org writes ("[xen-unstable bisection] complete test-i386-i386-pair"):
> *** Found and reproduced problem changeset ***
>
> Bug is in tree: xen http://xenbits.xen.org/staging/xen-unstable.hg
> Bug introduced: 1c8789852eaf
> Bug not present: 8269826353d8
>
>
> changeset: 23990:1c8789852eaf
> user: Jan Beulich <jbeulich@suse.com>
> date: Fri Oct 21 09:44:47 2011 +0200
>
> x86/hpet: allocate CPU masks dynamically
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Acked-by: Keir Fraser <keir@xen.org>
Looking at the log, it seems that both the source and destination host
for the migration test crashed.
http://www.chiark.greenend.org.uk/~xensrcts/logs/9471/test-i386-i386-pair/info.html
Oct 23 01:36:23.433334 (XEN) ----[ Xen-4.2-unstable x86_32p debug=y Not tainted ]----
Oct 23 01:36:44.057278 (XEN) CPU: 0
Oct 23 01:36:44.057308 (XEN) EIP: e008:[<ff146151>] __find_first_bit+0x1d/0x3c
Oct 23 01:36:44.069240 (XEN) EFLAGS: 00010246 CONTEXT: hypervisor
Oct 23 01:36:44.069273 (XEN) eax: 00000000 ebx: 00000000 ecx: 00000001 edx: 00000045
Oct 23 01:36:44.077245 (XEN) esi: ff2180e0 edi: 00000000 ebp: ff253e34 esp: ff253e2c
Oct 23 01:36:44.077282 (XEN) cr0: 8005003b cr4: 000426f0 cr3: 00bdf220 cr2: 00000000
Oct 23 01:36:44.089247 (XEN) ds: e010 es: e010 fs: 00d8 gs: 0000 ss: e010 cs: e008
Oct 23 01:36:44.097240 (XEN) Xen stack trace from esp=ff253e2c:
Oct 23 01:36:44.097271 (XEN) 00000002 ffbe4080 ff253e94 ff17fccc 00000000 00000002 bbcbc1c2 00000045
Oct 23 01:36:44.109238 (XEN) ff253fb0 ffbe4094 f3520d09 00000045 ff253ebc ff11649d ffbfdddc ff27f180
Oct 23 01:36:44.109278 (XEN) 00000000 00000000 00000000 00000000 00989680 ff27fa80 bbcbc1c2 00000000
Oct 23 01:36:44.117253 (XEN) ff2180e0 ff290080 ff253eb4 ff17f3e5 ffbe4080 ff14539a ff29d000 ff253f58
Oct 23 01:36:44.129244 (XEN) 00000002 ff253ebc ff253ee4 ff1695e0 ff290080 ff290080 ff253ee4 ff14fff5
Oct 23 01:36:44.129284 (XEN) ff290080 00000000 00000082 ff253ee4 00000000 ff2180e0 ff253f54 ff154841
Oct 23 01:36:44.137258 (XEN) 00000000 00000000 ff253f60 00000045 00000000 ffbdf000 0000001d ff27f020
Oct 23 01:36:44.149240 (XEN) ffbdf0c8 ff27f100 f30ab8f7 ff290094 00000000 00000000 00000000 ffbd9a80
Oct 23 01:36:44.157243 (XEN) ff27f100 ff264200 ffffffff ff253fb0 ff253f7c ff120011 00000000 ff253fb0
Oct 23 01:36:44.157281 (XEN) 0000e010 0000e010 00dac08b ff14cf86 ff253f60 ff253fb0 ff27f100 00000000
Oct 23 01:36:44.169273 (XEN) ff253fb0 ffffffff ff253f8c ff27f080 00f00000 ff14915d 0000e008 00000246
Oct 23 01:36:44.177260 (XEN) ff253fac ff14ab2c ff253fb8 ff253fa8 ff120083 deadbeef ff29d000 ffbdf000
Oct 23 01:36:44.177301 (XEN) ff253e38 deadbeef deadbeef 00000000 00000000 c166d350 c1663f94 00000000
Oct 23 01:36:44.189249 (XEN) 00f90000 c10023a7 00000061 00000246 c1663f84 00000069 0000007b 0000007b
Oct 23 01:36:44.197254 (XEN) 000000d8 00000000 00000000 ff29d000 00000000
Oct 23 01:36:44.197285 (XEN) Xen call trace:
Oct 23 01:36:44.209234 (XEN) [<ff146151>] __find_first_bit+0x1d/0x3c
Oct 23 01:36:44.209267 (XEN) [<ff17fccc>] handle_hpet_broadcast+0x87/0x263
Oct 23 01:36:44.217247 (XEN) [<ff17f3e5>] hpet_legacy_irq_tick+0x37/0x45
Oct 23 01:36:44.217281 (XEN) [<ff1695e0>] timer_interrupt+0x23/0x194
Oct 23 01:36:44.217314 (XEN) [<ff154841>] do_IRQ+0x4c8/0x573
Oct 23 01:36:44.229241 (XEN) [<ff14cf86>] common_interrupt+0x56/0x60
Oct 23 01:36:44.229274 (XEN) [<ff14915d>] default_idle+0x5f/0x64
Oct 23 01:36:44.237248 (XEN) [<ff14ab2c>] idle_loop+0x41/0x51
Oct 23 01:36:44.237280 (XEN)
Oct 23 01:36:44.237302 (XEN) Pagetable walk from 00000000:
Oct 23 01:36:44.237334 (XEN) L3[0x000] = 0000000123a91001 0001bf95
Oct 23 01:36:44.249238 (XEN) L2[0x000] = 0000000000000000 ffffffff
Oct 23 01:36:44.249269 (XEN)
Oct 23 01:36:44.249290 (XEN) ****************************************
Oct 23 01:36:44.257243 (XEN) Panic on CPU 0:
Oct 23 01:36:44.257269 (XEN) FATAL PAGE FAULT
Oct 23 01:36:44.257294 (XEN) [error_code=0000]
Oct 23 01:36:44.257325 (XEN) Faulting linear address: 00000000
Oct 23 01:36:44.269239 (XEN) ****************************************
Oct 23 01:36:44.269269 (XEN)
Oct 23 01:36:44.269290 (XEN) Reboot in five seconds...
next prev parent reply other threads:[~2011-10-24 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 14:02 [xen-unstable bisection] complete test-i386-i386-pair xen.org
2011-10-24 14:42 ` Ian Jackson [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-24 14:00 xen.org
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=20133.31073.66208.784286@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=keir@xen.org \
--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.