[Kernel-packages] [Bug 2046315] Re: panel flickering after the i915.psr2 is enabled
** Summary changed: - panel flickering after enabling the psr2 + panel flickering after the i915.psr2 is enabled -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: panel flickering after the i915.psr2 is enabled Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2061040] Re: I2C HID device sometimes fails to initialize causing touchpad to not work
$ git tag --contains af93a167eda90192563bce64c4bb989836afac1f Ubuntu-6.8.0-10.10 Ubuntu-6.8.0-11.11 Ubuntu-6.8.0-6.6 Ubuntu-6.8.0-7.7 Ubuntu-6.8.0-8.8 Ubuntu-6.8.0-9.9 v6.8 v6.8-rc1 The first commit is already in 6.8.0-22. Could you double confirm if the 2nd link is the real fix? I don't reproduce this issue with the same touchpad: ThinkPad BIOS N3YET57W (1.22 ), EC N3YHT43W Device: SNSL0028:00 2C2F:0028 Touchpad Kernel: /dev/input/event12 Group:5 Seat: seat0, default Size: 118x68mm Capabilities: pointer gesture Tap-to-click: disabled Tap-and-drag: enabled Tap drag lock:disabled Left-handed: disabled Nat.scrolling:disabled Middle emulation: disabled Calibration: n/a Scroll methods: *two-finger edge Click methods:*button-areas clickfinger Disable-w-typing: enabled Disable-w-trackpointing: enabled Accel profiles: flat *adaptive custom Rotation: n/a $ journalctl -k |grep SNSL Apr 16 13:28:02 Thames-3 kernel: i2c_hid_acpi i2c-SNSL0028:00: device did not ack reset within 1000 ms Apr 16 13:28:02 Thames-3 kernel: input: SNSL0028:00 2C2F:0028 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input10 Apr 16 13:28:02 Thames-3 kernel: input: SNSL0028:00 2C2F:0028 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input11 Apr 16 13:28:02 Thames-3 kernel: hid-generic 0018:2C2F:0028.0002: input,hidraw1: I2C HID v1.00 Mouse [SNSL0028:00 2C2F:0028] on i2c-SNSL0028:00 Apr 16 13:28:03 Thames-3 kernel: input: SNSL0028:00 2C2F:0028 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input20 Apr 16 13:28:03 Thames-3 kernel: input: SNSL0028:00 2C2F:0028 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input21 Apr 16 13:28:03 Thames-3 kernel: hid-multitouch 0018:2C2F:0028.0002: input,hidraw1: I2C HID v1.00 Mouse [SNSL0028:00 2C2F:0028] on i2c-SNSL0028:00 ** Changed in: linux (Ubuntu Noble) Status: New => Triaged -- 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/2061040 Title: I2C HID device sometimes fails to initialize causing touchpad to not work Status in linux package in Ubuntu: Triaged Status in linux source package in Noble: Triaged Bug description: Hi, Touchpad on my new Lenovo X1 Carbon (Gen12) with the Sensel haptic pad doesn't work on boot. I see this: | [Thu Apr 11 13:57:26 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack reset within 1000 ms | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | ... | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unbalanced collection at end of report description | [Thu Apr 11 13:57:26 2024] hid-generic: probe of 0018:2C2F:0028.0001 failed with error -22 Per the Arch Linux wiki page[1], removing and reloading the `i2c_hid_acpi` seems to fix it: | [Thu Apr 11 13:58:02 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack reset within 1000 ms | [Thu Apr 11 13:58:02 2024] input: SNSL0028:00 2C2F:0028 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-15/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input15 | [Thu Apr 11 13:58:02 2024] input: SNSL0028:00 2C2F:0028 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-15/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input16 | [Thu Apr 11 13:58:02 2024] hid-multitouch 0018:2C2F:0028.0002: input,hidraw0: I2C HID v1.00 Mouse [SNSL0028:00 2C2F:0028] on i2c-SNSL0028:00 | [Thu Apr 11 13:58:03 2024] psmouse serio1: trackpoint: Synaptics TrackPoint firmware: 0x08, buttons: 3/3 | [Thu Apr 11 13:58:03 2024] input: TPPS/2 Synaptics TrackPoint as /devices/platform/i8042/serio1/input/input18 From that Arch Linux wiki page, it seems to be a bug upstream[2] with the commit
[Kernel-packages] [Bug 2015782] Re: System freeze [(EE) NVIDIA(GPU-0): WAIT (2, 8, 0x8000, 0x00039cbc, 0x00039cc4)]
** Also affects: nvidia-graphics-drivers-550 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-550 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2015782 Title: System freeze [(EE) NVIDIA(GPU-0): WAIT (2, 8, 0x8000, 0x00039cbc, 0x00039cc4)] Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-550 package in Ubuntu: Confirmed Bug description: gnome-shell makes the system crash occasionally. Last time was after closing a youtube tab in firefox. Custom keyboard shorcuts are also not working sometimes. My system is Ubuntu 22.04.2 LTS Linux PC1 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC CPU: Ryzen 7 7700X RAM: 32 GB 6000 CL30 GPU: Nvidia 2060 Super MOBO: Asrock x670e Steel Legend ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 10 11:58:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-02-24 (44 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 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/nvidia-graphics-drivers-525/+bug/2015782/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
The new kernel is tagged as 5.15.0-105-generic, and it is a respin of 5.15.0-103-generic with the fix. https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/log/?h=Ubuntu-5.15.0-105.115 It should be available in -proposed soon, the Kernel Team are still rebuilding all the 5.15 derivatives. I'll write back once it is in -proposed for testing. Thanks, Matthew -- 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/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2046315] Re: panel flickering after enabling the psr2
** Summary changed: - oem-6.5: disable psr2 for some panels according to edid + panel flickering after enabling the psr2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: panel flickering after enabling the psr2 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2060101] Re: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera
** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: ipu6-drivers (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: ipu6-drivers (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: ipu6-drivers (Ubuntu Mantic) Importance: Undecided => High ** Changed in: ipu6-drivers (Ubuntu Mantic) Status: New => In Progress ** Changed in: ipu6-drivers (Ubuntu Mantic) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: ipu6-drivers (Ubuntu Noble) Importance: Undecided => High ** Changed in: ipu6-drivers (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => Won't Fix ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060101 Title: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in ipu6-drivers source package in Mantic: In Progress Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: In Progress Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060101/+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 2046681] Re: jammy-oem-6.5: one more panel needs to disable psr2
For oem-6.8 and noble kernels, the fix will be merged by https://bugs.launchpad.net/ubuntu/jammy/+source/linux- oem-6.8/+bug/2046315 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046681 Title: jammy-oem-6.5: one more panel needs to disable psr2 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2046681 [Impact] The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046681/+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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
** Also affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.8 (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 1878838] Re: [nvidia] Black screen (wrong VT) upon login
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1878838 Title: [nvidia] Black screen (wrong VT) upon login Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Status in nvidia-graphics-drivers-440 package in Ubuntu: Expired Bug description: OS: Fresh install of ubuntu 20.04 Steps: 1. Enter password to login (Black screen is shown) Workaround: 2. After blank screen is shown, press Ctrl+Alt+F3. (It'll show terminal with login prompt) 3. Don't login, simply press Ctrl+Alt+F2. (Now desktop is shown, black screen is gone) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 14:08:29 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-04-28 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=2a627b38-a2bd-4bec-9551-703eab56e5da ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1878838/+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 1878838] Re: [nvidia] Black screen (wrong VT) upon login
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1878838 Title: [nvidia] Black screen (wrong VT) upon login Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Status in nvidia-graphics-drivers-440 package in Ubuntu: Expired Bug description: OS: Fresh install of ubuntu 20.04 Steps: 1. Enter password to login (Black screen is shown) Workaround: 2. After blank screen is shown, press Ctrl+Alt+F3. (It'll show terminal with login prompt) 3. Don't login, simply press Ctrl+Alt+F2. (Now desktop is shown, black screen is gone) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 14:08:29 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-04-28 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=2a627b38-a2bd-4bec-9551-703eab56e5da ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1878838/+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 1878838] Re: [nvidia] Black screen (wrong VT) upon login
[Expired for nvidia-graphics-drivers-440 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1878838 Title: [nvidia] Black screen (wrong VT) upon login Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Status in nvidia-graphics-drivers-440 package in Ubuntu: Expired Bug description: OS: Fresh install of ubuntu 20.04 Steps: 1. Enter password to login (Black screen is shown) Workaround: 2. After blank screen is shown, press Ctrl+Alt+F3. (It'll show terminal with login prompt) 3. Don't login, simply press Ctrl+Alt+F2. (Now desktop is shown, black screen is gone) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 14:08:29 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-04-28 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=2a627b38-a2bd-4bec-9551-703eab56e5da ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1878838/+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 2061713] Re: ASUS Battery Won't Charge if Plugged in While Suspended
** Package changed: ubuntu => linux-signed-hwe-6.5 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061713 Title: ASUS Battery Won't Charge if Plugged in While Suspended Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: When running Ubuntu (or any other linux distro i've tried) the laptop will not charge if it is plugged in while suspended. Charging works find if the laptop is awake, or if it is shut down. It also works properly when running windows which makes me think its not a hardware problem but a linux issue. The charge status doesn't seem to update at all when the computer is suspended. If it is charging when its put to sleep then the charge LED on the side is lit, and if I then unplug the charger the LED doesn't turn off until the computer is woken up. If the computer is plugged in while sleeping I know it isn't charging even though the light doesn't turn on because I have left it overnight and the battery stays at the same percentage. I've been unable to find any information about what could be causing this issue. My Laptop is an ASUS Zenbook Flip UX461UA Ubuntu Version: Description: Ubuntu 22.04.4 LTS Release: 22.04 I'm not sure what package would be causing this. What I expect to be happening: The battery should start charging if its plugged in while suspended What happened instead: Battery doesn't charge and charging indicator doesn't change until the computer is woken up ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 23:21:17 2024 InstallationDate: Installed on 2024-04-16 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061713/+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 2061713] [NEW] ASUS Battery Won't Charge if Plugged in While Suspended
You have been subscribed to a public bug: When running Ubuntu (or any other linux distro i've tried) the laptop will not charge if it is plugged in while suspended. Charging works find if the laptop is awake, or if it is shut down. It also works properly when running windows which makes me think its not a hardware problem but a linux issue. The charge status doesn't seem to update at all when the computer is suspended. If it is charging when its put to sleep then the charge LED on the side is lit, and if I then unplug the charger the LED doesn't turn off until the computer is woken up. If the computer is plugged in while sleeping I know it isn't charging even though the light doesn't turn on because I have left it overnight and the battery stays at the same percentage. I've been unable to find any information about what could be causing this issue. My Laptop is an ASUS Zenbook Flip UX461UA Ubuntu Version: Description:Ubuntu 22.04.4 LTS Release:22.04 I'm not sure what package would be causing this. What I expect to be happening: The battery should start charging if its plugged in while suspended What happened instead: Battery doesn't charge and charging indicator doesn't change until the computer is woken up ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 23:21:17 2024 InstallationDate: Installed on 2024-04-16 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- ASUS Battery Won't Charge if Plugged in While Suspended https://bugs.launchpad.net/bugs/2061713 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. -- 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 2061254] Re: No mic detected - Ubuntu 24.04 Beta
I checked the latest ubuntu noble kernel, the fix is already merged to this kernel through this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060531 Please wait for the upcoming release version of noble kernel. commit 6a9156867a5ce4ded2967ca46b0a8d755d9a1ee7 Author: Jiawei Wang Date: Wed Mar 13 09:58:53 2024 +0800 ASoC: amd: yc: Revert "add new YC platform variant (0x63) support" BugLink: https://bugs.launchpad.net/bugs/2060531 commit 37bee1855d0e3b6dbeb8de71895f6f68cad137be upstream. This reverts commit 316a784839b21b122e1761cdca54677bb19a47fa, that enabled Yellow Carp (YC) driver for PCI revision id 0x63. Mukunda Vijendar [1] points out that revision 0x63 is Pink Sardine platform, not Yellow Carp. The YC driver should not be enabled for this platform. This patch prevents the YC driver from being incorrectly enabled. Link: https://lore.kernel.org/linux-sound/023092e1-689c-4b00-b93f-4092c3724...@amd.com/ [1] Signed-off-by: Jiawei Wang Link: https://msgid.link/r/20240313015853.3573242-3...@jwang.link Signed-off-by: Mark Brown Signed-off-by: Greg Kroah-Hartman Signed-off-by: Paolo Pisati ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Noble) Importance: Medium Assignee: Hui Wang (hui.wang) Status: New ** Changed in: linux (Ubuntu Noble) Status: New => In Progress -- 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/2061254 Title: No mic detected - Ubuntu 24.04 Beta Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: On Ubuntu 23.10, my laptop microphone is detected/working fine, but can't be detected on Ubuntu 24.04. Tried direct direct install of 24.04 and upgrade fromo 23.10, same problem ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:burnarz 43101 F pipewire /dev/snd/controlC0: burnarz 43106 F wireplumber /dev/snd/controlC1: burnarz 43106 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 01:04:10 2024 InstallationDate: Installed on 2024-04-13 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240412) MachineType: LENOVO 83AR PackageArchitecture: all ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2024 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: MDCN33WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Pro 5 16APH8 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrMDCN33WW:bd01/24/2024:br1.33:efr1.33:svnLENOVO:pn83AR:pvrIdeaPadPro516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrIdeaPadPro516APH8:skuLENOVO_MT_83AR_BU_idea_FM_IdeaPadPro516APH8: dmi.product.family: IdeaPad Pro 5 16APH8 dmi.product.name: 83AR dmi.product.sku: LENOVO_MT_83AR_BU_idea_FM_IdeaPad Pro 5 16APH8 dmi.product.version: IdeaPad Pro 5 16APH8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061254/+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 2061254] [NEW] No mic detected - Ubuntu 24.04 Beta
You have been subscribed to a public bug: On Ubuntu 23.10, my laptop microphone is detected/working fine, but can't be detected on Ubuntu 24.04. Tried direct direct install of 24.04 and upgrade fromo 23.10, same problem ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:burnarz 43101 F pipewire /dev/snd/controlC0: burnarz 43106 F wireplumber /dev/snd/controlC1: burnarz 43106 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 01:04:10 2024 InstallationDate: Installed on 2024-04-13 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240412) MachineType: LENOVO 83AR PackageArchitecture: all ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2024 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: MDCN33WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Pro 5 16APH8 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrMDCN33WW:bd01/24/2024:br1.33:efr1.33:svnLENOVO:pn83AR:pvrIdeaPadPro516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrIdeaPadPro516APH8:skuLENOVO_MT_83AR_BU_idea_FM_IdeaPadPro516APH8: dmi.product.family: IdeaPad Pro 5 16APH8 dmi.product.name: 83AR dmi.product.sku: LENOVO_MT_83AR_BU_idea_FM_IdeaPad Pro 5 16APH8 dmi.product.version: IdeaPad Pro 5 16APH8 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Tags: amd64 apport-bug noble wayland-session -- No mic detected - Ubuntu 24.04 Beta https://bugs.launchpad.net/bugs/2061254 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 2058315] Re: Mute/mic-mute LEDs not functioning on a HP platform
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => Chris Chiu (mschiu77) -- 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/2058315 Title: Mute/mic-mute LEDs not functioning on a HP platform Status in OEM Priority Project: New Status in linux package in Ubuntu: New Bug description: [Impact] LEDs on both mute and mic-mute key are not working on a HP platform. [Fix] The quirk in the commit b2d6a1fd0e3e513f5ebfc152d6fedae093df8e21 (ALSA: hda/realtek: Add quirks for HP G11 Laptops using CS35L56) in linux-next can make it work. [Test] 1. Install the v2023.12.1 of upstream sof-bin (https://github.com/thesofproject/sof-bin/releases/tag/v2023.12.1) 2. Then after the quirk is applied, both the mute and mic-mute LEDs on the keys should toggle accordingly on key presses. [Where problems could occur] If the subsystem ID is somehow reused by vendor for newer hardware, the newer hardware may not be functioning correctly. Also it requires correct tplg files to work. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2058315/+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 1943915] Enquiry-Please attend to this.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1943915 Title: IPU6 daemon+v4l2loopback is required to enable use for existing applications Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Expired Bug description: The device is properly detected but it seems there are still issues with gstreamer plugin. When I try to run cheese I get the following error message: ../src/intel/isl/isl.c:2018: FINISHME: ../src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is disabled, but a workaround is available. (cheese:3769): cheese-WARNING **: 08:02:37.506: Failed to allocate required memory.: gstv4l2src.c(660): gst_v4l2src_decide_allocation (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Buffer pool activation failed With VLC I get stefang@capella:~$ vlc v4l2:///dev/video0 VLC media player 3.0.9.2 Vetinari (revision 3.0.9.2-0-gd4c1aefe4d) [55cfdb6a3670] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. Using mplane plugin for capture [7f0230001160] v4l2 demux error: cannot get streaming parameters: Inappropriate ioctl for device libv4l2: error turning on stream: Link has been severed [7f0230001160] v4l2 demux error: cannot start streaming: Link has been severed Using mplane plugin for capture [7f0230001160] v4l2 demux error: not a radio tuner device Using mplane plugin for capture [7f0230007b70] v4l2 stream error: cannot get streaming parameters: Inappropriate ioctl for device libv4l2: error turning on stream: Link has been severed [7f0230007b70] v4l2 stream error: cannot start streaming: Link has been severed QObject::~QObject: Timers cannot be stopped from another thread ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-1012-oem 5.13.0-1012.16 ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1 Uname: Linux 5.13.0-1012-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 17 07:59:51 2021 InstallationDate: Installed on 2021-09-16 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-oem-5.13 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stefang1469 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-16 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Latitude 9420 Package: linux-oem-5.13 (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1012-oem root=UUID=e2704fd1-5330-4b87-9cdf-a353f5fe73b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-1012-oem N/A linux-backports-modules-5.13.0-1012-oem N/A linux-firmware 1.187.16 Tags: focal Uname: Linux 5.13.0-1012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/13/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 08XKF8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd04/13/2021:br1.2:svnDellInc.:pnLatitude9420:pvr:sku0A32:rvnDellInc.:rn08XKF8:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 9420 dmi.product.sku: 0A32 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1943915/+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 2061373] Re: Print kernel messages before the uefi POST screen disappears in Ubuntu24.04 Beta
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- 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/2061373 Title: Print kernel messages before the uefi POST screen disappears in Ubuntu24.04 Beta Status in linux package in Ubuntu: New Bug description: 1.The Version of product # lsb_release -rd No LSB modules are available. Description:Ubuntu Noble Numbat (development branch) Release:24.04 2.The version of package root@t:/tmp# apt-cache policy linux-image-6.8.0-22-generic linux-image-6.8.0-22-generic: Installed: 6.8.0-22.22 Candidate: 6.8.0-22.22 Version table: *** 6.8.0-22.22 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status 3.Expected to happen Print kernel output information after the server's POST screen disappears 4.Actual happend Print kernel output information before the server's POST screen disappears Please refer to the attached screenshot for details ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 15 07:46 seq crw-rw 1 root audio 116, 33 Apr 15 07:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Mon Apr 15 08:26:52 2024 InstallationDate: Installed on 2024-04-15 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Lenovo ThinkSystem SR650 V3 MB,EGS,DDR5,SH,2U PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=77cf1cbe-6d2e-4dec-9439-c7aa2a69b5d9 ro RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2023 dmi.bios.release: 3.10 dmi.bios.vendor: Lenovo dmi.bios.version: ESE121R-3.10 dmi.board.asset.tag: None dmi.board.name: STA7B05327 dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: None dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.ec.firmware.release: 3.90 dmi.modalias: dmi:bvnLenovo:bvrESE121R-3.10:bd11/15/2023:br3.10:efr3.90:svnLenovo:pnThinkSystemSR650V3MB,EGS,DDR5,SH,2U:pvr05:rvnLenovo:rnSTA7B05327:rvr05:cvnLenovo:ct23:cvrNone:sku7D75CTO0WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V3 MB,EGS,DDR5,SH,2U dmi.product.sku: 7D75CTO0WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061373/+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 2061378] Re: [24.04]: mpi3mr: Features and Bug Fixes
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- 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/2061378 Title: [24.04]: mpi3mr: Features and Bug Fixes Status in linux package in Ubuntu: New Bug description: Below are the features which we want to add in Ubuntu24.04 kernel over mpi3mr driver v8.8.1.0.50, - 829dce7e12c2 : mpi3mr: Driver version update to 8.8.1.0.50 - 57a80be5ec6f : mpi3mr: Update MPI Headers to revision 31 - 0a2714b787b9 : mpi3mr: Debug ability improvements - e8a5a3c3eb58 : mpi3mr: Set the WriteSame Divert Capability in the IOCInit MPI Request - 31ec576ee06a : mpi3mr: Clear ioctl blocking flag for an unresponsive controller - a18f4c58372d : mpi3mr: Set MPI request flags appropriately - dd896a6b0a0d : mpi3mr: Block devices are not removed even when VDs are offlined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061378/+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 2061376] Re: Touchpad scroll bounces back 22.04.4 Thinkpad X1 Yoga Gen5
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- 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/2061376 Title: Touchpad scroll bounces back 22.04.4 Thinkpad X1 Yoga Gen5 Status in linux package in Ubuntu: New Bug description: When scrolling anywhere using 2 fingers the scroll bounces back if fingers are lifted up from touchpad. Soft finger point muscles have some flex to them and I strongly believe this causes the scroll bounce back. Easily repeated to both directions. In bounce scroll rapidly moves to the opposite direction of where user wanted to scroll when lifting up fingers. Attached is log file evtest_event5.log from single scroll where there was bounce at lifting fingers. Hardware details: xinput --list WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ xwayland-pointer:16 id=6[slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:16id=7[slave pointer (2)] ⎜ ↳ xwayland-pointer-gestures:16id=8[slave pointer (2)] ⎜ ↳ xwayland-touch:16 id=10 [slave pointer (2)] ⎜ ↳ xwayland-tablet stylus:16 id=11 [slave pointer (2)] ⎜ ↳ xwayland-tablet eraser:16 id=12 [slave pointer (2)] ⎜ ↳ xwayland-tablet cursor:16 id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ xwayland-keyboard:16id=9[slave keyboard (3)] lshw *-input:0 product: Sleep Button physical id: 2 logical name: input0 logical name: /dev/input/event0 capabilities: platform *-input:1 product: Lid Switch physical id: 3 logical name: input1 logical name: /dev/input/event1 capabilities: platform *-input:2 product: Intel HID events physical id: 4 logical name: input17 logical name: /dev/input/event9 capabilities: platform *-input:3 product: ThinkPad Extra Buttons physical id: 5 logical name: input18 logical name: /dev/input/event10 capabilities: platform *-input:4 product: SYNA8007:00 06CB:CD8C Mouse physical id: 6 logical name: input19 logical name: /dev/input/event4 logical name: /dev/input/mouse0 capabilities: i2c *-input:5 product: Power Button physical id: 7 logical name: input2 logical name: /dev/input/event2 capabilities: platform *-input:6 product: SYNA8007:00 06CB:CD8C Touchpad physical id: 8 logical name: input20 logical name: /dev/input/event5 logical name: /dev/input/mouse1 capabilities: i2c *-input:7 product: Video Bus physical id: 9 logical name: input22 logical name: /dev/input/event11 capabilities: platform *-input:8 product: sof-hda-dsp Mic physical id: a logical name: input23 logical name: /dev/input/event12 *-input:9 product: sof-hda-dsp Headphone physical id: b logical name: input24 logical name: /dev/input/event13 *-input:10 product: sof-hda-dsp HDMI/DP,pcm=3 physical id: c logical name: input25 logical name: /dev/input/event14 *-input:11 product: sof-hda-dsp HDMI/DP,pcm=4 physical id: d logical name: input26 logical name: /dev/input/event15 *-input:12 product: sof-hda-dsp HDMI/DP,pcm=5 physical id: e logical name: input27 logical name: /dev/input/event16 *-input:13 product: AT Translated Set 2 keyboard physical id: f logical name: input3 logical name: /dev/input/event3 logical name: input3::capslock logical name: input3::numlock logical name: input3::scrolllock capabilities: i8042 *-input:14 product: TPPS/2 ALPS TrackPoint physical id: 10 logical name: input5 logical name: /dev/input/event6 logical name: /dev/input/mouse2 capabilities: i8042 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 2061684] Re: ULTS 24 linux 6.8.0-22 modules misversioned
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- 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/2061684 Title: ULTS 24 linux 6.8.0-22 modules misversioned Status in linux package in Ubuntu: New Bug description: I get unexpected symbol versioning errors on loading a WiFi module, both built-in and external: This is the built-in version: petal# find /lib/modules/6.8.0-22-generic -name 'rtw88*8821ce*' /lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst petal# dpkg -S /lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst linux-modules-extra-6.8.0-22-generic: /lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst petal# modinfo /lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst | head -15 filename: /lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst license:Dual BSD/GPL description:Realtek 802.11ac wireless 8821ce driver author: Realtek Corporation srcversion: D25FEEBE76FF505B9FB2F23 alias: pci:v10ECdC821sv*sd*bc*sc*i* alias: pci:v10ECdB821sv*sd*bc*sc*i* depends:rtw88_pci,rtw88_8821c retpoline: Y intree: Y name: rtw88_8821ce vermagic: 6.8.0-22-generic SMP preempt mod_unload modversions sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:6B:5D:B5:AB:9C:C5:55:DE:5D:86:F6:60:36:C5:0D:F0:A3:E2:6D:37 petal# journalctl --since 'Apr 14 15:20:00' --grep rtw _TRANSPORT=kernel |& head -10 Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version of symbol ieee80211_connection_loss Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol ieee80211_connection_loss (err -22) Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version of symbol ieee80211_report_wowlan_wakeup Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol ieee80211_report_wowlan_wakeup (err -22) Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version of symbol ieee80211_txq_get_depth Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol ieee80211_txq_get_depth (err -22) Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version of symbol ieee80211_probereq_get Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol ieee80211_probereq_get (err -22) Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version of symbol ieee80211_iterate_stations_atomic Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol ieee80211_iterate_stations_atomic (err -22) petal# grep ieee80211_txq_get_depth /lib/modules/6.8.0-22-generic/modules.symbols alias symbol:ieee80211_txq_get_depth mac80211 petal# find /lib/modules/6.8.0-22-generic -name 'mac80211.ko*' /lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst petal# dpkg -S /lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst linux-modules-extra-6.8.0-22-generic: /lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst petal# modinfo /lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst | head -14 filename: /lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst license:GPL description:IEEE 802.11 subsystem srcversion: B64ACC886876782FBE75414 depends:cfg80211,libarc4 retpoline: Y intree: Y name: mac80211 vermagic: 6.8.0-22-generic SMP preempt mod_unload modversions sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:6B:5D:B5:AB:9C:C5:55:DE:5D:86:F6:60:36:C5:0D:F0:A3:E2:6D:37 sig_hashalgo: sha512 signature: 03:6C:13:64:42:90:35:16:C4:D7:5A:CD:DB:46:BC:7A:0C:7A:29:8C: That looks like to me a packaging error, but then I compiled also an unofficial version of the driver from sources: petal# git remote -v origin https://github.com/lwfinger/rtw88 (fetch) origin https://github.com/lwfinger/rtw88 (push) petal# ls -ld rtw_8821ce.ko -rw--- 1 root src 609816 Apr 14 21:57 rtw_8821ce.ko petal# modinfo rtw_8821ce.ko filename: /usr/src/rtw88_lwfinger/rtw_8821ce.ko license:Dual BSD/GPL description:Realtek 802.11ac wireless 8821ce driver author: Realtek Corporation srcversion: B84BA04B6691B1F18054301 alias: pci:v10ECdC821sv*sd*bc*sc*i* alias: pci:v10ECdB821sv*sd*bc*sc*i* depends:rtw_pci,rtw_8821c retpoline: Y name: rtw_8821ce vermagic:
[Kernel-packages] [Bug 177235] Mutual Business Partnership
-- 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/177235 Title: slow USB 2.0 drive: it's mounted as USB 1.0, not USB 2.0! Status in linux package in Ubuntu: Incomplete Bug description: In gutsy 7.10 dist-upgraded to the max: Ubuntu 64-bit sometimes does not mount USB 2.0 devices as 2.0. 1) plugin in the USB drive 2) mount it if not automounted (sometimes it doesn't) 3) right-click, properties in nautilus, go to drive tab, see speed "12 Mbps" 4) umount it, unplug it 5) sudo rmmod ehci_hcd 6) plugin the USB drive 7) sudo modprobe ehci_hcd 8) mount it if not automounted 9) right-click, properties in nautilus, go to drive tab, see speed "480 Mbps" Something is horribly wrong at recognizing the proper USB speed mode of external drives. From /var/log/messages: note how the first time the drive is mounted properly as high speed, the second time as slow, then as high speed again with the trick of modprobe'ing the ehci_hcd driver. Somehow, the second time the driver sees the same USB hard drive, it fails to recognize it as USB 2.0. (when I modprobe the driver, the USB mouse and keyboard are also recognized, don't be confused by these). If you need more info let me know. Dec 18 11:46:50 instar kernel: [1089450.444192] usb 1-2: USB disconnect, address 3 Dec 18 11:47:23 instar kernel: [1089483.715043] ehci_hcd :00:1d.7: remove, state 4 Dec 18 11:47:23 instar kernel: [1089483.715053] usb usb5: USB disconnect, address 1 Dec 18 11:47:23 instar kernel: [1089483.719139] ehci_hcd :00:1d.7: USB bus 5 deregistered Dec 18 11:47:23 instar kernel: [1089483.720334] ACPI: PCI interrupt for device :00:1d.7 disabled Dec 18 11:47:45 instar kernel: [1089505.912002] usb 1-2: new full speed USB device using uhci_hcd and address 4 Dec 18 11:47:45 instar kernel: [1089506.134623] usb 1-2: configuration #1 chosen from 1 choice Dec 18 11:47:45 instar kernel: [1089506.137630] scsi7 : SCSI emulation for USB Mass Storage devices Dec 18 11:47:50 instar kernel: [1089511.132544] scsi 7:0:0:0: Direct-Access SEAGATE ST3320820A 3.AA PQ: 0 ANSI: 2 Dec 18 11:47:50 instar kernel: [1089511.137515] sd 7:0:0:0: [sde] 625142448 512-byte hardware sectors (320073 MB) Dec 18 11:47:50 instar kernel: [1089511.142502] sd 7:0:0:0: [sde] Write Protect is off Dec 18 11:47:50 instar kernel: [1089511.147491] sd 7:0:0:0: [sde] 625142448 512-byte hardware sectors (320073 MB) Dec 18 11:47:50 instar kernel: [1089511.152399] sd 7:0:0:0: [sde] Write Protect is off Dec 18 11:47:50 instar kernel: [1089511.152410] sde: sde1 Dec 18 11:47:50 instar kernel: [1089511.171501] sd 7:0:0:0: [sde] Attached SCSI disk Dec 18 11:47:50 instar kernel: [1089511.171542] sd 7:0:0:0: Attached scsi generic sg5 type 0 Dec 18 11:48:12 instar kernel: [1089532.675957] ACPI: PCI Interrupt :00:1d.7[A] -> GSI 20 (level, low) -> IRQ 20 Dec 18 11:48:12 instar kernel: [1089532.677029] ehci_hcd :00:1d.7: EHCI Host Controller Dec 18 11:48:12 instar kernel: [1089532.677207] ehci_hcd :00:1d.7: new USB bus registered, assigned bus number 5 Dec 18 11:48:12 instar kernel: [1089532.677244] ehci_hcd :00:1d.7: debug port 1 Dec 18 11:48:12 instar kernel: [1089532.677262] ehci_hcd :00:1d.7: irq 20, io mem 0xffafbc00 Dec 18 11:48:12 instar kernel: [1089532.682397] ehci_hcd :00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 Dec 18 11:48:12 instar kernel: [1089532.682516] usb usb5: configuration #1 chosen from 1 choice Dec 18 11:48:12 instar kernel: [1089532.682548] hub 5-0:1.0: USB hub found Dec 18 11:48:12 instar kernel: [1089532.682559] hub 5-0:1.0: 8 ports detected Dec 18 11:48:12 instar kernel: [1089533.022143] usb 5-2: new high speed USB device using ehci_hcd and address 2 Dec 18 11:48:12 instar kernel: [1089533.154844] usb 5-2: configuration #1 chosen from 1 choice Dec 18 11:48:12 instar kernel: [1089533.155098] scsi8 : SCSI emulation for USB Mass Storage devices Dec 18 11:48:13 instar kernel: [1089533.521886] usb 1-2: USB disconnect, address 4 Dec 18 11:48:13 instar kernel: [1089533.649595] usb 2-1: USB disconnect, address 3 Dec 18 11:48:13 instar kernel: [1089533.889048] usb 2-1: new low speed USB device using uhci_hcd and address 4 Dec 18 11:48:13 instar kernel: [1089534.065223] usb 2-1: configuration #1 chosen from 1 choice Dec 18 11:48:13 instar kernel: [1089534.082362] input: Logitech USB Receiver as /class/input/input12 Dec 18 11:48:13 instar kernel: [1089534.082393] input: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-:00:1d.1-1 Dec 18 11:48:13 instar kernel: [1089534.111043] /build/buildd/linux-source-2.6.22-2.6.22/drivers/hid/usbhid/hid-core.c: Fixing up Logitech keyboard report descriptor Dec 18 11:48:13 instar kernel: [1089534.111596] input: Logitech USB Receiver as
[Kernel-packages] [Bug 1049466] Mutual Business Partnership
-- 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/1049466 Title: Need support of Ralink RT3290 wifi support Status in Linux: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Precise: Invalid Status in linux-firmware source package in Precise: Fix Released Status in linux source package in Quantal: Invalid Status in linux-firmware source package in Quantal: Won't Fix Status in linux source package in Raring: Fix Released Status in linux-firmware source package in Raring: Fix Released Status in linux package in Baltix: Opinion Status in linux package in Gentoo Linux: New Bug description: RT3290 wifi chip is becoming common on consumer notebooks. Its support starts from 3.6 so support on 12.10 may need lbm-cw. commit a89534edaaa7008992b878680490e9b02a665563 Author: Woody Hung Date: Wed Jun 13 15:01:16 2012 +0800 rt2x00 : RT3290 chip support v4 This patch support the new chipset rt3290 wifi implementation in rt2x00. It initailize the related mac, bbp and rf register in startup phase. And this patch modify the efuse read/write method for the different efuse data offset of rt3290. Signed-off-by: Woody Hung Signed-off-by: John W. Linville To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1049466/+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 2052827] Re: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2052827 Title: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034981 Backport upstream commit: 873f64b791a2 mm/memcontrol.c: remove the redundant updating of stats_flush_threshold to jammy. [Impact] Remove the redundant updating of stats_flush_threshold. If the global var stats_flush_threshold has exceeded the trigger value for __mem_cgroup_flush_stats, further increment is unnecessary. This is targeting Sapphire Rapids platforms. [Fix] Upstream commit 873f64b791a2 fixes this issue. The fix involves not updating the status after a certain threshold has been hit as it is unnecessary. [Test Plan] I have tested the changes, and hit no regressions. [Where problems could occur] As the change has been upstream since 6.0-rc1, and is reducing a stats update which isn't needed, the change for regressions should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052827/+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 2053152] Re: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2053152 Title: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034984 [Description] When running UnixBench/Execl throughput case, false sharing is observed due to frequent read on base_addr and write on free_bytes, chunk_md. UnixBench/Execl represents a class of workload where bash scripts are spawned frequently to do some short jobs. It will do system call on execl frequently, and execl will call mm_init to initialize mm_struct of the process. mm_init will call __percpu_counter_init for percpu_counters initialization. Then pcpu_alloc is called to read the base_addr of pcpu_chunk for memory allocation. Inside pcpu_alloc, it will call pcpu_alloc_area to allocate memory from a specified chunk. This function will update "free_bytes" and "chunk_md" to record the rest free bytes and other meta data for this chunk. Correspondingly, pcpu_free_area will also update these 2 members when free memory. In current pcpu_chunk layout, `base_addr' is in the same cache line with `free_bytes' and `chunk_md', and `base_addr' is at the last 8 bytes. This patch moves `bound_map' up to `base_addr', to let `base_addr' locate in a new cacheline. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Platform-Independent Date HW is expected at Canonical: Component(s): Performance and Scalability [Software Information] Target Version: 23.10 Target Kernel: 6.5 Commit IDs: 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure to reduce false sharing External Links: [Business Justification] [Testing guidance] [External ID] OSVE-5160 The following requested patch has been applied upstream for v6.5-rc1: - 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure to reduce false sharing https://github.com/torvalds/linux/commit/3a6358c0dbe6a286a4f4504ba392a6039a9fbd12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053152/+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 2053069] Re: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2053069 Title: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034983 [Description] When running UnixBench/shell1 cases, we observed high false sharing for accessing i_mmap against i_mmap_rwsem. The patch places the i_mmap and i_mmap_rwsem in separate cache lines to avoid this false sharing problem. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): DNP Date HW is expected at Canonical: Component(s): Performance and Scalability [Software Information] Target Version: 23.10 Target Kernel: TBD Commit IDs: aee79d4e5271 fs/address_space: add alignment padding for i_map and i_mmap_rwsem to mitigate a false sharing. External Links: [Business Justification] [Testing guidance] [External ID] OSVE-5159 Here's the commit ID: aee79d4e5271cee4ffa89ed830189929a6272eb8 https://github.com/torvalds/linux/commit/aee79d4e5271cee4ffa89ed830189929a6272eb8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053069/+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 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: In Progress Bug description: [Impact] * Issue is causing transmit hang on E810 ports with bonding enabled. * Based on the provided logs, TX hang can last for even a couple of minutes, but in most scenarios, the network will be recovered after the ice driver performs a PF reset (TX hang handler routine). * Originally, the issue was observed during Tempest tests on a newly created OpenStack cluster, resulting in a lack of certification. [Fix] * Initially, a workaround has been proposed by Intel engineers to disable LAG initialization [1]. This change has been tested in an environment where reproduction is easily achieved. After multiple iterations, no reproduction has been observed. * Shortly after, Intel proposed a patch [2] to disable LAG initialization if NVM does not expose proper capabilities. [Test Plan] * To reproduce the issue, over a 20-node cluster was used with Ceph-based storage. The problem could sometimes manifest while deploying a cluster or after the cluster was already deployed during the Tempest test run. * The issue could appear on a random node, making reproduction hard to achieve. * Multiple stress tests on single host with similar configuration did not trigger a reproduction. [Where problems could occur] * All ice drivers with ice_lag_event_handler registered can expose the issue. This handler is not implemented in 20.04 * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this capability will be released. Although potentialy issue is caused by using features without proper FW support [2], we want to take a closer look once NVMs with proper support are introduced. [1] - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40 [2] - https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html 4d50fcdc2476eef94c14c6761073af5667bb43b6 [Other Info] * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice driver backported from mainline kernel from before patch [2] was added. * Original description of the case below: I'm having issues with an Intel E810-XXV card on a Dell server under Ubuntu Jammy. Details: - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results. - using a bond over the two ports of the same card, at 25Gbps to two different switches, bond is using LACP with hash layer3+4 and fast timeout. But I believe the bug is not directly related to bonding as the problem seems to be in the interface. - machine installed by maas. No issues during installation, but at that time bond is not formed yet, later when linux is booted, the bond is formed and works without issues for a while - it works for about 2 to 3 hours fine, then the issue starts (may or may not be related to network load, but it seems that it is triggered by some tests that I run after openstack finishes installing) - one of the legs of the bond freezes and everything that would go to that lag is discarded, in and out, ping to random external hosts start losing every second packet - after some time you can see on the kernel log messages about "NETDEV WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack trace - the switch does log that the bond is flapping --- ProblemType:
[Kernel-packages] [Bug 1971699] Re: disable Intel DMA remapping by default
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/1971699 Title: disable Intel DMA remapping by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+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 2049689] Re: partprobe is broken on empty loopback device
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2
verification-needed-jammy-linux-nvidia-tegra-igx
--
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/2049689
Title:
partprobe is broken on empty loopback device
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
SRU Justification:
[Impact]
* BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
but now returns EINVAL, breaking partprobe due to commit
"block: don't add or resize partition on the disk with GENHD_FL_NO_PART"
introduced in mantic 6.5.0-17 and jammy 5.15.0-94.
[Fix]
* backport commit
"block: Move checking GENHD_FL_NO_PART to bdev_add_partition()"
[Test Plan]
* dd if=/dev/zero of=/tmp/foo bs=1M count=50
* partprobe $(losetup --find --show /tmp/foo)
Before the fix this fails.
After the fix it should work.
[Where problems could occur]
* We may see issues on disk partitions operations.
Old description:
This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic
5.15.0-94.104).
Do this:
# dd if=/dev/zero of=/tmp/file bs=1M count=50
# partprobe "$(losetup --show --find /tmp/file)"
Notice this very odd error message:
Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
/dev/loop2 have been written, but we have been unable to inform the
kernel of the change, probably because it/they are in use. As a
result, the old partition(s) will remain in use. You should reboot
now before making further changes.
That's a result of an ioctl changing its error code in an incompatible
way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
partprobe.
5.15.0.91.88:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or
address)
5.15.0.94.91:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)
This is a userspace API break which impacts GNU parted and util-linux
(as confirmed by the util-linux maintainer).
This issue was discovered as part of Cockpit CI here:
https://github.com/cockpit-project/bots/pull/5793
This issue is being discussed on LKML here (with a patch likely to
land soon): https://lkml.org/lkml/2024/1/15/147
lsb_release -rd:
Description: Ubuntu 22.04.3 LTS
Release: 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049689/+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 2054094] Re: linux-tools-common: man page of usbip[d] is misplaced
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2054094 Title: linux-tools-common: man page of usbip[d] is misplaced Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] Just try man uspip, it doesn't work, because the man page file is at /usr/share/man/man1/usbipd.8.gz ^ ^^^ Looks wrong :) [Test Case] $ sudo apt install linux-tools-common $ man usbip No manual entry for usbip [Where Problems Could Occur] Manpage packaging change, no runtime impact expected. [Additional Description] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-tools-common 5.15.0-94.104 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 3196 F pulseaudio /dev/snd/pcmC0D0p: dmitry 3196 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 16 12:37:42 2024 InstallationDate: Installed on 2022-04-19 (668 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 15 9500 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=UUID=21336f25-776c-4f5f-b70c-8cf96f1f0d22 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.5.0-17-generic N/A linux-backports-modules-6.5.0-17-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.26 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-21 (543 days ago) dmi.bios.date: 08/15/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.1:bd08/15/2023:br1.24:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054094/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2044131] Re: i915 regression introduced with 5.5 kernel
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2044131 Title: i915 regression introduced with 5.5 kernel Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.15 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-hwe-5.15 source package in Jammy: Invalid Status in linux source package in Mantic: Fix Released Status in linux-hwe-5.15 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-hwe-5.15 source package in Noble: Invalid Bug description: [ Impact ] Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks which have been proven invalid for at least some hardware setups. A user trying to run Focal with HWE 5.15 kernel is not able to get any video output. After going through bisection between 5.4 and 5.5 this commit was identified. Reverting it on top of Focal HWE kernel fixes the issue. The issue has been addressed upstream in DRM tree (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d). dmesg and lspci from the affected configuration are attached to this bug. [ Test Plan ] 1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or higher. 2. Wait until boot finishes and see the blank screen. Actual result: there is no video output visible. Expected result: normal boot process should be visible (e.g. splash), then GUI should appear. [ Where problem could occur ] This bug was a result of assumptions in the checks that turned out to be not valid for some hardware. The checks were removed from global intel_mode_valid function and moved into connector specific .mode_valid() hooks, entirely skiping BXT/GLK DSI connectors. This should keep the checks where appropriate and skip for hardware that does not comply to them. [ Other info ] Original bug description: There is a regression preventing a user to upgrade from 5.4 kernel to anything that's higher than 5.5. When using such kernel the image orientation is wrong (rotated by 90°C). Also the kernel log contains: wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06 wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 24.8.0, H2C version 12 wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 80x25 wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga console wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory information wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:o> wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v> wrz 15 09:19:49 desktop kernel: wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.> wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]' (full stack trace attached) The video hardware in use is: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 [8086:3185] (rev 06) (prog-if 00 [VGA controller]) (...) Kernel driver in use: i915 Kernel modules: i915 The user wanted to upgrade from bionic to focal with HWE kernel (they needed it due to some networking hardware they wanted to have supported by the newer kernel). The user was testing mainline stable kernels and noticed that the last working kernel was the 5.4 series, while anything starting from 5.5 and above is BROKEN (symptoms as described in the first paragraph above). Together with the user we have run a bisection between v5.4
[Kernel-packages] [Bug 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2045561 Title: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Released Bug description: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux- virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from being configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a built-in, and on SUSE it is a module installed by default. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this module installed and loaded, the directory won't be there. Once enabled, it will be there. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if dmi-sysfs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name dmi-sysfs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045561/+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 2054699] Re: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2054699 Title: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Bug description: This is a public version of https://bugs.launchpad.net/bugs/2044822 SRU Justification: [Impact] Fix tsc clocksource on 4 sockets x86 servers was wrongly judged as 'unstable' by 'jiffies' and other watchdogs, and disabled [Fix] cherry-pick 233756a640be x86/tsc: Extend watchdog check exemption to 4-Sockets platform from upstream fixes this [Test Plan] This has been tested by intel, and has been upstreamed for a while. [Where problems could occur] This is a fairly narrow change, and extends a behaviour correction to cover up to 4-socket machines, rather than just 2 socket machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054699/+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 2048404] Re: Don't WARN_ON_ONCE() for a broken discovery table
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2
verification-needed-jammy-linux-nvidia-tegra-igx
--
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/2048404
Title:
Don't WARN_ON_ONCE() for a broken discovery table
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Won't Fix
Bug description:
SRU Justification
[Impact]
perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
The kernel warning message is triggered, when SPR MCC is used.
[ 17.945331] [ cut here ]
[ 17.946305] WARNING: CPU: 65 PID: 1 at
arch/x86/events/intel/uncore_discovery.c:184
intel_uncore_has_discovery_tables+0x4c0/0x65c
[ 17.946305] Modules linked in:
[ 17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
5.4.17-2136.313.1-X10-2c+ #4
It's caused by the broken discovery table of UPI.
The discovery tables are from hardware. Except for dropping the broken
information, there is nothing Linux can do. Using WARN_ON_ONCE() is
overkilled.
Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
is dropped and the reason.
[Fix]
Commit 5d515ee40cb57ea5331998f27df7946a69f14dc3 ('perf/x86/uncore:
Don't WARN_ON_ONCE() for a broken discovery table')
[Test]
AWS tested
[Regression potential]
Low regression potential. Only the code that prints the warning has
been changed.
[Other Info]
SF: #00347830
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048404/+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 2052005] Re: Validate connection interval to pass Bluetooth Test Suite
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2052005 Title: Validate connection interval to pass Bluetooth Test Suite Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] Ubuntu doesn't pass Bluetooth Test Suite to get Bluetooth certified. [Fix] Validate max connection interval to pass test case "GAP/CONN/CPUP/BV-05-C 'Connection Parameter Update Procedure Invalid Parameters Central Responder'" [Test] Run the test suite. With the patch applied the case is passed. [Where problems could occur] If any device requires setting a wrong interval to function properly, this might affect those devices in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052005/+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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2051050 Currently this patch is in the linux-next, and will be in the mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble kernel, Noble kernel will have this patch automatically. [Impact] In the gnome audio setting, if we adjust balancing setting, it doesn't work at all on a Dell machine with cirrus codec, that is because with the current driver, the exported amixer controls can't be handled by pulseaudio. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booted with the patched kernel, move the bar to the left or right to adjust the balance, we could hear the sound from left channel or right channel accordingly. [Where problems could occur] This change will not create "Master Volume" amixer controls, probably will make the audio control malfunction, that is we couldn't control playback or capture volume correctly, but this regression possibility is very low, we already tested the patch on the machines with cirrus codec, they all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2052817] Re: cpufreq: intel_pstate: Enable HWP IO boost for all servers
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2052817 Title: cpufreq: intel_pstate: Enable HWP IO boost for all servers Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: This is a public version of https://bugs.launchpad.net/bugs/2009321 Backport cpufreq: intel_pstate: Enable HWP IO boost for all servers [upstream 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 (merged in 6.4)] to jammy. [Impact] Currently there is a CPU model check for Skylake desktop and server along with the ACPI PM profile for performance and enterprise servers to enable IO boost. Patch removes the CPU model check, so that all current server models enable HWP IO boost by default. The HWP IO boost results in improvements for IO performance on both Ice Lake and Sapphire Rapid servers. Phoronix review: https://www.phoronix.com/news/Intel-ICL-SPR-IO-Perf- Boost Upstream review Link: https://lore.kernel.org/linux- pm/20230303041411.3161780-1-srinivas.pandruv...@linux.intel.com/ [Fix] Upstream patch: cpufreq: intel_pstate: Enable HWP IO boost for all servers 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 was merged to fix this. This will be back porting it to jammy. [Test Plan] I have tested this code, as has Intel. [Where problems could occur] The risk for regression is low. The change is fairly narrow, and has been upstreamed for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052817/+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 2053251] Re: performance: Scheduler: ratelimit updating of load_avg
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2053251 Title: performance: Scheduler: ratelimit updating of load_avg Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Bug description: This is a public version of https://bugs.launchpad.net/bugs/2040026 [Description] Improve cache bouncing on tg->load_avg [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Sapphire Rapids Date HW is expected at Canonical: Component(s): Perf-Scalability Scheduler [Software Information] Target Version: 24.04 Target Kernel: TBD Commit IDs: 1528c661c24b sched/fair: Ratelimit update to tg->load_avg External Links: [Business Justification] [Testing guidance] [External ID] LFE-7154 Here's the commit ID:1528c661c24b407e92194426b0adbb43de859ce0 https://github.com/torvalds/linux/commit/1528c661c24b407e92194426b0adbb43de859c0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053251/+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 2054567] Re: Fix bpf selftests build failure after v5.15.139 update
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2054567 Title: Fix bpf selftests build failure after v5.15.139 update Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU justification [Impact] Upstream v5.15.139 (#lp2049432) brought commit "selftests/bpf: Test tail call counting with bpf2bpf and data on stack" that affects one of the bpf kselftests (tailcall_bpf2bpf6). because LIBBPF_OPTS macro does not exists, it does not compile. Error below. [Fix] Initially, I thought cherry-picking commit "libbpf: Rename DECLARE_LIBBPF_OPTS into LIBBPF_OPTS" would be the best, but upstream stable just reverted the commit that broke it. Hence the fix consists of cherry-picking this commit from stable upstream 5.15.49: Commit 62900d358c48 (Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on stack") [Test] This should be solved soon, but compileselftests debian rule does not compile bpf selftests. I tested it by using our regression testing tooling, but same results can be achieved by running: $ make -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all KDIR=/usr/src/linux-headers-5.15.0--generic from the linux tree directory Without the fix, it fails to compile: /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c: In function ‘test_tailcall_bpf2bpf_6’: /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:9: warning: implicit declaration of function ‘LIBBPF_OPTS’; did you mean ‘LIBBPF_API’? [-Wimplicit-function-declaration] 822 | LIBBPF_OPTS(bpf_test_run_opts, topts, | ^~~ | LIBBPF_API /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21: error: ‘bpf_test_run_opts’ undeclared (first use in this function) 822 | LIBBPF_OPTS(bpf_test_run_opts, topts, | ^ /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21: note: each undeclared identifier is reported only once for each function it appears in /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:40: error: ‘topts’ undeclared (first use in this function) 822 | LIBBPF_OPTS(bpf_test_run_opts, topts, | ^ /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:823:17: error: expected expression before ‘.’ token 823 | .data_in = _v4, | ^ make[1]: *** [Makefile:471: /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tailcalls.test.o] Error 1 make: *** [Makefile:172: all] Error 2 With the fix, it compiles. [Regression potential] The only place this is being used is selftests, so the risk is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054567/+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 2055685] Re: Cranky update-dkms-versions rollout
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2055685 Title: Cranky update-dkms-versions rollout Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Bug description: SRU Justification [Impact] Having a common file for dkms-versions between main kernels and derivatives causes a lot of conflicts during rebase. Solution is to have a dkms-versions per kernels, under debian./dkms-version. While at it, instead of running ./update-dkms-version script, cranky update-dkms-versions was introduced. This is not used in xenial, therefore for xenial we only replaced debian/dkms-versions with debian./dkms-versions [Fix] This is needed only in the main kernels. 1. remove update-dkms-version script (where needed), in xenial:linux we don't have it 2. rename debian/dkms-version with debian.master/dkms-versions 3. Replace debian/dkms-versions references in debian scripts and rules with $(DEBIAN)/dkms-versions Note for derivatives: These changes will be inherited from the parent during cranky rebase. The only change to the cranky process is: instead of using ./update-dkms-versions script, cranky-update-dkms-versions should be used [Test] Build test on cbd. No issue found. [Regression pottential] Owners have tried this last cycle in derivatives and no issues were found. We may see build failures due to wrong dkms versions, but it will be fixed along the way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055685/+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 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2054809 Title: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Released Bug description: SRU Justification [Impact] The erofs.ko module (CONFIG_EROFS) is currently shipped in linux- modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from using the erofs filesystem. Erofs is a modern alternative to squashfs that supports more features such as ACLs. The following LPC presentation has more details on erofs and its advantages over squashfs: https://youtu.be/jt-hp_LtSBc. A user launching a VM using the linux-virtual kernel image is not able to mount erofs filesystems due to the lack of this kconfig. We make extensive use of erofs in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a (core) module that is built by default. To verify this works, it is sufficient to create an erofs filesystem with mkfs.erofs and verify that it can be mounted: $ mkdir sources $ echo abcde > sources/file $ mkfs.erofs erofs sources $ mount erofs mnt --mkdir $ ls mnt file Without this module installed and loaded, the mount will fail. Once enabled, it will succeed. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if erofs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name erofs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+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 2055468] Re: apply nvidia-tegra patches 2024 Feb 6-29
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2055468 Title: apply nvidia-tegra patches 2024 Feb 6-29 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2055468/+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 2058550] Re: apply nvidia-tegra patches 2024 Mar 9-20
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2058550 Title: apply nvidia-tegra patches 2024 Mar 9-20 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2058550/+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 2056143] Re: block/loop: No longer allows to create partitions
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2056143 Title: block/loop: No longer allows to create partitions Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: == SRU Justification == -- Impact -- In 22.04/Jammy with the GA 5.15 kernel there was an upstream change preventing partition table operations when GENHD_FL_NO_PART is set. 1a721de8489f "block: don't add or resize partition on the disk with GENHD_FL_NO_PART" Beside of changing return codes and breaking some user-space that way this also causes loop block devices to no longer be able to have partitions manually created. This is because the loop block driver uses GENHD_FL_NO_PART to prevent active partition scans. -- Fix -- This was changed in 5.19 (and thus Mantic is not affected) by introducing a separate flag to prevent those scans: b9684a71fca7 "block, loop: support partitions without scanning" The fix depends on a larger rewrite so it cannot be simply picked. The biggest change from the original is moving the check for the new flag into a helper function in genhd.h which checks whether a disk should be scanned for partitions. That function was dropped with the upstream rewrite and checking moved into the loop driver directly. But it felt like adjusting the helper was the better approach. Note: The upstream patch has a follow-up change submitted: 748008e1da92 "block: don't add partitions if GD_SUPPRESS_PART_SCAN is set" We do _NOT_ need that in Jammy/5.15 because block/partitions/core.c: blk_add_partitions() checks disk_part_scan_enabled() which was where we added the check for the backport instead of modifying disk_scan_partitions() directly. -- Testcase -- $ fallocate -l 1G /tmp/blob $ LOOPDEV=$(sudo losetup --find --show /tmp/blob) $ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt mkpart primary 0% 100% -- Regression Potential -- If things go wrong it might be other devices which no longer get scanned automatically or other issues with the loop block driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056143/+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 2056594] Re: apply nvidia-tegra patches 2024 Mar 8
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2056594 Title: apply nvidia-tegra patches 2024 Mar 8 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056594/+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 2056486] Re: apply nvidia-tegra patches 2024 Mar 1-7
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2056486 Title: apply nvidia-tegra patches 2024 Mar 1-7 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056486/+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 2055686] Re: Drop ABI checks from kernel build
This bug is awaiting verification that the linux-nvidia-tegra- igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra- igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia- tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx -- 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/2055686 Title: Drop ABI checks from kernel build Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Bug description: Drop the internal checks on the kernel ABI, module lists, et al. These checks are now applied after the fact by the workflow manager. This allows us to validate change after the builds complete so we do no waste builds which were correct but not annotated at upload time. NOTE: we still record the ABI data and publish it in linux-buildinfo files. These are used to perform the external validation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055686/+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 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin2004 -- 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/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+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 2061685] [NEW] ULTS weird behaviour 'screen' 'tmux' (likely kernel error)
Public bug reported: It is hard to provide evidence but the story is: * I start 'tmux' or 'screen'. * Everything works nicely until later, after I switch tabs/windows within them. * Then all my inputs behave as if I kept pressing the 'Ctrl' key, so when I type "v" what is actually receive is Ctrl-v. * If I reboot into kernel 5.15.0-102 with the same "root", that is the same 'tmux' and 'screen' binaries, this does not happen. * Apparently it does not happen inside an X terminal like 'xterm' or 'sakura', so I guess it is some weird bug in the console tty "discipline" (to use an old UNIX term). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel modules packaging -- 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/2061685 Title: ULTS weird behaviour 'screen' 'tmux' (likely kernel error) Status in linux package in Ubuntu: New Bug description: It is hard to provide evidence but the story is: * I start 'tmux' or 'screen'. * Everything works nicely until later, after I switch tabs/windows within them. * Then all my inputs behave as if I kept pressing the 'Ctrl' key, so when I type "v" what is actually receive is Ctrl-v. * If I reboot into kernel 5.15.0-102 with the same "root", that is the same 'tmux' and 'screen' binaries, this does not happen. * Apparently it does not happen inside an X terminal like 'xterm' or 'sakura', so I guess it is some weird bug in the console tty "discipline" (to use an old UNIX term). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061685/+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 2061684] [NEW] ULTS 24 linux 6.8.0-22 modules misversioned
Public bug reported: I get unexpected symbol versioning errors on loading a WiFi module, both built-in and external: This is the built-in version: petal# find /lib/modules/6.8.0-22-generic -name 'rtw88*8821ce*' /lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst petal# dpkg -S /lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst linux-modules-extra-6.8.0-22-generic: /lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst petal# modinfo /lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst | head -15 filename: /lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst license:Dual BSD/GPL description:Realtek 802.11ac wireless 8821ce driver author: Realtek Corporation srcversion: D25FEEBE76FF505B9FB2F23 alias: pci:v10ECdC821sv*sd*bc*sc*i* alias: pci:v10ECdB821sv*sd*bc*sc*i* depends:rtw88_pci,rtw88_8821c retpoline: Y intree: Y name: rtw88_8821ce vermagic: 6.8.0-22-generic SMP preempt mod_unload modversions sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:6B:5D:B5:AB:9C:C5:55:DE:5D:86:F6:60:36:C5:0D:F0:A3:E2:6D:37 petal# journalctl --since 'Apr 14 15:20:00' --grep rtw _TRANSPORT=kernel |& head -10 Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version of symbol ieee80211_connection_loss Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol ieee80211_connection_loss (err -22) Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version of symbol ieee80211_report_wowlan_wakeup Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol ieee80211_report_wowlan_wakeup (err -22) Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version of symbol ieee80211_txq_get_depth Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol ieee80211_txq_get_depth (err -22) Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version of symbol ieee80211_probereq_get Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol ieee80211_probereq_get (err -22) Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version of symbol ieee80211_iterate_stations_atomic Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol ieee80211_iterate_stations_atomic (err -22) petal# grep ieee80211_txq_get_depth /lib/modules/6.8.0-22-generic/modules.symbols alias symbol:ieee80211_txq_get_depth mac80211 petal# find /lib/modules/6.8.0-22-generic -name 'mac80211.ko*' /lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst petal# dpkg -S /lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst linux-modules-extra-6.8.0-22-generic: /lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst petal# modinfo /lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst | head -14 filename: /lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst license:GPL description:IEEE 802.11 subsystem srcversion: B64ACC886876782FBE75414 depends:cfg80211,libarc4 retpoline: Y intree: Y name: mac80211 vermagic: 6.8.0-22-generic SMP preempt mod_unload modversions sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:6B:5D:B5:AB:9C:C5:55:DE:5D:86:F6:60:36:C5:0D:F0:A3:E2:6D:37 sig_hashalgo: sha512 signature: 03:6C:13:64:42:90:35:16:C4:D7:5A:CD:DB:46:BC:7A:0C:7A:29:8C: That looks like to me a packaging error, but then I compiled also an unofficial version of the driver from sources: petal# git remote -v origin https://github.com/lwfinger/rtw88 (fetch) origin https://github.com/lwfinger/rtw88 (push) petal# ls -ld rtw_8821ce.ko -rw--- 1 root src 609816 Apr 14 21:57 rtw_8821ce.ko petal# modinfo rtw_8821ce.ko filename: /usr/src/rtw88_lwfinger/rtw_8821ce.ko license:Dual BSD/GPL description:Realtek 802.11ac wireless 8821ce driver author: Realtek Corporation srcversion: B84BA04B6691B1F18054301 alias: pci:v10ECdC821sv*sd*bc*sc*i* alias: pci:v10ECdB821sv*sd*bc*sc*i* depends:rtw_pci,rtw_8821c retpoline: Y name: rtw_8821ce vermagic: 6.8.0-22-generic SMP preempt mod_unload modversions So I rebooted into kernel 5.15.0-102 and 'rtw88_8821ce' seems to work as always: petal# modprobe rtw88_8821ce petal# dmesg | tail -3 [81954.635875] rtw_8821ce :01:00.0: sta 22:b0:01:a8:1e:4b with macid 0 left [81954.736381] rtw_8821ce :01:00.0: stop vif 60:e9:aa:a7:9d:31 on port 0 [81984.525318] rtw_8821ce :01:00.0: Firmware version 24.11.0, H2C version 12 I tried to use '--force-vermagic' and '--force-modversion' to see what would happen and
[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Good to know a new kernel is coming out soon to fix the issue. Thank you. Where is the best place to look to see when the patch is released? Many thanks. -- 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/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu Mantic) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: In Progress Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 1930877] Re: oops.kernel.org unusable
Report url http://oops.kernel.org/submitoops.php hasn't been working since 2020. Debian removed it in 2020 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1930877 Title: oops.kernel.org unusable Status in kerneloops package in Ubuntu: Confirmed Bug description: Nothing. Just like debian distribution, this package need to be remove. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1930877/+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 2060984] Re: FFe: New firmware release
nope, that's fine -- 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/2060984 Title: FFe: New firmware release Status in linux-firmware package in Ubuntu: New Bug description: A new upstream release of linux-firmware was tagged on 2024.04.10, this would sync us with that. Changes: - imx: sdma: update firmware to v3.6/v4.6 - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8 - amdgpu: DMCUB updates for various AMDGPU ASICs - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260 - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200 - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B - Montage: update firmware for Mont-TSSE - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops - rtw88: Add RTL8703B firmware v11.0.0 - rtw89: 8922a: add firmware v0.35.18.0 - rtw89: 8852c: update fw to v0.27.56.14 - mekdiatek: Update mt8186 SOF firmware to v2.0.1 - linux-firmware: update firmware for en8811h 2.5G ethernet phy - amdgpu: DMCUB updates for various AMDGPU ASICs - i915: Add DG2 HuC 7.10.15 - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2060984/+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 2061295] Re: No graphical boot with default Kubuntu 24.04
I also have an AMD CPU and I'm using the iGPU, in case that's related. I'm able to boot with 'quiet splash' if I add 'nomodeset', but then have to use a single screen at low res. -- 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/2061295 Title: No graphical boot with default Kubuntu 24.04 Status in linux package in Ubuntu: Confirmed Bug description: I upgraded from 23.10 to 24.04, and with it the new 6.8 kernel. I do not see the Kubuntu EFI logo, and the system never reaches the sddm login screen. I could not switch to a tty to login either. If I boot kernel 6.5 it works as expected. If I remove "quiet splash" from the boot parameters, then kernel 6.8 also boots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 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 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Apr 14 16:08:22 2024 InstallationDate: Installed on 2023-01-16 (454 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-13 (1 days ago) dmi.bios.date: 03/01/2024 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.08 dmi.board.asset.tag: Default string dmi.board.name: B650E PG Riptide WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.08:bd03/01/2024:br5.32:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061295/+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 2056743] Re: Keyboard stops working after suspend on Dell XPS 13
Should have added. I have a Dell laptop. alan: ~ $ inxi -b System: Host: Laptop Kernel: 5.15.0-102-generic x86_64 bits: 64 Desktop: Cinnamon 6.0.4 Distro: Linux Mint 21.3 Virginia Machine: Type: Laptop System: Dell product: Inspiron 5570 v: N/A serial: Mobo: Dell model: 0D65FD v: A00 serial: UEFI: Dell v: 1.14.0 date: 04/06/2023 Battery: ID-1: BAT0 charge: 42.0 Wh (100.0%) condition: 42.0/42.0 Wh (100.0%) CPU: Info: quad core Intel Core i7-8550U [MT MCP] speed (MHz): avg: 790 min/max: 400/4000 Graphics: Device-1: Intel UHD Graphics 620 driver: i915 v: kernel Device-2: Realtek USB Boot type: USB driver: N/A Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.2 Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169 Device-2: Intel Wireless 3165 driver: iwlwifi Device-3: Intel Bluetooth wireless interface type: USB driver: btusb Drives: Local Storage: total: 2.29 TiB used: 62.71 GiB (2.7%) Info: Processes: 313 Uptime: 1h 23m Memory: 15.51 GiB used: 2.45 GiB (15.8%) Shell: Bash inxi: 3.3.13 -- 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/2056743 Title: Keyboard stops working after suspend on Dell XPS 13 Status in linux package in Ubuntu: Confirmed Bug description: The problem occurs with the 5.15.0-102 kernel but not with 5.15.0-100. The issue seems to be identical to the problem reported for 6.7.0 here: https://bbs.archlinux.org/viewtopic.php?id=292203 On the page linked above is says a patch was submitted 2024-01-26 and the problem solved 2024-03-04 in linux 6.7.5 or linux-lts 6.6.17. I'm concerned that this still needs fixing in the 5.xxx kernel branch. Touchpad does not freeze and mouse-control of windows still works, so it's different from a bug reported elsewhere. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-102-generic 5.15.0-102.112 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 Uname: Linux 5.15.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 2494 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 09:54:23 2024 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378 InstallationDate: Installed on 2018-08-31 (2018 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-100-generic root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 1.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.0 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056743/+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 2061295] Re: No graphical boot with default Kubuntu 24.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/2061295 Title: No graphical boot with default Kubuntu 24.04 Status in linux package in Ubuntu: Confirmed Bug description: I upgraded from 23.10 to 24.04, and with it the new 6.8 kernel. I do not see the Kubuntu EFI logo, and the system never reaches the sddm login screen. I could not switch to a tty to login either. If I boot kernel 6.5 it works as expected. If I remove "quiet splash" from the boot parameters, then kernel 6.8 also boots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 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 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Apr 14 16:08:22 2024 InstallationDate: Installed on 2023-01-16 (454 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-13 (1 days ago) dmi.bios.date: 03/01/2024 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.08 dmi.board.asset.tag: Default string dmi.board.name: B650E PG Riptide WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.08:bd03/01/2024:br5.32:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061295/+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 2056743] Re: Keyboard stops working after suspend on Dell XPS 13
I am also having this issue with the keyboard stopping after sleep. 5.15.0-102 kernel. I have found by putting this line in grub I can make it work, however I lose the num lock light, only light on the keyboard. GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.dumbkbd=1 i8042.nomux=1 i8042.noaux=1" I can't get a reliable test deleting one of the 'nomux' or 'noaux', just seems that all 3 make things work. Shouldn't have to patch like this and I would really like the light back on. Do you believe the patch above will fix this too. -- 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/2056743 Title: Keyboard stops working after suspend on Dell XPS 13 Status in linux package in Ubuntu: Confirmed Bug description: The problem occurs with the 5.15.0-102 kernel but not with 5.15.0-100. The issue seems to be identical to the problem reported for 6.7.0 here: https://bbs.archlinux.org/viewtopic.php?id=292203 On the page linked above is says a patch was submitted 2024-01-26 and the problem solved 2024-03-04 in linux 6.7.5 or linux-lts 6.6.17. I'm concerned that this still needs fixing in the 5.xxx kernel branch. Touchpad does not freeze and mouse-control of windows still works, so it's different from a bug reported elsewhere. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-102-generic 5.15.0-102.112 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 Uname: Linux 5.15.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 2494 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 09:54:23 2024 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378 InstallationDate: Installed on 2018-08-31 (2018 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-100-generic root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 1.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.0 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056743/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH
Confirmed on 5.15.0-102 -- 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/2016388 Title: Kernel Panic on shutdown / reboot on NUC8I3BEH Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: In Progress Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 2056666] Re: [RTL8822CE] i could not able to connect my bluetooth headphone or for context any headphone to my ubuntu machine
After some updates on friday, this morning, I was able to connect my headset. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/205 Title: [RTL8822CE] i could not able to connect my bluetooth headphone or for context any headphone to my ubuntu machine Status in bluez package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Bug description: headphone is not showing up in my ubuntu bluetooth so i cant connect my headphone to my computer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 14:10:46 2024 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 82C7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-25-generic root=UUID=bed00b3d-206b-4607-8c0b-63d4f55998ef ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-ADA dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvrE8CN38WW:bd12/05/2022:br1.38:efr1.38:svnLENOVO:pn82C7:pvrLenovoV15-ADA:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoV15-ADA:skuLENOVO_MT_82C7_BU_idea_FM_V15-ADA: dmi.product.family: V15-ADA dmi.product.name: 82C7 dmi.product.sku: LENOVO_MT_82C7_BU_idea_FM_V15-ADA dmi.product.version: Lenovo V15-ADA dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 28:CD:C4:D1:98:3A ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:35089 acl:0 sco:0 events:1074 errors:0 TX bytes:48329 acl:0 sco:0 commands:549 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/205/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
This bug was fixed in the package intel-gpu-tools - 1.28-1ubuntu2 --- intel-gpu-tools (1.28-1ubuntu2) noble; urgency=medium * Fix various intel_gpu_top UI layout issues (LP: #1949314) -- Hector Cao Mon, 15 Apr 2024 10:51:29 +0200 ** Changed in: intel-gpu-tools (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 2060984] Re: FFe: New firmware release
Does this upload fix any release-critical bugs? Since if not, I would prefer to defer this for post-release. We are already in a critical enough state as is. -- 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/2060984 Title: FFe: New firmware release Status in linux-firmware package in Ubuntu: New Bug description: A new upstream release of linux-firmware was tagged on 2024.04.10, this would sync us with that. Changes: - imx: sdma: update firmware to v3.6/v4.6 - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8 - amdgpu: DMCUB updates for various AMDGPU ASICs - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260 - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200 - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B - Montage: update firmware for Mont-TSSE - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops - rtw88: Add RTL8703B firmware v11.0.0 - rtw89: 8922a: add firmware v0.35.18.0 - rtw89: 8852c: update fw to v0.27.56.14 - mekdiatek: Update mt8186 SOF firmware to v2.0.1 - linux-firmware: update firmware for en8811h 2.5G ethernet phy - amdgpu: DMCUB updates for various AMDGPU ASICs - i915: Add DG2 HuC 7.10.15 - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2060984/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2059143] Re: Remove getabis scripts
This bug is awaiting verification that the linux-lowlatency- hwe-5.15/5.15.0-103.113~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- lowlatency-hwe-5.15' to 'verification-done-focal-linux-lowlatency- hwe-5.15'. If the problem still exists, change the tag 'verification- needed-focal-linux-lowlatency-hwe-5.15' to 'verification-failed-focal- linux-lowlatency-hwe-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-lowlatency-hwe-5.15-v2 verification-needed-focal-linux-lowlatency-hwe-5.15 -- 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/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+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 1930877] Re: oops.kernel.org unusable
Agreed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1930877 Title: oops.kernel.org unusable Status in kerneloops package in Ubuntu: Confirmed Bug description: Nothing. Just like debian distribution, this package need to be remove. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1930877/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Hi! Thanks for reporting this. We will do our best to release new kernels in 1-2 days. In the meantime, the meta package will be deleted so that other people do not upgrade to 5.15.0-102. -- 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/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2059143] Re: Remove getabis scripts
This bug is awaiting verification that the linux- azure-5.15/5.15.0-1061.70~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- azure-5.15' to 'verification-done-focal-linux-azure-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux- azure-5.15' to 'verification-failed-focal-linux-azure-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-azure-5.15-v2 verification-needed-focal-linux-azure-5.15 -- 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/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+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 2059143] Re: Remove getabis scripts
This bug is awaiting verification that the linux- gcp-5.15/5.15.0-1056.64~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- gcp-5.15' to 'verification-done-focal-linux-gcp-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-gcp-5.15' to 'verification-failed-focal-linux-gcp-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-gcp-5.15-v2 verification-needed-focal-linux-gcp-5.15 -- 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/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+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 2059143] Re: Remove getabis scripts
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1058.64~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-5.15 -- 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/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+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 1930877] [NEW] oops.kernel.org unusable
You have been subscribed to a public bug by Kirill (frolovkirill7): Nothing. Just like debian distribution, this package need to be remove. ** Affects: kerneloops (Ubuntu) Importance: Undecided Status: Confirmed -- oops.kernel.org unusable https://bugs.launchpad.net/bugs/1930877 You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. -- 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 2059866] Re: submit url in /etc/kerneloops.conf gives DNS_PROBE_FINISHED_NXDOMAIN
*** This bug is a duplicate of bug 1930877 *** https://bugs.launchpad.net/bugs/1930877 ** This bug has been marked a duplicate of bug 1930877 oops.kernel.org unusable -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kerneloops in Ubuntu. https://bugs.launchpad.net/bugs/2059866 Title: submit url in /etc/kerneloops.conf gives DNS_PROBE_FINISHED_NXDOMAIN Status in kerneloops package in Ubuntu: New Bug description: submit-url = http://oops.kernel.org/submitoops.php Should we even include this package if it doesn't work? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/2059866/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
debdiff for noble ** Attachment removed: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz ** Attachment added: "intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765627/+files/intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Status in intel-gpu-tools source package in Noble: In Progress Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 2058331] Re: Update amd_sfh for AMD strix series
** Changed in: linux-oem-6.8 (Ubuntu Noble) Assignee: Anthony Wong (anthonywong) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2058331 Title: Update amd_sfh for AMD strix series Status in HWE Next: New Status in linux-oem-6.8 package in Ubuntu: New Status in linux-oem-6.8 source package in Noble: New Bug description: Extend MP2 register region to enable family 1AH based family on the supported OEM platforms, needs to be backported into oem-6.8. [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 Following fixes applied to linus tree: * 90184f90c9ac5 HID: amd_sfh: Set the AMD SFH driver to depend on x86 * 6296562f30b1c HID: amd_sfh: Extend MP2 register access to SFH * 2105e8e00da46 HID: amd_sfh: Improve boot time when SFH is available * c1db0073212ef HID: amd_sfh: Avoid disabling the interrupt * bbf0dec306966 HID: amd_sfh: Update HPD sensor structure elements * 333861f4cca6d HID: amd_sfh: Increase sensor command timeout To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058331/+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 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Changed in: intel-gpu-tools (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement Status in intel: Fix Released Status in The Kobuk project: In Progress Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [Description] igt-gpu-tool enabling for Raptor Lake-P [Hardware Information] Architecture: Intel Platform(s): Raptor Lake-P Date HW is expected at Canonical: Component(s): itg-gpu-tool [Software Information] Target Version: 22.04 Target Kernel: Commit IDs / External Links: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/1b32bcdb2d9965090234739aba891a90743e01c4 [Business Justification] [Testing guidance] [External ID] To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+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 2058578] Re: Add support for several cs35l41 amplifier devices (laptop audio support)
6.8 HWE kernel should be available soon some time after 24.04 release, so once that happens you will be able to install the 6.8 HWE kernel in Jammy and have those commits. ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058578 Title: Add support for several cs35l41 amplifier devices (laptop audio support) Status in linux-hwe-6.5 package in Ubuntu: Triaged Bug description: Support for the cs35l41_hda_property table has been already been backported to hwe-6.5-next: commit eec052d5cff271d7bf6854f28c62c4a6650c379b (HEAD -> hwe-6.5-next, tag: Ubuntu-hwe-6.5-6.5.0-27.28_22.04.1, origin/hwe-6.5-next) Support for several devices has been merged to torvalds/linux v6.8 tag: commit e8f897f4afef0031fe618a8e94127a0934896aba (HEAD, tag: v6.8) It would be great if the following commits for sound/pci/hda/cs35l41_hda_property.c could be cherry-picked for release in the near future (listed newest to oldest): b603d95692e47dc6f5f733e93c3841dc0c01e624 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d be220d2e5544ff094142d263db5cf94d034b5e39 c16dfab33f99fc3ff43d48253bc2784ccb84c1de 8c14dbf36424eb751d70c15f9a671549390057b2 7d65d70161ef75a3991480c91668ac11acedf211 ba7053b4b4a4ddcf530fa2b897e697004715d086 d110858a6925827609d11db8513d76750483ec06 ee694e7db47e1af00ffb29f569904a9ed576868f 916d051730ae48aef8b588fd096fefca4bc0590a ed7326a24a1a9af65fafefd86b505e7c3b968f6d 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 b592ed2e1d78a475f781802e441c499ab446975b 8c4c216db8fb84be9c4ca60d72b2066cf28f 2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f I am running on KDE neon 6.0 release 22.04 Linux Scott-Laptop 6.5.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 x86_64 x86_64 x86_64 GNU/Linux This works fine for me: #!/bin/bash git clone cd jammy git remote add upstream https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git fetch upstream git checkout hwe-6.5-next commits="2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f 8c4c216db8fb84be9c4ca60d72b2066cf28f b592ed2e1d78a475f781802e441c499ab446975b b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 ed7326a24a1a9af65fafefd86b505e7c3b968f6d 916d051730ae48aef8b588fd096fefca4bc0590a ee694e7db47e1af00ffb29f569904a9ed576868f d110858a6925827609d11db8513d76750483ec06 ba7053b4b4a4ddcf530fa2b897e697004715d086 7d65d70161ef75a3991480c91668ac11acedf211 8c14dbf36424eb751d70c15f9a671549390057b2 c16dfab33f99fc3ff43d48253bc2784ccb84c1de be220d2e5544ff094142d263db5cf94d034b5e39 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d b603d95692e47dc6f5f733e93c3841dc0c01e624" for c in $commits; do echo $c git cherry-pick $c done cp /boot/config-$(uname -r) .config make -j16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2058578/+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 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: Anthony Wong (anthonywong) => GuoqingJiang (guoqingjiang) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 09:42:52 2024 InstallationDate: Installed on 2022-06-28 (653 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+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 2061040] Re: I2C HID device sometimes fails to initialize causing touchpad to not work
** Changed in: linux (Ubuntu Noble) Assignee: Anthony Wong (anthonywong) => AaronMa (mapengyu) -- 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/2061040 Title: I2C HID device sometimes fails to initialize causing touchpad to not work Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: Hi, Touchpad on my new Lenovo X1 Carbon (Gen12) with the Sensel haptic pad doesn't work on boot. I see this: | [Thu Apr 11 13:57:26 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack reset within 1000 ms | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | ... | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unbalanced collection at end of report description | [Thu Apr 11 13:57:26 2024] hid-generic: probe of 0018:2C2F:0028.0001 failed with error -22 Per the Arch Linux wiki page[1], removing and reloading the `i2c_hid_acpi` seems to fix it: | [Thu Apr 11 13:58:02 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack reset within 1000 ms | [Thu Apr 11 13:58:02 2024] input: SNSL0028:00 2C2F:0028 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-15/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input15 | [Thu Apr 11 13:58:02 2024] input: SNSL0028:00 2C2F:0028 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-15/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input16 | [Thu Apr 11 13:58:02 2024] hid-multitouch 0018:2C2F:0028.0002: input,hidraw0: I2C HID v1.00 Mouse [SNSL0028:00 2C2F:0028] on i2c-SNSL0028:00 | [Thu Apr 11 13:58:03 2024] psmouse serio1: trackpoint: Synaptics TrackPoint firmware: 0x08, buttons: 3/3 | [Thu Apr 11 13:58:03 2024] input: TPPS/2 Synaptics TrackPoint as /devices/platform/i8042/serio1/input/input18 From that Arch Linux wiki page, it seems to be a bug upstream[2] with the commit fixing this: | https://github.com/torvalds/linux/commit/af93a167eda90192563bce64c4bb989836afac1f Or | https://lore.kernel.org/linux- input/20240331182440.14477-1...@kl.wtf/T/#u Can we get fix this backported? | [hloeung@dharkan tmp]$ apt-cache policy linux-image-generic-hwe-24.04 | linux-image-generic-hwe-24.04: | Installed: 6.8.0-22.22 | Candidate: 6.8.0-22.22 | Version table: | *** 6.8.0-22.22 500 | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 Packages | 100 /var/lib/dpkg/status | [hloeung@dharkan tmp]$ uname -a | Linux dharkan.local 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux | [hloeung@dharkan tmp]$ Thanks, Haw [1]: https://wiki.archlinux.org/title/Lenovo_ThinkPad_Z16_Gen_2 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=2271136 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061040/+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 2061378] [NEW] [24.04]: mpi3mr: Features and Bug Fixes
Public bug reported: Below are the features which we want to add in Ubuntu24.04 kernel over mpi3mr driver v8.8.1.0.50, - 829dce7e12c2 : mpi3mr: Driver version update to 8.8.1.0.50 - 57a80be5ec6f : mpi3mr: Update MPI Headers to revision 31 - 0a2714b787b9 : mpi3mr: Debug ability improvements - e8a5a3c3eb58 : mpi3mr: Set the WriteSame Divert Capability in the IOCInit MPI Request - 31ec576ee06a : mpi3mr: Clear ioctl blocking flag for an unresponsive controller - a18f4c58372d : mpi3mr: Set MPI request flags appropriately - dd896a6b0a0d : mpi3mr: Block devices are not removed even when VDs are offlined ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/2061378 Title: [24.04]: mpi3mr: Features and Bug Fixes Status in linux package in Ubuntu: New Bug description: Below are the features which we want to add in Ubuntu24.04 kernel over mpi3mr driver v8.8.1.0.50, - 829dce7e12c2 : mpi3mr: Driver version update to 8.8.1.0.50 - 57a80be5ec6f : mpi3mr: Update MPI Headers to revision 31 - 0a2714b787b9 : mpi3mr: Debug ability improvements - e8a5a3c3eb58 : mpi3mr: Set the WriteSame Divert Capability in the IOCInit MPI Request - 31ec576ee06a : mpi3mr: Clear ioctl blocking flag for an unresponsive controller - a18f4c58372d : mpi3mr: Set MPI request flags appropriately - dd896a6b0a0d : mpi3mr: Block devices are not removed even when VDs are offlined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061378/+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 2061376] Re: Touchpad scroll bounces back 22.04.4 Thinkpad X1 Yoga Gen5
** Attachment added: "evtest /dev/input/event5" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061376/+attachment/5765606/+files/evtest_event5.log ** Description changed: When scrolling anywhere using 2 fingers the scroll bounces back if fingers are lifted up from touchpad. Soft finger point muscles have some flex to them and I strongly believe this causes the scroll bounce back. Easily repeated to both directions. In bounce scroll rapidly moves to the opposite direction of where user wanted to scroll when lifting up fingers. + + Attached is log file evtest_event5.log from single scroll where there + was bounce at lifting fingers. Hardware details: xinput --list WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ xwayland-pointer:16 id=6[slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:16id=7[slave pointer (2)] ⎜ ↳ xwayland-pointer-gestures:16id=8[slave pointer (2)] ⎜ ↳ xwayland-touch:16 id=10 [slave pointer (2)] ⎜ ↳ xwayland-tablet stylus:16 id=11 [slave pointer (2)] ⎜ ↳ xwayland-tablet eraser:16 id=12 [slave pointer (2)] ⎜ ↳ xwayland-tablet cursor:16 id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] - ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] - ↳ xwayland-keyboard:16id=9[slave keyboard (3)] + ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] + ↳ xwayland-keyboard:16id=9[slave keyboard (3)] lshw - *-input:0 -product: Sleep Button -physical id: 2 -logical name: input0 -logical name: /dev/input/event0 -capabilities: platform - *-input:1 -product: Lid Switch -physical id: 3 -logical name: input1 -logical name: /dev/input/event1 -capabilities: platform - *-input:2 -product: Intel HID events -physical id: 4 -logical name: input17 -logical name: /dev/input/event9 -capabilities: platform - *-input:3 -product: ThinkPad Extra Buttons -physical id: 5 -logical name: input18 -logical name: /dev/input/event10 -capabilities: platform - *-input:4 -product: SYNA8007:00 06CB:CD8C Mouse -physical id: 6 -logical name: input19 -logical name: /dev/input/event4 -logical name: /dev/input/mouse0 -capabilities: i2c - *-input:5 -product: Power Button -physical id: 7 -logical name: input2 -logical name: /dev/input/event2 -capabilities: platform - *-input:6 -product: SYNA8007:00 06CB:CD8C Touchpad -physical id: 8 -logical name: input20 -logical name: /dev/input/event5 -logical name: /dev/input/mouse1 -capabilities: i2c - *-input:7 -product: Video Bus -physical id: 9 -logical name: input22 -logical name: /dev/input/event11 -capabilities: platform - *-input:8 -product: sof-hda-dsp Mic -physical id: a -logical name: input23 -logical name: /dev/input/event12 - *-input:9 -product: sof-hda-dsp Headphone -physical id: b -logical name: input24 -logical name: /dev/input/event13 - *-input:10 -product: sof-hda-dsp HDMI/DP,pcm=3 -physical id: c -logical name: input25 -logical name: /dev/input/event14 - *-input:11 -product: sof-hda-dsp HDMI/DP,pcm=4 -physical id: d -logical name: input26 -logical name: /dev/input/event15 - *-input:12 -product: sof-hda-dsp HDMI/DP,pcm=5 -physical id: e -logical name: input27 -logical name: /dev/input/event16 - *-input:13 -product: AT Translated Set 2 keyboard -physical id: f -logical name: input3 -logical name: /dev/input/event3 -logical name: input3::capslock -logical name: input3::numlock -logical name: input3::scrolllock -capabilities: i8042 - *-input:14 -product: TPPS/2 ALPS TrackPoint -physical id: 10 -logical name: input5 -logical name: /dev/input/event6 -logical name: /dev/input/mouse2 -capabilities: i8042 + *-input:0 + product: Sleep Button + physical id: 2 + logical name: input0 + logical name: /dev/input/event0 + capabilities: platform + *-input:1 +
[Kernel-packages] [Bug 1959384] Re: CONFIG_IO_STRICT_DEVMEM could be enabled
In Ubuntu noble: $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-* /boot/config-6.8.0-22-generic:# CONFIG_IO_STRICT_DEVMEM is not set /boot/config-6.8.0-7-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set ** Tags removed: kinetic lunar ** Tags added: noble -- 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/1959384 Title: CONFIG_IO_STRICT_DEVMEM could be enabled Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace access of active io-memory ranges. This could impact kernel debugability. In that case, you may reboot with iomem=relaxed on the kernel command line to override this setting. This config option is recommended by the Kernel Self Protection Project[1] and a 2019 study performed by Capsule 8 shows that it is enabled in many other major distro kernels[2]. [1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings [2] https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/ In Ubuntu impish: $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-* /boot/config-5.13.0-27-generic:# CONFIG_IO_STRICT_DEVMEM is not set /boot/config-5.13.0-27-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set /boot/config-5.16.3-051603-generic:# CONFIG_IO_STRICT_DEVMEM is not set /boot/config-5.16.3-051603-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set In Debian 11: $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-* /boot/config-5.10.0-10-amd64:CONFIG_IO_STRICT_DEVMEM=y /boot/config-5.10.0-11-amd64:CONFIG_IO_STRICT_DEVMEM=y In Debian sid: $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-* /boot/config-5.15.0-3-amd64:CONFIG_IO_STRICT_DEVMEM=y /boot/config-5.15.0-3-rt-amd64:CONFIG_IO_STRICT_DEVMEM=y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959384/+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 1971186] Re: Suggests linux-lowlatency-tools instead of linux-tools-lowlatency
** Tags added: noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/1971186 Title: Suggests linux-lowlatency-tools instead of linux-tools-lowlatency Status in linux-signed-lowlatency package in Ubuntu: New Bug description: Hi, the linux-image-*-lowlatency kernel package suggests the linux- lowlatency-tools package: $ apt show linux-image-5.15.0-27-lowlatency Package: linux-image-5.15.0-27-lowlatency Version: 5.15.0-27.28 [...] Suggests: fdutils, linux-doc | linux-lowlatency-source-5.15.0, linux-lowlatency-tools, linux-headers-5.15.0-27-lowlatency, linux-modules-extra-5.15.0-27-lowlatency The linux-lowlatency-tools package does not exist. However, a linux- tools-lowlatency does exist. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-lowlatency 5.15.0-27.28 Uname: Linux 5.17.5-051705-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon May 2 20:06:21 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-lowlatency UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/1971186/+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 1993566] Re: dbus-daemon: Unknown group "power" in message bus configuration file
** Tags added: noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1993566 Title: dbus-daemon: Unknown group "power" in message bus configuration file Status in thermald package in Ubuntu: Confirmed Bug description: Hi, I see the following error message in the logs: # journalctl | grep 'Unknown group "power"' Oct 19 18:41:35 jophur dbus-daemon[630]: dbus[630]: Unknown group "power" in message bus configuration file Oct 19 18:46:35 jophur dbus-daemon[630]: Unknown group "power" in message bus configuration file Oct 19 18:46:36 jophur dbus-daemon[630]: Unknown group "power" in message bus configuration file The problem comes from this file: # grep -r power /etc/dbus-1/ /etc/dbus-1/system.d/org.freedesktop.thermald.conf:
[Kernel-packages] [Bug 2061376] [NEW] Touchpad scroll bounces back 22.04.4 Thinkpad X1 Yoga Gen5
Public bug reported: When scrolling anywhere using 2 fingers the scroll bounces back if fingers are lifted up from touchpad. Soft finger point muscles have some flex to them and I strongly believe this causes the scroll bounce back. Easily repeated to both directions. In bounce scroll rapidly moves to the opposite direction of where user wanted to scroll when lifting up fingers. Hardware details: xinput --list WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ xwayland-pointer:16 id=6[slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:16 id=7[slave pointer (2)] ⎜ ↳ xwayland-pointer-gestures:16 id=8[slave pointer (2)] ⎜ ↳ xwayland-touch:16 id=10 [slave pointer (2)] ⎜ ↳ xwayland-tablet stylus:16 id=11 [slave pointer (2)] ⎜ ↳ xwayland-tablet eraser:16 id=12 [slave pointer (2)] ⎜ ↳ xwayland-tablet cursor:16 id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ xwayland-keyboard:16 id=9[slave keyboard (3)] lshw *-input:0 product: Sleep Button physical id: 2 logical name: input0 logical name: /dev/input/event0 capabilities: platform *-input:1 product: Lid Switch physical id: 3 logical name: input1 logical name: /dev/input/event1 capabilities: platform *-input:2 product: Intel HID events physical id: 4 logical name: input17 logical name: /dev/input/event9 capabilities: platform *-input:3 product: ThinkPad Extra Buttons physical id: 5 logical name: input18 logical name: /dev/input/event10 capabilities: platform *-input:4 product: SYNA8007:00 06CB:CD8C Mouse physical id: 6 logical name: input19 logical name: /dev/input/event4 logical name: /dev/input/mouse0 capabilities: i2c *-input:5 product: Power Button physical id: 7 logical name: input2 logical name: /dev/input/event2 capabilities: platform *-input:6 product: SYNA8007:00 06CB:CD8C Touchpad physical id: 8 logical name: input20 logical name: /dev/input/event5 logical name: /dev/input/mouse1 capabilities: i2c *-input:7 product: Video Bus physical id: 9 logical name: input22 logical name: /dev/input/event11 capabilities: platform *-input:8 product: sof-hda-dsp Mic physical id: a logical name: input23 logical name: /dev/input/event12 *-input:9 product: sof-hda-dsp Headphone physical id: b logical name: input24 logical name: /dev/input/event13 *-input:10 product: sof-hda-dsp HDMI/DP,pcm=3 physical id: c logical name: input25 logical name: /dev/input/event14 *-input:11 product: sof-hda-dsp HDMI/DP,pcm=4 physical id: d logical name: input26 logical name: /dev/input/event15 *-input:12 product: sof-hda-dsp HDMI/DP,pcm=5 physical id: e logical name: input27 logical name: /dev/input/event16 *-input:13 product: AT Translated Set 2 keyboard physical id: f logical name: input3 logical name: /dev/input/event3 logical name: input3::capslock logical name: input3::numlock logical name: input3::scrolllock capabilities: i8042 *-input:14 product: TPPS/2 ALPS TrackPoint physical id: 10 logical name: input5 logical name: /dev/input/event6 logical name: /dev/input/mouse2 capabilities: i8042 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci -vnvn" https://bugs.launchpad.net/bugs/2061376/+attachment/5765602/+files/lspci-vnvn.log -- 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/2061376 Title: Touchpad scroll bounces back 22.04.4 Thinkpad X1 Yoga Gen5 Status in linux package in Ubuntu: New Bug description: When scrolling anywhere using 2 fingers the scroll bounces back if fingers are lifted up from touchpad. Soft finger point muscles have some flex to them and I strongly believe this causes the scroll bounce back. Easily repeated to both directions. In bounce scroll rapidly moves to the opposite direction of where user wanted to scroll when lifting up fingers. Hardware details: xinput --list WARNING: running xinput against an
[Kernel-packages] [Bug 2042363] Re: AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl() on a Ubuntu 20.04 NFSV4 ser
Per below from the trace file Nov 30 11:13:40 duckseason kernel: [1291756.354728] nfsd_dispatch: vers 4 proc 1 Nov 30 11:13:40 duckseason kernel: [1291756.354731] svc: server 7c7e7536, pool 0, transport 3fd86d34, inuse=3 Nov 30 11:13:40 duckseason kernel: [1291756.354732] process_renew(6554b87b/4ab45507): starting Nov 30 11:13:40 duckseason kernel: [1291756.354734] svc: tcp_recv 3fd86d34 data 1 conn 0 close 0 Nov 30 11:13:40 duckseason kernel: [1291756.354736] svc: socket 3fd86d34 recvfrom(03fecffb, 4) = -11 Nov 30 11:13:40 duckseason kernel: [1291756.354737] RPC: TCP recv_record got -11 Nov 30 11:13:40 duckseason kernel: [1291756.354737] RPC: TCP recvfrom got EAGAIN we can see NFS server return -11 (EAGAIN), which can be executed from from the path, svc_recv -> svc_handle_xprt -> xprt->xpt_ops->xpo_recvfrom svc_tcp_recvfrom -> svc_recvfrom -> sock_recvmsg which probably triggers sock_recvmsg_nosec -> ... -> tcp_recvmsg As mentioned in recvfrom manpage, ERRORS The recvfrom() function shall fail if: EAGAIN or EWOULDBLOCK The socket's file descriptor is marked O_NONBLOCK and no data is waiting to be received; or MSG_OOB is set and no out-of-band data is available and either the socket's file descriptor is marked O_NONBLOCK or the socket does not support blocking to await out-of-band data. I am not sure if 7.3 NFS client opened non-blocking socket and no data on that socket to be read. So I would like to check if 7.3 client sent something different compared with 7.2 client which caused server returned BAD_SEQID to AIX 7.3 client. Please also collect relevant trace log from server side when connecting with 7.2 client, then we can investigate the difference between good one and bad one. If possible, maybe you can try with the latest 5.4 stable (5.4.274) and upstream version (6.9-rc4). -- 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/2042363 Title: AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl() on a Ubuntu 20.04 NFSV4 server Status in linux package in Ubuntu: New Bug description: ---Problem Description--- AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl(). NFS server is Ubuntu 20.04.6 LTS, GNU/Linux 5.4.0-139-generic x86_64. The problem does not appear to affect other combinations of NFS client (including AIX 7.2) with this NFS server. The AIX team have indicated that the cause of the EIO is triggered by the NFS server returning a BAD_SEQID error which leads to the AIX NFS client incorrectly zeroing the stateid, which then leads to the NFS server returning a BAD_STATEID error and the NFS client then returns the EIO error. The AIX team would like to understand why the BAD_SEQID has been returned. ---uname output--- Linux duckseason 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Machine Type = VMware ESXi Server 7.0 4 x Intel(R) Xeon(R) Gold 6348H CPU @ 2.30GHz ---Steps to Reproduce--- We cannot offer a simple way to recreate the problem as it involves IBM MQ running on two primary machines (AIX) using the Ubuntu server for it's HA NFSv4 storage. However, we can provide any requested trace or dumps from any or all of the involved machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042363/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
debdiff for Noble ** Attachment added: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Status in intel-gpu-tools source package in Noble: In Progress Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 2037212] Re: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
This problem still exists in noble:
# journalctl | grep ConfigurationDirectory
Apr 15 11:00:12 vougeot (uetoothd)[3112]: bluetooth.service:
ConfigurationDirectory 'bluetooth' already exists but the mode is different.
(File system: 755 ConfigurationDirectoryMode: 555)
** Tags added: noble
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2037212
Title:
ConfigurationDirectory 'bluetooth' already exists but the mode is
different. (File system: 755 ConfigurationDirectoryMode: 555)
Status in bluez package in Ubuntu:
Confirmed
Status in bluez package in Debian:
Confirmed
Bug description:
Hi,
when my system boots it logs the following warning in the journal:
$ journalctl | grep ConfigurationDirectory
Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth'
already exists but the mode is different. (File system: 755
ConfigurationDirectoryMode: 555)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 13:28:20 2023
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: 70:9C:D1:50:1F:7B ACL MTU: 1021:4 SCO MTU: 96:6
DOWN
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037212/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
The fixed is available for Noble at : https://launchpad.net/~hectorcao/+archive/ubuntu/lp-1949314 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Status in intel-gpu-tools source package in Noble: In Progress Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 2018128] Re: Apport does not collect all logs when the package is HWE kernel
On Ubuntu-desktop 24.04 development branch @ 15/4/2024 filing a bug against 'linux' now gives these warnings in terminal: REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg, insufficient permissions apport still continues gathering system info and launching browser correctly -- 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/2018128 Title: Apport does not collect all logs when the package is HWE kernel Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 22.04 LTS with kernel 5.19.0-41-generic When filing bugs against the package 'linux' apport collects all the logs needed to the kernel But in case the user is not on stock kernel anymore and has the HWE kernel apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my case) would it be possible to make apport collect all the logs needed in all kernel cases? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.4 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 05:25:30 2023 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Also affects: intel-gpu-tools (Ubuntu Noble) Importance: Undecided Assignee: Hector CAO (hectorcao) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Status in intel-gpu-tools source package in Noble: In Progress Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 - The proposed fix consists of backporting this fix to affected ubuntu + The fix has been part of a serie of fixes that improve intel_gpu_top UI + behavior for some corner cases : + https://patchwork.freedesktop.org/series/124890/ + + The proposed fix consists of backporting these fixes to affected Ubuntu releases : Jammy, Mantic and Noble [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu - releases : Jammy, Mantic and Noble + releases (Jammy, Mantic and Noble) + + Tvrtko Ursulin (4): + tools/intel_gpu_top: Fix clients header width when no clients + tools/intel_gpu_top: Fix client layout on first sample period + tools/intel_gpu_top: Optimise interactive display a bit + tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Status in intel-gpu-tools source package in Noble: In Progress Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is:
[Kernel-packages] [Bug 2060859] Re: Xorg freeze
"Input/output error" suggests there's a disk problem but I suppose such
an error could occur in any kernel driver.
Next time the error pops up, please run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Package changed: xorg-server (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Summary changed:
- Xorg freeze
+ Input/output error
--
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/2060859
Title:
Input/output error
Status in linux package in Ubuntu:
Incomplete
Bug description:
Whenever I open my laptop and start working, after some time (after
10-15 minutes) this automatically starts happening for all the
applications (terminal and all application ). and this happens every
day And the laptop stops working. Even the laptop doesn't turn off. i
forcefully close the laptop ( i already make 30gb swap partition) .
and when i hover on anything , my cursor look like square
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 10 23:41:40 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series /
Radeon Vega Mobile Series] [1002:15d8] (rev c2) (prog-if 00 [VGA controller])
Subsystem: Lenovo Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile
Series] [17aa:3804]
InstallationDate: Installed on 2024-04-08 (2 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=2a9c63d2-ea20-46aa-b9d5-674c8d948bd2 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/12/2021
dmi.bios.release: 1.28
dmi.bios.vendor: LENOVO
dmi.bios.version: BUCN28WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q55722WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S145-15API
dmi.ec.firmware.release: 1.28
dmi.modalias:
dmi:bvnLENOVO:bvrBUCN28WW:bd01/12/2021:br1.28:efr1.28:svnLENOVO:pn81UT:pvrLenovoIdeaPadS145-15API:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15API:skuLENOVO_MT_81UT_BU_idea_FM_IdeaPadS145-15API:
dmi.product.family: IdeaPad S145-15API
dmi.product.name: 81UT
dmi.product.sku: LENOVO_MT_81UT_BU_idea_FM_IdeaPad S145-15API
dmi.product.version: Lenovo IdeaPad S145-15API
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060859/+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 2059143] Re: Remove getabis scripts
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-103.113~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- hwe-5.15' to 'verification-done-focal-linux-hwe-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-hwe-5.15' to 'verification-failed-focal-linux-hwe-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-hwe-5.15-v2 verification-needed-focal-linux-hwe-5.15 -- 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/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+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 2059143] Re: Remove getabis scripts
This bug is awaiting verification that the linux- riscv-5.15/5.15.0-1054.58~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- riscv-5.15' to 'verification-done-focal-linux-riscv-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux- riscv-5.15' to 'verification-failed-focal-linux-riscv-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-riscv-5.15-v2 verification-needed-focal-linux-riscv-5.15 -- 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/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+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 2059143] Re: Remove getabis scripts
This bug is awaiting verification that the linux-oracle/5.15.0-1056.62 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oracle' to 'verification-done- jammy-linux-oracle'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oracle' to 'verification-failed-jammy- linux-oracle'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oracle-v2 verification-needed-jammy-linux-oracle -- 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/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+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 2059143] Re: Remove getabis scripts
This bug is awaiting verification that the linux-nvidia/5.15.0-1049.49 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia' to 'verification-done- jammy-linux-nvidia'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia' to 'verification-failed-jammy- linux-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-v2 verification-needed-jammy-linux-nvidia -- 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/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+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 2059143] Re: Remove getabis scripts
This bug is awaiting verification that the linux-raspi/5.15.0-1051.54 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+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 2059143] Re: Remove getabis scripts
This bug is awaiting verification that the linux-intel- iotg/5.15.0-1053.59 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to 'verification-done-jammy-linux-intel-iotg'. If the problem still exists, change the tag 'verification-needed-jammy-linux-intel-iotg' to 'verification-failed-jammy-linux-intel-iotg'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 verification-needed-jammy-linux-intel-iotg -- 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/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+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 2059143] Re: Remove getabis scripts
This bug is awaiting verification that the linux- lowlatency/5.15.0-103.113 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-lowlatency' to 'verification-done-jammy-linux-lowlatency'. If the problem still exists, change the tag 'verification-needed-jammy-linux-lowlatency' to 'verification-failed-jammy-linux-lowlatency'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-v2 verification-needed-jammy-linux-lowlatency -- 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/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+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
