Re: [irqdomain] 2cb09c90a4: suspend-stress.fail

[Marc Zyngier <maz@kernel.org>]

[-- Attachment #1: Type: text/plain, Size: 2451 bytes --]

Hi Oliver,

On Wed, 02 Jun 2021 08:12:31 +0100,
kernel test robot <oliver.sang@intel.com> wrote:
> 
> Greeting,
> 
> FYI, we noticed the following commit (built with gcc-9):
> 
> commit: 2cb09c90a4cde464dbfe78a57a9c128625c31122 ("irqdomain: Introduce irq_resolve_mapping()")
> https://git.kernel.org/cgit/linux/kernel/git/maz/arm-platforms.git irq/generic_handle_irq_domain
> 
> 
> in testcase: suspend-stress
> version: 
> with following parameters:
> 
> 	mode: mem
> 	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>
> 
> test started
> <--- but cannot finish. in attached dmesg.log
> [   56.989808] SUSPEND RESUME TEST STARTED
> 
> [   56.994723] Suspend to mem 1/10:
> 
> [   57.393914] /usr/bin/wget -q --timeout=1800 --tries=1 --local-encoding=UTF-8 http://internal-lkp-server:80/~lkp/cgi-bin/lkp-jobfile-append-var?job_file=/lkp/jobs/scheduled/lkp-ivb-toshiba1/suspend-stress-10-mem-debian-x86_64-20180403.cgz-2cb09c90a4cde464dbfe78a57a9c128625c31122-20210601-8940-10ohbtw-21.yaml&job_state=suspending-1/10 -O /dev/null
> 
> [   57.402918] Done
> 
> [   57.408029] Sleep for 10 seconds
> 
> [   57.413073] Suspend to mem 2/10:
> 
> [   57.417905] network not ready
> 
> [   57.422647] network not ready
> 
> [   57.427328] network not ready
> 
> [   57.431923] network not ready
> 
> [   57.436467] network not ready
> 
> [   57.440953] network not ready
> 
> [   57.445380] network not ready
> 
> [   57.449680] network not ready
> 
> [   57.453960] network not ready
> 
> [   58.066532] network not ready
> 
> [   59.069490] network not ready
> 
> [   60.072399] network not ready
> 
> [   61.075285] network not ready
> 
> [   62.078110] network not ready
> 
> [   62.899660] e1000e 0000:00:19.0 eth0: NIC Link is Up 100 Mbps Full Duplex, Flow Control: None

Can you give a few more details about the failure mode? Did you expect
the network interface to show up earlier? How repeatable is this
issue? Does it show up on any other platform?

It may take me some time to find similar HW, so any help pinpointing
the issue is most welcome.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.