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