** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1944409
Title:
Systemd uses CPU after wakeup due to
Upgrading to BIOS 1.13.3 on Latitude 3520 seems to have solved the issue.
Thanks for the help.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1944409
Title:
Systemd uses
** Changed in: oem-priority
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1944409
Title:
Systemd uses CPU after wakeup due to
Good. I woke up the laptop after leaving it hooked to the docking and in
sleep the whole night, no issues.
I consider it resolved. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
For Latitude 7520, BIOS 1.7.1 should fix this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1944409
Title:
Systemd uses CPU after wakeup due to power_supply BAT0
The issue is first found on other platform during enablement, and the
fix is landed in BIOS. Latitude 7520 has no problem with the BIOS
version we certified, however, the regression should be caused by BIOS
upgrade. Therefore, I assume the latest BIOS should contain fix for it.
As I know, the
After first reboot with BIOS 1.12.2 all seems fine, the update seems
even to have made the process of hooking up the docking station and
activating the external monitors faster.
After first sleep and wakeup, no battery pinging that I can see with
udevadm monitor, not even at a slow pace (but the
#7 output was already attached there, just grepped for brevity. The
first lines where confusing me though, I've now upgraded the system BIOS
from 1.6.1 to 1.12.2. 1.13 seems available on the official site, I'll
report back ASAP on the results of the upgrade.
--
You received this bug notification
reply #5
Can you try $ fwupdmgr get-updates to see if you can see the latest
firmware in LVFS? or attach your output here.
Also, you can always get latest BIOS here
https://www.dell.com/support/home/en-in/product-
support/product/latitude-15-7520-laptop/drivers, sometimes it is newer
than BIOS
The difference between your and my setup is that I do not use a docking station.
Maybe worth a try if this also happens without it.
Upstream bug has been reported here:
https://github.com/systemd/systemd/issues/21751
Also, I have a BIOS update that just came out so will install it right now and
I don't have any BIOS update available; as I said, my laptop (Dell
Latitude 7520) is fully updated.
$ sudo dmidecode -s bios-version
1.6.1
$ fwupdmgr get-updates | grep "Current version" -B2
Devices with no available firmware updates:
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI dbx
Could you try updating the BIOS firmware, and see whether this issue is
still reproducible?
I cannot observe the issue with BIOS firmware version 1.13.0 with
docking station DA310.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: oem-priority
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1944409
Title:
Systemd uses CPU after wakeup due to
No, no workaround. I still have to do the restart at every reboot with
the docking station attached.
My system is fully updated up to yesterday:
$ uname -a
Linux CLIFMI085 5.13.0-1021-oem #25-Ubuntu SMP Thu Dec 2 18:03:51 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug
I experience the same issue on a Dell Latitude 3520.
It is Manjaro and systemd version is 249 but the issue/solution is exactly the
same.
Did you find any permanent solution to the problem?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Tags added: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1944409
Title:
Systemd uses CPU after wakeup due to power_supply BAT0 (battery)
continued
** Tags added: fossa-squirtle
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1944409
Title:
18 matches
Mail list logo
