From: "Shyam Mani" <fox2mike@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: hb-install-amd64-kernel.xml
Date: Sun, 26 Feb 2006 14:38:56 +0000 [thread overview]
Message-ID: <200602261439.k1QEdqeB023279@robin.gentoo.org> (raw)
fox2mike 06/02/26 14:38:56
Modified: xml/htdocs/doc/en/handbook hb-install-amd64-kernel.xml
Log:
Fixes for 113156, backported to the current handbook as well.
Revision Changes Path
1.38 +10 -4 xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml?rev=1.38&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml?rev=1.38&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml.diff?r1=1.37&r2=1.38&cvsroot=gentoo
Index: hb-install-amd64-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- hb-install-amd64-kernel.xml 17 Feb 2006 02:34:39 -0000 1.37
+++ hb-install-amd64-kernel.xml 26 Feb 2006 14:38:55 -0000 1.38
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml,v 1.37 2006/02/17 02:34:39 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-amd64-kernel.xml,v 1.38 2006/02/26 14:38:55 fox2mike Exp $ -->
<sections>
-<version>2.13</version>
-<date>2006-02-15</date>
+<version>2.14</version>
+<date>2006-02-26</date>
<section>
<title>Timezone</title>
@@ -160,11 +160,17 @@
</pre>
<p>
-We shall then select the exact processor type.
+We shall then select the exact processor type.The x86_64 kernel maintainer
+strongly recommends users enable MCE features so that they are able to be
+notified of any hardware problems. On x86_64, these errors are not printed to
+<c>dmesg</c> like on other architectures, but to <path>/dev/mcelog</path>. This
+requires the <c>app-admin/mcelog</c> package.
</p>
<pre caption="Selecting processor type and features">
Processor type and features --->
+ [ ] Intel MCE Features
+ [ ] AMD MCE Features
Processor family (AMD-Opteron/Athlon64) --->
( ) AMD-Opteron/Athlon64
( ) Intel EM64T
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2006-02-26 14:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 14:38 Shyam Mani [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-21 14:47 [gentoo-doc-cvs] cvs commit: hb-install-amd64-kernel.xml Lukasz Damentko
2006-05-28 14:23 Josh Saddler
2006-05-28 14:21 Josh Saddler
2006-04-09 19:23 Jan Kundrat
2006-02-26 14:38 Shyam Mani
2006-02-17 2:34 Lukasz Damentko
2006-02-15 18:41 Shyam Mani
2006-02-15 15:33 Xavier Neys
2006-02-15 15:33 Xavier Neys
2006-02-15 15:33 Xavier Neys
2006-02-13 20:24 Shyam Mani
2005-11-27 1:46 Xavier Neys
2005-08-08 14:03 swift
2005-07-29 5:21 Shyam Mani
2005-07-27 22:17 Shyam Mani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200602261439.k1QEdqeB023279@robin.gentoo.org \
--to=fox2mike@lark.gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox