1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
3 "http://www.FreeBSD.org/XML/share/xml/freebsd50.dtd" [
4 <!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"
5 "http://www.FreeBSD.org/release/XML/release.ent">
7 <!ENTITY security SYSTEM "../../share/xml/security.xml">
8 <!ENTITY errata SYSTEM "../../share/xml/errata.xml">
11 <article xmlns="http://docbook.org/ns/docbook"
12 xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
15 <title>&os; &release.prev; Errata </title>
17 <author><orgname>The &os; Project</orgname></author>
19 <pubdate>$FreeBSD$</pubdate>
24 <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
28 <legalnotice xml:id="trademarks" role="trademarks">
36 <para>This document lists errata items for &os; &release.prev;,
37 containing significant information discovered after the
38 release or too late in the release cycle to be otherwise
39 included in the release documentation. This information
40 includes security advisories, as well as news relating to the
41 software or documentation that could affect its operation or
42 usability. An up-to-date version of this document should
43 always be consulted before installing this version of
46 <para>This errata document for &os; &release.prev; will be
47 maintained until the release of &os; &release.next;.</para>
51 <sect1 xml:id="intro">
52 <title>Introduction</title>
54 <para>This errata document contains <quote>late-breaking
55 news</quote> about &os; &release.prev; Before installing this
56 version, it is important to consult this document to learn about
57 any post-release discoveries or problems that may already have
58 been found and fixed.</para>
60 <para>Any version of this errata document actually distributed
61 with the release (for example, on a CDROM distribution) will be
62 out of date by definition, but other copies are kept updated on
63 the Internet and should be consulted as the <quote>current
64 errata</quote> for this release. These other copies of the
65 errata are located at <link
66 xlink:href="https://www.FreeBSD.org/releases/" />, plus any
67 sites which keep up-to-date mirrors of this location.</para>
69 <para>Source and binary snapshots of &os; &release.branch; also
70 contain up-to-date copies of this document (as of the time of
73 <para>For a list of all &os; CERT security advisories, see <link
74 xlink:href="https://www.FreeBSD.org/security/"/>.</para>
77 <sect1 xml:id="security">
78 <title>Security Advisories</title>
83 <sect1 xml:id="errata">
84 <title>Errata Notices</title>
89 <sect1 xml:id="open-issues">
90 <title>Open Issues</title>
94 <para>&os;/&arch.i386; &release.prev; running as a guest
95 operating system on <application>VirtualBox</application>
96 can have a problem with disk I/O access. It depends on some
97 specific hardware configuration and does not depend on a
98 specific version of <application>VirtualBox</application> or
99 host operating system.</para>
101 <para>It has been reported that instability may be present on
102 virtual machines running on other hypervisors, such as Xen
105 <para>It causes various errors and makes &os; quite unstable.
106 Although the cause is still unclear, disabling unmapped I/O
107 works as a workaround. To disable it, choose
108 <literal>Escape to loader prompt</literal> in the boot menu
109 and enter the following lines from &man.loader.8; prompt,
110 after an <literal>OK</literal>:</para>
112 <screen>set vfs.unmapped_buf_allowed=0
115 <para>Note that the following line has to be added to
116 <filename>/boot/loader.conf</filename> after a boot. It
117 disables unmapped I/O at every boot:</para>
119 <programlisting>vfs.unmapped_buf_allowed=0</programlisting>
123 <para>&os;/&arch.i386; &release.prev; installed on ZFS
124 may crash during boot when the ZFS pool mount is attempted
125 while booting an unmodified <literal>GENERIC</literal>
128 <para>As described in <filename>/usr/src/UPDATING</filename>
129 entry <literal>20121223</literal>, rebuilding the kernel
130 with <literal>options KSTACK_PAGES=4</literal> has been
131 observed to resolve the boot-time crash. This, however, is
132 not an ideal solution for inclusion in the
133 <literal>GENERIC</literal> kernel configuration, as
134 increasing <literal>KSTACK_PAGES</literal> implicitly
135 decreases available usermode threads in an environment that
136 is already resource-starved.</para>
138 <para>Taking into account the heavy resource requirements of
139 ZFS, in addition to the &arch.i386;-specific tuning
140 requirements for general workloads, using ZFS with the
141 &os;/&arch.i386; <literal>GENERIC</literal> kernel
142 is strongly discouraged.</para>
144 <para>If installing &os;/&arch.i386; on ZFS, it is possible to
145 configure the system after installation to increase the
146 <literal>KSTACK_PAGES</literal>.</para>
148 <para>When prompted by &man.bsdinstall.8; to perform
149 additional post-installation configuration to the system,
150 select <guibutton>[ YES ]</guibutton>.</para>
152 <para>This procedure requires the system sources available
153 locally. If the <literal>System source code</literal>
154 distribution was not selected during installation, it can
155 be obtained using <application>svnlite</application>:</para>
157 <screen>&prompt.root; mkdir -p /usr/src
158 &prompt.root; svnlite co svn://svn.freebsd.org/base/releng/10.2 /usr/src</screen>
160 <para>Build the <literal>kernel-toolchain</literal> required
161 to rebuild the kernel:</para>
163 <screen>&prompt.root; make -C /usr/src kernel-toolchain</screen>
165 <para>Next, create a kernel configuration file to increase the
166 <literal>KSTACK_PAGES</literal> option:</para>
168 <screen>&prompt.root; printf "include GENERIC\noptions KSTACK_PAGES=4\n" > <filename>/usr/src/sys/i386/conf/<replaceable>ZFS</replaceable></filename></screen>
170 <para>Then build and install the
171 <replaceable>ZFS</replaceable> kernel:</para>
173 <screen>&prompt.root; make -C /usr/src buildkernel KERNCONF=<replaceable>ZFS</replaceable>
174 &prompt.root; make -C /usr/src installkernel KERNCONF=<replaceable>ZFS</replaceable></screen>
177 <para>It is extremely important to take note that, by
178 default, &man.freebsd-update.8; will install the
179 <literal>GENERIC</literal> kernel configuration, and
180 as such, &man.freebsd-update.8; consumers are strongly
181 encouraged to avoid &os;-provided kernel binary upgrades
182 with such configurations.</para>
187 <para>Due to an incompatibility between &man.bsdconfig.8;
188 and &man.pkg.8;, packages included on the &os; dvd
189 installer will not be recognized by
190 &man.bsdconfig.8;.</para>
192 <para>To install packages from the <literal>dvd1.iso</literal>
193 installer, create the <filename
194 class="directory">/dist</filename> target directory, and
195 manually mount the <literal>dvd1.iso</literal>
196 <acronym>ISO</acronym>:</para>
198 <screen>&prompt.root; mkdir -p /dist
199 &prompt.root; mount -t cd9660 /dev/<replaceable>cd0</replaceable> /dist</screen>
202 <para>Be sure to use the correct <filename
203 class="directory">/dev</filename> device path for the
204 <literal>dvd1.iso</literal> <acronym>ISO</acronym>
208 <para>Next, set <envar>REPOS_DIR</envar> to the path of the
209 <filename class="directory">repos/</filename> directory
210 within the installer so &man.pkg.8; will use the correct
211 repository metadata.</para>
213 <para>If using &man.sh.1;:</para>
215 <screen>&prompt.root; export REPOS_DIR=/dist/packages/repos</screen>
217 <para>If using &man.csh.1;:</para>
219 <screen>&prompt.root; setenv REPOS_DIR /dist/packages/repos</screen>
222 <para>Keep in mind that <envar>REPOS_DIR</envar> will need
223 to be set again after the current shell session is
224 terminated, if continuing to use the packages provided on
225 the <literal>dvd1.iso</literal> installer.</para>
228 <para>Finally, bootstrap &man.pkg.8; from the
229 <acronym>ISO</acronym>, and install required
232 <screen>&prompt.root; pkg bootstrap
233 &prompt.root; pkg install <replaceable>xorg-server</replaceable> <replaceable>xorg</replaceable> <replaceable>gnome3</replaceable> [...]</screen>
237 <para>An issue was discovered where the &man.netstat.1;
238 <literal>-s</literal> option will cause a segmentation fault
239 on systems with <literal>IPSEC</literal> compiled into the
240 kernel. The issue was resolved in the
241 <literal>stable/10</literal> branch, and an Errata Notice is
242 planned after &release.prev; is released.</para>
244 <para>[2015-08-19] Resolved as FreeBSD-EN-15:12.</para>
248 <para>An issue was discovered that causes &man.make.1; to
249 generate noisy output when doing source-based upgrades from
250 &os; 9.3 and earlier. The issue was reported in PR 202277,
251 and after investigation and determining the issue does not
252 cause source-based upgrades to fail, a post-release Errata
253 Notice is planned.</para>
255 <para>[2015-08-19] Resolved as FreeBSD-EN-15:11.</para>
259 <para>An issue with &os; virtual machines with
260 <application>vagrant</application> was discovered that
261 affects the <application>VirtualBox</application> where the
262 virtual machine will not start on the initial boot invoked
263 with <literal>vagrant up</literal>.</para>
265 <para>The issue is due to the virtual machine
266 <acronym>MAC</acronym> being unset, as &os; does not provide
267 a default <filename>Vagrantfile</filename>.</para>
269 <para>It has been observed, however, that a subsequent
270 invocation of <literal>vagrant up</literal> will allow the
271 virtual machine to successfully boot, allowing access via
272 <literal>vagrant ssh</literal>.</para>
276 <para>[2015-08-16] An error was discovered in the release
277 notes for &os; &release.prev; regarding the
278 <literal>drm</literal> device driver. The entry for r282199
279 states the driver was updated to match the version &linux;
280 3.8.13 version, however the entry should have noted the
281 change affects device-independent code, and does not bring
282 the <literal>drm</literal> driver fully in line with the
283 stated &linux; version.</para>
288 <sect1 xml:id="late-news">
289 <title>Late-Breaking News</title>
291 <para>No news.</para>