Bug 1929907 - IdeaPad 5 15ARE05 WiFi often does not work after resuming from standby
Summary: IdeaPad 5 15ARE05 WiFi often does not work after resuming from standby
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-17 21:40 UTC by rugk
Modified: 2021-11-30 18:02 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-30 18:02:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journalctl --no-hostname -k -b -1 (177.77 KB, text/plain)
2021-02-17 21:40 UTC, rugk
no flags Details

Description rugk 2021-02-17 21:40:46 UTC
Created attachment 1757661 [details]
journalctl --no-hostname -k -b -1

1. Please describe the problem:
If I resume from standby/suspend on my device I often find that it shown it as if it had no WiFi. The GNOME line for the wifi is empty or… in the past it had also flickered (appeared and disappeared).

2. What is the Version-Release number of the kernel:
Linux *** 5.10.14-200.fc33.x86_64 #1 SMP Sun Feb 7 19:59:31 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Device: IdeaPad 5 15ARE05 AMD CPU
Fedora Silverblue 33

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
Yes, it's an old issue. It happens at least since AUg 2020, see:
https://discussion.fedoraproject.org/t/ideapad-5-15are05-with-amd-cpu-gpu-problems/20446/2?u=rugk

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Usually yes.

1. Put your device into standy.
2. Wake it up.

A few kernel versions ago, I could fix that by putting the device into standby and waking it up again. I maybe had to repeat this process, but afterwards it worked.

Currently it seems only a full reboot solves this problem.

Bluetooth connection always works fine.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
not tested

6. Are you running any modules that not shipped with directly Fedora's kernel?:
no

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
done

Comment 1 Ben Cotton 2021-11-04 16:03:55 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2021-11-30 18:02:16 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.