Re: port-sparc64/46274: sparc64 running netbsd 32bit code causes a lot of cores

[Martin Husemann <martin%duskware.de@localhost>]

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

From: Martin Husemann <martin%duskware.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: port-sparc64/46274: sparc64 running netbsd 32bit code causes a lot 
of cores
Date: Thu, 29 Mar 2012 15:56:47 +0200

 I don't know if this is related, but I'll document it here anyway:
 
 when trying to boot a full 32bit install with a 64bit kernel, the exec
 of /sbin/init fails with a strange data fault as well:
 
 root file system type: ffs
 init: copying out path `/sbin/init' 11
 vmcmds 7
 vmcmd[0] = vmcmd_map_pagedvn 0x10000/0x6000 fd@0 prot=05 flags=4
 vmcmd[1] = vmcmd_map_readvn 0x24000/0x698 fd@0x4000 prot=07 flags=4
 vmcmd[2] = vmcmd_map_pagedvn 0x40030000/0x12000 fd@0 prot=05 flags=2
 vmcmd[3] = vmcmd_map_zero 0x12000/0x10000 fd@0 prot=00 flags=1
 vmcmd[4] = vmcmd_map_readvn 0x22000/0xbe0 fd@0x12000 prot=03 flags=1
 vmcmd[5] = vmcmd_map_zero 0xff7fe000/0x600000 fd@0 prot=00 flags=8
 vmcmd[6] = vmcmd_map_zero 0xffdfe000/0x200000 fd@0 prot=03 flags=8
 execve_runproc finished
 panic: System process (pid 1) got sig 11
 
 Stopped in pid 1.1 (init) at    netbsd:cpu_Debugger+0x4:        nop
 db{1}> bt
 panic(1290078, 1, b, 400, 1000000, 2) at netbsd:panic+0x24
 issignal(3ce9800, 0, 3ce9800, 0, 0, b) at netbsd:issignal+0x3d4
 lwp_userret(3ce9800, 128dba8, 3d01c78, 8, 12a53c8, 127d930) at 
netbsd:lwp_userre
 t+0x200
 data_access_fault(5ac8fed0, 30, 40032a5c, 140052002, 140052814, 800801) at 
netbs
 d:data_access_fault+0x798
 
 Note that the faulting adress (0x40032a5c) should be properly mapped
 by vmcmd[2], backed by a vnode, and should just have been paged in.
 This happens before any syscall from init happens, AFAICT.
 
 Martin