[Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
Hello, After looking at it and discussing this with Dann Frazier yesterday (via IRC on #ubuntu-release), we discussed that iproute2 is an important package, it's in main, and has a huge bunch of reverse dependencies. Bumping from 6.1.x to 6.8.x is a bit too much atm, especially given how much is already happening and this being an LTS release. So with that, I'm going to NACK it for FFe and ask this to be uploaded via 0-day SRU or a regular SRU. :) Sorry but I hope you understand. ** Changed in: iproute2 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: iproute2 (Ubuntu) Status: Won't Fix => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) Status in iproute2 package in Ubuntu: Incomplete Bug description: iproute2 upstream produces releases coinciding with upstream kernel releases to support the latest kernel features. Noble's iproute2 is still back at v6.1 even though it will use the v6.8 kernel. This means we provide no userspace interface for newer features - some of which are noted by a networking hardware partner in bug 2060969. Ubuntu's iproute2 has diverged from Debian's to add support for Ubuntu FAN. Noble has dropped kernel support for Ubuntu FAN, so those are no longer needed, and we could now just do a merge. We could also port the FAN patches forward if we can identify a need (see the original description of this bug to a link to such a port), but I have not done any testing with that. I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and smoke tested it on an amd64 virtual machine: ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb (Reading database ... 83134 files and directories currently installed.) Preparing to unpack iproute2_6.8.0-1~24.04.1_amd64.deb ... Unpacking iproute2 (6.8.0-1~24.04.1) over (6.1.0-1ubuntu6) ... dpkg: warning: unable to delete old directory '/etc/iproute2/rt_tables.d': Directory not empty dpkg: warning: unable to delete old directory '/etc/iproute2/rt_protos.d': Directory not empty dpkg: warning: unable to delete old directory '/etc/iproute2': Directory not empty Setting up iproute2 (6.8.0-1~24.04.1) ... Removing obsolete conffile /etc/iproute2/group ... Removing obsolete conffile /etc/iproute2/rt_realms ... Removing obsolete conffile /etc/iproute2/rt_scopes ... Removing obsolete conffile /etc/iproute2/rt_tables ... Removing obsolete conffile /etc/iproute2/rt_tables.d/README ... Removing obsolete conffile /etc/iproute2/rt_protos.d/README ... Removing obsolete conffile /etc/iproute2/rt_protos ... Removing obsolete conffile /etc/iproute2/rt_dsfield ... Removing obsolete conffile /etc/iproute2/nl_protos ... Removing obsolete conffile /etc/iproute2/ematch_map ... Removing obsolete conffile /etc/iproute2/bpf_pinning ... Processing triggers for man-db (2.12.0-4build1) ... The system rebooted fine. The ip command seems to behave normally. Since the upstream test suite only appears to run at autopkgtest time, I triggered a run in my PPA, and it passed: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-test/noble/amd64/i/iproute2/20240412_210819_97417@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
** Also affects: mesa (Ubuntu Noble) Importance: Undecided Assignee: Juerg Haefliger (juergh) Status: Fix Released ** Also affects: ubuntu-settings (Ubuntu Noble) Importance: Undecided Assignee: Dave Jones (waveform) Status: Fix Released ** Also affects: pipewire (Ubuntu Noble) Importance: Undecided Assignee: Juerg Haefliger (juergh) Status: Invalid ** Also affects: linux-meta-raspi (Ubuntu Noble) Importance: Undecided Assignee: Juerg Haefliger (juergh) Status: Fix Released ** Also affects: linux-raspi (Ubuntu Noble) Importance: Undecided Assignee: Juerg Haefliger (juergh) Status: Fix Released ** Also affects: libcamera (Ubuntu Noble) Importance: Undecided Assignee: Juerg Haefliger (juergh) Status: Triaged ** Also affects: rpi-eeprom (Ubuntu Noble) Importance: Undecided Assignee: Dave Jones (waveform) Status: Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in Release Notes for Ubuntu: Fix Released Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Invalid Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in libcamera source package in Noble: Triaged Status in linux-meta-raspi source package in Noble: Fix Released Status in linux-raspi source package in Noble: Fix Released Status in mesa source package in Noble: Fix Released Status in pipewire source package in Noble: Invalid Status in rpi-eeprom source package in Noble: Fix Released Status in ubuntu-settings source package in Noble: Fix Released Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038546] Re: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64
Can you please adjust the status of Noble, too? Thanks ** Also affects: linux-firmware (Ubuntu Noble) Importance: High Status: Fix Released ** Changed in: linux-firmware (Ubuntu Noble) Status: Fix Released => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2038546 Title: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Mantic: Fix Released Status in linux-firmware source package in Noble: New Bug description: [Impact] /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the StarFive VisionFive board which uses the starfive kernel flavor. The file was available in Jammy and only recently removed from Mantic. File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding it cyfmac43430-sdio.clm_blob which file WHENCE links to brcmfmac43430-sdio.bin. So this file needs to change. [Fix] Include cypress/cyfmac firmware files in firmware packages. [Test Case] Check that wifi is functional. [Where Problems Could Occur] Potential wifi problems on platforms that are using the brcmfmac driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
** Also affects: linux-raspi (Ubuntu Noble) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Noble: Confirmed Bug description: I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a strange behaviour of the screen saver. In settings -> energy -> power saving options I selected Screen Blank after 5 minutes. After 5 minutes of inactivity, the screen goes blank, the monitor says No Signal and turns off, but a few seconds after it turns on again, showing a completely black screen. The desired behaviour here is that Ubuntu sends no signal to the monitor, so the monitor goes into low-consumption mode. But this is not happening, the monitor is on and showing a black screen. I wonder how to solve this problem, especially given the current energy situation in Europe. This bug is related to the Ubuntu 22.04 LTS and 22.10 version. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7 Uname: Linux 5.19.0-1009-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 21:31:27 2022 DisplayManager: gdm3 GsettingsChanges: ImageMediaBuild: 20221018.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038920] Re: Nezahl D1: usb 1-1: device descriptor read/64, error -71
** Changed in: linux-riscv (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2038920 Title: Nezahl D1: usb 1-1: device descriptor read/64, error -71 Status in linux-riscv package in Ubuntu: New Bug description: On the Nezha D1 board USB does not work correctly. I have connected a USB keyboard and get errors like: [ 4458.313671] usb 1-1: device descriptor read/64, error -71 [ 4459.189686] usb 1-1: device descriptor read/64, error -71 [ 4460.157594] usb 4-1: device descriptor read/64, error -62 [ 4460.461621] usb 4-1: device descriptor read/64, error -62 [ 4460.953646] usb 4-1: device descriptor read/64, error -62 [ 4461.257626] usb 4-1: device descriptor read/64, error -62 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 12:20:40 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038893] Re: probe-bcache[132]: unhandled signal 11 code 0x1 at 0x0038004000000004
** Changed in: bcache-tools (Ubuntu) Importance: Undecided => Low ** Changed in: linux-riscv (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2038893 Title: probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044 Status in bcache-tools package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Bug description: Running http://cdimage.ubuntu.com/ubuntu-server/daily- preinstalled/20231010/mantic-preinstalled-server-riscv64.img.xz on QEMU with qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -device virtio-net- device,netdev=eth0 -netdev user,id=eth0 -device virtio-rng-pci -drive file=mantic-preinstalled-server-riscv64.img,format=raw,if=virtio a crash was reported: Starting systemd-udevd version 253.5-1ubuntu6 [3.919909] probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044 [3.920554] CPU: 3 PID: 132 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.921064] Hardware name: riscv-virtio,qemu (DT) [3.921382] epc : 00380044 ra : 7fffadf8ac82 sp : 7fffce174160 [3.921750] gp : 5fd56800 tp : 7fffade18780 t0 : 1000 [3.922110] t1 : 5fd53a3c t2 : 0034e6b4 s0 : 7fffae006ae0 [3.922422] s1 : 7fffce174c78 a0 : 7fffce174178 a1 : 7fffae006ae0 [3.922751] a2 : 00022560 a3 : 7fff a4 : [3.923121] a5 : 00380045 a6 : 0007d436 a7 : 001d [3.923576] s2 : 0001 s3 : 7fffae005d80 s4 : 0003 [3.923913] s5 : 7d4352a0 s6 : s7 : 7fffce174160 [3.924251] s8 : 7fffce174a30 s9 : 7fffadfb86f0 s10: 7fffce174178 [3.924585] s11: 7fffce174188 t3 : 7fffadf8abe8 t4 : [3.924897] t5 : 7fffadfdda40 t6 : 7fffadfde028 [3.925090] status: 00024020 badaddr: 00380044 cause: 000c [3.933878] probe-bcache[130]: unhandled signal 11 code 0x1 at 0x00380044 [3.934386] CPU: 1 PID: 130 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.934742] Hardware name: riscv-virtio,qemu (DT) [3.934974] epc : 00380044 ra : 7fff9b9acc82 sp : 7fffe3a88160 [3.935316] gp : 91f30800 tp : 7fff9b83a780 t0 : 1000 [3.935869] t1 : 91f2da3c t2 : 0034e6b4 s0 : 7fff9ba28ae0 [3.936224] s1 : 7fffe3a88c78 a0 : 7fffe3a88178 a1 : 7fff9ba28ae0 [3.936606] a2 : 00022560 a3 : 7fff a4 : [3.937030] a5 : 00380045 a6 : 000b3fa0 a7 : 001d [3.937443] s2 : 0001 s3 : 7fff9ba27d80 s4 : 0003 [3.937868] s5 : b3f9f2a0 s6 : s7 : 7fffe3a88160 [3.938261] s8 : 7fffe3a88a30 s9 : 7fff9b9da6f0 s10: 7fffe3a88178 [3.938681] s11: 7fffe3a88188 t3 : 7fff9b9acbe8 t4 : [3.939113] t5 : 7fff9b9ffa40 t6 : 7fff9ba00028 [3.939469] status: 00024020 badaddr: 00380044 cause: 000c [3.951861] probe-bcache[129]: unhandled signal 11 code 0x1 at 0x00380044 [3.952290] CPU: 0 PID: 129 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.952680] Hardware name: riscv-virtio,qemu (DT) [3.952887] epc : 00380044 ra : 7fff86598c82 sp : 7fffea625160 [3.953236] gp : 74eb1800 tp : 7fff86426780 t0 : 1000 [3.953582] t1 : 74eaea3c t2 : 0034e6b4 s0 : 7fff86614ae0 [3.953936] s1 : 7fffea625c78 a0 : 7fffea625178 a1 : 7fff86614ae0 [3.954302] a2 : 00022560 a3 : 7fff a4 : [3.954700] a5 : 00380045 a6 : 0009411b a7 : 001d [3.955114] s2 : 0001 s3 : 7fff86613d80 s4 : 0003 [3.955657] s5 : 9411a2a0 s6 : s7 : 7fffea625160 [3.956018] s8 : 7fffea625a30 s9 : 7fff865c66f0 s10: 7fffea625178 [3.956368] s11: 7fffea625188 t3 : 7fff86598be8 t4 : [3.956741] t5 : 7fff865eba40 t6 : 7fff865ec028 [3.957026] status: 00024020 badaddr: 00380044 cause: 000c Begin: Loading essential drivers ... [6.255484] raid6: int64x8 gen() 635 MB/s ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1 ProcVersionSignature: Ubuntu
[Kernel-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs
Since this is no longer an FFe thing, I am removing so from the title. This should help fix our searches better. The ideal way would be to unsubscribe ubuntu-release, though. ** Summary changed: - FFe: Enable configuring resume offset via sysfs + Enable configuring resume offset via sysfs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760106 Title: Enable configuring resume offset via sysfs Status in OEM Priority Project: Fix Released Status in klibc package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in klibc source package in Bionic: New Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in klibc source package in Cosmic: New Status in linux source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Cannot hibernate & resume from a swapfile [Test Case] * Create or enlarge swapfile to be big enough for hibernation * Attempt to hibernate and resume [Regression Potential] * Hibernation is not reliable technology in itself, and multiple things may cause failure to resume. Thus it is sufficient to validate this bug after swapfile is attempted for hibernation and the disk offset kernel parameter is modified. Irrespective if actual suspending or resume were successful or not. [Other Info] * Original bug report In 4.17 a new attribute is introduced to configure the hibernation resume offset. Since Ubuntu enables a swapfile by default this attribute is important to be able to make hibernation work "out of the box". The patch in the kernel is here: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9 Systemd support for adopting this change is available here: https://github.com/systemd/systemd/pull/8406 As of 3/30/18 it's not yet been merged however. Klibc support for adopting this change is available here: https://www.zytor.com/pipermail/klibc/2018-March/003986.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
