release/doc/en_US.ISO8859-1/errata/article.xml

   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/share/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   xml:id="top">
  16
  17   <info>
  18     <title>&os; &release.prev; Errata</title>
  19
  20     <author><orgname>The &os; Project</orgname></author>
  21
  22     <pubdate>$FreeBSD$</pubdate>
  23
  24     <copyright>
  25       <year>2016</year>
  26
  27       <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
  28         Project</holder>
  29     </copyright>
  30
  31     <legalnotice xml:id="trademarks" role="trademarks">
  32       &tm-attrib.freebsd;
  33       &tm-attrib.intel;
  34       &tm-attrib.sparc;
  35       &tm-attrib.general;
  36     </legalnotice>
  37
  38     <abstract>
  39       <para>This document lists errata items for &os; &release.prev;,
  40         containing significant information discovered after the
  41         release or too late in the release cycle to be otherwise
  42         included in the release documentation.  This information
  43         includes security advisories, as well as news relating to the
  44         software or documentation that could affect its operation or
  45         usability.  An up-to-date version of this document should
  46         always be consulted before installing this version of
  47         &os;.</para>
  48
  49       <para>This errata document for &os; &release.prev; will be
  50         maintained until the release of &os; &release.next;.</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
 116 boot</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;&nbsp;&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;&nbsp;<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>[&nbsp;YES&nbsp;]</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 svn://svn.freebsd.org/base/releng/10.2 /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" &gt; <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;&nbsp;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 was discovered where the &man.netstat.1;
 241           <literal>-s</literal> option will cause a segmentation fault
 242           on systems with <literal>IPSEC</literal> compiled into the
 243           kernel.  The issue was resolved in the
 244           <literal>stable/10</literal> branch, and an Errata Notice is
 245           planned after &release.prev; is released.</para>
 246
 247         <para>[2015-08-19] Resolved as FreeBSD-EN-15:12.</para>
 248       </listitem>
 249
 250       <listitem>
 251         <para>An issue was discovered that causes &man.make.1; to
 252           generate noisy output when doing source-based upgrades from
 253           &os; 9.3 and earlier.  The issue was reported in PR 202277,
 254           and after investigation and determining the issue does not
 255           cause source-based upgrades to fail, a post-release Errata
 256           Notice is planned.</para>
 257
 258         <para>[2015-08-19] Resolved as FreeBSD-EN-15:11.</para>
 259       </listitem>
 260
 261       <listitem>
 262         <para>An issue with &os; virtual machines with
 263           <application>vagrant</application> was discovered that
 264           affects the <application>VirtualBox</application> where the
 265           virtual machine will not start on the initial boot invoked
 266           with <literal>vagrant up</literal>.</para>
 267
 268         <para>The issue is due to the virtual machine
 269           <acronym>MAC</acronym> being unset, as &os; does not provide
 270           a default <filename>Vagrantfile</filename>.</para>
 271
 272         <para>It has been observed, however, that a subsequent
 273           invocation of <literal>vagrant up</literal> will allow the
 274           virtual machine to successfully boot, allowing access via
 275           <literal>vagrant ssh</literal>.</para>
 276       </listitem>
 277
 278       <listitem>
 279         <para>[2015-08-16] An error was discovered in the release
 280           notes for &os; &release.prev; regarding the
 281           <literal>drm</literal> device driver.  The entry for r282199
 282           states the driver was updated to match the version &linux;
 283           3.8.13 version, however the entry should have noted the
 284           change affects device-independent code, and does not bring
 285           the <literal>drm</literal> driver fully in line with the
 286           stated &linux; version.</para>
 287       </listitem>
 288     </itemizedlist>
 289   </sect1>
 290
 291   <sect1 xml:id="late-news">
 292     <title>Late-Breaking News</title>
 293
 294     <para>No news.</para>
 295   </sect1>
 296 </article>