path: root/release/doc/en_US.ISO8859-1/errata/article.xml

<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
  "http://www.FreeBSD.org/XML/share/xml/freebsd50.dtd" [
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"
  "http://www.FreeBSD.org/release/XML/release.ent">
%release;
<!ENTITY security SYSTEM "../../share/xml/security.xml">
<!ENTITY errata SYSTEM "../../share/xml/errata.xml">
]>

<article xmlns="http://docbook.org/ns/docbook"
  xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">

  <info>
    <title>&os; &release.prev; Errata </title>

    <author><orgname>The &os; Project</orgname></author>

    <pubdate>$FreeBSD$</pubdate>

    <copyright>
      <year>2015</year>

      <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
	Project</holder>
    </copyright>

    <legalnotice xml:id="trademarks" role="trademarks">
      &tm-attrib.freebsd;
      &tm-attrib.intel;
      &tm-attrib.sparc;
      &tm-attrib.general;
    </legalnotice>

    <abstract>
      <para>This document lists errata items for &os; &release.prev;,
	containing significant information discovered after the
	release or too late in the release cycle to be otherwise
	included in the release documentation.  This information
	includes security advisories, as well as news relating to the
	software or documentation that could affect its operation or
	usability.  An up-to-date version of this document should
	always be consulted before installing this version of
	&os;.</para>

      <para>This errata document for &os; &release.prev; will be
	maintained until the release of &os; &release.next;.</para>
    </abstract>
  </info>

  <sect1 xml:id="intro">
    <title>Introduction</title>

    <para>This errata document contains <quote>late-breaking
	news</quote> about &os; &release.prev; Before installing this
      version, it is important to consult this document to learn about
      any post-release discoveries or problems that may already have
      been found and fixed.</para>

    <para>Any version of this errata document actually distributed
      with the release (for example, on a CDROM distribution) will be
      out of date by definition, but other copies are kept updated on
      the Internet and should be consulted as the <quote>current
	errata</quote> for this release.  These other copies of the
      errata are located at <link
	xlink:href="http://www.FreeBSD.org/releases/" />, plus any
      sites which keep up-to-date mirrors of this location.</para>

    <para>Source and binary snapshots of &os; &release.branch; also
      contain up-to-date copies of this document (as of the time of
      the snapshot).</para>

    <para>For a list of all &os; CERT security advisories, see <link
	xlink:href="http://www.FreeBSD.org/security/"/> or <link
      xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/"/>.</para>
  </sect1>

  <sect1 xml:id="security">
    <title>Security Advisories</title>

    &security;
  </sect1>

  <sect1 xml:id="errata">
    <title>Errata Notices</title>

    &errata;
  </sect1>

  <sect1 xml:id="open-issues">
    <title>Open Issues</title>

    <itemizedlist>
      <listitem>
	<para>&os;/&arch.i386; &release.prev; running as a guest
	  operating system on <application>VirtualBox</application>
	  can have a problem with disk I/O access.  It depends on some
	  specific hardware configuration and does not depend on a
	  specific version of <application>VirtualBox</application> or
	  host operating system.</para>

	<para>It causes various errors and makes &os; quite unstable.
	  Although the cause is still unclear, disabling unmapped I/O
	  works as a workaround.  To disable it, choose
	  <literal>Escape to loader prompt</literal> in the boot menu
	  and enter the following lines from &man.loader.8; prompt,
	  after an <literal>OK</literal>:</para>

	<screen>set vfs.unmapped_buf_allowed=0
