article.xml revision 278328
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 SYSTEM "../../share/xml/security.xml"> 8<!ENTITY errata SYSTEM "../../share/xml/errata.xml"> 9]> 10 11<article xmlns="http://docbook.org/ns/docbook" 12 xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"> 13 14 <info> 15 <title>&os; &release.prev; Errata </title> 16 17 <author><orgname>The &os; Project</orgname></author> 18 19 <pubdate>$FreeBSD: stable/10/release/doc/en_US.ISO8859-1/errata/article.xml 278328 2015-02-06 19:44:26Z gjb $</pubdate> 20 21 <copyright> 22 <year>2015</year> 23 24 <holder role="mailto:doc@FreeBSD.org">The &os; Documentation 25 Project</holder> 26 </copyright> 27 28 <legalnotice xml:id="trademarks" role="trademarks"> 29 &tm-attrib.freebsd; 30 &tm-attrib.intel; 31 &tm-attrib.sparc; 32 &tm-attrib.general; 33 </legalnotice> 34 35 <abstract> 36 <para>This document lists errata items for &os; &release.prev;, 37 containing significant information discovered after the 38 release or too late in the release cycle to be otherwise 39 included in the release documentation. This information 40 includes security advisories, as well as news relating to the 41 software or documentation that could affect its operation or 42 usability. An up-to-date version of this document should 43 always be consulted before installing this version of 44 &os;.</para> 45 46 <para>This errata document for &os; &release.prev; will be 47 maintained until the release of &os; &release.next;.</para> 48 </abstract> 49 </info> 50 51 <sect1 xml:id="intro"> 52 <title>Introduction</title> 53 54 <para>This errata document contains <quote>late-breaking 55 news</quote> about &os; &release.prev; Before installing this 56 version, it is important to consult this document to learn about 57 any post-release discoveries or problems that may already have 58 been found and fixed.</para> 59 60 <para>Any version of this errata document actually distributed 61 with the release (for example, on a CDROM distribution) will be 62 out of date by definition, but other copies are kept updated on 63 the Internet and should be consulted as the <quote>current 64 errata</quote> for this release. These other copies of the 65 errata are located at <link 66 xlink:href="http://www.FreeBSD.org/releases/" />, plus any 67 sites which keep up-to-date mirrors of this location.</para> 68 69 <para>Source and binary snapshots of &os; &release.branch; also 70 contain up-to-date copies of this document (as of the time of 71 the snapshot).</para> 72 73 <para>For a list of all &os; CERT security advisories, see <link 74 xlink:href="http://www.FreeBSD.org/security/"/> or <link 75 xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/"/>.</para> 76 </sect1> 77 78 <sect1 xml:id="security"> 79 <title>Security Advisories</title> 80 81 &security; 82 </sect1> 83 84 <sect1 xml:id="errata"> 85 <title>Errata Notices</title> 86 87 &errata; 88 </sect1> 89 90 <sect1 xml:id="open-issues"> 91 <title>Open Issues</title> 92 93 <itemizedlist> 94 <listitem> 95 <para>&os;/&arch.i386; &release.prev; running as a guest 96 operating system on <application>VirtualBox</application> 97 can have a problem with disk I/O access. It depends on some 98 specific hardware configuration and does not depend on a 99 specific version of <application>VirtualBox</application> or 100 host operating system.</para> 101 102 <para>It causes various errors and makes &os; quite unstable. 103 Although the cause is still unclear, disabling unmapped I/O 104 works as a workaround. To disable it, choose 105 <literal>Escape to loader prompt</literal> in the boot menu 106 and enter the following lines from &man.loader.8; prompt, 107 after an <literal>OK</literal>:</para> 108 109 <screen>set vfs.unmapped_buf_allowed=0 110boot</screen> 111 112 <para>Note that the following line has to be added to 113 <filename>/boot/loader.conf</filename> after a boot. It 114 disables unmapped I/O at every boot:</para> 115 116 <programlisting>vfs.unmapped_buf_allowed=0</programlisting> 117 118 <para>[2014-04-03 update] It has been reported that 119 instability may be present on virtual machines running 120 on other hypervisors, such as Xen or KVM.</para> 121 </listitem> 122 123 <listitem> 124 <para>&os;/&arch.i386; 10.1-RELEASE configured with 125 a multi-disk ZFS dataset (mirror, raidz1, raidz2, raidz3) 126 may crash during boot when the ZFS pool mount is attempted 127 while booting an unmodified <literal>GENERIC</literal> 128 kernel.</para> 129 130 <para>As described in <filename>/usr/src/UPDATING</filename> 131 entry <literal>20121223</literal>, rebuilding the kernel 132 with <literal>options KSTACK_PAGES=4</literal> has been 133 observed to resolve the boot-time crash. This, however, is 134 not an ideal solution for inclusion in the 135 <literal>GENERIC</literal> kernel configuration, as 136 increasing <literal>KSTACK_PAGES</literal> implicitly 137 decreases available usermode threads in an environment that 138 is already resource-starved.</para> 139 140 <para>Taking into account the heavy resource requirements of 141 ZFS, in addition to the &arch.i386;-specific tuning 142 requirements for general workloads, using ZFS with the 143 &os;/&arch.i386; <literal>GENERIC</literal> kernel 144 is strongly discouraged.</para> 145 146 <warning> 147 <para>It is extremely important to take note that, by 148 default, &man.freebsd-update.8; will install the 149 <literal>GENERIC</literal> kernel configuration, and 150 as such, &man.freebsd-update.8; consumers are strongly 151 encouraged to avoid &os;-provided kernel binary upgrades 152 with such configurations.</para> 153 </warning> 154 155 <note> 156 <para>Although there is slight change in how the crash 157 manifests on &os;/&arch.i386; between 10.0-RELEASE and 158 10.1-RELEASE, and given the date of the 159 <filename>/usr/src/UPDATING</filename> entry, there is no 160 evidence suggesting this is a regression between 161 &os; 10.0-RELEASE and &os; 10.1-RELEASE 162 directly.</para> 163 </note> 164 </listitem> 165 166 <listitem> 167 <para>Due to an incompatibility between &man.bsdconfig.8; 168 and &man.pkg.8; version 1.3, packages included on the 169 &os; dvd installer will not be recognized by 170 &man.bsdconfig.8;.</para> 171 172 <para>To install packages from the <literal>dvd1.iso</literal> 173 installer, create the <filename 174 class="directory">/dist</filename> target directory, and 175 manually mount the <literal>dvd1.iso</literal> 176 <acronym>ISO</acronym>:</para> 177 178 <screen>&prompt.root; mkdir -p /dist 179&prompt.root; mount -t cd9660 /dev/<replaceable>cd0</replaceable> /dist</screen> 180 181 <note> 182 <para>Be sure to use the correct <filename 183 class="directory">/dev</filename> device path for the 184 <literal>dvd1.iso</literal> <acronym>ISO</acronym> 185 installer.</para> 186 </note> 187 188 <para>Next, set <envar>REPOS_DIR</envar> to the path of the 189 <filename class="directory">repos/</filename> directory 190 within the installer so &man.pkg.8; will use the correct 191 repository metadata.</para> 192 193 <para>If using &man.sh.1;:</para> 194 195 <screen>&prompt.root; export REPOS_DIR=/dist/packages/repos</screen> 196 197 <para>If using &man.csh.1;:</para> 198 199 <screen>&prompt.root; setenv REPOS_DIR /dist/packages/repos</screen> 200 201 <note> 202 <para>Keep in mind that <envar>REPOS_DIR</envar> will need 203 to be set again after the current shell session is 204 terminated, if continuing to use the packages provided on 205 the <literal>dvd1.iso</literal> installer.</para> 206 </note> 207 208 <para>Finally, bootstrap &man.pkg.8; from the 209 <acronym>ISO</acronym>, and install required 210 packages:</para> 211 212 <screen>&prompt.root; pkg bootstrap 213&prompt.root; pkg install <replaceable>xorg-server</replaceable> <replaceable>xorg</replaceable> <replaceable>gnome2</replaceable> [...]</screen> 214 </listitem> 215 216 <listitem> 217 <para>[2015-02-06] <emphasis>Affects binary upgrade 218 users:</emphasis> The second phase of 219 <command>freebsd-update install</command>, the phase where 220 the running userland is upgraded, fails on systems deployed 221 with <literal>nss_ldap</literal> enabled in 222 &man.nsswitch.conf.5; when upgrading from 10.0-RELEASE to 223 10.1-RELEASE.</para> 224 225 <para>A workaround is to disable <literal>nss_ldap</literal> 226 in &man.nsswitch.conf.5; prior to running 227 <command>freebsd-update install</command> to upgrade the 228 userland, after which it can be enabled again when the 229 upgrade process is completed.</para> 230 231 <para>The problem is being investigated, and an Errata Notice 232 is expected to be issued when a solution to the problem is 233 identified.</para> 234 </listitem> 235 </itemizedlist> 236 </sect1> 237 238 <sect1 xml:id="late-news"> 239 <title>Late-Breaking News</title> 240 241 <para>No news.</para> 242 </sect1> 243</article> 244