r324421 amd64 kernel panics when entering multiuser mode

2017-10-09 Thread Oleg V. Nauman
panic: freeing invalid range cpuid = 0 time = 1507550062 Uptime: 2s . #0 doadump (textdump=) at pcpu.h:232 232 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:232 #1 0x804d68b6 in kern_reboot (howto=260) at /usr/src/sys/kern/k

Re: r324421 amd64 kernel panics when entering multiuser mode

2017-10-09 Thread Alan Cox
On Mon, Oct 9, 2017 at 4:22 AM, Oleg V. Nauman wrote: > panic: freeing invalid range > cpuid = 0 > time = 1507550062 > Uptime: 2s > . > #0 doadump (textdump=) at pcpu.h:232 > 232 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump (textdump=) at > pcpu.h:232 >

Re: r324421 amd64 kernel panics when entering multiuser mode

2017-10-09 Thread Oleg V. Nauman
On Monday 09 October 2017 05:05:14 Alan Cox wrote: > On Mon, Oct 9, 2017 at 4:22 AM, Oleg V. Nauman wrote: > > panic: freeing invalid range > > cpuid = 0 > > time = 1507550062 > > Uptime: 2s > > . > > #0 doadump (textdump=) at pcpu.h:232 > > 232 pcpu.h: No such file or directory. > >

Re: RFC how to use kernel procs/threads efficiently

2017-10-09 Thread Rick Macklem
Ian Lepore wrote: [stuff snipped] >taskqueue(9) is an existing mechanism to enqueue functions to execute >asynch using a pool of threads, but it doesn't answer the scalability >questions. In fact it may make them harder, inasmuch as I don't think >there's

Re: C++ in jemalloc

2017-10-09 Thread David Goldblatt
Re: the risk of dependencies on the C++ runtime. (apologies Konstantin, your email got trapped in a spam filter; "It is in violation of Google's recommended email sender guidelines", according to GMail). Avoiding C++ runtime dependencies is fairly straightforward in practice (e.g. a program that

latest iwm patches don't work with my 8265 chip

2017-10-09 Thread Pete Wright
hey there - i was really excited to see GNN's recent commits to add support to the 8265 Intel WiFi devices: https://svnweb.freebsd.org/base?view=revision&revision=324434 unfortunately this does not seem to work on my system.  after building and rebooting dmesg reports this: iwm0: mem 0xdf00

Re: latest iwm patches don't work with my 8265 chip

2017-10-09 Thread Pete Wright
On 10/09/2017 16:02, Pete Wright wrote: hey there - i was really excited to see GNN's recent commits to add support to the 8265 Intel WiFi devices: https://svnweb.freebsd.org/base?view=revision&revision=324434 unfortunately this does not seem to work on my system.  after building and reboot

Re: RFC how to use kernel procs/threads efficiently

2017-10-09 Thread Julian Elischer
On 10/10/17 4:25 am, Rick Macklem wrote: Ian Lepore wrote: [stuff snipped] taskqueue(9) is an existing mechanism to enqueue functions to execute asynch using a pool of threads, but it doesn't answer the scalability questions. In fact it may make them har