[Bug 148807] [panic] 8.1-RELEASE/10.1-STABLE "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 Steve Wills changed: What|Removed |Added CC|

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 Kubilay Kocak changed: What|Removed |Added Flags||mfc-stable9?,

Re: Unstable local network throughput

> On 11 Aug 2016, at 18:36, Adrian Chadd wrote: > > Hi! Hi Adrian, > mlx4_core0: mem > 0xfbe0-0xfbef,0xfb00-0xfb7f irq 64 at device 0.0 > numa-domain 1 on pci16 > mlx4_core: Initializing mlx4_core: Mellanox ConnectX VPI driver v2.1.6 > (Aug 11 2016) >

Re: Unstable local network throughput

Hi! mlx4_core0: mem 0xfbe0-0xfbef,0xfb00-0xfb7f irq 64 at device 0.0 numa-domain 1 on pci16 mlx4_core: Initializing mlx4_core: Mellanox ConnectX VPI driver v2.1.6 (Aug 11 2016) so the NIC is in numa-domain 1. Try pinning the worker threads to numa-domain 1 when you run the test:

Re: Unstable local network throughput

> On 11 Aug 2016, at 19:51, Ben RUBSON wrote: > > >> On 11 Aug 2016, at 18:36, Adrian Chadd wrote: >> >> Hi! > > Hi Adrian, > >> mlx4_core0: mem >> 0xfbe0-0xfbef,0xfb00-0xfb7f irq 64 at device 0.0 >> numa-domain 1 on pci16 >>

Re: Unstable local network throughput

On 08/11/16 12:54 PM, Ben RUBSON wrote: > >> On 11 Aug 2016, at 19:51, Ben RUBSON wrote: >> >> >>> On 11 Aug 2016, at 18:36, Adrian Chadd wrote: >>> >>> Hi! >> >> Hi Adrian, >> >>> mlx4_core0: mem >>> 0xfbe0-0xfbef,0xfb00-0xfb7f irq

Re: Unstable local network throughput

> On 11 Aug 2016, at 18:36, Adrian Chadd wrote: > > Hi! > > mlx4_core0: mem > 0xfbe0-0xfbef,0xfb00-0xfb7f irq 64 at device 0.0 > numa-domain 1 on pci16 > mlx4_core: Initializing mlx4_core: Mellanox ConnectX VPI driver v2.1.6 > (Aug 11 2016) > > so the

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #27 from Mike Andrews --- For what it's worth, the original problem I reported in this PR from 6 years ago is (for me anyway) long-ago solved... but then we're on 10.3 these days and are slowly rolling

Re: Unstable local network throughput

adrian did mean fixed-domain-rr. :-P sorry! (Sorry, needed to update my NUMA boxes, things "changed" since I wrote this.) -a ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail

Re: Unstable local network throughput

Which ones of these hit the line rate comfortably? -a On 11 August 2016 at 15:35, Ben RUBSON wrote: > >> On 11 Aug 2016, at 18:36, Adrian Chadd wrote: >> >> Hi! >> >> mlx4_core0: mem >> 0xfbe0-0xfbef,0xfb00-0xfb7f irq 64 at

Re: Panic in stable/11 (amd64) @r303903: page fault while in kernel mode

[snip] #define IF_LLADDR(ifp) \ LLADDR((struct sockaddr_dl *)((ifp)->if_addr->ifa_addr)) it's because if_addr is NULL in your dump. God knows why that is! My guess is we caught it in some stupid update window. Ok, so what should we do for

Re: Unstable local network throughput

> On 11 Aug 2016, at 00:11, Adrian Chadd wrote: > > hi, > > ok, lets start by getting the NUMA bits into the kernel so you can > mess with things. > > add this to the kernel > > options MAXMEMDOM=8 > (which hopefully is enough) > options VM_NUMA_ALLOC > options

Re: Unstable local network throughput

> On 11 Aug 2016, at 18:36, Adrian Chadd wrote: > > Hi! > > mlx4_core0: mem > 0xfbe0-0xfbef,0xfb00-0xfb7f irq 64 at device 0.0 > numa-domain 1 on pci16 > mlx4_core: Initializing mlx4_core: Mellanox ConnectX VPI driver v2.1.6 > (Aug 11 2016) > > so the