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 S1752314AbdBMIGt (ORCPT <rfc822;w@1wt.eu>);
        Mon, 13 Feb 2017 03:06:49 -0500
Received: from cn.fujitsu.com ([59.151.112.132]:51776 "EHLO
        heian.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org
        with ESMTP id S1752224AbdBMIGr (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 13 Feb 2017 03:06:47 -0500
X-IronPort-AV: E=Sophos;i="5.22,518,1449504000"; 
   d="scan'208";a="15529591"
Subject: Re: [lkp] [x86/acpi] dc6db24d24: BUG: unable to handle kernel paging
 request at 0000116007090008
To: Ye Xiaolong <xiaolong.ye@intel.com>
References: <20161020011604.GC17837@yexl-desktop>
 <5c5880ae-02a8-9f27-a47d-77aa5b3841b6@cn.fujitsu.com>
 <20161021030210.GH24319@yexl-desktop>
 <402c35ce-aca6-4b66-ecfd-2bcb7a4767b3@cn.fujitsu.com>
 <20161118061622.GD2684@yexl-desktop>
 <46cd9d61-229f-9452-80ae-b9b42f2672cb@cn.fujitsu.com>
 <20161121013110.GA591@yexl-desktop>
 <97e44a89-e527-5100-31b1-44cf1b0aea57@cn.fujitsu.com>
 <20170213013708.GI16630@yexl-desktop>
 <0188ea2f-f2a1-bfb0-5733-8c84abc3acac@cn.fujitsu.com>
 <20170213060505.GH28502@yexl-desktop>
CC: <guzheng1@huawei.com>, Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@kernel.org>, "Li, Philip" <philip.li@intel.com>,
        <lkp@01.org>, LKML <linux-kernel@vger.kernel.org>
From: Dou Liyang <douly.fnst@cn.fujitsu.com>
Message-ID: <3bf9ad5e-5903-0f52-cdad-908626348689@cn.fujitsu.com>
Date: Mon, 13 Feb 2017 16:06:38 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <20170213060505.GH28502@yexl-desktop>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.167.226.106]
X-yoursite-MailScanner-ID: 0910C477AE6E.AD8CF
X-yoursite-MailScanner: Found to be clean
X-yoursite-MailScanner-From: douly.fnst@cn.fujitsu.com
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Xiaolong

[...]
>>>
>>> Sorry for my neglect, the result for fd74da217df7d4bd25e95411da showed no dmesg
>>> because it's incomplete run and has no demsg stat at all.
>>
>> Is that means:
>>
>> you have already tested the Linux branch which contains the commit
>> fd74da217df7d. and it doesn't work well.
>>
>> Btw, Why the test is incomplete run ?
>
> Yes, We've got plenty test results for kernel that contains fd74da217df7d such as v4.9,
> v4.10-rc1, v4.10-rc2...., they all have the same dmesg errors.

Understood! :)

> For the incomplete run, it may happen sometimes due to kernel panic during boot time and
> 0day failed to capture its dmesg stat.
>
>>
>>> The bug still persists in v4.9, v4.10-rcx, the lastest kernel head,
>>
>> If the dmesg and stat of the test is NULL, How do you prove that the
>> bug still exists?
>
> This "dmesg stat is empty" refer to test for kernel image which head commit is fd74da217df7d,
> not for all test results.
>
>>
>>> could you help to check?
>>>
>>
>> Yes, I think we first should make the test with commit fd74da217df7d
>> work in the specific test machine.
>>
>> test machine: 72 threads Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
>> with 128G memory
>>
>> Am I right? waiting your response.
>
> Yes, currently we just found this issue on a specific machine, and I've queued the
> same jobs to other machines to see whether they have the same issue.
>

I will investigate it.


[...]

Thanks,
Liyang.