From: Borislav Petkov <bp@suse.de>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Chris Metcalf <cmetcalf@mellanox.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org, Tony Luck <tony.luck@intel.com>
Subject: Re: [lkp-robot] [EDAC] 5729ee3edf: kmsg.EDAC_sbridge:Failed_to_register_device_with_error
Date: Mon, 10 Jul 2017 05:40:00 +0200 [thread overview]
Message-ID: <20170710034000.GA22329@nazgul.tnic> (raw)
In-Reply-To: <20170710024217.GC26389@yexl-desktop>
On Mon, Jul 10, 2017 at 10:42:17AM +0800, kernel test robot wrote:
> commit: 5729ee3edf50e4627ab216a170a4748a2d62dd12 ("EDAC: Remove EDAC_MM_EDAC")
> https://git.kernel.org/cgit/linux/kernel/git/bp/bp.git edac-for-4.12-stub
So this is an old branch, lemme kill it.
> in testcase: unixbench
> with following parameters:
>
> runtime: 300s
> nr_task: 1
> test: pipe
> cpufreq_governor: performance
>
> test-description: UnixBench is the original BYTE UNIX benchmark suite aims to test performance of Unix-like system.
> test-url: https://github.com/kdlucas/byte-unixbench
>
>
> on test machine: 88 threads Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz with 64G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> kern :err : [ 32.919091] EDAC sbridge: Couldn't find mci handler
> kern :err : [ 32.919092] EDAC sbridge: Couldn't find mci handler
> kern :err : [ 32.919095] EDAC sbridge: Failed to register device with error -22.
AFAIR, we talked about this already. You need to disable CONFIG_EDAC_GHES
temporarily as it registers before the sbridge module.
kern :info : [ 26.382523] ghes_edac: This EDAC driver relies on BIOS to enumerate memory and get error reports.
kern :info : [ 26.392439] ghes_edac: Unfortunately, not all BIOSes reflect the memory layout correctly.
kern :info : [ 26.401574] ghes_edac: So, the end result of using this driver varies from vendor to vendor.
kern :info : [ 26.411001] ghes_edac: If you find incorrect reports, please contact your hardware vendor
kern :info : [ 26.420137] ghes_edac: to correct its BIOS.
kern :info : [ 26.424812] ghes_edac: This system has 8 DIMM sockets.
kern :info : [ 26.430737] EDAC MC0: Giving out device to module ghes_edac.c controller ghes_edac: DEV ghes (INTERRUPT)
kern :info : [ 26.441401] EDAC MC1: Giving out device to module ghes_edac.c controller ghes_edac: DEV ghes (INTERRUPT)
kern :info : [ 26.452619] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
We're working on fixing this properly but the fix is not ready yet.
Thanks.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
prev parent reply other threads:[~2017-07-10 3:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 2:42 kernel test robot
2017-07-10 3:40 ` Borislav Petkov [this message]
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=20170710034000.GA22329@nazgul.tnic \
--to=bp@suse.de \
--cc=cmetcalf@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=tony.luck@intel.com \
--cc=xiaolong.ye@intel.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
all inboxes | Powered by JetHome®