summaryrefslogtreecommitdiffstats
path: root/release
diff options
context:
space:
mode:
authorbmah <bmah@FreeBSD.org>2003-06-24 17:58:22 +0000
committerbmah <bmah@FreeBSD.org>2003-06-24 17:58:22 +0000
commit5a475da8315d6849725d0be607d8a6aca3aa97b2 (patch)
tree7ae72dd35b07da3dfd2854560235109f6a16de65 /release
parentc00d8c0364118283a19e5a00a7dbfe340ec79e90 (diff)
downloadFreeBSD-src-5a475da8315d6849725d0be607d8a6aca3aa97b2.zip
FreeBSD-src-5a475da8315d6849725d0be607d8a6aca3aa97b2.tar.gz
New errata: Problems with upgrading msdos(5) mounts from RO to RW. [1]
While here, move PAE item from "late-breaking news" to "open issues". Submitted by: tjr [1]
Diffstat (limited to 'release')
-rw-r--r--release/doc/en_US.ISO8859-1/errata/article.sgml20
1 files changed, 14 insertions, 6 deletions
diff --git a/release/doc/en_US.ISO8859-1/errata/article.sgml b/release/doc/en_US.ISO8859-1/errata/article.sgml
index 240cbbe..1b5acf0 100644
--- a/release/doc/en_US.ISO8859-1/errata/article.sgml
+++ b/release/doc/en_US.ISO8859-1/errata/article.sgml
@@ -135,6 +135,20 @@
<para>ACPI seems to make some i386 machines unstable. Turning off
ACPI support may help solve some of these problems; see an item
in <xref linkend="late-news">.</para>
+
+ <para>An integer overflow could cause kernel panics on PAE-using
+ machines with certain memory sizes. This bug has been corrected
+ on both the <literal>RELENG_5_1</literal> and
+ <literal>HEAD</literal> branches. A workaround for this problem
+ is to remove some memory, update the system in question, and
+ reinstall the memory.</para>
+
+ <para>Attempting to write to an &man.msdosfs.5; file system that
+ has been upgraded from read-only to read-write via
+ <command>mount -u</command> will cause the system to lock up.
+ To work around this problem, unmount the file system first, then
+ mount it again with the appropriate options instead of using
+ <command>mount -u</command>.</para>
]]>
</sect1>
@@ -185,12 +199,6 @@ hw.eisa_slots=0 # disable probing for EISA devices</programlisting>
support, various MAC framework updates, the GEOM disk geometry
system.</para>
- <para>An integer overflow could cause kernel panics on PAE-using
- machines with certain memory sizes. This bug has been corrected
- on both the <literal>RELENG_5_1</literal> and
- <literal>HEAD</literal> branches. A workaround for this problem
- is to remove some memory, update the system in question, and
- reinstall the memory.</para>
]]>
</sect1>
OpenPOWER on IntegriCloud