From: Doug Thompson <norsk5@yahoo.com>
To: bluesmoke ML <bluesmoke-devel@lists.sourceforge.net>,
RustyColbert <rusty.colbert@hp.com>
Subject: Re: Module loads but has error.
Date: Tue, 20 Oct 2009 14:05:19 -0700 (PDT) [thread overview]
Message-ID: <375171.22182.qm@web50101.mail.re2.yahoo.com> (raw)
In-Reply-To: <EC2969A33F12344780D895AFCAA422CE508626136F@GVW1095EXB.americas.hpqcorp.net>
Copying Mauro on this one as he has the lead on it. He is currently in Japan for a few days for the kernel summit
doug t
--- On Tue, 10/20/09, Colbert, Rusty <rusty.colbert@hp.com> wrote:
> From: Colbert, Rusty <rusty.colbert@hp.com>
> Subject: Module loads but has error.
> To: "bluesmoke ML" <bluesmoke-devel@lists.sourceforge.net>
> Date: Tuesday, October 20, 2009, 11:03 AM
>
> EDAC
> i7core: Device not
> found: dev 03.0 PCI ID 8086:2c18
>
>
>
> This would seem to be the
> PCI_DEVICE_ID_INTEL_I7_MCR
>
>
>
> The modules are loaded, but I think this
> error may have caused them to
> be ineffective. There are no files under
> /sys/devices/system/edac/mc as in
> older edac enabled kernels.
>
>
>
> I have access to multiple platforms and
> can acquire DIMMs with ECC
> errors, but I don't see the point in installing them if
> the driver is not
> installing properly.
>
>
>
> I am currently running on an HP ProLiant DL360. It
> has
> Intel Xeon CPUs X5550.
>
> Any pointers on how I should approach
> debugging this?
>
>
>
>
>
>
>
> -----Inline Attachment Follows-----
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference
> in SF, CA
> is the only developer event you need to attend this year.
> Jumpstart your
> developing skills, take BlackBerry mobile applications to
> market and stay
> ahead of the curve. Join us from November 9 - 12, 2009.
> Register now!
> http://p.sf.net/sfu/devconference
> -----Inline Attachment Follows-----
>
> _______________________________________________
> bluesmoke-devel mailing list
> bluesmoke-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
next prev parent reply other threads:[~2009-10-20 21:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 17:03 Module loads but has error Colbert, Rusty
2009-10-20 21:05 ` Doug Thompson [this message]
2009-10-20 21:18 ` Keith Mannthey
2009-10-20 22:47 ` Mauro Carvalho Chehab
2009-10-21 14:13 ` Colbert, Rusty
2009-10-21 15:26 ` Keith Mannthey
2009-10-21 20:03 ` Mauro Carvalho Chehab
2009-10-21 20:58 ` Colbert, Rusty
2009-10-21 23:03 ` Mauro Carvalho Chehab
2009-10-22 15:04 ` Colbert, Rusty
2009-10-22 20:02 ` Mauro Carvalho Chehab
2009-10-22 20:26 ` Colbert, Rusty
2009-10-21 17:55 ` Colbert, Rusty
2009-10-21 20:15 ` Mauro Carvalho Chehab
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=375171.22182.qm@web50101.mail.re2.yahoo.com \
--to=norsk5@yahoo.com \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=rusty.colbert@hp.com \
/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