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