boot</screen>

	<para>Note that the following line has to be added to
	  <filename>/boot/loader.conf</filename> after a boot.  It
	  disables unmapped I/O at every boot:</para>

	<programlisting>vfs.unmapped_buf_allowed=0</programlisting>

	<para>[2014-04-03 update]  It has been reported that
	  instability may be present on virtual machines running
	  on other hypervisors, such as Xen or KVM.</para>
      </listitem>

      <listitem>
	<para>&os;/&arch.i386;&nbsp;10.1-RELEASE configured with
	  a multi-disk ZFS dataset (mirror, raidz1, raidz2, raidz3)
	  may crash during boot when the ZFS pool mount is attempted
	  while booting an unmodified <literal>GENERIC</literal>
	  kernel.</para>

	<para>As described in <filename>/usr/src/UPDATING</filename>
	  entry <literal>20121223</literal>, rebuilding the kernel
	  with <literal>options KSTACK_PAGES=4</literal> has been
	  observed to resolve the boot-time crash.  This, however, is
	  not an ideal solution for inclusion in the
	  <literal>GENERIC</literal> kernel configuration, as
	  increasing <literal>KSTACK_PAGES</literal> implicitly
	  decreases available usermode threads in an environment that
	  is already resource-starved.</para>

	<para>Taking into account the heavy resource requirements of
	  ZFS, in addition to the &arch.i386;-specific tuning
	  requirements for general workloads, using ZFS with the
	  &os;/&arch.i386;&nbsp;<literal>GENERIC</literal> kernel
	  is strongly discouraged.</para>

	<warning>
	  <para>It is extremely important to take note that, by
	    default, &man.freebsd-update.8; will install the
	    <literal>GENERIC</literal> kernel configuration, and
	    as such, &man.freebsd-update.8; consumers are strongly
	    encouraged to avoid &os;-provided kernel binary upgrades
	    with such configurations.</para>
	</warning>

	<note>
	  <para>Although there is slight change in how the crash
	    manifests on &os;/&arch.i386; between 10.0-RELEASE and
	    10.1-RELEASE, and given the date of the
	    <filename>/usr/src/UPDATING</filename> entry, there is no
	    evidence suggesting this is a regression between
	    &os;&nbsp;10.0-RELEASE and &os;&nbsp;10.1-RELEASE
	    directly.</para>
	</note>
      </listitem>

      <listitem>
	<para>Due to an incompatibility between &man.bsdconfig.8;
	  and &man.pkg.8;&nbsp;version 1.3, packages included on the
	  &os;&nbsp;dvd installer will not be recognized by
	  &man.bsdconfig.8;.</para>

	<para>To install packages from the <literal>dvd1.iso</literal>
	  installer, create the <filename
	    class="directory">/dist</filename> target directory, and
	  manually mount the <literal>dvd1.iso</literal>
	  <acronym>ISO</acronym>:</para>

	<screen>&prompt.root; mkdir -p /dist
&prompt.root; mount -t cd9660 /dev/<replaceable>cd0</replaceable> /dist</screen>

	<note>
	  <para>Be sure to use the correct <filename
	      class="directory">/dev</filename> device path for the
	    <literal>dvd1.iso</literal> <acronym>ISO</acronym>
	    installer.</para>
	</note>

	<para>Next, set <envar>REPOS_DIR</envar> to the path of the
	  <filename class="directory">repos/</filename> directory
	  within the installer so &man.pkg.8; will use the correct
	  repository metadata.</para>

	<para>If using &man.sh.1;:</para>

	<screen>&prompt.root; export REPOS_DIR=/dist/packages/repos</screen>

	<para>If using &man.csh.1;:</para>

	<screen>&prompt.root; setenv REPOS_DIR /dist/packages/repos</screen>

	<note>
	  <para>Keep in mind that <envar>REPOS_DIR</envar> will need
	    to be set again after the current shell session is
	    terminated, if continuing to use the packages provided on
	    the <literal>dvd1.iso</literal> installer.</para>
	</note>

	<para>Finally, bootstrap &man.pkg.8; from the
	  <acronym>ISO</acronym>, and install required
	  packages:</para>

	<screen>&prompt.root; pkg bootstrap
&prompt.root; pkg install <replaceable>xorg-server</replaceable> <replaceable>xorg</replaceable> <replaceable>gnome2</replaceable> [...]</screen>
      </listitem>

      <listitem>
	<para>[2015-02-06] <emphasis>Affects binary upgrade
	    users:</emphasis> The second phase of
	  <command>freebsd-update install</command>, the phase where
	  the running userland is upgraded, fails on systems deployed
	  with <literal>nss_ldap</literal> enabled in
	  &man.nsswitch.conf.5; when upgrading from 10.0-RELEASE to
	  10.1-RELEASE.</para>

	<para>A workaround is to disable <literal>nss_ldap</literal>
	  in &man.nsswitch.conf.5; prior to running
	  <command>freebsd-update install</command> to upgrade the
	  userland, after which it can be enabled again when the
	  upgrade process is completed.</para>

	<para>The problem is being investigated, and an Errata Notice
	  is expected to be issued when a solution to the problem is
	  identified.</para>
      </listitem>

      <listitem>
	<para>[2015-03-31] Several reports were received regarding the
	  <acronym>QCOW2</acronym> &os;&nbsp;virtual machine images
	  crashing on boot.  As result of this, these images have been
	  removed from the <acronym>FTP</acronym> mirrors, and the
	  hashes removed from <filename>CHECKSUM.SHA256</filename> and
	  <filename>CHECKSUM.MD5</filename> in the <filename
	    class="directory">VM-IMAGES/</filename> directory on the
	  <acronym>FTP</acronym> mirrors.</para>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 xml:id="late-news">
    <title>Late-Breaking News</title>

    <para>No news.</para>
  </sect1>
</article>