Microsoft Teams with Linuxulator

[Graham Perrin]

From :



I have Teams 1.3.00.25560 at /compat/ubuntu/usr/bin/teams

When run, it seems to get no further than this (from htop):

…
PID USER  PRI  NI  VIRT   RES S CPU% MEM%   TIME+  Command
    0 root  -16   0 0  6416 S  5.4  0.0  1h08:14 kernel
    1 root   52   0 11928   124 S  0.0  0.0  0:00.09 └─ init
99908 grahamper  20   0 2193M  115M S  0.0  0.7  0:04.46    ├─ teams
99924 grahamper  20   0  911M 93160 S  0.0  0.6  0:00.29    │  ├─ Watchdog
99909 grahamper  52   0  356M 41936 S  0.0  0.3  0:00.08    │  └─ teams 
--type=zygote --no-sandbox

…

– and later:

…
99908 grahamper  20   0 2193M  115M S  0.0  0.7  0:04.68    ├─ teams
99924 grahamper  20   0  911M 93160 S  0.0  0.6  0:00.29    │  ├─ 
Chrome_ChildIOT
99909 grahamper  52   0  356M 41936 S  0.0  0.3  0:00.08    │  └─ teams 
--type=zygote --no-sandbox

…

– no GUI.

Any suggestions?

TIA
___
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"

Re: Laptop exhibits erratic responsiveness

[Konstantin Belousov]

On Mon, Nov 30, 2020 at 01:22:45PM -0800, David Wolfskill wrote:
> On Mon, Nov 30, 2020 at 11:03:29PM +0200, Konstantin Belousov wrote:
> > ...
> > > I suppose I will be commenting out that DIAGNOSTIC option now :-}
> > 
> > Try to just set debug.vmem_check to 0 and see if it helps.
> > ...
> 
> OK; I rebooted the new(er) laptop with the previous kernel (that was
> built with "option DIAGNOSTIC") and reproduced the issue:
> 
> --- albert.catwhisker.org ping statistics ---
> 37 packets transmitted, 37 packets received, 0.0% packet loss
> round-trip min/avg/max/stddev = 0.451/13.832/178.867/41.904 ms
> 
> Then:
> 
> g1-216(13.0-C)[2] sudo sysctl debug.vmem_check
> Password:
> debug.vmem_check: 1
> g1-216(13.0-C)[3] sudo sysctl debug.vmem_check=0
> debug.vmem_check: 1 -> 0
> 
> On recheck:
> 
> --- albert.catwhisker.org ping statistics ---
> 60 packets transmitted, 60 packets received, 0.0% packet loss
> round-trip min/avg/max/stddev = 0.411/0.551/1.051/0.084 ms
> 
> which looks pretty good to me.

I wanted to change the default some time ago.  Do not remember why it did
not happen.
___
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"

Re: Laptop exhibits erratic responsiveness

[David Wolfskill]

On Mon, Nov 30, 2020 at 11:03:29PM +0200, Konstantin Belousov wrote:
> ...
> > I suppose I will be commenting out that DIAGNOSTIC option now :-}
> 
> Try to just set debug.vmem_check to 0 and see if it helps.
> ...

OK; I rebooted the new(er) laptop with the previous kernel (that was
built with "option DIAGNOSTIC") and reproduced the issue:

--- albert.catwhisker.org ping statistics ---
37 packets transmitted, 37 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.451/13.832/178.867/41.904 ms

Then:

g1-216(13.0-C)[2] sudo sysctl debug.vmem_check
Password:
debug.vmem_check: 1
g1-216(13.0-C)[3] sudo sysctl debug.vmem_check=0
debug.vmem_check: 1 -> 0

On recheck:

--- albert.catwhisker.org ping statistics ---
60 packets transmitted, 60 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.411/0.551/1.051/0.084 ms

which looks pretty good to me.

Thank you, Konstantin! :-)

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
There's no point in asking Trump "Sir, have you no decency?" -- it is
already well established that neither he nor his enablers have any.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: Laptop exhibits erratic responsiveness

[Konstantin Belousov]

