port-xen/45961: panic: kernel diagnostic assertion "err == 0" failed: file "/usr/src/sys/arch/xen/xen/clock.c", line 465

[riz%NetBSD.org@localhost]

>Number:         45961
>Category:       port-xen
>Synopsis:       panic: kernel diagnostic assertion "err == 0" failed: file 
>"/usr/src/sys/arch/xen/xen/clock.c", line 465
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-xen-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 10 02:45:00 +0000 2012
>Originator:     Jeff Rizzo
>Release:        NetBSD 5.99.64
>Organization:
        
>Environment:
        
        
System: NetBSD 5.99.64 (EC2) #0: Thu Feb  9 17:10:50 PST 2012        
riz@wintermute:/space/build/obj.amd64/sys/arch/amd64/compile/EC2
Architecture: x86_64
Machine: amd64
>Description:

I got the following crash on Amazon EC2.  I assume it had
something to do with the fact that this hypervisor
says it's 3.0.


Loaded initial symtab at 0xffffffff807fb204, strtab at 0xffffffff80850e68, # 
entries 14537
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011, 2012
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 5.99.64 (EC2) #0: Thu Feb  9 17:10:50 PST 2012
        riz@wintermute:/space/build/obj.amd64/sys/arch/amd64/compile/EC2
total memory = 7680 MB
avail memory = 7427 MB
cprng kernel: WARNING insufficient entropy at creation.
mainbus0 (root)
hypervisor0 at mainbus0: Xen version 3.0
vcpu0 at hypervisor0: Intel(R) Xeon(R) CPU           E5430  @ 2.66GHz, id 
0x1067a
vcpu1 at hypervisor0pmap_kenter_pa: mapping already present
vcpu1: feature mismatch: cpu_feature[0] is 0xbeebcbf7, but CPU reported 
0xbfebfbff
: Intel(R) Xeon(R) CPU           E5430  @ 2.66GHz, id 0x1067a
xenbus0 at hypervisor0: Xen Virtual Bus Interface
xencons0 at hypervisor0: Xen Virtual Console Driver
panic: kernel diagnostic assertion "err == 0" failed: file 
"/usr/src/sys/arch/xen/xen/clock.c", line 465 
fatal breakpoint trap in supervisor mode
trap type 1 code 0 rip ffffffff801345c5 cs e030 rflags 246 cr2  21e176f000 cpl 
0 rsp ffffffff8182fd50
Stopped in pid 0.1 (system) at  netbsd:breakpoint+0x5:  leave
breakpoint() at netbsd:breakpoint+0x5
vpanic() at netbsd:vpanic+0x1f2
kern_assert() at netbsd:kern_assert+0xae
xen_initclocks() at netbsd:xen_initclocks+0x1e0
initclocks() at netbsd:initclocks+0x2d
main() at netbsd:main+0x2b3
ds          0
es          fd90
fs          100
gs          c180
rdi         0
rsi         d
rbp         ffffffff8182fd50
rbx         104
rdx         0
rcx         0
rax         1
r8          1
r9          1
r10         1
r11         e033
r12         ffffffff8048f250    copyright+0x18d50
r13         ffffffff8182fd90
r14         0
r15         0
rip         ffffffff801345c5    breakpoint+0x5
cs          e030
rflags      246
rsp         ffffffff8182fd50
ss          e02b
netbsd:breakpoint+0x5:  leave
db{0}> 
>How-To-Repeat:
        Boot a XEN3_DOMU kernel on an Amazon EC2 hypervisor that
        reports being Xen 3.0 (I've seen some that are 3.1, 3.3
        and 3.4 as well)
>Fix:
        None given.

>Unformatted: