From: Neftin, Sasha <sasha.neftin@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [e1000e] e86e383f28: suspend-stress.fail
Date: Thu, 2 Jul 2020 18:09:07 +0300 [thread overview]
Message-ID: <a3b1bca5-9270-df74-0c18-b7bcf37062a1@intel.com> (raw)
In-Reply-To: <6d83291fc68d52ecf48a952ac49a98e798b7b8b7.camel@intel.com>
On 7/2/2020 17:10, Zhang Rui wrote:
> On Thu, 2020-07-02 at 21:12 +0800, Kai-Heng Feng wrote:
>>> On Jul 2, 2020, at 20:20, Zhang Rui <rui.zhang@intel.com> wrote:
>>>
>>> Hi, all,
>>>
>>> This patch has been shipped in 5.8-rc1 with its upstream commit id
>>> 0c80cdbf3320. And we observed big drop of suspend quality.
>>>
>>> Previously, we have run into this "e1000e Hardware Error" issue,
>>> occasionally. But now, on a NUC I have, system suspend-to-mem fails
>>> within 10 suspend cycles in most cases, but won't work again until
>>> a reboot.
>>> https://bugzilla.kernel.org/show_bug.cgi?id=205015
>>>
>>> IMO, this is a regression, and we need to find a way to fix it.
>>
>> Should be fixed by
>> https://lore.kernel.org/lkml/20200618065453.12140-1-aaron.ma at canonical.com/
>>
>
> Great, I will give it a try and update later.
Rui,
Does ME/CSME AMT run on your machine?
Thanks,
sasha
>
> thanks,
> rui
>
>> Kai-Heng
>>
>>>
>>> thanks,
>>> rui
>>>
>>>
>>> On Sat, 2020-05-23 at 20:20 +0800, Kai-Heng Feng wrote:
>>>> [+Cc intel-wired-lan]
>>>>
>>>>> On May 21, 2020, at 13:27, kernel test robot <
>>>>> rong.a.chen at intel.com
>>>>>> wrote:
>>>>>
>>>>> Greeting,
>>>>>
>>>>> FYI, we noticed the following commit (built with gcc-7):
>>>>>
>>>>> commit: e86e383f2854234129c66e90f84ac2c74b2b1828 ("e1000e: Warn
>>>>> if
>>>>> disabling ULP failed")
>>>>>
>>>
>>>
> https://git.kernel.org/cgit/linux/kernel/git/jkirsher/next-queue.git
>>>>> dev-queue
>>>>
>>>> kern :warn : [ 240.884667] e1000e 0000:00:19.0 eth0: Failed to
>>>> disable ULP
>>>> kern :info : [ 241.896122] asix 2-3:1.0 eth1: link up,
>>>> 100Mbps,
>>>> full-duplex, lpa 0xC1E1
>>>> kern :err : [ 242.269348] e1000e 0000:00:19.0 eth0: Hardware
>>>> Error
>>>> kern :info : [ 242.772702] e1000e 0000:00:19.0:
>>>> pci_pm_resume+0x0/0x80 returned 0 after 2985422 usecs
>>>>
>>>> So the patch does catch issues previously ignored.
>>>>
>>>> I wonder what's the next move, maybe increase the ULP timeout
>>>> again?
>>>>
>>>> Kai-Heng
>>>>
>>>>> in testcase: suspend-stress
>>>>> with following parameters:
>>>>>
>>>>> mode: mem
>>>>> iterations: 10
>>>>>
>>>>>
>>>>>
>>>>> on test machine: 4 threads Broadwell with 8G memory
>>>>>
>>>>> caused below changes (please refer to attached dmesg/kmsg for
>>>>> entire log/backtrace):
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> If you fix the issue, kindly add following tag
>>>>> Reported-by: kernel test robot <rong.a.chen@intel.com>
>>>>>
>>>>> SUSPEND RESUME TEST STARTED
>>>>> Suspend to mem 1/10:
>>>>> /usr/bin/wget -q --timeout=1800 --tries=1 --local-encoding=UTF-
>>>>> 8
>>>>>
> http://inn:80/~lkp/cgi-bin/lkp-jobfile-append-var?job_file=/lkp/jobs/scheduled/lkp-bdw-nuc1/suspend-stress-10-mem-debian-x86_64-20180403.cgz-e86e383f2854234129c66e90f84ac2c74b2b1828-20200517-66267-13fgkna-8.yaml&job_state=suspending-1/10
>>>>> -O /dev/null
>>>>> Done
>>>>> Sleep for 10 seconds
>>>>> Suspend to mem 2/10:
>>>>> /usr/bin/wget -q --timeout=1800 --tries=1 --local-encoding=UTF-
>>>>> 8
>>>>>
> http://inn:80/~lkp/cgi-bin/lkp-jobfile-append-var?job_file=/lkp/jobs/scheduled/lkp-bdw-nuc1/suspend-stress-10-mem-debian-x86_64-20180403.cgz-e86e383f2854234129c66e90f84ac2c74b2b1828-20200517-66267-13fgkna-8.yaml&job_state=suspending-2/10
>>>>> -O /dev/null
>>>>> Done
>>>>> Sleep for 10 seconds
>>>>> Suspend to mem 3/10:
>>>>> /usr/bin/wget -q --timeout=1800 --tries=1 --local-encoding=UTF-
>>>>> 8
>>>>>
> http://inn:80/~lkp/cgi-bin/lkp-jobfile-append-var?job_file=/lkp/jobs/scheduled/lkp-bdw-nuc1/suspend-stress-10-mem-debian-x86_64-20180403.cgz-e86e383f2854234129c66e90f84ac2c74b2b1828-20200517-66267-13fgkna-8.yaml&job_state=suspending-3/10
>>>>> -O /dev/null
>>>>> Done
>>>>> Sleep for 10 seconds
>>>>> Suspend to mem 4/10:
>>>>> /usr/bin/wget -q --timeout=1800 --tries=1 --local-encoding=UTF-
>>>>> 8
>>>>>
> http://inn:80/~lkp/cgi-bin/lkp-jobfile-append-var?job_file=/lkp/jobs/scheduled/lkp-bdw-nuc1/suspend-stress-10-mem-debian-x86_64-20180403.cgz-e86e383f2854234129c66e90f84ac2c74b2b1828-20200517-66267-13fgkna-8.yaml&job_state=suspending-4/10
>>>>> -O /dev/null
>>>>> Done
>>>>> Sleep for 10 seconds
>>>>> Suspend to mem 5/10:
>>>>> /usr/bin/wget -q --timeout=1800 --tries=1 --local-encoding=UTF-
>>>>> 8
>>>>>
> http://inn:80/~lkp/cgi-bin/lkp-jobfile-append-var?job_file=/lkp/jobs/scheduled/lkp-bdw-nuc1/suspend-stress-10-mem-debian-x86_64-20180403.cgz-e86e383f2854234129c66e90f84ac2c74b2b1828-20200517-66267-13fgkna-8.yaml&job_state=suspending-5/10
>>>>> -O /dev/null
>>>>> Done
>>>>> Sleep for 10 seconds
>>>>> Suspend to mem 6/10:
>>>>> /usr/bin/wget -q --timeout=1800 --tries=1 --local-encoding=UTF-
>>>>> 8
>>>>>
> http://inn:80/~lkp/cgi-bin/lkp-jobfile-append-var?job_file=/lkp/jobs/scheduled/lkp-bdw-nuc1/suspend-stress-10-mem-debian-x86_64-20180403.cgz-e86e383f2854234129c66e90f84ac2c74b2b1828-20200517-66267-13fgkna-8.yaml&job_state=suspending-6/10
>>>>> -O /dev/null
>>>>> Failed
>>>>>
>>>>>
>>>>>
>>>>> To reproduce:
>>>>>
>>>>> git clone https://github.com/intel/lkp-tests.git
>>>>> cd lkp-tests
>>>>> bin/lkp install job.yaml # job file is attached in this
>>>>> email
>>>>> bin/lkp run job.yaml
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Rong Chen
>>>>>
>>>>> <config-5.7.0-rc4-01618-ge86e383f28542><job-
>>>>> script.txt><kmsg.xz><suspend-stress.txt><job.yaml>
>>>>
>>>>
>>
>>
>
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan at osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
>
next prev parent reply other threads:[~2020-07-02 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200521052753.GB12456@shao2-debian>
2020-05-23 12:20 ` [Intel-wired-lan] [e1000e] e86e383f28: suspend-stress.fail Kai-Heng Feng
2020-05-25 5:41 ` Neftin, Sasha
2020-05-26 9:49 ` Kai-Heng Feng
2020-07-02 12:20 ` Zhang Rui
2020-07-02 13:12 ` Kai-Heng Feng
2020-07-02 14:10 ` Zhang Rui
2020-07-02 15:09 ` Neftin, Sasha [this message]
2020-07-02 15:13 ` Zhang Rui
2020-07-07 12:50 ` Zhang Rui
2020-07-09 3:28 ` Zhang Rui
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=a3b1bca5-9270-df74-0c18-b7bcf37062a1@intel.com \
--to=sasha.neftin@intel.com \
--cc=intel-wired-lan@osuosl.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