Re: Jemalloc fallout on sandpoint
Hi Jason, > What kind of CPU is in this device? It's possible that jemalloc is making a > page size assumption that isn't true for this particular powerpc CPU (I think > there were other issues like this on another port...) It is: [ 1.000] cpu0 at mainbus0: 8245 (Revision 0.4), ID 0 (primary) [ 1.000] cpu0: HID0 0x90c000, powersave: 1 [ 1.000] cpu0: 265.31 MHz Regards, Julian
daily CVS update output
Updating src tree: P src/lib/libc/sys/modctl.2 P src/lib/libc/time/localtime.c P src/share/man/man9/filedesc.9 P src/sys/arch/aarch64/aarch64/pmap.c P src/sys/arch/aarch64/include/asan.h P src/sys/arch/aarch64/include/pmap.h P src/sys/arch/alpha/include/elf_machdep.h P src/sys/arch/arm/arm/armv6_start.S P src/sys/arch/sh3/sh3/kobj_machdep.c P src/sys/arch/vax/vsa/vsaudio.c P src/sys/dev/nvmm/nvmm.c P src/sys/dev/nvmm/nvmm_internal.h P src/sys/dev/pci/if_bnx.c P src/sys/dev/pci/yds.c P src/sys/kern/kern_module.c P src/sys/kern/subr_exec_fd.c P src/sys/kern/uipc_socket.c P src/sys/sys/module.h P src/usr.sbin/npf/npfctl/npf.conf.5 P src/usr.sbin/screenblank/screenblank.1 Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 41061011 Apr 9 03:03 ls-lRA.gz
Re: Jemalloc fallout on sandpoint
> On Apr 8, 2019, at 2:40 PM, Julian Coleman wrote: > > Hi all, > > Upgraded my QNAP TS-201 (sandpoint) to current, and all binaries crash with: What kind of CPU is in this device? It's possible that jemalloc is making a page size assumption that isn't true for this particular powerpc CPU (I think there were other issues like this on another port...) > : /usr/src/external/bsd/jemalloc/lib/../dist/src/pages.c:273: > Failed assertion: "PAGE_ADDR2BASE(addr) == addr" > [1] Abort trap (core dumped) sh > > Not sure how we can pass in an address that isn't the page base address here. > It looks like the allocations from pages.c have the same assertion, so they > shouldn't cause this. Could base_block_alloc() be allocating a block that > starts at an address that isn't a multiple of the page size? Should we > assert "PAGE_ADDR2BASE(block) == block" every time we allocate a block? > > Regards, > > Julian -- thorpej
Jemalloc fallout on sandpoint
Hi all, Upgraded my QNAP TS-201 (sandpoint) to current, and all binaries crash with: : /usr/src/external/bsd/jemalloc/lib/../dist/src/pages.c:273: Failed assertion: "PAGE_ADDR2BASE(addr) == addr" [1] Abort trap (core dumped) sh Not sure how we can pass in an address that isn't the page base address here. It looks like the allocations from pages.c have the same assertion, so they shouldn't cause this. Could base_block_alloc() be allocating a block that starts at an address that isn't a multiple of the page size? Should we assert "PAGE_ADDR2BASE(block) == block" every time we allocate a block? Regards, Julian
Re: pkgsrc/doc/guide build failure on -current (more jemalloc fallout)
I've files pkg/54105. On Mon, 8 Apr 2019 at 09:51, Chavdar Ivanov wrote: > > OK, I will file a PR against openjade. > > On Mon, 8 Apr 2019 at 08:18, Martin Husemann wrote: > > > > On Sun, Apr 07, 2019 at 08:21:07PM +0100, Chavdar Ivanov wrote: > > > : > > > /home/sysbuild/src/external/bsd/jemalloc/lib/../dist/src/arena.c:271: > > > Failed assertion: "bitmap_get(slab_data->bitmap, > > > &bin_info->bitmap_info, regind)" > > > *** Signal 6 > > > > Can you build tex with debug info and get a backtrace from that core, > > and (then/instead) file a bug against that TeX version? > > > > It very likely is a bug in the application (use after free or similar). > > > > Martin > > > > -- > --
Re: pkgsrc/doc/guide build failure on -current (more jemalloc fallout)
OK, I will file a PR against openjade. On Mon, 8 Apr 2019 at 08:18, Martin Husemann wrote: > > On Sun, Apr 07, 2019 at 08:21:07PM +0100, Chavdar Ivanov wrote: > > : > > /home/sysbuild/src/external/bsd/jemalloc/lib/../dist/src/arena.c:271: > > Failed assertion: "bitmap_get(slab_data->bitmap, > > &bin_info->bitmap_info, regind)" > > *** Signal 6 > > Can you build tex with debug info and get a backtrace from that core, > and (then/instead) file a bug against that TeX version? > > It very likely is a bug in the application (use after free or similar). > > Martin --
Re: pkgsrc/doc/guide build failure on -current (more jemalloc fallout)
On Sun, Apr 07, 2019 at 08:21:07PM +0100, Chavdar Ivanov wrote: > : > /home/sysbuild/src/external/bsd/jemalloc/lib/../dist/src/arena.c:271: > Failed assertion: "bitmap_get(slab_data->bitmap, > &bin_info->bitmap_info, regind)" > *** Signal 6 Can you build tex with debug info and get a backtrace from that core, and (then/instead) file a bug against that TeX version? It very likely is a bug in the application (use after free or similar). Martin
Re: mcelog?
On Apr 7, 9:48pm, "Aaron J. Grier" wrote: } On Wed, Mar 20, 2019 at 11:22:13AM -0700, John Nemeth wrote: } > I originally posted this on port-amd64, but didn't get any } > response, so now trying a list with a wider audience. } > } > One of my Xen hosts has been getting this error a lot: } > } > (XEN) Bank 4: 945a4000fd080813 atef3581180 } > (XEN) MCE: polling routine found correctable error. Use mcelog to parse above e } > rror output. } [...] } > In any event, if I'm reading the above correctly, I believe } > that it is telling that there is bad memory? } } which CPU manufacturer and model is this? memory is just one of many } possibilities which can generate machine check events. cpu0: "AMD Opteron(tm) Processor 6386 SE " cpu0: AMD Family 15h (686-class) cpu0: family 0x15 model 0x2 stepping 0 (id 0x600f20) } are we going to get an MSR interface for NetBSD any time soon? That would be nice. }-- End of excerpt from "Aaron J. Grier"
