From: Jakub Kicinski <kuba@kernel.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: Willy Tarreau <w@1wt.eu>, Heiner Kallweit <hkallweit1@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Florian Fainelli <f.fainelli@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, lkp@lists.01.org, lkp@intel.com,
rui.zhang@intel.com, yu.c.chen@intel.com
Subject: Re: [net] 6922110d15: suspend-stress.fail
Date: Tue, 7 Jun 2022 17:47:30 -0700 [thread overview]
Message-ID: <20220607174730.018fe58e@kernel.org> (raw)
In-Reply-To: <20220605143935.GA27576@xsang-OptiPlex-9020>
On Sun, 5 Jun 2022 22:39:35 +0800 kernel test robot wrote:
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-11):
>
> commit: 6922110d152e56d7569616b45a1f02876cf3eb9f ("net: linkwatch: fix failure to restore device state across suspend/resume")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> in testcase: suspend-stress
> version:
> with following parameters:
>
> mode: freeze
> iterations: 10
>
>
>
> on test machine: 4 threads Ivy Bridge with 4G 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 <oliver.sang@intel.com>
>
>
> Suspend to freeze 1/10:
> Done
> Suspend to freeze 2/10:
> network not ready
> network not ready
> network not ready
> network not ready
> network not ready
> network not ready
> network not ready
> network not ready
> network not ready
> network not ready
> network not ready
> Done
What's the failure? I'm looking at this script:
https://github.com/intel/lkp-tests/blob/master/tests/suspend-stress
And it seems that we are not actually hitting any "exit 1" paths here.
next prev parent reply other threads:[~2022-06-08 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 14:39 [net] 6922110d15: suspend-stress.fail kernel test robot
2022-06-08 0:47 ` Jakub Kicinski [this message]
2022-06-08 5:45 ` Willy Tarreau
2022-06-09 5:48 ` 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=20220607174730.018fe58e@kernel.org \
--to=kuba@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=geert+renesas@glider.be \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=netdev@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=rui.zhang@intel.com \
--cc=w@1wt.eu \
--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 NNTP newsgroup(s).