top -m io Segmentation fault(core dumped) on fresh r335360

top -m io Segmentation fault(core dumped) FreeBSD alex.super 12.0-CURRENT FreeBSD 12.0-CURRENT #11 r335360: Tue Jun 19 14:53:20 +07 2018 alex@alex.super:/usr/obj/usr/src/amd64.amd64/sys/IOSCHED amd64 -- - Alex. ___ freebsd-current@freebsd.org mailin

Re: Ryzen public erratas

On Mon, 18 Jun 2018 22:44:13 -0700 Eitan Adler wrote: > On 13 June 2018 at 04:16, Eitan Adler wrote: > > On 13 June 2018 at 03:35, Konstantin Belousov wrote: > >> Today I noted that AMD published the public errata document for Ryzens, > >> https://developer.amd.com/wp-content/resources/55449_

Re: review of nfsd rc.d script patch

Don Lewis wrote: >On 15 Jun, Rick Macklem wrote: >> Hi, >> >> For the pNFS service MDS machine, the nfsd can't be started until all nfs >> mounts >> in /etc/fstab are done. >> I think that adding "mountcritremote" to the "# REQUIRE:" line is sufficient >> to do this? >> >> I don't think delaying

Re: ESXi NFSv4.1 client id is nasty

Steve Wills wrote: On 06/18/18 17:42, Rick Macklem wrote: >> Steve Wills wrote: >>> Would it be possible or reasonable to use the client ID to log a message >>> telling the admin to enable a sysctl to enable the hacks? >> Yes. However, this client implementation id is only seen by the server >> whe

Re: ESXi NFSv4.1 client id is nasty

On Tue, Jun 19, 2018 at 5:11 AM, Rick Macklem wrote: > Steve Wills wrote: > On 06/18/18 17:42, Rick Macklem wrote: > >> Steve Wills wrote: > >>> Would it be possible or reasonable to use the client ID to log a > message > >>> telling the admin to enable a sysctl to enable the hacks? > >> Yes. How

Re: A head buildworld race visible in the ci.freebsd.org build history

On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote: > Li-Wen reported that the build is done in a 11.1-rel jail though, so > the libarchive (or any userland) change shouldn't be responsible. > > Can we update a canary builder to somewhere between r328278 and r88? butler1.nyi.freebsd.org is runnin

Re: Current @ r335314 not bootable with Geli and ZFS

On 2018-06-18 12:42, Thomas Laus wrote: > Something changed in /boot/gptzfsboot between r334610 and r335314. I > built current this morning and my system is un-bootable. I am using > redundant ZFS disks and only copied the updated /boot/gptzfsboot file to > my ada0 drive. I was able to boot the

Re: Current @ r335314 not bootable with Geli and ZFS

On 06/19/18 12:09, Allan Jude wrote: > > We tested all of the changes with the setup in tools/boot/rootgen.sh, it > will be interesting to figure out what went wrong with your setup, and > add it as a test case to prevent this in the future. > > The recent changes are: > > r335245 (reading the s

Re: Current @ r335314 not bootable with Geli and ZFS

On 06/19/18 14:22, Thomas Laus wrote: > On 06/19/18 12:09, Allan Jude wrote: >> >> We tested all of the changes with the setup in tools/boot/rootgen.sh, it >> will be interesting to figure out what went wrong with your setup, and >> add it as a test case to prevent this in the future. >> >> The rec

Re: Current @ r335314 not bootable with Geli and ZFS

> On 19 Jun 2018, at 21:51, Thomas Laus wrote: > > On 06/19/18 14:22, Thomas Laus wrote: >> On 06/19/18 12:09, Allan Jude wrote: >>> >>> We tested all of the changes with the setup in tools/boot/rootgen.sh, it >>> will be interesting to figure out what went wrong with your setup, and >>> add i

Re: top -m io Segmentation fault(core dumped) on fresh r335360

On 19 June 2018 at 02:28, Alex V. Petrov wrote: > top -m io > Segmentation fault(core dumped) > FreeBSD alex.super 12.0-CURRENT FreeBSD 12.0-CURRENT #11 r335360: Tue > Jun 19 14:53:20 +07 2018 > alex@alex.super:/usr/obj/usr/src/amd64.amd64/sys/IOSCHED amd64 r335390 should fix it. -- Eitan Ad

ci.freebsd.org's FreeBSD-head-amd64-gcc broken by -r335338 and/or -r335339 (-r335389 still broken)

>From https://ci.freebsd.org/job/FreeBSD-head-amd64-gcc/6190/consoleText and https://ci.freebsd.org/job/FreeBSD-head-amd64-gcc/6213/ as examples: --- ixl_pf_qmgr.o --- In file included from /workspace/src/sys/dev/ixl/ixl_pf_qmgr.h:36:0, from /workspace/src/sys/dev/ixl/ixl_pf_qmgr.

Re: A head buildworld race visible in the ci.freebsd.org build history

On 2018-Jun-19, at 8:02 AM, Li-Wen Hsu wrote: > On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote: >> Li-Wen reported that the build is done in a 11.1-rel jail though, so >> the libarchive (or any userland) change shouldn't be responsible. >> >> Can we update a canary builder to somewhere betwe

svn commit: r335399: . . . head/sys/security/mac_veriexec/ . . . breaks ci.freebsg.org builds of FreeBSD-head-{armv6,ar,m7,i386,mips,powerpc,powerpcspe}-build

Stephen J. Kiernan stevek at FreeBSD.org Wed Jun 20 00:41:33 UTC 2018 Author: stevek Date: Wed Jun 20 00:41:30 2018 New Revision: 335399 URL: https://svnweb.freebsd.org/changeset/base/335399 Log: MAC/veriexec implements a verified execution environment using the MAC framework. . . . Bu

Re: A head buildworld race visible in the ci.freebsd.org build history

On Tue, Jun 19, 2018 at 9:24 PM Mark Millard wrote: > > On 2018-Jun-19, at 8:02 AM, Li-Wen Hsu wrote: > > > On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote: > >> Li-Wen reported that the build is done in a 11.1-rel jail though, so > >> the libarchive (or any userland) change shouldn't be responsi

Re: A head buildworld race visible in the ci.freebsd.org build history

On 2018-Jun-19, at 9:14 PM, Li-Wen Hsu wrote: > On Tue, Jun 19, 2018 at 9:24 PM Mark Millard wrote: >> >> On 2018-Jun-19, at 8:02 AM, Li-Wen Hsu wrote: >> >>> On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote: Li-Wen reported that the build is done in a 11.1-rel jail though, so the