From: kernel test robot <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: [sb_edac] 7d375bffa5:
Date: Sun, 23 Aug 2015 08:08:22 +0800 [thread overview]
Message-ID: <87egiukgsp.fsf@yhuang-dev.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 7d375bffa52477c1be7db5a5dda99996582512c3 ("sb_edac: Fix support for systems with two home agents per socket")
We found the following message in kernel log on a Sandy Bridge-EP machine.
[ 21.647493] EDAC sbridge: Couldn't find mci handler
[ 21.647505] EDAC sbridge: Couldn't find mci handler
Thanks,
Ying Huang
[-- Attachment #2: kmsg.xz --]
[-- Type: application/x-xz, Size: 28236 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <ying.huang@intel.com>
To: Tony Luck <tony.luck@intel.com>
Cc: lkp@01.org
Cc: LKML <linux-kernel@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Subject: [lkp] [sb_edac] 7d375bffa5:
Date: Sun, 23 Aug 2015 08:08:22 +0800 [thread overview]
Message-ID: <87egiukgsp.fsf@yhuang-dev.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 7d375bffa52477c1be7db5a5dda99996582512c3 ("sb_edac: Fix support for systems with two home agents per socket")
We found the following message in kernel log on a Sandy Bridge-EP machine.
[ 21.647493] EDAC sbridge: Couldn't find mci handler
[ 21.647505] EDAC sbridge: Couldn't find mci handler
Thanks,
Ying Huang
[-- Attachment #2: kmsg.xz --]
[-- Type: application/x-xz, Size: 28236 bytes --]
next reply other threads:[~2015-08-23 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 0:08 kernel test robot [this message]
2015-08-23 0:08 ` [lkp] [sb_edac] 7d375bffa5: kernel test robot
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=87egiukgsp.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=lkp@lists.01.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 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.