[Kernel-packages] [Bug 1976587] [NEW] Fix can't boot up after change to vmd
Public bug reported: [Impact] ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) -- 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/1976587 Title: Fix can't boot up after change to vmd Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: New Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.14 source package in Kinetic: New Status in linux-oem-5.17 source package in Kinetic: New Bug description: [Impact] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976587/+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 1976556] Re: [Lenovo 300e 2nd GEN] ELAN Touchpad not working
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1976556 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1976556 Title: [Lenovo 300e 2nd GEN] ELAN Touchpad not working Status in linux package in Ubuntu: Incomplete Bug description: Used Ubunutu 22.04 with the current 5.15.x Kernel, cross tested with Linux Mint and 5.14.x Kernel. I have a Lenovo 300e 2nd Gen with an ELAN Touchscreen AND Touchpad with AMD processor. The Touchscreen is working flawlessly. The TouchPAD is dead. According to the Windows driver: %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group2_Inst, HID\VEN_ELAN_0660; ClickPad for Capela 14e Windows %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group1_Inst, HID\VEN_ELAN_0661; ClickPad for Windows 100e/300e %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group3_Inst, HID\VEN_ELAN_066C; ClickPad for 100e/300e AMD Pollock %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group1_Inst, HID\VEN_ELAN_066E; ClickPad for 100W&300W Gen3 AMD Pollock %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group1_Inst, HID\VEN_ELAN_066F; ClickPad for 300W Gen3 Intel JasperLake it is an ELAN066C According to similar solutions i tried to block several built in kernel modules, without success. https://askubuntu.com/questions/1248176/ideapad-5-15are05-elan- touchpad-not-working-on-20-04-nor-on-18-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976556/+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 1976556] [NEW] [Lenovo 300e 2nd GEN] ELAN Touchpad not working
You have been subscribed to a public bug: Used Ubunutu 22.04 with the current 5.15.x Kernel, cross tested with Linux Mint and 5.14.x Kernel. I have a Lenovo 300e 2nd Gen with an ELAN Touchscreen AND Touchpad with AMD processor. The Touchscreen is working flawlessly. The TouchPAD is dead. According to the Windows driver: %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group2_Inst, HID\VEN_ELAN_0660; ClickPad for Capela 14e Windows %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group1_Inst, HID\VEN_ELAN_0661; ClickPad for Windows 100e/300e %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group3_Inst, HID\VEN_ELAN_066C; ClickPad for 100e/300e AMD Pollock %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group1_Inst, HID\VEN_ELAN_066E; ClickPad for 100W&300W Gen3 AMD Pollock %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group1_Inst, HID\VEN_ELAN_066F; ClickPad for 300W Gen3 Intel JasperLake it is an ELAN066C According to similar solutions i tried to block several built in kernel modules, without success. https://askubuntu.com/questions/1248176/ideapad-5-15are05-elan-touchpad- not-working-on-20-04-nor-on-18-04 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment -- [Lenovo 300e 2nd GEN] ELAN Touchpad not working https://bugs.launchpad.net/bugs/1976556 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 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
Ah, SOLVED, like this: Triggered by your remarks, I found https://unix.stackexchange.com/a/656183, which says: RUB_CMDLINE_LINUX_DEFAULT="atkbd.reset i8042.reset i8042.nomux quiet splash". If this doesn't work, follow the same process but try GRUB_CMDLINE_LINUX_DEFAULT="i8042.direct i8042.dumbkbd" ... and that last line worked for me: keyboard works immediatly after boot and resume. So my grub line is now GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.debug=1i8042.direct i8042.dumbkbd" I guess I can remove i8042.debug=1 Thank you! -- 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/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Fresh install of Ubuntu 22.04, fully updated, no changes or configuration at all. Newish HP laptop (so recent hardware) Problem: After resuming from suspend, the laptop's keyboard is not working for about 30 seconds (the laptop's touchpad is working at once). Looking at dmesg, it looks the keyboard only starts working after: [di mei 31 19:10:21 2022] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input106 ... which happens about 35 seconds after the resume sequence completes. From dmesg: suspend: [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:51 2022] usb 1-1: USB disconnect, device number 2 [di mei 31 19:06:51 2022] PM: suspend entry (s2idle) [di mei 31 19:06:51 2022] Filesystems sync: 0.007 seconds [di mei 31 19:06:51 2022] Freezing user space processes ... (elapsed 0.001 seconds) done. [di mei 31 19:06:51 2022] OOM killer disabled. [di mei 31 19:06:51 2022] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [di mei 31 19:06:51 2022] printk: Suspending console(s) (use no_console_suspend to debug) [di mei 31 19:06:52 2022] ACPI: EC: interrupt blocked After 3 minutes: open laptop lid, and it wakes up: [di mei 31 19:09:45 2022] ACPI: EC: interrupt unblocked [di mei 31 19:09:46 2022] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [di mei 31 19:09:46 2022] OOM killer enabled. [di mei 31 19:09:46 2022] Restarting tasks ... [di mei 31 19:09:46 2022] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821 [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: rom_version status=0 version=1 [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: cfg_sz 10, total sz 31990 [di mei 31 19:09:46 2022] done. [di mei 31 19:09:46 2022] PM: suspend exit [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: fw version 0x829a7644 ... and then after 35 seconds [di mei 31 19:10:21 2022] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input106 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1329 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 31 19:24:02 2022 InstallationDate: Installed on 2022-05-31 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 005: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio Bus
[Kernel-packages] [Bug 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
I tried "i8042.noaux=1", but no change: after boot and after resume: touchpad works immediatly, but keyboard takes 25-45 seconds. dmesg included ** Attachment added: "dmesg "i8042.noaux=1"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+attachment/5594428/+files/dmesg.i8042.noaux.txt -- 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/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Fresh install of Ubuntu 22.04, fully updated, no changes or configuration at all. Newish HP laptop (so recent hardware) Problem: After resuming from suspend, the laptop's keyboard is not working for about 30 seconds (the laptop's touchpad is working at once). Looking at dmesg, it looks the keyboard only starts working after: [di mei 31 19:10:21 2022] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input106 ... which happens about 35 seconds after the resume sequence completes. From dmesg: suspend: [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:51 2022] usb 1-1: USB disconnect, device number 2 [di mei 31 19:06:51 2022] PM: suspend entry (s2idle) [di mei 31 19:06:51 2022] Filesystems sync: 0.007 seconds [di mei 31 19:06:51 2022] Freezing user space processes ... (elapsed 0.001 seconds) done. [di mei 31 19:06:51 2022] OOM killer disabled. [di mei 31 19:06:51 2022] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [di mei 31 19:06:51 2022] printk: Suspending console(s) (use no_console_suspend to debug) [di mei 31 19:06:52 2022] ACPI: EC: interrupt blocked After 3 minutes: open laptop lid, and it wakes up: [di mei 31 19:09:45 2022] ACPI: EC: interrupt unblocked [di mei 31 19:09:46 2022] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [di mei 31 19:09:46 2022] OOM killer enabled. [di mei 31 19:09:46 2022] Restarting tasks ... [di mei 31 19:09:46 2022] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821 [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: rom_version status=0 version=1 [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: cfg_sz 10, total sz 31990 [di mei 31 19:09:46 2022] done. [di mei 31 19:09:46 2022] PM: suspend exit [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: fw version 0x829a7644 ... and then after 35 seconds [di mei 31 19:10:21 2022] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input106 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1329 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 31 19:24:02 2022 InstallationDate: Installed on 2022-05-31 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 005: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14s-dq2xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=6b217a97-66c0-4829-bbef-01ac3d8034c9 ro quiet
[Kernel-packages] [Bug 1976511] Re: kernel taint ( warning ) caused by smpboot.c: on 5.4.0
It seems very similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882478/ which have been fixed on Bionic. -- 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/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: Apr 6 02:33:31 G292-280 kernel: [0.007531] [ cut here ] Apr 6 02:33:31 G292-280 kernel: [0.007531] sched: CPU #20's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. Apr 6 02:33:31 G292-280 kernel: [0.007531] WARNING: CPU: 20 PID: 0 at /build/linux-hwe-5.4-9Mb2g5/linux-hwe-5.4-5.4.0/arch/x86/kernel/smpboot.c:426 topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Modules linked in: Apr 6 02:33:31 G292-280 kernel: [0.007531] CPU: 20 PID: 0 Comm: swapper/20 Not tainted 5.4.0-107-generic #121~18.04.1-Ubuntu Apr 6 02:33:31 G292-280 kernel: [0.007531] Hardware name: GIGABYTE G292-280-00/MG52-G20-00, BIOS F02 10/28/2021 Apr 6 02:33:31 G292-280 kernel: [0.007531] RIP: 0010:topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Code: 41 5c 5d c3 80 3d 1e 75 ba 01 00 75 ec 89 f1 41 89 d9 89 fe 45 89 e0 48 c7 c7 b8 00 b4 a6 c6 05 04 75 ba 01 01 e8 b4 c7 03 00 <0f> 0b eb cb 0f 1f 44 00 00 55 0f b6 05 a3 8d f0 01 c6 05 9c 8d f0 Apr 6 02:33:31 G292-280 kernel: [0.007531] RSP: :b76b58e17eb8 EFLAGS: 00010086 Apr 6 02:33:31 G292-280 kernel: [0.007531] RAX: RBX: RCX: a7264e88 Apr 6 02:33:31 G292-280 kernel: [0.007531] RDX: a7264e88 RSI: 0096 RDI: 0046 Apr 6 02:33:31 G292-280 kernel: [0.007531] RBP: b76b58e17ec8 R08: R09: 0002f680 Apr 6 02:33:31 G292-280 kernel: [0.007531] R10: 8b69bf80 R11: 02c0 R12: 0001 Apr 6 02:33:31 G292-280 kernel: [0.007531] R13: 0014 R14: 0014 R15: 0002 Apr 6 02:33:31 G292-280 kernel: [0.007531] FS: () GS:8b69bf80() knlGS: Apr 6 02:33:31 G292-280 kernel: [0.007531] CS: 0010 DS: ES: CR0: 80050033 Apr 6 02:33:31 G292-280 kernel: [0.007531] CR2: CR3: 007ee1a0a001 CR4: 00760ee0 Apr 6 02:33:31 G292-280 kernel: [0.007531] DR0: DR1: DR2: Apr 6 02:33:31 G292-280 kernel: [0.007531] DR3: DR6: fffe0ff0 DR7: 0400 Apr 6 02:33:31 G292-280 kernel: [0.007531] PKRU: Apr 6 02:33:31 G292-280 kernel: [0.007531] Call Trace: Apr 6 02:33:31 G292-280 kernel: [0.007531] set_cpu_sibling_map+0x14f/0x600 Apr 6 02:33:31 G292-280 kernel: [0.007531] start_secondary+0x6e/0x1c0 Apr 6 02:33:31 G292-280 kernel: [0.007531] secondary_startup_64+0xa4/0xb0 Apr 6 02:33:31 G292-280 kernel: [0.007531] ---[ end trace 789d1f3abd3d96d4 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+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 1786013] Autopkgtest regression report (linux-meta-oem-5.17/5.17.0.1009.9)
All autopkgtests for the newly accepted linux-meta-oem-5.17 (5.17.0.1009.9) for jammy have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.55.3+22.04ubuntu1 (amd64) r8168/8.049.02-1ubuntu1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu11 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-oem-5.17 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
Please give "i8042.noaux=1" a try, 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/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Fresh install of Ubuntu 22.04, fully updated, no changes or configuration at all. Newish HP laptop (so recent hardware) Problem: After resuming from suspend, the laptop's keyboard is not working for about 30 seconds (the laptop's touchpad is working at once). Looking at dmesg, it looks the keyboard only starts working after: [di mei 31 19:10:21 2022] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input106 ... which happens about 35 seconds after the resume sequence completes. From dmesg: suspend: [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:51 2022] usb 1-1: USB disconnect, device number 2 [di mei 31 19:06:51 2022] PM: suspend entry (s2idle) [di mei 31 19:06:51 2022] Filesystems sync: 0.007 seconds [di mei 31 19:06:51 2022] Freezing user space processes ... (elapsed 0.001 seconds) done. [di mei 31 19:06:51 2022] OOM killer disabled. [di mei 31 19:06:51 2022] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [di mei 31 19:06:51 2022] printk: Suspending console(s) (use no_console_suspend to debug) [di mei 31 19:06:52 2022] ACPI: EC: interrupt blocked After 3 minutes: open laptop lid, and it wakes up: [di mei 31 19:09:45 2022] ACPI: EC: interrupt unblocked [di mei 31 19:09:46 2022] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [di mei 31 19:09:46 2022] OOM killer enabled. [di mei 31 19:09:46 2022] Restarting tasks ... [di mei 31 19:09:46 2022] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821 [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: rom_version status=0 version=1 [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: cfg_sz 10, total sz 31990 [di mei 31 19:09:46 2022] done. [di mei 31 19:09:46 2022] PM: suspend exit [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: fw version 0x829a7644 ... and then after 35 seconds [di mei 31 19:10:21 2022] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input106 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1329 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 31 19:24:02 2022 InstallationDate: Installed on 2022-05-31 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 005: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14s-dq2xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=6b217a97-66c0-4829-bbef-01ac3d8034c9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No
[Kernel-packages] [Bug 1970957] Re: suspend problem
This is to confirm Linux 5.18.0-051800-generic x86_64 fixed my Lenovo T460. Thanks mo! -- 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/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+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 1976358] Re: Charset Boot-Login
** Package changed: linux (Ubuntu) => gdm (Ubuntu) -- 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/1976358 Title: Charset Boot-Login Status in gdm package in Ubuntu: Confirmed Bug description: For Jammy Jellyfish 22.04: The charset of the boot-login is the american one. If I changed the charset to e.g. Swiss German, I will struggle, because special chars are on other keys. For logins while running the system it takes the custom charset. /* I can't run the terminal window while this issue encountered */ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1976358/+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 1966499] Re: Recent 5.13 kernel has broken KVM support
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1012.12 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' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- 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/1966499 Title: Recent 5.13 kernel has broken KVM support Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] This is caused by commit 08335308 "KVM: x86: check PIR even for vCPUs with disabled APICv", this patch needs 7e1901f6c "KVM: VMX: prepare sync_pir_to_irr for running with APICv disabled" otherwise if APICv is disabled in this vcpu it will trigger warning messages in vmx_sync_pir_to_irr() of vmx.c: WARN_ON(!vcpu->arch.apicv_active); With warnings like: [ cut here ] WARNING: CPU: 13 PID: 6997 at arch/x86/kvm/vmx/vmx.c:6336 vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel] ? xfer_to_guest_mode_work+0xe2/0x110 Modules linked in: vhost_net vhost vhost_iotlb tap xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink bridge stp llc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm joydev input_leds ioatdma rapl intel_cstate efi_pstore ipmi_si mei_me mei mac_hid acpi_pad vcpu_run+0x4d/0x220 [kvm] acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid mgag200 i2c_algo_bit drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect sysimgblt ghash_clmulni_intel fb_sys_fops ixgbe cec aesni_intel rc_core crypto_simd xfrm_algo cryptd drm ahci dca i2c_i801 xhci_pci mdio libahci i2c_smbus lpc_ich xhci_pci_renesas wmi CPU: 13 PID: 6997 Comm: qemu-system-x86 Tainted: G W I 5.13.0-39-generic #44-Ubuntu Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS SE5C610.86B.01.01.1008.031920151331 03/19/2015 kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm] RIP: 0010:vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel] Code: e8 47 f5 18 00 8b 93 00 03 00 00 89 45 ec 83 e2 20 85 d2 74 dc 48 8b 55 f0 65 48 2b 14 25 28 00 00 00 75 1d 48 8b 5d f8 c9 c3 <0f> 0b eb 87 f0 80 4b 39 40 8b 93 00 03 00 00 8b 45 ec 83 e2 20 eb RSP: 0018:ae4d8d107c98 EFLAGS: 00010046 RAX: RBX: 99c552942640 RCX: 99c5043a72f0 RDX: 99c552942640 RSI: 0001 RDI: 99c552942640 RBP: ae4d8d107cb0 R08: 99c86f6a7140 R09: 00027100 R10: 4228 R11: 000a R12: 99c552942640 R13: R14: ae4d8d1a63e0 R15: 99c552942640 FS: 7f6ae9be7640() GS:99c86f68() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: CR3: 00010b8a6006 CR4: 001726e0 Call Trace: kvm_vcpu_ioctl+0x243/0x5e0 [kvm] vcpu_enter_guest+0x383/0xf50 [kvm] ? xfer_to_guest_mode_work+0xe2/0x110 ? kvm_vm_ioctl+0x364/0x730 [kvm] ? __fget_files+0x86/0xc0 vcpu_run+0x4d/0x220 [kvm] __x64_sys_ioctl+0x91/0xc0 do_syscall_64+0x61/0xb0 ? fput+0x13/0x20 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? do_syscall_64+0x6e/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? do_syscall_64+0x6e/0xb0 ? do_syscall_64+0x6e/0xb0 ? do_syscall_64+0x6e/0xb0 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6aebce1a2b Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 f3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6ae8ffe3f8 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: ae80 RCX: 7f6aebce1a2b RDX: RSI: ae80 RDI: 000c RBP: 557d3b429b90 R08: 557d3a4ebff0 R09: kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm] R10: 0001 R11: 0246 R12:
[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted
This bug is awaiting verification that the linux-
intel-5.13/5.13.0-1012.12 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' to 'verification-
done-focal'. If the problem still exists, change the tag 'verification-
needed-focal' to 'verification-failed-focal'.
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: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1966066
Title:
audio from external sound card is distorted
Status in linux package in Ubuntu:
Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
Invalid
Status in linux source package in Impish:
Fix Released
Status in linux-signed-hwe-5.13 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
Invalid
Bug description:
[Impact]
Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
next packet size") landed in 5.13.0-35 introduced regression to USB
audio device.
It's because this patch introduced the available frame size check, but
the conversion forgot to initialize the temporary variable properly.
A workaround is to modify /etc/pulse/daemon.conf, set the
default-sample-rate to 48000, uncomment it by removing the semicolon
at the beginning of the line. And restart pulseaudio with:
systemctl --user restart pulseaudio.service
[Fix]
* 23939115 ALSA: usb-audio: Fix packet size calculation regression
This patch can be cherry-picked into Impish kernel, and it's already in
the master-next branch of Jammy tree.
[Test]
Test kernels built with 5.13.0-37 + this patch, can be found in:
* Focal-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
* Impish-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/
Both kernels were tested by affected users and they're working as
expected.
[Where problems could occur]
If this patch is incorrect, it might affect USB audio devices.
[Original Bug Report]
The sound card is a Focusrite Scarlett 2i2.
The sound is distorted everywhere.
Sound via HDMI works.
Seen others having the same problem:
(Edit because of previously wrong link here)
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card
ubuntu release: Ubuntu 20.04.4 LTS
package name involved in bug: linux-image-5.13.0-37-generic
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 23 12:56:02 2022
InstallationDate: Installed on 2020-12-18 (459 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066/+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 1971667] Re: Skip setting ethernet LED on Dell EMC board
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1012.12 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' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1971667 Title: Skip setting ethernet LED on Dell EMC board Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-iotg package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-intel-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg source package in Focal: Invalid Status in linux source package in Jammy: New Status in linux-intel-5.13 source package in Jammy: New Status in linux-intel-iotg source package in Jammy: In Progress Status in linux source package in Kinetic: Confirmed Status in linux-intel-5.13 source package in Kinetic: Invalid Status in linux-intel-iotg source package in Kinetic: New Bug description: [Impact] LED is not show networking status on the said Dell EMC board. [Fix] Don't set the LED on it. [Test] Check the LED and it's showing correct status. The LED continues to work after S3. [Where problems could occur] We use a UUID to match the board, so all other users are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971667/+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 1884726] Re: [TTM] Buffer eviction failed
Switched to nvidia proprietary driver and so far no more crashes in the browser, need more time to fully test with the nvidia driver. Definitely a nouveau driver bug with the kernel: Linux svn 5.4.0-55-generic #61~18.04.1-Ubuntu SMP Wed Nov 11 14:12:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Attached is the crash_history. ** Attachment added: "crash history nouveau driver kernel 5.4.8-55 hwe (ubuntu lxde 18.04))" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884726/+attachment/5594367/+files/crash_history.txt -- 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/1884726 Title: [TTM] Buffer eviction failed Status in linux package in Ubuntu: Expired Bug description: Under some usage conditions on Ubuntu 20.04 I get an almost complete system freeze and after some minutes I get this issuing a dmesg command: "[TTM] Buffer eviction failed". I can always reproduce the problem using Streetview function inside maps.google.com using Firefox (77.0.1). My kernel version is 5.4.0-38 and my graphic card is an old Nvidia 01:00.0 VGA compatible controller: NVIDIA Corporation G86M [GeForce 8400M GS] (rev a1 When I switch to closed source Nvidia proprietary driver (ver. 340.108) I have no issues. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michele1586 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=4e56d43d-0da0-4af9-a55c-035f04c115bf InstallationDate: Installed on 2017-11-13 (952 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer Aspire 5720 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-38-generic root=UUID=28547816-80be-43c8-a86e-d655d7d8ad5e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-38.42-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-38-generic N/A linux-backports-modules-5.4.0-38-generic N/A linux-firmware1.187.1 StagingDrivers: ashmem_linux Tags: focal staging Uname: Linux 5.4.0-38-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (60 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp _MarkForUpload: True dmi.bios.date: 11/10/2008 dmi.bios.vendor: Acer dmi.bios.version: V1.45 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Nettiling dmi.board.vendor: Acer dmi.board.version: V1.45 dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: V1.45 dmi.modalias: dmi:bvnAcer:bvrV1.45:bd11/10/2008:svnAcer:pnAspire5720:pvrV1.45:rvnAcer:rnNettiling:rvrV1.45:cvnAcer:ct1:cvrV1.45: dmi.product.family: None dmi.product.name: Aspire 5720 dmi.product.sku: None dmi.product.version: V1.45 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2019-08-08T12:13:15.951541 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884726/+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 1786013] Autopkgtest regression report (linux-meta-oracle-5.4/5.4.0.1074.80~18.04.53)
All autopkgtests for the newly accepted linux-meta-oracle-5.4 (5.4.0.1074.80~18.04.53) for bionic have finished running. The following regressions have been reported in tests triggered by the package: kpatch/0.5.0-0ubuntu1.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
Same issue here. Heavy black flickering on the screen with Ubuntu 22.04 after upgrade from 20.04 and after a clean install. No extra repos, only default packages. Aspire 3 A315-31 series N17Q2 Mesa Intel® HD Graphics 500 (APL 2) Linux laptop 5.15.0-33-generic #34-Ubuntu SMP Wed May 18 13:34:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+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 1884726] Re: [TTM] Buffer eviction failed
Update info: 01:00.0 VGA compatible controller: NVIDIA Corporation G96 [GeForce 9500 GT] (rev a1) I can work with intensive GPU accel (opengl / opengles) without any crashes. With the browser (Chrome,Chromium,Brave, and recently i have read about the TTM crash with Firefox), it can crash the computer after a few minutes while scrolling down the page with lots of ads. I am not sure if the bug is in TTM/drm or the GPU userspace in the browser. But Chromium crashes right after login into lightdm. I was not even aware chromium had a background thread running. Just for Information, here is how chromium is rendering the page, looks like corrupt page. ** Attachment added: "corrupt rendering" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884726/+attachment/5594364/+files/2022-06-01-160634_1920x1080_scrot.png -- 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/1884726 Title: [TTM] Buffer eviction failed Status in linux package in Ubuntu: Expired Bug description: Under some usage conditions on Ubuntu 20.04 I get an almost complete system freeze and after some minutes I get this issuing a dmesg command: "[TTM] Buffer eviction failed". I can always reproduce the problem using Streetview function inside maps.google.com using Firefox (77.0.1). My kernel version is 5.4.0-38 and my graphic card is an old Nvidia 01:00.0 VGA compatible controller: NVIDIA Corporation G86M [GeForce 8400M GS] (rev a1 When I switch to closed source Nvidia proprietary driver (ver. 340.108) I have no issues. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michele1586 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=4e56d43d-0da0-4af9-a55c-035f04c115bf InstallationDate: Installed on 2017-11-13 (952 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer Aspire 5720 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-38-generic root=UUID=28547816-80be-43c8-a86e-d655d7d8ad5e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-38.42-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-38-generic N/A linux-backports-modules-5.4.0-38-generic N/A linux-firmware1.187.1 StagingDrivers: ashmem_linux Tags: focal staging Uname: Linux 5.4.0-38-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (60 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp _MarkForUpload: True dmi.bios.date: 11/10/2008 dmi.bios.vendor: Acer dmi.bios.version: V1.45 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Nettiling dmi.board.vendor: Acer dmi.board.version: V1.45 dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: V1.45 dmi.modalias: dmi:bvnAcer:bvrV1.45:bd11/10/2008:svnAcer:pnAspire5720:pvrV1.45:rvnAcer:rnNettiling:rvrV1.45:cvnAcer:ct1:cvrV1.45: dmi.product.family: None dmi.product.name: Aspire 5720 dmi.product.sku: None dmi.product.version: V1.45 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2019-08-08T12:13:15.951541 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884726/+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 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise on AMD Caicos
** Attachment removed: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5311593/+files/modified.conffile..etc.gdm3.custom.conf.txt ** Attachment removed: "This is what I see (taken from a camera) after Ubuntu finishes booting and loads the login manager." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5150317/+files/i5Fee.jpg ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5150318/+files/Dependencies.txt ** Attachment removed: "Output of "lspci -k"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5154814/+files/output.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5150319/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "xrandr" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5173498/+files/xrandr.txt ** Attachment removed: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5173499/+files/dmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5311591/+files/Dependencies.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308778/+files/Dependencies.txt ** Attachment removed: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5310808/+files/modified.conffile..etc.gdm3.custom.conf.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308779/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308780/+files/modified.conffile..etc.gdm3.custom.conf.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308786/+files/CurrentDmesg.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5311592/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308787/+files/DpkgLog.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308788/+files/Lspci.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308789/+files/Lsusb.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308790/+files/ProcCpuinfo.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308791/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308792/+files/ProcModules.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308793/+files/UdevDb.txt ** Attachment removed: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308794/+files/xdpyinfo.txt ** Attachment removed: "Xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308795/+files/Xrandr.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308796/+files/Dependencies.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308797/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308798/+files/modified.conffile..etc.gdm3.custom.conf.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5310806/+files/Dependencies.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5310807/+files/ProcCpuinfoMinimal.txt ** Information type changed from Public to Private -- 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/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise on AMD Caicos Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu
[Kernel-packages] [Bug 1870597] Re: libinput says "your system is too slow"
** Attachment removed: "BootLog.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350642/+files/BootLog.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350644/+files/Lspci.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5345771/+files/Dependencies.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5345772/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ShellJournal.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5345773/+files/ShellJournal.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350643/+files/CurrentDmesg.txt ** Attachment removed: "Lsusb-t.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350646/+files/Lsusb-t.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350645/+files/Lsusb.txt ** Attachment removed: "Lsusb-v.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350647/+files/Lsusb-v.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350648/+files/ProcCpuinfo.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350649/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350650/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350651/+files/ProcModules.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350652/+files/UdevDb.txt ** Attachment removed: "Xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350653/+files/Xrandr.txt ** Attachment removed: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350654/+files/xdpyinfo.txt ** Description changed: - During the freeze, the output of the install had a message from "gdm-x- - session" saying "your system is too slow". - - To reproduce: - 1. Launch the Ubuntu installer - 2. Begin the installation process - 3. When the installation process begins, move the cursor around - 4. Notice how the PC freezes and drops mouse events - - Description: Ubuntu Focal Fossa (development branch) - Release: 20.04 - - gnome-shell: - Installed: 3.36.0-2ubuntu2 - Candidate: 3.36.0-2ubuntu2 - Version table: - *** 3.36.0-2ubuntu2 500 - 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages - 100 /var/lib/dpkg/status - - ProblemType: Bug - DistroRelease: Ubuntu 20.04 - Package: gnome-shell 3.36.0-2ubuntu2 - ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 - Uname: Linux 5.4.0-21-generic x86_64 - NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair - ApportVersion: 2.20.11-0ubuntu21 - Architecture: amd64 - CasperVersion: 1.442 - Date: Fri Apr 3 14:24:21 2020 - DisplayManager: gdm3 - GsettingsChanges: - - LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash - RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 - SourcePackage: gnome-shell - UpgradeStatus: No upgrade log present (probably fresh install) - --- - ProblemType: Bug - ApportVersion: 2.20.11-0ubuntu22 - Architecture: amd64 - CasperVersion: 1.442 - CompositorRunning: None - DistUpgraded: Fresh install - DistroCodename: focal - DistroRelease: Ubuntu 20.04 - DistroVariant: ubuntu - ExtraDebuggingInterest: Yes - GraphicsCard: - Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Dell UHD Graphics 620 [1028:0810] - LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) - MachineType: Dell Inc. Inspiron 5570 - NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair - Package: xorg-server (not installed) - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash - ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- - ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 - Tags: focal ubuntu - Uname: Linux 5.4.0-21-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: - - _MarkForUpload: True - dmi.bios.date: 05/15/2019 - dmi.bios.vendor: Dell Inc. - dmi.bios.version: 1.2.3 - dmi.board.name: 09YTN7 -
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-bluefield/5.4.0.1037.38)
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1037.38) for focal have finished running. The following regressions have been reported in tests triggered by the package: glibc/unknown (arm64) mali-midgard/unknown (arm64) wireguard-linux-compat/1.0.20201112-1~20.04.1 (arm64) lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64) bbswitch/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1975621] Re: [Star Labs Lite IV] screen flashes on-off unless PSR is turned off
I am trying something new : since the machine is using Wayland I have removeed the following package that was installed by default (as [installed,automatic]) : xserver-xorg-video-intel Seen on the following post that it could help : https://forums.debian.net/viewtopic.php?t=149472 Will report tomorrow if this helps fixing the problem. -- 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/1975621 Title: [Star Labs Lite IV] screen flashes on-off unless PSR is turned off Status in linux package in Ubuntu: Confirmed Bug description: Laptop is a Starlabs Lite Mv IV Integrated graphic card is Mesa Intel® UHD Graphics 605 (GLK 3) Screen backlight turns off and on quickly from time to time Seems to be random : can happen several times per minute, then nothing happens for a few minutes. Seems to happen more often if the graphic card load is increased. Might be related to the graphic card core temperature/load-related. Fixed the problem by adding the following kernel option : i915.enable_psr=0 [3.868968] i915 :00:02.0: [drm] Unknown revid 0x06 [3.869555] i915 :00:02.0: [drm] VT-d active for gfx access [3.869566] fb0: switching to i915 from EFI VGA [3.869878] i915 :00:02.0: vgaarb: deactivate vga console [3.921387] i915 :00:02.0: [drm] couldn't get memory information [3.922325] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [3.923660] i915 :00:02.0: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v1.4) [4.222037] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 [4.222440] snd_hda_intel :00:0e.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.561945] fbcon: i915drmfb (fb0) is primary device [4.593816] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device [ 4954.090871] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Machine has latest firmware (CoreBoot) And its Ubuntu is the latest LTS, kept up to date. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 24 19:38:39 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation GeminiLake [UHD Graphics 605] [8086:2212] InstallationDate: Installed on 2022-04-26 (28 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Star Labs Lite ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash mitigations=off i915.enable_psr=0 vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2022 dmi.bios.release: 4.16 dmi.bios.vendor: coreboot dmi.bios.version: 4.16 dmi.board.name: Lite dmi.board.vendor: Star Labs dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Star Labs dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4: dmi.product.family: I4 dmi.product.name: Lite dmi.product.sku: I4 dmi.product.version: 1.0 dmi.sys.vendor: Star Labs version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1976533] Re: [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- 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/1976533 Title: [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Description: s390/dasd: Fix data corruption for ESE devices Symptom: Filesystem errors and data inconsistency. Problem: Wrong tracks are formatted or the same track is formatted twice. 1. For ESE devices we get an error when accessing an unformatted track. The handling of this error will return zero data for read requests and format the track on demand before writing to it. To do this the code needs to distinguish between read and write requests. This is done with data from the blocklayer request. A pointer to the blocklayer request is stored in the CQR. If there is an error on the device an ERP request is built to do error recovery. While the ERP request is mostly a copy of the original CQR the pointer to the blocklayer request is not copied to not accidentally pass it back to the blocklayer without cleanup. This leads to the error that during ESE handling after an ERP request was built it is not possible to determine the IO direction. This leads to the formatting of a track for read requests which might in turn lead to data corruption. 2. When using alias devices a track might be accessed by multiple requests simultaneously and there is a race window that a track gets formatted twice resulting in data loss. Solution: 1. Return the callback data of the original request in case there are ERP requests build on top of it and thus determine the correct IO direction. 2. Prevent the double format by remembering the amount of formatted tracks when starting a request and comparing this number before actually formatting a track on the fly. If the number has changed there is a chance that the current track was finally formatted in between. As a result do not format the track and restart the current IO to check. Reproduction: Prepare an ESE DASD device using dasdfmt and fdasd. Install any filesystem on the prepared partitions and issue regular I/O using dd or any other tool while Alias DASD devices are set online as well. Upstream-ID: 5b53a405e4658580e1faf7c217db3f55a21ba849 71f3871657370dbbaf942a1c758f64e49a36c70f Problem-ID:198418 Preventive:yes Date: 2022-06-01 Author:hoepp...@linux.ibm.com Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1976533/+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 1976533] [NEW] [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices
Public bug reported: Description: s390/dasd: Fix data corruption for ESE devices Symptom: Filesystem errors and data inconsistency. Problem: Wrong tracks are formatted or the same track is formatted twice. 1. For ESE devices we get an error when accessing an unformatted track. The handling of this error will return zero data for read requests and format the track on demand before writing to it. To do this the code needs to distinguish between read and write requests. This is done with data from the blocklayer request. A pointer to the blocklayer request is stored in the CQR. If there is an error on the device an ERP request is built to do error recovery. While the ERP request is mostly a copy of the original CQR the pointer to the blocklayer request is not copied to not accidentally pass it back to the blocklayer without cleanup. This leads to the error that during ESE handling after an ERP request was built it is not possible to determine the IO direction. This leads to the formatting of a track for read requests which might in turn lead to data corruption. 2. When using alias devices a track might be accessed by multiple requests simultaneously and there is a race window that a track gets formatted twice resulting in data loss. Solution: 1. Return the callback data of the original request in case there are ERP requests build on top of it and thus determine the correct IO direction. 2. Prevent the double format by remembering the amount of formatted tracks when starting a request and comparing this number before actually formatting a track on the fly. If the number has changed there is a chance that the current track was finally formatted in between. As a result do not format the track and restart the current IO to check. Reproduction: Prepare an ESE DASD device using dasdfmt and fdasd. Install any filesystem on the prepared partitions and issue regular I/O using dd or any other tool while Alias DASD devices are set online as well. Upstream-ID: 5b53a405e4658580e1faf7c217db3f55a21ba849 71f3871657370dbbaf942a1c758f64e49a36c70f Problem-ID:198418 Preventive:yes Date: 2022-06-01 Author:hoepp...@linux.ibm.com Component: kernel ** Affects: ubuntu-z-systems Importance: High Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-198422 severity-high targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-198422 severity-high targetmilestone-inin2004 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- 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/1976533 Title: [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Description: s390/dasd: Fix data corruption for ESE devices Symptom: Filesystem errors and data inconsistency. Problem: Wrong tracks are formatted or the same track is formatted twice. 1. For ESE devices we get an error when accessing an unformatted track. The handling of this error will return zero data for read requests and format the track on demand before writing to it. To do this the code needs to distinguish between read and write requests. This is done with data from the blocklayer request. A pointer to the blocklayer request is stored in the CQR. If there is an error on the device an ERP request is built to do error recovery. While the ERP request is mostly a copy of the original CQR the pointer to the blocklayer request is not copied to not accidentally pass it back to the blocklayer without cleanup. This leads to the error that during ESE handling after an ERP request was built it is not possible to determine the IO direction. This leads to the formatting of a track for read requests which might in turn lead to data corruption. 2. When using alias devices a track might
[Kernel-packages] [Bug 1976533] [NEW] [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices
You have been subscribed to a public bug: Description: s390/dasd: Fix data corruption for ESE devices Symptom: Filesystem errors and data inconsistency. Problem: Wrong tracks are formatted or the same track is formatted twice. 1. For ESE devices we get an error when accessing an unformatted track. The handling of this error will return zero data for read requests and format the track on demand before writing to it. To do this the code needs to distinguish between read and write requests. This is done with data from the blocklayer request. A pointer to the blocklayer request is stored in the CQR. If there is an error on the device an ERP request is built to do error recovery. While the ERP request is mostly a copy of the original CQR the pointer to the blocklayer request is not copied to not accidentally pass it back to the blocklayer without cleanup. This leads to the error that during ESE handling after an ERP request was built it is not possible to determine the IO direction. This leads to the formatting of a track for read requests which might in turn lead to data corruption. 2. When using alias devices a track might be accessed by multiple requests simultaneously and there is a race window that a track gets formatted twice resulting in data loss. Solution: 1. Return the callback data of the original request in case there are ERP requests build on top of it and thus determine the correct IO direction. 2. Prevent the double format by remembering the amount of formatted tracks when starting a request and comparing this number before actually formatting a track on the fly. If the number has changed there is a chance that the current track was finally formatted in between. As a result do not format the track and restart the current IO to check. Reproduction: Prepare an ESE DASD device using dasdfmt and fdasd. Install any filesystem on the prepared partitions and issue regular I/O using dd or any other tool while Alias DASD devices are set online as well. Upstream-ID: 5b53a405e4658580e1faf7c217db3f55a21ba849 71f3871657370dbbaf942a1c758f64e49a36c70f Problem-ID:198418 Preventive:yes Date: 2022-06-01 Author:hoepp...@linux.ibm.com Component: kernel ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-198422 severity-high targetmilestone-inin2004 -- [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices https://bugs.launchpad.net/bugs/1976533 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 1976531] Status changed to Confirmed
This change was made by a bot. ** 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/1976531 Title: Mouse is no longer recognized after I suspend my PC and wake it back up Status in linux package in Ubuntu: Confirmed Bug description: When I went to Suspend my PC, I woke it back up again. I returned to the Lock Screen as expected. However, even though my keyboard responded to button pushes, the mouse connected did not light up at all; it was no longer receiving power until I unplugged the mouse and plugged it back in. The mouse, like the keyboard, should have had power sent to it when the PC woke up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rose842 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 12:06:47 2022 InstallationDate: Installed on 2022-05-22 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=804dde02-f626-4837-9802-fcd2a3da1eeb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:br4.6:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:sku: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976531/+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 1976531] [NEW] Mouse is no longer recognized after I suspend my PC and wake it back up
Public bug reported: When I went to Suspend my PC, I woke it back up again. I returned to the Lock Screen as expected. However, even though my keyboard responded to button pushes, the mouse connected did not light up at all; it was no longer receiving power until I unplugged the mouse and plugged it back in. The mouse, like the keyboard, should have had power sent to it when the PC woke up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rose842 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 12:06:47 2022 InstallationDate: Installed on 2022-05-22 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=804dde02-f626-4837-9802-fcd2a3da1eeb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:br4.6:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:sku: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1976531 Title: Mouse is no longer recognized after I suspend my PC and wake it back up Status in linux package in Ubuntu: New Bug description: When I went to Suspend my PC, I woke it back up again. I returned to the Lock Screen as expected. However, even though my keyboard responded to button pushes, the mouse connected did not light up at all; it was no longer receiving power until I unplugged the mouse and plugged it back in. The mouse, like the keyboard, should have had power sent to it when the PC woke up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rose842 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 12:06:47 2022 InstallationDate: Installed on 2022-05-22 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=804dde02-f626-4837-9802-fcd2a3da1eeb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:br4.6:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:sku: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
** Changed in: grub2 (Ubuntu) Assignee: Didier Roche (didrocks) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+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 1875767] Re: When operating install/removal with apt, zed floods log and apparently crashes snapshoting
** Changed in: zsys (Ubuntu) Assignee: Didier Roche (didrocks) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1875767 Title: When operating install/removal with apt, zed floods log and apparently crashes snapshoting Status in zfs-linux package in Ubuntu: Won't Fix Status in zsys package in Ubuntu: Incomplete Bug description: Hello! When I ran a install, it behaved like this: ERROR rpc error: code = DeadlineExceeded desc = context deadline exceeded ... etc apt messages ... A processar 'triggers' para libc-bin (2.31-0ubuntu9) ... ERROR rpc error: code = Unavailable desc = transport is closing Log gets flooded by the follow message: abr 28 20:41:48 manauara zed[512257]: eid=10429 class=history_event pool_guid=0x7E8B0F177C4DD12C abr 28 20:41:49 manauara zed[508106]: Missed 1 events And machine load gets high for incredible amount of time. Workarround is: systemctl restart zsysd systemctl restart zed System also gets a bit slow and fans get high for a while (because the load). This is a fresh install of ubuntu 20.04 with ZFS on SATA SSD. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 28 20:49:14 2020 InstallationDate: Installed on 2020-04-27 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1875767/+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 1975582] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2022-06-01 10:42 EDT--- We now queued these patches on the upstream s390 tree targeting 5.19 https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=for-next=3ae11dbcfac906a8c3a480e98660a823130dc16a https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=for- next=6d5946274df1fff539a7eece458a43be733d1db8 -- 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/1975582 Title: [UBUNTU 20.04] rcu stalls with many storage key guests Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: ---Problem Description--- There can be rcu stalls when running lots of large guests with storage keys: [1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU [1377614.579845] rcu: 18-: (2099 ticks this GP) idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 [1377614.579895](t=2100 jiffies g=155867385 q=20879) [1377614.579898] Task dump for CPU 18: [1377614.579899] CPU 1/KVM R running task0 1030947 256019 0x0604 [1377614.579902] Call Trace: [1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0) [1377614.579918] [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 [1377614.579919] [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 [1377614.579924] [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 [1377614.579926] [<001f1eceb26c>] update_process_times+0x3c/0x80 [1377614.579931] [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 [1377614.579932] [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 [1377614.579933] [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 [1377614.579935] [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 [1377614.579938] [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 [1377614.579942] [<001f1f4c6d08>] ext_int_handler+0x130/0x134 [1377614.579945] [<001f1ec0af10>] ptep_zap_key+0x40/0x60 Contact Information = cborn...@de.ibm.com ---uname output--- RELEASE: 5.4.0-90-generic VERSION: #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021 == Comment: #1 - Christian Borntraeger - 2022-05-24 03:59:37 == This is a test patch that might address the rcu stalls. == Comment: #2 - Christian Borntraeger - 2022-05-24 04:00:22 == This is a 2nd patch that reduces the cost of key setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1975582/+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 1974241] Re: mlxbf_gige: revert "add interrupt counts" commit
This bug is awaiting verification that the linux-bluefield/5.4.0-1037.40 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' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1974241 Title: mlxbf_gige: revert "add interrupt counts" commit Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] There is a mlxbf_gige driver commit (ed0dd97e64a5) which pertains to "UBUNTU: SAUCE: mlxbf_gige: add interrupt counts to "ethtool -S". This logic is modified in upstream Linux, so this SAUCE commit will need to be reverted. [Fix] The fix is to revert this driver commit. [Test Case] With this commit reverted the driver should function as before (e.g. probe succeeds, oob_net0 link up, etc) EXCEPT that the output of "ethtool -S" will no longer show the interrupt counts. [Regression Potential] The amount of driver logic being reverted is quite small, so no potential for creating a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1974241/+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 1974096] Re: cls_flower: Fix inability to match GRE/IPIP packets
This bug is awaiting verification that the linux-bluefield/5.4.0-1037.40 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' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1974096 Title: cls_flower: Fix inability to match GRE/IPIP packets Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug When a packet of a new flow arrives in openvswitch kernel module, it dissects the packet and passes the extracted flow key to ovs-vswtichd daemon. If hw- offload configuration is enabled, the daemon creates a new TC flower entry to bypass openvswitch kernel module for the flow (TC flower can also offload flows to NICs but this time that does not matter). In this processing flow, I found the following issue in cases of GRE/IPIP packets. When ovs_flow_key_extract() in openvswitch module parses a packet of a new GRE (or IPIP) flow received on non-tunneling vports, it extracts information of the outer IP header for ip_proto/src_ip/dst_ip match keys. This means ovs-vswitchd creates a TC flower entry with IP protocol/addresses match keys whose values are those of the outer IP header. OTOH, TC flower, which uses flow_dissector (different parser from openvswitch module), extracts information of the inner IP header. * How to test The following flow is an example to describe the issue in more detail. <--- Outer IP -> <-- Inner IP --> +--+--+--+--+--+--+ | ip_proto | src_ip | dst_ip | ip_proto | src_ip | dst_ip | | 47 (GRE) | 192.168.10.1 | 192.168.10.2 | 6 (TCP) | 10.0.0.1 | 10.0.0.2 | +--+--+--+--+--+--+ In this case, TC flower entry and extracted information are shown as below: - ovs-vswitchd creates TC flower entry with: - ip_proto: 47 - src_ip: 192.168.10.1 - dst_ip: 192.168.10.2 - TC flower extracts below for IP header matches: - ip_proto: 6 - src_ip: 10.0.0.1 - dst_ip: 10.0.0.2 Thus, GRE or IPIP packets never match the TC flower entry, as each dissector behaves differently. IMHO, the behavior of TC flower (flow dissector) does not look correct, as ip_proto/src_ip/dst_ip in TC flower match means the outermost IP header information except for GRE/IPIP cases. This patch adds a new flow_dissector flag FLOW_DISSECTOR_F_STOP_BEFORE_ENCAP which skips dissection of the encapsulated inner GRE/IPIP header in TC flower classifier. * What it could break. N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1974096/+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 1974246] Re: mlxbf_gige: increase MDIO polling rate
This bug is awaiting verification that the linux-bluefield/5.4.0-1037.40 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' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1974246 Title: mlxbf_gige: increase MDIO polling rate Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] There is MDIO logic within the mlxbf_gige driver that currently polls for completed transactions every 100us. This has been reviewed and tested in the lab and found to be inefficient. [Fix] The fix is to modify the driver logic to increase the MDIO polling rate to 5us. With this change the amount of time spent waiting for the MDIO BUSY signal to de-assert drops from ~100us to ~27us for each operation. [Test Case] The driver should function as before, specifically: * driver probes successfully * oob_net0 link comes up, as seen with "ifconfig -a" * reset and power cycle testing toggle PHY hardware, and oob_net0 link still comes up [Regression Potential] This change affects all MDIO transactions to the board-level PHY device, and as such, could cause a regression with PHY communications. However, this change has been heavily tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1974246/+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 1976511] Re: kernel taint ( warning ) caused by smpboot.c: on 5.4.0
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: Apr 6 02:33:31 G292-280 kernel: [0.007531] [ cut here ] Apr 6 02:33:31 G292-280 kernel: [0.007531] sched: CPU #20's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. Apr 6 02:33:31 G292-280 kernel: [0.007531] WARNING: CPU: 20 PID: 0 at /build/linux-hwe-5.4-9Mb2g5/linux-hwe-5.4-5.4.0/arch/x86/kernel/smpboot.c:426 topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Modules linked in: Apr 6 02:33:31 G292-280 kernel: [0.007531] CPU: 20 PID: 0 Comm: swapper/20 Not tainted 5.4.0-107-generic #121~18.04.1-Ubuntu Apr 6 02:33:31 G292-280 kernel: [0.007531] Hardware name: GIGABYTE G292-280-00/MG52-G20-00, BIOS F02 10/28/2021 Apr 6 02:33:31 G292-280 kernel: [0.007531] RIP: 0010:topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Code: 41 5c 5d c3 80 3d 1e 75 ba 01 00 75 ec 89 f1 41 89 d9 89 fe 45 89 e0 48 c7 c7 b8 00 b4 a6 c6 05 04 75 ba 01 01 e8 b4 c7 03 00 <0f> 0b eb cb 0f 1f 44 00 00 55 0f b6 05 a3 8d f0 01 c6 05 9c 8d f0 Apr 6 02:33:31 G292-280 kernel: [0.007531] RSP: :b76b58e17eb8 EFLAGS: 00010086 Apr 6 02:33:31 G292-280 kernel: [0.007531] RAX: RBX: RCX: a7264e88 Apr 6 02:33:31 G292-280 kernel: [0.007531] RDX: a7264e88 RSI: 0096 RDI: 0046 Apr 6 02:33:31 G292-280 kernel: [0.007531] RBP: b76b58e17ec8 R08: R09: 0002f680 Apr 6 02:33:31 G292-280 kernel: [0.007531] R10: 8b69bf80 R11: 02c0 R12: 0001 Apr 6 02:33:31 G292-280 kernel: [0.007531] R13: 0014 R14: 0014 R15: 0002 Apr 6 02:33:31 G292-280 kernel: [0.007531] FS: () GS:8b69bf80() knlGS: Apr 6 02:33:31 G292-280 kernel: [0.007531] CS: 0010 DS: ES: CR0: 80050033 Apr 6 02:33:31 G292-280 kernel: [0.007531] CR2: CR3: 007ee1a0a001 CR4: 00760ee0 Apr 6 02:33:31 G292-280 kernel: [0.007531] DR0: DR1: DR2: Apr 6 02:33:31 G292-280 kernel: [0.007531] DR3: DR6: fffe0ff0 DR7: 0400 Apr 6 02:33:31 G292-280 kernel: [0.007531] PKRU: Apr 6 02:33:31 G292-280 kernel: [0.007531] Call Trace: Apr 6 02:33:31 G292-280 kernel: [0.007531] set_cpu_sibling_map+0x14f/0x600 Apr 6 02:33:31 G292-280 kernel: [0.007531] start_secondary+0x6e/0x1c0 Apr 6 02:33:31 G292-280 kernel: [0.007531] secondary_startup_64+0xa4/0xb0 Apr 6 02:33:31 G292-280 kernel: [0.007531] ---[ end trace 789d1f3abd3d96d4 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+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 1976511] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1976511 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: Incomplete Bug description: Apr 6 02:33:31 G292-280 kernel: [0.007531] [ cut here ] Apr 6 02:33:31 G292-280 kernel: [0.007531] sched: CPU #20's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. Apr 6 02:33:31 G292-280 kernel: [0.007531] WARNING: CPU: 20 PID: 0 at /build/linux-hwe-5.4-9Mb2g5/linux-hwe-5.4-5.4.0/arch/x86/kernel/smpboot.c:426 topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Modules linked in: Apr 6 02:33:31 G292-280 kernel: [0.007531] CPU: 20 PID: 0 Comm: swapper/20 Not tainted 5.4.0-107-generic #121~18.04.1-Ubuntu Apr 6 02:33:31 G292-280 kernel: [0.007531] Hardware name: GIGABYTE G292-280-00/MG52-G20-00, BIOS F02 10/28/2021 Apr 6 02:33:31 G292-280 kernel: [0.007531] RIP: 0010:topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Code: 41 5c 5d c3 80 3d 1e 75 ba 01 00 75 ec 89 f1 41 89 d9 89 fe 45 89 e0 48 c7 c7 b8 00 b4 a6 c6 05 04 75 ba 01 01 e8 b4 c7 03 00 <0f> 0b eb cb 0f 1f 44 00 00 55 0f b6 05 a3 8d f0 01 c6 05 9c 8d f0 Apr 6 02:33:31 G292-280 kernel: [0.007531] RSP: :b76b58e17eb8 EFLAGS: 00010086 Apr 6 02:33:31 G292-280 kernel: [0.007531] RAX: RBX: RCX: a7264e88 Apr 6 02:33:31 G292-280 kernel: [0.007531] RDX: a7264e88 RSI: 0096 RDI: 0046 Apr 6 02:33:31 G292-280 kernel: [0.007531] RBP: b76b58e17ec8 R08: R09: 0002f680 Apr 6 02:33:31 G292-280 kernel: [0.007531] R10: 8b69bf80 R11: 02c0 R12: 0001 Apr 6 02:33:31 G292-280 kernel: [0.007531] R13: 0014 R14: 0014 R15: 0002 Apr 6 02:33:31 G292-280 kernel: [0.007531] FS: () GS:8b69bf80() knlGS: Apr 6 02:33:31 G292-280 kernel: [0.007531] CS: 0010 DS: ES: CR0: 80050033 Apr 6 02:33:31 G292-280 kernel: [0.007531] CR2: CR3: 007ee1a0a001 CR4: 00760ee0 Apr 6 02:33:31 G292-280 kernel: [0.007531] DR0: DR1: DR2: Apr 6 02:33:31 G292-280 kernel: [0.007531] DR3: DR6: fffe0ff0 DR7: 0400 Apr 6 02:33:31 G292-280 kernel: [0.007531] PKRU: Apr 6 02:33:31 G292-280 kernel: [0.007531] Call Trace: Apr 6 02:33:31 G292-280 kernel: [0.007531] set_cpu_sibling_map+0x14f/0x600 Apr 6 02:33:31 G292-280 kernel: [0.007531] start_secondary+0x6e/0x1c0 Apr 6 02:33:31 G292-280 kernel: [0.007531] secondary_startup_64+0xa4/0xb0 Apr 6 02:33:31 G292-280 kernel: [0.007531] ---[ end trace 789d1f3abd3d96d4 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+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 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
** Attachment removed: "nvidia-bug-report log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934620/+attachment/5592914/+files/nvidia-bug-report.log.gz -- 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+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 1976511] Re: kernel taint ( warning ) caused by smpboot.c: on 5.4.0
You can find above message in kernel.log file. ** Attachment added: "sosreport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+attachment/5594318/+files/sosreport-G292-280-18.04HWE5.4.0-110-generic-2022-05-25-cvumffx.tar.xz -- 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/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: Incomplete Bug description: Apr 6 02:33:31 G292-280 kernel: [0.007531] [ cut here ] Apr 6 02:33:31 G292-280 kernel: [0.007531] sched: CPU #20's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. Apr 6 02:33:31 G292-280 kernel: [0.007531] WARNING: CPU: 20 PID: 0 at /build/linux-hwe-5.4-9Mb2g5/linux-hwe-5.4-5.4.0/arch/x86/kernel/smpboot.c:426 topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Modules linked in: Apr 6 02:33:31 G292-280 kernel: [0.007531] CPU: 20 PID: 0 Comm: swapper/20 Not tainted 5.4.0-107-generic #121~18.04.1-Ubuntu Apr 6 02:33:31 G292-280 kernel: [0.007531] Hardware name: GIGABYTE G292-280-00/MG52-G20-00, BIOS F02 10/28/2021 Apr 6 02:33:31 G292-280 kernel: [0.007531] RIP: 0010:topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Code: 41 5c 5d c3 80 3d 1e 75 ba 01 00 75 ec 89 f1 41 89 d9 89 fe 45 89 e0 48 c7 c7 b8 00 b4 a6 c6 05 04 75 ba 01 01 e8 b4 c7 03 00 <0f> 0b eb cb 0f 1f 44 00 00 55 0f b6 05 a3 8d f0 01 c6 05 9c 8d f0 Apr 6 02:33:31 G292-280 kernel: [0.007531] RSP: :b76b58e17eb8 EFLAGS: 00010086 Apr 6 02:33:31 G292-280 kernel: [0.007531] RAX: RBX: RCX: a7264e88 Apr 6 02:33:31 G292-280 kernel: [0.007531] RDX: a7264e88 RSI: 0096 RDI: 0046 Apr 6 02:33:31 G292-280 kernel: [0.007531] RBP: b76b58e17ec8 R08: R09: 0002f680 Apr 6 02:33:31 G292-280 kernel: [0.007531] R10: 8b69bf80 R11: 02c0 R12: 0001 Apr 6 02:33:31 G292-280 kernel: [0.007531] R13: 0014 R14: 0014 R15: 0002 Apr 6 02:33:31 G292-280 kernel: [0.007531] FS: () GS:8b69bf80() knlGS: Apr 6 02:33:31 G292-280 kernel: [0.007531] CS: 0010 DS: ES: CR0: 80050033 Apr 6 02:33:31 G292-280 kernel: [0.007531] CR2: CR3: 007ee1a0a001 CR4: 00760ee0 Apr 6 02:33:31 G292-280 kernel: [0.007531] DR0: DR1: DR2: Apr 6 02:33:31 G292-280 kernel: [0.007531] DR3: DR6: fffe0ff0 DR7: 0400 Apr 6 02:33:31 G292-280 kernel: [0.007531] PKRU: Apr 6 02:33:31 G292-280 kernel: [0.007531] Call Trace: Apr 6 02:33:31 G292-280 kernel: [0.007531] set_cpu_sibling_map+0x14f/0x600 Apr 6 02:33:31 G292-280 kernel: [0.007531] start_secondary+0x6e/0x1c0 Apr 6 02:33:31 G292-280 kernel: [0.007531] secondary_startup_64+0xa4/0xb0 Apr 6 02:33:31 G292-280 kernel: [0.007531] ---[ end trace 789d1f3abd3d96d4 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+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 1976511] Re: kernel taint ( warning ) caused by smpboot.c: on 5.4.0
We didn't find this on Ubuntu 20.04.4 LTS hwe-kernel ( 5.13.0-41-generic). Both Ubuntu 20.04.4 ga-kernel and 18.04.6 hwe-kernel (5.4.0-107-generic) are found. -- 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/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: Incomplete Bug description: Apr 6 02:33:31 G292-280 kernel: [0.007531] [ cut here ] Apr 6 02:33:31 G292-280 kernel: [0.007531] sched: CPU #20's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. Apr 6 02:33:31 G292-280 kernel: [0.007531] WARNING: CPU: 20 PID: 0 at /build/linux-hwe-5.4-9Mb2g5/linux-hwe-5.4-5.4.0/arch/x86/kernel/smpboot.c:426 topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Modules linked in: Apr 6 02:33:31 G292-280 kernel: [0.007531] CPU: 20 PID: 0 Comm: swapper/20 Not tainted 5.4.0-107-generic #121~18.04.1-Ubuntu Apr 6 02:33:31 G292-280 kernel: [0.007531] Hardware name: GIGABYTE G292-280-00/MG52-G20-00, BIOS F02 10/28/2021 Apr 6 02:33:31 G292-280 kernel: [0.007531] RIP: 0010:topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Code: 41 5c 5d c3 80 3d 1e 75 ba 01 00 75 ec 89 f1 41 89 d9 89 fe 45 89 e0 48 c7 c7 b8 00 b4 a6 c6 05 04 75 ba 01 01 e8 b4 c7 03 00 <0f> 0b eb cb 0f 1f 44 00 00 55 0f b6 05 a3 8d f0 01 c6 05 9c 8d f0 Apr 6 02:33:31 G292-280 kernel: [0.007531] RSP: :b76b58e17eb8 EFLAGS: 00010086 Apr 6 02:33:31 G292-280 kernel: [0.007531] RAX: RBX: RCX: a7264e88 Apr 6 02:33:31 G292-280 kernel: [0.007531] RDX: a7264e88 RSI: 0096 RDI: 0046 Apr 6 02:33:31 G292-280 kernel: [0.007531] RBP: b76b58e17ec8 R08: R09: 0002f680 Apr 6 02:33:31 G292-280 kernel: [0.007531] R10: 8b69bf80 R11: 02c0 R12: 0001 Apr 6 02:33:31 G292-280 kernel: [0.007531] R13: 0014 R14: 0014 R15: 0002 Apr 6 02:33:31 G292-280 kernel: [0.007531] FS: () GS:8b69bf80() knlGS: Apr 6 02:33:31 G292-280 kernel: [0.007531] CS: 0010 DS: ES: CR0: 80050033 Apr 6 02:33:31 G292-280 kernel: [0.007531] CR2: CR3: 007ee1a0a001 CR4: 00760ee0 Apr 6 02:33:31 G292-280 kernel: [0.007531] DR0: DR1: DR2: Apr 6 02:33:31 G292-280 kernel: [0.007531] DR3: DR6: fffe0ff0 DR7: 0400 Apr 6 02:33:31 G292-280 kernel: [0.007531] PKRU: Apr 6 02:33:31 G292-280 kernel: [0.007531] Call Trace: Apr 6 02:33:31 G292-280 kernel: [0.007531] set_cpu_sibling_map+0x14f/0x600 Apr 6 02:33:31 G292-280 kernel: [0.007531] start_secondary+0x6e/0x1c0 Apr 6 02:33:31 G292-280 kernel: [0.007531] secondary_startup_64+0xa4/0xb0 Apr 6 02:33:31 G292-280 kernel: [0.007531] ---[ end trace 789d1f3abd3d96d4 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+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 1976511] [NEW] kernel taint ( warning ) caused by smpboot.c: on 5.4.0
Public bug reported: Apr 6 02:33:31 G292-280 kernel: [0.007531] [ cut here ] Apr 6 02:33:31 G292-280 kernel: [0.007531] sched: CPU #20's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. Apr 6 02:33:31 G292-280 kernel: [0.007531] WARNING: CPU: 20 PID: 0 at /build/linux-hwe-5.4-9Mb2g5/linux-hwe-5.4-5.4.0/arch/x86/kernel/smpboot.c:426 topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Modules linked in: Apr 6 02:33:31 G292-280 kernel: [0.007531] CPU: 20 PID: 0 Comm: swapper/20 Not tainted 5.4.0-107-generic #121~18.04.1-Ubuntu Apr 6 02:33:31 G292-280 kernel: [0.007531] Hardware name: GIGABYTE G292-280-00/MG52-G20-00, BIOS F02 10/28/2021 Apr 6 02:33:31 G292-280 kernel: [0.007531] RIP: 0010:topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Code: 41 5c 5d c3 80 3d 1e 75 ba 01 00 75 ec 89 f1 41 89 d9 89 fe 45 89 e0 48 c7 c7 b8 00 b4 a6 c6 05 04 75 ba 01 01 e8 b4 c7 03 00 <0f> 0b eb cb 0f 1f 44 00 00 55 0f b6 05 a3 8d f0 01 c6 05 9c 8d f0 Apr 6 02:33:31 G292-280 kernel: [0.007531] RSP: :b76b58e17eb8 EFLAGS: 00010086 Apr 6 02:33:31 G292-280 kernel: [0.007531] RAX: RBX: RCX: a7264e88 Apr 6 02:33:31 G292-280 kernel: [0.007531] RDX: a7264e88 RSI: 0096 RDI: 0046 Apr 6 02:33:31 G292-280 kernel: [0.007531] RBP: b76b58e17ec8 R08: R09: 0002f680 Apr 6 02:33:31 G292-280 kernel: [0.007531] R10: 8b69bf80 R11: 02c0 R12: 0001 Apr 6 02:33:31 G292-280 kernel: [0.007531] R13: 0014 R14: 0014 R15: 0002 Apr 6 02:33:31 G292-280 kernel: [0.007531] FS: () GS:8b69bf80() knlGS: Apr 6 02:33:31 G292-280 kernel: [0.007531] CS: 0010 DS: ES: CR0: 80050033 Apr 6 02:33:31 G292-280 kernel: [0.007531] CR2: CR3: 007ee1a0a001 CR4: 00760ee0 Apr 6 02:33:31 G292-280 kernel: [0.007531] DR0: DR1: DR2: Apr 6 02:33:31 G292-280 kernel: [0.007531] DR3: DR6: fffe0ff0 DR7: 0400 Apr 6 02:33:31 G292-280 kernel: [0.007531] PKRU: Apr 6 02:33:31 G292-280 kernel: [0.007531] Call Trace: Apr 6 02:33:31 G292-280 kernel: [0.007531] set_cpu_sibling_map+0x14f/0x600 Apr 6 02:33:31 G292-280 kernel: [0.007531] start_secondary+0x6e/0x1c0 Apr 6 02:33:31 G292-280 kernel: [0.007531] secondary_startup_64+0xa4/0xb0 Apr 6 02:33:31 G292-280 kernel: [0.007531] ---[ end trace 789d1f3abd3d96d4 ]--- ** 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/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: New Bug description: Apr 6 02:33:31 G292-280 kernel: [0.007531] [ cut here ] Apr 6 02:33:31 G292-280 kernel: [0.007531] sched: CPU #20's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. Apr 6 02:33:31 G292-280 kernel: [0.007531] WARNING: CPU: 20 PID: 0 at /build/linux-hwe-5.4-9Mb2g5/linux-hwe-5.4-5.4.0/arch/x86/kernel/smpboot.c:426 topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Modules linked in: Apr 6 02:33:31 G292-280 kernel: [0.007531] CPU: 20 PID: 0 Comm: swapper/20 Not tainted 5.4.0-107-generic #121~18.04.1-Ubuntu Apr 6 02:33:31 G292-280 kernel: [0.007531] Hardware name: GIGABYTE G292-280-00/MG52-G20-00, BIOS F02 10/28/2021 Apr 6 02:33:31 G292-280 kernel: [0.007531] RIP: 0010:topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Code: 41 5c 5d c3 80 3d 1e 75 ba 01 00 75 ec 89 f1 41 89 d9 89 fe 45 89 e0 48 c7 c7 b8 00 b4 a6 c6 05 04 75 ba 01 01 e8 b4 c7 03 00 <0f> 0b eb cb 0f 1f 44 00 00 55 0f b6 05 a3 8d f0 01 c6 05 9c 8d f0 Apr 6 02:33:31 G292-280 kernel: [0.007531] RSP: :b76b58e17eb8 EFLAGS: 00010086 Apr 6 02:33:31 G292-280 kernel: [0.007531] RAX: RBX: RCX: a7264e88 Apr 6 02:33:31 G292-280 kernel: [0.007531] RDX: a7264e88 RSI: 0096 RDI: 0046 Apr 6 02:33:31 G292-280 kernel: [0.007531] RBP: b76b58e17ec8 R08: R09: 0002f680 Apr 6 02:33:31 G292-280 kernel: [0.007531] R10: 8b69bf80 R11: 02c0 R12: 0001 Apr 6 02:33:31 G292-280 kernel: [0.007531] R13: 0014 R14: 0014 R15: 0002 Apr 6 02:33:31 G292-280 kernel: [0.007531] FS:
[Kernel-packages] [Bug 1884726] Re: [TTM] Buffer eviction failed
I have a similar issue with LXDE 18.04. sb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.6 LTS Release:18.04 Codename: bionic It seems to be related to nouveau driver when in use by the chromium web engine. Chrome, Chromium, Brave freeze the system (crash report below), in some occasions if you can kill the browser (if you can) and enter CTRL+DEL several times and wait a few minutes (3 to 10 min). [40802.271418] [TTM] Buffer eviction failed [40802.289063] [ cut here ] [40802.289067] Trying to vfree() bad address (b4473d8e) [40802.289086] WARNING: CPU: 1 PID: 12940 at /build/linux-hwe-5.4-rs4SmW/linux-hwe-5.4-5.4.0/mm/vmalloc.c:2240 __vunmap+0x1fe/0x210 [40802.289087] Modules linked in: cdc_mbim cdc_ncm ppp_deflate bsd_comp ppp_async cdc_ether qmi_wwan cdc_wdm option usbnet usb_wwan usbserial mii nls_utf8 isofs binfmt_misc nouveau mxm_wmi wmi video ttm coretemp kvm_intel drm_kms_helper kvm drm input_leds snd_hda_codec_via snd_hda_codec_generic serio_raw ledtrig_audio snd_hda_intel i2c_algo_bit lpc_ich snd_intel_dspcfg fb_sys_fops snd_hda_codec syscopyarea snd_hda_core sysfillrect sysimgblt asus_atk0110 snd_hwdep mac_hid sch_fq_codel tw5864 solo6x10 videobuf2_dma_contig videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore parport_pc ppdev lp parport ip_tables x_tables autofs4 uas usb_storage psmouse r8169 pata_acpi pata_jmicron realtek [40802.289121] CPU: 1 PID: 12940 Comm: chromium-browse Not tainted 5.4.0-55-generic #61~18.04.1-Ubuntu [40802.289122] Hardware name: System manufacturer System Product Name/P5Q SE PLUS, BIOS 220408/28/2009 [40802.289124] RIP: 0010:__vunmap+0x1fe/0x210 [40802.289126] Code: e8 67 85 e2 ff 0f 0b eb e0 31 d2 31 f6 48 c7 c7 ff ff ff ff e8 c3 fc ff ff eb c6 48 89 fe 48 c7 c7 08 76 36 a0 e8 42 85 e2 ff <0f> 0b eb bb 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 [40802.289126] RSP: 0018:a33e00fa38e0 EFLAGS: 00010286 [40802.289128] RAX: RBX: RCX: 0006 [40802.289128] RDX: 0007 RSI: 0086 RDI: 8e8baba978c0 [40802.289129] RBP: a33e00fa3908 R08: 04f3 R09: 0004 [40802.289130] R10: R11: 0001 R12: 0a80 [40802.289130] R13: 8e8ba133ba80 R14: 251bee76401f R15: 0018 [40802.289132] FS: 7fa148d3fc00() GS:8e8baba8() knlGS: [40802.289132] CS: 0010 DS: ES: CR0: 80050033 [40802.289133] CR2: 7fc3c86f7fd0 CR3: 9707c000 CR4: 000406e0 [40802.289134] Call Trace: [40802.289139] vunmap+0x2f/0x40 [40802.289213] nvkm_umem_unmap+0x4e/0x70 [nouveau] [40802.289233] nvkm_object_dtor+0xa2/0x180 [nouveau] [40802.289254] nvkm_object_del+0x25/0x90 [nouveau] [40802.289274] nvkm_ioctl_del+0x8c/0xa0 [nouveau] [40802.289294] nvkm_ioctl+0x11d/0x280 [nouveau] [40802.289328] nvkm_client_ioctl+0x12/0x20 [nouveau] [40802.289347] nvif_object_ioctl+0x47/0x50 [nouveau] [40802.289366] nvif_object_fini+0x5a/0x80 [nouveau] [40802.289386] nvif_mem_fini+0xe/0x10 [nouveau] [40802.289418] nouveau_mem_fini+0x57/0x70 [nouveau] [40802.289451] nouveau_mem_del+0x1d/0x40 [nouveau] [40802.289483] nouveau_manager_del+0x11/0x20 [nouveau] [40802.289489] ttm_bo_cleanup_memtype_use+0x79/0x80 [ttm] [40802.289492] ttm_bo_release+0x1d9/0x220 [ttm] [40802.289495] ttm_bo_put+0x24/0x30 [ttm] [40802.289528] nouveau_gem_object_del+0x55/0x90 [nouveau] [40802.289554] drm_gem_object_free+0x45/0x80 [drm] [40802.289563] drm_gem_object_put_unlocked+0x53/0x70 [drm] [40802.289571] drm_gem_object_handle_put_unlocked+0x6a/0xb0 [drm] [40802.289580] drm_gem_object_release_handle+0x74/0xa0 [drm] [40802.289588] ? drm_gem_object_handle_put_unlocked+0xb0/0xb0 [drm] [40802.289592] idr_for_each+0x4c/0xd0 [40802.289601] drm_gem_release+0x20/0x30 [drm] [40802.289609] drm_file_free.part.11+0x215/0x260 [drm] [40802.289617] drm_release+0x9e/0xd0 [drm] [40802.289620] __fput+0xc6/0x260 [40802.289621] fput+0xe/0x10 [40802.289624] task_work_run+0x9d/0xc0 [40802.289626] do_exit+0x382/0xb80 [40802.289628] do_group_exit+0x43/0xa0 [40802.289630] get_signal+0x14f/0x860 [40802.289632] do_signal+0x34/0x6d0 [40802.289634] ? do_vfs_ioctl+0xa9/0x640 [40802.289636] ? handle_mm_fault+0xcb/0x210 [40802.289639] exit_to_usermode_loop+0x90/0x130 [40802.289640] do_syscall_64+0x170/0x190 [40802.289642] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [40802.289643] RIP: 0033:0x7fa143499217 [40802.289647] Code: Bad RIP value. [40802.289648] RSP: 002b:7fff72e36638 EFLAGS: 0246 ORIG_RAX: 0010 [40802.289649] RAX: ffea RBX: 556556e71310 RCX: 7fa143499217 [40802.289650] RDX: 7fff72e36690 RSI: c0306480 RDI: 0018 [40802.289651]
[Kernel-packages] [Bug 1976503] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1976503 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1976503 Title: Power cycle USB ports on shutdown/reboot Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Bug description: [Impact] USB storage can be stuck in USB reset loop after reboot. More reboots don't help the situation, unless it's re-plugged. [Fix] Power cycle USB ports on system shutdown/reboot. [Test] The USB storage survived 300 times of reboots, and it works under each reboot cycle. [Where problems could occur] One potential problem I can think of is S5 WoL over USB ethernet. Since the port power and its associated ACPI power are turned off, WoL may stop working, if WoL over USB is a thing. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1976503/+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 1976503] [NEW] Power cycle USB ports on shutdown/reboot
Public bug reported: [Impact] USB storage can be stuck in USB reset loop after reboot. More reboots don't help the situation, unless it's re-plugged. [Fix] Power cycle USB ports on system shutdown/reboot. [Test] The USB storage survived 300 times of reboots, and it works under each reboot cycle. [Where problems could occur] One potential problem I can think of is S5 WoL over USB ethernet. Since the port power and its associated ACPI power are turned off, WoL may stop working, if WoL over USB is a thing. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Tags: oem-priority originate-from-1974127 stella ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided => Medium ** Tags added: oem-priority originate-from-1974127 stella -- 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/1976503 Title: Power cycle USB ports on shutdown/reboot Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Bug description: [Impact] USB storage can be stuck in USB reset loop after reboot. More reboots don't help the situation, unless it's re-plugged. [Fix] Power cycle USB ports on system shutdown/reboot. [Test] The USB storage survived 300 times of reboots, and it works under each reboot cycle. [Where problems could occur] One potential problem I can think of is S5 WoL over USB ethernet. Since the port power and its associated ACPI power are turned off, WoL may stop working, if WoL over USB is a thing. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1976503/+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 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
the fix for oem-5.14 comes via stable updates ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Confirmed Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+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 1970957] Re: suspend problem
Installing kernel 5.18 did not help on my Lenovo Thinkpad P70. System still won't wake from suspend. -- 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/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+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 1912935] Re: battery drain while notebook off / shutdown
I have hp pavillion au624tx and facing the face issue, which is very annoying. It consumes 3% of my battery each hour !! I think, it is something related to power-profiles-daemon, is it possible to switch cpu frequency to balance mode while it is shutting down ? -- 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/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1959215] Re: unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 0000000000001cc8" on Impish with node vought
Found on node vought with F-OEM 5.14.0-1040.44 ** Tags added: 5.14 focal oem sru-20220509 -- 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/1959215 Title: unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 1cc8" on Impish with node vought Status in Stress-ng: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: Issue found on Intel node "vought" with: * 5.13.0-28.31 * 5.13.0-27 * And possibly the 5.13.0-23 from the last cycle (this test didn't finish properly and marked as "Incomplete" back then, just like this cycle). For more earlier Impish kernels, this system was not tested with this test on them. The test will hang with unshare test in ubuntu_stress_smoke_tests: 12:39:39 DEBUG| [stdout] udp RETURNED 0 12:39:39 DEBUG| [stdout] udp PASSED 12:39:39 DEBUG| [stdout] udp-flood STARTING 12:39:41 DEBUG| [stdout] udp-flood RETURNED 0 12:39:41 DEBUG| [stdout] udp-flood PASSED 12:39:41 DEBUG| [stdout] unshare STARTING (Test hangs here) And eventually the test will be killed because of the timeout setting. stress-ng Test suite HEAD SHA1: b81116c Error can be found in dmesg: [ 2371.109961] BUG: unable to handle page fault for address: 1cc8 [ 2371.110074] #PF: supervisor read access in kernel mode [ 2371.114323] #PF: error_code(0x) - not-present page [ 2371.119931] PGD 0 P4D 0 [ 2371.125257] Oops: [#1] SMP NOPTI [ 2371.129247] CPU: 51 PID: 207256 Comm: stress-ng Tainted: P O 5.13.0-27-generic #29-Ubuntu [ 2371.133203] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS SE5C620.86B.0D.01.0395.022720191340 02/27/2019 [ 2371.135887] RIP: 0010:__next_zones_zonelist+0x6/0x50 [ 2371.138525] Code: d0 0f 4e d0 3d ff 03 00 00 7f 0d 48 63 d2 5d 48 8b 04 d5 60 e5 35 af c3 31 c0 5d c3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 <8b> 4f 08 48 89 f8 48 89 e5 48 85 d2 75 10 eb 1d 48 63 49 50 48 0f [ 2371.143813] RSP: 0018:a9c8b399fac0 EFLAGS: 00010282 [ 2371.146078] RAX: RBX: RCX: [ 2371.148293] RDX: 9c98e894ea98 RSI: 0002 RDI: 1cc0 [ 2371.150477] RBP: a9c8b399fb28 R08: R09: [ 2371.152650] R10: 0002 R11: d9bfbfcc5600 R12: 00052cc0 [ 2371.154778] R13: 0002 R14: 0001 R15: 00152cc0 [ 2371.156876] FS: 7fcbd141d740() GS:9cc14ccc() knlGS: [ 2371.158936] CS: 0010 DS: ES: CR0: 80050033 [ 2371.160958] CR2: 1cc8 CR3: 00059f292001 CR4: 007706e0 [ 2371.162950] DR0: DR1: DR2: [ 2371.164888] DR3: DR6: fffe0ff0 DR7: 0400 [ 2371.166811] PKRU: 5554 [ 2371.168694] Call Trace: [ 2371.170544] ? __alloc_pages+0x2f1/0x330 [ 2371.172386] kmalloc_large_node+0x45/0xb0 [ 2371.174222] __kmalloc_node+0x276/0x300 [ 2371.176036] ? queue_delayed_work_on+0x39/0x60 [ 2371.177853] kvmalloc_node+0x5a/0x90 [ 2371.179622] expand_one_shrinker_info+0x82/0x190 [ 2371.181382] prealloc_shrinker+0x175/0x1d0 [ 2371.183091] alloc_super+0x2bf/0x330 [ 2371.184764] ? __fput_sync+0x30/0x30 [ 2371.186384] sget_fc+0x74/0x2e0 [ 2371.187951] ? set_anon_super+0x50/0x50 [ 2371.189473] ? mqueue_create+0x20/0x20 [ 2371.190944] get_tree_keyed+0x34/0xd0 [ 2371.192363] mqueue_get_tree+0x1c/0x20 [ 2371.193734] vfs_get_tree+0x2a/0xc0 [ 2371.195105] fc_mount+0x13/0x50 [ 2371.196409] mq_init_ns+0x10a/0x1b0 [ 2371.197667] copy_ipcs+0x130/0x220 [ 2371.198899] create_new_namespaces+0xa6/0x2e0 [ 2371.200113] unshare_nsproxy_namespaces+0x5a/0xb0 [ 2371.201303] ksys_unshare+0x1db/0x3c0 [ 2371.202480] __x64_sys_unshare+0x12/0x20 [ 2371.203649] do_syscall_64+0x61/0xb0 [ 2371.204804] ? exit_to_user_mode_loop+0xec/0x160 [ 2371.205966] ? exit_to_user_mode_prepare+0x37/0xb0 [ 2371.207102] ? syscall_exit_to_user_mode+0x27/0x50 [ 2371.208222] ? __x64_sys_close+0x11/0x40 [ 2371.209336] ? do_syscall_64+0x6e/0xb0 [ 2371.210438] ? asm_exc_page_fault+0x8/0x30 [ 2371.211545] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2371.212641] RIP: 0033:0x7fcbd1562c4b [ 2371.213698] Code: 73 01 c3 48 8b 0d e5 e1 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 10 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 e1 0e 00 f7 d8 64 89 01 48 [ 2371.215851] RSP: 002b:7ffc5d8eb878 EFLAGS: 0246 ORIG_RAX: 0110 [ 2371.216846] RAX: ffda RBX: 7ffc5d8eba20 RCX: 7fcbd1562c4b [ 2371.217830] RDX:
[Kernel-packages] [Bug 1976488] [NEW] Move focal/linux-azure-fde to 5.15
Public bug reported: [Impact] Use focal/linux-azure-5.15 as based for linux-azure-fde. The 5.15 linux- azure kernel already contains all the changes needed by confidential computing. [Test Plan] The resulting UEFI binary should be able to boot in a CVM instance. [Where problems could occur] Regressions in the upgrade process might happen. However this scenario should be tested before promoting this kernel to focal-updates. ** Affects: linux-azure-fde (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure-fde (Ubuntu Focal) Importance: High Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Also affects: linux-azure-fde (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure-fde (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-azure-fde (Ubuntu Focal) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure-fde (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-fde in Ubuntu. https://bugs.launchpad.net/bugs/1976488 Title: Move focal/linux-azure-fde to 5.15 Status in linux-azure-fde package in Ubuntu: New Status in linux-azure-fde source package in Focal: In Progress Bug description: [Impact] Use focal/linux-azure-5.15 as based for linux-azure-fde. The 5.15 linux-azure kernel already contains all the changes needed by confidential computing. [Test Plan] The resulting UEFI binary should be able to boot in a CVM instance. [Where problems could occur] Regressions in the upgrade process might happen. However this scenario should be tested before promoting this kernel to focal-updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure-fde/+bug/1976488/+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 1976473] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594290/+files/ProcInterrupts.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594291/+files/ProcModules.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594288/+files/ProcCpuinfoMinimal.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594294/+files/UdevDb.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594295/+files/WifiSyslog.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594292/+files/PulseList.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594296/+files/acpidump.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594289/+files/ProcEnviron.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594293/+files/RfKill.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594287/+files/ProcCpuinfo.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594286/+files/PaInfo.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594282/+files/Lspci-vt.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594285/+files/Lsusb-v.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594283/+files/Lsusb.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594284/+files/Lsusb-t.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594280/+files/IwConfig.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594279/+files/CurrentDmesg.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594281/+files/Lspci.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] Re: Unable to change screen brightness in ubuntu desktop
apport information ** Tags added: apport-collected jammy wayland-session ** Description changed: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. - My BIOS is updated to the latest version and I have NVIDIA Driver with - version 510.73.05. + My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: yorozuya 2677 F pulseaudio + /dev/snd/controlC0: yorozuya 2677 F pulseaudio + /dev/snd/controlC1: yorozuya 2677 F pulseaudio + /dev/snd/controlC3: yorozuya 2677 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-05-30 (2 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + MachineType: Dell Inc. Dell G15 5515 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-33-generic N/A + linux-backports-modules-5.15.0-33-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3 + Tags: wayland-session jammy + Uname: Linux 5.15.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/14/2022 + dmi.bios.release: 5.3 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.6.0 + dmi.board.asset.tag: not specified + dmi.board.name: 0TGD6F + dmi.board.vendor: Dell Inc. + dmi.board.version: A04 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: 1.6.0 + dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: + dmi.product.family: GSeries + dmi.product.name: Dell G15 5515 + dmi.product.sku: 0A6E + dmi.product.version: 1.6.0 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1976473/+attachment/5594278/+files/AlsaInfo.txt -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev
[Kernel-packages] [Bug 1970957] Re: suspend problem
Great to hear Andrey. And sorry, I wrote 4.18 but meant 5.18 of course. -- 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/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+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 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
Thanks for replying. See included dmesg. I generated it with the following command ... hopefully OK sudo dmesg -T > dmesg_after_suspend_and_resume.txt Snippet from dmesg: [wo jun 1 11:38:40 2022] i8042: [28649] 65 -> i8042 (parameter) [wo jun 1 11:38:40 2022] i8042: [28649] ab <- i8042 (interrupt, 0, 0) [wo jun 1 11:38:40 2022] i8042: [28650] 83 <- i8042 (interrupt, 0, 1) [wo jun 1 11:38:40 2022] i8042: [28650] f2 -> i8042 (kbd-data) [wo jun 1 11:38:40 2022] i8042: [28652] fa <- i8042 (interrupt, 0, 1) [wo jun 1 11:38:40 2022] i8042: [28653] fa <- i8042 (interrupt, 0, 1) [wo jun 1 11:38:40 2022] i8042: [28653] 60 -> i8042 (command) [wo jun 1 11:38:40 2022] i8042: [28653] 64 -> i8042 (parameter) [wo jun 1 11:38:40 2022] i8042: [28653] 60 -> i8042 (command) ** Attachment added: "dmesg with "i8042.debug=1"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+attachment/5594274/+files/dmesg_after_suspend_and_resume.txt -- 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/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Fresh install of Ubuntu 22.04, fully updated, no changes or configuration at all. Newish HP laptop (so recent hardware) Problem: After resuming from suspend, the laptop's keyboard is not working for about 30 seconds (the laptop's touchpad is working at once). Looking at dmesg, it looks the keyboard only starts working after: [di mei 31 19:10:21 2022] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input106 ... which happens about 35 seconds after the resume sequence completes. From dmesg: suspend: [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [di mei 31 19:06:51 2022] usb 1-1: USB disconnect, device number 2 [di mei 31 19:06:51 2022] PM: suspend entry (s2idle) [di mei 31 19:06:51 2022] Filesystems sync: 0.007 seconds [di mei 31 19:06:51 2022] Freezing user space processes ... (elapsed 0.001 seconds) done. [di mei 31 19:06:51 2022] OOM killer disabled. [di mei 31 19:06:51 2022] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [di mei 31 19:06:51 2022] printk: Suspending console(s) (use no_console_suspend to debug) [di mei 31 19:06:52 2022] ACPI: EC: interrupt blocked After 3 minutes: open laptop lid, and it wakes up: [di mei 31 19:09:45 2022] ACPI: EC: interrupt unblocked [di mei 31 19:09:46 2022] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [di mei 31 19:09:46 2022] OOM killer enabled. [di mei 31 19:09:46 2022] Restarting tasks ... [di mei 31 19:09:46 2022] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821 [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: rom_version status=0 version=1 [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: cfg_sz 10, total sz 31990 [di mei 31 19:09:46 2022] done. [di mei 31 19:09:46 2022] PM: suspend exit [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: fw version 0x829a7644 ... and then after 35 seconds [di mei 31 19:10:21 2022] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input106 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1329 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 31 19:24:02 2022 InstallationDate: Installed on 2022-05-31 (0 days
[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI
A humble request: Just to reiterate myself, please post more comments on the official thread of fujitsu. Hope some engineers wake up! (also in English) https://forum.ts.fujitsu.com/forum/viewtopic.php?f=65=49256 -- 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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+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 1971712] Re: Add support for Intel DG2
works fine on Dell hybrid with ADL iGPU and DG2 dGPU -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1976481] Status changed to Confirmed
This change was made by a bot. ** 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/1976481 Title: ath9k driver takes 100% of CPU since update to 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, I recently updated my home server to Ubuntu 22.04, and since then my WiFi access point (ath9k driver) fails after an hour or so. I saw with htop that one of my CPU core is at 100% of the kernel. With perf top I could find it's spending time in the ath9k driver, in ioread32, see the attachment. Looks like an infinite loop or so. It worked very well before the upgrade. Any idea? Thanks, Tom ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3274 F pulseaudio /dev/snd/controlC1: gdm3274 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Jun 1 10:35:42 2022 InstallationDate: Installed on 2020-08-25 (644 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: ASUSTeK COMPUTER INC. N550JV ProcEnviron: LANG=fr_BE.UTF-8 LANGUAGE=fr_BE:fr PATH=(custom, no user) TERM=screen-256color SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=/dev/mapper/lvgroup-system ro quiet splash vt.handoff=7 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.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-19 (12 days ago) dmi.bios.date: 11/19/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JV.208:bd11/19/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N550JV dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976481/+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 1976481] [NEW] ath9k driver takes 100% of CPU since update to 22.04
Public bug reported: Hi all, I recently updated my home server to Ubuntu 22.04, and since then my WiFi access point (ath9k driver) fails after an hour or so. I saw with htop that one of my CPU core is at 100% of the kernel. With perf top I could find it's spending time in the ath9k driver, in ioread32, see the attachment. Looks like an infinite loop or so. It worked very well before the upgrade. Any idea? Thanks, Tom ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3274 F pulseaudio /dev/snd/controlC1: gdm3274 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Jun 1 10:35:42 2022 InstallationDate: Installed on 2020-08-25 (644 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: ASUSTeK COMPUTER INC. N550JV ProcEnviron: LANG=fr_BE.UTF-8 LANGUAGE=fr_BE:fr PATH=(custom, no user) TERM=screen-256color SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=/dev/mapper/lvgroup-system ro quiet splash vt.handoff=7 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.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-19 (12 days ago) dmi.bios.date: 11/19/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JV.208:bd11/19/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N550JV dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy ** Attachment added: "Capture d’écran 2022-06-01 104143.png" https://bugs.launchpad.net/bugs/1976481/+attachment/5594244/+files/Capture%20d%E2%80%99%C3%A9cran%202022-06-01%20104143.png -- 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/1976481 Title: ath9k driver takes 100% of CPU since update to 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, I recently updated my home server to Ubuntu 22.04, and since then my WiFi access point (ath9k driver) fails after an hour or so. I saw with htop that one of my CPU core is at 100% of the kernel. With perf top I could find it's spending time in the ath9k driver, in ioread32, see the attachment. Looks like an infinite loop or so. It worked very well before the upgrade. Any idea? Thanks, Tom ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3274 F pulseaudio /dev/snd/controlC1: gdm3274 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Jun 1 10:35:42 2022 InstallationDate: Installed on 2020-08-25 (644 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: ASUSTeK COMPUTER INC. N550JV ProcEnviron: LANG=fr_BE.UTF-8 LANGUAGE=fr_BE:fr PATH=(custom, no user) TERM=screen-256color SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=/dev/mapper/lvgroup-system ro quiet splash vt.handoff=7 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.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-19 (12 days ago) dmi.bios.date:
[Kernel-packages] [Bug 1971712] Re: Add support for Intel DG2
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1969966] Re: No support for Intel Killer AX1675i
Work Around Tested in Ubuntu 22.04 (5.15-33 generic) Compile a driver for AX1675i from Intel's instructions Step 1 – Download the Latest Git and Build-Essential packages $ sudo apt update $ sudo apt-get install -y git $ sudo apt-get install -y build-essential Step 2 – Download the Iwlwifi-Firmware.git repository $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git $ cd linux-firmware $ sudo cp iwlwifi-* /lib/firmware/ $ cd .. Step 3 – Create the Backported Iwlwifi Driver for your current setup $ git clone https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git $ cd backport-iwlwifi $ sudo make defconfig-iwlwifi-public $ sudo make -j4 $ sudo make install This command might be necessary to force your machine to use the Driver from boot: $ update-initramfs -u -- 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/1969966 Title: No support for Intel Killer AX1675i Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 5511 laptop but can't get WiFi or Bluetooth. About WiFi I get these logs: ➜ sudo dmesg|grep wifi -i [4.917786] Loading modules backported from iwlwifi [4.917787] iwlwifi-stack-public:master:9858:4c7cba27 [4.984194] Intel(R) Wireless WiFi driver for Linux [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002) [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, rfid=0x2010d000 [4.996123] iwlwifi: probe of :00:14.3 failed with error -22 About Bluetooth I get these logs: ➜ sudo dmesg|grep bluetooth -i [4.977780] Bluetooth: Core ver 2.22 [4.977793] NET: Registered PF_BLUETOOTH protocol family [4.977794] Bluetooth: HCI device and connection manager initialized [4.977799] Bluetooth: HCI socket layer initialized [4.977800] Bluetooth: L2CAP socket layer initialized [4.977803] Bluetooth: SCO socket layer initialized [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018 [5.003784] Bluetooth: hci0: Device revision is 0 [5.003787] Bluetooth: hci0: Secure boot is enabled [5.003788] Bluetooth: hci0: OTP lock is enabled [5.003788] Bluetooth: hci0: API lock is enabled [5.003789] Bluetooth: hci0: Debug lock is disabled [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.006774] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-19-0-3.sfi (-2) [5.007774] Bluetooth: hci0: MSFT supported features length mismatch [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.023201] Bluetooth: BNEP filters: protocol multicast [7.023204] Bluetooth: BNEP socket layer initialized I'm in doubt about WiFi, since the message doesn't mention a missing firmware, but Bluetooth is very clear about it. I'm using Ubuntu 22.04 LTS with bleeding edge kernel 5.17.4. I also tried with 5.18rc1 but no change --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-26 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 20220329.git681281e4-0ubuntu1 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. Tags: jammy Uname: Linux 5.17.4-051704-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-02-03 (83 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969966/+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 1966089] Re: Update OS policy capability handshake
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966089 Title: Update OS policy capability handshake Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: == SRU JAMMY == Update int340x OS policy capability handshake; required for full functionality in thermald 2.4.9 to improve functionality for newer H/W. == The fix == Upstream commit: commit c7ff29763989bd09c433f73fae3c1e1c15d9cda4 Author: Srinivas Pandruvada Date: Mon Mar 14 15:09:37 2022 -0700 thermal: int340x: Update OS policy capability handshake Update the firmware with OS supported policies mask, so that firmware can relinquish its internal controls. Without this update several Tiger Lake laptops gets performance limited with in few seconds of executing in turbo region. The existing way of enumerating firmware policies via IDSP method and selecting policy by directly writing those policy UUIDS via _OSC method is not supported in newer generation of hardware. There is a new UUID "B23BA85D-C8B7-3542-88DE-8DE2FFCFD698" is defined for updating policy capabilities. As part of ACPI _OSC method: Arg0 - UUID: B23BA85D-C8B7-3542-88DE-8DE2FFCFD698 Arg1 - Rev ID: 1 Arg2 - Count: 2 Arg3 - Capability buffers: Array of Arg2 DWORDS DWORD1: As defined in the ACPI 5.0 Specification - Bit 0: Query Flag - Bits 1-3: Always 0 - Bits 4-31: Reserved DWORD2 and beyond: - Bit0: set to 1 to indicate Intel(R) Dynamic Tuning is active, 0 to indicate it is disabled and legacy thermal mechanism should be enabled. - Bit1: set to 1 to indicate Intel(R) Dynamic Tuning is controlling active cooling, 0 to indicate bios shall enable legacy thermal zone with active trip point. - Bit2: set to 1 to indicate Intel(R) Dynamic Tuning is controlling passive cooling, 0 to indicate bios shall enable legacy thermal zone with passive trip point. - Bit3: set to 1 to indicate Intel(R) Dynamic Tuning is handling critical trip point, 0 to indicate bios shall enable legacy thermal zone with critical trip point. - Bits 4:31: Reserved From sysfs interface, there is an existing interface to update policy UUID using attribute "current_uuid". User space can write the same UUID for ACTIVE, PASSIVE and CRITICAL policy. Driver converts these UUIDs to DWORD2 Bit 1 to Bit 3. When any of the policy is activated by user space it is assumed that dynamic tuning is active. For example $cd /sys/bus/platform/devices/INTC1040:00/uuids To support active policy $echo "3A95C389-E4B8-4629-A526-C52C88626BAE" > current_uuid To support passive policy $echo "42A441D6-AE6A-462b-A84B-4A8CE79027D3" > current_uuid To support critical policy $echo "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" > current_uuid To check all the supported policies $cat current_uuid 3A95C389-E4B8-4629-A526-C52C88626BAE 42A441D6-AE6A-462b-A84B-4A8CE79027D3 97C68AE7-15FA-499c-B8C9-5DA81D606E0A To match the bit format for DWORD2, rearranged enum int3400_thermal_uuid and int3400_thermal_uuids[] by swapping current INT3400_THERMAL_ACTIVE and INT3400_THERMAL_PASSIVE_1. If the policies are enumerated via IDSP method then legacy method is used, if not the new method is used to update policy support. Signed-off-by: Srinivas Pandruvada Signed-off-by: Rafael J. Wysocki To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966089/+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 1976281] Re: snapd autopkgtest tests impossible combination of things
I uploaded snapd 2.55.5 as a SRU to all the relevant releases. They are in the "unapproved" queue right now, see e.g. https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=snapd -- 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/1976281 Title: snapd autopkgtest tests impossible combination of things Status in snapd: New Status in linux package in Ubuntu: Incomplete Status in snapd package in Ubuntu: New Bug description: snapd autopkgtest tests impossible combination of things In debian/tests/integrationtests snapd without reexec is enforced # ensure we always run from the deb that is currently tested export SNAP_REEXEC=0 mkdir -p /etc/systemd/system/snapd.service.d cat < /etc/systemd/system/snapd.service.d/no-reexec.conf [Service] Environment=SNAP_REEXEC=$SNAP_REEXEC EOF systemctl daemon-reload systemctl restart snapd In those tests https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/amd64/s/snapd/20220525_161731_b567f@/log.gz installation of core22 is attempted + snap install --edge core22 error: cannot install "core22": snap "core22" assumes unsupported features: snapd2.55.5 (try to refresh snapd) Which now requires snapd 2.55.5 which is not available in stable updates in any releases, maximum is 2.55.3 Please rollback core22 requiring 2.55.5, or ship updates to snapd deb to skip that test case when running with older snapd debs (i.e. make it dependent on 2.55.5+), or please mark snapd autopkgtests of snapd as currently broken in britney & adt-matrix hints. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1976281/+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 1976473] Re: Unable to change screen brightness in ubuntu desktop
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1976473 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Incomplete Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976473] [NEW] Unable to change screen brightness in ubuntu desktop
Public bug reported: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. ** 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/1976473 Title: Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: New Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1976470] [NEW] Jammy update: v5.17.12 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.17.12 upstream stable release
from git://git.kernel.org/
Linux 5.17.12
ALSA: ctxfi: Add SB046x PCI ID
ACPI: sysfs: Fix BERT error region memory mapping
random: check for signals after page of pool writes
random: wire up fops->splice_{read,write}_iter()
random: convert to using fops->write_iter()
random: convert to using fops->read_iter()
random: unify batched entropy implementations
random: move randomize_page() into mm where it belongs
random: move initialization functions out of hot pages
random: make consistent use of buf and len
random: use proper return types on get_random_{int,long}_wait()
random: remove extern from functions in header
random: use static branch for crng_ready()
random: credit architectural init the exact amount
random: handle latent entropy and command line from random_init()
random: use proper jiffies comparison macro
random: remove ratelimiting for in-kernel unseeded randomness
random: move initialization out of reseeding hot path
random: avoid initializing twice in credit race
random: use symbolic constants for crng_init states
siphash: use one source of truth for siphash permutations
random: help compiler out with fast_mix() by using simpler arguments
random: do not use input pool from hard IRQs
random: order timer entropy functions below interrupt functions
random: do not pretend to handle premature next security model
random: use first 128 bits of input as fast init
random: do not use batches when !crng_ready()
random: insist on random_get_entropy() existing in order to simplify
xtensa: use fallback for random_get_entropy() instead of zero
sparc: use fallback for random_get_entropy() instead of zero
um: use fallback for random_get_entropy() instead of zero
x86/tsc: Use fallback for random_get_entropy() instead of zero
nios2: use fallback for random_get_entropy() instead of zero
arm: use fallback for random_get_entropy() instead of zero
mips: use fallback for random_get_entropy() instead of just c0 random
riscv: use fallback for random_get_entropy() instead of zero
m68k: use fallback for random_get_entropy() instead of zero
timekeeping: Add raw clock fallback for random_get_entropy()
powerpc: define get_cycles macro for arch-override
alpha: define get_cycles macro for arch-override
parisc: define get_cycles macro for arch-override
s390: define get_cycles macro for arch-override
ia64: define get_cycles macro for arch-override
init: call time_init() before rand_initialize()
random: fix sysctl documentation nits
random: document crng_fast_key_erasure() destination possibility
random: make random_get_entropy() return an unsigned long
random: allow partial reads if later user copies fail
random: check for signals every PAGE_SIZE chunk of /dev/[u]random
random: check for signal_pending() outside of need_resched() check
random: do not allow user to keep crng key around on stack
random: do not split fast init input in add_hwgenerator_randomness()
random: mix build-time latent entropy into pool at init
random: re-add removed comment about get_random_{u32,u64} reseeding
random: treat bootloader trust toggle the same way as cpu trust toggle
random: skip fast_init if hwrng provides large chunk of entropy
random: check for signal and try earlier when generating entropy
random: reseed more often immediately after booting
random: make consistent usage of crng_ready()
random: use SipHash as interrupt entropy accumulator
random: replace custom notifier chain with standard one
random: don't let 644 read-only sysctls be written to
random: give sysctl_random_min_urandom_seed a more sensible value
random: do crng pre-init loading in worker rather than irq
random: unify cycles_t and jiffies usage and types
random: cleanup UUID handling
random: only wake up writers after zap if threshold was passed
random: round-robin registers as ulong, not u32
random: clear fast pool, crng, and batches in cpuhp bring up
random: pull add_hwgenerator_randomness() declaration into random.h
random: check for crng_init == 0 in add_device_randomness()
random: unify early init crng load accounting
random: do not take pool spinlock at boot
random: defer fast pool mixing to worker
random: rewrite header introductory comment
random: group sysctl functions
random: group userspace read/write functions
random: group entropy collection functions
random: group entropy extraction functions
random: group crng functions
random: group initialization wait functions
random: remove whitespace and reorder includes
random: remove useless
[Kernel-packages] [Bug 1973633] Re: wrong acpi_call sent at boot, how to disable discrete graphic card?
Sure, here is the output of `cat /sys/bus/pci/devices/:03:00.0/power_state`: D0 -- 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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+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 1976398] Re: Screen flickering in Ubuntu 22.04 and Intel UHD graphics (adding "i915.enable_dc=0 intel_idle.max_cstate=2" doesn't help)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-lowlatency (Ubuntu) Status: New => Confirmed -- 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/1976398 Title: Screen flickering in Ubuntu 22.04 and Intel UHD graphics (adding "i915.enable_dc=0 intel_idle.max_cstate=2" doesn't help) Status in linux-signed-lowlatency package in Ubuntu: Confirmed Bug description: Intermittent screen flickering (random moving image sideways). Issues started after upgrade to 22.04 (kernel 5.15, last 5.13 kernel from 21.10 was fine). A similar bug to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 but adding below line to grub options: "i915.enable_dc=0 intel_idle.max_cstate=2" and executing "sudo update-grub" doesn't help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-lowlatency 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-lowlatency 5.15.30 Uname: Linux 5.15.0-33-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue May 31 20:06:18 2022 InstallationDate: Installed on 2021-05-12 (383 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: linux-signed-lowlatency UpgradeStatus: Upgraded to jammy on 2022-05-07 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/1976398/+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 1842320] Re: Out of Memory on boot with 5.2.0 kernel
** Bug watch added: GNU Savannah Bug Tracker #61058 http://savannah.gnu.org/bugs/?61058 ** Also affects: grub via http://savannah.gnu.org/bugs/?61058 Importance: Unknown Status: Unknown -- 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/1842320 Title: Out of Memory on boot with 5.2.0 kernel Status in grub: Unknown Status in OEM Priority Project: In Progress Status in grub2-signed package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d". Can still boot using the previous 5.0.0-25-generic kernel, but the 5.2.0-15-generic fails to start. On selecting Ubuntu from Grub, the message "error: out of memory." is immediately shown. Pressing a key attempts to start boot-up but fails to mount root fs. Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free shows the following (run from Gnome terminal): totalusedfree shared buff/cache available Mem:7906564 1761196 3833240 1020216 2312128 4849224 Swap: 1003516 0 1003516 Kernel packages installed: linux-generic 5.2.0.15.16 amd64 linux-headers-5.2.0-15 5.2.0-15.16 all linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64 linux-headers-generic 5.2.0.15.16 amd64 linux-image-5.0.0-25-generic 5.0.0-25.26 amd64 linux-image-5.2.0-15-generic 5.2.0-15.16+signed1 amd64 linux-image-generic5.2.0.15.16 amd64 linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64 linux-modules-extra-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-extra-5.2.0-15-generic 5.2.0-15.16 amd64 Photo of kernel panic attached. NVMe drive partition layout (GPT): Device StartEnd Sectors Size Type /dev/nvme0n1p120481050623 1048576 512M EFI System /dev/nvme0n1p2 10506242549759 1499136 732M Linux filesystem /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem $ sudo pvs PV VGFmt Attr PSizePFree /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a-- <475.71g0 $ sudo lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root ubuntu-vg -wi-ao 474.75g swap_1 ubuntu-vg -wi-ao 980.00m Partition 3 is LUKS encrypted. Root LV is ext4. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gmckeown 1647 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-15 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision FHD Camera Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.181 Tags: eoan Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-02 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2019 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.25:bd05/17/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku: 2QH38EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1842320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
