[Bug 2051672] Re: Backport iproute2 6.8.0 to noble
I have an update on this. I've talked with the LXD team during the engineering sprint in Madrid and at the moment we can't break ubuntu-fan or we could potentially break some running LXD installations. I asked the LXD team to start working as soon as possible to remove the support for this feature, that at this point is going happen in Oracular. Therefore, good job with the iproute2 sync in Oracular @dannf. Unfortunately in Noble we still need to wait for now and support ubuntu- fan... In the meantime I've sent an updated patch set to re-enable ubuntu-fan in the kernel (with a small redesign to prevent potential incompatibilities with the upstream vxlan_policy rules): https://lists.ubuntu.com/archives/kernel-team/2024-May/150684.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: Backport iproute2 6.8.0 to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056461] Re: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
** Description changed:
+ [Impact]
+
+ It seems that kernel 6.8 introduced a regression in the 9pfs related to
+ caching and netfslib, that can cause some user-space apps to read
+ content from files that is not up-to-date (when they are used in a
+ producer/consumer fashion).
+
+ It seems that the offending commit is this one:
+
+ 80105ed2fd27 ("9p: Use netfslib read/write_iter")
+
+ Reverting the commit seems to fix the problem. However the actual bug
+ might be in netfslib or how netfslib is used in the 9p context.
+
+ The regression has been reported upstream and we are still investigating
+ (https://lore.kernel.org/lkml/Zj0ErxVBE3DYT2Ea@gpd/).
+
+ In the meantime it probably makes sense to temporarily revert the commit
+ as a SAUCE patch. Then we will drop the SAUCE patch once we'll have a
+ proper fix upstream.
+
+ [Test case]
+
+ The following test should complete correctly without any timeout:
+
+ pull-lp-source -d hello
+ autopkgtest-buildvm-ubuntu-cloud -r noble
+ autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img
+
+
+ [Fix]
+
+ Revert the following commit (until we have a proper fix upstream):
+
+ 80105ed2fd27 ("9p: Use netfslib read/write_iter")
+
+ [Regression potential]
+
+ We may experience other regressions related to 9pfs with this change,
+ however it's quite unlikely to happen since we are reverting a commit,
+ restoring the previous behavior.
+
+ [Original bug report]
+
autopkgtest-virt-qemu sometimes hangs when running tests on noble
images. Originally reported by schopin, who also provided a reproducer:
- pull-lp-source -d hello
- autopkgtest-buildvm-ubuntu-cloud -r noble
- autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img
+ pull-lp-source -d hello
+ autopkgtest-buildvm-ubuntu-cloud -r noble
+ autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img
I've been able to reproduce it with debugging enabled:
- autopkgtest -ddd -U hello_2.10-3.dsc -- qemu --debug --show-boot
+ autopkgtest -ddd -U hello_2.10-3.dsc -- qemu --debug --show-boot
/path/to/image
It can get stuck during different stages, but AFAICT always during
"copydown" operations, log excerpts follow. It may be a coincidence, but
this started happening around the time linux-image-6.8.0-11-generic
(6.8.0-11.11) migrated to noble. The testbeds I used booted 6.6 but then
rebooted into that 6.8 kernel after being upgraded by autopkgtest.
-- logs --
Removing autopkgtest-satdep (0) ...
[...]
autopkgtest-virt-qemu: DBG: executing copydown
/tmp/autopkgtest.output.g8v75e8g/tests-tree/ /t/
autopkgtest-virt-qemu: DBG: ['cmdls', "(['tar', '--directory',
'/tmp/autopkgtest.output.g8v75e]
autopkgtest-virt-qemu: DBG: ['srcstdin', "<_io.BufferedReader
name='/dev/null'>", 'deststdout']
autopkgtest-virt-qemu: DBG: +< tar --directory
/tmp/autopkgtest.output.g8v75e8g/tests-tree/ --
autopkgtest-virt-qemu: DBG: +> /tmp/autopkgtest-qemu.ztmr6f5k/runcmd sh -ec
if ! test -d /tmp-
autopkgtest-virt-qemu: DBG: +>?
-- or --
autopkgtest: DBG: sending command to testbed: copydown
/tmp/autopkgtest.output.c9utq3bx/tests-tree/
/tmp/autopkgtest.H8NDfW/build.DLR/src/
autopkgtest-virt-qemu: DBG: executing copydown
/tmp/autopkgtest.output.c9utq3bx/tests-tree/
/tmp/autopkgtest.H8NDfW/build.DLR/src/
autopkgtest-virt-qemu: DBG: ['cmdls', "(['tar', '--directory',
'/tmp/autopkgtest.output.c9utq3bx/tests-tree/', '--warning=none', '-c', '.',
'-f', '-'], ['/tmp/autopkgtest-qemu.qtkcgg5l/runcm]
autopkgtest-virt-qemu: DBG: ['srcstdin', "<_io.BufferedReader
name='/dev/null'>", 'deststdout', "<_io.BufferedReader name='/dev/null'>",
'devnull_read', <_io.BufferedReader name='/dev/null'>]
autopkgtest-virt-qemu: DBG: +< tar --directory
/tmp/autopkgtest.output.c9utq3bx/tests-tree/ --warning=none -c . -f -
autopkgtest-virt-qemu: DBG: +> /tmp/autopkgtest-qemu.qtkcgg5l/runcmd sh -ec
if ! test -d /tmp/autopkgtest.H8NDfW/build.DLR/src/; then mkdir --
/tmp/autopkgtest.H8NDfW/build.DLR/src/; fi; cd-
autopkgtest-virt-qemu: DBG: +>?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056461
Title:
autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056461] Re: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
I've uploaded a test kernel here:
https://people.canonical.com/~arighi/lp2056461/amd64/
With this one I can't reproduce the problem. It'd be great if someone
else could test it as well, to confirm that it's actually fixing the
problem.
Note: this kernel is a 6.8.0-32.32 with this commit reverted:
commit 80105ed2fd27 ("9p: Use netfslib read/write_iter")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056461
Title:
autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056461] Re: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
I've done some bisecting and it looks like the culprit is this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80105ed2fd2715fb09a8fdb0655a8bdc86c120db I'll prepare a test kernel with this one reverted, then if it's confirmed, we can figure out a proper fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056461 Title: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065005] [NEW] ThinkPad P16s fails to resume from suspend sometimes [6.8]
Public bug reported: On a ThinkPad P16s running Noble, resuming from suspend fails about 10% of the time. This usually leads to a reboot, and more rarely to a hang that requires forcing a power off. I don't recall this being the case with kernel 6.5 in Mantic. How to reproduce: * suspend the laptop (systemctl suspend, via the Gnome GUI, closing the lid, method doesn't matter) * resume * repeat about 10 times A quick look at kernel logs doesn't show any kernel panic so perhaps the issue happens too early in the resume process for dmesg to be updated. This happens on both (at least) 6.8.0-31 and 6.8.0-28. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:aieri 4787 F pipewire /dev/snd/controlC0: aieri 4793 F wireplumber /dev/snd/controlC1: aieri 4793 F wireplumber CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 7 08:54:34 2024 MachineType: LENOVO 21K9001NUS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=zfs:zroot/ROOT/ubuntu quiet loglevel=4 rtc_cmos.use_acpi_alarm=1 spl.spl_hostid=0x4605c990 RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-14 (22 days ago) dmi.bios.date: 02/20/2024 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET55W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K9001NUS dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrR2FET55W(1.35):bd02/20/2024:br1.35:efr1.16:svnLENOVO:pn21K9001NUS:pvrThinkPadP16sGen2:rvnLENOVO:rn21K9001NUS:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K9_BU_Think_FM_ThinkPadP16sGen2: dmi.product.family: ThinkPad P16s Gen 2 dmi.product.name: 21K9001NUS dmi.product.sku: LENOVO_MT_21K9_BU_Think_FM_ThinkPad P16s Gen 2 dmi.product.version: ThinkPad P16s Gen 2 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065005 Title: ThinkPad P16s fails to resume from suspend sometimes [6.8] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058830] Re: vp9 hw decode broken on modern AMD apus, needs amdgpu update
Sadly I've updated this morning to Ubuntu 24.04 noble. I have a snapshot taken before upgrading that I can eventually clone. But I've never tried booting from another dataset so I'm not 100% confident. I can also try using this proposed firmware in noble. Or maybe we can wait for someone that still run on jammy to do the testing. Let me know what you think. I think I might have some free time this week. By the way I've been running since the end of March until yesterday with the firmware from upstream downloaded iirc on the 19/03/24. Those solved the issue for sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058830 Title: vp9 hw decode broken on modern AMD apus, needs amdgpu update To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/2058830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058830] Re: vp9 hw decode broken on modern AMD apus, needs amdgpu update
For anyone still on 22.04 and 23.10 beware: the recent apt upgrade of the linux-firmware package does not contains any update to the amdgpu vcn firmware from upstream. So, if you updated, you have to re-copy the ones from upstream (see workaround section above). In my case the dmese reported VCN version reverted to: `[2.889013] [drm] Found VCN firmware Version ENC: 1.19 DEC: 7 VEP: 0 Revision: 0 ` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058830 Title: vp9 hw decode broken on modern AMD apus, needs amdgpu update To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/2058830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064508] Re: re-enable Ubuntu FAN in the Noble kernel
Test result with the patch set applied (ubuntu_fan_smoke_test): 11:48:05 INFO | Writing results to /home/ubuntu/autotest/client/results/default 11:48:05 INFO | START timestamp=1714564085localtime=May 01 11:48:05 11:48:05 INFO | START ubuntu_fan_smoke_test.setup ubuntu_fan_smoke_test.setup timeout=1200timestamp=1714564085 localtime=May 01 11:48:05 11:48:07 INFO | GOODubuntu_fan_smoke_test.setup ubuntu_fan_smoke_test.setup timestamp=1714564087localtime=May 01 11:48:07 completed successfully 11:48:07 INFO | END GOODubuntu_fan_smoke_test.setup ubuntu_fan_smoke_test.setup timestamp=1714564087localtime=May 01 11:48:07 11:48:07 INFO | START ubuntu_fan_smoke_test.fan-smoke-test ubuntu_fan_smoke_test.fan-smoke-testtimeout=1800timestamp=1714564087 localtime=May 01 11:48:07 11:51:46 INFO | Testing Fan Networking (pre-0.13.0 API) 11:51:46 INFO | docker pull --platform linux/amd64 ubuntu: PASSED 11:51:46 INFO | enable disable fan test: PASSED 11:51:46 INFO | fanctl show test: PASSED 11:51:46 INFO | fanctl check bridge config test: PASSED 11:51:46 INFO | fanatic docker test(--dns=192.168.122.1): PASSED 11:51:47 INFO | GOODubuntu_fan_smoke_test.fan-smoke-test ubuntu_fan_smoke_test.fan-smoke-testtimestamp=1714564307localtime=May 01 11:51:47 completed successfully 11:51:47 INFO | END GOODubuntu_fan_smoke_test.fan-smoke-test ubuntu_fan_smoke_test.fan-smoke-testtimestamp=1714564307localtime=May 01 11:51:47 11:51:47 INFO | END GOODtimestamp=1714564307 localtime=May 01 11:51:47 11:51:47 INFO | Report successfully generated at /home/ubuntu/autotest/client/results/default/job_report.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064508 Title: re-enable Ubuntu FAN in the Noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064508] Re: re-enable Ubuntu FAN in the Noble kernel
Patch set to re-enable Ubuntu FAN in the 6.8 Noble kernel: https://lists.ubuntu.com/archives/kernel-team/2024-May/150684.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064508 Title: re-enable Ubuntu FAN in the Noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064508] [NEW] re-enable Ubuntu FAN in the Noble kernel
Public bug reported: [Impact] In LP: #2063298, we have opted to deprecate Ubuntu FAN support because of the maintenance overhead and the possibility of regressions / conflicts with the new networking eBPF APIs in kernels >= 6.8. However, we cannot disable this feature in HWE/backport kernels, so it seems safer to adjust the Ubuntu FAN kernel patch set to ensure proper co-existence with the updated vxlan policy requirements in newer 6.8 kernels. The re-introduction of Ubuntu FAN should be considered as a temporary measure, aimed at facilitating a smooth transition during its deprecation without disrupting existing users (specifically Juju), and enabling the backporting of 6.8 kernels to older releases. The main plan is still to deprecate Ubuntu FAN in newer releases. [Test case] Rely on the specific Ubuntu FAN regression test to validate the proper kernel support of this feature: https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client- tests/tree/ubuntu_fan_smoke_test?h=autotest3 [Fix] Re-apply the Ubuntu FAN patch set to the latest Noble kernel 6.8 and integrate the IFLA_VXLAN_FAN_MAP attribute type in vxlan_policy to satisfy the strict length validation check. [Regression potential] We may experience regressions with eBPF vxlan capabilities and potentially specific use cases of the Ubuntu FAN technology (Juju installations). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064508 Title: re-enable Ubuntu FAN in the Noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: Backport iproute2 6.8.0 to noble
Thanks @dannf for updating the bug! The SRU description looks good to me and everything seems reasonable, same with the plan. I'll keep monitoring this tracker and we'll proceed once oracular will be open. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: Backport iproute2 6.8.0 to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045503] Re: provide a sched-ext enabled kernel for the 24.10 release
** Summary changed: - apply sched-ext patch set to linux-unstable + provide a sched-ext enabled kernel for the 24.10 release ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Noble) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045503 Title: provide a sched-ext enabled kernel for the 24.10 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
Hello, any progress on this? Now that ubuntu-fan is officially deprecated in Noble can we simply sync iproute2 with Debian? Is there any pending activity / requirement that are preventing this? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063965] Re: package sgml-base 1.31 failed to install/upgrade: Local modifications to /etc/pam.d/common-* triggered dpkg error
** Changed in: sgml-base (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063965 Title: package sgml-base 1.31 failed to install/upgrade: Local modifications to /etc/pam.d/common-* triggered dpkg error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/2063965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063965] Re: package sgml-base 1.31 failed to install/upgrade: Local modifications to /etc/pam.d/common-* triggered dpkg error
** Attachment removed: "Df.txt" https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/2063965/+attachment/5771676/+files/Df.txt ** Attachment removed: "Dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/2063965/+attachment/5771677/+files/Dmesg.txt ** Attachment removed: "DpkgHistoryLog.txt" https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/2063965/+attachment/5771678/+files/DpkgHistoryLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063965 Title: package sgml-base 1.31 failed to install/upgrade: Local modifications to /etc/pam.d/common-* triggered dpkg error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/2063965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063965] [NEW] package sgml-base 1.31 failed to install/upgrade: Local modifications to /etc/pam.d/common-* triggered dpkg error
Public bug reported: Summary: Running `sudo apt install libpam-mount` I get ``` pam-auth-update: Local modifications to /etc/pam.d/common-*, not updating. pam-auth-update: Run pam-auth-update --force to override. Setting up libpam-mount-bin (2.19-1) ... Processing triggers for libc-bin (2.38-1ubuntu6.2) ... Processing triggers for man-db (2.11.2-3) ... Errors were encountered while processing: sgml-base E: Sub-process /usr/bin/dpkg returned an error code (1) ``` Plus apport-gtk pop-up My `/etc/pam.d/common-authentication` is modified. 1) Release ```$ lsb_release -r Release:23.10 ``` 2) Package version ```$ apt-cache policy sgml-base libpam-mount sgml-base: Installed: 1.31 Candidate: 1.31 Version table: *** 1.31 500 500 http://it.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu mantic/main i386 Packages 100 /var/lib/dpkg/status 1.30 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu jammy/main i386 Packages libpam-mount: Installed: 2.19-1 Candidate: 2.19-1 Version table: *** 2.19-1 500 500 http://it.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status 2.18-2build2 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ``` 3) What is expected Usually in this situation I get a dpkg prompt saying something like "package maintainer provided a different configuration file" and asking me which version of the configuration file. Or to see the differences. Some file are then saved and `NAME.dpkg-new`/`NAME.dpkg-old`. This way I can install the module and care about editing `/etc/pam.d/common-auth` later. 4) What happened See error above ProblemType: Package DistroRelease: Ubuntu 23.10 Package: sgml-base 1.31 ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 AptOrdering: libhx32:amd64: Install libpam-mount:amd64: Install libpam-mount-bin:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Apr 27 20:54:15 2024 ErrorMessage: il sottoprocesso installato pacchetto sgml-base script post-installation ha restituito lo stato di errore 2 InstallationDate: Installed on 2023-04-23 (370 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1.1 apt 2.7.3ubuntu0.1 SourcePackage: sgml-base Title: package sgml-base 1.31 failed to install/upgrade: il sottoprocesso installato pacchetto sgml-base script post-installation ha restituito lo stato di errore 2 UpgradeStatus: Upgraded to mantic on 2023-10-20 (190 days ago) ** Affects: sgml-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063965 Title: package sgml-base 1.31 failed to install/upgrade: Local modifications to /etc/pam.d/common-* triggered dpkg error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/2063965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058752] Re: ath11k high jitter and packet loss when operating in 802.11ax mode
unfortunately the problem is not actually gone in noble. I have upgraded to the beta and are having significant but intermittent problems. On 6.8.0-31-generic I get periods of normal traffic mixed with 100% packet loss for some seconds. This looks as follows: 64 bytes from 192.168.16.77: icmp_seq=2622 ttl=64 time=2.47 ms 64 bytes from 192.168.16.77: icmp_seq=2623 ttl=64 time=2.80 ms 64 bytes from 192.168.16.77: icmp_seq=2624 ttl=64 time=2.77 ms From 192.168.16.231 icmp_seq=2637 Destination Host Unreachable From 192.168.16.231 icmp_seq=2638 Destination Host Unreachable From 192.168.16.231 icmp_seq=2639 Destination Host Unreachable From 192.168.16.231 icmp_seq=2640 Destination Host Unreachable From 192.168.16.231 icmp_seq=2644 Destination Host Unreachable From 192.168.16.231 icmp_seq=2645 Destination Host Unreachable 64 bytes from 192.168.16.77: icmp_seq=2646 ttl=64 time=162 ms 64 bytes from 192.168.16.77: icmp_seq=2647 ttl=64 time=1.95 ms 64 bytes from 192.168.16.77: icmp_seq=2648 ttl=64 time=44.3 ms 64 bytes from 192.168.16.77: icmp_seq=2649 ttl=64 time=143 ms 64 bytes from 192.168.16.77: icmp_seq=2650 ttl=64 time=2.37 ms 64 bytes from 192.168.16.77: icmp_seq=2651 ttl=64 time=151 ms 64 bytes from 192.168.16.77: icmp_seq=2652 ttl=64 time=2.69 ms 64 bytes from 192.168.16.77: icmp_seq=2653 ttl=64 time=6.66 ms 64 bytes from 192.168.16.77: icmp_seq=2654 ttl=64 time=47.2 ms 64 bytes from 192.168.16.77: icmp_seq=2655 ttl=64 time=40.1 ms 64 bytes from 192.168.16.77: icmp_seq=2656 ttl=64 time=44.9 ms 64 bytes from 192.168.16.77: icmp_seq=2657 ttl=64 time=1583 ms 64 bytes from 192.168.16.77: icmp_seq=2658 ttl=64 time=560 ms 64 bytes from 192.168.16.77: icmp_seq=2659 ttl=64 time=1506 ms 64 bytes from 192.168.16.77: icmp_seq=2660 ttl=64 time=457 ms 64 bytes from 192.168.16.77: icmp_seq=2661 ttl=64 time=809 ms 64 bytes from 192.168.16.77: icmp_seq=2662 ttl=64 time=3014 ms 64 bytes from 192.168.16.77: icmp_seq=2663 ttl=64 time=2005 ms 64 bytes from 192.168.16.77: icmp_seq=2664 ttl=64 time=982 ms 64 bytes from 192.168.16.77: icmp_seq=2665 ttl=64 time=2.47 ms 64 bytes from 192.168.16.77: icmp_seq=2666 ttl=64 time=2471 ms 64 bytes from 192.168.16.77: icmp_seq=2667 ttl=64 time=1464 ms 64 bytes from 192.168.16.77: icmp_seq=2668 ttl=64 time=440 ms 64 bytes from 192.168.16.77: icmp_seq=2669 ttl=64 time=54.2 ms 64 bytes from 192.168.16.77: icmp_seq=2670 ttl=64 time=2.35 ms If I find some time I'll try rerunning the same test from windows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058752 Title: ath11k high jitter and packet loss when operating in 802.11ax mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063298] [NEW] deprecate ubuntu-fan in Noble
Public bug reported: [Impact] In order to provide ubuntu-fan we need to maintain additional kernel SAUCE patches that are currently conflicting with upstream code, potentially breaking networking eBPF APIs. To prevent such incompatibility the whole patch set requires a major redesign. However, after investigations and a detailed assessment we have not found any relevant real-world use-case that still requuires ubuntu-fan, as most of its features are now available in the upstream kernel and user-space tools, using alternative solutions. Moreover, maintaining ubuntu-fan is also slowing down / preventing the development of other packages (see for example LP: #2051672). Therefore, we are proposing to deprecate ubuntu-fan starting with noble. [Test case] We have ubuntu-fan test cases in our regression testing suite. Such tests are expected to fail with the noble kernel, so we can hint/disable them in Noble. [Fix] Drop (do not apply) the ubuntu-fan SAUCE patch set from the Ubuntu kernel. [Regression potential] There are still some existing tools/systems that may still rely on ubuntu-fan, so we may experience regressions when such systems are moving to noble. However, the potential of breaking eBPF networking has a much higher impact, so we can probably workaround any potential ubuntu-fan regression using alternative upstream solutions. ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Affects: iproute2 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: iproute2 (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063298 Title: deprecate ubuntu-fan in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2063298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
According to the information that I collected (asking around, investigating, etc.), it seems that there are no critical users of ubuntu-fan. Moreover, considering the impact of the ubuntu-fan kernel patches (that would require a major refactoring to avoid breaking the network eBPF ABI), we decided to proceed with the plan to deprecate this feature in all the noble kernels. Therefore, all the user-space components that rely on such feature can follow the same plan and drop their corresponding ubuntu-fan support (iproute2 included). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061727] Re: bpfcc-tools autotest failure when multiple linux-tools- packages are installed
Test plan:
- without this change:
/usr/lib/linux-tools-6.8.0-22/bpftool /usr/lib/linux-tools-6.8.0-25/bpftool gen
skeleton /tmp/bpfcc-0.29.1+ds/libbpf-tools/.output/bashreadline.bpf.o >
/tmp/bpfcc-0.29.1+ds/libbpf-tools/.output/bashreadline.skel.h
Usage: bpftool [OPTIONS] OBJECT { COMMAND | help }
bpftool batch file FILE
bpftool version
OBJECT := { prog | map | link | cgroup | perf | net | feature | btf |
gen | struct_ops | iter }
OPTIONS := { {-j|--json} [{-p|--pretty}] | {-d|--debug} |
{-V|--version} }
make[2]: *** [Makefile:192:
/tmp/bpfcc-0.29.1+ds/libbpf-tools/.output/bashreadline.skel.h] Error 255
make[2]: *** Deleting file
'/tmp/bpfcc-0.29.1+ds/libbpf-tools/.output/bashreadline.skel.h'
make[2]: Leaving directory '/tmp/bpfcc-0.29.1+ds/libbpf-tools'
- with this change applied:
100% tests passed, 0 tests failed out of 37
Total Test time (real) = 83.22 sec
make: Leaving directory '/tmp/autopkgtest.MOnsj0/tree/obj-x86_64-linux-gnu'
autopkgtest [06:43:12]: test command1: ---]
autopkgtest [06:43:12]: test command1: - - - - - - - - - - results - - - - - -
- - - -
command1 PASS
autopkgtest [06:43:12]: summary
command1 PASS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061727
Title:
bpfcc-tools autotest failure when multiple linux-tools-
packages are installed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2061727/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061727] Re: bpfcc-tools autotest failure when multiple linux-tools- packages are installed
debdiff in attach allows to run the autopkgtest correctly also with multiple kernels installed. ** Patch added: "bpfcc-tools-fix-autopkgtest.debdiff" https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2061727/+attachment/5766017/+files/bpfcc-tools-fix-autopkgtest.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061727 Title: bpfcc-tools autotest failure when multiple linux-tools- packages are installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2061727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061727] [NEW] bpfcc-tools autotest failure when multiple linux-tools- packages are installed
Public bug reported:
[Impact]
The autopkgtest for bpfcc-tools fails with the following error when
multiple linux-tools packages (multiple kernels) are installed:
942s /usr/lib/linux-tools-6.8.0-22/bpftool
/usr/lib/linux-tools-6.8.0-25/bpftool gen skeleton
/tmp/autopkgtest.2W4dxr/build.Uhs/src/libbpf-tools/.output/bashreadline.bpf.o >
/tmp/autopkgtest.2W4dxr/build.Uhs/src/libbpf-tools/.output/bashreadline.skel.h
942s Usage: bpftool [OPTIONS] OBJECT { COMMAND | help }
942sbpftool batch file FILE
942sbpftool version
942s
942sOBJECT := { prog | map | link | cgroup | perf | net | feature | btf
| gen | struct_ops | iter }
942sOPTIONS := { {-j|--json} [{-p|--pretty}] | {-d|--debug} |
942s {-V|--version} }
942s make[2]: *** [Makefile:192:
/tmp/autopkgtest.2W4dxr/build.Uhs/src/libbpf-tools/.output/bashreadline.skel.h]
Error 255
942s make[2]: *** Deleting file
'/tmp/autopkgtest.2W4dxr/build.Uhs/src/libbpf-tools/.output/bashreadline.skel.h'
942s make[2]: Leaving directory
'/tmp/autopkgtest.2W4dxr/build.Uhs/src/libbpf-tools'
942s make[1]: *** [debian/rules:44: override_dh_auto_install] Error 2
942s make[1]: Leaving directory '/tmp/autopkgtest.2W4dxr/build.Uhs/src'
The reason is that in debian/rules we evaluate BPFTOOL assuming that
only one kernel is installed, but we may have multiple kernels
(therefore multiple linux-tools-) installed.
[Test case]
Install multiple linux-tools- and run the bpfcc-tools
autopkgtest.
[Fix]
Evaluate BPFTOOL in debian/rules only taking the last bpftool listed in
/usr/lib/linux-tools-*/bpftool.
[Regression potential]
This change affects only the autopkgtest and it allows to run the test
correctly also when multiple kernels are installed, no regresssion is
expected.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: bpfcc-tools 0.29.1+ds-1ubuntu6
ProcVersionSignature: User Name 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20240413
CloudSubPlatform: config-disk (/dev/vdb)
Date: Tue Apr 16 05:38:06 2024
PackageArchitecture: all
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: bpfcc
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: bpfcc (Ubuntu)
Importance: Undecided
Status: New
** Affects: bpfcc (Ubuntu Noble)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cloud-image noble
** Also affects: bpfcc (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061727
Title:
bpfcc-tools autotest failure when multiple linux-tools-
packages are installed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2061727/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: displaycal 3.9.11-2 fails to start in noble, needs python 3.11
It's also worth noting that displaycal-py3 does not support python 3.12 yet. See for example https://github.com/eoyilmaz/displaycal- py3/issues/335#issuecomment-2016761349 ** Bug watch added: github.com/eoyilmaz/displaycal-py3/issues #335 https://github.com/eoyilmaz/displaycal-py3/issues/335 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: displaycal 3.9.11-2 fails to start in noble, needs python 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] [NEW] displaycal 3.9.11-2 fails to start in noble, needs python 3.11
Public bug reported: I have upgraded to the noble beta today, and displaycal fails to start. The package dependencies request python 3.12, but the actual software needs 3.11 (or older). ``` $ apt show displaycal | grep Depends WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Depends: libc6 (>= 2.34), libx11-6, libxinerama1 (>= 2:1.1.4), libxrandr2 (>= 2:1.2.0), libxxf86vm1, python3 (<< 3.13), python3 (>= 3.12~), python3-build, python3-certifi, python3-dbus, python3-distro, python3-numpy, python3-pil, python3-pychromecast, python3-send2trash, python3-wxgtk4.0, python3-zeroconf, python3:any, dbus-x11, argyll, libjs-jquery, python3-gi, libsdl2-mixer-2.0-0 $ displaycal --help Traceback (most recent call last): File "/usr/bin/displaycal", line 4, in from DisplayCAL.main import main File "/usr/lib/python3/dist-packages/DisplayCAL/main.py", line 27, in raise RuntimeError( RuntimeError: Need Python version >= 3.8 <= 3.11, got 3.12.2 ``` ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: displaycal 3.9.11-2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 15:16:10 2024 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: displaycal-py3 UpgradeStatus: Upgraded to noble on 2024-04-14 (0 days ago) mtime.conffile..etc.xdg.autostart.z-displaycal-apply-profiles.desktop: 2023-10-22T21:28:16.420795 ** Affects: displaycal-py3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: displaycal 3.9.11-2 fails to start in noble, needs python 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060909] Re: Apply mitigations for the native BHI hardware vulnerabilty
** Description changed:
[Impact]
Branch History Injection (BHI) attacks may allow a malicious application
to influence indirect branch prediction in kernel by poisoning the
branch history. eIBRS isolates indirect branch targets in ring0.
The BHB can still influence the choice of indirect branch predictor
entry, and although branch predictor entries are isolated between modes
when eIBRS is enabled, the BHB itself is not isolated between modes.
Previously the only known real-world BHB attack vector was via
unprivileged eBPF. Further research has found attacks that don't require
unprivileged eBPF.
See also:
https://www.phoronix.com/news/Linux-BHI-Branch-History-Inject
[Test case]
https://www.vusec.net/projects/native-bhi/
[Fix]
Backport from upstream the merge that introduces spectre_bhi= boot
option to control BHI mitigation:
2bb69f5fc721 ("Merge tag 'nativebhi' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
ed2e8d49b54d ("KVM: x86: Add BHI_NO")
95a6ccbdc719 ("x86/bhi: Mitigate KVM by default")
ec9404e40e8f ("x86/bhi: Add BHI mitigation knob")
be482ff95009 ("x86/bhi: Enumerate Branch History Injection (BHI) bug")
0f4a837615ff ("x86/bhi: Define SPEC_CTRL_BHI_DIS_S")
7390db8aea0d ("x86/bhi: Add support for clearing branch history at syscall
entry")
1e3ad78334a6 ("x86/syscall: Don't force use of indirect calls for system
calls")
0cd01ac5dcb1 ("x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs
file")
Also set spectre_bhi=auto by default, that will rely on the BHI_DIS_S
hardware control if it's available on the system CPUs, otherwise a
- proper software sequence will be deployed at VMexit.
+ proper software sequence will be executed at VMexit.
+
+ NOTE: we may get these changes via stable update in 6.8, when that
+ happens we can drop this backport and apply the patch set like any other
+ regular stable update.
[Regression potential]
We may experience performance regressions with this new mitigation
enabled, especially in VMs and CPUs that don't have the BHI hardware
support capability (due to the extra software sequence executed at
VMexit).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060909
Title:
Apply mitigations for the native BHI hardware vulnerabilty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060909/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060909] Re: Apply mitigations for the native BHI hardware vulnerabilty
** Summary changed: - Backport mitigations for the native BHI hardware vulnerabilty + Apply mitigations for the native BHI hardware vulnerabilty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060909 Title: Apply mitigations for the native BHI hardware vulnerabilty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060909] Re: Backport mitigations for the native BHI hardware vulnerabilty
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
** Description changed:
[Impact]
Branch History Injection (BHI) attacks may allow a malicious application
to influence indirect branch prediction in kernel by poisoning the
branch history. eIBRS isolates indirect branch targets in ring0.
The BHB can still influence the choice of indirect branch predictor
entry, and although branch predictor entries are isolated between modes
when eIBRS is enabled, the BHB itself is not isolated between modes.
Previously the only known real-world BHB attack vector was via
unprivileged eBPF. Further research has found attacks that don't require
unprivileged eBPF.
+ See also:
+ https://www.phoronix.com/news/Linux-BHI-Branch-History-Inject
+
[Test case]
https://www.vusec.net/projects/native-bhi/
[Fix]
Backport from upstream the merge that introduces spectre_bhi= boot
option to control BHI mitigation:
- 2bb69f5fc721 ("Merge tag 'nativebhi' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
- ed2e8d49b54d ("KVM: x86: Add BHI_NO")
- 95a6ccbdc719 ("x86/bhi: Mitigate KVM by default")
- ec9404e40e8f ("x86/bhi: Add BHI mitigation knob")
- be482ff95009 ("x86/bhi: Enumerate Branch History Injection (BHI) bug")
- 0f4a837615ff ("x86/bhi: Define SPEC_CTRL_BHI_DIS_S")
- 7390db8aea0d ("x86/bhi: Add support for clearing branch history at syscall
entry")
- 1e3ad78334a6 ("x86/syscall: Don't force use of indirect calls for system
calls")
- 0cd01ac5dcb1 ("x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs
file")
+ 2bb69f5fc721 ("Merge tag 'nativebhi' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
+ ed2e8d49b54d ("KVM: x86: Add BHI_NO")
+ 95a6ccbdc719 ("x86/bhi: Mitigate KVM by default")
+ ec9404e40e8f ("x86/bhi: Add BHI mitigation knob")
+ be482ff95009 ("x86/bhi: Enumerate Branch History Injection (BHI) bug")
+ 0f4a837615ff ("x86/bhi: Define SPEC_CTRL_BHI_DIS_S")
+ 7390db8aea0d ("x86/bhi: Add support for clearing branch history at syscall
entry")
+ 1e3ad78334a6 ("x86/syscall: Don't force use of indirect calls for system
calls")
+ 0cd01ac5dcb1 ("x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs
file")
Also set spectre_bhi=auto by default, that will rely on the BHI_DIS_S
hardware control if it's available on the system CPUs, otherwise a
proper software sequence will be deployed at VMexit.
[Regression potential]
We may experience performance regressions with this new mitigation
enabled, especially in VMs and CPUs that don't have the BHI hardware
support capability (due to the extra software sequence executed at
VMexit).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060909
Title:
Backport mitigations for the native BHI hardware vulnerabilty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060909/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060909] [NEW] Backport mitigations for the native BHI hardware vulnerabilty
Public bug reported:
[Impact]
Branch History Injection (BHI) attacks may allow a malicious application
to influence indirect branch prediction in kernel by poisoning the
branch history. eIBRS isolates indirect branch targets in ring0.
The BHB can still influence the choice of indirect branch predictor
entry, and although branch predictor entries are isolated between modes
when eIBRS is enabled, the BHB itself is not isolated between modes.
Previously the only known real-world BHB attack vector was via
unprivileged eBPF. Further research has found attacks that don't require
unprivileged eBPF.
[Test case]
https://www.vusec.net/projects/native-bhi/
[Fix]
Backport from upstream the merge that introduces spectre_bhi= boot
option to control BHI mitigation:
2bb69f5fc721 ("Merge tag 'nativebhi' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
ed2e8d49b54d ("KVM: x86: Add BHI_NO")
95a6ccbdc719 ("x86/bhi: Mitigate KVM by default")
ec9404e40e8f ("x86/bhi: Add BHI mitigation knob")
be482ff95009 ("x86/bhi: Enumerate Branch History Injection (BHI) bug")
0f4a837615ff ("x86/bhi: Define SPEC_CTRL_BHI_DIS_S")
7390db8aea0d ("x86/bhi: Add support for clearing branch history at syscall
entry")
1e3ad78334a6 ("x86/syscall: Don't force use of indirect calls for system
calls")
0cd01ac5dcb1 ("x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs
file")
Also set spectre_bhi=auto by default, that will rely on the BHI_DIS_S
hardware control if it's available on the system CPUs, otherwise a
proper software sequence will be deployed at VMexit.
[Regression potential]
We may experience performance regressions with this new mitigation
enabled, especially in VMs and CPUs that don't have the BHI hardware
support capability (due to the extra software sequence executed at
VMexit).
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Affects: linux (Ubuntu Noble)
Importance: Undecided
Status: Fix Committed
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060909
Title:
Backport mitigations for the native BHI hardware vulnerabilty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060909/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055805] Re: touchpad not working with kernel 6.8
@tijs thanks for testing it! If 6.8.0-19 is working I assume that also the latest kernel in release (6.8.0-22.22) is also working. If that's the case I think we can close this for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055805 Title: touchpad not working with kernel 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058830] Re: vp9 hw decode broken on modern AMD apus, needs amdgpu update
Any news? Pulling firmware from upstream is enough to solve this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058830 Title: vp9 hw decode broken on modern AMD apus, needs amdgpu update To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/2058830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060130] Re: [SPR][EMR][GNR] TDX: efi: TD Measurement support for kernel cmdline/initrd sections from EFI stub
Applied all the listed commits to noble/linux, including also:
9c55461040a9 ("x86/efistub: Remap kernel text read-only before dropping
NX attribute")
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060130
Title:
[SPR][EMR][GNR] TDX: efi: TD Measurement support for kernel
cmdline/initrd sections from EFI stub
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060130/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059080] Re: Add Real-time Linux Analysis tool (rtla) to linux-tools
** Changed in: linux (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059080 Title: Add Real-time Linux Analysis tool (rtla) to linux-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059762] [NEW] CONFIG_INTEL_TDX_HOST conflicts with kexec in linux >= 6.8 for noble
Public bug reported:
[Impact]
CONFIG_INTEL_TDX_HOST depends on !KEXEC_CORE in the latest 6.8 kernel.
This was introduced by:
cb8eb06d50fc ("x86/virt/tdx: Disable TDX host support when kexec is
enabled")
We cannot regress kexec, therefore we need to disable
CONFIG_INTEL_TDX_HOST in the generic kernel, despite our attempt with
LP: #2046040.
[Fix]
Disable CONFIG_INTEL_TDX_HOST in the generic kernel, until upstream will
properly support this option with kexec.
[Regression potential]
The Intel host TDX feature won't be available in the generic kernel.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Affects: linux (Ubuntu Noble)
Importance: Undecided
Status: Fix Committed
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059762
Title:
CONFIG_INTEL_TDX_HOST conflicts with kexec in linux >= 6.8 for noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059762/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059237] Re: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot
If the issue is fixed without the extra patch, I think we can ignore it, it was probably a false positive from UBSAN. Let's keep an eye on it and if it shows up again in the future we can do a test with my additional patch. Thanks for update! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059237 Title: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2059237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046040] Re: enable CONFIG_INTEL_TDX_HOST in linux >= 6.7 for noble
Changing the state to Won't fix, because of LP: #2059762. ** Changed in: linux (Ubuntu Noble) Status: Fix Released => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046040 Title: enable CONFIG_INTEL_TDX_HOST in linux >= 6.7 for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059237] Re: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot
Looking at the code this issue seems to be introduced by `UBUNTU: SAUCE:
modpost: support arbitrary symbol length in modversion` and the UBSAN
warning tells us that accessing vers->name[0] could be an out-of-bounds
access.
The struct modversion_info contains a flexibile array (name), that is
correctly defined as the last member of the struct, and its size is
allocated dynamically at runtime, so I would expect that vars->name[0]
is always allocated, unless vars is not initialized properly or there's
an empty name.
So, my guess is that UBSAN isn't really happy about the flexible array
and this is just a false positive.
However, to be 100% sure that we are not actually doing and out-of-bound
access and prevent the warning, we could apply something like the
following on top of our SAUCE patch:
diff --git a/arch/powerpc/kernel/module_64.c b/arch/powerpc/kernel/module_64.c
index 195714fc6e22..1f5960e25758 100644
--- a/arch/powerpc/kernel/module_64.c
+++ b/arch/powerpc/kernel/module_64.c
@@ -350,6 +350,8 @@ static void dedotify_versions(struct modversion_info *vers,
struct modversion_info *end = (void *)vers + size;
for (; vers < end && vers->next; vers = (void *)vers + vers->next) {
+ if (size <= offsetof(struct modversion_info, name))
+ continue;
if (vers->name[0] == '.') {
memmove(vers->name, vers->name+1, strlen(vers->name));
}
In this case even if (for any reason) vars->name[] is an empty string we can
prevent the out-of-bound access and make UBSAN happy.
Opinions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059237
Title:
[Ubuntu-24.04] "array-index-out-of-bounds" error is observed after
every reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2059237/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059080] [NEW] Add Real-time Linux Analysis tool (rtla) to linux-tools
Public bug reported: [Impact] The **rtla** is a meta-tool that includes a set of commands that aims to analyze the real-time properties of Linux. Considering the latest "low-latency" capabilities acquired by the generic kernel and also considering the recent trend in Ubuntu to focus on performance and observability (see for example https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame- pointers-by-default), it makes sense to provide more tools that can help to analyze timing/responsive performance, such as rtla. [Test case] Simple rtla usage to measure the timer irq / timer thread latency: $ sudo rtla timerlat [Fix] Enable the build of the rtla binary during the kernel build and ship it with linux-tools. [Regression potential] The only potential regression is an increased amount of size in the linux-tools package, due to the extra binary. However, the binary itself is really small, the kernel already has all the required capabilities enabled and we don't need to introduce any additional user-space dependency, therefore such extra space is expected to be minimal. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059080 Title: Add Real-time Linux Analysis tool (rtla) to linux-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058830] Re: vp9 hw decode broken on modern AMD apus, needs amdgpu update
** Description changed: Current version of amdgpu binaries in linux-firmware shipped with ubuntu 22.04 (jammy) and ubuntu 23.10 (mantic) create various problems when decoding VP9 content with the iGPU on modern AMD mobile processor (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H processor). The issue has been reported and solved upstream: - https://gitlab.com/kernel-firmware/linux- - firmware/-/commit/977332782302476e1c863b09b840f463d0378807 + https://gitlab.freedesktop.org/mesa/mesa/-/issues/8044 + + [EDIT: fixed link] Solution dates to the end of February: https://gitlab.com/kernel- firmware/linux- firmware/-/commit/977332782302476e1c863b09b840f463d0378807 Ubuntu 24.04 already ships the updated binaries and should not be affected. Steps to reproduce: * on an affected system play a VP9 video with hardware decoding Additional links: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807 * https://bugzilla.redhat.com/show_bug.cgi?id=2267714 * https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9 Workaround: * download the amdgpu folder from upstream linux-firmware repos * compress each file with zstd * copy into /lib/firmware/amdgpu * regenerate the initrd I'm currently running ubuntu 23.10 (mantic) with binaries from upstream and the issue is solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058830 Title: vp9 hw decode broken on modern AMD apus, needs amdgpu update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2058830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058830] Re: vp9 hw decode broken on modern AMD apus, needs amdgpu update
** Summary changed: - vp9 hw decode broke on modern AMD apus, needs amdgpu update + vp9 hw decode broken on modern AMD apus, needs amdgpu update ** Description changed: - Current version of amdgpu in linux-firmware shipped with ubuntu 22.04 - (jammy) and ubuntu 23.10 (mantic) create various problems when decoding - VP9 content with the iGPU on modern AMD mobile processor (rembrant and - phoenix, i.e. 6xxxU/H, 7x40U/H and 7735U/H processor). + Current version of amdgpu binaries in linux-firmware shipped with ubuntu + 22.04 (jammy) and ubuntu 23.10 (mantic) create various problems when + decoding VP9 content with the iGPU on modern AMD mobile processor + (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7735U/H processor). The issue has been reported and solved upstream: https://gitlab.com/kernel-firmware/linux- firmware/-/commit/977332782302476e1c863b09b840f463d0378807 Solution dates to the end of February: https://gitlab.com/kernel- firmware/linux- firmware/-/commit/977332782302476e1c863b09b840f463d0378807 Ubuntu 24.04 already ships the updated binaries and should not be affected. Steps to reproduce: * on an affected system play a VP9 video with hardware decoding Additional links: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807 * https://bugzilla.redhat.com/show_bug.cgi?id=2267714 * https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9 Workaround: * download the amdgpu folder from upstream linux-firmware repos * compress each file with zstd * copy into /lib/firmware/amdgpu * regenerate the initrd I'm currently running ubuntu 23.10 (mantic) with binaries from upstream and the issue is solved. ** Description changed: Current version of amdgpu binaries in linux-firmware shipped with ubuntu 22.04 (jammy) and ubuntu 23.10 (mantic) create various problems when decoding VP9 content with the iGPU on modern AMD mobile processor - (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7735U/H processor). + (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H processor). The issue has been reported and solved upstream: https://gitlab.com/kernel-firmware/linux- firmware/-/commit/977332782302476e1c863b09b840f463d0378807 Solution dates to the end of February: https://gitlab.com/kernel- firmware/linux- firmware/-/commit/977332782302476e1c863b09b840f463d0378807 Ubuntu 24.04 already ships the updated binaries and should not be affected. Steps to reproduce: * on an affected system play a VP9 video with hardware decoding Additional links: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807 * https://bugzilla.redhat.com/show_bug.cgi?id=2267714 * https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9 Workaround: * download the amdgpu folder from upstream linux-firmware repos * compress each file with zstd * copy into /lib/firmware/amdgpu * regenerate the initrd I'm currently running ubuntu 23.10 (mantic) with binaries from upstream and the issue is solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058830 Title: vp9 hw decode broken on modern AMD apus, needs amdgpu update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2058830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058830] [NEW] vp9 hw decode broken on modern AMD apus, needs amdgpu update
Public bug reported: Current version of amdgpu binaries in linux-firmware shipped with ubuntu 22.04 (jammy) and ubuntu 23.10 (mantic) create various problems when decoding VP9 content with the iGPU on modern AMD mobile processor (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H processor). The issue has been reported and solved upstream: https://gitlab.com/kernel-firmware/linux- firmware/-/commit/977332782302476e1c863b09b840f463d0378807 Solution dates to the end of February: https://gitlab.com/kernel- firmware/linux- firmware/-/commit/977332782302476e1c863b09b840f463d0378807 Ubuntu 24.04 already ships the updated binaries and should not be affected. Steps to reproduce: * on an affected system play a VP9 video with hardware decoding Additional links: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807 * https://bugzilla.redhat.com/show_bug.cgi?id=2267714 * https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9 Workaround: * download the amdgpu folder from upstream linux-firmware repos * compress each file with zstd * copy into /lib/firmware/amdgpu * regenerate the initrd I'm currently running ubuntu 23.10 (mantic) with binaries from upstream and the issue is solved. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058830 Title: vp9 hw decode broken on modern AMD apus, needs amdgpu update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2058830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058752] Re: ath11k high jitter and packet loss when operating in 802.11ax mode
Well, that was a pleasant surprise! On 6.8.0-11 the problem seems to be completely gone. I guess I'll be upgrading to Noble as soon as possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058752 Title: ath11k high jitter and packet loss when operating in 802.11ax mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051560] Re: Provide python perf module
** Changed in: linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051560 Title: Provide python perf module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051560] Re: Provide python perf module
Patch sent to the kernel team mailing list for review: https://lists.ubuntu.com/archives/kernel-team/2024-March/149751.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051560 Title: Provide python perf module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058752] [NEW] ath11k high jitter and packet loss when operating in 802.11ax mode
Public bug reported:
On 6.5.0-26-generic, my QCNFA765 cannot really operate in 802.11ax mode.
I have a Thinkpad P16s Gen 2 with a (soldered, sadly) QCNFA765 card, which uses
the ath11k driver.
I also have a Ruckus R650 AP, which supports wifi6.
Connecting the two and pinging the AP yields the following:
```
64 bytes from 192.168.16.77: icmp_seq=45 ttl=64 time=22.4 ms
64 bytes from 192.168.16.77: icmp_seq=46 ttl=64 time=29.6 ms
64 bytes from 192.168.16.77: icmp_seq=47 ttl=64 time=26.8 ms
64 bytes from 192.168.16.77: icmp_seq=48 ttl=64 time=2174 ms
64 bytes from 192.168.16.77: icmp_seq=49 ttl=64 time=1158 ms
64 bytes from 192.168.16.77: icmp_seq=50 ttl=64 time=130 ms
64 bytes from 192.168.16.77: icmp_seq=51 ttl=64 time=503 ms
64 bytes from 192.168.16.77: icmp_seq=54 ttl=64 time=1832 ms
64 bytes from 192.168.16.77: icmp_seq=55 ttl=64 time=808 ms
64 bytes from 192.168.16.77: icmp_seq=56 ttl=64 time=9.32 ms
64 bytes from 192.168.16.77: icmp_seq=57 ttl=64 time=2.11 ms
64 bytes from 192.168.16.77: icmp_seq=58 ttl=64 time=25.6 ms
64 bytes from 192.168.16.77: icmp_seq=59 ttl=64 time=30.9 ms
64 bytes from 192.168.16.77: icmp_seq=60 ttl=64 time=95.6 ms
^C
--- 192.168.16.77 ping statistics ---
60 packets transmitted, 55 received, 8.3% packet loss, time 59273ms
rtt min/avg/max/mdev = 2.105/275.084/2344.792/560.334 ms, pipe 3
```
Those periodic bursts of >1s latency make some webpages fail to load and
videochats unusable.
No interference is present in my channel of choice.
Nothing interesting is printed in dmesg while the above occurs.
The above does not happen if:
* I disable wifi 6 in the AP
* I ping a wifi 5 AP (I also have an older R710, which is a 802.11ac AP)
* I ping the R650 in wifi 6 mode from a AX210 on kernel 6.2
* I ping the R650 from a completely different OS and device (e.g. Android)
I'll test with a 24.04 daily image next.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 21 16:58:07 2024
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: root=zfs:zroot/ROOT/ubuntu quiet loglevel=4
rtc_cmos.use_acpi_alarm=1 spl.spl_hostid=0x4605c990
RelatedPackageVersions:
linux-restricted-modules-6.5.0-26-generic N/A
linux-backports-modules-6.5.0-26-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/15/2024
dmi.bios.release: 1.18
dmi.bios.vendor: LENOVO
dmi.bios.version: R2FET38W (1.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21K9001NUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrR2FET38W(1.18):bd01/15/2024:br1.18:efr1.11:svnLENOVO:pn21K9001NUS:pvrThinkPadP16sGen2:rvnLENOVO:rn21K9001NUS:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K9_BU_Think_FM_ThinkPadP16sGen2:
dmi.product.family: ThinkPad P16s Gen 2
dmi.product.name: 21K9001NUS
dmi.product.sku: LENOVO_MT_21K9_BU_Think_FM_ThinkPad P16s Gen 2
dmi.product.version: ThinkPad P16s Gen 2
dmi.sys.vendor: LENOVO
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058752
Title:
ath11k high jitter and packet loss when operating in 802.11ax mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058752/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051560] Re: Provide python perf module
** Description changed: + [Impact] + + We need to provide the python perf module, because some applications + (such as tuned) require it. + + This module is implemented inside perf, provided by the kernel. + + At the moment we provide a distinct perf for each kernel installed in + the system. There is really no reason to do that, because perf is both + backward and forward compatible, but this is a different issue and we + are not going to solve it in this context and it will be addressed in a + separate bug. + + For now, to solve this specific issue, we need to enable the python + module when we build perf (as part of the kernel build) and ship the + library inside the linux-tools- package. + + However, this brings a new problem, because we need to install the + module in a standard python path (so that python applications can be + able to use it in a regular way), but we need to support multiple + installed versions and add some logic to transparently select the right + one when a generic user-space python application uses `import perf`. + + For this reason we need to provide a python wrapper module that is + imported via a regular `import perf` and it transparently loads the + actual python perf module, based on the kernel that is currently + running. + + [Test case] + + Install linux-tools- and run the following simple test + case: + + $ python -c 'import perf; [print(c) for c in perf.cpu_map()]' + + [Fix] + + - Enable the python perf module build during the regular kernel build + - Provide a virtual `perf` python module wrapper in linux-tools-common + + [Regression potential] + + We are adding a new python module to linux-tools (that is something new, + we don't ship any other python module), but we are not changing anything + that is already provided, so the only regression that can happen is an + increased size of the linux-tools package. + + [Original bug report] + The tuned package has some plugins which rely on the perf python module [1], and right now they are not working because we do not have the perf python module available in Ubuntu. Initially, this was reported in this other bug [2], but it seems the scope of that bug is bigger than what we (Server) need for tuned. So filing this new bug as requested by the Kernel team to provide just the python module. For reference, in Fedora it's shipped in the bin:python3-perf package: [root@f39 ~]# rpm -ql python3-perf /usr/lib/.build-id /usr/lib/.build-id/80 /usr/lib/.build-id/80/9022196f598cb3327545c2d497b1d9fdf55630 /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/PKG-INFO /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/SOURCES.txt /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/dependency_links.txt /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/top_level.txt /usr/lib64/python3.12/site-packages/perf.cpython-312-x86_64-linux-gnu.so /usr/share/licenses/python3-perf /usr/share/licenses/python3-perf/COPYING Built from their kernel-tools package[3]. - [1] https://bugs.launchpad.net/ubuntu/+source/tuned/+bug/2051290 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613393 [3] https://src.fedoraproject.org/rpms/kernel-tools/blob/rawhide/f/kernel-tools.spec#_148 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051560 Title: Provide python perf module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058191] Re: Getting SIGSEGV and SIGILL in many programs
Unfortunately those traces don't say much without the debugging symbols. If it happens also with the mainline kernel we should see similar bugs reported upstream, that's why I'm not very convinced about this being a kernel issue. More likely a library issue, considering that it happens with different applications (or interactions between kernel and a particular library). You mention that the last kernel that was working was like a 6.5? There's a huge delta between 6.5 and 6.8. Maybe we could try to restrict this range a bit more... At https://kernel.ubuntu.com/mainline/ you can find the debs of pretty much all the mainline kernel versions, maybe you could also test some kernels between 6.5 and 6.8 (assuming you can easily reproduce the problem), in order to restrict the range of changes and have a better idea where to look. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058191 Title: Getting SIGSEGV and SIGILL in many programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058191] Re: Getting SIGSEGV and SIGILL in many programs
Hm... honestly this looks more like a user-space / brave issue than a kernel issue. Do you get similar SIGSEGV with other apps? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058191 Title: Getting SIGSEGV and SIGILL in many programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058191] Re: Getting SIGSEGV and SIGILL in many programs
Can you give it a try also with the latest upstream 6.8 (available here https://kernel.ubuntu.com/mainline/v6.8.1/). This should help to verify if it's an upstream issue or a specific issue with the Ubuntu kernel. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058191 Title: Getting SIGSEGV and SIGILL in many programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055805] Re: touchpad not working with kernel 6.8
@tijs not exactly that kernel, but a kernel that has all the fixes that are included in 6.8.1. :) If you are willing to do one more test to confirm that everything is fine in the next candidate kernel for 24.04, you could try with 6.8.0-20.20 from this ppa: https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/bootstrap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055805 Title: touchpad not working with kernel 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055805] Re: touchpad not working with kernel 6.8
I don't have the hardware at the moment. It'd be great if you could do a test with the latest mainline build, so that we can better understand if it's an upstream issue or something specific with the Ubuntu kernel (or maybe a kernel .config issue): https://kernel.ubuntu.com/mainline/v6.8.1/ Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055805 Title: touchpad not working with kernel 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058191] Re: Getting SIGSEGV and SIGILL in many programs
The message `mce: [Hardware Error]: Machine check events logged` really seems to indicate a potential hardware malfunction. Can you double check if this is happening only with the latest 6.8? Do you see anything similar in dmesg with other kernels? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058191 Title: Getting SIGSEGV and SIGILL in many programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058165] Re: System freeze on copy large files on usb
Can you elaborate more on the freeze part? Does the system completely freezes and it never recovers or is it a temporary freeze (until the copy completes)? How much RAM do you have in your system? Can you check if the following helps to mitigate the problem? $ echo $((32 * 1024 * 1024)) | sudo tee /proc/sys/vm/dirty_bytes $ echo $((16 * 1024 * 1024)) | sudo tee /proc/sys/vm/dirty_background_bytes Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058165 Title: System freeze on copy large files on usb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lowlatency/+bug/2058165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056616] Re: left-over ceph debugging printks
** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056616 Title: left-over ceph debugging printks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051342] Re: Enable lowlatency settings in the generic kernel
** Changed in: linux (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051342 Title: Enable lowlatency settings in the generic kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056126] Re: hwmon: (coretemp) Fix core count limitation
** Changed in: linux (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056126 Title: hwmon: (coretemp) Fix core count limitation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056126] [NEW] hwmon: (coretemp) Fix core count limitation
Public bug reported: [Impact] In linux 6.8 the coretemp driver supports at most 128 cores per package. Cores higher than 128 will lose their core temperature information. There is an upstream patch set that allows to support more than 128 cores per package, but it's applied to linux-next for now and it's scheduled for 6.9. We should apply the patch set to the Noble 6.8 kernel, so that we can properly support systems with a large amount of cores per package. [Test case] Read temperature info from /sys/class/hwmon on a system with > 128 cores per package (that means we don't have a proper test case to verify the fix at the moment). [Fix] Apply the following commits (from linux-next): 18cb15e9c108 hwmon: (coretemp) Use dynamic allocated memory for core temp_data f0a5f46b0100 hwmon: (coretemp) Remove redundant temp_data->is_pkg_data 16a29729c00c hwmon: (coretemp) Split package temp_data and core temp_data b48fddda2b30 hwmon: (coretemp) Abstract core_temp helpers a30f3dc6e9bf hwmon: (coretemp) Remove redundant pdata->cpu_map[] e416450cb080 hwmon: (coretemp) Replace sensor_device_attribute with device_attribute 46ee134971bb hwmon: (coretemp) Remove unnecessary dependency of array index 9f360b22929c hwmon: (coretemp) Introduce enum for attr index [Regression potential] We may experience hwmon-related regressions, either systems reading incorrect temperature information or even bugs/crashes when accessing data from /sys/class/hwmon. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056126 Title: hwmon: (coretemp) Fix core count limitation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054682] Re: apfs-dkms FTBS in noble with the latest 6.8 kernel
** Changed in: linux-apfs-rw (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054682 Title: apfs-dkms FTBS in noble with the latest 6.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-apfs-rw/+bug/2054682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055310] Re: dmesg spammed by virtui-fs and 9pnet-virtio messages
I haven't been able to reproduce this on my PC yet... Looking at the error, especially the virtio-fs part, I'm wondering if you're missing virtiofsd in your host. Can you try to `apt install virtiofsd` (if you don't have it installed already)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055310 Title: dmesg spammed by virtui-fs and 9pnet-virtio messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951440] Re: Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON
** Changed in: linux (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951440 Title: Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049390] Re: Please change CONFIG_CONSOLE_LOGLEVEL_QUIET to 3
For the general use case I think that reducing the verbosity makes sense. About our testing, I think we're not booting kernels with "quiet", and if we do we should definitely drop it from the kernel boot options. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049390 Title: Please change CONFIG_CONSOLE_LOGLEVEL_QUIET to 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055310] Re: dmesg spammed by virtui-fs and 9pnet-virtio messages
I don't see these messages with the latest Noble using the kernel from the proposed pocket (6.8.0-11-generic). Can you also give it a try (if you can)? Hopefully we'll be able to promote a 6.8 in release soon, we are currently blocked by a glibc regression (that doesn't seem to be a kernel regression). If we can unblock/hint this one (hopefully this week, or worst case next week) we'll have a new 6.8 in release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055310 Title: dmesg spammed by virtui-fs and 9pnet-virtio messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977730] [NEW] Kinetic update: v5.18.1 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.18.1 upstream stable release
from git://git.kernel.org/
lockdown: also lock down previous kgdb use
HID: amd_sfh: Add support for sensor discovery
random: fix sysctl documentation nits
init: call time_init() before rand_initialize()
ia64: define get_cycles macro for arch-override
s390: define get_cycles macro for arch-override
parisc: define get_cycles macro for arch-override
alpha: define get_cycles macro for arch-override
powerpc: define get_cycles macro for arch-override
timekeeping: Add raw clock fallback for random_get_entropy()
m68k: use fallback for random_get_entropy() instead of zero
riscv: use fallback for random_get_entropy() instead of zero
mips: use fallback for random_get_entropy() instead of just c0 random
arm: use fallback for random_get_entropy() instead of zero
nios2: use fallback for random_get_entropy() instead of zero
x86/tsc: Use fallback for random_get_entropy() instead of zero
um: use fallback for random_get_entropy() instead of zero
sparc: use fallback for random_get_entropy() instead of zero
xtensa: use fallback for random_get_entropy() instead of zero
random: insist on random_get_entropy() existing in order to simplify
random: do not use batches when !crng_ready()
random: use first 128 bits of input as fast init
random: do not pretend to handle premature next security model
random: order timer entropy functions below interrupt functions
random: do not use input pool from hard IRQs
random: help compiler out with fast_mix() by using simpler arguments
siphash: use one source of truth for siphash permutations
random: use symbolic constants for crng_init states
random: avoid initializing twice in credit race
random: move initialization out of reseeding hot path
random: remove ratelimiting for in-kernel unseeded randomness
random: use proper jiffies comparison macro
random: handle latent entropy and command line from random_init()
random: credit architectural init the exact amount
random: use static branch for crng_ready()
random: remove extern from functions in header
random: use proper return types on get_random_{int,long}_wait()
random: make consistent use of buf and len
random: move initialization functions out of hot pages
random: move randomize_page() into mm where it belongs
random: unify batched entropy implementations
random: convert to using fops->read_iter()
random: convert to using fops->write_iter()
random: wire up fops->splice_{read,write}_iter()
random: check for signals after page of pool writes
ACPI: sysfs: Fix BERT error region memory mapping
ALSA: ctxfi: Add SB046x PCI ID
Linux 5.18.1
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ v5.18.1 upstream stable release
+ from git://git.kernel.org/
-v5.18.1 upstream stable release
-from git://git.kernel.org/
+ lockdown: also lock down previous kgdb use
+ HID: amd_sfh: Add support for sensor discovery
+ random: fix sysctl documentation nits
+ init: call time_init() before rand_initialize()
+ ia64: define get_cycles macro for arch-override
+ s390: define get_cycles macro for arch-override
+ parisc: define get_cycles macro for arch-override
+ alpha: define get_cycles macro for arch-override
+ powerpc: define get_cycles
[Bug 1977732] [NEW] Kinetic update: v5.18.2 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.18.2 upstream stable release
from git://git.kernel.org/
Linux 5.18.2
ALSA: usb-audio: Optimize TEAC clock quirk
bpf: Do write access check for kfunc and global func
bpf: Check PTR_TO_MEM | MEM_RDONLY in check_helper_mem_access
bpf: Reject writes for PTR_TO_MAP_KEY in check_helper_mem_access
bpf: Fix excessive memory allocation in stack_map_alloc()
bpf: Fix usage of trace RCU in local storage.
bpf: Enlarge offset check value to INT_MAX in bpf_skb_{load,store}_bytes
bpf: Fix combination of jit blinding and pointers to bpf subprogs.
bpf: Fix potential array overflow in bpf_trampoline_get_progs()
bpf: Fill new bpf_prog_pack with illegal instructions
NFSD: Fix possible sleep during nfsd4_release_lockowner()
NFS: Memory allocation failures are not server fatal errors
docs: submitting-patches: Fix crossref to 'The canonical patch format'
tpm: ibmvtpm: Correct the return value in tpm_ibmvtpm_probe()
tpm: Fix buffer access in tpm2_get_tpm_pt()
media: i2c: imx412: Fix power_off ordering
media: i2c: imx412: Fix reset GPIO polarity
x86/sgx: Ensure no data in PCMD page after truncate
x86/sgx: Fix race between reclaimer and page fault handler
x86/sgx: Obtain backing storage page with enclave mutex held
x86/sgx: Mark PCMD page as dirty when modifying contents
x86/sgx: Disconnect backing page references from dirty status
HID: multitouch: add quirks to enable Lenovo X12 trackpoint
HID: multitouch: Add support for Google Whiskers Touchpad
fs/ntfs3: validate BOOT sectors_per_clusters
raid5: introduce MD_BROKEN
dm verity: set DM_TARGET_IMMUTABLE feature flag
dm stats: add cond_resched when looping over entries
dm crypt: make printing of the key constant-time
dm integrity: fix error code in dm_integrity_ctr()
ARM: dts: s5pv210: Correct interrupt name for bluetooth in Aries
Bluetooth: hci_qca: Use del_timer_sync() before freeing
ALSA: usb-audio: Configure sync endpoints before data
ALSA: usb-audio: Add missing ep_idx in fixed EP quirks
ALSA: usb-audio: Workaround for clock setup on TEAC devices
tools/memory-model/README: Update klitmus7 compat table
zsmalloc: fix races between asynchronous zspage free and page migration
crypto: qat - rework the VF2PF interrupt handling logic
crypto: ecrdsa - Fix incorrect use of vli_cmp
crypto: caam - fix i.MX6SX entropy delay value
KVM: SVM: Use kzalloc for sev ioctl interfaces to prevent kernel data leak
KVM: x86/mmu: Don't rebuild page when the page is synced and no tlb flushing is
required
KVM: x86: Drop WARNs that assert a triple fault never "escapes" from L2
KVM: x86: Fix the intel_pt PMI handling wrongly considered from guest
KVM: x86: avoid loading a vCPU after .vm_destroy was called
KVM: x86: avoid calling x86 emulator without a decoded instruction
KVM: x86: fix typo in __try_cmpxchg_user causing non-atomicness
KVM: x86: Use __try_cmpxchg_user() to emulate atomic accesses
KVM: x86: Use __try_cmpxchg_user() to update guest PTE A/D bits
x86/uaccess: Implement macros for CMPXCHG on user addresses
x86, kvm: use correct GFP flags for preemption disabled
x86/kvm: Alloc dummy async #PF token outside of raw spinlock
x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave)
KVM: PPC: Book3S HV: fix incorrect NULL check on list iterator
netfilter: conntrack: re-fetch conntrack after insertion
netfilter: nf_tables: double hook unregistration in netns path
netfilter: nf_tables: hold mutex on netns pre_exit path
netfilter: nf_tables: sanitize nft_set_desc_concat_parse()
netfilter: nft_limit: Clone packet limits' cost value
exfat: check if cluster num is valid
drm/i915: Fix -Wstringop-overflow warning in call to intel_read_wm_latency()
net: ipa: compute proper aggregation limit
pipe: Fix missing lock in pipe_resize_ring()
pipe: make poll_usage boolean and annotate its access
assoc_array: Fix BUG_ON during garbage collect
i2c: ismt: prevent memory corruption in ismt_access()
netfilter: nf_tables: disallow non-stateful expression in sets earlier
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Bug 1977544] [NEW] missing python3-pycurl dep
Public bug reported: this is missing python3-pycurl as a dependency, as reported here: https://github.com/osdlyrics/osdlyrics/issues/75 ** Affects: osdlyrics (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977544 Title: missing python3-pycurl dep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/osdlyrics/+bug/1977544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976287] Re: casper: qemu instances too small during autopkgtest (potential OOM failures)
** Summary changed: - casper: qemu image too small in autopkgtest + casper: qemu instances too small during autopkgtest (potential OOM failures) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976287 Title: casper: qemu instances too small during autopkgtest (potential OOM failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1976287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976287] Re: casper: qemu image too small in autopkgtest
Fix for focal (where we are experiencing regressions with hwe-5.15) in the attached debdiff. ** Patch added: "casper-increase-memory-to-test-instances.debdiff" https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1976287/+attachment/5593861/+files/casper-increase-memory-to-test-instances.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976287 Title: casper: qemu image too small in autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1976287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976287] [NEW] casper: qemu image too small in autopkgtest
Public bug reported: [Impact] During autopkgtest we are creating VMs with 768MB of RAM, that used to be enough in the past, but nowdays we typically require more memory and we may trigger some sporadic out-of-memory failures during autopkgtest. [Test case] Run autopkgtest with a recent kernel (e.g., 5.15 or above). [Fix] Bump up the memory size to 1G. [Regression potential] We may see regressions in test systems with a small amount of memory (in the host / hypervisor), because after this change we need more RAM in order to run and complete autopkgtest successfully. ** Affects: casper (Ubuntu) Importance: Undecided Status: New ** Affects: casper (Ubuntu Focal) Importance: Undecided Status: New ** Affects: casper (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: casper (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: casper (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: casper (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: casper (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976287 Title: casper: qemu image too small in autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1976287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)
as ~larsoner mentioned, those scripts contain some `return` but not in functions, so they may fail in some cases; you should change all `return` to `exit 0` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907878 Title: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal
This seems to fix the test failure. ** Patch added: "systemd-test-make-test-execute-pass-on-Linux-5.15.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592621/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.debdiff ** Patch removed: "systemd-test-make-test-execute-pass-on-Linux-5.15.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592620/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.patch ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975587 Title: systemd: fix test-execute autotest failure with kernel 5.15 in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal
** Patch added: "systemd-test-make-test-execute-pass-on-Linux-5.15.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592620/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975587 Title: systemd: fix test-execute autotest failure with kernel 5.15 in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975587] [NEW] systemd: fix test-execute autotest failure with kernel 5.15 in focal
Public bug reported:
[Impact]
test-execute autotest is failing in focal with kernel 5.15. This is
because the following kernel commit changed the ABI for ioprio:
e70344c05995 ("block: fix default IO priority handling")
Previously setting IOPRIO_CLASS_NONE for a process would report
IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
IOPRIO_CLASS_BE instead.
[Test case]
Run systemd autopkgtest and check for the test-execute result.
[Fix]
Change test/test-execute/exec-ioschedulingclass-none.service to
recognize both "none" and "best-effort" as valid returned strings from
ionice.
This change is already available in jammy and above.
[Regression potential]
We may see regressions in systemd autopkgtest, we won't introduce any
potential regressions in systemd itself, because this is only affecting
the specific unit test.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975587
Title:
systemd: fix test-execute autotest failure with kernel 5.15 in focal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969752] Re: oss4-dkms '-mfloat-abi=hard' build failure
@vorlon JFYI, I've just created LP: #1975499 for kinetic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969752 Title: oss4-dkms '-mfloat-abi=hard' build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1969752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975499] [NEW] drop oss4-dkms in kinetic
Public bug reported: [Impact] oss4-dkms fails to build in Jammy with the following error: gcc: error: unrecognized command-line option ‘-mfloat-abi=hard’ We have considered to drop support of this package in other architectures (except amd64) - see for example LP: #1969752, but starting from kinetic we may also consider to drop oss4 completely, considering that not many people are still using it. [Test case] $ sudo apt install oss4-dkms [Fix] Drop oss4-dkms completely. [Regression potential] We may still have users of oss4 that would experience a regression, but considering that oss is a quite old technology it could be worth considering to move to a more modern sound system. ** Affects: oss4 (Ubuntu) Importance: Undecided Status: New ** Affects: oss4 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: oss4 (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975499 Title: drop oss4-dkms in kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1975499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974442] [NEW] enable CONFIG_DEVTMPFS_SAFE
Public bug reported: [Impact] Use nosuid,noexec mount options on devtmpfs, this allows to provide a bit of extra security by preventing mmapping stuff in /dev with PROT_EXEC or having setuid executables. [Test case] If we really want to provide a test case for this...: $ grep devtmpfs /proc/mounts We should see nosuid,noexec in the mount options if this change is applied, otherwise we should only see nosuid (or none of the above). [Fix] Enable CONFIG_DEVTMPFS_SAFE. [Regression potential] This change can potentially break some drivers that require mmapping /dev/mem with the PROT_EXEC flag (for example non-KSM video drivers, or drivers that need to execute BIOS / firmware code directly from /dev/mem). However, it'd be nice to see if we still have drivers that are still relying on this dangerous behavior and provide some additional safety measures in the system. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974442 Title: enable CONFIG_DEVTMPFS_SAFE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1974442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Tested on Ubuntu 18.04 and UX433F Zenbook 14, worked only the backlight but not the digits. Then the system crashed when rebooted and stuck without the chance to repair even in recovery mode. I haven't tried to find a solution starting with a live OS in ramdisk since I wanted to try the newest Ubuntu 22.04, and haven't tested yet here (a little bit scared, evaluating pro and cons...) Cheers, Andrea Il giorno lun 16 mag 2022 alle ore 07:01 Adolfo Jayme < 1810...@bugs.launchpad.net> ha scritto: > ** Changed in: linux (Ubuntu) >Importance: Undecided => Wishlist > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1823320). > https://bugs.launchpad.net/bugs/1810183 > > Title: > numpad on touchpad doesn't work in ASUS Zenbook 14 > > Status in Linux: > New > Status in linux package in Ubuntu: > Confirmed > > Bug description: > I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 > alongside windows 10. > The numeric keypads are within the touchpad and are supposed to be > turned on by a button on the touchpad. This works well in Windows but > doesn't work in Ubuntu. > I have tried to search for any related problems/solutions online but I > haven't been able to. > I will appreciate any suggestion or help. > Thanks, > --- > ProblemType: Bug > ApportVersion: 2.20.10-0ubuntu13.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 18.10 > InstallationDate: Installed on 2018-12-30 (4 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > Package: linux (not installed) > Tags: cosmic > Uname: Linux 4.19.11-041911-generic x86_64 > UnreportableReason: The running kernel is not an Ubuntu kernel > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > --- > ProblemType: Bug > ApportVersion: 2.20.10-0ubuntu13.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 18.10 > InstallationDate: Installed on 2018-12-30 (4 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > Package: linux (not installed) > Tags: cosmic > Uname: Linux 4.18.10-041810-generic x86_64 > UnreportableReason: The running kernel is not an Ubuntu kernel > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > > To manage notifications about this bug go to: > https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions > > -- -- Andrea Mattana -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973620] [NEW] prevent kernel panic with overlayfs + shiftfs
Public bug reported: [Impact] The patch that we have recently re-introduced to properly support overlayfs on top of shiftfs can introduce potential kernel panics, for example: BUG: kernel NULL pointer dereference, address: 0008 [ 447.039738] #PF: supervisor read access in kernel mode [ 447.040369] #PF: error_code(0x) - not-present page [ 447.041002] PGD 0 P4D 0 [ 447.041325] Oops: [#1] SMP NOPTI [ 447.041798] CPU: 0 PID: 73766 Comm: sudo Not tainted 5.15.0-28-generic #29~20.04.1-Ubuntu [ 447.042800] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Ubuntu-1.8.2-1ubuntu1+esm1 04/01/2014 [ 447.043979] RIP: 0010:aa_file_perm+0x3a/0x470 [ 447.044565] Code: 54 53 48 83 ec 68 48 89 7d 80 89 4d 8c 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 63 05 01 0a 19 01 48 03 82 c0 00 00 00 <4c> 8b 68 08 f6 46 40 02 0f 85 d0 00 00 00 41 f6 45 40 02 0f 85 c5 [ 447.046837] RSP: 0018:aefe80a4bca8 EFLAGS: 00010246 [ 447.047481] RAX: RBX: 96e4038abd01 RCX: 0004 [ 447.048351] RDX: 96e4038abd00 RSI: 96e401215eb8 RDI: 9c22a2ac [ 447.049241] RBP: aefe80a4bd38 R08: R09: [ 447.050121] R10: R11: R12: 96e401215eb8 [ 447.051040] R13: 96e4038abd00 R14: 9c22a2ac R15: 0004 [ 447.051942] FS: 7eff3c0f8c80() GS:96e45e40() knlGS: [ 447.052981] CS: 0010 DS: ES: CR0: 80050033 [ 447.053696] CR2: 0008 CR3: 02be2000 CR4: 003506f0 [ 447.054571] Call Trace: [ 447.054883] [ 447.055154] ? unlock_page_memcg+0x2f/0x40 [ 447.055668] ? page_remove_rmap+0x4b/0x320 [ 447.056180] common_file_perm+0x72/0x170 [ 447.056669] apparmor_file_permission+0x1c/0x20 [ 447.057237] security_file_permission+0x30/0x1a0 [ 447.057898] rw_verify_area+0x35/0x60 [ 447.058392] vfs_read+0x6d/0x1a0 [ 447.058842] ksys_read+0xb1/0xe0 [ 447.059276] __x64_sys_read+0x1a/0x20 [ 447.059732] do_syscall_64+0x5c/0xc0 [ 447.060183] ? __set_current_blocked+0x3b/0x60 [ 447.060738] ? exit_to_user_mode_prepare+0x3d/0x1c0 [ 447.061434] ? syscall_exit_to_user_mode+0x27/0x50 [ 447.062099] ? do_syscall_64+0x69/0xc0 [ 447.062603] ? irqentry_exit_to_user_mode+0x9/0x20 [ 447.063210] ? irqentry_exit+0x19/0x30 [ 447.063678] ? exc_page_fault+0x89/0x160 [ 447.064165] ? asm_exc_page_fault+0x8/0x30 [ 447.064675] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 447.065298] RIP: 0033:0x7eff3c2cb002 [Test case] It is really easy to trigger this specific kernel panic running the lxc autopackage test. [Fix] This bug happens because we don't need to decrement anymore the refcount for the previous vm_file value in ovl_vm_prfile_set(). So the fix simply consists of removing the unnecessary fput(). [Regression potential] This patch affects only overlayfs (only when AUFS is enabled), so we may see regressions in overlayfs in kernels that have AUFS enabled (focal hwe and cloud kernels). ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973620 Title: prevent kernel panic with overlayfs + shiftfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972059] Re: One screen does not come back from lock
Here is another one. When I finally got back inside (with both screens working) it was 16:57:15. ** Attachment added: "journal.zip" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+attachment/5589849/+files/journal.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972059 Title: One screen does not come back from lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972059] Re: One screen does not come back from lock
Hi it happened again. This time pretty bad, the monitor did not wake up, even after various Ctrl-Alt-F. But after I switched it off-on, it worked. I was able to login using the other monitor and I immediately check the time: 18:23:37. The other monitor finally came back after that time. I attach the journal file. ** Attachment added: "journal.zip" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+attachment/5589626/+files/journal.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972059 Title: One screen does not come back from lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1414765] Re: Cinnamon session restore does not work
Hello! I tried @SquareRobin solution and it seems to be working fine, I'm under 20.3 - 5.2.7 Cinnamon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1414765 Title: Cinnamon session restore does not work To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1414765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
Alex, thanks for the review! We can definitely remove the dependency of AUFS and provide a standalone patch, in this way we can provide this feature also to those kernels that don't have AUFS enabled (like all the recent kernels in jammy). I'll work on that and will ping you when I have a patch ready to be tested (unless you prepare something before me). :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967924 Title: re-apply missing overlayfs SAUCE patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972059] Re: One screen does not come back from lock
I would like to amend the description of the problem. It happened twice today. I press a kew, and the screen comes back, with the password request, but it is "frozen". If I move the mouse, it only moves on the other screen, and no typing happens. After doing some Ctrl-Alt-F. I land on the "select users" screen and it works again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972059 Title: One screen does not come back from lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
Everything looks good, so I re-applied the patch with the addition of this extra fix: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.15-next=b4c25dba7993400e9c57d3e60bec4ab8bce1b701 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967924 Title: re-apply missing overlayfs SAUCE patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
I think I have a proper fix to re-introduce this patch without panicing the kernel. I'm currently running some stress tests to make sure nothing is broken. If everything goes well I'll re-introduce this patch with the proper fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967924 Title: re-apply missing overlayfs SAUCE patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972059] Re: One screen does not come back from lock
Still on wayland ** Attachment added: "journalctl -b0 > journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+attachment/5587892/+files/journal.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972059 Title: One screen does not come back from lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
@mihalicyn Yes, this patch without AUFS enabled doesn't introduce any problem, but that's because without AUFS the patch is basically a no-op. Here's the ported patch that was applied to 5.15: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.15-next=e3e60b65fa4db4722bd4b02a9dae58f7ff5d83d2 It'd be great if you could take a look and see if you spot any obvious bugs. I'll do more tests later today, trying to better figure out the real issue here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967924 Title: re-apply missing overlayfs SAUCE patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971474] Re: SRU: Update gdb to the final 12.1 release in 22.04 LTS
And it fixes a VSCode integration issue. https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971409 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971474 Title: SRU: Update gdb to the final 12.1 release in 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972059] [NEW] One screen does not come back from lock
Public bug reported: I have 2 screen (Dell). Since having upgraded to 22.04, one of them struggles to come back after a lock. Sometimes takes a few seconds, sometimes it is ok and sometimes it takes longer. I have found that if I do Ctrl-Alt-F1... the screen comes back. I have a DP and HDMI cable and tried to switch them around, it is always the same screen: a Dell U2415 UltraSharp 24. Never happened with any other version since about 18.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 7 13:39:19 2022 DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 seconds (Configuring libpam-systemd (amd64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (825 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (7 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972059 Title: One screen does not come back from lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1972059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
This patch seems to introduce this NULL pointer dereference, that can be triggered systematically running lxc autopkgtest: BUG: kernel NULL pointer dereference, address: 0008 [ 447.039738] #PF: supervisor read access in kernel mode [ 447.040369] #PF: error_code(0x) - not-present page [ 447.041002] PGD 0 P4D 0 [ 447.041325] Oops: [#1] SMP NOPTI [ 447.041798] CPU: 0 PID: 73766 Comm: sudo Not tainted 5.15.0-28-generic #29~20.04.1-Ubuntu [ 447.042800] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Ubuntu-1.8.2-1ubuntu1+esm1 04/01/2014 [ 447.043979] RIP: 0010:aa_file_perm+0x3a/0x470 [ 447.044565] Code: 54 53 48 83 ec 68 48 89 7d 80 89 4d 8c 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 63 05 01 0a 19 01 48 03 82 c0 00 00 00 <4c> 8b 68 08 f6 46 40 02 0f 85 d0 00 00 00 41 f6 45 40 02 0f 85 c5 [ 447.046837] RSP: 0018:aefe80a4bca8 EFLAGS: 00010246 [ 447.047481] RAX: RBX: 96e4038abd01 RCX: 0004 [ 447.048351] RDX: 96e4038abd00 RSI: 96e401215eb8 RDI: 9c22a2ac [ 447.049241] RBP: aefe80a4bd38 R08: R09: [ 447.050121] R10: R11: R12: 96e401215eb8 [ 447.051040] R13: 96e4038abd00 R14: 9c22a2ac R15: 0004 [ 447.051942] FS: 7eff3c0f8c80() GS:96e45e40() knlGS: [ 447.052981] CS: 0010 DS: ES: CR0: 80050033 [ 447.053696] CR2: 0008 CR3: 02be2000 CR4: 003506f0 [ 447.054571] Call Trace: [ 447.054883] [ 447.055154] ? unlock_page_memcg+0x2f/0x40 [ 447.055668] ? page_remove_rmap+0x4b/0x320 [ 447.056180] common_file_perm+0x72/0x170 [ 447.056669] apparmor_file_permission+0x1c/0x20 [ 447.057237] security_file_permission+0x30/0x1a0 [ 447.057898] rw_verify_area+0x35/0x60 [ 447.058392] vfs_read+0x6d/0x1a0 [ 447.058842] ksys_read+0xb1/0xe0 [ 447.059276] __x64_sys_read+0x1a/0x20 [ 447.059732] do_syscall_64+0x5c/0xc0 [ 447.060183] ? __set_current_blocked+0x3b/0x60 [ 447.060738] ? exit_to_user_mode_prepare+0x3d/0x1c0 [ 447.061434] ? syscall_exit_to_user_mode+0x27/0x50 [ 447.062099] ? do_syscall_64+0x69/0xc0 [ 447.062603] ? irqentry_exit_to_user_mode+0x9/0x20 [ 447.063210] ? irqentry_exit+0x19/0x30 [ 447.063678] ? exc_page_fault+0x89/0x160 [ 447.064165] ? asm_exc_page_fault+0x8/0x30 [ 447.064675] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 447.065298] RIP: 0033:0x7eff3c2cb002 This panic happens only when AUFS is enabled (so it can be seen only in focal with 5.15 at the moment). I'm going to revert the patch for now, until we figure out a better way to re-apply this change. ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967924 Title: re-apply missing overlayfs SAUCE patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
NOTE to clarify: I'm going to revert this patch in focal/hwe-5.15, that is the only 5.15 kernel with this patch that has AUFS enabled (so the only kernel where this bug can be triggered). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967924 Title: re-apply missing overlayfs SAUCE patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971409] Re: value_copy: Assertion `arg->contents != nullptr' failed.
Got the same issue in VSCode using gdb 12.0.90. I compiled gdb 12.1 and it works. Can we get it updated to 12.1? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971409 Title: value_copy: Assertion `arg->contents != nullptr' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971699] Re: disable Intel DMA remapping by default
** Summary changed: - disable Intel DMA remapping options by default + disable Intel DMA remapping by default -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971699] [NEW] disable Intel DMA remapping by default
Public bug reported: [Impact] It seems that enabling Intel IOMMU can cause some weird gfx problems, see for example: https://bugs.launchpad.net/bugs/1971146 https://bugs.launchpad.net/bugs/1965882 [Test case] We don't have any specific test case, only other bug reports that tracked down the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971593] Re: make wireless-tools a dependency for network-manager
** Description changed: The wpa-dhclient autopkgtest is always failing without wireless-tools - installed. Maybe wireless-tools should be an explicit dependency of - network-manager. + installed. Maybe wireless-tools should be added to the test dependencies + (debian/tests/control). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971593 Title: make wireless-tools a dependency for network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971593] [NEW] make wireless-tools a dependency for network-manager
Public bug reported: The wpa-dhclient autopkgtest is always failing without wireless-tools installed. Maybe wireless-tools should be an explicit dependency of network-manager. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971593 Title: make wireless-tools a dependency for network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960754] Re: gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied
I'm still having this issue on version (2:4.13.17~dfsg-0ubuntu0.21.04.2) ** Changed in: samba (Ubuntu) Status: Fix Released => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960754 Title: gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1960754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911860] Re: coturn does not start after update of Jan 13 '21 (20.04.1 LTS)
** Changed in: coturn (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911860 Title: coturn does not start after update of Jan 13 '21 (20.04.1 LTS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coturn/+bug/1911860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960754] Re: gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied
** Description changed: Getting the following error gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied - - I seen this was also an issue in redhat + I seen this was also an issue in redhat https://bugzilla.redhat.com/show_bug.cgi?id=1908506 - Description:Ubuntu 20.04.3 LTS Release:20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960754 Title: gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1960754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960754] Re: gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied
Would that be version (2:4.13.17~dfsg-0ubuntu0.21.04.2) ? Because I'm still having this issue on version (2:4.13.17~dfsg-0ubuntu0.21.04.2) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960754 Title: gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1960754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960754] Re: gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied
Im sorry for the really late response -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960754 Title: gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1960754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960754] Re: gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied
Hello i have ^Croot@nextcloud:~apt install smbclient Reading package lists... Done Building dependency tree Reading state information... Done smbclient is already the newest version (2:4.13.17~dfsg-0ubuntu0.21.04.2). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960754 Title: gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1960754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
