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 % sponsor PUBLIC "-//FreeBSD//ENTITIES Sponsor Specification//EN" "sponsor.ent">
9 <!ENTITY % vendor PUBLIC "-//FreeBSD//ENTITIES Vendor Specification//EN" "vendor.ent">
11 <!ENTITY security SYSTEM "../../share/xml/security.xml">
12 <!ENTITY errata SYSTEM "../../share/xml/errata.xml">
15 <article xmlns="http://docbook.org/ns/docbook"
16 xmlns:xlink="http://www.w3.org/1999/xlink"
19 <title>&os; &release; Errata </title>
21 <author><orgname>The &os; Project</orgname></author>
23 <pubdate>$FreeBSD$</pubdate>
28 <holder role="mailto:doc@FreeBSD.org">The &os; Documentation Project</holder>
31 <legalnotice xml:id="trademarks" role="trademarks">
39 <para>This document lists errata items for &os; &release;,
40 containing significant information discovered after the release
41 or too late in the release cycle to be otherwise included in the
42 release documentation.
43 This information includes security advisories, as well as news
44 relating to the software or documentation that could affect its
45 operation or usability. An up-to-date version of this document
46 should always be consulted before installing this version of
49 <para>This errata document for &os; &release;
50 will be maintained until the release of &os; &release.next;.</para>
54 <sect1 xml:id="intro">
55 <title>Introduction</title>
57 <para>This errata document contains <quote>late-breaking news</quote>
59 Before installing this version, it is important to consult this
60 document to learn about any post-release discoveries or problems
61 that may already have been found and fixed.</para>
63 <para>Any version of this errata document actually distributed
64 with the release (for example, on a CDROM distribution) will be
65 out of date by definition, but other copies are kept updated on
66 the Internet and should be consulted as the <quote>current
67 errata</quote> for this release. These other copies of the
69 <link xlink:href="https://www.FreeBSD.org/releases/" />,
71 which keep up-to-date mirrors of this location.</para>
73 <para>Source and binary snapshots of &os; &release.branch; also
74 contain up-to-date copies of this document (as of the time of
77 <para>For a list of all &os; CERT security advisories, see
78 <link xlink:href="https://www.FreeBSD.org/security/"/>.</para>
81 <sect1 xml:id="security">
82 <title>Security Advisories</title>
87 <sect1 xml:id="errata">
88 <title>Errata Notices</title>
93 <sect1 xml:id="open-issues">
94 <title>Open Issues</title>
98 <para>An issue was discovered with Amazon® EC2™
99 images which would cause the virtual machine to hang during
100 boot when upgrading from previous FreeBSD versions. New
101 EC2™ installations are not affected, but existing
102 installations running earlier releases are advised to wait
103 until the issue is resolved in an Errata Notice before
104 upgrading. An Errata Notice to address this is planned
105 following the release.</para>
109 <para>&os;/&arch.i386; installed on ZFS may crash during boot
110 when the ZFS pool mount is attempted while booting an
111 unmodified <literal>GENERIC</literal> kernel.</para>
113 <para>A system tunable has been added as of revision
114 <literal>r286584</literal> to make the
115 <literal>kern.kstack_pages</literal> tunable configurable
116 without recompiling the kernel.</para>
118 <para>To mitigate system crashes with such configurations,
119 chose <literal>Escape to loader prompt</literal> in the boot
120 menu and enter the following lines from &man.loader.8;
121 prompt, after an <literal>OK</literal>:</para>
123 <screen>set kern.kstack_pages=4
126 <para>Add this line to
127 <filename>/boot/loader.conf</filename> for the change to
128 persist across reboots:</para>
130 <programlisting>kern.kstack_pages=4</programlisting>
134 <para>A bug was diagnosed in interaction of the
135 <literal>pmap_activate()</literal> function and
136 <acronym>TLB</acronym> shootdown <acronym>IPI</acronym>
137 handler on amd64 systems which have <acronym>PCID</acronym>
138 features but do not implement the <acronym>INVPCID</acronym>
139 instruction. On such machines, such as SandyBridge™
140 and IvyBridge™ microarchitectures, set the loader
141 tunable <literal>vm.pmap.pcid_enabled=0</literal> during
144 <screen>set vm.pmap.pcid_enabled=0
147 <para>Add this line to
148 <filename>/boot/loader.conf</filename> for the change to
149 persist across reboots:</para>
151 <para>To check if the system is affected, check
152 &man.dmesg.8; for <acronym>PCID</acronym> listed in the
153 "Features2", and absence of
154 <acronym>INVPCID</acronym> in the "Structured Extended
155 Features". If the <acronym>PCID</acronym> feature is
156 not present, or <acronym>INVPCID</acronym> is present,
157 system is not affected.</para>
159 <programlisting>vm.pmap.pcid_enabled=0</programlisting>
163 <para>The Release Notes erroneously states the
164 <literal>WITH_SYSTEM_COMPILER</literal> &man.src.conf.5;
165 option is enabled by default, however this was disabled
166 prior to the final release build.</para>
170 <para>The release announcement stated "Wireless support
171 for 802.11n has been added." This was intended to
172 state "Wireless support for 802.11n has been added for
173 additional wireless network drivers."</para>
177 <para>Some release notes pertaining to the Cavium ThunderX
178 platform (the &os;/&arch.arm64; reference platform) were
183 <para revision="289550" contrib="sponsor"
184 sponsor="&cavium;">Support for the Cavium Virtualized
185 NIC ethernet driver has been added.</para>
189 <para revision="286919" contrib="sponsor"
190 sponsor="&cavium;">Support for the GICv3 and ITS device
191 drivers has been added.</para>
195 <para revision="296308" contrib="sponsor"
196 sponsor="&cavium;">Support for PCI Enhanced Allocation
197 support has been added.</para>
203 <para revision="293860">[2016-10-20] Several recent Dell
204 systems fail to find a bootable disk when the system boots
205 in Legacy/BIOS/CSM mode, the boot disk is partitioned with
206 <acronym>GPT</acronym>, and the Active flag in the
207 Protective <acronym>MBR</acronym> is not set. To work
208 around this issue, either configure the system to boot in
209 <acronym>UEFI</acronym> mode, or choose the "GPT
210 + Active" scheme.</para>
214 <para>[2016-10-21] Support for <literal>sha512</literal> and
215 <literal>skein</literal> checksumming has been added to the
216 <acronym>ZFS</acronym> filesystem. This was not mentioned
217 in the release notes.</para>
219 <para>Systems being upgraded from earlier &os; releases with
220 <acronym>ZFS</acronym> will see a message in <literal>zpool
221 status</literal> output noting the pool is not at the
222 latest version, and some features may not be enabled.
223 Additional instructions on how to update
224 <acronym>ZFS</acronym> pools to the latest version and
225 update the boot blocks for all boot drives in the pool will
226 also be provided in the output.</para>
228 <para>This information is also documented in
229 <filename>/usr/src/UPDATING</filename>, which is included if
230 the <literal>src</literal> component is selected during
235 <para>[2016-10-21] The size of the <acronym>GPT</acronym>
236 enabled <acronym>ZFS</acronym> boot blocks
237 (<filename>/boot/gptzfsboot</filename>) has increased past
238 64K. Systems upgraded from older releases may experience
239 a problem where the size of the existing
240 "freebsd-boot" partition is too small to hold the
241 new <filename>gptzfsboot</filename>.</para>
243 <para>Systems where the boot partition is immediately followed
244 by the swap partition, such as those installed via
245 &man.bsdinstall.8;, can resize the swap partition slightly
246 using the &man.gpart.8; <literal>resize</literal> command,
247 so space can be reclaimed to increase the size of the
248 freebsd-boot partition.</para>
252 <para>[2016-10-21] Due to a bug in earlier versions of
253 &man.clang.1; that is difficult to work around in the
254 upgrade process, to upgrade the system from sources via
255 buildworld to -CURRENT or &release;, it is necessary to
256 upgrade machines running 9.x to at least revision r286035,
257 or machines running 10.x to revision r286033. Source-based
258 upgrades from 10.3-RELEASE are not affected. This differs
259 from the historical situation where one could generally
260 upgrade from anywhere on earlier stable branches, so caution
261 should be exercised.</para>
266 <sect1 xml:id="late-news">
267 <title>Late-Breaking News</title>
269 <para>No news.</para>