NetBSD Problem Report #47486

From www@NetBSD.org  Tue Jan 22 12:19:24 2013
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	by www.NetBSD.org (Postfix) with ESMTP id DC10563BA5D
	for <gnats-bugs@gnats.NetBSD.org>; Tue, 22 Jan 2013 12:19:23 +0000 (UTC)
Message-Id: <20130122121922.D258A63BA5D@www.NetBSD.org>
Date: Tue, 22 Jan 2013 12:19:22 +0000 (UTC)
From: ci4ic4@gmail.com
Reply-To: ci4ic4@gmail.com
To: gnats-bugs@NetBSD.org
Subject: XEN3_DOMU diag assert fail
X-Send-Pr-Version: www-1.0

>Number:         47486
>Category:       port-xen
>Synopsis:       XEN3_DOMU diag assert fail
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-xen-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 22 12:20:00 +0000 2013
>Closed-Date:    Thu Dec 20 15:32:03 +0000 2018
>Last-Modified:  Thu Dec 20 15:32:03 +0000 2018
>Originator:     Chavdar Ivanov
>Release:        6.99.16 amd64
>Organization:
Delcam Plc
>Environment:
support6# uname -a 
NetBSD support6.delcam.local 6.99.16 NetBSD 6.99.16 (XEN3_DOMU) #0: Mon Jan 21 21:09:50 UTC 2013  builds@b6.netbsd.org:/home/builds/ab/HEAD/amd64/201301211830Z-obj/home/builds/ab/HEAD/src/sys/arch/amd64/compile/XEN3_DOMU amd64
>Description:
Somewhere after the 13th of January 2012 my XEN3_DOMU fully pv host running under XenServer 6.1 started to panic; the first sign of the problem is fault with /usr/sbin/sshd as follows: 

# gdb /usr/sbin/sshd 
...
Reading symbols from /usr/sbin/sshd...(no debugging symbols found)...done.
(gdb) run 
Starting program: /usr/sbin/sshd 

Program received signal SIGSEGV, Segmentation fault.
0x00007f7ff434cddc in ?? () from /usr/lib/libcrypto.so.8
(gdb) bt
#0  0x00007f7ff434cddc in ?? () from /usr/lib/libcrypto.so.8
#1  0x00007f7ff432bbe6 in ?? () from /usr/lib/libcrypto.so.8
#2  0x00007f7ff435c7ae in BIO_set () from /usr/lib/libcrypto.so.8
#3  0x00007f7ff435c802 in ?? () from /usr/lib/libcrypto.so.8
#4  0x00007f7ff432bf6f in BIO_new_mem_buf () from /usr/lib/libcrypto.so.8
#5  0x00007f7ff4817b92 in ?? () from /usr/lib/libssh.so.20
#6  0x00007f7ff4817e26 in ?? () from /usr/lib/libssh.so.20
#7  0x00007f7ff4818bef in key_parse_private () from /usr/lib/libssh.so.20
#8  0x00007f7ff4818c80 in key_load_private () from /usr/lib/libssh.so.20
#9  0x000000000040de3d in main ()

Further I get a panic:

1]   Segmentation fault (core dumped) /usr/sbin/sshd
/etc/rc.d/sshd exited with code 1
Starting smbd.
panic: kernel diagnostic assertion "uvm_page_locked_p(pg)" failed: file "/home/builds/ab/HEAD/src/sys/arch/x86/x86/pmap.c", line 3306 
cpu3: Begin traceback...
kern_assert() at netbsd:kern_assert+0xae
pmap_remove_pte() at netbsd:pmap_remove_pte+0x312
pmap_remove() at netbsd:pmap_remove+0x1e9
ubc_alloc() at netbsd:ubc_alloc+0x5c3
ubc_uiomove() at netbsd:ubc_uiomove+0xe1
ffs_write() at netbsd:ffs_write+0x2c5
VOP_WRITE() at netbsd:VOP_WRITE+0x37
vn_write() at netbsd:vn_write+0xf9
dofilewrite() at netbsd:dofilewrite+0x7d
sys_write() at netbsd:sys_write+0x62
syscall() at netbsd:syscall+0x94
--- syscall (number 4) ---
7f7ff7438a7a:
cpu3: End traceback...

dumping to dev 142,17 (offset=4186991, size=0): not possible
rebooting...

The system works fine with a kernel from 07/01/2013 (I've lost subsequent kernels after a panic destroyed my root disk and I had to reinstall from scratch). The userland is current as of today (22/01/2013). 


>How-To-Repeat:
- Clean installation of NetBSD-current amd64 under XenServer 6.1
- switch system to PV by running 

xe vm-param-set  uuid=db74941f-2ccc-9c01-ecb2-bc2e26ffce19 HVM-boot-policy=
xe vm-param-set  uuid=db74941f-2ccc-9c01-ecb2-bc2e26ffce19 PV-kernel=/boot/guest/netxen
xe vm-param-set  uuid=db74941f-2ccc-9c01-ecb2-bc2e26ffce19 PV-args=boot_verbose=1,vfs.root.mountfrom=ffs:/dev/xbd1s1a,kern.hz=100

and modifying the /etc/fstab and ifconfig.xennet0 files
- copy the XEN3_DOMU kernel to /boot/guest/netxen on the XenServer 

>Fix:
None known to me at this time.

>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: kern-bug-people->port-xen-bug-people
Responsible-Changed-By: jdolecek@NetBSD.org
Responsible-Changed-When: Tue, 14 Aug 2018 17:49:02 +0000
Responsible-Changed-Why:
Moved to port-xen


State-Changed-From-To: open->feedback
State-Changed-By: jdolecek@NetBSD.org
State-Changed-When: Tue, 14 Aug 2018 17:49:02 +0000
State-Changed-Why:
an you confirm whether this still happens with 8.0?


Responsible-Changed-From-To: port-xen-bug-people->port-xen-maintainer
Responsible-Changed-By: jdolecek@NetBSD.org
Responsible-Changed-When: Tue, 28 Aug 2018 18:37:59 +0000
Responsible-Changed-Why:
Fixing to port-xen-maintainer


From: Chavdar Ivanov <ci4ic4@gmail.com>
To: gnats-bugs@gnats.netbsd.org
Cc: 
Subject: Re: port-xen/47486
Date: Thu, 20 Dec 2018 10:16:32 +0000

 NetBSD-current amd64 8.99.26:
 --
 # uname -a
 NetBSD hween 8.99.26 NetBSD 8.99.26 (XEN3_DOMU) #9: Sun Nov 25
 00:42:10 GMT 2018
 sysbuild@ymir:/home/sysbuild/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/XEN3_DOMU
 amd64
 --

 Tested under XCP-NG v. 7.6 in PV mode. sshd works fine, so whatever
 the problem was, it has been fixed in the mean time.

 At the moment the same guest is running 8.99.27 from a few days ago
 without a problem.
 -- 
 ----

State-Changed-From-To: feedback->closed
State-Changed-By: bouyer@NetBSD.org
State-Changed-When: Thu, 20 Dec 2018 15:32:03 +0000
State-Changed-Why:
Submitter reports the problem is fixed in newer versions.


>Unformatted:

Home	PR Database Search