This bug is awaiting verification that the linux-azure/6.2.0-1009.9
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug was fixed in the package linux - 6.2.0-23.23
---
linux (6.2.0-23.23) lunar; urgency=medium
* lunar/linux: 6.2.0-23.23 -proposed tracker (LP: #2019845)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.19.0-45.46
---
linux (5.19.0-45.46) kinetic; urgency=medium
* kinetic/linux: 5.19.0-45.46 -proposed tracker (LP: #2023057)
* Kinetic update: upstream stable patchset 2023-05-23 (LP: #2020599)
- wifi: cfg80211: Partial revert "wifi:
Hi Jared you can follow the release of all of the Jammy cloud kernel
here https://kernel.ubuntu.com/sru/dashboards/web/kernel-stable-
board.html , where this fix is included in the 2023.05.15 cycle. They
should be released to updates in the next week.
- Luke
--
You received this bug
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1014.14 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still
Hey Andrea,
Thanks for the help getting this all fixed up. I see that the change is
committed for Lunar and Kinetic.
Is there a good way for me to follow when this'll land for the Ubuntu
Jammy linux-aws, linux-gcp, and linux-azure packages?
--
You received this bug notification because you
This bug is awaiting verification that the linux/5.19.0-44.45 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu Lunar)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
[Impact]
Commit f382fb0bcef4 ("block: remove legacy IO schedulers") introduced a
behavior change in the blkio throttle cgroup subsystem: IO statistics
are not reported anymore unless a throttling rule is explicitly defined,
because the current code only counts
** Description changed:
+ [Impact]
+
+ Commit f382fb0bcef4 ("block: remove legacy IO schedulers") introduced a
+ behavior change in the blkio throttle cgroup subsystem: IO statistics
+ are not reported anymore unless a throttling rule is explicitly defined,
+ because the current code only counts
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-aws (Ubuntu)
** No longer affects: linux-azure (Ubuntu)
** No longer affects: linux-gcp (Ubuntu)
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also
Potential upstream fix:
https://lore.kernel.org/lkml/20230401094708.77631-1-hanjinke@bytedance.com/
However this seems to partially restore the old behavior of cgroup v1,
because we still need to set io throttling limits in order to get the io
statistics.
We may need an additional fix like
I've updated this to report the issue for linux-azure and linux-gcp as
their jammy-updates repo's have recently updated to kernel 5.19 and
appear to be affected as well. I could use some guidance on reporting
this upstream as 5.19 doesn't seem to be a supported kernel version
(looking
It might be worth to report this also upstream, apparently there was a
behavior change with the blkio controller in cgroup1 that happend at
some point between 5.15 and 5.19. I'll do more tests and will let you
know if I find anything relevant. Thanks for reporting this!
--
You received this bug
A few clarifications from IRC:
1. We run all of our Ubuntu 22.04 LTS nodes with the kernel args
'systemd.unified_cgroup_hierarchy=0
systemd.legacy_systemd_cgroup_controller=true' to force cgroups v1 as,
unfortunately, we cannot safely turn on cgroups v2 yet (that's another pile of
work I want
17 matches
Mail list logo
