Re: Jemalloc fallout on sandpoint

2019-04-11 Thread Frank Wille
Quoting Robert Swindells : Do powerpc kernels have a sysctl for page size ? I'm fairly sure that arm does. Yes. It has: # sysctl -a | grep page hw.pagesize = 4096 But I don't know if you can change that at runtime. -- Frank Wille

re: Jemalloc fallout on sandpoint

2019-04-09 Thread matthew green
> Do powerpc kernels have a sysctl for page size ? I'm fairly sure that > arm does. everyone has this :-) getpagesize() is the simple method, but the standards function is sysconf(_SC_PAGESIZE). .mrg.

Re: Jemalloc fallout on sandpoint

2019-04-09 Thread Julian Coleman
Hi Christos, > The problem is that on powerpc we use MAX_PAGE_SHIFT not the right page > shift for the machine. I will fix it to compute and use the MIN_PAGE_SHIFT > soon. This: Modified Files: src/external/bsd/jemalloc/include/jemalloc/internal: jemalloc_internal_defs.h

Re: Jemalloc fallout on sandpoint

2019-04-09 Thread Christos Zoulas
In article , Robert Swindells wrote: >On 2019-04-09 01:26, Jason Thorpe wrote: >>> 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 possib

Re: Jemalloc fallout on sandpoint

2019-04-09 Thread Robert Swindells
On 2019-04-09 01:26, Jason Thorpe wrote: 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 f

Re: Jemalloc fallout on sandpoint

2019-04-09 Thread Christos Zoulas
In article <20190408213840.ga11...@orion.coris.org.uk>, Julian Coleman wrote: >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] Abo

Re: Jemalloc fallout on sandpoint

2019-04-09 Thread Rin Okuyama
On 2019/04/09 14:26, Julian Coleman wrote: 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 mainb

Re: Jemalloc fallout on sandpoint

2019-04-08 Thread Julian Coleman
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

Re: Jemalloc fallout on sandpoint

2019-04-08 Thread Jason Thorpe
> 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

Jemalloc fallout on sandpoint

2019-04-08 Thread Julian Coleman
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 ba