Re: FreeBSD CI Weekly Report 2020-04-12

2020-04-15 Thread Kristof Provost
On 15 Apr 2020, at 0:37, Li-Wen Hsu wrote: (Please send the followup to freebsd-testing@ and note Reply-To is set.) FreeBSD CI Weekly Report 2020-04-12 === Here is a summary of the FreeBSD Continuous Integration results for the period from 2020-04-06 to 2020-0

Re: FreeBSD CI Weekly Report 2020-04-12

2020-04-15 Thread Kristof Provost
On 15 Apr 2020, at 15:34, Kristof Provost wrote: On 15 Apr 2020, at 0:37, Li-Wen Hsu wrote: (Please send the followup to freebsd-testing@ and note Reply-To is set.) FreeBSD CI Weekly Report 2020-04-12 === Here is a summary of the FreeBSD Continuous Integration

Re: FreeBSD CI Weekly Report 2020-04-12

2020-04-15 Thread Olivier Cochard-Labbé
On Wed, Apr 15, 2020 at 4:10 PM Kristof Provost wrote: > > The problem appears to be that > /usr/local/lib/python3.7/site-packages/scapy/arch/unix.py is misparsing > the `netstat -rnW` output. > Shouldn't scapy use the libxo output of netstat to mitigate this regression ? ___

Re: FreeBSD CI Weekly Report 2020-04-12

2020-04-15 Thread Kristof Provost
On 15 Apr 2020, at 16:49, Olivier Cochard-Labbé wrote: On Wed, Apr 15, 2020 at 4:10 PM Kristof Provost wrote: The problem appears to be that /usr/local/lib/python3.7/site-packages/scapy/arch/unix.py is misparsing the `netstat -rnW` output. Shouldn't scapy use the libxo output of netstat

panic: sleeping thread. Possibly related to drm and swapping.

2020-04-15 Thread Steve Kargl
Just recieved this panic. I am using drm-legacy-kmod-g20200306 on a Dell Latitude D530 laptop. The panic occurred as I was starting libreoffice. Suggestions? mobile dumped core - see /var/crash/vmcore.2 Wed Apr 15 09:22:07 PDT 2020 FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r359179M:

Re: FreeBSD CI Weekly Report 2020-04-12

2020-04-15 Thread Alexander V . Chernikov
15.04.2020, 15:10, "Kristof Provost" : > On 15 Apr 2020, at 15:34, Kristof Provost wrote: >>  On 15 Apr 2020, at 0:37, Li-Wen Hsu wrote: >>>  (Please send the followup to freebsd-testing@ and note Reply-To is >>>  set.) >>> >>>  FreeBSD CI Weekly Report 2020-04-12 >>>  ===

Re: FreeBSD CI Weekly Report 2020-04-12

2020-04-15 Thread Muhammad Moinur Rahman
Hi Alexandar, I have changed net/scapy to apply a simple patch as a workaround for the time being. ports@r531789 should do the trick for now. So no need to revert. Kind Regards, Moin > On 16 Apr, 2020, at 02:21, Alexander V. Chernikov wrote: > > > > 15.04.2020, 15:10, "Kristof Provost" : >

anyone else seeing bind fail on recent -current?

2020-04-15 Thread Michael Butler
This instance is/was running in a jail but now fails sometime after SVN r359823 .. I'm trying to bisect but any hints appreciated .. named[98746]: named[98746]: BIND 9 is maintained by Internet Systems Consortium, named[98746]: Inc. (ISC), a non

Re: anyone else seeing bind fail on recent -current?

2020-04-15 Thread Michael Butler
On 4/15/20 7:19 PM, Michael Butler wrote: > This instance is/was running in a jail but now fails sometime after SVN > r359823 .. I'm trying to bisect but any hints appreciated .. > > named[98746]: > named[98746]: BIND 9 is maintained by Internet

Re: anyone else seeing bind fail on recent -current?

2020-04-15 Thread Kubilay Kocak
On 16/04/2020 10:24 am, Michael Butler wrote: On 4/15/20 7:19 PM, Michael Butler wrote: This instance is/was running in a jail but now fails sometime after SVN r359823 .. I'm trying to bisect but any hints appreciated .. named[98746]: named[9

Re: CFT: if_bridge performance improvements

2020-04-15 Thread Pavel Timofeev
вт, 14 апр. 2020 г., 12:51 Kristof Provost : > Hi, > > Thanks to support from The FreeBSD Foundation I’ve been able to work > on improving the throughput of if_bridge. > It changes the (data path) locking to use the NET_EPOCH infrastructure. > Benchmarking shows substantial improvements (x5 in tes