article.xml revision 324242
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"> 6%release; 7<!ENTITY security PUBLIC "-//FreeBSD//ENTITIES Security Advisory List//EN" 8 "http://www.FreeBSD.org/release/XML/share/xml/security.xml"> 9<!ENTITY errata PUBLIC "-//FreeBSD//ENTITIES Errata List//EN" 10 "http://www.FreeBSD.org/release/XML/share/xml/errata.xml"> 11]> 12 13<article xmlns="http://docbook.org/ns/docbook" 14 xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"> 15 16 <info> 17 <title>&os; &release.prev; Errata</title> 18 19 <author><orgname>The &os; Project</orgname></author> 20 21 <pubdate>$FreeBSD: stable/10/release/doc/en_US.ISO8859-1/errata/article.xml 324242 2017-10-03 19:08:16Z gjb $</pubdate> 22 23 <copyright> 24 <year>2017</year> 25 26 <holder role="mailto:doc@FreeBSD.org">The &os; Documentation 27 Project</holder> 28 </copyright> 29 30 <legalnotice xml:id="trademarks" role="trademarks"> 31 &tm-attrib.freebsd; 32 &tm-attrib.intel; 33 &tm-attrib.sparc; 34 &tm-attrib.general; 35 </legalnotice> 36 37 <abstract> 38 <para>This document lists errata items for &os; &release.prev;, 39 containing significant information discovered after the 40 release or too late in the release cycle to be otherwise 41 included in the release documentation. This information 42 includes security advisories, as well as news relating to the 43 software or documentation that could affect its operation or 44 usability. An up-to-date version of this document should 45 always be consulted before installing this version of 46 &os;.</para> 47 48 <para>This errata document for &os; &release.prev; will be 49 maintained until &os; &release.prev; reaches 50 end-of-life.</para> 51 </abstract> 52 </info> 53 54 <sect1 xml:id="intro"> 55 <title>Introduction</title> 56 57 <para>This errata document contains <quote>late-breaking 58 news</quote> about &os; &release.prev; Before installing this 59 version, it is important to consult this document to learn about 60 any post-release discoveries or problems that may already have 61 been found and fixed.</para> 62 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 68 errata are located at <link 69 xlink:href="https://www.FreeBSD.org/releases/" />, plus any 70 sites which keep up-to-date mirrors of this location.</para> 71 72 <para>Source and binary snapshots of &os; &release.branch; also 73 contain up-to-date copies of this document (as of the time of 74 the snapshot).</para> 75 76 <para>For a list of all &os; CERT security advisories, see <link 77 xlink:href="https://www.FreeBSD.org/security/"/>.</para> 78 </sect1> 79 80 <sect1 xml:id="security"> 81 <title>Security Advisories</title> 82 83 &security; 84 </sect1> 85 86 <sect1 xml:id="errata"> 87 <title>Errata Notices</title> 88 89 &errata; 90 </sect1> 91 92 <sect1 xml:id="open-issues"> 93 <title>Open Issues</title> 94 95 <itemizedlist> 96 <listitem> 97 <para>&os;/&arch.i386; &release.prev; running as a guest 98 operating system on <application>VirtualBox</application> 99 can have a problem with disk I/O access. It depends on some 100 specific hardware configuration and does not depend on a 101 specific version of <application>VirtualBox</application> or 102 host operating system.</para> 103 104 <para>It has been reported that instability may be present on 105 virtual machines running on other hypervisors, such as Xen 106 or KVM.</para> 107 108 <para>It causes various errors and makes &os; quite unstable. 109 Although the cause is still unclear, disabling unmapped I/O 110 works as a workaround. To disable it, choose 111 <literal>Escape to loader prompt</literal> in the boot menu 112 and enter the following lines from &man.loader.8; prompt, 113 after an <literal>OK</literal>:</para> 114 115 <screen>set vfs.unmapped_buf_allowed=0 116boot</screen> 117 118 <para>Note that the following line has to be added to 119 <filename>/boot/loader.conf</filename> after a boot. It 120 disables unmapped I/O at every boot:</para> 121 122 <programlisting>vfs.unmapped_buf_allowed=0</programlisting> 123 </listitem> 124 125 <listitem> 126 <para>&os;/&arch.i386; &release.prev; installed on ZFS 127 may crash during boot when the ZFS pool mount is attempted 128 while booting an unmodified <literal>GENERIC</literal> 129 kernel.</para> 130 131 <para>As described in <filename>/usr/src/UPDATING</filename> 132 entry <literal>20121223</literal>, rebuilding the kernel 133 with <literal>options KSTACK_PAGES=4</literal> has been 134 observed to resolve the boot-time crash. This, however, is 135 not an ideal solution for inclusion in the 136 <literal>GENERIC</literal> kernel configuration, as 137 increasing <literal>KSTACK_PAGES</literal> implicitly 138 decreases available usermode threads in an environment that 139 is already resource-starved.</para> 140 141 <para>Taking into account the heavy resource requirements of 142 ZFS, in addition to the &arch.i386;-specific tuning 143 requirements for general workloads, using ZFS with the 144 &os;/&arch.i386; <literal>GENERIC</literal> kernel 145 is strongly discouraged.</para> 146 147 <para>If installing &os;/&arch.i386; on ZFS, it is possible to 148 configure the system after installation to increase the 149 <literal>KSTACK_PAGES</literal>.</para> 150 151 <para>When prompted by &man.bsdinstall.8; to perform 152 additional post-installation configuration to the system, 153 select <guibutton>[ YES ]</guibutton>.</para> 154 155 <para>This procedure requires the system sources available 156 locally. If the <literal>System source code</literal> 157 distribution was not selected during installation, it can 158 be obtained using <application>svnlite</application>:</para> 159 160 <screen>&prompt.root; mkdir -p /usr/src 161&prompt.root; svnlite co https://svn.freebsd.org/base/releng/10.4 /usr/src</screen> 162 163 <para>Build the <literal>kernel-toolchain</literal> required 164 to rebuild the kernel:</para> 165 166 <screen>&prompt.root; make -C /usr/src kernel-toolchain</screen> 167 168 <para>Next, create a kernel configuration file to increase the 169 <literal>KSTACK_PAGES</literal> option:</para> 170 171 <screen>&prompt.root; printf "include GENERIC\noptions KSTACK_PAGES=4\n" > <filename>/usr/src/sys/i386/conf/<replaceable>ZFS</replaceable></filename></screen> 172 173 <para>Then build and install the 174 <replaceable>ZFS</replaceable> kernel:</para> 175 176 <screen>&prompt.root; make -C /usr/src buildkernel KERNCONF=<replaceable>ZFS</replaceable> 177&prompt.root; make -C /usr/src installkernel KERNCONF=<replaceable>ZFS</replaceable></screen> 178 179 <warning> 180 <para>It is extremely important to take note that, by 181 default, &man.freebsd-update.8; will install the 182 <literal>GENERIC</literal> kernel configuration, and 183 as such, &man.freebsd-update.8; consumers are strongly 184 encouraged to avoid &os;-provided kernel binary upgrades 185 with such configurations.</para> 186 </warning> 187 </listitem> 188 189 <listitem> 190 <para>Due to an incompatibility between &man.bsdconfig.8; 191 and &man.pkg.8;, packages included on the &os; dvd 192 installer will not be recognized by 193 &man.bsdconfig.8;.</para> 194 195 <para>To install packages from the <literal>dvd1.iso</literal> 196 installer, create the <filename 197 class="directory">/dist</filename> target directory, and 198 manually mount the <literal>dvd1.iso</literal> 199 <acronym>ISO</acronym>:</para> 200 201 <screen>&prompt.root; mkdir -p /dist 202&prompt.root; mount -t cd9660 /dev/<replaceable>cd0</replaceable> /dist</screen> 203 204 <note> 205 <para>Be sure to use the correct <filename 206 class="directory">/dev</filename> device path for the 207 <literal>dvd1.iso</literal> <acronym>ISO</acronym> 208 installer.</para> 209 </note> 210 211 <para>Next, set <envar>REPOS_DIR</envar> to the path of the 212 <filename class="directory">repos/</filename> directory 213 within the installer so &man.pkg.8; will use the correct 214 repository metadata.</para> 215 216 <para>If using &man.sh.1;:</para> 217 218 <screen>&prompt.root; export REPOS_DIR=/dist/packages/repos</screen> 219 220 <para>If using &man.csh.1;:</para> 221 222 <screen>&prompt.root; setenv REPOS_DIR /dist/packages/repos</screen> 223 224 <note> 225 <para>Keep in mind that <envar>REPOS_DIR</envar> will need 226 to be set again after the current shell session is 227 terminated, if continuing to use the packages provided on 228 the <literal>dvd1.iso</literal> installer.</para> 229 </note> 230 231 <para>Finally, bootstrap &man.pkg.8; from the 232 <acronym>ISO</acronym>, and install required 233 packages:</para> 234 235 <screen>&prompt.root; pkg bootstrap 236&prompt.root; pkg install <replaceable>xorg-server</replaceable> <replaceable>xorg</replaceable> <replaceable>gnome3</replaceable> [...]</screen> 237 </listitem> 238 239 <listitem> 240 <para>An issue with &os; virtual machines with 241 <application>vagrant</application> was discovered that 242 affects the <application>VirtualBox</application> where the 243 virtual machine will not start on the initial boot invoked 244 with <literal>vagrant up</literal>.</para> 245 246 <para>The issue is due to the virtual machine 247 <acronym>MAC</acronym> being unset, as &os; does not provide 248 a default <filename>Vagrantfile</filename>.</para> 249 250 <para>It has been observed, however, that a subsequent 251 invocation of <literal>vagrant up</literal> will allow the 252 virtual machine to successfully boot, allowing access via 253 <literal>vagrant ssh</literal>.</para> 254 </listitem> 255 </itemizedlist> 256 </sect1> 257 258 <sect1 xml:id="late-news"> 259 <title>Late-Breaking News</title> 260 261 <para>No news.</para> 262 </sect1> 263</article> 264