Nope, same with http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201402240050Z/amd64/binary/kernel/netbsd-GENERIC.gz
( same with slight change in the addresses ). .... boot device: raid0 root on raid0a dumps on raid0b root file system type: ffs uvm_fault(0xfffffe8006d1be60, 0x0, 1) -> e uvm_fault(0xfffffe8006d1be60, 0x0, 1) -> e fatal page fault in supervisor mode trap type 6 code 0 rip ffffffff807d3d3b cs 8 rflags 10246 cr2 0 ilevel 0 rsp fffffe8006d097b0 curlwp 0xfffffe8006d2ea00 pid 1.1 lowest kstack 0xfffffe8006d06280 kernel: page fault trap, code=0 Stopped in pid 1.1 (init) at netbsd:trap+0x99b: movzwl 0(%rax),%eax db{1}> bt trap() at netbsdL:trap+0x9c8 --- trap (number 6) --- ?() at 0 execve_loadvm() at netbsd:execve_loadvm+0x1db execve1() at netbsd:execve1+0x2d start_init() at netbsd:start_init+0x2a7 db{1}> ... On 21 February 2014 20:32, David Laight <da...@l8s.co.uk> wrote: > On Fri, Feb 21, 2014 at 02:24:34PM +0000, Chavdar Ivanov wrote: >> The panic still takes place with 6.99.32 from the overnight build. > > Something must be different about your build (or system). > Any guesses. > > The first address printed for the faulting %rip is the one that is > most likely to be right. > > David > > -- > David Laight: da...@l8s.co.uk -- ----