From: kernel test robot <oliver.sang@intel.com>
To: Vitaly Lifshits <vitaly.lifshits@intel.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Dima Ruinskiy <dima.ruinskiy@intel.com>,
Naama Meir <naamax.meir@linux.intel.com>,
<intel-wired-lan@lists.osuosl.org>, <rui.zhang@intel.com>,
<yu.c.chen@intel.com>, <oliver.sang@inte.com>
Subject: [linus:master] [e1000e] 861e808602: suspend-stress.fail
Date: Wed, 15 May 2024 09:50:31 +0800 [thread overview]
Message-ID: <202405150942.f9b873b1-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "suspend-stress.fail" on:
commit: 861e8086029e003305750b4126ecd6617465f5c7 ("e1000e: move force SMBUS from enable ulp function to avoid PHY loss issue")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master a7c840ba5fa78d7761b9fedc33d69cef44986d79]
[test failed on linux-next/master 6ba6c795dc73c22ce2c86006f17c4aa802db2a60]
in testcase: suspend-stress
version:
with following parameters:
mode: freeze
iterations: 10
compiler: gcc-13
test machine: 4 threads (Broadwell) with 8G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202405150942.f9b873b1-oliver.sang@intel.com
test started
<--- but cannot really run suspend-stress tests successfully
as a contrast, for parent, we always noticed the jobs run smoothly
SUSPEND RESUME TEST STARTED
Suspend to freeze 1/10:
/usr/bin/wget -q --timeout=3600 --tries=1 --local-encoding=UTF-8 http://internal-lkp-server:80/~lkp/cgi-bin/lkp-jobfile-append-var?job_file=/lkp/jobs/scheduled/lkp-bdw-nuc1/suspend-stress-10-freeze-debian-x86_64-20180403.cgz-6dbdd4de0362-20240406-63993-p7cw6d-0.yaml&job_state=suspending-1/10 -O /dev/null
Done
Sleep for 10 seconds
...
Suspend to freeze 10/10:
/usr/bin/wget -q --timeout=3600 --tries=1 --local-encoding=UTF-8 http://internal-lkp-server:80/~lkp/cgi-bin/lkp-jobfile-append-var?job_file=/lkp/jobs/scheduled/lkp-bdw-nuc1/suspend-stress-10-freeze-debian-x86_64-20180403.cgz-6dbdd4de0362-20240406-63993-p7cw6d-0.yaml&job_state=suspending-10/10 -O /dev/null
Done
Sleep for 10 seconds
SUSPEND RESUME TEST SUCCESS
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240515/202405150942.f9b873b1-oliver.sang@intel.com
if you need more information, please let us know. Thanks!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-05-15 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 1:50 kernel test robot [this message]
2024-05-15 4:57 ` [Intel-wired-lan] [linus:master] [e1000e] 861e808602: suspend-stress.fail (e1000e: move force SMBUS from enable ulp function to avoid PHY loss issue) Paul Menzel
2024-05-15 9:29 ` Zhang, Rui
2024-05-17 5:50 ` Paul Menzel
2024-05-20 1:47 ` Zhang, Rui
2024-05-17 5:55 ` 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=202405150942.f9b873b1-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=dima.ruinskiy@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=naamax.meir@linux.intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@inte.com \
--cc=rui.zhang@intel.com \
--cc=vitaly.lifshits@intel.com \
--cc=yu.c.chen@intel.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).