syslogd dumps core on amd64 cuurent - working now

I rebuilt world and it is working now ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

syslogd dumps core on amd64 cuurent

Todays change to syslogd.c causes it to dump core on starting: (syslogd)5014}/etc/rc.d/syslogd stop Stopping syslogd. Waiting for PIDS: 731. (syslogd)5015}make install install -s -o root -g wheel -m 555 syslogd /usr/sbin/syslogd install -o root -g wheel -m 444 syslog.conf.5.gz

Re: NFSv4 performance degradation with 12.0-CURRENT client

Alan Somers wrote: [stuff snipped] >Mounting nullfs with the nocache option, ad kib suggested, fixed the >problem. Also, applying kib's patch and then mounting nullfs with >default options also fixed the problem. Here is the nfsstat output >for "ls -al" when using kib's patch. Notice the client

Re: NFSv4 performance degradation with 12.0-CURRENT client

Konstantin Belousov wrote: [stuff snipped] >I thought that the issue was in tracking any opens and mmaps, but from this >reply it is not that clear. Do you need callback when all opens and mmaps >have ended, or only opens and mmaps for write ? If later, we already have >a suitable mechanism

Re: Enabling NUMA in BIOS stop booting FreeBSD

On Sat, Nov 26, 2016 at 01:55:14PM -0800, Adrian Chadd wrote: > ok, hm. then i don' know offhand, not without putting in printf debugging. :) I am not expert in this code, I am need you patches for printf debugging. > On 26 November 2016 at 13:51, Slawa Olhovchenkov wrote: > >

Re: Enabling NUMA in BIOS stop booting FreeBSD

ok, hm. then i don' know offhand, not without putting in printf debugging. :) -a On 26 November 2016 at 13:51, Slawa Olhovchenkov wrote: > On Sat, Nov 26, 2016 at 01:49:00PM -0800, Adrian Chadd wrote: > >> Ok. So boot verbose and let's see what it says. > > See first message:

Re: Enabling NUMA in BIOS stop booting FreeBSD

On Sat, Nov 26, 2016 at 01:49:00PM -0800, Adrian Chadd wrote: > Ok. So boot verbose and let's see what it says. See first message: it's already verbose boot. Yes, only 3 lines. > > On 26 November 2016 at 10:39, Slawa Olhovchenkov wrote: > > On Sat, Nov 26, 2016 at 09:44:49AM

Re: Enabling NUMA in BIOS stop booting FreeBSD

Ok. So boot verbose and let's see what it says. -adrian On 26 November 2016 at 10:39, Slawa Olhovchenkov wrote: > On Sat, Nov 26, 2016 at 09:44:49AM -0800, Adrian Chadd wrote: > >> The ACPI SRAT parsing code - sys/x86/acpica/srat.c . >> >> I'd start by enabling bootverbose -

Re: Enabling NUMA in BIOS stop booting FreeBSD

On Sat, Nov 26, 2016 at 09:44:49AM -0800, Adrian Chadd wrote: > The ACPI SRAT parsing code - sys/x86/acpica/srat.c . > > I'd start by enabling bootverbose - adds one echo (SLIT.Localities and > the table); adds CPU affinity info (legacy, XAPIC, ACPI) and other > locality stuff. I am use r308809

Panic with some recent changes (between r309016 and r309184)

Is this known? The traceback: panic: vm_page_assert_xbusied: page 0xf807fae225b0 not exclusive busy @ /usr/src/sys/vm/vm_pager.c:263 cpuid = 5 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0a528ea620 vpanic() at vpanic+0x186/frame

boot fails on Table SSDT at 0x...

Hi curr...@freebsd.org I was running FreeBSD lapr.js.berklix.net 12.0-CURRENT FreeBSD 12.0-CURRENT #12753: Tue Nov 22 23:31:24 CET 2016 j...@lapr.js.berklix.net:/data/release/12.0-CURRENT/usr/src/sys/amd64/compile/LAPR.small amd64 I updated to .ctm_status

Re: Enabling NUMA in BIOS stop booting FreeBSD

The ACPI SRAT parsing code - sys/x86/acpica/srat.c . I'd start by enabling bootverbose - adds one echo (SLIT.Localities and the table); adds CPU affinity info (legacy, XAPIC, ACPI) and other locality stuff. -adrian On 26 November 2016 at 09:37, Slawa Olhovchenkov wrote: > On

Re: Enabling NUMA in BIOS stop booting FreeBSD

On Sat, Nov 26, 2016 at 09:35:08AM -0800, Adrian Chadd wrote: > It may be something to do with memory topology parsing. Maybe we need > some more debugging there to try and catch it. What debug you need? > On 26 November 2016 at 01:21, Slawa Olhovchenkov wrote: > > I am try to

Re: Enabling NUMA in BIOS stop booting FreeBSD

It may be something to do with memory topology parsing. Maybe we need some more debugging there to try and catch it. -a On 26 November 2016 at 01:21, Slawa Olhovchenkov wrote: > I am try to enable NUMA in bios and can't boot FreeBSD. > Boot stoped after next messages: > >

Re: Enabling NUMA in BIOS stop booting FreeBSD

On Sat, Nov 26, 2016 at 07:07:20PM +0300, Slawa Olhovchenkov wrote: > On Sat, Nov 26, 2016 at 05:57:47PM +0200, Konstantin Belousov wrote: > > > On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote: > > > I am try to enable NUMA in bios and can't boot FreeBSD. > > > Boot stoped

Re: Enabling NUMA in BIOS stop booting FreeBSD

On Sat, Nov 26, 2016 at 05:57:47PM +0200, Konstantin Belousov wrote: > On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote: > > I am try to enable NUMA in bios and can't boot FreeBSD. > > Boot stoped after next messages: > > > > === > > Booting... > > KDB: debugger backends: ddb >

Re: Enabling NUMA in BIOS stop booting FreeBSD

On Sat, Nov 26, 2016 at 05:57:47PM +0200, Konstantin Belousov wrote: > On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote: > > I am try to enable NUMA in bios and can't boot FreeBSD. > > Boot stoped after next messages: > > > > === > > Booting... > > KDB: debugger backends: ddb >

Re: Enabling NUMA in BIOS stop booting FreeBSD

On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote: > I am try to enable NUMA in bios and can't boot FreeBSD. > Boot stoped after next messages: > > === > Booting... > KDB: debugger backends: ddb > KDB: current backend: ddb So at least the hammer_time() has a chance to initialize

Enabling NUMA in BIOS stop booting FreeBSD

I am try to enable NUMA in bios and can't boot FreeBSD. Boot stoped after next messages: === Booting... KDB: debugger backends: ddb KDB: current backend: ddb === This is verbose boot. No reaction to ~^B, NMI. Same for head and 10.3-RELEASE. Hardware is Supermicro X10DRi, Dual E5-2650v4, 256GB