On Mon, Nov 30, 2020 at 12:48:47PM -0800, David Wolfskill wrote:
> On Mon, Nov 30, 2020 at 05:21:28AM -0800, David Wolfskill wrote:
> > ...
> > FWIW, the copy of the laptop's "head" kernel config in
> > http://www.catwhisker.org/~david/FreeBSD/head/CANARY is current.
> > 
> > And the only difference between the stable/12 config and the head config
> > is:
> > 
> > g1-48(12.2-S)[3] diff -u FreeBSD-1{2,3}/CANARY
> > --- FreeBSD-12/CANARY   2019-07-08 10:43:51.940026000 -0700
> > +++ FreeBSD-13/CANARY   2015-03-22 10:03:41.0 -0700
> > @@ -342,7 +342,7 @@
> >  # from some parts of the kernel.  As this makes everything more noisy,
> >  # it is disabled by default.
> >  #
> > -# options  DIAGNOSTIC
> > +optionsDIAGNOSTIC
> >  
> >  #
> >  # REGRESSION causes optional kernel interfaces necessary only for 
> > regression
> > 
> > Hmmm... so I suppose that re-disbling DIAGNOSTIC might be a reasonable
> > thing to try, as well, yeah...?  :-}
> > 
> 
> Well, success(ish):
> 
> * I was able to reproduce the observed effect using the newer laptop,
> running a kernel from 14 Nov (thus, r367674):
> 
> * I was able to reproduce the observed effect using the newer laptop,
>   running a kernel from 14 Nov (thus, r367674).  (I had cloned the old
>   laptop's disk drive and slapped it inito the newer laptop.)
> 
> * I then updated the kernel config file ("CANARY") to comment out the
>   DIAGNOSTIC option, then rebuilt/installed the kernel.
> 
> * Upon reboot, "ping albert" showed remarkably consistent RTTs (compared
>   to before) -- e.g., the initial example I posted showed:
> 
>   --- albert.catwhisker.org ping statistics ---
>   67 packets transmitted, 67 packets received, 0.0% packet loss
>   round-trip min/avg/max/stddev =3D 0.428/1024.248/68482.244/8303.513 ms
> 
>   On the newer laptop after the above change, I saw:
> 
>   --- albert.catwhisker.org ping statistics ---
>   30 packets transmitted, 30 packets received, 0.0% packet loss
>   round-trip min/avg/max/stddev = 0.463/0.574/0.671/0.054 ms
> 
> Please especially note the maxima & standard deviations.
> 
> 
> FWIW, I do have (in /boot/loader.conf):
> 
> # Try to reduce WITNESS overhead
> vm.debug.divisor=4
> 
> (which I also utilize at work).
> 
> I suppose I will be commenting out that DIAGNOSTIC option now :-}

Try to just set debug.vmem_check to 0 and see if it helps.
___
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"

Re: Laptop exhibits erratic responsiveness

[David Wolfskill]

On Mon, Nov 30, 2020 at 05:21:28AM -0800, David Wolfskill wrote:
> ...
> FWIW, the copy of the laptop's "head" kernel config in
> http://www.catwhisker.org/~david/FreeBSD/head/CANARY is current.
> 
> And the only difference between the stable/12 config and the head config
> is:
> 
> g1-48(12.2-S)[3] diff -u FreeBSD-1{2,3}/CANARY
> --- FreeBSD-12/CANARY   2019-07-08 10:43:51.940026000 -0700
> +++ FreeBSD-13/CANARY   2015-03-22 10:03:41.0 -0700
> @@ -342,7 +342,7 @@
>  # from some parts of the kernel.  As this makes everything more noisy,
>  # it is disabled by default.
>  #
> -# options  DIAGNOSTIC
> +optionsDIAGNOSTIC
>  
>  #
>  # REGRESSION causes optional kernel interfaces necessary only for regression
> 
> Hmmm... so I suppose that re-disbling DIAGNOSTIC might be a reasonable
> thing to try, as well, yeah...?  :-}
> 

Well, success(ish):

* I was able to reproduce the observed effect using the newer laptop,
running a kernel from 14 Nov (thus, r367674):

