Index: stable/10/release/doc/en_US.ISO8859-1/errata/article.xml
===================================================================
--- stable/10/release/doc/en_US.ISO8859-1/errata/article.xml (revision 333376)
+++ stable/10/release/doc/en_US.ISO8859-1/errata/article.xml (revision 333377)
@@ -1,263 +1,263 @@
%release;
]>
&os; &release.prev; ErrataThe &os; Project$FreeBSD$
- 2017
+ 2018The &os; Documentation
Project
&tm-attrib.freebsd;
&tm-attrib.intel;
&tm-attrib.sparc;
&tm-attrib.general;
This document lists errata items for &os; &release.prev;,
containing significant information discovered after the
release or too late in the release cycle to be otherwise
included in the release documentation. This information
includes security advisories, as well as news relating to the
software or documentation that could affect its operation or
usability. An up-to-date version of this document should
always be consulted before installing this version of
&os;.This errata document for &os; &release.prev; will be
maintained until &os; &release.prev; reaches
end-of-life.IntroductionThis errata document contains late-breaking
news about &os; &release.prev; Before installing this
version, it is important to consult this document to learn about
any post-release discoveries or problems that may already have
been found and fixed.Any version of this errata document actually distributed
with the release (for example, on a CDROM distribution) will be
out of date by definition, but other copies are kept updated on
the Internet and should be consulted as the current
errata for this release. These other copies of the
errata are located at , plus any
sites which keep up-to-date mirrors of this location.Source and binary snapshots of &os; &release.branch; also
contain up-to-date copies of this document (as of the time of
the snapshot).For a list of all &os; CERT security advisories, see .Security Advisories
&security;
Errata Notices
&errata;
Open Issues&os;/&arch.i386; &release.prev; running as a guest
operating system on VirtualBox
can have a problem with disk I/O access. It depends on some
specific hardware configuration and does not depend on a
specific version of VirtualBox or
host operating system.It has been reported that instability may be present on
virtual machines running on other hypervisors, such as Xen
or KVM.It causes various errors and makes &os; quite unstable.
Although the cause is still unclear, disabling unmapped I/O
works as a workaround. To disable it, choose
Escape to loader prompt in the boot menu
and enter the following lines from &man.loader.8; prompt,
after an OK:set vfs.unmapped_buf_allowed=0
bootNote that the following line has to be added to
/boot/loader.conf after a boot. It
disables unmapped I/O at every boot:vfs.unmapped_buf_allowed=0&os;/&arch.i386; &release.prev; installed on ZFS
may crash during boot when the ZFS pool mount is attempted
while booting an unmodified GENERIC
kernel.As described in /usr/src/UPDATING
entry 20121223, rebuilding the kernel
with options KSTACK_PAGES=4 has been
observed to resolve the boot-time crash. This, however, is
not an ideal solution for inclusion in the
GENERIC kernel configuration, as
increasing KSTACK_PAGES implicitly
decreases available usermode threads in an environment that
is already resource-starved.Taking into account the heavy resource requirements of
ZFS, in addition to the &arch.i386;-specific tuning
requirements for general workloads, using ZFS with the
&os;/&arch.i386; GENERIC kernel
is strongly discouraged.If installing &os;/&arch.i386; on ZFS, it is possible to
configure the system after installation to increase the
KSTACK_PAGES.When prompted by &man.bsdinstall.8; to perform
additional post-installation configuration to the system,
select [ YES ].This procedure requires the system sources available
locally. If the System source code
distribution was not selected during installation, it can
be obtained using svnlite:&prompt.root; mkdir -p /usr/src
&prompt.root; svnlite co https://svn.freebsd.org/base/releng/10.4 /usr/srcBuild the kernel-toolchain required
to rebuild the kernel:&prompt.root; make -C /usr/src kernel-toolchainNext, create a kernel configuration file to increase the
KSTACK_PAGES option:&prompt.root; printf "include GENERIC\noptions KSTACK_PAGES=4\n" > /usr/src/sys/i386/conf/ZFSThen build and install the
ZFS kernel:&prompt.root; make -C /usr/src buildkernel KERNCONF=ZFS
&prompt.root; make -C /usr/src installkernel KERNCONF=ZFSIt is extremely important to take note that, by
default, &man.freebsd-update.8; will install the
GENERIC kernel configuration, and
as such, &man.freebsd-update.8; consumers are strongly
encouraged to avoid &os;-provided kernel binary upgrades
with such configurations.Due to an incompatibility between &man.bsdconfig.8;
and &man.pkg.8;, packages included on the &os; dvd
installer will not be recognized by
&man.bsdconfig.8;.To install packages from the dvd1.iso
installer, create the /dist target directory, and
manually mount the dvd1.iso
ISO:&prompt.root; mkdir -p /dist
&prompt.root; mount -t cd9660 /dev/cd0 /distBe sure to use the correct /dev device path for the
dvd1.iso ISO
installer.Next, set REPOS_DIR to the path of the
repos/ directory
within the installer so &man.pkg.8; will use the correct
repository metadata.If using &man.sh.1;:&prompt.root; export REPOS_DIR=/dist/packages/reposIf using &man.csh.1;:&prompt.root; setenv REPOS_DIR /dist/packages/reposKeep in mind that REPOS_DIR will need
to be set again after the current shell session is
terminated, if continuing to use the packages provided on
the dvd1.iso installer.Finally, bootstrap &man.pkg.8; from the
ISO, and install required
packages:&prompt.root; pkg bootstrap
&prompt.root; pkg install xorg-serverxorggnome3 [...]An issue with &os; virtual machines with
vagrant was discovered that
affects the VirtualBox where the
virtual machine will not start on the initial boot invoked
with vagrant up.The issue is due to the virtual machine
MAC being unset, as &os; does not provide
a default Vagrantfile.It has been observed, however, that a subsequent
invocation of vagrant up will allow the
virtual machine to successfully boot, allowing access via
vagrant ssh.Late-Breaking NewsNo news.
Index: stable/11/release/doc/en_US.ISO8859-1/errata/article.xml
===================================================================
--- stable/11/release/doc/en_US.ISO8859-1/errata/article.xml (revision 333376)
+++ stable/11/release/doc/en_US.ISO8859-1/errata/article.xml (revision 333377)
@@ -1,224 +1,224 @@
%release;
%sponsor;
%vendor;
]>
&os; &release; ErrataThe &os; Project$FreeBSD$
- 2017
+ 2018The &os; Documentation
Project
&tm-attrib.freebsd;
&tm-attrib.intel;
&tm-attrib.sparc;
&tm-attrib.general;
This document lists errata items for &os; &release;,
containing significant information discovered after the
release or too late in the release cycle to be otherwise
included in the release documentation. This information
includes security advisories, as well as news relating to the
software or documentation that could affect its operation or
usability. An up-to-date version of this document should
always be consulted before installing this version of
&os;.This errata document for &os; &release; will be maintained
until the release of &os; &release.next;.IntroductionThis errata document contains late-breaking
news about &os; &release; Before installing this
version, it is important to consult this document to learn about
any post-release discoveries or problems that may already have
been found and fixed.Any version of this errata document actually distributed
with the release (for example, on a CDROM distribution) will be
out of date by definition, but other copies are kept updated on
the Internet and should be consulted as the current
errata for this release. These other copies of the
errata are located at , plus any
sites which keep up-to-date mirrors of this location.Source and binary snapshots of &os; &release.branch; also
contain up-to-date copies of this document (as of the time of
the snapshot).For a list of all &os; CERT security advisories, see .Security Advisories
&security;
Errata Notices
&errata;
Open Issues&os;/&arch.i386; installed on ZFS may crash during boot
when the ZFS pool mount is attempted while booting an
unmodified GENERIC kernel.A system tunable has been added as of revision
r286584 to make the
kern.kstack_pages tunable configurable
without recompiling the kernel.To mitigate system crashes with such configurations,
choose Escape to loader prompt in the
boot menu and enter the following lines from &man.loader.8;
prompt, after an OK:set kern.kstack_pages=4
bootAdd this line to
/boot/loader.conf for the change to
persist across reboots:kern.kstack_pages=4[2017-07-21] Due to a bug in earlier versions of
&man.clang.1; that is difficult to work around in the
upgrade process, to upgrade the system from sources via
buildworld to -CURRENT or &release;, it is necessary to
upgrade machines running 9.x to at least revision r286035,
or machines running 10.x to revision r286033. Source-based
upgrades from 10.3-RELEASE are not affected. This differs
from the historical situation where one could generally
upgrade from anywhere on earlier stable branches, so caution
should be exercised.[2017-07-25] &os;/&arch.arm64; currently lacks
EFI real-time clock
(RTC) support, which may cause the system
to boot with the wrong time set.As a workaround, either enable &man.ntpdate.8; or
include ntpd_sync_on_start="YES" in
&man.rc.conf.5;.[2017-07-25] A late issue was discovered with
&os;/&arch.arm64; and "root on
ZFS" installations where the root
ZFS pool would fail to be located.There currently is no workaround.[2017-07-26] Note for those upgrading from 11.1-RC2 in
VirtualBox:If system panics were experienced when upgrading from
11.1-RC1 to 11.1-RC2, and the emulators/virtualbox-ose-additions{,-nox11}
port was built locally as a resolution, the port will either
need to be rebuilt when upgrading from 11.1-RC2 to
11.1-RELEASE, or reinstall the package from the pkg(8)
mirrors using either: &prompt.root; pkg install -f virtualbox-ose-additionsor &prompt.root; pkg install -f virtualbox-ose-additions-nox11To ensure the system does not panic after rebooting into
the updated kernel, it is recommended to disable the
vboxguest service in &man.rc.conf.5;
prior to rebooting the system if possible, or use
&man.pkg.8; to forcefully reinstall the package.Systems being upgraded from 11.1-RC1 and earlier and
11.1-RC3 to 11.1-RELEASE should be unaffected.[2017-07-27] The release notes erroneously state
revision r315330 was sponsored by Rubicon
Communications, LLC (Netgate), when in fact this work was
done by Hiroki Mori independently.[2017-08-09] The release notes stated the
&man.ruptime.1;, &man.rwho.1;, and &man.rwhod.8; utilities
have been marked "deprecated", however this change
was reversed in 12.0-CURRENT.The other utilities mentioned in the entry in the
release notes, however, are unchanged.[2017-11-06] An issue with &os; virtual machines with
vagrant was discovered that
affects the VirtualBox where the
virtual machine will not start on the initial boot invoked
with vagrant up.The issue is due to the virtual machine
MAC being unset, as &os; does not provide
a default Vagrantfile.It has been observed, however, that a subsequent
invocation of vagrant up will allow the
virtual machine to successfully boot, allowing access via
vagrant ssh.Late-Breaking NewsNo news.