[regression] igc does not function anymore after second resume from standby

[regression] igc does not function anymore after second resume from standby

[Linux regression tracking (Thorsten Leemhuis)]

[Tony, Przemek: lore did not find any mail from Sasha in the past few
weeks, so from here it looks like this might be something somebody else
needs to handle.]

Hi, Thorsten here, the Linux kernel's regression tracker.

Sasha, I noticed a report about a regression in bugzilla.kernel.org that
appears to be caused by this change of yours:
6f31d6b643a32c ("igc: Refactor runtime power management flow") [v6.10-rc1]

As many (most?) kernel developers don't keep an eye on the bug tracker,
I decided to write this mail. To quote from
https://bugzilla.kernel.org/show_bug.cgi?id=219143 :

>  Martin 2024-08-09 15:17:49 UTC
> 
> Starting with Kernel 6.10.x I experienced network connection
> problems after resuming my system for the second time.
> 
> My system contains two Intel I225-V (rev2 and rev3) cards.
> 
> I ran a bisection and got a hit: 6f31d6b643a32cc126cf86093fca1ea575948bf0
> 
> rmmod igc ; modprobe igc remedies the issue till the next but one resume.

See the ticket for more details. Martin, the reporter, is CCed.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

#regzbot duplicate: https://bugzilla.kernel.org/show_bug.cgi?id=219143
#regzbot from: Martin

Re: [regression] igc does not function anymore after second resume from standby

[Tony Nguyen]

On 8/14/2024 3:42 AM, Linux regression tracking (Thorsten Leemhuis) wrote:
> [Tony, Przemek: lore did not find any mail from Sasha in the past few
> weeks, so from here it looks like this might be something somebody else
> needs to handle.]

Adding a couple of others who are involved in the driver.

Thanks,
Tony

> Hi, Thorsten here, the Linux kernel's regression tracker.
> 
> Sasha, I noticed a report about a regression in bugzilla.kernel.org that
> appears to be caused by this change of yours:
> 6f31d6b643a32c ("igc: Refactor runtime power management flow") [v6.10-rc1]
> 
> As many (most?) kernel developers don't keep an eye on the bug tracker,
> I decided to write this mail. To quote from
> https://bugzilla.kernel.org/show_bug.cgi?id=219143 :
> 
>>   Martin 2024-08-09 15:17:49 UTC
>>
>> Starting with Kernel 6.10.x I experienced network connection
>> problems after resuming my system for the second time.
>>
>> My system contains two Intel I225-V (rev2 and rev3) cards.
>>
>> I ran a bisection and got a hit: 6f31d6b643a32cc126cf86093fca1ea575948bf0
>>
>> rmmod igc ; modprobe igc remedies the issue till the next but one resume.
> 
> See the ticket for more details. Martin, the reporter, is CCed.
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
> 
> #regzbot duplicate: https://bugzilla.kernel.org/show_bug.cgi?id=219143
> #regzbot from: Martin