From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751616AbdFIJkx (ORCPT <rfc822;w@1wt.eu>);
        Fri, 9 Jun 2017 05:40:53 -0400
Received: from mail.skyhub.de ([5.9.137.197]:36182 "EHLO mail.skyhub.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751515AbdFIJkv (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 9 Jun 2017 05:40:51 -0400
Date: Fri, 9 Jun 2017 11:40:26 +0200
From: Borislav Petkov <bp@alien8.de>
To: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>
Cc: "Ye, Xiaolong" <xiaolong.ye@intel.com>,
        "'Borislav Petkov'" <bp@suse.de>,
        "'linux-edac'" <linux-edac@vger.kernel.org>,
        "'LKML'" <linux-kernel@vger.kernel.org>,
        "'Stephen Rothwell'" <sfr@canb.auug.org.au>,
        "'lkp@01.org'" <lkp@01.org>
Subject: Re: [lkp-robot] [EDAC, sb_edac]  e2f747b1f4:
 kmsg.EDAC_sbridge:Failed_to_register_device_with_error
Message-ID: <20170609094025.ee33cazzf4qdahle@pd.tnic>
References: <20170605062231.GA2969@yexl-desktop>
 <E6AF1AFDEA62A94A97508F458CBDD47F6F5A2058@SHSMSX101.ccr.corp.intel.com>
 <E6AF1AFDEA62A94A97508F458CBDD47F6F5A321C@SHSMSX101.ccr.corp.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <E6AF1AFDEA62A94A97508F458CBDD47F6F5A321C@SHSMSX101.ccr.corp.intel.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Jun 09, 2017 at 02:28:30AM +0000, Zhuo, Qiuxu wrote:
> Hi Xiaolong,
> 
>     Fixed this issue by 'EDAC, sb_edac: Avoid creating 'SOCK' EDAC memory controller' (you were also CCed by 'Reported-by').
>     Thanks for this test case :-)

Xiaolong,

can you please run Qiuxu's patch to verify it fixes your issue?

Thanks.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.