From: Borislav Petkov <borislav.petkov@amd.com>
To: Joachim Ernst <joachim.ernst@web.de>
Cc: bluesmoke-devel@lists.sourceforge.net
Subject: Re: EDAC and DDR3 memory
Date: Sat, 19 Dec 2009 16:13:52 +0100 [thread overview]
Message-ID: <20091219151352.GA25072@aftab> (raw)
In-Reply-To: <4B2CBA37.2090101@web.de>
On Sat, Dec 19, 2009 at 12:34:15PM +0100, Joachim Ernst wrote:
> Dear EDAC-Developers,
>
> is there a chance to get DDR3 running with EDAC?
> Here is the output of dmesg | grep EDAC:
>
> EDAC MC: Ver: 2.1.0 Dec 8 2009
> EDAC amd64_edac: Ver: 3.2.0 Dec 8 2009
> EDAC amd64: ECC is enabled by BIOS, Proceeding with EDAC module
> initialization
> EDAC MC: F10h CPU detected
> EDAC amd64: f10_probe_valid_hardware() This machine is running with DDR3
> memory. This is not currently supported. DCHR0=0x3f58090d DCHR1=0x3f58090d
> EDAC amd64: Contact 'amd64_edac' module MAINTAINER to help add support.
DDR3 support got merged last week so you can give 2.6.33-rc1 a try.
--
Regards/Gruss,
Boris.
Operating | Advanced Micro Devices GmbH
System | Karl-Hammerschmidt-Str. 34, 85609 Dornach b. München, Germany
Research | Geschäftsführer: Andrew Bowd, Thomas M. McCoy, Giuliano Meroni
Center | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
(OSRC) | Registergericht München, HRB Nr. 43632
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
next prev parent reply other threads:[~2009-12-19 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 11:34 EDAC and DDR3 memory Joachim Ernst
2009-12-19 15:13 ` Borislav Petkov [this message]
2009-12-21 21:23 ` Doug Thompson
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=20091219151352.GA25072@aftab \
--to=borislav.petkov@amd.com \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=joachim.ernst@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.