* I was able to reproduce the observed effect using the newer laptop,
  running a kernel from 14 Nov (thus, r367674).  (I had cloned the old
  laptop's disk drive and slapped it inito the newer laptop.)

* I then updated the kernel config file ("CANARY") to comment out the
  DIAGNOSTIC option, then rebuilt/installed the kernel.

* Upon reboot, "ping albert" showed remarkably consistent RTTs (compared
  to before) -- e.g., the initial example I posted showed:

  --- albert.catwhisker.org ping statistics ---
  67 packets transmitted, 67 packets received, 0.0% packet loss
  round-trip min/avg/max/stddev =3D 0.428/1024.248/68482.244/8303.513 ms

  On the newer laptop after the above change, I saw:

  --- albert.catwhisker.org ping statistics ---
  30 packets transmitted, 30 packets received, 0.0% packet loss
  round-trip min/avg/max/stddev = 0.463/0.574/0.671/0.054 ms

Please especially note the maxima & standard deviations.


FWIW, I do have (in /boot/loader.conf):

# Try to reduce WITNESS overhead
vm.debug.divisor=4

(which I also utilize at work).

I suppose I will be commenting out that DIAGNOSTIC option now :-}

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
There's no point in asking Trump "Sir, have you no decency?" -- it is
already well established that neither he nor his enablers have any.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: buildworld fails ( stopped in /usr/src/lib/libsysdecode )

[Johan Hendriks]

On 30/11/2020 16:03, Michal Meloun wrote:



On 30.11.2020 13:11, Johan Hendriks wrote:


On 30/11/2020 12:29, Hans Petter Selasky wrote:

On 11/30/20 11:43 AM, Johan Hendriks wrote:
My server running FreeBSD 13.0-CURRENT #7 r368110 fails to build to 
r368182
I did a make cleanworld && make cleanworld to make sure i use a 
fresh build but it errors out with the following message.


This is a known issue and will be fixed.

--HPS


Thank you for the conformation.
And thank you all for your work on FreeBSD.

regards
Johan



Fixed in r368187. Sorry for troubles.
Michal



Thank you, no problem and no need for a sorry!

___
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"

Re: buildworld fails ( stopped in /usr/src/lib/libsysdecode )

[Michal Meloun]

On 30.11.2020 13:11, Johan Hendriks wrote:


On 30/11/2020 12:29, Hans Petter Selasky wrote:

On 11/30/20 11:43 AM, Johan Hendriks wrote:
My server running FreeBSD 13.0-CURRENT #7 r368110 fails to build to 
r368182
I did a make cleanworld && make cleanworld to make sure i use a fresh 
build but it errors out with the following message.


This is a known issue and will be fixed.

--HPS


Thank you for the conformation.
And thank you all for your work on FreeBSD.

regards
Johan



Fixed in r368187. Sorry for troubles.
Michal

___
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"

Re: dtrace: give %'d a chance?

[Andriy Gapon]

On 19/11/2020 16:57, Mark Johnston wrote:
> On Thu, Nov 19, 2020 at 01:28:56PM +0200, Andriy Gapon wrote:
>>
>> what do people think about adding
>> setlocale(LC_NUMERIC, "");
>> to dtrace's main function?
> 
> That seems reasonable to me.
> 
>> My primary interest is to (pretty-)print some numbers with a thousands 
>> separator.
>>
>> Not sure if any other LC_ types are worth bothering.
> 
> Maybe LC_TIME?  libdtrace a couple of date formatters, %T and %Y.  A
> locale-aware formatter might be worth having.

FWIW, I've just discovered that despite what
http://dtrace.org/guide/chp-fmt.html says about %Y its output is not dependent
on locale settings.
A quick look at the code confirms that -- pfprint_time uses ctime_r.
But %T (undocumented at the above link) indeed depends on LC_TIME as
pfprint_time822 uses strftime("%a, %d %b %G %T %Z").

Sample output in C locale:
1000
Mon, 30 Nov 2020 13:47:24 UTC
2020 Nov 30 13:47:24

The same formats (%'d, %T, %Y) in uk_UA locale:
10 000 000
Пн, 30 лист. 2020 13:43:11 UTC
2020 Nov 30 13:43:11

-- 
Andriy Gapon
___
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"

Re: Laptop exhibits erratic responsiveness

[David Wolfskill]

On Mon, Nov 30, 2020 at 02:10:51PM +0100, Mateusz Guzik wrote:
> ...
> > I definitely do NOT see anything like this running stable/12 (presently
> > at r368181).
> >
> > I will try some experiments with another laptop (a newer one, for which
> > the built-in mouse is detected weirdly, making it annoying to use for me
> > -- but I can still ping from it).
> >
> 
> As a sanity check, does the issue manifest itself if you build a
> GENERIC-NODEBUG kernel?
> 
> -- 
> Mateusz Guzik 
> 

I will try that, but I'm not sure how soon -- I use this laptop whenever
I'm interacting with computers (which is most of the time that I'm
awake).  I will see what happens with the newer laptop later today.


