NetBSD Problem Report #46105

From riz@wintermute.localdomain  Mon Feb 27 01:20:41 2012
Return-Path: <riz@wintermute.localdomain>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	by www.NetBSD.org (Postfix) with ESMTP id B0CD463B952
	for <gnats-bugs@gnats.NetBSD.org>; Mon, 27 Feb 2012 01:20:41 +0000 (UTC)
Message-Id: <20120227012043.8E1C811C87F@wintermute.localdomain>
Date: Sun, 26 Feb 2012 17:20:43 -0800 (PST)
From: riz@NetBSD.org
Reply-To: riz@NetBSD.org
To: gnats-bugs@gnats.NetBSD.org
Subject: hypervisor-dependent(?) xen crash
X-Send-Pr-Version: 3.95

>Number:         46105
>Category:       port-xen
>Synopsis:       mmu_update panics with 3.1
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    port-xen-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 27 01:25:00 +0000 2012
>Last-Modified:  Mon Feb 27 18:30:02 +0000 2012
>Originator:     Jeff Rizzo
>Release:        NetBSD 6.0_BETA
>Organization:

>Environment:


System: 6.0_BETA i386 on amazon EC2 hypervisors
Architecture: i386
Machine: i386
>Description:
	While creating NetBSD 6.0_BETA/i386 AMIs for Amazon EC2, 2 out of
	7 did not come up properly.  When I investigated more closely,
	both the ones which did not come up had a hypervisor version of
	3.1, while all the others were 3.4.

	Other details: the instances only had 1 vcpu, so MP should not
	be a factor.  The regions where the failures occurred (and
	are more likely, I guess, to have 3.1 hypervisors) were "us-west-1"
	and "ap-northeast-1".

	Here is the console log for one of the crashed instances:


i-31e8d376
2012-02-27T00:25:51+0000
Xen Minimal OS!
  start_info: 0xa01000(VA)
    nr_pages: 0x26700
  shared_inf: 0xdea91000(MA)
     pt_base: 0xa04000(VA)
nr_pt_frames: 0x9
    mfn_list: 0x967000(VA)
   mod_start: 0x0(VA)
     mod_len: 0
       flags: 0x0
    cmd_line:  root=/dev/sda1 ro 4
  stack:      0x946780-0x966780
MM: Init
      _text: 0x0(VA)
     _etext: 0x61e65(VA)
   _erodata: 0x76000(VA)
     _edata: 0x7b6d4(VA)
stack start: 0x946780(VA)
       _end: 0x966d34(VA)
  start_pfn: a10
    max_pfn: 26700
Mapping memory range 0xc00000 - 0x26700000
setting 0x0-0x76000 readonly
skipped 0x1000
MM: Initialise page allocator for b3e000(b3e000)-0(26700000)
MM: done
Demand map pfns at 26701000-36701000.
Heap resides at 36702000-76702000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x26701000.
Initialising scheduler
Thread "Idle": pointer: 0x36702008, stack: 0xbf0000
Initialising xenbus
Thread "xenstore": pointer: 0x36702478, stack: 0x26600000
Dummy main: start_info=0x966880
Thread "main": pointer: 0x367028e8, stack: 0x26610000
"main" "root=/dev/sda1" "ro" "4" 
vbd 2049 is hd0
******************* BLKFRONT for device/vbd/2049 **********


backend at /local/domain/0/backend/vbd/1279/2049
Failed to read /local/domain/0/backend/vbd/1279/2049/feature-barrier.
Failed to read /local/domain/0/backend/vbd/1279/2049/feature-flush-cache.
2097152 sectors of 0 bytes
**************************
vbd 2050 is hd1
******************* BLKFRONT for device/vbd/2050 **********


backend at /local/domain/0/backend/vbd/1279/2050
Failed to read /local/domain/0/backend/vbd/1279/2050/feature-barrier.
Failed to read /local/domain/0/backend/vbd/1279/2050/feature-flush-cache.
10485760 sectors of 0 bytes
**************************
[H[J  Booting 'NetBSD AMI'

root (hd0)
 Filesystem type is ext2fs, using whole disk
kernel /boot/netbsd root=xbd1

xc_dom_probe_bzimage_kernel: kernel is not a bzImage
close blk: backend at /local/domain/0/backend/vbd/1279/2049
close blk: backend at /local/domain/0/backend/vbd/1279/2050
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 6.0_BETA (EC2) #0: Sun Feb 26 11:35:03 PST 2012
	riz@breadfruit.tastylime.net:/home/riz/obj.i386/sys/arch/i386/compile/EC2
total memory = 615 MB
avail memory = 596 MB
mainbus0 (root)
hypervisor0 at mainbus0: Xen version 3.1
vcpu0 at hypervisor0: Intel(R) Xeon(R) CPU           E5430  @ 2.66GHz, id 0x1067a
xenbus0 at hypervisor0: Xen Virtual Bus Interface
xencons0 at hypervisor0: Xen Virtual Console Driver
npx0 at hypervisor0: using exception 16
xennet0 at xenbus0 id 0: Xen Virtual Network Interface
xennet0: MAC address 12:31:3f:01:50:9b
xbd0 at xenbus0 id 2049: Xen Virtual Block Device Interface
xbd1 at xenbus0 id 2050: Xen Virtual Block Device Interface
balloon0 at xenbus0 id 0: Xen Balloon driver
balloon0: current reservation: 629760 KiB
xennet0: using RX copy mode
balloon0: current reservation: 157440 pages => target: 157440 pages
boot device: xbd1
root on xbd1a dumps on xbd1b
root file system type: ffs
xpq_flush_queue: 3 entries (0 successful) on cpu0 (0)
cpu0 (0):
  0x00000000c11b5000: 0x00000000afa96001
  0x00000000c11b5008: 0x00000000afa55001
  0x00000000c11b5010: 0x00000000afa54001
panic: HYPERVISOR_mmu_update failed, ret: -22

fatal breakpoint trap in supervisor mode
trap type 1 code 0 eip c0136664 cs 9 eflags 282 cr2 36fbe000 ilevel 8
Stopped in pid 1.1 (init) at    netbsd:breakpoint+0x4:  popl    %ebp
breakpoint(c049074a,c04f35a0,c04c5e34,d8d22a78,c04f36a4,8,d8d22a5c,c04fe970,3,3)
 at netbsd:breakpoint+0x4
vpanic(c04c5e34,d8d22a78,d8d22a9c,c13c7880,8,1,d8d22acc,c042fd08,c04c5e34,ffffff
ea) at netbsd:vpanic+0x218
panic(c04c5e34,ffffffea,0,afa54001,0,2,d8d22adc,c03f703c,c1339d10,c150be8c) at n
etbsd:panic+0x18
xpq_flush_queue(c04ce5ea,0,d8d22b8c,c03f7cf4,c150be5c,0,0,bf7ff000,6,c11b5018) a
t netbsd:xpq_flush_queue+0x188
xpq_queue_tlb_flush(6,c0485cd4,0,c071d000,c11b5010,c071d000,d8d22b7c,c013564d,c1
1b5010,0) at netbsd:xpq_queue_tlb_flush+0x19
tlbflush(c11b5010,0,afa54001,0,0,bfdfc000,0,3,0,0) at netbsd:tlbflush+0x1a
cpu_load_pmap(c150cf08,c04f1b00,d8d22c0c,c03f9146,c150be58,d8d22bd8,0,0,ffffffff
,ffffffff) at netbsd:cpu_load_pmap+0xfd
pmap_load(c049a744,d8d22d2c,c0100838,c01d3d0e,c049a744,bf7ffff5,b,0,ffffffff,fff
fffff) at netbsd:pmap_load+0x1b0
do_pmap_load(c01d3d0e,c049a744,bf7ffff5,b,0,ffffffff,ffffffff,0,b0717,c14f7800) a
t netbsd:do_pmap_load+0x16
copyout(c14f7800,7c8000,c0632200,0,c010006d,0,0,0,0,0) at netbsd:copyout+0x48
ds          d8d20011
es          c04c0011    copyright+0x35bd1
fs          31
gs          d8d20011
edi         d8d22a78
esi         c04c5e34    copyright+0x3b9f4
ebp         d8d22a0c
ebx         104
edx         ffffffff
ecx         0
eax         1
eip         c0136664    breakpoint+0x4
cs          9
eflags      282
esp         d8d22a0c
ss          11
netbsd:breakpoint+0x4:  popl    %ebp
db{0}> 

>How-To-Repeat:

	Try to launch a PAE domU on a 3.1 hypervisor.
>Fix:
	None Given.

>Audit-Trail:
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: port-xen-maintainer@NetBSD.org, gnats-admin@NetBSD.org,
        netbsd-bugs@NetBSD.org
Subject: Re: port-xen/46105: hypervisor-dependent(?) xen crash
Date: Mon, 27 Feb 2012 12:35:56 +0100

 --MGYHOYXEY6WxJCY8
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline

 On Mon, Feb 27, 2012 at 01:25:01AM +0000, riz@NetBSD.org wrote:
 > 	While creating NetBSD 6.0_BETA/i386 AMIs for Amazon EC2, 2 out of
 > 	7 did not come up properly.  When I investigated more closely,
 > 	both the ones which did not come up had a hypervisor version of
 > 	3.1, while all the others were 3.4.
 > 
 > 	Other details: the instances only had 1 vcpu, so MP should not
 > 	be a factor.  The regions where the failures occurred (and
 > 	are more likely, I guess, to have 3.1 hypervisors) were "us-west-1"
 > 	and "ap-northeast-1".
 > 
 > 	Here is the console log for one of the crashed instances:
 > [...]

 Hum, 6.0_BETA 201202250740Z boots fine for me on a NetBSD/amd64 domains0
 and 3.1.4 hypervisor. I tested both i386PAE and amd64 domUs.
 I fear it's one of the bugs we fixed with recursive table pages;
 if so it's going to be hard to work around.

 Do you know if it happens with all Amazon 3.1 hypervisors, or only
 some ?
 I guess there's no way to restricy a domain to some hypervisor versions
 on amazon ?

 Also, please apply the attached diff if you can reproduce this.
 It prints the tiny version of the hypervisor, which can help identifing bugs
 present.


 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

 --MGYHOYXEY6WxJCY8
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename="version.diff"

 Index: hypervisor.c
 ===================================================================
 RCS file: /cvsroot/src/sys/arch/xen/xen/hypervisor.c,v
 retrieving revision 1.61
 diff -u -p -u -r1.61 hypervisor.c
 --- hypervisor.c	17 Feb 2012 18:42:19 -0000	1.61
 +++ hypervisor.c	27 Feb 2012 11:34:09 -0000
 @@ -210,12 +210,15 @@ hypervisor_attach(device_t parent, devic
  #endif
  #endif /* NPCI */
  	union hypervisor_attach_cookie hac;
 +	char xen_extra_version[XEN_EXTRAVERSION_LEN];

  	xenkernfs_init();

  	xen_version = HYPERVISOR_xen_version(XENVER_version, NULL);
 -	aprint_normal(": Xen version %d.%d\n", XEN_MAJOR(xen_version),
 -	       XEN_MINOR(xen_version));
 +	memset(xen_extra_version, 0, sizeof(xen_extra_version));
 +	HYPERVISOR_xen_version(XENVER_extraversion, xen_extra_version);
 +	aprint_normal(": Xen version %d.%d%s\n", XEN_MAJOR(xen_version),
 +	       XEN_MINOR(xen_version), xen_extra_version);

  	xengnt_init();
  	events_init();

 --MGYHOYXEY6WxJCY8--

From: Jeff Rizzo <riz@NetBSD.org>
To: gnats-bugs@NetBSD.org
Cc: Manuel Bouyer <bouyer@netbsd.org>
Subject: Re: port-xen/46105: hypervisor-dependent(?) xen crash
Date: Mon, 27 Feb 2012 09:21:13 -0800

 On 2/27/12 3:40 AM, Manuel Bouyer wrote:
 >  
 >  On Mon, Feb 27, 2012 at 01:25:01AM +0000, riz@NetBSD.org wrote:
 >  > 	While creating NetBSD 6.0_BETA/i386 AMIs for Amazon EC2, 2 out of
 >  > 	7 did not come up properly.  When I investigated more closely,
 >  > 	both the ones which did not come up had a hypervisor version of
 >  > 	3.1, while all the others were 3.4.
 >  > 
 >  > 	Other details: the instances only had 1 vcpu, so MP should not
 >  > 	be a factor.  The regions where the failures occurred (and
 >  > 	are more likely, I guess, to have 3.1 hypervisors) were "us-west-1"
 >  > 	and "ap-northeast-1".
 >  > 
 >  > 	Here is the console log for one of the crashed instances:
 >  > [...]
 >  
 >  Hum, 6.0_BETA 201202250740Z boots fine for me on a NetBSD/amd64 domains0
 >  and 3.1.4 hypervisor. I tested both i386PAE and amd64 domUs.
 >  I fear it's one of the bugs we fixed with recursive table pages;
 >  if so it's going to be hard to work around.
 >  
 >  Do you know if it happens with all Amazon 3.1 hypervisors, or only
 >  some ?

 Appears to be only some;  I just tried duplicating the problem (with
 your patch), and of 5 launches, 2 were 3.1, and one of the two crashed. 
 Unfortunately, it did not seem to print the tiny version.  :/
 >  I guess there's no way to restricy a domain to some hypervisor versions
 >  on amazon ?

 Nope.

 >  
 >  Also, please apply the attached diff if you can reproduce this.
 >  It prints the tiny version of the hypervisor, which can help identifing bugs
 >  present.
 >

 It didn't seem to do anything;  maybe I biffed it somehow.

 Here is the dmesg from the instance that booted OK:

 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 6.0_BETA (EC2) #1: Mon Feb 27 08:36:48 PST 2012

 riz@breadfruit.tastylime.net:/home/riz/obj.i386/sys/arch/i386/compile/EC2
 total memory = 615 MB
 avail memory = 596 MB
 timecounter: Timecounters tick every 10.000 msec
 mainbus0 (root)
 hypervisor0 at mainbus0: Xen version 3.1
 VIRQ_DEBUG interrupt using event channel 3
 vcpu0 at hypervisor0: Intel(R) Xeon(R) CPU           E5430  @ 2.66GHz,
 id 0x1067a
 xenbus0 at hypervisor0: Xen Virtual Bus Interface
 xencons0 at hypervisor0: Xen Virtual Console Driver
 xencons0: console major 143, unit 0
 xencons0: using event channel 2
 npx0 at hypervisor0: using exception 16
 timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
 timecounter: Timecounter "xen_system_time" frequency 1000000000 Hz
 quality 10000
 Xen clock: using event channel 5
 xenbus0: using event channel 1
 xennet0 at xenbus0 id 0: Xen Virtual Network Interface
 xennet0: MAC address 12:31:3f:00:82:a5
 xennet0: using event channel 6
 xbd0 at xenbus0 id 2049: Xen Virtual Block Device Interface
 xbd0: using event channel 7
 xbd1 at xenbus0 id 2050: Xen Virtual Block Device Interface
 xbd1: using event channel 8
 balloon0 at xenbus0 id 0: Xen Balloon driver
 balloon0: current reservation: 629760 KiB
 xennet0: using RX copy mode
 xbd0: 1024 MB, 512 bytes/sect x 2097152 sectors
 xbd1: 5120 MB, 512 bytes/sect x 10485760 sectors
 Kernelized RAIDframe activated
 balloon0: current reservation: 157440 pages => target: 157440 pages
 boot device: xbd1
 root on xbd1a dumps on xbd1b
 root file system type: ffs
 xbd1: WARNING: cache flush not supported by backend

From: Manuel Bouyer <bouyer@antioche.eu.org>
To: Jeff Rizzo <riz@NetBSD.org>
Cc: gnats-bugs@NetBSD.org
Subject: Re: port-xen/46105: hypervisor-dependent(?) xen crash
Date: Mon, 27 Feb 2012 18:30:54 +0100

 On Mon, Feb 27, 2012 at 09:21:13AM -0800, Jeff Rizzo wrote:
 > Appears to be only some;  I just tried duplicating the problem (with
 > your patch), and of 5 launches, 2 were 3.1, and one of the two crashed. 

 It seemed to crash early enough for the problem to be reliably
 reproductible.

 > Unfortunately, it did not seem to print the tiny version.  :/
 > >  I guess there's no way to restricy a domain to some hypervisor versions
 > >  on amazon ?
 > 
 > Nope.
 > 
 > >  
 > >  Also, please apply the attached diff if you can reproduce this.
 > >  It prints the tiny version of the hypervisor, which can help identifing bugs
 > >  present.
 > >
 > 
 > It didn't seem to do anything;  maybe I biffed it somehow.
 > 
 > Here is the dmesg from the instance that booted OK:
 > 
 > 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 6.0_BETA (EC2) #1: Mon Feb 27 08:36:48 PST 2012
 >        
 > riz@breadfruit.tastylime.net:/home/riz/obj.i386/sys/arch/i386/compile/EC2
 > total memory = 615 MB
 > avail memory = 596 MB
 > timecounter: Timecounters tick every 10.000 msec
 > mainbus0 (root)
 > hypervisor0 at mainbus0: Xen version 3.1

 Mine now says:
 NetBSD 6.99.3 (XEN3PAE_DOMU) #19: Mon Feb 27 18:27:36 CET 2012
         bouyer@hop:/dsk/l1/misc/bouyer/tmp/i386/obj/dsk/l1/misc/bouyer/quota2/src/sys/arch/i386/compile/XEN3PAE_DOMU
 total memory = 512 MB
 avail memory = 496 MB
 timecounter: Timecounters tick every 10.000 msec
 cprng kernel: WARNING insufficient entropy at creation.
 mainbus0 (root)
 hypervisor0 at mainbus0: Xen version 3.1.4

 I think XENVER_extraversion should work; even Xen 3.0 has it.
 I hope amazon didn't remove it ...

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

From: Jeff Rizzo <riz@NetBSD.org>
To: Manuel Bouyer <bouyer@antioche.eu.org>
Cc: gnats-bugs@NetBSD.org
Subject: Re: port-xen/46105: hypervisor-dependent(?) xen crash
Date: Mon, 27 Feb 2012 10:10:00 -0800

 OK, I fixed the patch (my fault, not yours), and got the teeny version
 info.  Once again, I got one 3.1 crash, and one without crash.  They
 both appear to be the same hypervisor version:

 From the one that didn't crash:

 hypervisor0 at mainbus0: Xen version 3.1.2-128.1.10.el5


 From the one that did:
 hypervisor0 at mainbus0: Xen version 3.1.2-128.1.10.el5

 Here's the crash log, in case it helps.

 i-c596ac82
 2012-02-27T18:01:35+0000
 Xen Minimal OS!
   start_info: 0xa01000(VA)
     nr_pages: 0x26700
   shared_inf: 0xbfd92000(MA)
      pt_base: 0xa04000(VA)
 nr_pt_frames: 0x9
     mfn_list: 0x967000(VA)
    mod_start: 0x0(VA)
      mod_len: 0
        flags: 0x0
     cmd_line:  root=/dev/sda1 ro 4
   stack:      0x946780-0x966780
 MM: Init
       _text: 0x0(VA)
      _etext: 0x61e65(VA)
    _erodata: 0x76000(VA)
      _edata: 0x7b6d4(VA)
 stack start: 0x946780(VA)
        _end: 0x966d34(VA)
   start_pfn: a10
     max_pfn: 26700
 Mapping memory range 0xc00000 - 0x26700000
 setting 0x0-0x76000 readonly
 skipped 0x1000
 MM: Initialise page allocator for b3e000(b3e000)-0(26700000)
 MM: done
 Demand map pfns at 26701000-36701000.
 Heap resides at 36702000-76702000.
 Initialising timer interface
 Initialising console ... done.
 gnttab_table mapped at 0x26701000.
 Initialising scheduler
 Thread "Idle": pointer: 0x36702008, stack: 0xbf0000
 Initialising xenbus
 Thread "xenstore": pointer: 0x36702478, stack: 0x26600000
 Dummy main: start_info=0x966880
 Thread "main": pointer: 0x367028e8, stack: 0x26610000
 "main" "root=/dev/sda1" "ro" "4"
 vbd 2049 is hd0
 ******************* BLKFRONT for device/vbd/2049 **********


 backend at /local/domain/0/backend/vbd/3319/2049
 Failed to read /local/domain/0/backend/vbd/3319/2049/feature-barrier.
 Failed to read /local/domain/0/backend/vbd/3319/2049/feature-flush-cache.
 2097152 sectors of 0 bytes
 **************************
 vbd 2050 is hd1
 ******************* BLKFRONT for device/vbd/2050 **********


 backend at /local/domain/0/backend/vbd/3319/2050
 Failed to read /local/domain/0/backend/vbd/3319/2050/feature-barrier.
 Failed to read /local/domain/0/backend/vbd/3319/2050/feature-flush-cache.
 10485760 sectors of 0 bytes
 **************************
 [H[J  Booting 'NetBSD AMI'

 root (hd0)
  Filesystem type is ext2fs, using whole disk
 kernel /boot/netbsd root=xbd1

 xc_dom_probe_bzimage_kernel: kernel is not a bzImage
 close blk: backend at /local/domain/0/backend/vbd/3319/2049
 close blk: backend at /local/domain/0/backend/vbd/3319/2050
 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 6.0_BETA (EC2) #2: Mon Feb 27 09:34:05 PST 2012

 riz@breadfruit.tastylime.net:/home/riz/obj.i386/sys/arch/i386/compile/EC2
 total memory = 615 MB
 avail memory = 596 MB
 mainbus0 (root)
 hypervisor0 at mainbus0: Xen version 3.1.2-128.1.10.el5
 vcpu0 at hypervisor0: Intel(R) Xeon(R) CPU           E5430  @ 2.66GHz,
 id 0x1067a
 xenbus0 at hypervisor0: Xen Virtual Bus Interface
 xencons0 at hypervisor0: Xen Virtual Console Driver
 npx0 at hypervisor0: using exception 16
 xennet0 at xenbus0 id 0: Xen Virtual Network Interface
 xennet0: MAC address 12:31:40:00:48:87
 xbd0 at xenbus0 id 2049: Xen Virtual Block Device Interface
 xbd1 at xenbus0 id 2050: Xen Virtual Block Device Interface
 balloon0 at xenbus0 id 0: Xen Balloon driver
 balloon0: current reservation: 629760 KiB
 xennet0: using RX copy mode
 balloon0: current reservation: 157440 pages => target: 157440 pages
 boot device: xbd1
 root on xbd1a dumps on xbd1b
 root file system type: ffs
 xpq_flush_queue: 3 entries (0 successful) on cpu0 (0)
 cpu0 (0):
   0x00000003ddc96000: 0x00000002d6379001
   0x00000003ddc96008: 0x00000002d6338001
   0x00000003ddc96010: 0x00000002d6337001
 panic: HYPERVISOR_mmu_update failed, ret: -22

 fatal breakpoint trap in supervisor mode
 trap type 1 code 0 eip c0136664 cs 9 eflags 282 cr2 36fc0000 ilevel 8
 Stopped in pid 1.1 (init) at    netbsd:breakpoint+0x4:  popl    %ebp
 breakpoint(c049078a,c04f35a0,c04c5e74,d8d22a78,c04f36a4,8,d8d22a5c,c04fe970,3,3)
  at netbsd:breakpoint+0x4
 vpanic(c04c5e74,d8d22a78,d8d22a9c,c13c7880,8,1,d8d22acc,c042fd48,c04c5e74,ffffff
 ea) at netbsd:vpanic+0x218
 panic(c04c5e74,ffffffea,3,d6337001,2,2,d8d22adc,c03f707c,c1339d10,c150be8c)
 at n
 etbsd:panic+0x18
 xpq_flush_queue(c04ce62a,0,d8d22b8c,c03f7d34,c150be5c,0,0,bf7ff000,6,ddc96018)
 a
 t netbsd:xpq_flush_queue+0x188
 xpq_queue_tlb_flush(6,c0485d14,0,c071d000,ddc96010,c071d000,d8d22b7c,c013564d,dd
 c96010,3) at netbsd:xpq_queue_tlb_flush+0x19
 tlbflush(ddc96010,3,d6337001,2,0,bfdfc000,0,3,0,0) at netbsd:tlbflush+0x1a
 cpu_load_pmap(c150cf08,c04f1b00,d8d22c0c,c03f9186,c150be58,d8d22bd8,0,0,ffffffff
 ,ffffffff) at netbsd:cpu_load_pmap+0xfd
 pmap_load(c049a784,d8d22d2c,c0100838,c01d3d5e,c049a784,bf7ffff5,b,0,ffffffff,fff
 fffff) at netbsd:pmap_load+0x1b0
 do_pmap_load(c01d3d5e,c049a784,bf7ffff5,b,0,ffffffff,ffffffff,0,b0717,c14f7800)
 a
 t netbsd:do_pmap_load+0x16
 copyout(c14f7800,7c8000,c0632200,0,c010006d,0,0,0,0,0) at
 netbsd:copyout+0x48
 ds          d8d20011
 es          c04c0011    copyright+0x35b91
 fs          31
 gs          d8d20011
 edi         d8d22a78
 esi         c04c5e74    copyright+0x3b9f4
 ebp         d8d22a0c
 ebx         104
 edx         ffffffff
 ecx         0
 eax         1
 eip         c0136664    breakpoint+0x4
 cs          9
 eflags      282
 esp         d8d22a0c
 ss          11
 netbsd:breakpoint+0x4:  popl    %ebp
 db{0}>

>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.