Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 05:02:03PM -0800, Steve Kargl wrote: > On Sat, Dec 08, 2018 at 02:43:17AM +0200, Konstantin Belousov wrote: > > On Fri, Dec 07, 2018 at 04:25:39PM -0800, Steve Kargl wrote: > > > On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > > > > > > > > Most likel

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Konstantin Belousov
On Fri, Dec 07, 2018 at 05:02:03PM -0800, Steve Kargl wrote: > On Sat, Dec 08, 2018 at 02:43:17AM +0200, Konstantin Belousov wrote: > > On Fri, Dec 07, 2018 at 04:25:39PM -0800, Steve Kargl wrote: > > > On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > > > > > > > > Most likel

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Sat, Dec 08, 2018 at 02:43:17AM +0200, Konstantin Belousov wrote: > On Fri, Dec 07, 2018 at 04:25:39PM -0800, Steve Kargl wrote: > > On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > > > > > > Most likely this is an issue fixed by r339350. > > > > My tree is at r341703. T

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Konstantin Belousov
On Fri, Dec 07, 2018 at 04:25:39PM -0800, Steve Kargl wrote: > On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > > On Fri, Dec 07, 2018 at 03:52:33PM -0800, Steve Kargl wrote: > > > On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > > > > On Fri, Dec 07, 2018 at 03:

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > On Fri, Dec 07, 2018 at 03:52:33PM -0800, Steve Kargl wrote: > > On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > > > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > > > > > > > make core dumps. >

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Konstantin Belousov
On Fri, Dec 07, 2018 at 03:52:33PM -0800, Steve Kargl wrote: > On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > > > > > make core dumps. > > > devd core dumps. > > > init core dumps. > > > cc core dumps. > > > c++

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 03:52:33PM -0800, Steve Kargl wrote: > On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > > > > > make core dumps. > > > devd core dumps. > > > init core dumps. > > > cc core dumps. > > > c++

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > > > make core dumps. > > devd core dumps. > > init core dumps. > > cc core dumps. > > c++ core dumps. > > > > Something seems to be broken. > > > > Further invest

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 06:23:57PM -0500, Shawn Webb wrote: > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > Dell 7510 laptop was happily running FreeBSD12-alpha9 > > from Oct. 10th. I decided to update to top-of-tree > > today, which would be FreeBSD13 at r341703. > > analysis >

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > make core dumps. > devd core dumps. > init core dumps. > cc core dumps. > c++ core dumps. > > Something seems to be broken. > Further investigation, as core dumps. cpp core dumps. /rescue/vi core dumps. All of these programs

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Shawn Webb
On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > Dell 7510 laptop was happily running FreeBSD12-alpha9 > from Oct. 10th. I decided to update to top-of-tree > today, which would be FreeBSD13 at r341703. > > % cd /usr/obj > % rm -rf usr > % cd ../src > % svn update > % make -j6 buildw

HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
Dell 7510 laptop was happily running FreeBSD12-alpha9 from Oct. 10th. I decided to update to top-of-tree today, which would be FreeBSD13 at r341703. % cd /usr/obj % rm -rf usr % cd ../src % svn update % make -j6 buildwould (OK) % make -j6 buildkernel (OK) % make installkernel(OK) % mergema

Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2

2018-12-07 Thread Willem Jan Withagen
On 05/12/2018 00:48, Toomas Soome wrote: Yes, that must be true but it does not hurt to get checked. And of course, lsdev -v from 11.x loader would be good too. Anyhow, I am afraid we have reached to point where more specific debug info is needed (printed out), with lack of output about disks

Re: iflib.tx_abdicate: very strange behavior on incoming IPsec traffic (regression?)

2018-12-07 Thread Lev Serebryakov
On 07.12.2018 18:02, Lev Serebryakov wrote: >> (I'm not sure, that it is exactly "bug" or "defect" and want to > ... discuss it here before filing PR. > >> Now I'm throwing IPsec into mix. All incoming traffic is tunneled with >> IPsec policy, with aes-128-gcm encryption. And with IPsec tx_abd

Re: iflib.tx_abdicate: very strange behavior on incoming IPsec traffic (regression?)

2018-12-07 Thread Lev Serebryakov
On 07.12.2018 16:40, Lev Serebryakov wrote: > (I'm not sure, that it is exactly "bug" or "defect" and want to ... discuss it here before filing PR. > Now I'm throwing IPsec into mix. All incoming traffic is tunneled with > IPsec policy, with aes-128-gcm encryption. And with IPsec tx_abdicate >

iflib.tx_abdicate: very strange behavior on incoming IPsec traffic (regression?)

2018-12-07 Thread Lev Serebryakov
(I'm not sure, that it is exactly "bug" or "defect" and want to I've found very strange behavior of 13-CURRENT system I210 (igb) interfaces and enabled "dev.igb.X.iflib.tx_abdicate". I'm measuring "router" performance with BSDRP's "equilibrium" script (thank you, Oliver, for this great tool!)

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

2018-12-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 Andriy Gapon changed: What|Removed |Added Assignee|a...@freebsd.org|a...@freebsd.org Status

Re: rm cannot recursively delete directory on tmpfs on RPi2

2018-12-07 Thread Michal Meloun
On 07.12.2018 10:59, Mateusz Guzik wrote: > On 12/7/18, Michal Meloun wrote: >> >> >> On 07.12.2018 7:25, Mateusz Guzik wrote: >>> On 12/7/18, Jia-Shiun Li wrote: On Fri, Dec 7, 2018 at 12:36 AM Alan Somers wrote: > On Wed, Dec 5, 2018 at 10:18 PM Jia-Shiun Li > wrote:

Re: rm cannot recursively delete directory on tmpfs on RPi2

2018-12-07 Thread Michal Meloun
On 07.12.2018 10:59, Mateusz Guzik wrote: > On 12/7/18, Michal Meloun wrote: >> >> >> On 07.12.2018 7:25, Mateusz Guzik wrote: >>> On 12/7/18, Jia-Shiun Li wrote: On Fri, Dec 7, 2018 at 12:36 AM Alan Somers wrote: > On Wed, Dec 5, 2018 at 10:18 PM Jia-Shiun Li > wrote:

Re: rm cannot recursively delete directory on tmpfs on RPi2

2018-12-07 Thread Mateusz Guzik
On 12/7/18, Michal Meloun wrote: > > > On 07.12.2018 7:25, Mateusz Guzik wrote: >> On 12/7/18, Jia-Shiun Li wrote: >>> On Fri, Dec 7, 2018 at 12:36 AM Alan Somers wrote: >>> On Wed, Dec 5, 2018 at 10:18 PM Jia-Shiun Li wrote: > > amd64 and RPi3 do not have this issue. > >>

Re: rm cannot recursively delete directory on tmpfs on RPi2

2018-12-07 Thread Michal Meloun
On 07.12.2018 7:25, Mateusz Guzik wrote: > On 12/7/18, Jia-Shiun Li wrote: >> On Fri, Dec 7, 2018 at 12:36 AM Alan Somers wrote: >> >>> On Wed, Dec 5, 2018 at 10:18 PM Jia-Shiun Li wrote: amd64 and RPi3 do not have this issue. jsli@rpi2:/home/jsli 13:04 # uname -a Fre