FWIW, the copy of the laptop's "head" kernel config in
http://www.catwhisker.org/~david/FreeBSD/head/CANARY is current.

And the only difference between the stable/12 config and the head config
is:

g1-48(12.2-S)[3] diff -u FreeBSD-1{2,3}/CANARY
--- FreeBSD-12/CANARY   2019-07-08 10:43:51.940026000 -0700
+++ FreeBSD-13/CANARY   2015-03-22 10:03:41.0 -0700
@@ -342,7 +342,7 @@
 # from some parts of the kernel.  As this makes everything more noisy,
 # it is disabled by default.
 #
-# options  DIAGNOSTIC
+optionsDIAGNOSTIC
 
 #
 # REGRESSION causes optional kernel interfaces necessary only for regression

Hmmm... so I suppose that re-disbling DIAGNOSTIC might be a reasonable
thing to try, as well, yeah...?  :-}

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
There's no point in asking Trump "Sir, have you no decency?" -- it is
already well established that neither he nor his enablers have any.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: Laptop exhibits erratic responsiveness

[Mateusz Guzik]

On 11/30/20, David Wolfskill  wrote:
> On Sun, Nov 29, 2020 at 03:20:15PM +0100, Mateusz Guzik wrote:
>> On 11/29/20, David Wolfskill  wrote:
>> > On Sat, Nov 28, 2020 at 10:47:57AM -0500, Jonathan Looney wrote:
>> >> FWIW, I would try running lockstat on the box. (My supposition is that
>> >> the
>> >> delay is due to a lock. That could be incorrect.  Lockstat may provide
>> >> some
>> >> clue as to whether this is a line of inquiry worth pursuing.)
>> >> 
>> >
>> > Thanks (again), Jonathan.
>> >
>> > So... I did that (during this morning's daily upgrade cycle); the
>> > results may be "of interest" to some.
>> ...
>> > http://www.catwhisker.org/~david/FreeBSD/head/lockstat/README
>> ...
>>
>> According to the data you got the entire kernel "freezes" every 11-12
>> seconds. So something way off is going on there.
>>
>> Given that the bug seems to be reproducible I think it would be best
>> if you just bisected to the offending commit.
>>
>> --
>> Mateusz Guzik 
>
> I had thought that the issue arose  (as noted in my initial message)
> around 09 Nov, which was the day that my daily update on head went from
> r367484 to r367517.
>
> So for my inital attempt at a "before the breakage" kernel (& world), I
> "updated" sources to r367444, as I had updated to that revision on 07
> Nov.
>
> Testing (again, via "ping albert") still showed most RTTs around 0.600
> ms, but (around) every 11th packet, I would see an RTT in the 400 - 650
> ms range -- around a factor of 1000(ish).  So while I was not seeing
> RTTs in excess of 68 seconds (as I did at least one time for the initial
> message), I believe(d) that the underlying issue still existed at
> r367444.
>
> Lather, rinse, repeat -- for:
>
> * r367484 (from 08 Nov)
> * r367243 (from 01 Nov)
> * r366312 (from 01 Oct)
> * r363759 (from 01 Aug)
>
> At this point, I was questioning many assumptions, so I cleared /usr/obj
> completely and then updated back to r368143... and the issue remained.
>
> (The laptop was quite busy yesterday.)
>
> I definitely do NOT see anything like this running stable/12 (presently
> at r368181).
>
> I will try some experiments with another laptop (a newer one, for which
> the built-in mouse is detected weirdly, making it annoying to use for me
> -- but I can still ping from it).
>

As a sanity check, does the issue manifest itself if you build a
GENERIC-NODEBUG kernel?

-- 
Mateusz Guzik 
___
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"

Re: Laptop exhibits erratic responsiveness

[David Wolfskill]

On Sun, Nov 29, 2020 at 03:20:15PM +0100, Mateusz Guzik wrote:
> On 11/29/20, David Wolfskill  wrote:
> > On Sat, Nov 28, 2020 at 10:47:57AM -0500, Jonathan Looney wrote:
> >> FWIW, I would try running lockstat on the box. (My supposition is that
> >> the
> >> delay is due to a lock. That could be incorrect.  Lockstat may provide
> >> some
> >> clue as to whether this is a line of inquiry worth pursuing.)
> >> 
> >
> > Thanks (again), Jonathan.
> >
> > So... I did that (during this morning's daily upgrade cycle); the
> > results may be "of interest" to some.
> ...
> > http://www.catwhisker.org/~david/FreeBSD/head/lockstat/README
> ...
> 
> According to the data you got the entire kernel "freezes" every 11-12
> seconds. So something way off is going on there.
> 
> Given that the bug seems to be reproducible I think it would be best
> if you just bisected to the offending commit.
> 
> -- 
> Mateusz Guzik 

I had thought that the issue arose  (as noted in my initial message)
around 09 Nov, which was the day that my daily update on head went from
r367484 to r367517.

So for my inital attempt at a "before the breakage" kernel (& world), I
"updated" sources to r367444, as I had updated to that revision on 07
Nov.

Testing (again, via "ping albert") still showed most RTTs around 0.600
ms, but (around) every 11th packet, I would see an RTT in the 400 - 650
ms range -- around a factor of 1000(ish).  So while I was not seeing
RTTs in excess of 68 seconds (as I did at least one time for the initial
message), I believe(d) that the underlying issue still existed at
r367444.

Lather, rinse, repeat -- for:

* r367484 (from 08 Nov)
* r367243 (from 01 Nov)
* r366312 (from 01 Oct)
* r363759 (from 01 Aug)

At this point, I was questioning many assumptions, so I cleared /usr/obj
completely and then updated back to r368143... and the issue remained.

(The laptop was quite busy yesterday.)

I definitely do NOT see anything like this running stable/12 (presently
at r368181).

I will try some experiments with another laptop (a newer one, for which
the built-in mouse is detected weirdly, making it annoying to use for me
-- but I can still ping from it).

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
"Make America Great Again," he said -- and THIS is what he did??!?

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: buildworld fails ( stopped in /usr/src/lib/libsysdecode )

[Johan Hendriks]

On 30/11/2020 12:29, Hans Petter Selasky wrote:

On 11/30/20 11:43 AM, Johan Hendriks wrote:
My server running FreeBSD 13.0-CURRENT #7 r368110 fails to build to 
r368182
I did a make cleanworld && make cleanworld to make sure i use a fresh 
build but it errors out with the following message.


This is a known issue and will be fixed.

--HPS


Thank you for the conformation.
And thank you all for your work on FreeBSD.

regards
Johan

___
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"

Re: buildworld fails ( stopped in /usr/src/lib/libsysdecode )

[Hans Petter Selasky]

On 11/30/20 11:43 AM, Johan Hendriks wrote:

My server running FreeBSD 13.0-CURRENT #7 r368110 fails to build to r368182
I did a make cleanworld && make cleanworld to make sure i use a fresh 
build but it errors out with the following message.


This is a known issue and will be fixed.

--HPS

___
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"

Re: zpool export: umount failed, device inexplicably busy

[Ryan Moeller]

On 10/6/20 4:29 PM, Graham Perrin wrote:

lsof finds no open file.



Please be wary of lsof. I'm not sure it works on OpenZFS. The port 
reaches into /usr/src for zfs headers in locations that don't exist 
anymore to access kernel memory in /dev/kmem using structs that are 
different in OpenZFS. It is likely not building the ZFS support code on 
13-current, and it is not expected to work on 12 with openzfs from 
ports, either.


-Ryan




How else might I tell why the device is busy?

Mobile hard disk drive, USB.

--

root@momh167-gjp4-8570p:~ # zpool export Transcend
cannot unmount '/Volumes/t500': umount failed
root@momh167-gjp4-8570p:~ # lsof /Volumes/t500
root@momh167-gjp4-8570p:~ # zpool export Transcend
cannot unmount '/Volumes/t500': umount failed
root@momh167-gjp4-8570p:~ # zpool export Transcend
cannot unmount '/Volumes/t500': umount failed
root@momh167-gjp4-8570p:~ # umount /Volumes/t500/
umount: unmount of /Volumes/t500 failed: Device busy
root@momh167-gjp4-8570p:~ # lsof /Volumes/t500
root@momh167-gjp4-8570p:~ # zfs version
zfs-0.8.0-1
zfs-kmod-0.8.0-1
root@momh167-gjp4-8570p:~ # zpool iostat Transcend 3
  capacity operations bandwidth
pool    alloc   free   read  write   read  write
--  -  -  -  -  -  -
Transcend    126G   338G  0  0  3.29K  1.45K
Transcend    126G   338G  0  0  0  0
Transcend    126G   338G  0  0  0  0
Transcend    126G   338G  0  0  0  0
Transcend    126G   338G  0  0  0  0
Transcend    126G   338G  0  0  0  0
^C
root@momh167-gjp4-8570p:~ # umount /Volumes/t500/
umount: unmount of /Volumes/t500 failed: Device busy
root@momh167-gjp4-8570p:~ # ls -ahl /Volumes/t500
total 10
drwxr-xr-x  3 root  wheel    3B Sep  2 19:02 .
drwxr-xr-x  4 root  wheel    4B Sep  5 09:15 ..
drwxr-xr-x  6 grahamperrin  grahamperrin 6B Sep 11 17:54 VirtualBox
root@momh167-gjp4-8570p:~ # zpool status Transcend
  pool: Transcend
 state: ONLINE
  scan: scrub repaired 0B in 00:28:07 with 0 errors on Tue Oct  6 
00:03:13 2020

config:

    NAME    STATE READ WRITE CKSUM
    Transcend   ONLINE   0 0 0
  da0p1 ONLINE   0 0 0

errors: No known data errors
root@momh167-gjp4-8570p:~ # umount /Volumes/t500/
umount: unmount of /Volumes/t500 failed: Device busy
root@momh167-gjp4-8570p:~ # lsof /Volumes/t500
root@momh167-gjp4-8570p:~ # date ; uname -v
Tue Oct  6 21:20:17 BST 2020
FreeBSD 13.0-CURRENT #67 r366424: Sun Oct  4 19:54:32 BST 2020 
root@momh167-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG

root@momh167-gjp4-8570p:~ # ls /dev/da*
/dev/da0    /dev/da0p1
root@momh167-gjp4-8570p:~ # zfs get all Transcend Transcend/VirtualBox
NAME  PROPERTY VALUE SOURCE
Transcend type filesystem    -
Transcend creation  Wed Sep  2 18:31 2020 -
Transcend used 126G  -
Transcend available 324G  -
Transcend referenced 126G  -
Transcend compressratio 1.66x -
Transcend mounted yes   -
Transcend quota none  default
Transcend reservation none default
Transcend recordsize 128K  default
Transcend mountpoint /Volumes/t500 local
Transcend sharenfs off   default
Transcend checksum on    default
Transcend compression zstd  local
Transcend atime on    default
Transcend devices on    default
Transcend exec on    default
Transcend setuid on    default
Transcend readonly off   default
Transcend jailed off   default
Transcend snapdir hidden    default
Transcend aclmode discard   default
Transcend aclinherit restricted    default
Transcend createtxg 1 -
Transcend canmount on    default
Transcend xattr on    default
Transcend copies 1 default
Transcend version 5 -
Transcend utf8only off   -
Transcend normalization none  -
Transcend casesensitivity sensitive -
Transcend vscan off   default
Transcend nbmand off   default
Transcend sharesmb off  

buildworld fails ( stopped in /usr/src/lib/libsysdecode )

[Johan Hendriks]

My server running FreeBSD 13.0-CURRENT #7 r368110 fails to build to r368182
I did a make cleanworld && make cleanworld to make sure i use a fresh 
build but it errors out with the following message.


Building /usr/obj/usr/src/amd64.amd64/lib/libsysdecode/ioctl.o
cc -target x86_64-unknown-freebsd13.0 
--sysroot=/usr/obj/usr/src/amd64.amd64/tmp 
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin  -O2 -pipe -fno-common   
-I/usr/obj/usr/src/amd64.amd64/lib/libsysdecode -I/usr/src/sys 
-I/usr/src/libexec/rtld-elf -DPF -g -std=gnu99 -Wno-format-zero-length 
-fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k 
-W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes 
-Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch 
-Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline 
-Wnested-externs -Wredundant-decls -Wold-style-definition 
-Wno-pointer-sign -Wmissing-variable-declarations -Wthread-safety 
-Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable 
-Qunused-arguments    -c ioctl.c -o ioctl.o

In file included from ioctl.c:33:
In file included from /usr/src/sys/./cam/scsi/scsi_pass.h:35:
In file included from /usr/src/sys/cam/cam_ccb.h:46:
In file included from /usr/src/sys/cam/nvme/nvme_all.h:33:
/usr/src/sys/dev/nvme/nvme.h:1733:56: error: unused parameter 's' 
[-Werror,-Wunused-parameter]

void    nvme_completion_swapbytes(struct nvme_completion *s)
  ^
/usr/src/sys/dev/nvme/nvme.h:1747:58: error: unused parameter 's' 
[-Werror,-Wunused-parameter]

void    nvme_power_state_swapbytes(struct nvme_power_state *s)
    ^
/usr/src/sys/dev/nvme/nvme.h:1760:66: error: unused parameter 's' 
[-Werror,-Wunused-parameter]

void    nvme_controller_data_swapbytes(struct nvme_controller_data *s)
    ^
/usr/src/sys/dev/nvme/nvme.h:1812:64: error: unused parameter 's' 
[-Werror,-Wunused-parameter]

void    nvme_namespace_data_swapbytes(struct nvme_namespace_data *s)
^
/usr/src/sys/dev/nvme/nvme.h:1841:82: error: unused parameter 's' 
[-Werror,-Wunused-parameter]
void    nvme_error_information_entry_swapbytes(struct 
nvme_error_information_entry *s)

^
/usr/src/sys/dev/nvme/nvme.h:1858:26: error: unused parameter 'p' 
[-Werror,-Wunused-parameter]

void    nvme_le128toh(void *p)
    ^
/usr/src/sys/dev/nvme/nvme.h:1874:82: error: unused parameter 's' 
[-Werror,-Wunused-parameter]
void    nvme_health_information_page_swapbytes(struct 
nvme_health_information_page *s)

^
/usr/src/sys/dev/nvme/nvme.h:1902:62: error: unused parameter 's' 
[-Werror,-Wunused-parameter]

void    nvme_firmware_page_swapbytes(struct nvme_firmware_page *s)
    ^
/usr/src/sys/dev/nvme/nvme.h:1913:50: error: unused parameter 's' 
[-Werror,-Wunused-parameter]

void    nvme_ns_list_swapbytes(struct nvme_ns_list *s)
    ^
/usr/src/sys/dev/nvme/nvme.h:1924:76: error: unused parameter 's' 
[-Werror,-Wunused-parameter]
void    nvme_command_effects_page_swapbytes(struct 
nvme_command_effects_page *s)

^
/usr/src/sys/dev/nvme/nvme.h:1937:78: error: unused parameter 's' 
[-Werror,-Wunused-parameter]
void    nvme_res_notification_page_swapbytes(struct 
nvme_res_notification_page *s)

^
/usr/src/sys/dev/nvme/nvme.h:1946:76: error: unused parameter 's' 
[-Werror,-Wunused-parameter]
void    nvme_sanitize_status_page_swapbytes(struct 
nvme_sanitize_status_page *s)

^
/usr/src/sys/dev/nvme/nvme.h:1962:66: error: unused parameter 's' 
[-Werror,-Wunused-parameter]

void    intel_log_temp_stats_swapbytes(struct intel_log_temp_stats *s)
    ^
/usr/src/sys/dev/nvme/nvme.h:1979:58: error: unused parameter 's' 
[-Werror,-Wunused-parameter]

void    nvme_resv_status_swapbytes(struct nvme_resv_status *s, size_t size)
    ^
/usr/src/sys/dev/nvme/nvme.h:1979:68: error: unused parameter 'size' 
[-Werror,-Wunused-parameter]

void    nvme_resv_status_swapbytes(struct nvme_resv_status *s, size_t size)
  ^
/usr/src/sys/dev/nvme/nvme.h:1996:66: error: unused parameter 's' 
[-Werror,-Wunused-parameter]
void    nvme_resv_status_ext_swapbytes(struct nvme_resv_status_ext *s, 
size_t size)

    ^
/usr/src/sys/dev/nvme/nvme.h:1996:76: error: unused parameter 'size' 
[-Werror,-Wunused-parameter]
void    nvme_resv_status_ext_swapbytes(struct nvme_resv_status_ext *s, 
size_t size)

^
17 errors generated.
*** Error code 1

Stop.
bmake[5]: stopped in /usr/src/lib/libsysdecode
.ERROR_TARGET='ioctl.o'
.ERROR_META_FILE='/usr/obj/usr/src/amd64.amd64/lib/libsysdecode/ioctl.o.meta'