From: Ye Xiaolong <xiaolong.ye@intel.com>
To: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>
Cc: "'Stephen Rothwell'" <sfr@canb.auug.org.au>,
"'LKML'" <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>, "'Borislav Petkov'" <bp@suse.de>,
"'lkp@01.org'" <lkp@01.org>,
"'linux-edac'" <linux-edac@vger.kernel.org>
Subject: Re: [LKP] [lkp-robot] [EDAC, sb_edac] e2f747b1f4: kmsg.EDAC_sbridge:Failed_to_register_device_with_error
Date: Mon, 12 Jun 2017 13:11:13 +0800 [thread overview]
Message-ID: <20170612051113.GD22185@yexl-desktop> (raw)
In-Reply-To: <20170612013046.GG29690@yexl-desktop>
On 06/12, Ye Xiaolong wrote:
>On 06/10, Zhuo, Qiuxu wrote:
>>> From: Borislav Petkov [mailto:bp@alien8.de]
>>>
>>> Xiaolong,
>>>
>>> can you please run Qiuxu's patch to verify it fixes your issue?
>>
>>
>>Hi Boris,
>> I manually verified the fix patch on the Broadwell-DE server on which the bug was found by Xiaolong:
>> the sb_edac can be loaded successfully, and it identified which size and type of DIMMs were installed
>> in each slot correctly (see attached dmesg.sb_edac.on.Broadwell-DE.log).
>>
>>Hi Xiaolong,
>> Would you please also test the patch by your LKP method by which the issue was found last time.
>>
>
>Got it, I've queued test jobs for your fix patch, will let you know the result
>once I get the it.
Confirmed the error is gone with qiuxu's fix patch.
Tested-by: From: Ye Xiaolong <xiaolong.ye@intel.com>
Thanks,
Xiaolong
>
>Thanks,
>Xiaolong
>
>
>>Thanks!
>>
>>BR
>>Qiuxu
>>
>>
>>
>
>
>_______________________________________________
>LKP mailing list
>LKP@lists.01.org
>https://lists.01.org/mailman/listinfo/lkp
next prev parent reply other threads:[~2017-06-12 5:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 6:22 kernel test robot
2017-06-05 13:07 ` Zhuo, Qiuxu
2017-06-09 2:28 ` Zhuo, Qiuxu
2017-06-09 9:40 ` Borislav Petkov
2017-06-10 4:16 ` Zhuo, Qiuxu
2017-06-12 1:30 ` Ye Xiaolong
2017-06-12 5:11 ` Ye Xiaolong [this message]
2017-06-14 9:55 ` [LKP] " Borislav Petkov
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=20170612051113.GD22185@yexl-desktop \
--to=xiaolong.ye@intel.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=qiuxu.zhuo@intel.com \
--cc=sfr@canb.auug.org.au \
/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
Powered by JetHome