Re: Intel Xeon D-2146NT SoC Support

2019-02-06 Thread O'Connor, Daniel
> On 7 Feb 2019, at 10:58, Lyndon Nerenberg wrote: > > [ I asked this on -hardware but didn't get any responses, so I'm > widening the scope a bit. ] > > We're looking a buying a Supermicro system with the X11SDV-8C-TP8F > motherboard. This uses a Xeon D-2146NT SoC. It's not clear what >

Intel Xeon D-2146NT SoC Support

2019-02-06 Thread Lyndon Nerenberg
[ I asked this on -hardware but didn't get any responses, so I'm widening the scope a bit. ] We're looking a buying a Supermicro system with the X11SDV-8C-TP8F motherboard. This uses a Xeon D-2146NT SoC. It's not clear what the embedded chipset is, so it's proving a bit tricky to confirm

Re: 9211 (LSI/SAS) issues on 11.2-STABLE

2019-02-06 Thread Karl Denninger
On 2/6/2019 09:18, Borja Marcos wrote: >> On 5 Feb 2019, at 23:49, Karl Denninger wrote: >> >> BTW under 12.0-STABLE (built this afternoon after the advisories came >> out, with the patches) it's MUCH worse. I get the same device resets >> BUT it's followed by an immediate panic which I cannot

Re: Request for more intelligent local port allocation algorithm

2019-02-06 Thread David King via freebsd-stable
Just to add to this, if anyone is doing some work on the outbound tcp connection, could they also have a look at the bug here https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210726 Thanks! On Wed, 6 Feb 2019 at 15:15, Paul wrote: > Hi dev team, > > It's not a secret that when application is

Re: 9211 (LSI/SAS) issues on 11.2-STABLE

2019-02-06 Thread Borja Marcos
> On 5 Feb 2019, at 23:49, Karl Denninger wrote: > > BTW under 12.0-STABLE (built this afternoon after the advisories came > out, with the patches) it's MUCH worse. I get the same device resets > BUT it's followed by an immediate panic which I cannot dump as it > generates a page-fault

Request for more intelligent local port allocation algorithm

2019-02-06 Thread Paul
Hi dev team, It's not a secret that when application is trying to establish new TCP connection, without first binding a socket to specific local interface address, OS handles that automatically. Unfortunately there is a catch, that lies in a different logic of local port allocation: (1) when

Re: More CARP issues under 12

2019-02-06 Thread Pete French
On 06/02/2019 12:16, Andrey V. Elsukov wrote: Hi, this doesn't look very useful. Do you have some specificity with this host except carp? Some modifications to kernel config, lagg, jails, etc. No, none of those. Its a supermicro motherboard, runs FreeBSD GENERIC and mysql+redis on top,

Re: More CARP issues under 12

2019-02-06 Thread Andrey V. Elsukov
On 05.02.2019 18:06, Pete French wrote: > The branch and revision is 12.0-STABLE r343538 GENERIC > >> # kgdb >> >> (kgdb) list *ether_output+0x6b6 > > trying to do this on the actual box is hard, as it panics, but on another > machine running the same build I get this, which should suffice if