Re: port-sparc64/57219: ./configure for gcl-2.6.14 crashes kernel (reboot) on NetBSD 9.3 sparc64

[Alexander Schreiber <als%thangorodrim.ch@localhost>]

The following reply was made to PR port-sparc64/57219; it has been noted by GNATS.

From: Alexander Schreiber <als%thangorodrim.ch@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: port-sparc64/57219: ./configure for gcl-2.6.14 crashes kernel
 (reboot) on NetBSD 9.3 sparc64
Date: Tue, 7 Feb 2023 02:26:45 +0100

 Rebuilt a GENERIC with full DEBUG enabled:
 
 options        DIAGNOSTIC      # extra kernel sanity checking
 makeoptions     DEBUG="-g"
 options         DEBUG
 options         LOCKDEBUG
 options         DB_MAX_WIDTH=160
 options         DDB_ONPANIC=2   # print stack trace
 
 
 ran ./configure again and got this
 on the serial console:
 
 login: [ 1533.9117629] vmcmds 0/8, error 12
 [ 1533.9512858] vmcmd[0] = vmcmd_map_pagedvn 0/0x2000 fd@0 prot=05 flags=4
 [ 1534.0302952]      ^--- failed
 [ 1534.0656327] vmcmd[1] = vmcmd_map_readvn 0x100000/0x1388 fd@0 prot=07 flags=4
 [ 1534.1508814] vmcmd[2] = vmcmd_map_pagedvn 0x40200000/0x14000 fd@0 prot=05 flags=2
 [ 1534.2402860] vmcmd[3] = vmcmd_map_zero 0x14000/0x100000 fd@0 prot=00 flags=1
 [ 1534.3244898] vmcmd[4] = vmcmd_map_readvn 0x114000/0xe88 fd@0x14000 prot=03 flags=1
 [ 1534.4149331] vmcmd[5] = vmcmd_map_zero 0xfffffffff7efe000/0x100000 fd@0 prot=00 flags=0
 [ 1534.5105806] vmcmd[6] = vmcmd_map_zero 0xfffffffff7ffe000/0x7e00000 fd@0 prot=00 flags=8
 [ 1534.6072559] vmcmd[7] = vmcmd_map_zero 0xffffffffffdfe000/0x200000 fd@0 prot=03 flags=8
 [ 1534.7028980] execve_dovmcmds: vmcmd 0 failed: 12
 [ 1534.7579983] panic: kernel diagnostic assertion "start < end" failed: file "/usr/src/sys/uvm/uvm_map.c", line 4754 
 [ 1534.8827368] cpu0: Begin traceback...
 [ 1534.9263989] cpu0: End traceback...
 [ 1534.9679831] Frame pointer is at 0x178852d51
 [ 1534.9679831] Call traceback:
 [ 1534.9679831]  netbsd:cpu_reboot+0x244(19d1b70, 0, ffff, 19a12e9, 1606580, 1c70000) fp = 178852e31
 [ 1534.9679831]  netbsd:vpanic+0x174(104, 0, 195e658, 1cc2000, 0, 1034b1a00) fp = 178852ee1
 [ 1534.9679831]  netbsd:kern_assert+0x34(195e658, 1788538d8, 1cd9000, 1cda400, 104, 1cda508) fp = 178852f91
 [ 1534.9679831]  netbsd:uvm_unmap1+0xa8(195e658, 195e648, 19f0350, 19f0980, 1292, 2014000) fp = 178853051
 [ 1534.9679831]  netbsd:execve_runproc+0x42c(103a68610, 0, 0, 0, 0, 101e81780) fp = 178853111
 [ 1534.9679831]  netbsd:execve1+0x48(c, 178853ad8, 30, 0, 0, 103a80e08) fp = 178853221
 [ 1534.9679831]  netbsd:syscall+0x3dc(1034b1a00, 402a8c88, 402a8ca0, 402a8cb0, 15a2740, 1c62660) fp = 1788534f1
 [ 1534.9679831]  netbsd:1011abc+0(178853ed0, c3b, 40951828, 3b, 178853f40, 1034b1a00) fp = 178853621
 [ 1534.9679831]  netbsd:1105b8+0(402a8c88, 402a8ca0, 402a8cb0, 23b250, 160, 23bc04) fp = ffffffffffffbec1
 
 [ 1534.9679831] dumping to dev 12,1 offset 4194460
     16 M [ 1534.9679831] wddump: DMA error
 [ 1534.9679831] - i/o error
 [ 1535.0219663] tlp0: receive ring overrun
 [ 1535.0676942] cpu0: rebooting
 
 Upon reboot, savecore actually wrote a 100 MB compressed core to /var/crash/ ..