flight 6413 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/6413/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-amd64-pair 8 xen-boot/dst_host fail REGR. vs. 6396
test-amd64-amd64-pair 7 xen-boot/src_host fail REGR. vs. 6396
test-amd64-amd64-xl-win 5 xen-boot fail REGR. vs. 6396
test-amd64-i386-rhel6hvm-intel 5 xen-boot fail REGR. vs. 6396
test-amd64-i386-win-vcpus1 5 xen-boot fail REGR. vs. 6396
test-amd64-xcpkern-i386-pair 8 xen-boot/dst_host fail REGR. vs. 6396
test-amd64-xcpkern-i386-pair 7 xen-boot/src_host fail REGR. vs. 6396
test-amd64-xcpkern-i386-pv 5 xen-boot fail REGR. vs. 6396
test-amd64-xcpkern-i386-rhel6hvm-intel 5 xen-boot fail REGR. vs. 6396
test-amd64-xcpkern-i386-xl 5 xen-boot fail REGR. vs. 6396
test-i386-i386-pv 5 xen-boot fail REGR. vs. 6396
test-i386-i386-xl-win 5 xen-boot fail REGR. vs. 6396
test-i386-xcpkern-i386-xl 5 xen-boot fail REGR. vs. 6396
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-amd64-win 16 leak-check/check fail never pass
test-amd64-i386-rhel6hvm-amd 8 guest-saverestore fail never pass
test-amd64-i386-win 16 leak-check/check fail never pass
test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass
test-amd64-xcpkern-i386-rhel6hvm-amd 8 guest-saverestore fail never pass
test-amd64-xcpkern-i386-win 16 leak-check/check fail never pass
test-amd64-xcpkern-i386-xl-win 13 guest-stop fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-i386-xcpkern-i386-win 16 leak-check/check fail never pass
version targeted for testing:
xen 84bacd800bf8
baseline version:
xen a8fee4ad3ad0
------------------------------------------------------------
People who touched revisions under test:
Ian Jackson <ian.jackson@eu.citrix.com>
Jan Beulich <jbeulich@novell.com>
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Wei Gang <gang.wei@intel.com>
------------------------------------------------------------
jobs:
build-i386-xcpkern pass
build-amd64 pass
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl pass
test-amd64-i386-xl pass
test-i386-i386-xl pass
test-amd64-xcpkern-i386-xl fail
test-i386-xcpkern-i386-xl fail
test-amd64-i386-rhel6hvm-amd fail
test-amd64-xcpkern-i386-rhel6hvm-amd fail
test-amd64-i386-xl-credit2 pass
test-amd64-xcpkern-i386-xl-credit2 pass
test-amd64-i386-rhel6hvm-intel fail
test-amd64-xcpkern-i386-rhel6hvm-intel fail
test-amd64-i386-xl-multivcpu pass
test-amd64-xcpkern-i386-xl-multivcpu pass
test-amd64-amd64-pair fail
test-amd64-i386-pair pass
test-i386-i386-pair pass
test-amd64-xcpkern-i386-pair fail
test-i386-xcpkern-i386-pair pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-i386-i386-pv fail
test-amd64-xcpkern-i386-pv fail
test-i386-xcpkern-i386-pv pass
test-amd64-i386-win-vcpus1 fail
test-amd64-i386-xl-win-vcpus1 fail
test-amd64-amd64-win fail
test-amd64-i386-win fail
test-i386-i386-win fail
test-amd64-xcpkern-i386-win fail
test-i386-xcpkern-i386-win fail
test-amd64-amd64-xl-win fail
test-i386-i386-xl-win fail
test-amd64-xcpkern-i386-xl-win fail
------------------------------------------------------------
sg-report-flight on woking.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images
Logs, config files, etc. are available at
http://www.chiark.greenend.org.uk/~xensrcts/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
Not pushing.
------------------------------------------------------------
changeset: 23033:84bacd800bf8
tag: tip
user: Jan Beulich <jbeulich@novell.com>
date: Sat Mar 12 13:20:51 2011 +0000
x86/HPET: adjust types
''unsigned int'' is better suited as an array index on
x86-64.
''u32'' produces better code than ''unsigned
long'' on x86-64, so use the
former for storing 32-bit values read from the hardware.
this_cpu() uses an implicit smp_processor_id(), and hence using
per_cpu() when the result of smp_processor_id() is already available
is more efficient.
Fold one case of cpu_isset()+cpu_clear() into cpu_test_and_clear().
Drop the unused return value of evt_do_broadcast().
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Acked-by: Wei Gang <gang.wei@intel.com>
changeset: 23032:ac572e1df261
user: Jan Beulich <jbeulich@novell.com>
date: Sat Mar 12 13:20:11 2011 +0000
x86/HPET: use dynamic allocation for hpet_events[]
Typically there are far less than 32 counters available, and hence
there''s no use in wasting the memory on (almost) every system.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Acked-by: Wei Gang <gang.wei@intel.com>
changeset: 23031:5263151fba9b
user: Jan Beulich <jbeulich@novell.com>
date: Sat Mar 12 13:19:34 2011 +0000
x86/HPET: cleanup
- separate init and resume code paths (so that the [larger] init parts
can go init .init.* sections)
- drop the separate legacy_hpet_event object, as we can easily re-use
the first slot of hpet_events[] for that purpose (the whole array is
otherwise unused when the legacy code is being used)
- use section placement attributes where reasonable
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Acked-by: Wei Gang <gang.wei@intel.com>
changeset: 23030:87aa1277eae0
user: Jan Beulich <jbeulich@novell.com>
date: Sat Mar 12 13:19:02 2011 +0000
x86/HPET: fix initialization order
At least the legacy path can enter its interrupt handler callout while
initialization is still in progress - that handler checks whether
->event_handler is non-NULL, and hence all other initialization must
happen before setting this field.
Do the same to the MSI initialization just in case (and to keep the
code in sync).
Signed-off-by: Jan Beulich <jbeulich@novell.com>
changeset: 23029:a8fee4ad3ad0
user: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
date: Fri Mar 11 18:22:23 2011 +0000
libxl: do not try to use blktap with qdisk
libxl_device_disk_add tries to use blktap when available even for qdisk
devices, this patch fixes it.
Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
(qemu changes not included)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Ian Jackson
2011-Mar-14 17:22 UTC
[Xen-devel] Re: [xen-unstable test] 6413: regressions - FAIL
Ian Jackson writes ("[xen-unstable test] 6413: regressions -
FAIL"):> Tests which did not succeed and are blocking:
> test-amd64-amd64-xl-win 5 xen-boot fail REGR. vs. 6396
Xen boot crash. Lots of these ...
Ian.
Mar 13 23:29:31.091587 (XEN) Brought up 8 CPUs
Mar 13 23:29:31.205401 (XEN) Testing NMI watchdog --- CPU#0 okay. CPU#1 stuck.
CPU#2 stuck. CPU#3 stuck. CPU#4 stuck. CPU#5 stuck. CPU#6 s
tuck. CPU#7 stuck.
Mar 13 23:29:31.369445 (XEN) Xen BUG at hpet.c:252
Mar 13 23:29:31.369492 (XEN) ----[ Xen-4.1.0-rc7-pre x86_64 debug=y Not
tainted ]----
Mar 13 23:29:31.381434 (XEN) CPU: 0
Mar 13 23:29:31.381473 (XEN) RIP: e008:[<ffff82c480195228>]
hpet_msi_unmask+0x1f/0x51
Mar 13 23:29:31.389418 (XEN) RFLAGS: 0000000000010046 CONTEXT: hypervisor
Mar 13 23:29:31.389475 (XEN) rax: 0000000000000000 rbx: ffff830239380d00
rcx: 0000000000000001
Mar 13 23:29:31.401458 (XEN) rdx: ffff830239312980 rsi: 0000000000000001
rdi: 0000000000000019
Mar 13 23:29:31.401525 (XEN) rbp: ffff82c480297ce8 rsp: ffff82c480297ce8 r8:
000000000000001e
Mar 13 23:29:31.409446 (XEN) r9: 0000000000000038 r10: 00007d0a00000000
r11: 0000000000000001
Mar 13 23:29:31.421428 (XEN) r12: ffff830239380d34 r13: 0000000000000286
r14: 0000000000000019
Mar 13 23:29:31.429410 (XEN) r15: ffff830239312dd0 cr0: 000000008005003b
cr4: 00000000000026f0
Mar 13 23:29:31.429477 (XEN) cr3: 00000000bf49c000 cr2: 0000000000000000
Mar 13 23:29:31.441419 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss:
0000 cs: e008
Mar 13 23:29:31.441484 (XEN) Xen stack trace from rsp=ffff82c480297ce8:
Mar 13 23:29:31.449422 (XEN) ffff82c480297cf8 ffff82c48019531b
ffff82c480297d38 ffff82c480160358
Mar 13 23:29:31.449490 (XEN) ffff82c480297d38 00000000fffffff4
0000000000000019 ffff82c480195428
Mar 13 23:29:31.461442 (XEN) ffff82c48022a42b ffff830239312980
ffff82c480297d78 ffff82c4801610c8
Mar 13 23:29:31.469426 (XEN) ffff830239312dd0 0000000000000019
0000000000000000 0000000000000100
Mar 13 23:29:31.469493 (XEN) 0000000000000000 ffff830239312980
ffff82c480297dd8 ffff82c4802743ec
Mar 13 23:29:31.481445 (XEN) 0000000000000086 0000000000da7a63
0000001980123b91 0000000000000064
Mar 13 23:29:31.489429 (XEN) 0000000800000001 ffff82c480274222
ffff82c48028a8d0 ffff82c480239358
Mar 13 23:29:31.489496 (XEN) ffff82c480246c90 0000000000000007
ffff82c480297df8 ffff82c480178abe
Mar 13 23:29:31.501449 (XEN) ffff82c480246c90 ffff82c48028a7f8
ffff82c480297e08 ffff82c480273567
Mar 13 23:29:31.509432 (XEN) ffff82c480297e28 ffff82c480257221
0000000000000080 ffff82c4802474a0
Mar 13 23:29:31.509500 (XEN) ffff82c480297f08 ffff82c480271fb6
00000000002d1a00 ffffffff00000000
Mar 13 23:29:31.521451 (XEN) 000000000007bf20 0000000000000000
0000000000000000 ffff83000007bdc0
Mar 13 23:29:31.529435 (XEN) ffff83000007bfb0 ffff83000007bf20
0000000000f23000 0100000000000000
Mar 13 23:29:31.541417 (XEN) 00000000bf200000 0000000000000000
0000000000000000 ffff82c4802872e0
Mar 13 23:29:31.541484 (XEN) ffffffff00000000 0000000001000000
0000000800000000 000000010000006e
Mar 13 23:29:31.549437 (XEN) 0000000000000003 00000000000002f8
0000000000000000 0000000000000000
Mar 13 23:29:31.561422 (XEN) 0000000000000000 0000000000000000
0000000000000000 0000000000000000
Mar 13 23:29:31.561488 (XEN) 0000000000067e9c ffff82c4801000b5
0000000000000000 0000000000000000
Mar 13 23:29:31.569440 (XEN) 0000000000000000 0000000000000000
0000000000000000 0000000000000000
Mar 13 23:29:31.581485 (XEN) 0000000000000000 0000000000000000
0000000000000000 0000000000000000
Mar 13 23:29:31.581552 (XEN) Xen call trace:
Mar 13 23:29:31.581594 (XEN) [<ffff82c480195228>]
hpet_msi_unmask+0x1f/0x51
Mar 13 23:29:31.589448 (XEN) [<ffff82c48019531b>]
hpet_msi_startup+0x9/0x10
Mar 13 23:29:31.589507 (XEN) [<ffff82c480160358>] setup_irq+0x72/0x98
Mar 13 23:29:31.601445 (XEN) [<ffff82c4801610c8>] request_irq+0x70/0x9f
Mar 13 23:29:31.601502 (XEN) [<ffff82c4802743ec>]
hpet_broadcast_init+0x1ca/0x44e
Mar 13 23:29:31.609446 (XEN) [<ffff82c480178abe>]
_disable_pit_irq+0x34/0x89
Mar 13 23:29:31.609505 (XEN) [<ffff82c480273567>]
disable_pit_irq+0x10/0x2e
Mar 13 23:29:31.621447 (XEN) [<ffff82c480257221>]
do_initcalls+0x22/0x30
Mar 13 23:29:31.621504 (XEN) [<ffff82c480271fb6>]
__start_xen+0x2fcd/0x32c2
Mar 13 23:29:31.625845 (XEN)
Mar 13 23:29:31.625881 (XEN)
Mar 13 23:29:31.625915 (XEN) ****************************************
Mar 13 23:29:31.629437 (XEN) Panic on CPU 0:
Mar 13 23:29:31.633827 (XEN) Xen BUG at hpet.c:252
Mar 13 23:29:31.637429 (XEN) ****************************************
Mar 13 23:29:31.641840 (XEN)
Mar 13 23:29:31.645416 (XEN) Reboot in five seconds...
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Keir Fraser
2011-Mar-14 17:34 UTC
Re: [Xen-devel] Re: [xen-unstable test] 6413: regressions - FAIL
On 14/03/2011 17:22, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:> Ian Jackson writes ("[xen-unstable test] 6413: regressions - FAIL"): >> Tests which did not succeed and are blocking: >> test-amd64-amd64-xl-win 5 xen-boot fail REGR. vs. 6396 > > Xen boot crash. Lots of these ...This is most definitely due to one of c/s 23031, 23032, or 23033 (patches 2-4 of Jan''s recent series updating the HPET management code). Over to Jan... -- Keir> Ian. > > Mar 13 23:29:31.091587 (XEN) Brought up 8 CPUs > Mar 13 23:29:31.205401 (XEN) Testing NMI watchdog --- CPU#0 okay. CPU#1 stuck. > CPU#2 stuck. CPU#3 stuck. CPU#4 stuck. CPU#5 stuck. CPU#6 s > tuck. CPU#7 stuck. > Mar 13 23:29:31.369445 (XEN) Xen BUG at hpet.c:252 > Mar 13 23:29:31.369492 (XEN) ----[ Xen-4.1.0-rc7-pre x86_64 debug=y Not > tainted ]---- > Mar 13 23:29:31.381434 (XEN) CPU: 0 > Mar 13 23:29:31.381473 (XEN) RIP: e008:[<ffff82c480195228>] > hpet_msi_unmask+0x1f/0x51 > Mar 13 23:29:31.389418 (XEN) RFLAGS: 0000000000010046 CONTEXT: hypervisor > Mar 13 23:29:31.389475 (XEN) rax: 0000000000000000 rbx: ffff830239380d00 > rcx: 0000000000000001 > Mar 13 23:29:31.401458 (XEN) rdx: ffff830239312980 rsi: 0000000000000001 > rdi: 0000000000000019 > Mar 13 23:29:31.401525 (XEN) rbp: ffff82c480297ce8 rsp: ffff82c480297ce8 > r8: 000000000000001e > Mar 13 23:29:31.409446 (XEN) r9: 0000000000000038 r10: 00007d0a00000000 > r11: 0000000000000001 > Mar 13 23:29:31.421428 (XEN) r12: ffff830239380d34 r13: 0000000000000286 > r14: 0000000000000019 > Mar 13 23:29:31.429410 (XEN) r15: ffff830239312dd0 cr0: 000000008005003b > cr4: 00000000000026f0 > Mar 13 23:29:31.429477 (XEN) cr3: 00000000bf49c000 cr2: 0000000000000000 > Mar 13 23:29:31.441419 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: > 0000 cs: e008 > Mar 13 23:29:31.441484 (XEN) Xen stack trace from rsp=ffff82c480297ce8: > Mar 13 23:29:31.449422 (XEN) ffff82c480297cf8 ffff82c48019531b > ffff82c480297d38 ffff82c480160358 > Mar 13 23:29:31.449490 (XEN) ffff82c480297d38 00000000fffffff4 > 0000000000000019 ffff82c480195428 > Mar 13 23:29:31.461442 (XEN) ffff82c48022a42b ffff830239312980 > ffff82c480297d78 ffff82c4801610c8 > Mar 13 23:29:31.469426 (XEN) ffff830239312dd0 0000000000000019 > 0000000000000000 0000000000000100 > Mar 13 23:29:31.469493 (XEN) 0000000000000000 ffff830239312980 > ffff82c480297dd8 ffff82c4802743ec > Mar 13 23:29:31.481445 (XEN) 0000000000000086 0000000000da7a63 > 0000001980123b91 0000000000000064 > Mar 13 23:29:31.489429 (XEN) 0000000800000001 ffff82c480274222 > ffff82c48028a8d0 ffff82c480239358 > Mar 13 23:29:31.489496 (XEN) ffff82c480246c90 0000000000000007 > ffff82c480297df8 ffff82c480178abe > Mar 13 23:29:31.501449 (XEN) ffff82c480246c90 ffff82c48028a7f8 > ffff82c480297e08 ffff82c480273567 > Mar 13 23:29:31.509432 (XEN) ffff82c480297e28 ffff82c480257221 > 0000000000000080 ffff82c4802474a0 > Mar 13 23:29:31.509500 (XEN) ffff82c480297f08 ffff82c480271fb6 > 00000000002d1a00 ffffffff00000000 > Mar 13 23:29:31.521451 (XEN) 000000000007bf20 0000000000000000 > 0000000000000000 ffff83000007bdc0 > Mar 13 23:29:31.529435 (XEN) ffff83000007bfb0 ffff83000007bf20 > 0000000000f23000 0100000000000000 > Mar 13 23:29:31.541417 (XEN) 00000000bf200000 0000000000000000 > 0000000000000000 ffff82c4802872e0 > Mar 13 23:29:31.541484 (XEN) ffffffff00000000 0000000001000000 > 0000000800000000 000000010000006e > Mar 13 23:29:31.549437 (XEN) 0000000000000003 00000000000002f8 > 0000000000000000 0000000000000000 > Mar 13 23:29:31.561422 (XEN) 0000000000000000 0000000000000000 > 0000000000000000 0000000000000000 > Mar 13 23:29:31.561488 (XEN) 0000000000067e9c ffff82c4801000b5 > 0000000000000000 0000000000000000 > Mar 13 23:29:31.569440 (XEN) 0000000000000000 0000000000000000 > 0000000000000000 0000000000000000 > Mar 13 23:29:31.581485 (XEN) 0000000000000000 0000000000000000 > 0000000000000000 0000000000000000 > Mar 13 23:29:31.581552 (XEN) Xen call trace: > Mar 13 23:29:31.581594 (XEN) [<ffff82c480195228>] hpet_msi_unmask+0x1f/0x51 > Mar 13 23:29:31.589448 (XEN) [<ffff82c48019531b>] hpet_msi_startup+0x9/0x10 > Mar 13 23:29:31.589507 (XEN) [<ffff82c480160358>] setup_irq+0x72/0x98 > Mar 13 23:29:31.601445 (XEN) [<ffff82c4801610c8>] request_irq+0x70/0x9f > Mar 13 23:29:31.601502 (XEN) [<ffff82c4802743ec>] > hpet_broadcast_init+0x1ca/0x44e > Mar 13 23:29:31.609446 (XEN) [<ffff82c480178abe>] > _disable_pit_irq+0x34/0x89 > Mar 13 23:29:31.609505 (XEN) [<ffff82c480273567>] disable_pit_irq+0x10/0x2e > Mar 13 23:29:31.621447 (XEN) [<ffff82c480257221>] do_initcalls+0x22/0x30 > Mar 13 23:29:31.621504 (XEN) [<ffff82c480271fb6>] __start_xen+0x2fcd/0x32c2 > Mar 13 23:29:31.625845 (XEN) > Mar 13 23:29:31.625881 (XEN) > Mar 13 23:29:31.625915 (XEN) **************************************** > Mar 13 23:29:31.629437 (XEN) Panic on CPU 0: > Mar 13 23:29:31.633827 (XEN) Xen BUG at hpet.c:252 > Mar 13 23:29:31.637429 (XEN) **************************************** > Mar 13 23:29:31.641840 (XEN) > Mar 13 23:29:31.645416 (XEN) Reboot in five seconds... > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jan Beulich
2011-Mar-15 09:47 UTC
[Xen-devel] Re: [xen-unstable test] 6413: regressions - FAIL
>>> On 14.03.11 at 18:22, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote: > Ian Jackson writes ("[xen-unstable test] 6413: regressions - FAIL"): >> Tests which did not succeed and are blocking: >> test-amd64-amd64-xl-win 5 xen-boot fail REGR. vs. 6396 > > Xen boot crash. Lots of these ...Yes, I can see my thinko is c/s 23033:84bacd800bf8 (too bad all my test systems either have ARAT or no MSI support in their HPETs). I''m sorry for that and will send a fix soon. Jan> Mar 13 23:29:31.091587 (XEN) Brought up 8 CPUs > Mar 13 23:29:31.205401 (XEN) Testing NMI watchdog --- CPU#0 okay. CPU#1 stuck. > CPU#2 stuck. CPU#3 stuck. CPU#4 stuck. CPU#5 stuck. CPU#6 s > tuck. CPU#7 stuck. > Mar 13 23:29:31.369445 (XEN) Xen BUG at hpet.c:252 > Mar 13 23:29:31.369492 (XEN) ----[ Xen-4.1.0-rc7-pre x86_64 debug=y Not tainted > ]---- > Mar 13 23:29:31.381434 (XEN) CPU: 0 > Mar 13 23:29:31.381473 (XEN) RIP: e008:[<ffff82c480195228>] > hpet_msi_unmask+0x1f/0x51 > Mar 13 23:29:31.389418 (XEN) RFLAGS: 0000000000010046 CONTEXT: hypervisor > Mar 13 23:29:31.389475 (XEN) rax: 0000000000000000 rbx: ffff830239380d00 > rcx: 0000000000000001 > Mar 13 23:29:31.401458 (XEN) rdx: ffff830239312980 rsi: 0000000000000001 > rdi: 0000000000000019 > Mar 13 23:29:31.401525 (XEN) rbp: ffff82c480297ce8 rsp: ffff82c480297ce8 > r8: 000000000000001e > Mar 13 23:29:31.409446 (XEN) r9: 0000000000000038 r10: 00007d0a00000000 > r11: 0000000000000001 > Mar 13 23:29:31.421428 (XEN) r12: ffff830239380d34 r13: 0000000000000286 > r14: 0000000000000019 > Mar 13 23:29:31.429410 (XEN) r15: ffff830239312dd0 cr0: 000000008005003b > cr4: 00000000000026f0 > Mar 13 23:29:31.429477 (XEN) cr3: 00000000bf49c000 cr2: 0000000000000000 > Mar 13 23:29:31.441419 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: > 0000 cs: e008 > Mar 13 23:29:31.441484 (XEN) Xen stack trace from rsp=ffff82c480297ce8: > Mar 13 23:29:31.449422 (XEN) ffff82c480297cf8 ffff82c48019531b > ffff82c480297d38 ffff82c480160358 > Mar 13 23:29:31.449490 (XEN) ffff82c480297d38 00000000fffffff4 > 0000000000000019 ffff82c480195428 > Mar 13 23:29:31.461442 (XEN) ffff82c48022a42b ffff830239312980 > ffff82c480297d78 ffff82c4801610c8 > Mar 13 23:29:31.469426 (XEN) ffff830239312dd0 0000000000000019 > 0000000000000000 0000000000000100 > Mar 13 23:29:31.469493 (XEN) 0000000000000000 ffff830239312980 > ffff82c480297dd8 ffff82c4802743ec > Mar 13 23:29:31.481445 (XEN) 0000000000000086 0000000000da7a63 > 0000001980123b91 0000000000000064 > Mar 13 23:29:31.489429 (XEN) 0000000800000001 ffff82c480274222 > ffff82c48028a8d0 ffff82c480239358 > Mar 13 23:29:31.489496 (XEN) ffff82c480246c90 0000000000000007 > ffff82c480297df8 ffff82c480178abe > Mar 13 23:29:31.501449 (XEN) ffff82c480246c90 ffff82c48028a7f8 > ffff82c480297e08 ffff82c480273567 > Mar 13 23:29:31.509432 (XEN) ffff82c480297e28 ffff82c480257221 > 0000000000000080 ffff82c4802474a0 > Mar 13 23:29:31.509500 (XEN) ffff82c480297f08 ffff82c480271fb6 > 00000000002d1a00 ffffffff00000000 > Mar 13 23:29:31.521451 (XEN) 000000000007bf20 0000000000000000 > 0000000000000000 ffff83000007bdc0 > Mar 13 23:29:31.529435 (XEN) ffff83000007bfb0 ffff83000007bf20 > 0000000000f23000 0100000000000000 > Mar 13 23:29:31.541417 (XEN) 00000000bf200000 0000000000000000 > 0000000000000000 ffff82c4802872e0 > Mar 13 23:29:31.541484 (XEN) ffffffff00000000 0000000001000000 > 0000000800000000 000000010000006e > Mar 13 23:29:31.549437 (XEN) 0000000000000003 00000000000002f8 > 0000000000000000 0000000000000000 > Mar 13 23:29:31.561422 (XEN) 0000000000000000 0000000000000000 > 0000000000000000 0000000000000000 > Mar 13 23:29:31.561488 (XEN) 0000000000067e9c ffff82c4801000b5 > 0000000000000000 0000000000000000 > Mar 13 23:29:31.569440 (XEN) 0000000000000000 0000000000000000 > 0000000000000000 0000000000000000 > Mar 13 23:29:31.581485 (XEN) 0000000000000000 0000000000000000 > 0000000000000000 0000000000000000 > Mar 13 23:29:31.581552 (XEN) Xen call trace: > Mar 13 23:29:31.581594 (XEN) [<ffff82c480195228>] hpet_msi_unmask+0x1f/0x51 > Mar 13 23:29:31.589448 (XEN) [<ffff82c48019531b>] hpet_msi_startup+0x9/0x10 > Mar 13 23:29:31.589507 (XEN) [<ffff82c480160358>] setup_irq+0x72/0x98 > Mar 13 23:29:31.601445 (XEN) [<ffff82c4801610c8>] request_irq+0x70/0x9f > Mar 13 23:29:31.601502 (XEN) [<ffff82c4802743ec>] > hpet_broadcast_init+0x1ca/0x44e > Mar 13 23:29:31.609446 (XEN) [<ffff82c480178abe>] > _disable_pit_irq+0x34/0x89 > Mar 13 23:29:31.609505 (XEN) [<ffff82c480273567>] disable_pit_irq+0x10/0x2e > Mar 13 23:29:31.621447 (XEN) [<ffff82c480257221>] do_initcalls+0x22/0x30 > Mar 13 23:29:31.621504 (XEN) [<ffff82c480271fb6>] __start_xen+0x2fcd/0x32c2 > Mar 13 23:29:31.625845 (XEN) > Mar 13 23:29:31.625881 (XEN) > Mar 13 23:29:31.625915 (XEN) **************************************** > Mar 13 23:29:31.629437 (XEN) Panic on CPU 0: > Mar 13 23:29:31.633827 (XEN) Xen BUG at hpet.c:252 > Mar 13 23:29:31.637429 (XEN) **************************************** > Mar 13 23:29:31.641840 (XEN) > Mar 13 23:29:31.645416 (XEN) Reboot in five seconds... > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jan Beulich
2011-Mar-15 09:56 UTC
[Xen-devel] Re: [xen-unstable test] 6413: regressions - FAIL
>>> On 15.03.11 at 10:47, "Jan Beulich" <JBeulich@novell.com> wrote: >>>> On 14.03.11 at 18:22, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote: >> Ian Jackson writes ("[xen-unstable test] 6413: regressions - FAIL"): >>> Tests which did not succeed and are blocking: >>> test-amd64-amd64-xl-win 5 xen-boot fail REGR. vs. 6396 >> >> Xen boot crash. Lots of these ... > > Yes, I can see my thinko is c/s 23033:84bacd800bf8 (too bad all > my test systems either have ARAT or no MSI support in their HPETs). > I''m sorry for that and will send a fix soon. > > Jan > >> Mar 13 23:29:31.091587 (XEN) Brought up 8 CPUs >> Mar 13 23:29:31.205401 (XEN) Testing NMI watchdog --- CPU#0 okay. CPU#1 stuck. >> CPU#2 stuck. CPU#3 stuck. CPU#4 stuck. CPU#5 stuck. CPU#6 s >> tuck. CPU#7 stuck.But I hope these aren''t related, as I can''t see how any recent change could have broken the watchdog NMI setup logic. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2011-Mar-15 10:00 UTC
Re: [Xen-devel] Re: [xen-unstable test] 6413: regressions - FAIL
On 15/03/2011 09:56, "Jan Beulich" <JBeulich@novell.com> wrote:>>>> On 15.03.11 at 10:47, "Jan Beulich" <JBeulich@novell.com> wrote: >>>>> On 14.03.11 at 18:22, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote: >>> Ian Jackson writes ("[xen-unstable test] 6413: regressions - FAIL"): >>>> Tests which did not succeed and are blocking: >>>> test-amd64-amd64-xl-win 5 xen-boot fail REGR. vs. 6396 >>> >>> Xen boot crash. Lots of these ... >> >> Yes, I can see my thinko is c/s 23033:84bacd800bf8 (too bad all >> my test systems either have ARAT or no MSI support in their HPETs). >> I''m sorry for that and will send a fix soon. >> >> Jan >> >>> Mar 13 23:29:31.091587 (XEN) Brought up 8 CPUs >>> Mar 13 23:29:31.205401 (XEN) Testing NMI watchdog --- CPU#0 okay. CPU#1 >>> stuck. >>> CPU#2 stuck. CPU#3 stuck. CPU#4 stuck. CPU#5 stuck. CPU#6 s >>> tuck. CPU#7 stuck. > > But I hope these aren''t related, as I can''t see how any recent > change could have broken the watchdog NMI setup logic.I think our NMI watchdog support is not working properly on all new CPUs, and it''s been that way for some time. -- Keir> Jan > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
George Dunlap
2011-Mar-29 15:15 UTC
Re: [Xen-devel] Re: [xen-unstable test] 6413: regressions - FAIL
Has there been a fix for this one? I just did a pull of 4.1-release, and I''m getting this every couple of boots... -George On Tue, Mar 15, 2011 at 10:00 AM, Keir Fraser <keir.xen@gmail.com> wrote:> On 15/03/2011 09:56, "Jan Beulich" <JBeulich@novell.com> wrote: > >>>>> On 15.03.11 at 10:47, "Jan Beulich" <JBeulich@novell.com> wrote: >>>>>> On 14.03.11 at 18:22, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote: >>>> Ian Jackson writes ("[xen-unstable test] 6413: regressions - FAIL"): >>>>> Tests which did not succeed and are blocking: >>>>> test-amd64-amd64-xl-win 5 xen-boot fail REGR. vs. 6396 >>>> >>>> Xen boot crash. Lots of these ... >>> >>> Yes, I can see my thinko is c/s 23033:84bacd800bf8 (too bad all >>> my test systems either have ARAT or no MSI support in their HPETs). >>> I''m sorry for that and will send a fix soon. >>> >>> Jan >>> >>>> Mar 13 23:29:31.091587 (XEN) Brought up 8 CPUs >>>> Mar 13 23:29:31.205401 (XEN) Testing NMI watchdog --- CPU#0 okay. CPU#1 >>>> stuck. >>>> CPU#2 stuck. CPU#3 stuck. CPU#4 stuck. CPU#5 stuck. CPU#6 s >>>> tuck. CPU#7 stuck. >> >> But I hope these aren''t related, as I can''t see how any recent >> change could have broken the watchdog NMI setup logic. > > I think our NMI watchdog support is not working properly on all new CPUs, > and it''s been that way for some time. > > -- Keir > >> Jan >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2011-Mar-29 15:30 UTC
Re: [Xen-devel] Re: [xen-unstable test] 6413: regressions - FAIL
Then it can''t be due to 23033:84bacd as Jan thought, as 4.1 branch does not have that changeset. -- Keir On 29/03/2011 16:15, "George Dunlap" <dunlapg@umich.edu> wrote:> Has there been a fix for this one? > > I just did a pull of 4.1-release, and I''m getting this every couple of > boots... > -George > > On Tue, Mar 15, 2011 at 10:00 AM, Keir Fraser <keir.xen@gmail.com> wrote: >> On 15/03/2011 09:56, "Jan Beulich" <JBeulich@novell.com> wrote: >> >>>>>> On 15.03.11 at 10:47, "Jan Beulich" <JBeulich@novell.com> wrote: >>>>>>> On 14.03.11 at 18:22, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote: >>>>> Ian Jackson writes ("[xen-unstable test] 6413: regressions - FAIL"): >>>>>> Tests which did not succeed and are blocking: >>>>>> test-amd64-amd64-xl-win 5 xen-boot fail REGR. vs. >>>>>> 6396 >>>>> >>>>> Xen boot crash. Lots of these ... >>>> >>>> Yes, I can see my thinko is c/s 23033:84bacd800bf8 (too bad all >>>> my test systems either have ARAT or no MSI support in their HPETs). >>>> I''m sorry for that and will send a fix soon. >>>> >>>> Jan >>>> >>>>> Mar 13 23:29:31.091587 (XEN) Brought up 8 CPUs >>>>> Mar 13 23:29:31.205401 (XEN) Testing NMI watchdog --- CPU#0 okay. CPU#1 >>>>> stuck. >>>>> CPU#2 stuck. CPU#3 stuck. CPU#4 stuck. CPU#5 stuck. CPU#6 s >>>>> tuck. CPU#7 stuck. >>> >>> But I hope these aren''t related, as I can''t see how any recent >>> change could have broken the watchdog NMI setup logic. >> >> I think our NMI watchdog support is not working properly on all new CPUs, >> and it''s been that way for some time. >> >> -- Keir >> >>> Jan >>> >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel >> >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >>_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jan Beulich
2011-Mar-29 16:11 UTC
Re: [Xen-devel] Re: [xen-unstable test] 6413: regressions - FAIL
>>> On 29.03.11 at 17:15, George Dunlap <dunlapg@umich.edu> wrote: > Has there been a fix for this one? > > I just did a pull of 4.1-release, and I''m getting this every couple of > boots...The boot crash or the NMI stuck? The former had been fixed (though as Keir said only in -unstable, as the problem c/s is only there). The latter hasn''t got any attention afaik. Jan> On Tue, Mar 15, 2011 at 10:00 AM, Keir Fraser <keir.xen@gmail.com> wrote: >> On 15/03/2011 09:56, "Jan Beulich" <JBeulich@novell.com> wrote: >> >>>>>> On 15.03.11 at 10:47, "Jan Beulich" <JBeulich@novell.com> wrote: >>>>>>> On 14.03.11 at 18:22, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote: >>>>> Ian Jackson writes ("[xen-unstable test] 6413: regressions - FAIL"): >>>>>> Tests which did not succeed and are blocking: >>>>>> test-amd64-amd64-xl-win 5 xen-boot fail REGR. vs. 6396 >>>>> >>>>> Xen boot crash. Lots of these ... >>>> >>>> Yes, I can see my thinko is c/s 23033:84bacd800bf8 (too bad all >>>> my test systems either have ARAT or no MSI support in their HPETs). >>>> I''m sorry for that and will send a fix soon. >>>> >>>> Jan >>>> >>>>> Mar 13 23:29:31.091587 (XEN) Brought up 8 CPUs >>>>> Mar 13 23:29:31.205401 (XEN) Testing NMI watchdog --- CPU#0 okay. CPU#1 >>>>> stuck. >>>>> CPU#2 stuck. CPU#3 stuck. CPU#4 stuck. CPU#5 stuck. CPU#6 s >>>>> tuck. CPU#7 stuck. >>> >>> But I hope these aren''t related, as I can''t see how any recent >>> change could have broken the watchdog NMI setup logic. >> >> I think our NMI watchdog support is not working properly on all new CPUs, >> and it''s been that way for some time. >> >> -- Keir >> >>> Jan >>> >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel >> >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >>_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel