NetBSD Problem Report #55291

From www@netbsd.org  Sat May 23 15:22:24 2020
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 58BE51A9241
	for <gnats-bugs@gnats.NetBSD.org>; Sat, 23 May 2020 15:22:24 +0000 (UTC)
Message-Id: <20200523152223.3CB991A9244@mollari.NetBSD.org>
Date: Sat, 23 May 2020 15:22:23 +0000 (UTC)
From: prlw1@cam.ac.uk
Reply-To: prlw1@cam.ac.uk
To: gnats-bugs@NetBSD.org
Subject: panic: HYPERVISOR_mmu_update failed, ret: -16
X-Send-Pr-Version: www-1.0

>Number:         55291
>Category:       port-xen
>Synopsis:       panic: HYPERVISOR_mmu_update failed, ret: -16
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-xen-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat May 23 15:25:00 +0000 2020
>Closed-Date:    Thu Jul 23 09:38:49 +0000 2020
>Last-Modified:  Thu Jul 23 09:38:49 +0000 2020
>Originator:     Patrick Welche
>Release:        NetBSD-9.99.63/amd64 of 22 May 2020 + jdolecek's patch for PR 55285
>Organization:
>Environment:
Xen 4.11.3nb2
>Description:
With jdolecek's patch for PR 55285, the XEN3_DOM0 kernel boots to multiuser, and then panics:

Starting cupsd.
Starting cron.
The following components reported failures:
    /etc/rc.d/sysctl
See /var/run/rc.log for more information.
Sat May 23 16:11:29 BST 2020
[ 239.1600116] xpq_flush_queue: 1 entries (0 successful) on cpu0 (0)
[ 239.1600116] panic: HYPERVISOR_mmu_update failed, ret: -16

[ 239.1600116] cpu0: Begin traceback...
[ 239.1600116] vpanic() at netbsd:vpanic+0x146
[ 239.1600116] snprintf() at netbsd:snprintf
[ 239.1600116] xpq_queue_machphys_update() at netbsd:xpq_queue_machphys_update
[ 239.1600116] pmap_enter_ma() at netbsd:pmap_enter_ma+0x69d
[ 239.1600116] pmap_enter() at netbsd:pmap_enter+0x58
[ 239.1600116] udv_fault() at netbsd:udv_fault+0x100
[ 239.1600116] uvm_fault_internal() at netbsd:uvm_fault_internal+0x518
[ 239.1600116] trap() at netbsd:trap+0x66c
[ 239.1600116] --- trap (number 6) ---
[ 239.1600116] 7237b698b62f:
[ 239.1600116] cpu0: End traceback...

[ 239.1600116] dumping to dev 168,1 (offset=33554431, size=0): not possible
[ 239.1600116] rebooting...
(XEN) Hardware Dom0 shutdown: rebooting machine
(XEN) Resetting with ACPI MEMORY or I/O RESET_REG.

>How-To-Repeat:
Boot XEN3_DOM0
>Fix:

>Release-Note:

>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/55291: panic: HYPERVISOR_mmu_update failed, ret: -16
Date: Sat, 23 May 2020 17:30:19 +0200

 On Sat, May 23, 2020 at 03:25:01PM +0000, prlw1@cam.ac.uk wrote:
 > Starting cupsd.
 > Starting cron.
 > The following components reported failures:
 >     /etc/rc.d/sysctl
 > See /var/run/rc.log for more information.
 > Sat May 23 16:11:29 BST 2020
 > [ 239.1600116] xpq_flush_queue: 1 entries (0 successful) on cpu0 (0)
 > [ 239.1600116] panic: HYPERVISOR_mmu_update failed, ret: -16
 > 
 > [ 239.1600116] cpu0: Begin traceback...
 > [ 239.1600116] vpanic() at netbsd:vpanic+0x146
 > [ 239.1600116] snprintf() at netbsd:snprintf
 > [ 239.1600116] xpq_queue_machphys_update() at netbsd:xpq_queue_machphys_update
 > [ 239.1600116] pmap_enter_ma() at netbsd:pmap_enter_ma+0x69d
 > [ 239.1600116] pmap_enter() at netbsd:pmap_enter+0x58
 > [ 239.1600116] udv_fault() at netbsd:udv_fault+0x100
 > [ 239.1600116] uvm_fault_internal() at netbsd:uvm_fault_internal+0x518
 > [ 239.1600116] trap() at netbsd:trap+0x66c
 > [ 239.1600116] --- trap (number 6) ---
 > [ 239.1600116] 7237b698b62f:
 > [ 239.1600116] cpu0: End traceback...
 > 
 > [ 239.1600116] dumping to dev 168,1 (offset=33554431, size=0): not possible
 > [ 239.1600116] rebooting...
 > (XEN) Hardware Dom0 shutdown: rebooting machine
 > (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
 > 
 > >How-To-Repeat:
 > Boot XEN3_DOM0

 We'll need more details, because I don't get this problem.
 Do you have a serial console ?
 Is it with a xen-debug.gz kernel ?

 are you doing anything special, e.g. start X11, when it panics ?

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

From: Patrick Welche <prlw1@cam.ac.uk>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-xen/55291: panic: HYPERVISOR_mmu_update failed, ret: -16
Date: Sat, 23 May 2020 16:48:28 +0100

 On Sat, May 23, 2020 at 03:35:02PM +0000, Manuel Bouyer wrote:
 >  are you doing anything special, e.g. start X11, when it panics ?

 Exactly right - I stopped trying to start xdm and all is well!

State-Changed-From-To: open->closed
State-Changed-By: prlw1@NetBSD.org
State-Changed-When: Thu, 23 Jul 2020 09:38:49 +0000
State-Changed-Why:
Now testing after the recent PR kern/55285 commit, I no longer see this panic.


>Unformatted:

Home	PR Database Search