On 27.12.2017 22:04, Andreas Gustafsson wrote: > I just noticed another problem that may be related: on pmax, the > t_ptrace_wait test is triggering a panic: > > babylon5.netbsd.org$ tail -n 19 /bracket/pmax/test/2017.12.25.17.00.15/test.log > lib/libc/sys/t_ptrace_wait (279/719): 81 test cases > attach3: [0.417968s] Passed. > attach4: [0.402344s] Passed. > eventmask1: [0.382812s] Passed. > eventmask2: [1.054688s] Passed. > eventmask3: sorry, pid 14241 was killed: orphaned traced process > [0.367187s] Expected failure: PR kern/51630: /tmp/bracket/build/2017.12.25.17.00.15-pmax/src/tests/lib/libc/sys/t_ptrace_wait.c:1137: memcmp(&set_event, &get_event, len) == 0 not met > eventmask4: [0.371094s] Passed. > eventmask5: [0.367188s] Passed. > eventmask6: [0.902343s] Passed. > fork2: [0.402344s] Passed. > fpregs1: [ warning: LOW reference: vaddr=0x00000084, exception TLBL, pc=0x800580dc <(no symbol)> ] > pid 18518(t_ptrace_wait): trap: cpu0, TLB miss (load or instr. fetch) in kernel mode > status=0x8ff34, cause=0x8, epc=0x800580dc, vaddr=0x84 > tf=0x80b038b0 ksp=0x80b03950 ra=0x8036799c ppl=0x8054cee0 > kernel: TLB miss (load or instr. fetch) trap > Stopped in pid 18518.1 (t_ptrace_wait) at netbsd:process_read_fpregs+0x14: > lw v1,0(a2) > db> > > This started some time between source date 2017.12.07.03.25.51 and > 2017.12.12.08.27.32. > That one looks like a MIPS bug with fpregs read/write. Is this reproducible always?
Attachment:
signature.asc
Description: OpenPGP digital signature