linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: "Ye, Xiaolong" <xiaolong.ye@intel.com>
Cc: Tony Luck <tony.luck@gmail.com>,
	"Huang, Ying" <ying.huang@intel.com>,
	"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
	Tomasz Nowicki <tomasz.nowicki@linaro.org>,
	"Chen, Gong" <gong.chen@linux.intel.com>,
	Jonathan Zhang <zjzhang@codeaurora.org>,
	Fu Wei <fu.wei@linaro.org>,
	"Tyler Baicar" <tbaicar@codeaurora.org>,
	Borislav Petkov <bp@suse.de>, LKML <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"lkp@01.org" <lkp@01.org>
Subject: Re: [lkp] [ACPI / APEI]  a3e2acc5e3: kmsg.BERT:Can't_request_iomem_region<#-#>
Date: Tue, 12 Jul 2016 01:21:26 +0000	[thread overview]
Message-ID: <E9EB2E0F-5635-4550-9761-FD3910828E3C@intel.com> (raw)
In-Reply-To: <20160712005201.GE19249@yexl-desktop>

Get BIOS version with:

# dmidecode   -t  0

Sent from my iPhone

> On Jul 11, 2016, at 17:54, Ye, Xiaolong <xiaolong.ye@intel.com> wrote:
> 
>> On Sun, Jul 10, 2016 at 08:28:37PM -0700, Tony Luck wrote:
>> I'm very surprised that there was a BERT table on an Atom machine. More details about the machine please. Also BIOS version.
> 
> Hi, ying
> 
> Could you tell me what's BERT table? and how to check the BIOS version?
> 
> Thanks,
> Xiaolong
> 
>> 
>> Sent from my iPhone
>> 
>>> On Jul 10, 2016, at 18:43, kernel test robot <xiaolong.ye@intel.com> wrote:
>>> 
>>> 
>>> FYI, we noticed the following commit:
>>> 
>>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>>> commit a3e2acc5e37b22b6808a0b8e46887c3577de9c9e ("ACPI / APEI: Add Boot Error Record Table (BERT) support")
>>> 
>>> in testcase: locktorture
>>> with following parameters: runtime=300s
>>> 
>>> on test machine: Atom with 8G memory
>>> 
>>> caused below changes:
>>> 
>>> 
>>> [   12.317148] BERT: Can't request iomem region <00000000bfccfc18-00000000bfccfc2b>.
>>> 
>>> 
>>> 
>>> To reproduce:
>>> 
>>>       git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
>>>       cd lkp-tests
>>>       bin/lkp install job.yaml  # job file is attached in this email
>>>       bin/lkp run     job.yaml
>>> 
>>> 
>>> 
>>> Thanks,
>>> Xiaolong
>>> <config-4.7.0-rc4-00003-ga3e2acc>
>>> <kmsg.xz>
>>> <job.yaml>

  reply	other threads:[~2016-07-12  1:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11  1:43 [lkp] [ACPI / APEI] a3e2acc5e3: kmsg.BERT:Can't_request_iomem_region<#-#> kernel test robot
2016-07-11  3:28 ` Tony Luck
2016-07-12  0:52   ` Ye Xiaolong
2016-07-12  1:21     ` Luck, Tony [this message]
2016-07-12  5:48       ` Ye Xiaolong

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=E9EB2E0F-5635-4550-9761-FD3910828E3C@intel.com \
    --to=tony.luck@intel.com \
    --cc=bp@suse.de \
    --cc=fu.wei@linaro.org \
    --cc=gong.chen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tbaicar@codeaurora.org \
    --cc=tomasz.nowicki@linaro.org \
    --cc=tony.luck@gmail.com \
    --cc=xiaolong.ye@intel.com \
    --cc=ying.huang@intel.com \
    --cc=zjzhang@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).