Hi, this is your Linux kernel regression tracker. I noticed a regression report in bugzilla.kernel.org that afaics nobody acted upon since it was reported. That's why I decided to forward it by mail to those that afaics should handle this. To quote from https://bugzilla.kernel.org/show_bug.cgi?id=216386 : > Utkarsh Verma 2022-08-20 09:16:41 UTC > > I have an ASUS TUF FX505DT which has the RTL8822BE wifi card. I recently upgraded to kernel 5.19 and this issue started popping up. > > When I close my laptop lid and let it sleep for a considerable amount of time, the wifi stops working the next time I open it, and I have to reboot my PC to get internet. This is annoying because I suspended my PC to continue with my work after some time quickly, and having to reboot defeats the purpose. > > I tried removing and reloading the kernel module for this device as well, and it fails with the following dmesg log. > > ``` > [ 4914.877037] rtw_8822be 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible > [ 4914.886333] rtw_8822be 0000:04:00.0: mac power on failed > [ 4914.886342] rtw_8822be 0000:04:00.0: failed to power on mac > [ 4914.886344] rtw_8822be 0000:04:00.0: failed to setup chip efuse info > [ 4914.886348] rtw_8822be 0000:04:00.0: failed to setup chip information > [ 4914.892027] rtw_8822be 0000:04:00.0: Firmware version 27.2.0, H2C version 13 > [ 4914.922150] rtw_8822be: probe of 0000:04:00.0 failed with error -114 > ``` See the ticket for details and further comments. Please look into the issue if you're among the main recipients of this mail (and not just CCed). I hope I picked the right people to sent this to, if not just let everyone know. Anyway, to ensure this is not forgotten lets get this tracked by the the Linux kernel regression tracking bot: #regzbot introduced: https://bugzilla.kernel.org/show_bug.cgi?id=216386 #regzbot ignore-activity This isn't a regression? This issue or a fix for it are already discussed somewhere else? It was fixed already? You want to clarify when the regression started to happen? Or point out I got the title or something else totally wrong? Then just reply -- ideally with also telling regzbot about it, as explained here: https://linux-regtracking.leemhuis.info/tracked-regression/ Reminder for developers: When fixing the issue, add 'Link:' tags pointing to the report in bugzilla, as the kernel's documentation calls for; above page explains why this is important for tracked regressions. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) P.S.: As the Linux kernel's regression tracker I deal with a lot of reports and sometimes miss something important when writing mails like this. If that's the case here, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.
