article.xml revision 286739
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 286739 2015-08-13 19:04:41Z 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 has been reported that instability may be present on 103 virtual machines running on other hypervisors, such as Xen 104 or KVM.</para> 105 106 <para>It causes various errors and makes &os; quite unstable. 107 Although the cause is still unclear, disabling unmapped I/O 108 works as a workaround. To disable it, choose 109 <literal>Escape to loader prompt</literal> in the boot menu 110 and enter the following lines from &man.loader.8; prompt, 111 after an <literal>OK</literal>:</para> 112 113 <screen>set vfs.unmapped_buf_allowed=0 114boot</screen> 115 116 <para>Note that the following line has to be added to 117 <filename>/boot/loader.conf</filename> after a boot. It 118 disables unmapped I/O at every boot:</para> 119 120 <programlisting>vfs.unmapped_buf_allowed=0</programlisting> 121 </listitem> 122 123 <listitem> 124 <para>&os;/&arch.i386; &release.prev; installed on ZFS 125 may crash during boot when the ZFS pool mount is attempted 126 while booting an unmodified <literal>GENERIC</literal> 127 kernel.</para> 128 129 <para>As described in <filename>/usr/src/UPDATING</filename> 130 entry <literal>20121223</literal>, rebuilding the kernel 131 with <literal>options KSTACK_PAGES=4</literal> has been 132 observed to resolve the boot-time crash. This, however, is 133 not an ideal solution for inclusion in the 134 <literal>GENERIC</literal> kernel configuration, as 135 increasing <literal>KSTACK_PAGES</literal> implicitly 136 decreases available usermode threads in an environment that 137 is already resource-starved.</para> 138 139 <para>Taking into account the heavy resource requirements of 140 ZFS, in addition to the &arch.i386;-specific tuning 141 requirements for general workloads, using ZFS with the 142 &os;/&arch.i386; <literal>GENERIC</literal> kernel 143 is strongly discouraged.</para> 144 145 <para>If installing &os;/&arch.i386; on ZFS, it is possible to 146 configure the system after installation to increase the 147 <literal>KSTACK_PAGES</literal>.</para> 148 149 <para>When prompted by &man.bsdinstall.8; to perform 150 additional post-installation configuration to the system, 151 select <guibutton>[ YES ]</guibutton>.</para> 152 153 <para>This procedure requires the system sources available 154 locally. If the <literal>System source code</literal> 155 distribution was not selected during installation, it can 156 be obtained using <application>svnlite</application>:</para> 157 158 <screen>&prompt.root; mkdir -p /usr/src 159&prompt.root; svnlite co svn://svn.freebsd.org/base/releng/10.2 /usr/src</screen> 160 161 <para>Build the <literal>kernel-toolchain</literal> required 162 to rebuild the kernel:</para> 163 164 <screen>&prompt.root; make -C /usr/src kernel-toolchain</screen> 165 166 <para>Next, create a kernel configuration file to increase the 167 <literal>KSTACK_PAGES</literal> option:</para> 168 169 <screen>&prompt.root; printf "include GENERIC\noptions KSTACK_PAGES=4\n" > <filename>/usr/src/sys/i386/conf/<replaceable>ZFS</replaceable></filename></screen> 170 171 <para>Then build and install the 172 <replaceable>ZFS</replaceable> kernel:</para> 173 174 <screen>&prompt.root; make -C /usr/src buildkernel KERNCONF=<replaceable>ZFS</replaceable> 175&prompt.root; make -C /usr/src installkernel KERNCONF=<replaceable>ZFS</replaceable></screen> 176 177 <warning> 178 <para>It is extremely important to take note that, by 179 default, &man.freebsd-update.8; will install the 180 <literal>GENERIC</literal> kernel configuration, and 181 as such, &man.freebsd-update.8; consumers are strongly 182 encouraged to avoid &os;-provided kernel binary upgrades 183 with such configurations.</para> 184 </warning> 185 </listitem> 186 187 <listitem> 188 <para>Due to an incompatibility between &man.bsdconfig.8; 189 and &man.pkg.8;, packages included on the &os; dvd 190 installer will not be recognized by 191 &man.bsdconfig.8;.</para> 192 193 <para>To install packages from the <literal>dvd1.iso</literal> 194 installer, create the <filename 195 class="directory">/dist</filename> target directory, and 196 manually mount the <literal>dvd1.iso</literal> 197 <acronym>ISO</acronym>:</para> 198 199 <screen>&prompt.root; mkdir -p /dist 200&prompt.root; mount -t cd9660 /dev/<replaceable>cd0</replaceable> /dist</screen> 201 202 <note> 203 <para>Be sure to use the correct <filename 204 class="directory">/dev</filename> device path for the 205 <literal>dvd1.iso</literal> <acronym>ISO</acronym> 206 installer.</para> 207 </note> 208 209 <para>Next, set <envar>REPOS_DIR</envar> to the path of the 210 <filename class="directory">repos/</filename> directory 211 within the installer so &man.pkg.8; will use the correct 212 repository metadata.</para> 213 214 <para>If using &man.sh.1;:</para> 215 216 <screen>&prompt.root; export REPOS_DIR=/dist/packages/repos</screen> 217 218 <para>If using &man.csh.1;:</para> 219 220 <screen>&prompt.root; setenv REPOS_DIR /dist/packages/repos</screen> 221 222 <note> 223 <para>Keep in mind that <envar>REPOS_DIR</envar> will need 224 to be set again after the current shell session is 225 terminated, if continuing to use the packages provided on 226 the <literal>dvd1.iso</literal> installer.</para> 227 </note> 228 229 <para>Finally, bootstrap &man.pkg.8; from the 230 <acronym>ISO</acronym>, and install required 231 packages:</para> 232 233 <screen>&prompt.root; pkg bootstrap 234&prompt.root; pkg install <replaceable>xorg-server</replaceable> <replaceable>xorg</replaceable> <replaceable>gnome3</replaceable> [...]</screen> 235 </listitem> 236 237 <listitem> 238 <para>An issue was discovered where the &man.netstat.1; 239 <literal>-s</literal> option will cause a segmentation fault 240 on systems with <literal>IPSEC</literal> compiled into the 241 kernel. The issue was resolved in the 242 <literal>stable/10</literal> branch, and an Errata Notice is 243 planned after &release.prev; is released.</para> 244 </listitem> 245 246 <listitem> 247 <para>An issue was discovered that causes &man.make.1; to 248 generate noisy output when doing source-based upgrades from 249 &os; 9.3 and earlier. The issue was reported in PR 202277, 250 and after investigation and determining the issue does not 251 cause source-based upgrades to fail, a post-release Errata 252 Notice is planned.</para> 253 </listitem> 254 255 <listitem> 256 <para>An issue with &os; virtual machines with 257 <application>vagrant</application> was discovered that 258 affects the <application>VirtualBox</application> where the 259 virtual machine will not start on the initial boot invoked 260 with <literal>vagrant up</literal>.</para> 261 262 <para>The issue is due to the virtual machine 263 <acronym>MAC</acronym> being unset, as &os; does not provide 264 a default <filename>Vagrantfile</filename>.</para> 265 266 <para>It has been observed, however, that a subsequent 267 invocation of <literal>vagrant up</literal> will allow the 268 virtual machine to successfully boot, allowing access via 269 <literal>vagrant ssh</literal>.</para> 270 </listitem> 271 </itemizedlist> 272 </sect1> 273 274 <sect1 xml:id="late-news"> 275 <title>Late-Breaking News</title> 276 277 <para>No news.</para> 278 </sect1> 279</article> 280