On May 25, 2020, at 13:41, Neftin, Sasha
<sasha.neftin(a)intel.com> wrote:
On 5/23/2020 15:20, Kai-Heng Feng wrote:
> [+Cc intel-wired-lan]
>> On May 21, 2020, at 13:27, kernel test robot <rong.a.chen(a)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, you can't simple increase ULP timeout. Why ME required more time? We need
to find ME expert and understand why FWSM (firmware semaphore, bit 10 ULP_CFG_DN)
indication take too much time. I wonder if this indication work as properly. Please, try
to understand. All delay/timeout approach not acceptable.
Sorry if I caused any confusion, just want to point out this bug dates back to Broadwell
systems:
kern :info : [ 0.000000] DMI: /NUC5i3RYB, BIOS RYBDWi35.86A.0363.2017.0316.1028
03/16/2017
And NUC5i3RYB doesn't seem to have ME:
https://www.intel.com/content/dam/support/us/en/documents/mini-pcs/nuc-ki...
Unfortunately I don't have any Broadwell system around, so I wonder if Intel Ethernet
folks have access to the affected system...
Kai-Heng
Also, we communicated: : Intel vPro (vPro CPU + Corporate ME FW) system (i.e. I219LM
system) is NOT POR to support Linux
> 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(a)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/sche...
-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/sche...
-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/sche...
-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/sche...
-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/sche...
-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/sche...
-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(a)osuosl.org
>
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan