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