Re: A RPi4B panic from 9.99.70 NetBSD for a diagnostic assertion failure: The traceback

[Mark Millard <marklmi%yahoo.com@localhost>]

It took a lot of activity but I got another panic
(of the same type):

[ 8337.1806591] panic: kernel diagnostic assertion "uvm_pagelookup(uobj, offset) == NULL || ((a->ar_flags & UVM_PAGE_ARRAY_FILL_DIRTY) != 0 && !uvm_obj_page_dirty_p(pg))" failed: file "/home/source/ab/HEAD/src/sys/uvm/uvm_vnode.c", line 321 
[ 8337.2006589] cpu1: Begin traceback...
[ 8337.2006589] trace fp ffffc0008233f680
[ 8337.2106591] fp ffffc0008233f6b0 vpanic() at ffffc000004b8908 netbsd:vpanic+0x150
[ 8337.2106591] fp ffffc0008233f720 kern_assert() at ffffc000007d772c netbsd:kern_assert+0x5c
[ 8337.2206591] fp ffffc0008233f7b0 uvn_findpage() at ffffc0000043db5c netbsd:uvn_findpage+0xfc
[ 8337.2306589] fp ffffc0008233f820 uvn_findpages() at ffffc0000043dec8 netbsd:uvn_findpages+0xb8
[ 8337.2406590] fp ffffc0008233f920 genfs_do_putpages() at ffffc0000052d2ec netbsd:genfs_do_putpages+0xb5c
[ 8337.2506587] fp ffffc0008233fb40 VOP_PUTPAGES() at ffffc000005295dc netbsd:VOP_PUTPAGES+0x3c
[ 8337.2606589] fp ffffc0008233fba0 ffs_write() at ffffc0000040a15c netbsd:ffs_write+0x2ec
[ 8337.2706587] fp ffffc0008233fc40 VOP_WRITE() at ffffc00000528128 netbsd:VOP_WRITE+0x40
[ 8337.2706587] fp ffffc0008233fc90 vn_write() at ffffc0000051fb00 netbsd:vn_write+0x108
[ 8337.2806588] fp ffffc0008233fce0 dofilewrite() at ffffc000004c8798 netbsd:dofilewrite+0x70
[ 8337.2906604] fp ffffc0008233fd60 sys_pwrite() at ffffc0000051626c netbsd:sys_pwrite+0xac
[ 8337.3006594] fp ffffc0008233fdb0 syscall() at ffffc0000008c9bc netbsd:syscall+0x18c
[ 8337.3106615] fp ffffc0008233fe60 trap_el0_sync() at ffffc0000008dac0 netbsd:trap_el0_sync+0x60
[ 8337.3106615] tf ffffc0008233fed0 el0_trap() at ffffc0000008ad0c netbsd:el0_trap
[ 8337.3206597] ---- trapframe 0xffffc0008233fed0 (304 bytes) ----
[ 8337.3306598]     pc=0000f5e8bc1b9d18,   spsr=0000000060000000
[ 8337.3306598]    esr=00000000560000ae,    far=ffffc0005995d000
[ 8337.3406598]     x0=0000000000000004,     x1=0000f5e8bc53c430
[ 8337.3406598]     x2=0000000000001000,     x3=0000000000000000
[ 8337.3506598]     x4=000000000081f000,     x5=000000000000081e
[ 8337.3606600]     x6=0000000000001000,     x7=0000000000000000
[ 8337.3606600]     x8=0000f5e8bca9e188,     x9=0000fffffffbe0b0
[ 8337.3706606]    x10=0000000000000040,    x11=000000000000003f
[ 8337.3706606]    x12=000003d7a2f02030,    x13=000003d7a2f02080
[ 8337.3806601]    x14=0000f5e8bbc008c0,    x15=0000f5e8bc082000
[ 8337.3806601]    x16=0000f5e8bc313558,    x17=0000f5e8bc1b9d14
[ 8337.3906604]    x18=0000000000000057,    x19=0000f5e8bc563000
[ 8337.4006602]    x20=0000f5e8bca3d800,    x21=00000002001092e8
[ 8337.4006602]    x22=0000f5e8bca5f120,    x23=000000020011d000
[ 8337.4106606]    x24=0000000000000000,    x25=000000020010a270
[ 8337.4106606]    x26=0000000000000000,    x27=0000000000000000
[ 8337.4206604]    x28=0000000000000000, fp=x29=0000fffffffbe300
[ 8337.4206604] lr=x30=0000f5e8bc5484e0,     sp=0000fffffffbe300
[ 8337.4306606] ------------------------------------------------
[ 8337.4406610] cpu1: End traceback...

[ 8337.4406610] dumping to dev 168,2 offset 19047695
[ 8337.4406610] dump 

(Again hung up.)


I had updated /usr/src and /usr/xsrc (tar expands)
and /usr/pkgsrc (cvs). I was doing pkg_chk -u -s
when it failed.

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)