Re: Panics from today's sources

[John Klos <john%ziaspace.com@localhost>]

Hi,

> On Sun, Apr 03, 2022 at 05:20:37PM +0000, John Klos wrote:
> > [ 56496.032711] uvm_fault(0xffffffff81908580, 0xffffbd134d9bc000, 2) -> e
> > [ 56496.032711] fatal page fault in supervisor mode
> > [ 56496.032711] trap type 6 code 0x2 rip 0xffffffff80c4f634 cs 0x8 rflags
> > 0x10202 cr2 0xffffbd134d9bcc90 ilevel 0 rsp 0xffffa604bbfebda0
> > [ 56496.032711] curlwp 0xfffffd0d7.0327109] panic: trap
> > [ 56496.032711] cpu5: Begin traceback...
> > panic() at netbsd:panic+0x3c
> > [ 56496.032711] trap() at netbsd7109] uvm_pagefree() at
> > netbsd:uvm_pagefree+0x2d5
> > [ 56496.003271] uvm_unmapace_free() at netbsd:uvmspace_free+0xe4
> > [ 56496.042711] exit1()_exit+0x39
> > [ 56496.042711] syscall() at netbsd:syscall+0x1f2
> > cpu5: End traceback...
>
> Is that happening to specific processes? Which process is trying to exit here?
> I have updated three machines today and don't see anything like that so far.

I've been stress testing, so the system was running a pkg_rolling-replace 
with some heavy packages like rust and firefox, plus running build.sh of 
NetBSD-current in a tmpfs in a loop, plus running VMs in simh and qemu, so 
it'd be hard to say which process it was at the time.

However, after updating to more recent -current, this hasn't happened any 
more, so I think it's safe to say that whatever was causing it has been 
fixed.

Thanks,
John