[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d61678f-7494-4c26-a039-f5db633ab140@molgen.mpg.de>
Date: Thu, 30 May 2024 09:55:32 +0200
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: En-Wei WU <en-wei.wu@...onical.com>
Cc: jesse.brandeburg@...el.com, intel-wired-lan@...ts.osuosl.org,
rickywu0421@...il.com, linux-kernel@...r.kernel.org, edumazet@...gle.com,
anthony.l.nguyen@...el.com, netdev@...r.kernel.org, kuba@...nel.org,
pabeni@...hat.com, davem@...emloft.net, wojciech.drewek@...el.com
Subject: Re: [Intel-wired-lan] [PATCH] ice: irdma hardware init failed after
suspend/resume
Dear En-Wei,
Thank you for your quick reply.
Am 30.05.24 um 09:08 schrieb En-Wei WU:
>> Sorry for being unclear. I meant, does resuming the system take longer
>> now? (initcall_debug might give a clue.)
> I've tested the S3 suspend/resume with the initcall_debug kernel
> command option, and it shows no clear difference between having or not
> having the ice_init_rdma in ice_resume:
> Without ice_init_rdma:
> ```
> [ 104.241129] ice 0000:86:00.0: PM: pci_pm_resume+0x0/0x110 returned 0 after 9415 usecs
> [ 104.241206] ice 0000:86:00.1: PM: pci_pm_resume+0x0/0x110 returned 0 after 9443 usecs
> ```
> With ice_init_rdma:
> ```
> [ 122.749022] ice 0000:86:00.1: PM: pci_pm_resume+0x0/0x110 returned 0 after 9485 usecs
> [ 122.749068] ice 0000:86:00.0: PM: pci_pm_resume+0x0/0x110 returned 0 after 9532 usecs
> ```
Thank you for verifying this. Nice to hear, it has no impact.
[…]
Kind regards,
Paul
Powered by blists - more mailing lists