svn commit: r306972 - in stable/11/release/doc: en_US.ISO8859-1/errata share/xml

[Glen Barber]

Author: gjb
Date: Mon Oct 10 15:49:49 2016
New Revision: 306972
URL: https://svnweb.freebsd.org/changeset/base/306972

Log:
  - Add known-issue entries for 11.0-RELEASE errata.html.
  - Bump version numbers in release.ent.
  - Bump the copyright year for the errata file.
  
  Sponsored by:	The FreeBSD Foundation

Modified:
  stable/11/release/doc/en_US.ISO8859-1/errata/article.xml
  stable/11/release/doc/share/xml/release.ent

Modified: stable/11/release/doc/en_US.ISO8859-1/errata/article.xml
==============================================================================
--- stable/11/release/doc/en_US.ISO8859-1/errata/article.xml	Mon Oct 10 15:48:40 2016	(r306971)
+++ stable/11/release/doc/en_US.ISO8859-1/errata/article.xml	Mon Oct 10 15:49:49 2016	(r306972)
@@ -19,7 +19,7 @@
     <pubdate>$FreeBSD$</pubdate>
 
     <copyright>
-      <year>2015</year>
+      <year>2016</year>
 
       <holder role="mailto:doc at FreeBSD.org">The &os; Documentation Project</holder>
     </copyright>
@@ -89,7 +89,79 @@
   <sect1 xml:id="open-issues">
     <title>Open Issues</title>
 
-    <para>No open issues.</para>
+    <itemizedlist>
+      <listitem>
+	<para>An issue was discovered with Amazon® EC2™
+	  images which would cause the virtual machine to hang during
+	  boot when upgrading from previous FreeBSD versions. New
+	  EC2™ installations are not affected, but exisiting
+	  installations running earlier releases are advised to wait
+	  until the issue is resolved in an Errata Notice before
+	  upgrading.  An Errata Notice to address this is planned
+	  following the release.</para>
+      </listitem>
+
+      <listitem>
+	<para>&os;/&arch.i386; installed on ZFS may crash during boot
+	  when the ZFS pool mount is attempted while booting an
+	  unmodified <literal>GENERIC</literal> kernel.</para>
+
+	<para>A system tunable has been added as of revision
+	  <literal>r286584</literal> to make the
+	  <literal>kern.kstack_pages</literal> tunable configurable
+	  without recompiling the kernel.</para>
+
+	<para>To mitigate system crashes with such configurations,
+	  chose <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 kern.kstack_pages=4
+boot</screen>
+
+	<para>Add this line to
+	  <filename>/boot/loader.conf</filename> for the change to
+	  persist across reboots:</para>
+
+	<programlisting>kern.kstack_pages=4</programlisting>
+      </listitem>
+
+      <listitem>
+	<para>A bug was diagnosed in interaction of the
+	  <literal>pmap_activate()</literal> function and
+	  <acronym>TLB</acronym> shootdown <acronym>IPI</acronym>
+	  handler on amd64 systems which have <acronym>PCID</acronym>
+	  features but do not implement the <acronym>INVPCID</acronym>
+	  instruction.  On such machines, such as SandyBridge™
+	  and IvyBridge™ microarchitectures, set the loader
+	  tunable <literal>vm.pmap.pcid_enabled=0</literal> during
+	  boot:</para>
+
+	<screen>set vm.pmap.pcid_enabled=0
+boot</screen>
+
+	<para>Add this line to
+	  <filename>/boot/loader.conf</filename> for the change to
+	  persist across reboots:</para>
+
+	<para>To check if the system is affected, check
+	  &man.dmesg.8; for <acronym>PCID</acronym> listed in the
+	  "Features2", and absence of
+	  <acronym>INVPCID</acronym> in the "Structured Extended
+	  Features".  If the <acronym>PCID</acronym> feature is
+	  not present, or <acronym>INVPCID</acronym> is present,
+	  system is not affected.</para>
+
+	<programlisting>vm.pmap.pcid_enabled=0</programlisting>
+      </listitem>
+
+      <listitem>
+	<para>The Release Notes errorneously states the
+	  <literal>WITH_SYSTEM_COMPILER</literal> &man.src.conf.5;
+	  option is enabled by default, however this was disabled
+	  prior to the final release build.</para>
+      </listitem>
+    </itemizedlist>
   </sect1>
 
   <sect1 xml:id="late-news">

Modified: stable/11/release/doc/share/xml/release.ent
==============================================================================
--- stable/11/release/doc/share/xml/release.ent	Mon Oct 10 15:48:40 2016	(r306971)
+++ stable/11/release/doc/share/xml/release.ent	Mon Oct 10 15:49:49 2016	(r306972)
@@ -11,15 +11,15 @@
 <!-- The previous version used for comparison in the "What's New"
      section.  For -CURRENT, we might point back to the last
      branchpoint. -->
-<!ENTITY release.prev "10.3-RELEASE">
+<!ENTITY release.prev "11.0-RELEASE">
 
 <!-- The previous stable release, useful for pointing user's at the
      release they SHOULD be running if they don't want the bleeding
      edge. -->
-<!ENTITY release.prev.stable "10.2-RELEASE">
+<!ENTITY release.prev.stable "10.3-RELEASE">
 
 <!-- The next version to be released, usually used for snapshots. -->
-<!ENTITY release.next "12.0-RELEASE">
+<!ENTITY release.next "11.1-RELEASE">
 
 <!-- The name of this branch. -->
 <!ENTITY release.branch "11.0-STABLE">
@@ -39,8 +39,8 @@
      doc.relnotes.mk when updating this -->
 <!ENTITY release.type "snapshot">
 <!ENTITY % release.type.current  "IGNORE">
-<!ENTITY % release.type.snapshot "IGNORE">
-<!ENTITY % release.type.release "INCLUDE">
+<!ENTITY % release.type.snapshot "INCLUDE">
+<!ENTITY % release.type.release "IGNORE">
 
 <![%release.type.current;[
 <!ENTITY release '&release.current;'>
@@ -58,7 +58,7 @@
 <!ENTITY release.manpath.xorg          "7.5.1">
 <!ENTITY release.manpath.netbsd        "5.1">
 <!ENTITY release.manpath.freebsd-ports "Ports">
-<!ENTITY release.manpath.freebsd       "10-current">
+<!ENTITY release.manpath.freebsd       "11-current">
 
 <!-- Text constants which probably don't need to be changed.-->