Re: port-vax/57839

["Jan-Benedict Glaw via gnats" <gnats-admin%NetBSD.org@localhost>]

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

From: Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: port-vax/57839
Date: Thu, 5 Nov 2026 23:45:01 +0100

 --oNku53dHTcHtLiB4
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 Hi,
 
 first of all, this issue is still reproducible with an
 DIAGNOSTIC-enabled kernel (here in SIMH; needed to upsize the miniroot
 fs from 8m to 10m):
 
 [ 1398.1366770] panic: pmap_destroy used pmap
 [ 1398.1366770] cpu0: Begin traceback...
 [ 1398.1466792] Stack traceback:
 [ 1398.3567255] 0xa71e9d44: vpanic+0x17c(0x8039afcf,0xa71e9ddc)
 [ 1398.5867762] 0xa71e9d64: aprint_verbose+0x0(0x8039afcf)
 [ 1398.7968225] 0xa71e9d90: pmap_kenter_pa+0x0(0x9f525740)
 [ 1399.0168710] 0xa71e9de0: uvmspace_free+0x7b(0x9fea4d80)
 [ 1399.2069129] 0xa71e9e08: uvm_proc_exit+0x53(0x9f8ca640)
 [ 1399.2869305] 0xa71e9e2c: exit1+0x170(0x9f8ae880,0,0)
 [ 1399.3669481] 0xa71e9ed8: sys_exit+0x31(0x9f8ae880,0xa71e9f54,0xa71e9f4c)
 [ 1399.5169812] 0xa71e9f18: syscall+0xec(0xa71e9fb4)
 [ 1399.5169812] cpu0: End traceback...
 
 [ 1399.5169812] dump to dev 9,1 not possible
 
 HALT instruction, PC: 80013FFC (PUSHAB 8039B207)
 
 
 =2E..while on a non-DIAG  kernel, the test just passes.
 
 
 
 I think there's still a pm_pcbs referencing the pmap when it is fed to
 pmap_destroy, It's always linked in through cpu_lwp_fork(), and
 cleared through pmap_deactivate() called through mi_switch(). But that
 doesn't happen if the LWP never runs (eg. through error pathes.) The
 testcase (lwp_create_bad_lid_ptr) provokes such an error path.
 
   Right now, I'm building a new kernel that invokes pmap_deactivate()
 in cpu_lwp_free() IFF l !=3D curlwp.  That should be enough I hope...
 
   Martin, ISTR that you stated something like you'd like to run ATF
 more often on VAX, but you tend to have DIAGNOSTIC enabled. I really
 hope this catches it!
 
 MfG, JBG
 
 --=20
 
 --oNku53dHTcHtLiB4
 Content-Type: application/pgp-signature; name="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 
 iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCau0G6QAKCRAdvV51g5nh
 u6gsAJ4vOkf+lTixb/sCvzFZcqdWdxayHgCdFZn421agAm00YQH9f16/NE8lW14=
 =hldp
 -----END PGP SIGNATURE-----
 
 --oNku53dHTcHtLiB4--