> From: Jeremie Courreges-Anglas <[email protected]>
> Date: Tue, 14 Dec 2021 13:29:11 +0100
> 
> On Fri, Oct 08 2021, Jeremie Courreges-Anglas <[email protected]> wrote:
> > riscv64.ports was running dpb(1) with two other members in the build
> > cluster.  A few minutes ago I found it in ddb(4).  The report is short,
> > sadly, as the machine doesn't return from the 'bt' command.
> >
> > The machine is acting both as an NFS server and and NFS client.
> >
> > OpenBSD/riscv64 (riscv64.ports.openbsd.org) (console)
> 
> Another crash, using a system built with clang 13.
> 
> OpenBSD/riscv64 (riscv64.ports.openbsd.org) (console)
> 
> login: Data modified on freelist: word 2308854010 of object 
> 0xffffffc023bdf910 size 0x10 previous type free (invalid addr 
> 0x9e7190984a8998c3)
> panic: malloc: wrong bucket
> Stopped at      panic+0x106:    addi    a0,zero,256    TID    PID    UID     
> PR
> FLAGS     PFLAGS  CPU  COMMAND
>   82701  17452      0        0x11          0    2  perl
>  277683   4352     55    0x100000          0    3  sh
>   77432  50275     55         0x2          0    0  cc
> *448509  16769      0        0x13          0    1K perl
> panic() at panic+0x102
> panic() at malloc+0x6a8
> malloc() at amap_alloc1+0x106
> amap_alloc1() at amap_copy+0xe6
> amap_copy() at uvm_fault_check+0x210
> uvm_fault_check() at uvm_fault+0xdc
> uvm_fault() at do_trap_user+0x11a
> https://www.openbsd.org/ddb.html describes the minimum info required in bug
> reports.  Insufficient info makes it difficult to find and fix bugs.
> ddb{1}> show panic
> *cpu1: malloc: wrong bucket
> ddb{1}> show uvm
> Current UVM status:
>   pagesize=4096 (0x1000), pagemask=0xfff, pageshift=12
>   4052437 VM pages: 97962 active, 20027 inactive, 1 wired, 3027027 free 
> (378378
>  zero)
>   min  10% (25) anon, 10% (25) vnode, 5% (12) vtext
>   freemin=135081, free-target=180108, inactive-target=180109, 
> wired-max=1350812
> 
>   faults=467319658, traps=0, intrs=0, ctxswitch=34286925 fpuswitch=0
>   softint=15861115, syscalls=218471585, kmapent=51
>   fault counts:
>     noram=0, noanon=0, noamap=0, pgwait=0, pgrele=0
>     ok relocks(total)=322246(322248), anget(retries)=257638497(0), 
> amapcopy=605
> 63375
>     neighbor anon/obj pg=216611560/170442328, 
> gets(lock/unlock)=135754423/32226
> 6
>     cases: anon=179416812, anoncow=78221685, obj=130852112, prcopy=4902291, 
> prz
> ero=73926772
>   daemon and swap counts:
>     woke=15, revs=0, scans=0, obscans=0, anscans=0
>     busy=0, freed=0, reactivate=0, deactivate=0
>     pageouts=0, pending=0, nswget=0
>     nswapdev=1
>     swpages=4259839, swpginuse=0, swpgonly=0 paging=0
>   kernel pointers:
>     objs(kern)=0xffffffc000a988d0
> ddb{1}>
> 
> 
> I'm a bit short on time and typing ddb commands on riscv64 often
> resulted into hangs so far, which sucks when you have no PDU to reset
> the machine.  So if you can think of some useful command to type please
> let me know soonish: I'd like to resume this llvm 13 ports bulk build.

Memory corruption of some sort.  I'm not going to lear much from more
poking.  So go ahead and reset the machine.

Reply via email to