[Kernel-packages] [Bug 1956518] Re: linux-firmware 1.187.24 may crash USB ports
We need more data. Please run 'apport-collect 1956518' with the device plugged in that you believe is causing issues. -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1956518/+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 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
There is a "usb 1-14: USB disconnect, device number 5" in the 1013 dmesg, so your bluetooth device is done. Let's see... -- 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/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
could you test latest stable mainline build for 5.14.21: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14.21/ this would show if it's a regression there or in the distro backports -- 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/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1956519] Re: kernel panic after upgrading to kernel 5.13.0-23
Matthew, thanks a lot for your detailed analysis. I stumbled across Evgeny's patch yesterday as a most notable change related to null ptr handling, but totally missed the second patch from Basavaraj too. How peculiar. Anyway, please do let me know once you have a kernel build and I will give it a ride. -- 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/1956519 Title: kernel panic after upgrading to kernel 5.13.0-23 Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: In Progress Bug description: After upgrading my son's Asus PN50 with Ubuntu 21.10 to the latest kernel 5.13.0-23, I am no longer able to boot it normally. Kernel fails with the panic halfway through the boot process (which got overall suspiciously slow): [1.359465] BUG: kernel NULL pointer dereference, address: 000c [1.359498] #PF: supervisor write access in kernel mode [1.359519] #PF: error_code(0x0002) - not-present page [1.359540] PGD 0 P4D 0 [1.359553] Oops: 0002 [#1] SMP NOPTI [1.359569] CPU: 0 PID: 175 Comm: systemd-udevd Not tainted 5.13.0-23-generic #23-Ubuntu [1.359602] Hardware name: ASUSTeK COMPUTER INC. MINIPC PN50/PN50, BIOS 0623 05/13/2021 [1.359632] RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh] [1.359661] Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 00 00 00 e8 23 07 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 00 00 48 8d bb 80 01 00 00 48 c7 c6 20 6d [1.359729] RSP: 0018:bf71c099f9d8 EFLAGS: 00010246 [1.359750] RAX: RBX: RCX: [1.359777] RDX: 0020 RSI: c03cd249 RDI: a680004c [1.359804] RBP: bf71c099fa20 R08: R09: 0006 [1.359831] R10: bf71c0d0 R11: 0007 R12: 000fffe0 [1.359857] R13: 992bc3387cd8 R14: 992bc11560c8 R15: 992bc3387cd8 [1.359884] FS: 7ff0ec1a48c0() GS:992ebf60() knlGS: [1.359915] CS: 0010 DS: ES: CR0: 80050033 [1.359937] CR2: 000c CR3: 000102fd CR4: 00350ef0 [1.359964] Call Trace: [1.359976] ? __pci_set_master+0x5f/0xe0 [1.359997] amd_mp2_pci_probe+0xad/0x160 [amd_sfh] [1.360021] local_pci_probe+0x48/0x80 [1.360038] pci_device_probe+0x105/0x1c0 [1.360056] really_probe+0x24b/0x4c0 [1.360073] driver_probe_device+0xf0/0x160 [1.360091] device_driver_attach+0xab/0xb0 [1.360110] __driver_attach+0xb2/0x140 [1.360126] ? device_driver_attach+0xb0/0xb0 [1.360145] bus_for_each_dev+0x7e/0xc0 [1.360161] driver_attach+0x1e/0x20 [1.360177] bus_add_driver+0x135/0x1f0 [1.360194] driver_register+0x95/0xf0 [1.360210] ? 0xc03d2000 [1.360225] __pci_register_driver+0x57/0x60 [1.360242] amd_mp2_pci_driver_init+0x23/0x1000 [amd_sfh] [1.360266] do_one_initcall+0x48/0x1d0 [1.360284] ? kmem_cache_alloc_trace+0xfb/0x240 [1.360306] do_init_module+0x62/0x290 [1.360323] load_module+0xa8f/0xb10 [1.360340] __do_sys_finit_module+0xc2/0x120 [1.360359] __x64_sys_finit_module+0x18/0x20 [1.360377] do_syscall_64+0x61/0xb0 [1.361638] ? ksys_mmap_pgoff+0x135/0x260 [1.362883] ? exit_to_user_mode_prepare+0x37/0xb0 [1.364121] ? syscall_exit_to_user_mode+0x27/0x50 [1.365343] ? __x64_sys_mmap+0x33/0x40 [1.366550] ? do_syscall_64+0x6e/0xb0 [1.367749] ? do_syscall_64+0x6e/0xb0 [1.368923] ? do_syscall_64+0x6e/0xb0 [1.370079] ? syscall_exit_to_user_mode+0x27/0x50 [1.371227] ? do_syscall_64+0x6e/0xb0 [1.372359] ? exc_page_fault+0x8f/0x170 [1.373478] ? asm_exc_page_fault+0x8/0x30 [1.374584] entry_SYSCALL_64_after_hwframe+0x44/0xae [1.375684] RIP: 0033:0x7ff0ec73a94d [1.376767] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 64 0f 00 f7 d8 64 89 01 48 [1.377926] RSP: 002b:7ffd00724ba8 EFLAGS: 0246 ORIG_RAX: 0139 [1.379076] RAX: ffda RBX: 55e130084390 RCX: 7ff0ec73a94d [1.380225] RDX: RSI: 7ff0ec8ca3fe RDI: 0005 [1.381363] RBP: 0002 R08: R09: [1.382488] R10: 0005 R11: 0246 R12: 7ff0ec8ca3fe [1.383598] R13: 55e130083370 R14: 55e130084480 R15: 55e130086cb0 [1.384698] Modules linked in: ahci(+) libahci i2c_piix4(+) r8169(+) amd_sfh(+) i2c_hid_acpi realtek i2c_hid xhci_pci(+) xhci_pci_renesas wmi(+)
[Kernel-packages] [Bug 1956461] Re: webcam doesn't work
This issue happens starting from kernel 5.4.0-92 and did not occur in kernel 5.4.0-91. Linux Mint 20 Ulyana ** Attachment added: "dmesg+lsusb output from working (5.4.0-91) / not-working (5.4.0-92) kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956461/+attachment/5552992/+files/2022-01-07-webcam-issue.txt ** 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/1956461 Title: webcam doesn't work Status in linux package in Ubuntu: Confirmed Bug description: After installing kernel 5.4.0-92 the webcam Creative HD720p stop to be seen by the system. There is no /dev/vl4/ folder --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 3094 F pulseaudio /dev/snd/controlC0: piotr 3094 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2020-06-07 (578 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-92-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: Tags: uma Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956461/+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 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Invalid Bug description: [Impact] The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot when SEV is enabled. The kernel panics with the following backtrace : [1.531125] ledtrig-cpu: registered to indicate activity on CPUs [1.531760] EFI Variables Facility v0.08 2004-May-17 [1.532575] general protection fault: [#1] SMP NOPTI [1.533116] CPU: 11 PID: 1 Comm: swapper/0 Not tainted 5.4.157-debug6 #15 [1.533788] Hardware name: Scaleway SCW-ENT1-L, BIOS 0.0.0 02/06/2015 [1.534429] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.534949] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.535120] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.535120] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.535120] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.535120] RBP: b96e4001be10 R08: R09: 0228 [1.538947] R10: 0001 R11: R12: 978437e555a0 [1.538947] R13: R14: R15: [1.538947] FS: () GS:97843f6c() knlGS: [1.538947] CS: 0010 DS: ES: CR0: 80050033 [1.538947] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.538947] Call Trace: [1.538947] ? efi_rci2_sysfs_init+0x29a/0x29a [1.538947] do_one_initcall+0x4a/0x200 [1.538947] kernel_init_freeable+0x1c0/0x263 [1.538947] ? rest_init+0xb0/0xb0 [1.538947] kernel_init+0xe/0x110 [1.538947] ret_from_fork+0x22/0x40 [1.538947] Modules linked in: [1.545871] ---[ end trace 815dc8177e65da02 ]--- [1.546328] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.546872] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.548703] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.549218] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.549916] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.550617] RBP: b96e4001be10 R08: R09: 0228 [1.551337] R10: 0001 R11: R12: 978437e555a0 [1.552036] R13: R14: R15: [1.552737] FS: () GS:97843f6c() knlGS: [1.553529] CS: 0010 DS: ES: CR0: 80050033 [1.554093] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.554818] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [1.555335] Kernel Offset: 0x1fa0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.555335] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b ]--- - The previous kernel (linux-image-5.4.0-91-generic) boots correctly with SEV. Bisection of the kernels b/w 5.4.0-91 and 5.4.0-92 identified the following commit as the source of regresssion : # git bisect good 7ca05228f713c24eb55574b36e32d9b54c5a1b76 is the first bad commit commit 7ca05228f713c24eb55574b36e32d9b54c5a1b76 Author: Lenny Szubowicz Date: Fri Sep 4 21:31:05 2020 -0400 efi: Support for MOK variable config table BugLink: https://bugs.launchpad.net/bugs/1928679 ... Since the panic happens in very early stages of boot, no trace of the panic is present in the log files and apparently it is not possible to collect a kernel crash dump, the crashkernel has not been enabled yet. [Test case] The kernel need to boot properly with SEV enabled. [Potential regression] The fix is very specific and restricted and should cause regressions, however it touches ioremap that is widely used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- Mailing list: https://launchpad.net/~
[Kernel-packages] [Bug 1956849] Re: Almost all USB ports suddenly stopped working; unbootable
** Attachment added: "lsusb -v -v -v" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+attachment/5552994/+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/1956849 Title: Almost all USB ports suddenly stopped working; unbootable Status in linux package in Ubuntu: New Bug description: This package needs to be pulled NOW. It disables almost all USB-3.0 and USB-C ports completely. Even though I had automatic software updates turned OFF (or so I thought), my Mac Pro suddenly got a new kernel when I rebooted it this morning: Linux macpro-obs 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and it contains a P0 showstopper bug. Upon rebooting, I got dropped into the initrd prompt because Linux could not see the external USB drive that I'm booting from (WDBAGF5000AGY-WESN). I wasted an entire day figuring out what was wrong, and even went so far as to order a replacement SSD, planning to rebuild everything from scratch, because the drive failed to appear in every single USB port I tried. Then I discovered that a different SSD didn't work, either. At that point, I realized that something else was wrong, and I kept trying until I found one other port that worked. I was then able to boot and get dmesg and lsusb output. This kernel update broke not only the built-in ports, but also the ports on a generic USB-C PCIe card (Amazon B08PF8XR73). Mac Pro built-in USB-3.0(A) ports (2x): working Mac Pro built-in USB-C ports (4x): dead USB-C PCIe card USB-C ports (2x): dead USB-C PCIe card USB-3.0(A) ports (5x): dead All devices fail to appear in lsusb when attached to the port, including an Apple USB keyboard, an Anker USB-C Ethernet adapter, a WD SSD, and a Sandisk SSD. I'm going to roll back my kernel to a working kernel, but this package needs to be pulled NOW before it affects too many people. This is too catastrophic a bug to wait even a day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+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 1938998] Re: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly
Has this (now confirmed) problem been identified and fixed, and if so, which versions of the package(s) contain the fix? With this information, one could update to the version containing the fix and seeing if the system actually works as expected. I now generally turn off the updates for these packages when the update manager suggests them, as I don't want to interrupt my workflow by having to restore from backup if the fix isn't in there. -- 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/1938998 Title: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+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 1938998] Re: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly
The bug has not been confirmed by another human. That's just the status used by the kernel bot. Since all the relevant packages (mesa, xorg-server and kernel) have been updated since this bug was logged we would appreciate it if you could retest. If the problem still occurs then please consider: * Testing a newer kernel because you're currently on the old kernel series. You can change that with 'sudo apt install linux-generic- hwe-20.04'. * Reporting the problem to Cinnamon (https://github.com/linuxmint/cinnamon/issues) if it is specific to that environment. -- 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/1938998 Title: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+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 1956849] Re: Almost all USB ports suddenly stopped working; unbootable
Also attached lsusb output from a working kernel for comparison. And yes, it looks like this is a VIA-chipset-specific regression. I stand corrected about the Mac's built-in USB-C ports. Those don't work even after rolling back the kernel to the previous version. I'll file a separate bug for that. ** Attachment added: "lsusb -v from working kernel.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+attachment/5553000/+files/lsusb%20-v%20from%20working%20kernel.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/1956849 Title: Almost all USB ports suddenly stopped working; unbootable Status in linux package in Ubuntu: New Bug description: This package needs to be pulled NOW. It disables almost all USB-3.0 and USB-C ports completely. Even though I had automatic software updates turned OFF (or so I thought), my Mac Pro suddenly got a new kernel when I rebooted it this morning: Linux macpro-obs 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and it contains a P0 showstopper bug. Upon rebooting, I got dropped into the initrd prompt because Linux could not see the external USB drive that I'm booting from (WDBAGF5000AGY-WESN). I wasted an entire day figuring out what was wrong, and even went so far as to order a replacement SSD, planning to rebuild everything from scratch, because the drive failed to appear in every single USB port I tried. Then I discovered that a different SSD didn't work, either. At that point, I realized that something else was wrong, and I kept trying until I found one other port that worked. I was then able to boot and get dmesg and lsusb output. This kernel update broke not only the built-in ports, but also the ports on a generic USB-C PCIe card (Amazon B08PF8XR73). Mac Pro built-in USB-3.0(A) ports (2x): working Mac Pro built-in USB-C ports (4x): dead USB-C PCIe card USB-C ports (2x): dead USB-C PCIe card USB-3.0(A) ports (5x): dead All devices fail to appear in lsusb when attached to the port, including an Apple USB keyboard, an Anker USB-C Ethernet adapter, a WD SSD, and a Sandisk SSD. I'm going to roll back my kernel to a working kernel, but this package needs to be pulled NOW before it affects too many people. This is too catastrophic a bug to wait even a day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+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 1956926] [NEW] Jammy update: v5.15.13 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.15.13 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: 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/1956926 Title: Jammy update: v5.15.13 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Bug description: 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.15.13 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956926/+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 1956518] Re: linux-firmware 1.187.24 may crash USB ports
I have the same problem with Dell Latitude E7440, Ubuntu 20.04, after an update to kernel 5.4.0-92, and having linux-firmware 1.187.24. 1) I'm using a UGreen USB Switch to switch between the inputs of keyboard, mouse and audio between two stations 2) After the kernel and linux-firmware upgrade I did a reboot, the system took much longer to start (console shown "failed to enumerate USB devices"), when it did boot external keyboards and mouse wasn't working 3) Pluging in any device directly to laptop's USB port does not work 4) I've managed to get the external keyboard and mouse to work by disabling the Bluetooth in Ubuntu settings and rebooting back to 5.4.0-91 (worked via USB Switch) 5) However after another reboot to 5.4.0-91, USB ports stopped working again -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1956518/+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 1955932] Re: ps5 controller no longer working
Thanks for the investigation! I will try fiddling around with Steam and see if I can get it working. Good to know I should disregard the errors. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1955932 Title: ps5 controller no longer working Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Bug description: Hello! Up until today, my playstation 5 controller worked great with ubuntu + steam both over bluetooth and wired. Now, I can get the controller connected via bluetooth, and I can use `jstest /dev/input/js0` to read input from the controller in my terminal, but Steam no longer recognizes the controller. This bug only just started happening today. When I check in my journalctl logs when connecting the controller, I see the following, which indicates that perhaps something is going wrong... ``` Dez 28 23:43:13 zagreus kernel: hid-generic 0005:054C:0CE6.0023: unknown main item tag 0x0 Dez 28 23:43:13 zagreus kernel: input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:8/0005:054C:0CE6.0023/input/input65 Dez 28 23:43:13 zagreus kernel: hid-generic 0005:054C:0CE6.0023: input,hidraw8: BLUETOOTH HID v1.00 Gamepad [Wireless Controller] on 9c:b6:d0:ef:fd:7c Dez 28 23:43:13 zagreus systemd-udevd[14721]: js0: Process '/usr/bin/jscal-restore /dev/input/js0' failed with exit code 1. Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) config/udev: Adding input device Wireless Controller (/dev/input/js0) Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) No input driver specified, ignoring this device. Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) This device may have been added with another device file. Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) config/udev: Adding input device Wireless Controller (/dev/input/event30) Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) No input driver specified, ignoring this device. Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) This device may have been added with another device file. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 28 23:49:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:082a] InstallationDate: Installed on 2020-10-25 (429 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-43-generic root=/dev/mapper/vgubuntu-root ro ipv6.disable=1 quiet splash ipv6.disable=1 vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2019 dmi.bios.release: 2.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 0TPN17 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:br2.11:svnDellInc.:pnXPS139360:pvr:sku082A:rvnDellInc.:rn0TPN17:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 082A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1955932/+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
Re: [Kernel-packages] [Bug 1955932] Re: ps5 controller no longer working
Thanks for the investigation! I will try fiddling around with Steam and see if I can resolve the issue then :) On 10.01.22 06:51, Daniel van Vugt wrote: > I've just set up a brand new PS5 controller (via Bluetooth) on Ubuntu > 20.04 with kernel 5.11.0-44-generic and 'sudo evtest' seems to show it > is working. It reports events for almost all the buttons. > > Re-reading your bug report I think you have a problem specific to Steam. > > The errors you mention from Xorg (gdm-x-session[1946]: (II) ...) are > probably not relevant and should be ignored. > > > ** Changed in: linux-hwe-5.11 (Ubuntu) > Status: New => Invalid > > ** Changed in: xorg-server (Ubuntu) > Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1955932 > > Title: >ps5 controller no longer working > > Status in linux-hwe-5.11 package in Ubuntu: >Invalid > Status in xorg-server package in Ubuntu: >Invalid > > Bug description: >Hello! > >Up until today, my playstation 5 controller worked great with ubuntu + >steam both over bluetooth and wired. > >Now, I can get the controller connected via bluetooth, and I can use >`jstest /dev/input/js0` to read input from the controller in my >terminal, but Steam no longer recognizes the controller. This bug only >just started happening today. > >When I check in my journalctl logs when connecting the controller, I >see the following, which indicates that perhaps something is going >wrong... > >``` >Dez 28 23:43:13 zagreus kernel: hid-generic 0005:054C:0CE6.0023: unknown > main item tag 0x0 >Dez 28 23:43:13 zagreus kernel: input: Wireless Controller as > /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:8/0005:054C:0CE6.0023/input/input65 >Dez 28 23:43:13 zagreus kernel: hid-generic 0005:054C:0CE6.0023: > input,hidraw8: BLUETOOTH HID v1.00 Gamepad [Wireless Controller] on > 9c:b6:d0:ef:fd:7c >Dez 28 23:43:13 zagreus systemd-udevd[14721]: js0: Process > '/usr/bin/jscal-restore /dev/input/js0' failed with exit code 1. >Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) > config/udev: Adding input device Wireless Controller (/dev/input/js0) >Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) No input > driver specified, ignoring this device. >Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) This > device may have been added with another device file. >Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) > config/udev: Adding input device Wireless Controller (/dev/input/event30) >Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) No input > driver specified, ignoring this device. >Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) This > device may have been added with another device file. >``` > >ProblemType: Bug >DistroRelease: Ubuntu 20.04 >Package: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 >ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 >Uname: Linux 5.11.0-43-generic x86_64 >ApportVersion: 2.20.11-0ubuntu27.21 >Architecture: amd64 >BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' >CasperMD5CheckResult: skip >CompositorRunning: None >CurrentDesktop: ubuntu:GNOME >Date: Tue Dec 28 23:49:50 2021 >DistUpgraded: Fresh install >DistroCodename: focal >DistroVariant: ubuntu >ExecutablePath: /usr/lib/xorg/Xorg >ExtraDebuggingInterest: Yes >GraphicsCard: > Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA > controller]) > Subsystem: Dell UHD Graphics 620 [1028:082a] >InstallationDate: Installed on 2020-10-25 (429 days ago) >InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) >MachineType: Dell Inc. XPS 13 9360 >ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-43-generic > root=/dev/mapper/vgubuntu-root ro ipv6.disable=1 quiet splash ipv6.disable=1 > vt.handoff=7 >SourcePackage: xorg-server >UpgradeStatus: No upgrade log present (probably fresh install) >dmi.bios.date: 03/14/2019 >dmi.bios.release: 2.11 >dmi.bios.vendor: Dell Inc. >dmi.bios.version: 2.11.0 >dmi.board.name: 0TPN17 >dmi.board.vendor: Dell Inc. >dmi.board.version: A00 >dmi.chassis.type: 9 >dmi.chassis.vendor: Dell Inc. >dmi.modalias: > dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:br2.11:svnDellInc.:pnXPS139360:pvr:sku082A:rvnDellInc.:rn0TPN17:rvrA00:cvnDellInc.:ct9:cvr: >dmi.product.family: XPS >dmi.product.name: XPS 13 9360 >dmi.product.sku: 082A >dmi.sys.vendor: Dell Inc. >version.compiz: compiz N/A >version.libdrm2: libdrm2 2.4.105-3~20.04.2 >version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 >version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 >
[Kernel-packages] [Bug 1952193] Re: NULL pointer dereference at _mod_memcg_state+0x14/0xb0
** Description changed: Hello. We meet a randomly host kernel panics with same RIP and "BUG: kernel NULL pointer dereference". - At current time affected kernel versions was from 5.4.0-53 to 5.4.0-84. + At current time affected kernel versions was from 5.4.0-53 to 5.4.0-87. For now i have a dmesg log and crash file, but no clue where what to do next. Environment: - Distributor ID: Ubuntu - Description:Ubuntu 18.04.6 LTS - Release:18.04 - Codename: bionic - + Distributor ID: Ubuntu + Description:Ubuntu 18.04.6 LTS + Release:18.04 + Codename: bionic Crash report - KERNEL: usr/lib/debug/boot/vmlinux-5.4.0-84-generic - DUMPFILE: dump.202111240900 [PARTIAL DUMP] - CPUS: 24 - DATE: Wed Nov 24 09:00:22 2021 - UPTIME: 15 days, 23:17:07 + KERNEL: usr/lib/debug/boot/vmlinux-5.4.0-84-generic + DUMPFILE: dump.202111240900 [PARTIAL DUMP] + CPUS: 24 + DATE: Wed Nov 24 09:00:22 2021 + UPTIME: 15 days, 23:17:07 LOAD AVERAGE: 46.41, 37.67, 30.39 -TASKS: 3071 - NODENAME: cmp20 - RELEASE: 5.4.0-84-generic - VERSION: #94~18.04.1-Ubuntu SMP Thu Aug 26 23:17:46 UTC 2021 - MACHINE: x86_64 (2299 Mhz) - MEMORY: 255.9 GB -PANIC: "Oops: [#1] SMP PTI" (check log for details) - PID: 2239917 - COMMAND: "CPU 0/KVM" - TASK: 9bbd9662 [THREAD_INFO: 9bbd9662] - CPU: 14 -STATE: TASK_RUNNING (PANIC) + TASKS: 3071 + NODENAME: cmp20 + RELEASE: 5.4.0-84-generic + VERSION: #94~18.04.1-Ubuntu SMP Thu Aug 26 23:17:46 UTC 2021 + MACHINE: x86_64 (2299 Mhz) + MEMORY: 255.9 GB + PANIC: "Oops: [#1] SMP PTI" (check log for details) + PID: 2239917 + COMMAND: "CPU 0/KVM" + TASK: 9bbd9662 [THREAD_INFO: 9bbd9662] + CPU: 14 + STATE: TASK_RUNNING (PANIC) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1952193 Title: NULL pointer dereference at _mod_memcg_state+0x14/0xb0 Status in linux-meta-hwe-5.4 package in Ubuntu: New Bug description: Hello. We meet a randomly host kernel panics with same RIP and "BUG: kernel NULL pointer dereference". At current time affected kernel versions was from 5.4.0-53 to 5.4.0-87. For now i have a dmesg log and crash file, but no clue where what to do next. Environment: Distributor ID: Ubuntu Description:Ubuntu 18.04.6 LTS Release:18.04 Codename: bionic Crash report KERNEL: usr/lib/debug/boot/vmlinux-5.4.0-84-generic DUMPFILE: dump.202111240900 [PARTIAL DUMP] CPUS: 24 DATE: Wed Nov 24 09:00:22 2021 UPTIME: 15 days, 23:17:07 LOAD AVERAGE: 46.41, 37.67, 30.39 TASKS: 3071 NODENAME: cmp20 RELEASE: 5.4.0-84-generic VERSION: #94~18.04.1-Ubuntu SMP Thu Aug 26 23:17:46 UTC 2021 MACHINE: x86_64 (2299 Mhz) MEMORY: 255.9 GB PANIC: "Oops: [#1] SMP PTI" (check log for details) PID: 2239917 COMMAND: "CPU 0/KVM" TASK: 9bbd9662 [THREAD_INFO: 9bbd9662] CPU: 14 STATE: TASK_RUNNING (PANIC) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1952193/+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 1926481] Re: lockf returns false-positive EDEADLK in multiprocess multithreaded environment
Posted to more specific mailing list: linux-fsdevel.vger.kernel.org https://lore.kernel.org/linux-fsdevel/cal-cveifotfbyrfocb0yeyor+sctpwo_2__49tapronhr+t...@mail.gmail.com/T/#u -- 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/1926481 Title: lockf returns false-positive EDEADLK in multiprocess multithreaded environment Status in linux package in Ubuntu: Confirmed Bug description: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # uname -a Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 ноя 12 09:53 seq crw-rw 1 root audio 116, 33 ноя 12 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-22 (280 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0a89:0030 Aktiv Rutoken ECP Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M |__ Port 1: Dev 4, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1d0fe562-8128-4922-836e-b0a384fc5054 ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linu
Re: [Kernel-packages] [Bug 1955903] Re: Dell XPS 13 9370 never wakes from sleep
Actually, I can't find any references to "mem_sleep_default=deep" in /etc/default/grub, although I do see that /boot/grub/grub.cfg contains some (see attached). On Mon, Jan 10, 2022 at 3:10 AM Daniel van Vugt <1955...@bugs.launchpad.net> wrote: > You still have one instance of "mem_sleep_default=deep" in your kernel > command line. Please remove it then run 'sudo update-grub' and reboot. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1955903 > > Title: > Dell XPS 13 9370 never wakes from sleep > > Status in linux package in Ubuntu: > New > > Bug description: > Every so often, whether I close the lid of the laptop or not, the > screen will go blank and neither pressing a key nor moving the mouse > will show anything. The only thing I can do to recover is hold the > power button down for 10 seconds to restart. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 > Uname: Linux 5.4.0-91-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.11-0ubuntu27.21 > Architecture: amd64 > CasperMD5CheckResult: skip > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Tue Dec 28 08:25:44 2021 > DistUpgraded: 2020-05-08 07:44:41,528 ERROR got error from > PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to > execute child process “./xorg_fix_proprietary.py” (No such file or > directory) (8)) > DistributionChannelDescriptor: ># This is a distribution channel descriptor ># For more information see > http://wiki.ubuntu.com/DistributionChannelDescriptor >canonical-oem-somerville-xenial-amd64-20160624-2 > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GpuHangFrequency: Once a week > GpuHangReproducibility: Seems to happen randomly > GpuHangStarted: Immediately after installing this version of Ubuntu > GraphicsCard: >Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 > [VGA controller]) > Subsystem: Dell UHD Graphics 620 [1028:07e6] > InstallationDate: Installed on 2018-03-12 (1387 days ago) > InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary > 20160624-10:47 > MachineType: Dell Inc. XPS 13 9370 > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic > root=UUID=d9d0f137-4a05-4e95-aac6-c6835b632839 ro locale=en_US > alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 > mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep quiet splash > vt.handoff=7 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: Upgraded to focal on 2020-05-08 (599 days ago) > dmi.bios.date: 10/07/2021 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.17.0 > dmi.board.name: 0F6P3V > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.17.0:bd10/07/2021:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: XPS > dmi.product.name: XPS 13 9370 > dmi.product.sku: 07E6 > dmi.sys.vendor: Dell Inc. > version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 > version.libdrm2: libdrm2 2.4.105-3~20.04.2 > version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 > version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955903/+subscriptions > > ** Attachment added: "grub" https://bugs.launchpad.net/bugs/1955903/+attachment/5553037/+files/grub ** Attachment added: "grub.cfg" https://bugs.launchpad.net/bugs/1955903/+attachment/5553038/+files/grub.cfg -- 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/1955903 Title: Dell XPS 13 9370 never wakes from sleep Status in linux package in Ubuntu: New Bug description: Every so often, whether I close the lid of the laptop or not, the screen will go blank and neither pressing a key nor moving the mouse will show anything. The only thing I can do to recover is hold the power button down for 10 seconds to res
[Kernel-packages] [Bug 1956426] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.25 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1956426 Title: MIssing firmware for Intel Visual Sensing Controller Status in OEM Priority Project: Fix Committed Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] Need firmware blob for Intel Visual Sensing Controller for IPU6 cameras on Intel Alder Lake platforms. [Fix] Two commits from upstream repo https://github.com/intel/ivsc-firmware main branch. While Intel has no plan to upstream their IPU6 driver before kernel camera API is out, the firmware blobs will probably stay where they are until the plan changed. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] This is a follow-up for bug 1955383, which at the time being SRU-ed, Intel has not yet published these ivsc fw for redistribution. Focal is nomiated to support oem-5.14 kernel. == original bug report == This is a followup for bug 1955383 that ivsc firmware was not publicly released at the time submitting other Intel IPU6 works for Alder Lake platform. They're now available in https://github.com/intel/ivsc- firmware To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1956426/+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 1955689] Please test proposed package
Hello Kai-Heng, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.25 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1955689 Title: Add Bluetooth support for Qualcomm WCN6856 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] WCN6856 Bluetooth doesn't work. [Fix] Backport firmware blobs and driver support to make it work by loading correct firmwares. [Test] Bluetooth scanning and pairing work, and continue to do so after several suspend/resume cycles. [Where problems could occur] The upstream version of btusb_generate_qca_nvm_name() adds several missing le*_to_cpu() macros, so if this device was ever used on a Big Endian system, this is a behavioral change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955689/+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 1955613] Please test proposed package
Hello Kai-Heng, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.25 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1955613 Title: Add basic Wifi support for Qualcomm WCN6856 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Qualcomm WCN6856 doens't work. [Fix] Backport missing bits to make Wifi 5 work. Wifi 6 support is not in the scope of this SRU. [Test] The system can connect to Wifi. Wifi still works after several rounds of suspend/resume cycles. [Where problems could occur] The change is limited to ath11k, which is also the only user of mhi bus, so the scope of risk is limited. Let alone it never worked before, so there's not much room to go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955613/+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 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.25 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: Incomplete Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: lin
[Kernel-packages] [Bug 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
another one to test is v5.15.8 -- 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/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1956426] Re: MIssing firmware for Intel Visual Sensing Controller
This bug was fixed in the package linux-firmware - 1.204 --- linux-firmware (1.204) jammy; urgency=medium * Support Intel IPU6 MIPI camera on Alder Lake platforms (LP: #1955383) - SAUCE: intel-ipu6: Add IPU6 firmware files - SAUCE: intel-ipu6: update IPU6 Release_20210121 WW04 firmware files - SAUCE: Camera bins release on 2021-11-01 for Alder Lake * [Packaging] Downgrade firmware-sof-signed depends to recommends * QCA: Add Bluetooth default nvm file for WCN685x (LP: #1955689) * Missing firmware for Intel Visual Sensing Controller (LP: #1956426) - SAUCE: first release of ivsc firmware binaries - SAUCE: firmware: add support of more sensors * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - SAUCE: WCN6855 hw2.0: update board-2.bin - SAUCE: WCN6855 hw2.0: 1.1: add WLAN.HSP.1.1-03003-QCAHSPSWPL_V1_V2_SILICONZ_LITE-2 linux-firmware (1.203) jammy; urgency=medium * SAUCE: check_whence.py: Add python3 shebang * SAUCE: check_whence.py: Also process WHENCE.ubuntu * SAUCE: check_whence.py: Ignore debian/ and fw_source/ directories * SAUCE: check_whence.py: Ignore ea/ directory * [Packaging] Add check debian rule * [Packaging] rebase-upstream: Add usage * [Packaging] rebase-upstream: Fix shellcheck warnings * Rebase to upstream commit b0e898fbaf377c99a36aac6fdeb7250003648ca4 (LP: #1953008) Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9462 - linux-firmware: Update firmware file for Intel Bluetooth 9462 - rtw89: 8852a: update fw to v0.13.30.0 - linux-firmware: update firmware for MT7921 WiFi device - QCA: Update Bluetooth firmware for WCN685x - linux-firmware: Update NXP Management Complex firmware to version 10.28.1 - Mellanox: Add new mlxsw_spectrum firmware xx.2010.1006 - bnx2x: Add FW 7.13.20.0 - QCA: Update Bluetooth firmware for WCN685x - linux-firmware: Update AMD cpu microcode - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - amdgpu: update VCN firmware for green sardine - iwlwifi: update 9000-family firmwares to core64-96 - iwlwifi: add new FWs from core64-96 release - rtl_bt: Update RTL8852A BT USB firmware to 0xDBA9_6937 - amdgpu: update sienna cichlid firmware from 21.40 - amdgpu: update arcturus firmware from 21.40 - amdgpu: update renoir firmware from 21.40 - amdgpu: update navy flounder firmware from 21.40 - amdgpu: update green sardine firmware from 21.40 - amdgpu: update dimgrey cavefish firmware from 21.40 - amdgpu: add cyan skillfish firmware from 21.40 - amdgpu: update beige goby firmware from 21.40 - amdgpu: update vangogh firmware from 21.40 - amdgpu: update picasso firmware from 21.40 - amdgpu: update vega10 firmware from 21.40 - amdgpu: update vega12 firmware from 21.40 - amdgpu: update vega20 firmware from 21.40 - amdgpu: update navi10 firmware from 21.40 - amdgpu: update navi12 firmware from 21.40 - amdgpu: update raven firmware from 21.40 - amdgpu: update navi14 firmware from 21.40 - amdgpu: update raven2 firmware from 21.40 - linux-firmware: Update AMD cpu microcode - QCA: Add Bluetooth firmware for WCN685x - mrvl: prestera: Update Marvell Prestera Switchdev v4.0 - Update ath10k/QCA6174/hw3.0/board-2.bin - amdgpu: update vangogh DMCUB firmware - amdgpu: update yellow carp dmcub firmware - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Updat
[Kernel-packages] [Bug 1955689] Re: Add Bluetooth support for Qualcomm WCN6856
This bug was fixed in the package linux-firmware - 1.204 --- linux-firmware (1.204) jammy; urgency=medium * Support Intel IPU6 MIPI camera on Alder Lake platforms (LP: #1955383) - SAUCE: intel-ipu6: Add IPU6 firmware files - SAUCE: intel-ipu6: update IPU6 Release_20210121 WW04 firmware files - SAUCE: Camera bins release on 2021-11-01 for Alder Lake * [Packaging] Downgrade firmware-sof-signed depends to recommends * QCA: Add Bluetooth default nvm file for WCN685x (LP: #1955689) * Missing firmware for Intel Visual Sensing Controller (LP: #1956426) - SAUCE: first release of ivsc firmware binaries - SAUCE: firmware: add support of more sensors * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - SAUCE: WCN6855 hw2.0: update board-2.bin - SAUCE: WCN6855 hw2.0: 1.1: add WLAN.HSP.1.1-03003-QCAHSPSWPL_V1_V2_SILICONZ_LITE-2 linux-firmware (1.203) jammy; urgency=medium * SAUCE: check_whence.py: Add python3 shebang * SAUCE: check_whence.py: Also process WHENCE.ubuntu * SAUCE: check_whence.py: Ignore debian/ and fw_source/ directories * SAUCE: check_whence.py: Ignore ea/ directory * [Packaging] Add check debian rule * [Packaging] rebase-upstream: Add usage * [Packaging] rebase-upstream: Fix shellcheck warnings * Rebase to upstream commit b0e898fbaf377c99a36aac6fdeb7250003648ca4 (LP: #1953008) Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9462 - linux-firmware: Update firmware file for Intel Bluetooth 9462 - rtw89: 8852a: update fw to v0.13.30.0 - linux-firmware: update firmware for MT7921 WiFi device - QCA: Update Bluetooth firmware for WCN685x - linux-firmware: Update NXP Management Complex firmware to version 10.28.1 - Mellanox: Add new mlxsw_spectrum firmware xx.2010.1006 - bnx2x: Add FW 7.13.20.0 - QCA: Update Bluetooth firmware for WCN685x - linux-firmware: Update AMD cpu microcode - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - amdgpu: update VCN firmware for green sardine - iwlwifi: update 9000-family firmwares to core64-96 - iwlwifi: add new FWs from core64-96 release - rtl_bt: Update RTL8852A BT USB firmware to 0xDBA9_6937 - amdgpu: update sienna cichlid firmware from 21.40 - amdgpu: update arcturus firmware from 21.40 - amdgpu: update renoir firmware from 21.40 - amdgpu: update navy flounder firmware from 21.40 - amdgpu: update green sardine firmware from 21.40 - amdgpu: update dimgrey cavefish firmware from 21.40 - amdgpu: add cyan skillfish firmware from 21.40 - amdgpu: update beige goby firmware from 21.40 - amdgpu: update vangogh firmware from 21.40 - amdgpu: update picasso firmware from 21.40 - amdgpu: update vega10 firmware from 21.40 - amdgpu: update vega12 firmware from 21.40 - amdgpu: update vega20 firmware from 21.40 - amdgpu: update navi10 firmware from 21.40 - amdgpu: update navi12 firmware from 21.40 - amdgpu: update raven firmware from 21.40 - amdgpu: update navi14 firmware from 21.40 - amdgpu: update raven2 firmware from 21.40 - linux-firmware: Update AMD cpu microcode - QCA: Add Bluetooth firmware for WCN685x - mrvl: prestera: Update Marvell Prestera Switchdev v4.0 - Update ath10k/QCA6174/hw3.0/board-2.bin - amdgpu: update vangogh DMCUB firmware - amdgpu: update yellow carp dmcub firmware - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Updat
[Kernel-packages] [Bug 1955613] Re: Add basic Wifi support for Qualcomm WCN6856
This bug was fixed in the package linux-firmware - 1.204 --- linux-firmware (1.204) jammy; urgency=medium * Support Intel IPU6 MIPI camera on Alder Lake platforms (LP: #1955383) - SAUCE: intel-ipu6: Add IPU6 firmware files - SAUCE: intel-ipu6: update IPU6 Release_20210121 WW04 firmware files - SAUCE: Camera bins release on 2021-11-01 for Alder Lake * [Packaging] Downgrade firmware-sof-signed depends to recommends * QCA: Add Bluetooth default nvm file for WCN685x (LP: #1955689) * Missing firmware for Intel Visual Sensing Controller (LP: #1956426) - SAUCE: first release of ivsc firmware binaries - SAUCE: firmware: add support of more sensors * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - SAUCE: WCN6855 hw2.0: update board-2.bin - SAUCE: WCN6855 hw2.0: 1.1: add WLAN.HSP.1.1-03003-QCAHSPSWPL_V1_V2_SILICONZ_LITE-2 linux-firmware (1.203) jammy; urgency=medium * SAUCE: check_whence.py: Add python3 shebang * SAUCE: check_whence.py: Also process WHENCE.ubuntu * SAUCE: check_whence.py: Ignore debian/ and fw_source/ directories * SAUCE: check_whence.py: Ignore ea/ directory * [Packaging] Add check debian rule * [Packaging] rebase-upstream: Add usage * [Packaging] rebase-upstream: Fix shellcheck warnings * Rebase to upstream commit b0e898fbaf377c99a36aac6fdeb7250003648ca4 (LP: #1953008) Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9462 - linux-firmware: Update firmware file for Intel Bluetooth 9462 - rtw89: 8852a: update fw to v0.13.30.0 - linux-firmware: update firmware for MT7921 WiFi device - QCA: Update Bluetooth firmware for WCN685x - linux-firmware: Update NXP Management Complex firmware to version 10.28.1 - Mellanox: Add new mlxsw_spectrum firmware xx.2010.1006 - bnx2x: Add FW 7.13.20.0 - QCA: Update Bluetooth firmware for WCN685x - linux-firmware: Update AMD cpu microcode - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - amdgpu: update VCN firmware for green sardine - iwlwifi: update 9000-family firmwares to core64-96 - iwlwifi: add new FWs from core64-96 release - rtl_bt: Update RTL8852A BT USB firmware to 0xDBA9_6937 - amdgpu: update sienna cichlid firmware from 21.40 - amdgpu: update arcturus firmware from 21.40 - amdgpu: update renoir firmware from 21.40 - amdgpu: update navy flounder firmware from 21.40 - amdgpu: update green sardine firmware from 21.40 - amdgpu: update dimgrey cavefish firmware from 21.40 - amdgpu: add cyan skillfish firmware from 21.40 - amdgpu: update beige goby firmware from 21.40 - amdgpu: update vangogh firmware from 21.40 - amdgpu: update picasso firmware from 21.40 - amdgpu: update vega10 firmware from 21.40 - amdgpu: update vega12 firmware from 21.40 - amdgpu: update vega20 firmware from 21.40 - amdgpu: update navi10 firmware from 21.40 - amdgpu: update navi12 firmware from 21.40 - amdgpu: update raven firmware from 21.40 - amdgpu: update navi14 firmware from 21.40 - amdgpu: update raven2 firmware from 21.40 - linux-firmware: Update AMD cpu microcode - QCA: Add Bluetooth firmware for WCN685x - mrvl: prestera: Update Marvell Prestera Switchdev v4.0 - Update ath10k/QCA6174/hw3.0/board-2.bin - amdgpu: update vangogh DMCUB firmware - amdgpu: update yellow carp dmcub firmware - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Updat
[Kernel-packages] [Bug 1953008] Re: Support USB4 DP alt mode for AMD Yellow Carp graphics card
This bug was fixed in the package linux-firmware - 1.204 --- linux-firmware (1.204) jammy; urgency=medium * Support Intel IPU6 MIPI camera on Alder Lake platforms (LP: #1955383) - SAUCE: intel-ipu6: Add IPU6 firmware files - SAUCE: intel-ipu6: update IPU6 Release_20210121 WW04 firmware files - SAUCE: Camera bins release on 2021-11-01 for Alder Lake * [Packaging] Downgrade firmware-sof-signed depends to recommends * QCA: Add Bluetooth default nvm file for WCN685x (LP: #1955689) * Missing firmware for Intel Visual Sensing Controller (LP: #1956426) - SAUCE: first release of ivsc firmware binaries - SAUCE: firmware: add support of more sensors * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - SAUCE: WCN6855 hw2.0: update board-2.bin - SAUCE: WCN6855 hw2.0: 1.1: add WLAN.HSP.1.1-03003-QCAHSPSWPL_V1_V2_SILICONZ_LITE-2 linux-firmware (1.203) jammy; urgency=medium * SAUCE: check_whence.py: Add python3 shebang * SAUCE: check_whence.py: Also process WHENCE.ubuntu * SAUCE: check_whence.py: Ignore debian/ and fw_source/ directories * SAUCE: check_whence.py: Ignore ea/ directory * [Packaging] Add check debian rule * [Packaging] rebase-upstream: Add usage * [Packaging] rebase-upstream: Fix shellcheck warnings * Rebase to upstream commit b0e898fbaf377c99a36aac6fdeb7250003648ca4 (LP: #1953008) Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9462 - linux-firmware: Update firmware file for Intel Bluetooth 9462 - rtw89: 8852a: update fw to v0.13.30.0 - linux-firmware: update firmware for MT7921 WiFi device - QCA: Update Bluetooth firmware for WCN685x - linux-firmware: Update NXP Management Complex firmware to version 10.28.1 - Mellanox: Add new mlxsw_spectrum firmware xx.2010.1006 - bnx2x: Add FW 7.13.20.0 - QCA: Update Bluetooth firmware for WCN685x - linux-firmware: Update AMD cpu microcode - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - amdgpu: update VCN firmware for green sardine - iwlwifi: update 9000-family firmwares to core64-96 - iwlwifi: add new FWs from core64-96 release - rtl_bt: Update RTL8852A BT USB firmware to 0xDBA9_6937 - amdgpu: update sienna cichlid firmware from 21.40 - amdgpu: update arcturus firmware from 21.40 - amdgpu: update renoir firmware from 21.40 - amdgpu: update navy flounder firmware from 21.40 - amdgpu: update green sardine firmware from 21.40 - amdgpu: update dimgrey cavefish firmware from 21.40 - amdgpu: add cyan skillfish firmware from 21.40 - amdgpu: update beige goby firmware from 21.40 - amdgpu: update vangogh firmware from 21.40 - amdgpu: update picasso firmware from 21.40 - amdgpu: update vega10 firmware from 21.40 - amdgpu: update vega12 firmware from 21.40 - amdgpu: update vega20 firmware from 21.40 - amdgpu: update navi10 firmware from 21.40 - amdgpu: update navi12 firmware from 21.40 - amdgpu: update raven firmware from 21.40 - amdgpu: update navi14 firmware from 21.40 - amdgpu: update raven2 firmware from 21.40 - linux-firmware: Update AMD cpu microcode - QCA: Add Bluetooth firmware for WCN685x - mrvl: prestera: Update Marvell Prestera Switchdev v4.0 - Update ath10k/QCA6174/hw3.0/board-2.bin - amdgpu: update vangogh DMCUB firmware - amdgpu: update yellow carp dmcub firmware - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Updat
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
This bug was fixed in the package linux-firmware - 1.204 --- linux-firmware (1.204) jammy; urgency=medium * Support Intel IPU6 MIPI camera on Alder Lake platforms (LP: #1955383) - SAUCE: intel-ipu6: Add IPU6 firmware files - SAUCE: intel-ipu6: update IPU6 Release_20210121 WW04 firmware files - SAUCE: Camera bins release on 2021-11-01 for Alder Lake * [Packaging] Downgrade firmware-sof-signed depends to recommends * QCA: Add Bluetooth default nvm file for WCN685x (LP: #1955689) * Missing firmware for Intel Visual Sensing Controller (LP: #1956426) - SAUCE: first release of ivsc firmware binaries - SAUCE: firmware: add support of more sensors * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - SAUCE: WCN6855 hw2.0: update board-2.bin - SAUCE: WCN6855 hw2.0: 1.1: add WLAN.HSP.1.1-03003-QCAHSPSWPL_V1_V2_SILICONZ_LITE-2 linux-firmware (1.203) jammy; urgency=medium * SAUCE: check_whence.py: Add python3 shebang * SAUCE: check_whence.py: Also process WHENCE.ubuntu * SAUCE: check_whence.py: Ignore debian/ and fw_source/ directories * SAUCE: check_whence.py: Ignore ea/ directory * [Packaging] Add check debian rule * [Packaging] rebase-upstream: Add usage * [Packaging] rebase-upstream: Fix shellcheck warnings * Rebase to upstream commit b0e898fbaf377c99a36aac6fdeb7250003648ca4 (LP: #1953008) Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9462 - linux-firmware: Update firmware file for Intel Bluetooth 9462 - rtw89: 8852a: update fw to v0.13.30.0 - linux-firmware: update firmware for MT7921 WiFi device - QCA: Update Bluetooth firmware for WCN685x - linux-firmware: Update NXP Management Complex firmware to version 10.28.1 - Mellanox: Add new mlxsw_spectrum firmware xx.2010.1006 - bnx2x: Add FW 7.13.20.0 - QCA: Update Bluetooth firmware for WCN685x - linux-firmware: Update AMD cpu microcode - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - amdgpu: update VCN firmware for green sardine - iwlwifi: update 9000-family firmwares to core64-96 - iwlwifi: add new FWs from core64-96 release - rtl_bt: Update RTL8852A BT USB firmware to 0xDBA9_6937 - amdgpu: update sienna cichlid firmware from 21.40 - amdgpu: update arcturus firmware from 21.40 - amdgpu: update renoir firmware from 21.40 - amdgpu: update navy flounder firmware from 21.40 - amdgpu: update green sardine firmware from 21.40 - amdgpu: update dimgrey cavefish firmware from 21.40 - amdgpu: add cyan skillfish firmware from 21.40 - amdgpu: update beige goby firmware from 21.40 - amdgpu: update vangogh firmware from 21.40 - amdgpu: update picasso firmware from 21.40 - amdgpu: update vega10 firmware from 21.40 - amdgpu: update vega12 firmware from 21.40 - amdgpu: update vega20 firmware from 21.40 - amdgpu: update navi10 firmware from 21.40 - amdgpu: update navi12 firmware from 21.40 - amdgpu: update raven firmware from 21.40 - amdgpu: update navi14 firmware from 21.40 - amdgpu: update raven2 firmware from 21.40 - linux-firmware: Update AMD cpu microcode - QCA: Add Bluetooth firmware for WCN685x - mrvl: prestera: Update Marvell Prestera Switchdev v4.0 - Update ath10k/QCA6174/hw3.0/board-2.bin - amdgpu: update vangogh DMCUB firmware - amdgpu: update yellow carp dmcub firmware - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Updat
[Kernel-packages] [Bug 1956964] [NEW] iwlwifi connection drops using AX200
Public bug reported: I get occasional (sometimes once per hour, sometimes more often) connection drops on my Thinkpad T14s Gen 1 (which uses an Intel AX 200 chipset). dmesg reports a microcode SW error and seems to restart the adapter. I recently moved, so I'm not sure if it's caused by the environment or an update. I'm using a Fritzbox 7530 AX router and got an older model (7490) and another Thinkpad (T450s) with an intel chipset available for testing if necessary. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-23-generic 5.13.0-23.23 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jonas 2455 F pulseaudio /dev/snd/controlC1: jonas 2455 F pulseaudio /dev/snd/controlC3: jonas 2455 F pulseaudio /dev/snd/controlC0: jonas 2455 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: i3 Date: Mon Jan 10 13:50:22 2022 InstallationDate: Installed on 2021-01-22 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20UH001QGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-29 (41 days ago) dmi.bios.date: 11/30/2020 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET60W(1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UH001QGE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrR1CET60W(1.29):bd11/30/2020:br1.29:efr1.29:svnLENOVO:pn20UH001QGE:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QGE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UH_BU_Think_FM_ThinkPadT14sGen1: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UH001QGE dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1956964 Title: iwlwifi connection drops using AX200 Status in linux package in Ubuntu: New Bug description: I get occasional (sometimes once per hour, sometimes more often) connection drops on my Thinkpad T14s Gen 1 (which uses an Intel AX 200 chipset). dmesg reports a microcode SW error and seems to restart the adapter. I recently moved, so I'm not sure if it's caused by the environment or an update. I'm using a Fritzbox 7530 AX router and got an older model (7490) and another Thinkpad (T450s) with an intel chipset available for testing if necessary. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-23-generic 5.13.0-23.23 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jonas 2455 F pulseaudio /dev/snd/controlC1: jonas 2455 F pulseaudio /dev/snd/controlC3: jonas 2455 F pulseaudio /dev/snd/controlC0: jonas 2455 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: i3 Date: Mon Jan 10 13:50:22 2022 InstallationDate: Installed on 2021-01-22 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20UH001QGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-29 (41 days ago) dmi.bios.date: 11/30/2020 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET60W(1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UH001QGE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrR1CET60W(1.29):bd11/30/2020:br1.29:efr1.29:svnLENOVO:pn20UH001QGE:pvrThinkPadT14s
[Kernel-packages] [Bug 1954926] Re: Focal: CIFS stable updates
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1954926 Title: Focal: CIFS stable updates Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: Fix Committed Bug description: SRU Justification [Impact] Backport several stable updates to v5.4 Azure [Test Case] Microsoft tested [Where things could go wrong] Samba connections could fail [Other Info] SF: #00324495 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954926/+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 1938998] Re: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly
Ah, OK. I'll re-test and report back. -- 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/1938998 Title: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+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 1955513] Re: NUC11PAHi7-Tiger Lake
Some more info to add for the HDMI audio issue: I tried out the hardware on another monitor and it appears that stereo PCM audio over HDMI works fine. What appears to be broken is surround sound and bitstream audio over HDMI. This only occurs in Linux/Ubuntu 22.04. In windows 10 everything works as expected. With respect to wifi: Issues persist, no further info to add. -- 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/1955513 Title: NUC11PAHi7-Tiger Lake Status in linux package in Ubuntu: Confirmed Bug description: in Ubuntu Jammy Jellyfish 22.04, with kernel 5.13.0-22-generic running on the NUC11PAHi7 hardware platform, the audio is broken. No audio is output over HDMI or headphone jack despite the sound hardware being detected. The issue is with the OS/Kernel since I booted the hardware with Windows 10 and it worked. Another issue is that the machine constantly drops the WiFi connection, again this is behavior not observed when I booted into Win 10. BIOS is the stock default version PATGL357.0041 and there is no other current update available. Please fix. Thank You. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-16 (6 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Intel(R) Client Systems NUC11PAHi7 Package: linux (not installed) 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.13.0-22-generic root=UUID=38af8d01--4dbd-a306-eb38ded7a2e3 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.202 Tags: wayland-session jammy Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-18 (4 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev pulse pulse-access sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/11/2021 dmi.bios.release: 0.41 dmi.bios.vendor: Intel Corp. dmi.bios.version: PATGL357.0041.2021.0811.1505 dmi.board.name: NUC11PABi7 dmi.board.vendor: Intel Corporation dmi.board.version: K90104-305 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.3 dmi.modalias: dmi:bvnIntelCorp.:bvrPATGL357.0041.2021.0811.1505:bd08/11/2021:br0.41:efr3.3:svnIntel(R)ClientSystems:pnNUC11PAHi7:pvrM15513-306:rvnIntelCorporation:rnNUC11PABi7:rvrK90104-305:cvnIntelCorporation:ct35:cvr2.0:skuRNUC11PAHi7000: dmi.product.family: PA dmi.product.name: NUC11PAHi7 dmi.product.sku: RNUC11PAHi7000 dmi.product.version: M15513-306 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955513/+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 1955513] Re: NUC11PAHi7-Tiger Lake
For the audio issue, I did notice that when set to bitstream over HDMI and surround, it would randomly work (not very often) before logon to the desktop but audio would quit after. This was a very low occurrence however of this mode working. -- 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/1955513 Title: NUC11PAHi7-Tiger Lake Status in linux package in Ubuntu: Confirmed Bug description: in Ubuntu Jammy Jellyfish 22.04, with kernel 5.13.0-22-generic running on the NUC11PAHi7 hardware platform, the audio is broken. No audio is output over HDMI or headphone jack despite the sound hardware being detected. The issue is with the OS/Kernel since I booted the hardware with Windows 10 and it worked. Another issue is that the machine constantly drops the WiFi connection, again this is behavior not observed when I booted into Win 10. BIOS is the stock default version PATGL357.0041 and there is no other current update available. Please fix. Thank You. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-16 (6 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Intel(R) Client Systems NUC11PAHi7 Package: linux (not installed) 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.13.0-22-generic root=UUID=38af8d01--4dbd-a306-eb38ded7a2e3 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.202 Tags: wayland-session jammy Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2021-12-18 (4 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev pulse pulse-access sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/11/2021 dmi.bios.release: 0.41 dmi.bios.vendor: Intel Corp. dmi.bios.version: PATGL357.0041.2021.0811.1505 dmi.board.name: NUC11PABi7 dmi.board.vendor: Intel Corporation dmi.board.version: K90104-305 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.3 dmi.modalias: dmi:bvnIntelCorp.:bvrPATGL357.0041.2021.0811.1505:bd08/11/2021:br0.41:efr3.3:svnIntel(R)ClientSystems:pnNUC11PAHi7:pvrM15513-306:rvnIntelCorporation:rnNUC11PABi7:rvrK90104-305:cvnIntelCorporation:ct35:cvr2.0:skuRNUC11PAHi7000: dmi.product.family: PA dmi.product.name: NUC11PAHi7 dmi.product.sku: RNUC11PAHi7000 dmi.product.version: M15513-306 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955513/+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 1956793] Re: linux-azure-cvm: Avoid leaking guest memory when communicating with the host
** Changed in: linux-azure-cvm (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-cvm in Ubuntu. https://bugs.launchpad.net/bugs/1956793 Title: linux-azure-cvm: Avoid leaking guest memory when communicating with the host Status in linux-azure-cvm package in Ubuntu: New Status in linux-azure-cvm source package in Focal: Fix Committed Bug description: [Impact] Initialize memory of request offers message to be sent to the host so padding or uninitialized fields do not leak guest memory contents. Patch: https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- next [Test case] Testing the information leakage to the host is not viable, but since the patch the vmbus layer that affects all the hyper-v drivers, a boot test on Hyper-V and on Azure should be enough to validate the patch, considering how small the change is. [Potential regression] The change is very restricted, but on an eventual regression it might affect any of the hyperv guest drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure-cvm/+bug/1956793/+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 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
and here's oem-5.14 1015 minus one patch to see if it caused the bug: http://aaltoset.kapsi.fi/oem-debug/ -- 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/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1956849] Re: Almost all USB ports suddenly stopped working; unbootable
Yes, I have "VIA Labs, Inc. Hub" device: Bus 002 Device 010: ID 2109:2811 VIA Labs, Inc. Hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass9 Hub bDeviceSubClass 0 bDeviceProtocol 1 Single TT bMaxPacketSize064 idVendor 0x2109 VIA Labs, Inc. idProduct 0x2811 Hub bcdDevice 90.90 iManufacturer 1 VIA Labs, Inc. iProduct2 USB2.0 Hub iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0019 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 12 -- 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/1956849 Title: Almost all USB ports suddenly stopped working; unbootable Status in linux package in Ubuntu: New Bug description: This package needs to be pulled NOW. It disables almost all USB-3.0 and USB-C ports completely. Even though I had automatic software updates turned OFF (or so I thought), my Mac Pro suddenly got a new kernel when I rebooted it this morning: Linux macpro-obs 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and it contains a P0 showstopper bug. Upon rebooting, I got dropped into the initrd prompt because Linux could not see the external USB drive that I'm booting from (WDBAGF5000AGY-WESN). I wasted an entire day figuring out what was wrong, and even went so far as to order a replacement SSD, planning to rebuild everything from scratch, because the drive failed to appear in every single USB port I tried. Then I discovered that a different SSD didn't work, either. At that point, I realized that something else was wrong, and I kept trying until I found one other port that worked. I was then able to boot and get dmesg and lsusb output. This kernel update broke not only the built-in ports, but also the ports on a generic USB-C PCIe card (Amazon B08PF8XR73). Mac Pro built-in USB-3.0(A) ports (2x): working Mac Pro built-in USB-C ports (4x): dead USB-C PCIe card USB-C ports (2x): dead USB-C PCIe card USB-3.0(A) ports (5x): dead All devices fail to appear in lsusb when attached to the port, including an Apple USB keyboard, an Anker USB-C Ethernet adapter, a WD SSD, and a Sandisk SSD. I'm going to roll back my kernel to a working kernel, but this package needs to be pulled NOW before it affects too many people. This is too catastrophic a bug to wait even a day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+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 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
@taalton, @vicamo, thank you for such rapid assistance. I will test these immediately and report back in a few minutes. -- 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/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
@timo, there's an issue with the last set of packages. Here's what happens when I try to install: sudo apt install ./linux-headers-5.14.0-1015-oem_5.14.0-1015.15+revert_amd64.deb ./linux-image-unsigned-5.14.0-1015-oem_5.14.0-1015.15+revert_amd64.deb ./linux-modules-5.14.0-1015-oem_5.14.0-1015.15+revert_amd64.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'linux-headers-5.14.0-1015-oem' instead of './linux-headers-5.14.0-1015-oem_5.14.0-1015.15+revert_amd64.deb' Note, selecting 'linux-image-unsigned-5.14.0-1015-oem' instead of './linux-image-unsigned-5.14.0-1015-oem_5.14.0-1015.15+revert_amd64.deb' Note, selecting 'linux-modules-5.14.0-1015-oem' instead of './linux-modules-5.14.0-1015-oem_5.14.0-1015.15+revert_amd64.deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-headers-5.14.0-1015-oem : Depends: linux-oem-5.14-headers-5.14.0-1015 but it is not installable E: Unable to correct problems, you have held broken packages. -- 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/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
@timo, attempting to install the first set, 5.14.21, results in this error: The following packages have unmet dependencies: linux-headers-5.14.21-051421-generic : Depends: libc6 (>= 2.34) but 2.31-0ubuntu9.3 is to be installed Do you have a suggestion on how to proceed here too? -- 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/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1943464] Re: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin20045 -- 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/1943464 Title: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] * After reassigning a PCHID of a ConnectX-5 based RoCE Adapter from one physical LPAR to another, running Ubuntu 20.04 with kernel 5.4 (latest), a lifetime issue occurs. * Subsequent testing on newer kernels now shows that a NULL pointer dereference in the zPCI code happens (causing a hard crash) that was previously hidden by leaking the struct pci_dev. * For a more detailed root cause analysis, see the below original bug description. [Fix] The following three commits fix this issue in focal: * upstream (since v5.12-rc4): 0b13525c20febcfecccf6fc1db5969727401317d 0b13525c20fe "s390/pci: fix leak of PCI device structure" backport: https://launchpadlibrarian.net/566161494/0001-s390-pci-fix-leak-of-PCI-device-structure.patch * upstream (since v5.14-rc7): 2a671f77ee49f3e78997b77fdee139467ff6a598 2a671f77ee49 "s390/pci: fix use after free of zpci_dev" backport: https://launchpadlibrarian.net/566161496/0002-s390-pci-fix-use-after-free-of-zpci_dev.patch * upstream (since v5.15-rc5): a46044a92add6a400f4dada7b943b30221f7cc80 a46044a92add "s390/pci: fix zpci_zdev_put() on reserve" backport: https://launchpadlibrarian.net/566161497/0003-s390-pci-fix-zpci_zdev_put-on-reserve.patch * Commit 0b13525c20fe fixes a lifetime issue of the struct pci_dev that was not released on removal, commit 2a671f77ee49 fixes the 'NULL pointer dereference' (causing the hard crash) itself. and commit a46044a92add fixes the handling of multiple events for a single reserve state transition of the device. Without this, the NULL dereference can still be triggered as Reassign I/O Path causes a redudant second removal event. * Since none of the three upstream commits does apply cleanly to focal master-next by just cherry-picking them (mainly due to changes in the context), the above backports are needed. [Test Case] * Two z15 or LinuxONE III LPARs, one with a Connect-X5 based RoCE adapter attached. * LPARs need to run Ubuntu 20.04 with kernel 5.4 to hit the lifetime issue (that hides the also potential existing 'NULL pointer dereference') - with Hirsute and kernel 5.11 the 'NULL pointer dereference' crash occurs. * Now change the PCHID (physical channel identifier) to a different one from the 2nd LPAR (at the HMC?). * Verify if the reassignment worked properly (by checking the PCHID) and monitor the kernel ring buffer dmesg (diagnostic messages) for "Krnl PSW" crash (caused by NULL pointer) (for more error details, please see below original bug description). * Due hardware availability reasons (the ConnectX-5 cards are only used in special cases), the testing needs to be done by IBM. [Regression Potential / What can go wrong] * What can go wrong with: 2a671f77ee49 "s390/pci: fix use after free of zpci_dev" * The reference count to the struct zpci_dev got increased while it is used by the PCI core. This could cause a leak if not properly released. * Hot-plug of there Connect-X5 devices could be broken on s390x entirely, in case the new pointer handing is erroneous. * This may even have an impact on "cold plug", too. * Fortunately the modifications are quite minimal and thereby traceable, * and affect /arch/s390/pci/pci.c and arch/s390/pci/pci_bus.h only, hence are specific to the s390x platform only and there again to "plugging" of zPCI devices. * What can go wrong with: 0b13525c20fe "s390/pci: fix leak of PCI device structure" * The function zpci_remove_device got expanded with an additional set_error argument, and the internal flow got significantly changed. In case handled in a wrong way, this may harm the entire remove/release logic. * The calls of zpci_remove_device need to be adjusted (as part of the new arg), failures here will most likely be identified at compile time. * The initialization of the pci_dev struct got improved, * and the flow in __zpci_event_availability carefully changed to reflect the device slot/bus remove characteristics. However, issues here may lead again to general zpci hotplug removal issues. * Fortunately all modifications are limited to s390x only (/arch/s390/* and
[Kernel-packages] [Bug 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
@taalton, I installed just the image and modules for 5.14.0-1015 comment 31 without the headers (so no DKMS), and got the same error: "No Bluetooth adapters have been found." I just installed 5.14.21 and will report back here too. -- 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/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1947718] Re: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732
This is a kernel regression and now almost three months old. Could somebody please have a look? -- 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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33
[Kernel-packages] [Bug 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
@tjaalton and @vicamo, I have tested with 5.14.21 without the headers and the bluetooth device is recognized and appears to work. I attached a bluetooth headset and listen to audio without issue. -- 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/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1933771] Re: Bluetooth headset random disconnects AX200
This seems to be mostly solved in Ubuntu 21.10 (compared to 21.04. linux-firmware 1.201.3) for me now. I do regularly (multiple times in a minute) get a hiccup which lasts a fraction of a second where there's no sound output. Not an issue for videocalls (other microphone than through the bluethooth headset to keep A2DP sink opposed to the crappy HFP). That hiccup isn't ideal when listening to music though. -- 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/1933771 Title: Bluetooth headset random disconnects AX200 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Hirsute: In Progress Bug description: [Impact] Using several different bluetooth headsets I find that the Bluetooth functionality of the built-in AX200 module of my motherboard keeps randomly disconnecting. I found that this has been fixed in recent Linux firmware updates, but I am not sure that fix has landed yet in Ubuntu Hirsute. Herewith I am posting the link to exactly the issue I am having: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155 And the Linux Firmware commit that resolves this: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180 A related Fedora bug: https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274 It's difficult to relate the upstream kernel version firmware version in which this was fixed (linux-firmware-20210511) to the version of the linux-firmware Ubuntu package (for me). Perhaps someone can comment on whether this has been merged in. I am still experiencing disconnects with 1.197.1 at least. -- Description: Ubuntu 21.04 Release: 21.04 linux-firmware: Installed: 1.197.1 Candidate: 1.197.1 I expected: Bluetooth headset to remain connected What happened: Bluetooth headset connects, then randomly disconnects and reconnects while playing media [Test Case] See above. [Fix] Update AX20x firmware blobs. [Where Problems Could Occur] New firmware blobs so previously working adapter might now fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
@tjaalton and @vicamo, I have tested with 5.15.8 without the headers and the bluetooth device is recognized and appears to work. I again attached a bluetooth headset and listened to audio without issue. So in summary: FAIL 5.14.0-1013 "No Bluetooth adapters have been found" FAIL 5.14.0-1015 "No Bluetooth adapters have been found" FAIL 5.14.0-1015 without patch (from comment 31) "No Bluetooth adapters have been found" pass 5.14.21-051421-generic Bluetooth adapter available; test audio device works pass 5.15.8-051508-generic Bluetooth adapter available; test audio device works I hope this is helpful, and if there is anything else I can do, please let me know. -- 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/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1956982] [NEW] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04
Public bug reported: Please integrate this customer critical/reported fix that was submitted as a stand along patch: Accepted 11/29/21: Applied to 5.16/scsi-fixes, thanks! [1/1] lpfc: Fix nonrecovery of remote ports following an unsolicited LOGO https://git.kernel.org/mkp/scsi/c/0956ba63bd94 As well as this latest set of bug fix patches accepted upstream 12/6/2021: scsi: lpfc: Fix leaked lpfc_dmabuf mbox allocations with NPIV commitf0d3919697492950f57a26a1093aee53880d669d scsi: lpfc: Change return code on I/Os received during link bounce commit2e81b1a374da5d6024208c16c4a5224a70cafa64 scsi: lpfc: Fix lpfc_force_rscn ndlp kref imbalance commit7576d48c64f36f6fea9df2882f710a474fa35f40 scsi: lpfc: Fix NPIV port deletion crash commit8ed190a91950564775cbaae9e8e8083a69a8da23 scsi: lpfc: Trigger SLI4 firmware dump before doing driver cleanup commit7dd2e2a923173d637c272e483966be8e96a72b64 scsi: lpfc: Adjust CMF total bytes and rxmonitor commita6269f837045acb02904f31f05acde847ec8f8a7 scsi: lpfc: Cap CMF read bytes to MBPI commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 scsi: lpfc: Add additional debugfs support for CMF commit6014a2468f0e49194f612b1f09f99eacee0a409a scsi: lpfc: Update lpfc version to 14.0.0.4 commit4437503bfbec2f02b41b2492520fe627715889a7 Extended log info: -cover-letter.patch 0001-lpfc-Fix-leaked-lpfc_dmabuf-mbox-allocations-with-np.patch commitf0d3919697492950f57a26a1093aee53880d669d lpfc: Fix memory leaked lpfc_dmabuf mbox allocations Fix leaked lpfc_dmabuf allocations in an mbox. svn: r82112 bz: 249968 250131 0002-lpfc-Change-return-code-on-ios-received-during-link-.patch commit2e81b1a374da5d6024208c16c4a5224a70cafa64 lpfc: Group RPI_SUSPENDED error action with DID_REQUEUE Fix Medusa IO errors on Scope and Scale LIP test svn: r82348 bz: 247164 250466 Fix Medusa IO errors on Scope and Scale LIP test - build svn: r82377 bz: 247164 250466 0003-lpfc-Fix-lpfc_force_rscn-ndlp-kref-imbalance.patch commit7576d48c64f36f6fea9df2882f710a474fa35f40 lpfc: Fix lpfc_force_rscn ndlp kref imbalance Fix ndlp kref crash during lpfc_force_rscn svn: r82526 bz: 250692 250695 0004-lpfc-Fix-NPIV-port-deletion-crash.patch commit8ed190a91950564775cbaae9e8e8083a69a8da23 lpfc: Fix NPIV port deletion crash Fix crash when deleting a large number of vports. svn: r82120 bz: 240671 250158 Fix a log message formatting error introduced in svn r82120. svn: r82743 bz: 249968 250131 0005-lpfc-Trigger-SLI4-firmware-dump-before-doing-driver-.patch commit7dd2e2a923173d637c272e483966be8e96a72b64 lpfc: Trigger SLI4 firmware dump immediately without delays Trigger SLI4 firmware dump immediately without delays svn: r82770 bz: 250111 251061 0006-lpfc-Adjust-CMF-total-bytes-and-rxmonitor.patch commita6269f837045acb02904f31f05acde847ec8f8a7 lpfc: Adjust CMF total bytes and rxmonitor Adjust CMF total bytes and add to rxmonitor svn: r82429 bz: 250581 250587 0007-lpfc-Cap-CMF-read-bytes-to-MBPI.patch commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 lpfc: Cap CMF read bytes to MBPI Cap CMF read bytes to MBPI only for shortened timer intervals svn: r82483 bz: 250605 251274 0008-lpfc-Add-additional-debugfs-support-for-CMF.patch commit6014a2468f0e49194f612b1f09f99eacee0a409a lpfc: Add additional debugfs support for CMF Add debugfs support for CMF parameters svn: r82144 bz: 250206 250237 Coverity: CID 19805 Fix memory illegal access svn: r82349 bz: 250454 250465 0009-lpfc-Update-lpfc-version-to-14.0.0.4.patch commit4437503bfbec2f02b41b2492520fe627715889a7 ** 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/1956982 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04 Status in linux package in Ubuntu: New Bug description: Please integrate this customer critical/reported fix that was submitted as a stand along patch: Accepted 11/29/21: Applied to 5.16/scsi-fixes, thanks! [1/1] lpfc: Fix nonrecovery of remote ports following an unsolicited LOGO https://git.kernel.org/mkp/scsi/c/0956ba63bd94 As well as this latest set of bug fix patches accepted upstream 12/6/2021: scsi: lpfc: Fix leaked lpfc_dmabuf mbox allocations with NPIV commitf0d3919697492950f57a26a1093aee53880d669d scsi: lpfc: Change return code on I/Os received during link bounce commit2e81b1a374da5d6024208c16c4a5224a70cafa64 scsi: lpfc: Fix lpfc_force_rscn ndlp kref imbalance commit7576d48c64f36f6fea9df2882f710a474fa35f40 scsi: lpfc: Fix NPIV port deletion crash commit8ed190a91950564775cbaa
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 soft lockup when zfs.ko is loaded on s390x
Update: we're still getting the same failure even with zfs 2.1.2. I've opened an issue upstream: https://github.com/openzfs/zfs/issues/12942 ** Bug watch added: github.com/openzfs/zfs/issues #12942 https://github.com/openzfs/zfs/issues/12942 -- 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/1954676 Title: jammy 5.15 soft lockup when zfs.ko is loaded on s390x Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Moving to zfs 2.1.1 (from Debian) seems to fix the problem. [Regression potential] It is a major zfs update so we may introduce zfs regressions, but it seems sane to be aligned with the upstream zfs version. Also the zfs smoke tests passed across all architectures, so moving to this new version seems the right thing to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1954676/+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 1954676] Re: jammy 5.15 soft lockup when zfs.ko is loaded on s390x
Quick summary: it really looks like a compiler issue, because everything works using the same version of kernel + zfs, but on Impish. Also trying to compile zfs with gcc-10 doesn't show any problem. -- 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/1954676 Title: jammy 5.15 soft lockup when zfs.ko is loaded on s390x Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Moving to zfs 2.1.1 (from Debian) seems to fix the problem. [Regression potential] It is a major zfs update so we may introduce zfs regressions, but it seems sane to be aligned with the upstream zfs version. Also the zfs smoke tests passed across all architectures, so moving to this new version seems the right thing to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1954676/+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 1956982] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04
** 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/1956982 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Please integrate this customer critical/reported fix that was submitted as a stand along patch: Accepted 11/29/21: Applied to 5.16/scsi-fixes, thanks! [1/1] lpfc: Fix nonrecovery of remote ports following an unsolicited LOGO https://git.kernel.org/mkp/scsi/c/0956ba63bd94 As well as this latest set of bug fix patches accepted upstream 12/6/2021: scsi: lpfc: Fix leaked lpfc_dmabuf mbox allocations with NPIV commitf0d3919697492950f57a26a1093aee53880d669d scsi: lpfc: Change return code on I/Os received during link bounce commit2e81b1a374da5d6024208c16c4a5224a70cafa64 scsi: lpfc: Fix lpfc_force_rscn ndlp kref imbalance commit7576d48c64f36f6fea9df2882f710a474fa35f40 scsi: lpfc: Fix NPIV port deletion crash commit8ed190a91950564775cbaae9e8e8083a69a8da23 scsi: lpfc: Trigger SLI4 firmware dump before doing driver cleanup commit7dd2e2a923173d637c272e483966be8e96a72b64 scsi: lpfc: Adjust CMF total bytes and rxmonitor commita6269f837045acb02904f31f05acde847ec8f8a7 scsi: lpfc: Cap CMF read bytes to MBPI commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 scsi: lpfc: Add additional debugfs support for CMF commit6014a2468f0e49194f612b1f09f99eacee0a409a scsi: lpfc: Update lpfc version to 14.0.0.4 commit4437503bfbec2f02b41b2492520fe627715889a7 Extended log info: -cover-letter.patch 0001-lpfc-Fix-leaked-lpfc_dmabuf-mbox-allocations-with-np.patch commitf0d3919697492950f57a26a1093aee53880d669d lpfc: Fix memory leaked lpfc_dmabuf mbox allocations Fix leaked lpfc_dmabuf allocations in an mbox. svn: r82112 bz: 249968 250131 0002-lpfc-Change-return-code-on-ios-received-during-link-.patch commit2e81b1a374da5d6024208c16c4a5224a70cafa64 lpfc: Group RPI_SUSPENDED error action with DID_REQUEUE Fix Medusa IO errors on Scope and Scale LIP test svn: r82348 bz: 247164 250466 Fix Medusa IO errors on Scope and Scale LIP test - build svn: r82377 bz: 247164 250466 0003-lpfc-Fix-lpfc_force_rscn-ndlp-kref-imbalance.patch commit7576d48c64f36f6fea9df2882f710a474fa35f40 lpfc: Fix lpfc_force_rscn ndlp kref imbalance Fix ndlp kref crash during lpfc_force_rscn svn: r82526 bz: 250692 250695 0004-lpfc-Fix-NPIV-port-deletion-crash.patch commit8ed190a91950564775cbaae9e8e8083a69a8da23 lpfc: Fix NPIV port deletion crash Fix crash when deleting a large number of vports. svn: r82120 bz: 240671 250158 Fix a log message formatting error introduced in svn r82120. svn: r82743 bz: 249968 250131 0005-lpfc-Trigger-SLI4-firmware-dump-before-doing-driver-.patch commit7dd2e2a923173d637c272e483966be8e96a72b64 lpfc: Trigger SLI4 firmware dump immediately without delays Trigger SLI4 firmware dump immediately without delays svn: r82770 bz: 250111 251061 0006-lpfc-Adjust-CMF-total-bytes-and-rxmonitor.patch commita6269f837045acb02904f31f05acde847ec8f8a7 lpfc: Adjust CMF total bytes and rxmonitor Adjust CMF total bytes and add to rxmonitor svn: r82429 bz: 250581 250587 0007-lpfc-Cap-CMF-read-bytes-to-MBPI.patch commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 lpfc: Cap CMF read bytes to MBPI Cap CMF read bytes to MBPI only for shortened timer intervals svn: r82483 bz: 250605 251274 0008-lpfc-Add-additional-debugfs-support-for-CMF.patch commit6014a2468f0e49194f612b1f09f99eacee0a409a lpfc: Add additional debugfs support for CMF Add debugfs support for CMF parameters svn: r82144 bz: 250206 250237 Coverity: CID 19805 Fix memory illegal access svn: r82349 bz: 250454 250465 0009-lpfc-Update-lpfc-version-to-14.0.0.4.patch commit4437503bfbec2f02b41b2492520fe627715889a7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956982/+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 1956984] [NEW] hirsute:linux 5.11.0-45.49 fails to boot
Public bug reported: [ Impact ] hirsute:linux 5.11.0-45.49 is not booting on several systems/instances. The boot failure is caused at least in most of the cases by systemd services failing to start. On a amd64 test VM the journald service times out when it's configured to use any storage type (which is the default config). [ Fix ] I was able to boot a VM with the following commit reverted: 327aa2137d989f278ece7e8e31c218dfb3416c35 - mm: filemap: check if THP has hwpoisoned subpage for PMD page fault [ Additional Info ] On an affected VM, after a bit more than 1 hour after booting I get the following soft lockup which helped identify a suspicious commit: [12164.210808] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [systemd-journal:478] [12164.211616] Modules linked in: binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev bochs_drm drm_vram_helper drm_ttm_helper input_leds ttm joydev drm_kms_helper cec rc_core serio_raw fb_sys_fops syscopyarea sysfillrect sysimgblt mac_hid parport_pc parport qemu_fw_cfg sch_fq_codel msr drm ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover i2c_piix4 pata_acpi floppy [12164.211649] CPU: 1 PID: 478 Comm: systemd-journal Tainted: G L 5.11.0-45-generic #49-Ubuntu [12164.211651] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 [12164.211653] RIP: 0010:xas_load+0x33/0x80 [12164.211659] Code: 48 89 c2 83 e2 03 48 83 fa 02 75 08 48 3d 00 10 00 00 77 02 5d c3 0f b6 48 fe 48 8d 70 fe 38 4f 10 77 f1 48 8b 57 08 48 d3 ea <83> e2 3f 89 d0 48 83 c0 04 48 8b 44 c6 08 48 89 77 18 48 89 c1 83 [12164.211661] RSP: :b17440c7fb68 EFLAGS: 0246 [12164.211662] RAX: 92d2823ea6ca RBX: 92d282e52ee8 RCX: [12164.211664] RDX: 003b RSI: 92d2823ea6c8 RDI: b17440c7fb78 [12164.211665] RBP: b17440c7fb68 R08: 92d2823eb47a R09: 92d28674b750 [12164.211666] R10: R11: R12: 003b [12164.211667] R13: 003b R14: 92d282e52ee8 R15: 61c8864680b583eb [12164.211669] FS: 7fdf28760900() GS:92d2fdc8() knlGS: [12164.211670] CS: 0010 DS: ES: CR0: 80050033 [12164.211672] CR2: 7fdf28522018 CR3: 02d34000 CR4: 06e0 [12164.211675] Call Trace: [12164.211678] find_get_entry+0x5a/0x160 [12164.211682] find_lock_entry+0x2d/0x120 [12164.211685] shmem_getpage_gfp+0xe8/0x8c0 [12164.211687] ? asm_sysvec_apic_timer_interrupt+0x12/0x20 [12164.211691] shmem_fault+0x7b/0x220 [12164.211693] ? file_update_time+0x62/0x140 [12164.211696] __do_fault+0x3c/0xe0 [12164.211699] do_shared_fault+0x19/0xb0 [12164.211701] do_fault+0x1cd/0x1f0 [12164.211704] handle_pte_fault+0x1e5/0x260 [12164.211706] __handle_mm_fault+0x59a/0x7c0 [12164.211709] ? timerqueue_add+0x68/0xa0 [12164.211711] handle_mm_fault+0xd7/0x2b0 [12164.211714] do_user_addr_fault+0x1a0/0x450 [12164.211717] exc_page_fault+0x69/0x150 [12164.211720] ? asm_exc_page_fault+0x8/0x30 [12164.211722] asm_exc_page_fault+0x1e/0x30 [12164.211723] RIP: 0033:0x7fdf28fbece1 [12164.211727] Code: 0f 11 5f 30 0f 11 64 17 f0 0f 11 6c 17 e0 0f 11 74 17 d0 0f 11 7c 17 c0 c3 0f 10 06 0f 10 4e 10 0f 10 54 16 f0 0f 10 5c 16 e0 <0f> 11 07 0f 11 4f 10 0f 11 54 17 f0 0f 11 5c 17 e0 c3 48 39 f7 0f [12164.211728] RSP: 002b:7fffd18bffd8 EFLAGS: 00010287 [12164.211730] RAX: 7fdf28522018 RBX: 7fffd18c0520 RCX: 7fdf28521fd8 [12164.211731] RDX: 002b RSI: 7fffd18c0520 RDI: 7fdf28522018 [12164.211732] RBP: 5643719d90c0 R08: 0001 R09: 0003afd8 [12164.211733] R10: 0002 R11: 7fffd1947090 R12: 002b [12164.211734] R13: 23e0650ff2b8eb94 R14: R15: 7fffd18c ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Hirsute) Importance: High Assignee: Kamal Mostafa (kamalmostafa) Status: Confirmed ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) 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/1956984 Title: hirsute:linux 5.11.0-45.49 fails to boot Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Confirmed Bug description: [ Impact ] hirsute:linux 5.11.0-45.49 is not booting on several systems/instances. The boot failure is caused at least in most of the cases by systemd services failing to start. On a amd64 test VM the journald service times out when it's configured to use any storage type (which is the default config). [ Fix ] I was able t
[Kernel-packages] [Bug 1956984] Re: hirsute:linux 5.11.0-45.49 fails to boot
This is caused by a bogus backport of a patch from 5.14.y: [hirsute] 327aa2137d98 mm: filemap: check if THP has hwpoisoned subpage for PMD page fault Contains a fragment that was applied to the wrong function. Corrected patch is on the way. ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => High -- 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/1956984 Title: hirsute:linux 5.11.0-45.49 fails to boot Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Confirmed Bug description: [ Impact ] hirsute:linux 5.11.0-45.49 is not booting on several systems/instances. The boot failure is caused at least in most of the cases by systemd services failing to start. On a amd64 test VM the journald service times out when it's configured to use any storage type (which is the default config). [ Fix ] I was able to boot a VM with the following commit reverted: 327aa2137d989f278ece7e8e31c218dfb3416c35 - mm: filemap: check if THP has hwpoisoned subpage for PMD page fault [ Additional Info ] On an affected VM, after a bit more than 1 hour after booting I get the following soft lockup which helped identify a suspicious commit: [12164.210808] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [systemd-journal:478] [12164.211616] Modules linked in: binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev bochs_drm drm_vram_helper drm_ttm_helper input_leds ttm joydev drm_kms_helper cec rc_core serio_raw fb_sys_fops syscopyarea sysfillrect sysimgblt mac_hid parport_pc parport qemu_fw_cfg sch_fq_codel msr drm ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover i2c_piix4 pata_acpi floppy [12164.211649] CPU: 1 PID: 478 Comm: systemd-journal Tainted: G L 5.11.0-45-generic #49-Ubuntu [12164.211651] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 [12164.211653] RIP: 0010:xas_load+0x33/0x80 [12164.211659] Code: 48 89 c2 83 e2 03 48 83 fa 02 75 08 48 3d 00 10 00 00 77 02 5d c3 0f b6 48 fe 48 8d 70 fe 38 4f 10 77 f1 48 8b 57 08 48 d3 ea <83> e2 3f 89 d0 48 83 c0 04 48 8b 44 c6 08 48 89 77 18 48 89 c1 83 [12164.211661] RSP: :b17440c7fb68 EFLAGS: 0246 [12164.211662] RAX: 92d2823ea6ca RBX: 92d282e52ee8 RCX: [12164.211664] RDX: 003b RSI: 92d2823ea6c8 RDI: b17440c7fb78 [12164.211665] RBP: b17440c7fb68 R08: 92d2823eb47a R09: 92d28674b750 [12164.211666] R10: R11: R12: 003b [12164.211667] R13: 003b R14: 92d282e52ee8 R15: 61c8864680b583eb [12164.211669] FS: 7fdf28760900() GS:92d2fdc8() knlGS: [12164.211670] CS: 0010 DS: ES: CR0: 80050033 [12164.211672] CR2: 7fdf28522018 CR3: 02d34000 CR4: 06e0 [12164.211675] Call Trace: [12164.211678] find_get_entry+0x5a/0x160 [12164.211682] find_lock_entry+0x2d/0x120 [12164.211685] shmem_getpage_gfp+0xe8/0x8c0 [12164.211687] ? asm_sysvec_apic_timer_interrupt+0x12/0x20 [12164.211691] shmem_fault+0x7b/0x220 [12164.211693] ? file_update_time+0x62/0x140 [12164.211696] __do_fault+0x3c/0xe0 [12164.211699] do_shared_fault+0x19/0xb0 [12164.211701] do_fault+0x1cd/0x1f0 [12164.211704] handle_pte_fault+0x1e5/0x260 [12164.211706] __handle_mm_fault+0x59a/0x7c0 [12164.211709] ? timerqueue_add+0x68/0xa0 [12164.211711] handle_mm_fault+0xd7/0x2b0 [12164.211714] do_user_addr_fault+0x1a0/0x450 [12164.211717] exc_page_fault+0x69/0x150 [12164.211720] ? asm_exc_page_fault+0x8/0x30 [12164.211722] asm_exc_page_fault+0x1e/0x30 [12164.211723] RIP: 0033:0x7fdf28fbece1 [12164.211727] Code: 0f 11 5f 30 0f 11 64 17 f0 0f 11 6c 17 e0 0f 11 74 17 d0 0f 11 7c 17 c0 c3 0f 10 06 0f 10 4e 10 0f 10 54 16 f0 0f 10 5c 16 e0 <0f> 11 07 0f 11 4f 10 0f 11 54 17 f0 0f 11 5c 17 e0 c3 48 39 f7 0f [12164.211728] RSP: 002b:7fffd18bffd8 EFLAGS: 00010287 [12164.211730] RAX: 7fdf28522018 RBX: 7fffd18c0520 RCX: 7fdf28521fd8 [12164.211731] RDX: 002b RSI: 7fffd18c0520 RDI: 7fdf28522018 [12164.211732] RBP: 5643719d90c0 R08: 0001 R09: 0003afd8 [12164.211733] R10: 0002 R11: 7fffd1947090 R12: 002b [12164.211734] R13: 23e0650ff2b8eb94 R14: R15: 7fffd18c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://lau
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 soft lockup when zfs.ko is loaded on s390x
I've tried multiple versions of gcc and here's the result: - gcc 11.2.0-13ubuntu1 : bad - gcc 11.2.0-12ubuntu1 : bad - gcc 11.2.0-10ubuntu1 : bad - gcc 11.2.0-7ubuntu2 : good - gcc 10.3.0-13ubuntu1 : good Apparently the last version of gcc that seems to work with zfs + kernel 5.15 is 11.2.0-7ubuntu2 (the one currently in impish). The same behavior happens both with a vanilla 5.15 and our Ubuntu kernel 5.15 (only on s390x, all the other architectures are working just fine). -- 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/1954676 Title: jammy 5.15 soft lockup when zfs.ko is loaded on s390x Status in gcc-11 package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in gcc-11 source package in Jammy: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to downgrade gcc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1954676/+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 1954676] Re: jammy 5.15 soft lockup when zfs.ko is loaded on s390x
** Also affects: gcc-11 (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. + + This seems to happen only when zfs is compile with gcc >= + 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the + problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Moving to zfs 2.1.1 (from Debian) seems to fix the problem. [Regression potential] It is a major zfs update so we may introduce zfs regressions, but it seems sane to be aligned with the upstream zfs version. Also the zfs smoke tests passed across all architectures, so moving to this new version seems the right thing to do. ** Description changed: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] - Moving to zfs 2.1.1 (from Debian) seems to fix the problem. - - [Regression potential] - - It is a major zfs update so we may introduce zfs regressions, but it - seems sane to be aligned with the upstream zfs version. Also the zfs - smoke tests passed across all architectures, so moving to this new - version seems the right thing to do. + Temporary workaround is to downgrade gcc. -- 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/1954676 Title: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 Status in gcc-11 package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in gcc-11 source package in Jammy: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to downgrade gcc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1954676/+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 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1
** Summary changed: - jammy 5.15 soft lockup when zfs.ko is loaded on s390x + jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 ** Changed in: gcc-11 (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: zfs-linux (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: zfs-linux (Ubuntu Jammy) Assignee: (unassigned) => Andrea Righi (arighi) -- 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/1954676 Title: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 Status in gcc-11 package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in gcc-11 source package in Jammy: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to downgrade gcc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1954676/+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 1956985] [NEW] Focal update: v5.14.21 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.14.21 upstream stable release from git://git.kernel.org/ Linux 5.14.21 Revert "ACPI: scan: Release PM resources blocked by unused objects" thermal: Fix NULL pointer dereferences in of_thermal_ functions perf/core: Avoid put_page() when GUP fails PCI: Add MSI masking quirk for Nvidia ION AHCI PCI/MSI: Deal with devices lying about their MSI mask capability PCI/MSI: Destroy sysfs before freeing entries parisc/entry: fix trace test in syscall exit path Bluetooth: btusb: Add support for TP-Link UB500 Adapter bootconfig: init: Fix memblock leak in xbc_make_cmdline() loop: Use blk_validate_block_size() to validate block size block: Add a helper to validate the block size fortify: Explicitly disable Clang support KVM: Fix steal time asm constraints Revert "drm: fb_helper: fix CONFIG_FB dependency" Revert "drm: fb_helper: improve CONFIG_FB dependency" ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu) Status: Confirmed => Invalid -- 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/1956985 Title: Focal update: v5.14.21 upstream stable release Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: New Bug description: 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.14.21 upstream stable release from git://git.kernel.org/ Linux 5.14.21 Revert "ACPI: scan: Release PM resources blocked by unused objects" thermal: Fix NULL pointer dereferences in of_thermal_ functions perf/core: Avoid put_page() when GUP fails PCI: Add MSI masking quirk for Nvidia ION AHCI PCI/MSI: Deal with devices lying about their MSI mask capability PCI/MSI: Destroy sysfs before freeing entries parisc/entry: fix trace test in syscall exit path Bluetooth: btusb: Add support for TP-Link UB500 Adapter bootconfig: init: Fix memblock leak in xbc_make_cmdline() loop: Use blk_validate_block_size() to validate block size block: Add a helper to validate the block size fortify: Explicitly disable Clang support KVM: Fix steal time asm constraints Revert "drm: fb_helper: fix CONFIG_FB dependency" Revert "drm: fb_helper: improve CONFIG_FB dependency" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956985/+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 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
looks like 1015 didn't actually contain 5.14.21 but .20, though I doubt the fix was there but you may also try .20 mainline to see if it fails -- 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/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1956984] Re: hirsute:linux 5.11.0-45.49 fails to boot
https://lists.ubuntu.com/archives/kernel-team/2022-January/127054.html -- 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/1956984 Title: hirsute:linux 5.11.0-45.49 fails to boot Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Confirmed Bug description: [ Impact ] hirsute:linux 5.11.0-45.49 is not booting on several systems/instances. The boot failure is caused at least in most of the cases by systemd services failing to start. On a amd64 test VM the journald service times out when it's configured to use any storage type (which is the default config). [ Fix ] I was able to boot a VM with the following commit reverted: 327aa2137d989f278ece7e8e31c218dfb3416c35 - mm: filemap: check if THP has hwpoisoned subpage for PMD page fault [ Additional Info ] On an affected VM, after a bit more than 1 hour after booting I get the following soft lockup which helped identify a suspicious commit: [12164.210808] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [systemd-journal:478] [12164.211616] Modules linked in: binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev bochs_drm drm_vram_helper drm_ttm_helper input_leds ttm joydev drm_kms_helper cec rc_core serio_raw fb_sys_fops syscopyarea sysfillrect sysimgblt mac_hid parport_pc parport qemu_fw_cfg sch_fq_codel msr drm ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover i2c_piix4 pata_acpi floppy [12164.211649] CPU: 1 PID: 478 Comm: systemd-journal Tainted: G L 5.11.0-45-generic #49-Ubuntu [12164.211651] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 [12164.211653] RIP: 0010:xas_load+0x33/0x80 [12164.211659] Code: 48 89 c2 83 e2 03 48 83 fa 02 75 08 48 3d 00 10 00 00 77 02 5d c3 0f b6 48 fe 48 8d 70 fe 38 4f 10 77 f1 48 8b 57 08 48 d3 ea <83> e2 3f 89 d0 48 83 c0 04 48 8b 44 c6 08 48 89 77 18 48 89 c1 83 [12164.211661] RSP: :b17440c7fb68 EFLAGS: 0246 [12164.211662] RAX: 92d2823ea6ca RBX: 92d282e52ee8 RCX: [12164.211664] RDX: 003b RSI: 92d2823ea6c8 RDI: b17440c7fb78 [12164.211665] RBP: b17440c7fb68 R08: 92d2823eb47a R09: 92d28674b750 [12164.211666] R10: R11: R12: 003b [12164.211667] R13: 003b R14: 92d282e52ee8 R15: 61c8864680b583eb [12164.211669] FS: 7fdf28760900() GS:92d2fdc8() knlGS: [12164.211670] CS: 0010 DS: ES: CR0: 80050033 [12164.211672] CR2: 7fdf28522018 CR3: 02d34000 CR4: 06e0 [12164.211675] Call Trace: [12164.211678] find_get_entry+0x5a/0x160 [12164.211682] find_lock_entry+0x2d/0x120 [12164.211685] shmem_getpage_gfp+0xe8/0x8c0 [12164.211687] ? asm_sysvec_apic_timer_interrupt+0x12/0x20 [12164.211691] shmem_fault+0x7b/0x220 [12164.211693] ? file_update_time+0x62/0x140 [12164.211696] __do_fault+0x3c/0xe0 [12164.211699] do_shared_fault+0x19/0xb0 [12164.211701] do_fault+0x1cd/0x1f0 [12164.211704] handle_pte_fault+0x1e5/0x260 [12164.211706] __handle_mm_fault+0x59a/0x7c0 [12164.211709] ? timerqueue_add+0x68/0xa0 [12164.211711] handle_mm_fault+0xd7/0x2b0 [12164.211714] do_user_addr_fault+0x1a0/0x450 [12164.211717] exc_page_fault+0x69/0x150 [12164.211720] ? asm_exc_page_fault+0x8/0x30 [12164.211722] asm_exc_page_fault+0x1e/0x30 [12164.211723] RIP: 0033:0x7fdf28fbece1 [12164.211727] Code: 0f 11 5f 30 0f 11 64 17 f0 0f 11 6c 17 e0 0f 11 74 17 d0 0f 11 7c 17 c0 c3 0f 10 06 0f 10 4e 10 0f 10 54 16 f0 0f 10 5c 16 e0 <0f> 11 07 0f 11 4f 10 0f 11 54 17 f0 0f 11 5c 17 e0 c3 48 39 f7 0f [12164.211728] RSP: 002b:7fffd18bffd8 EFLAGS: 00010287 [12164.211730] RAX: 7fdf28522018 RBX: 7fffd18c0520 RCX: 7fdf28521fd8 [12164.211731] RDX: 002b RSI: 7fffd18c0520 RDI: 7fdf28522018 [12164.211732] RBP: 5643719d90c0 R08: 0001 R09: 0003afd8 [12164.211733] R10: 0002 R11: 7fffd1947090 R12: 002b [12164.211734] R13: 23e0650ff2b8eb94 R14: R15: 7fffd18c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956984/+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 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
This bug was fixed in the package linux - 5.13.0-25.26
---
linux (5.13.0-25.26) impish; urgency=medium
* amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
(LP: #1956401)
- drm/amdkfd: fix boot failure when iommu is disabled in Picasso.
* OOB write on BPF_RINGBUF (LP: #1956585)
- SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other
than 0
-- Kleber Sacilotto de Souza Fri, 07 Jan
2022 16:16:40 +0100
** Changed in: linux (Ubuntu Impish)
Status: Confirmed => Fix Released
--
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/1956401
Title:
amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
works
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Impish:
Fix Released
Bug description:
SRU Justification
Impact:
This does not occur with linux-image-5.13.0-22-generic, but does with
linux-image-5.13.0-23-generic.
On startup, I get about a 60 second hang, with the following in the kernel
dmesg:
Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
I have the following GPU:
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Picass
o (rev c2) (prog-if 00 [VGA controller])
04:00.0 0300: 1002:15d8 (rev c2)
(This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)
I get a similar hang if I start firefox (when it's probing OpenGL
contexts), and even with glxgears and glxinfo. Seems like anything
that'd kick on a OpenGL context does it. I had a freeze as well when
I tried running firefox and glxgears both. Along with odd BUG:
messages logged (I have some in the attached log.)
I was running with "iommu=pt", but did try with this removed, still
got the errors (I think amdgpu driver uses the IOMMU even when it's
set to IOMMU=pt though.). See the attached log for some very odd
"[Hardware Error]" messages that were logged on one test run. I think
this was when I tried to run firestorm (second life viewer) -- that
had a large pause then opened to a black window.
Per Google, I see there was a bug like this that turned up in kernel
5.14.15 but fixed in 5.14.17. See
https://gitlab.freedesktop.org/drm/amd/-/issues/1770
Thanks!
--Henry
Fix:
upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is
disabled in Picasso.")
Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
from an upstream patch set. multiple confirmations the problem is
resolved with the kernel in -proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+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 1955906] Re: [SRU][J/OEM-5.14] Add an ID of QCOM WCN6855 bluetooth
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1018.19 --- linux-oem-5.14 (5.14.0-1018.19) focal; urgency=medium * OOB write on BPF_RINGBUF (LP: #1956585) - SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other than 0 linux-oem-5.14 (5.14.0-1015.15) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1015.15 -proposed tracker (LP: #1956424) * Support Intel IPU6 MIPI camera on Alder Lake platforms (LP: #1955383) - SAUCE: intel ipu drivers first release - SAUCE: IPU driver release WW48 - SAUCE: IPU driver release WW48 with MCU - SAUCE: IPU driver release WW52 - SAUCE: IPU driver release WW04 - SAUCE: IPU driver release WW14 - SAUCE: Fix ov01a1s output mirror issue - SAUCE: integrate IPU6 builds - [Config] updateconfigs for IPU6 driver - SAUCE: Fix ov01a1s IQ issues - SAUCE: intel/ipu6: Remove unnecessary video devices - SAUCE: change power control driver to acpi driver - SAUCE: IPU6 driver release for kernel 5.13 - SAUCE: sensor HM11b1 brightness bugfix - SAUCE: Fix build error on Kernel 5.13 - SAUCE: IPU6 driver release for kernel 5.14 on 2021-11-01 - [Config] IPU6: enable OV01A10 sensor - SAUCE: intel visual sensing controller(VSC) driver first release - [Config] ivsc: enable Intel VSC drivers - SAUCE: ivsc: return error when device not ready - SAUCE: ivsc: add soft dependencies for intel_vsc module - SAUCE: ljca: switch wait event to uninterruptible - SAUCE: mei-vsc: switch wait event to uninterruptible - SAUCE: mei_vsc: add ACPI HID for ADL - SAUCE: ljca: add multi ACPI HID support - SAUCE: ivsc: add delay for acquire camera to wait firmware ready - SAUCE: mei_vsc: distinguish platform with different camera sensor - SAUCE: i2c-ljca: fix a potential issue - SAUCE: ljca: disable autosuspend by default * Add Bluetooth support for Qualcomm WCN6856 (LP: #1955689) - Revert "UBUNTU: SAUCE: Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller" - Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller - Bluetooth: btusb: re-definition for board_id in struct qca_version - Bluetooth: btusb: Add the new support IDs for WCN6855 * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - bus: mhi: core: Add support for forced PM resume - ath11k: add string type to search board data in board-2.bin for WCN6855 - ath11k: change to use dynamic memory for channel list of scan * rtw88_8821ce causes freeze (LP: #1927808) - rtw88: Disable PCIe ASPM while doing NAPI poll on 8821CE linux-oem-5.14 (5.14.0-1014.14) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1014.14 -proposed tracker (LP: #1956354) * [SRU][J/OEM-5.14] Add an ID of QCOM WCN6855 bluetooth (LP: #1955906) - SAUCE: Bluetooth: btusb: Add support for Foxconn QCA 0xe0d0 * audio mute/ mic mute are not working on a HP machine (LP: #1955691) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * CVE-2021-4090 - NFSD: Fix exposure in nfsd4_decode_bitmap() -- Thadeu Lima de Souza Cascardo Fri, 07 Jan 2022 15:27:13 -0300 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4090 -- 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/1955906 Title: [SRU][J/OEM-5.14] Add an ID of QCOM WCN6855 bluetooth Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] An ID of WCN6855 bluetooth from Foxconn is missing. [Fix] Add an ID in btusb to load correct driver. This patch is based on SRU https://bugs.launchpad.net/bugs/1955689. Please apply it first. [Test] Verified on HW with BT headphones, it works fine. [Where problems could occur] Limited to specific HW, it may not work well. Due to the schedule of project and only ID is added, SRU it as SAUCE patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955906/+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 1955613] Re: Add basic Wifi support for Qualcomm WCN6856
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1018.19 --- linux-oem-5.14 (5.14.0-1018.19) focal; urgency=medium * OOB write on BPF_RINGBUF (LP: #1956585) - SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other than 0 linux-oem-5.14 (5.14.0-1015.15) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1015.15 -proposed tracker (LP: #1956424) * Support Intel IPU6 MIPI camera on Alder Lake platforms (LP: #1955383) - SAUCE: intel ipu drivers first release - SAUCE: IPU driver release WW48 - SAUCE: IPU driver release WW48 with MCU - SAUCE: IPU driver release WW52 - SAUCE: IPU driver release WW04 - SAUCE: IPU driver release WW14 - SAUCE: Fix ov01a1s output mirror issue - SAUCE: integrate IPU6 builds - [Config] updateconfigs for IPU6 driver - SAUCE: Fix ov01a1s IQ issues - SAUCE: intel/ipu6: Remove unnecessary video devices - SAUCE: change power control driver to acpi driver - SAUCE: IPU6 driver release for kernel 5.13 - SAUCE: sensor HM11b1 brightness bugfix - SAUCE: Fix build error on Kernel 5.13 - SAUCE: IPU6 driver release for kernel 5.14 on 2021-11-01 - [Config] IPU6: enable OV01A10 sensor - SAUCE: intel visual sensing controller(VSC) driver first release - [Config] ivsc: enable Intel VSC drivers - SAUCE: ivsc: return error when device not ready - SAUCE: ivsc: add soft dependencies for intel_vsc module - SAUCE: ljca: switch wait event to uninterruptible - SAUCE: mei-vsc: switch wait event to uninterruptible - SAUCE: mei_vsc: add ACPI HID for ADL - SAUCE: ljca: add multi ACPI HID support - SAUCE: ivsc: add delay for acquire camera to wait firmware ready - SAUCE: mei_vsc: distinguish platform with different camera sensor - SAUCE: i2c-ljca: fix a potential issue - SAUCE: ljca: disable autosuspend by default * Add Bluetooth support for Qualcomm WCN6856 (LP: #1955689) - Revert "UBUNTU: SAUCE: Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller" - Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller - Bluetooth: btusb: re-definition for board_id in struct qca_version - Bluetooth: btusb: Add the new support IDs for WCN6855 * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - bus: mhi: core: Add support for forced PM resume - ath11k: add string type to search board data in board-2.bin for WCN6855 - ath11k: change to use dynamic memory for channel list of scan * rtw88_8821ce causes freeze (LP: #1927808) - rtw88: Disable PCIe ASPM while doing NAPI poll on 8821CE linux-oem-5.14 (5.14.0-1014.14) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1014.14 -proposed tracker (LP: #1956354) * [SRU][J/OEM-5.14] Add an ID of QCOM WCN6855 bluetooth (LP: #1955906) - SAUCE: Bluetooth: btusb: Add support for Foxconn QCA 0xe0d0 * audio mute/ mic mute are not working on a HP machine (LP: #1955691) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * CVE-2021-4090 - NFSD: Fix exposure in nfsd4_decode_bitmap() -- Thadeu Lima de Souza Cascardo Fri, 07 Jan 2022 15:27:13 -0300 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4090 -- 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/1955613 Title: Add basic Wifi support for Qualcomm WCN6856 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Confirmed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Qualcomm WCN6856 doens't work. [Fix] Backport missing bits to make Wifi 5 work. Wifi 6 support is not in the scope of this SRU. [Test] The system can connect to Wifi. Wifi still works after several rounds of suspend/resume cycles. [Where problems could occur] The change is limited to ath11k, which is also the only user of mhi bus, so the scope of risk is limited. Let alone it never worked before, so there's not much room to go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955613/+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 1955691] Re: audio mute/ mic mute are not working on a HP machine
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1018.19 --- linux-oem-5.14 (5.14.0-1018.19) focal; urgency=medium * OOB write on BPF_RINGBUF (LP: #1956585) - SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other than 0 linux-oem-5.14 (5.14.0-1015.15) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1015.15 -proposed tracker (LP: #1956424) * Support Intel IPU6 MIPI camera on Alder Lake platforms (LP: #1955383) - SAUCE: intel ipu drivers first release - SAUCE: IPU driver release WW48 - SAUCE: IPU driver release WW48 with MCU - SAUCE: IPU driver release WW52 - SAUCE: IPU driver release WW04 - SAUCE: IPU driver release WW14 - SAUCE: Fix ov01a1s output mirror issue - SAUCE: integrate IPU6 builds - [Config] updateconfigs for IPU6 driver - SAUCE: Fix ov01a1s IQ issues - SAUCE: intel/ipu6: Remove unnecessary video devices - SAUCE: change power control driver to acpi driver - SAUCE: IPU6 driver release for kernel 5.13 - SAUCE: sensor HM11b1 brightness bugfix - SAUCE: Fix build error on Kernel 5.13 - SAUCE: IPU6 driver release for kernel 5.14 on 2021-11-01 - [Config] IPU6: enable OV01A10 sensor - SAUCE: intel visual sensing controller(VSC) driver first release - [Config] ivsc: enable Intel VSC drivers - SAUCE: ivsc: return error when device not ready - SAUCE: ivsc: add soft dependencies for intel_vsc module - SAUCE: ljca: switch wait event to uninterruptible - SAUCE: mei-vsc: switch wait event to uninterruptible - SAUCE: mei_vsc: add ACPI HID for ADL - SAUCE: ljca: add multi ACPI HID support - SAUCE: ivsc: add delay for acquire camera to wait firmware ready - SAUCE: mei_vsc: distinguish platform with different camera sensor - SAUCE: i2c-ljca: fix a potential issue - SAUCE: ljca: disable autosuspend by default * Add Bluetooth support for Qualcomm WCN6856 (LP: #1955689) - Revert "UBUNTU: SAUCE: Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller" - Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller - Bluetooth: btusb: re-definition for board_id in struct qca_version - Bluetooth: btusb: Add the new support IDs for WCN6855 * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - bus: mhi: core: Add support for forced PM resume - ath11k: add string type to search board data in board-2.bin for WCN6855 - ath11k: change to use dynamic memory for channel list of scan * rtw88_8821ce causes freeze (LP: #1927808) - rtw88: Disable PCIe ASPM while doing NAPI poll on 8821CE linux-oem-5.14 (5.14.0-1014.14) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1014.14 -proposed tracker (LP: #1956354) * [SRU][J/OEM-5.14] Add an ID of QCOM WCN6855 bluetooth (LP: #1955906) - SAUCE: Bluetooth: btusb: Add support for Foxconn QCA 0xe0d0 * audio mute/ mic mute are not working on a HP machine (LP: #1955691) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * CVE-2021-4090 - NFSD: Fix exposure in nfsd4_decode_bitmap() -- Thadeu Lima de Souza Cascardo Fri, 07 Jan 2022 15:27:13 -0300 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4090 -- 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/1955691 Title: audio mute/ mic mute are not working on a HP machine Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not working on a HP platform [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955691/+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/
[Kernel-packages] [Bug 1955689] Re: Add Bluetooth support for Qualcomm WCN6856
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1018.19 --- linux-oem-5.14 (5.14.0-1018.19) focal; urgency=medium * OOB write on BPF_RINGBUF (LP: #1956585) - SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other than 0 linux-oem-5.14 (5.14.0-1015.15) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1015.15 -proposed tracker (LP: #1956424) * Support Intel IPU6 MIPI camera on Alder Lake platforms (LP: #1955383) - SAUCE: intel ipu drivers first release - SAUCE: IPU driver release WW48 - SAUCE: IPU driver release WW48 with MCU - SAUCE: IPU driver release WW52 - SAUCE: IPU driver release WW04 - SAUCE: IPU driver release WW14 - SAUCE: Fix ov01a1s output mirror issue - SAUCE: integrate IPU6 builds - [Config] updateconfigs for IPU6 driver - SAUCE: Fix ov01a1s IQ issues - SAUCE: intel/ipu6: Remove unnecessary video devices - SAUCE: change power control driver to acpi driver - SAUCE: IPU6 driver release for kernel 5.13 - SAUCE: sensor HM11b1 brightness bugfix - SAUCE: Fix build error on Kernel 5.13 - SAUCE: IPU6 driver release for kernel 5.14 on 2021-11-01 - [Config] IPU6: enable OV01A10 sensor - SAUCE: intel visual sensing controller(VSC) driver first release - [Config] ivsc: enable Intel VSC drivers - SAUCE: ivsc: return error when device not ready - SAUCE: ivsc: add soft dependencies for intel_vsc module - SAUCE: ljca: switch wait event to uninterruptible - SAUCE: mei-vsc: switch wait event to uninterruptible - SAUCE: mei_vsc: add ACPI HID for ADL - SAUCE: ljca: add multi ACPI HID support - SAUCE: ivsc: add delay for acquire camera to wait firmware ready - SAUCE: mei_vsc: distinguish platform with different camera sensor - SAUCE: i2c-ljca: fix a potential issue - SAUCE: ljca: disable autosuspend by default * Add Bluetooth support for Qualcomm WCN6856 (LP: #1955689) - Revert "UBUNTU: SAUCE: Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller" - Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller - Bluetooth: btusb: re-definition for board_id in struct qca_version - Bluetooth: btusb: Add the new support IDs for WCN6855 * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - bus: mhi: core: Add support for forced PM resume - ath11k: add string type to search board data in board-2.bin for WCN6855 - ath11k: change to use dynamic memory for channel list of scan * rtw88_8821ce causes freeze (LP: #1927808) - rtw88: Disable PCIe ASPM while doing NAPI poll on 8821CE linux-oem-5.14 (5.14.0-1014.14) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1014.14 -proposed tracker (LP: #1956354) * [SRU][J/OEM-5.14] Add an ID of QCOM WCN6855 bluetooth (LP: #1955906) - SAUCE: Bluetooth: btusb: Add support for Foxconn QCA 0xe0d0 * audio mute/ mic mute are not working on a HP machine (LP: #1955691) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * CVE-2021-4090 - NFSD: Fix exposure in nfsd4_decode_bitmap() -- Thadeu Lima de Souza Cascardo Fri, 07 Jan 2022 15:27:13 -0300 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4090 -- 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/1955689 Title: Add Bluetooth support for Qualcomm WCN6856 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Confirmed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] WCN6856 Bluetooth doesn't work. [Fix] Backport firmware blobs and driver support to make it work by loading correct firmwares. [Test] Bluetooth scanning and pairing work, and continue to do so after several suspend/resume cycles. [Where problems could occur] The upstream version of btusb_generate_qca_nvm_name() adds several missing le*_to_cpu() macros, so if this device was ever used on a Big Endian system, this is a behavioral change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955689/+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 1927808] Re: rtw88_8821ce causes freeze
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1018.19 --- linux-oem-5.14 (5.14.0-1018.19) focal; urgency=medium * OOB write on BPF_RINGBUF (LP: #1956585) - SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other than 0 linux-oem-5.14 (5.14.0-1015.15) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1015.15 -proposed tracker (LP: #1956424) * Support Intel IPU6 MIPI camera on Alder Lake platforms (LP: #1955383) - SAUCE: intel ipu drivers first release - SAUCE: IPU driver release WW48 - SAUCE: IPU driver release WW48 with MCU - SAUCE: IPU driver release WW52 - SAUCE: IPU driver release WW04 - SAUCE: IPU driver release WW14 - SAUCE: Fix ov01a1s output mirror issue - SAUCE: integrate IPU6 builds - [Config] updateconfigs for IPU6 driver - SAUCE: Fix ov01a1s IQ issues - SAUCE: intel/ipu6: Remove unnecessary video devices - SAUCE: change power control driver to acpi driver - SAUCE: IPU6 driver release for kernel 5.13 - SAUCE: sensor HM11b1 brightness bugfix - SAUCE: Fix build error on Kernel 5.13 - SAUCE: IPU6 driver release for kernel 5.14 on 2021-11-01 - [Config] IPU6: enable OV01A10 sensor - SAUCE: intel visual sensing controller(VSC) driver first release - [Config] ivsc: enable Intel VSC drivers - SAUCE: ivsc: return error when device not ready - SAUCE: ivsc: add soft dependencies for intel_vsc module - SAUCE: ljca: switch wait event to uninterruptible - SAUCE: mei-vsc: switch wait event to uninterruptible - SAUCE: mei_vsc: add ACPI HID for ADL - SAUCE: ljca: add multi ACPI HID support - SAUCE: ivsc: add delay for acquire camera to wait firmware ready - SAUCE: mei_vsc: distinguish platform with different camera sensor - SAUCE: i2c-ljca: fix a potential issue - SAUCE: ljca: disable autosuspend by default * Add Bluetooth support for Qualcomm WCN6856 (LP: #1955689) - Revert "UBUNTU: SAUCE: Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller" - Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller - Bluetooth: btusb: re-definition for board_id in struct qca_version - Bluetooth: btusb: Add the new support IDs for WCN6855 * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - bus: mhi: core: Add support for forced PM resume - ath11k: add string type to search board data in board-2.bin for WCN6855 - ath11k: change to use dynamic memory for channel list of scan * rtw88_8821ce causes freeze (LP: #1927808) - rtw88: Disable PCIe ASPM while doing NAPI poll on 8821CE linux-oem-5.14 (5.14.0-1014.14) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1014.14 -proposed tracker (LP: #1956354) * [SRU][J/OEM-5.14] Add an ID of QCOM WCN6855 bluetooth (LP: #1955906) - SAUCE: Bluetooth: btusb: Add support for Foxconn QCA 0xe0d0 * audio mute/ mic mute are not working on a HP machine (LP: #1955691) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * CVE-2021-4090 - NFSD: Fix exposure in nfsd4_decode_bitmap() -- Thadeu Lima de Souza Cascardo Fri, 07 Jan 2022 15:27:13 -0300 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4090 -- 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/1927808 Title: rtw88_8821ce causes freeze Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DK
[Kernel-packages] [Bug 1938104] Re: shiftfs module is not built because CONFIG_SHIFT_FS is not set
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1026.32 --- linux-oem-5.13 (5.13.0-1026.32) focal; urgency=medium [ Ubuntu: 5.13.0-25.26 ] * amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works (LP: #1956401) - drm/amdkfd: fix boot failure when iommu is disabled in Picasso. * OOB write on BPF_RINGBUF (LP: #1956585) - SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other than 0 -- Thadeu Lima de Souza Cascardo Fri, 07 Jan 2022 14:03:28 -0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1938104 Title: shiftfs module is not built because CONFIG_SHIFT_FS is not set Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Bug description: Shiftfs is built and included in all other ubuntu kernels that I know of and if I'm not mistaken is sponsored by ubuntu mostly for use with LXD containers, which is my use case. It also included in the linux- oem-5.10. Is there a reason shiftfs is not included in the 5.13 oem release? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1938104/+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 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1018.19 --- linux-oem-5.14 (5.14.0-1018.19) focal; urgency=medium * OOB write on BPF_RINGBUF (LP: #1956585) - SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other than 0 linux-oem-5.14 (5.14.0-1015.15) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1015.15 -proposed tracker (LP: #1956424) * Support Intel IPU6 MIPI camera on Alder Lake platforms (LP: #1955383) - SAUCE: intel ipu drivers first release - SAUCE: IPU driver release WW48 - SAUCE: IPU driver release WW48 with MCU - SAUCE: IPU driver release WW52 - SAUCE: IPU driver release WW04 - SAUCE: IPU driver release WW14 - SAUCE: Fix ov01a1s output mirror issue - SAUCE: integrate IPU6 builds - [Config] updateconfigs for IPU6 driver - SAUCE: Fix ov01a1s IQ issues - SAUCE: intel/ipu6: Remove unnecessary video devices - SAUCE: change power control driver to acpi driver - SAUCE: IPU6 driver release for kernel 5.13 - SAUCE: sensor HM11b1 brightness bugfix - SAUCE: Fix build error on Kernel 5.13 - SAUCE: IPU6 driver release for kernel 5.14 on 2021-11-01 - [Config] IPU6: enable OV01A10 sensor - SAUCE: intel visual sensing controller(VSC) driver first release - [Config] ivsc: enable Intel VSC drivers - SAUCE: ivsc: return error when device not ready - SAUCE: ivsc: add soft dependencies for intel_vsc module - SAUCE: ljca: switch wait event to uninterruptible - SAUCE: mei-vsc: switch wait event to uninterruptible - SAUCE: mei_vsc: add ACPI HID for ADL - SAUCE: ljca: add multi ACPI HID support - SAUCE: ivsc: add delay for acquire camera to wait firmware ready - SAUCE: mei_vsc: distinguish platform with different camera sensor - SAUCE: i2c-ljca: fix a potential issue - SAUCE: ljca: disable autosuspend by default * Add Bluetooth support for Qualcomm WCN6856 (LP: #1955689) - Revert "UBUNTU: SAUCE: Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller" - Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller - Bluetooth: btusb: re-definition for board_id in struct qca_version - Bluetooth: btusb: Add the new support IDs for WCN6855 * Add basic Wifi support for Qualcomm WCN6856 (LP: #1955613) - bus: mhi: core: Add support for forced PM resume - ath11k: add string type to search board data in board-2.bin for WCN6855 - ath11k: change to use dynamic memory for channel list of scan * rtw88_8821ce causes freeze (LP: #1927808) - rtw88: Disable PCIe ASPM while doing NAPI poll on 8821CE linux-oem-5.14 (5.14.0-1014.14) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1014.14 -proposed tracker (LP: #1956354) * [SRU][J/OEM-5.14] Add an ID of QCOM WCN6855 bluetooth (LP: #1955906) - SAUCE: Bluetooth: btusb: Add support for Foxconn QCA 0xe0d0 * audio mute/ mic mute are not working on a HP machine (LP: #1955691) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * CVE-2021-4090 - NFSD: Fix exposure in nfsd4_decode_bitmap() -- Thadeu Lima de Souza Cascardo Fri, 07 Jan 2022 15:27:13 -0300 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4090 -- 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Incomplete Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware
[Kernel-packages] [Bug 1936295] Re: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1026.32 --- linux-oem-5.13 (5.13.0-1026.32) focal; urgency=medium [ Ubuntu: 5.13.0-25.26 ] * amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works (LP: #1956401) - drm/amdkfd: fix boot failure when iommu is disabled in Picasso. * OOB write on BPF_RINGBUF (LP: #1956585) - SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other than 0 -- Thadeu Lima de Souza Cascardo Fri, 07 Jan 2022 14:03:28 -0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1936295 Title: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate the FW bug Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Bug description: *Problem description:* On Lenovo Thinkpad T14s, X13, A475 (and probably more models) the Elantech Trackpoint firmware is defective. The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. Currently, the Trackpoint is barely usable and it's impossible to productively work using it. For a long while, Elantech has not yet put forward (nor confirmed) a firmware update. However, there is a Linux kernel patch mitigating the firmware bug. The kernel bugfix discards the wrongly reported packages by the Elantech hardware. This solves the problem for the user. *Solution:* Please apply existing kernel patch here. https://bugzilla.kernel.org/show_bug.cgi?id=209167 Bug entry in the Linux Kernel.org Bugzilla https://bugzilla.kernel.org/attachment.cgi?id=295733&action=diff Diff of bugfix *T14s and X13 are Ubuntu certified:* The Lenovo Thinkpad T14s and X13 are Ubuntu certified, but apparently this hardware issue has slipped the Ubuntu certification process! https://ubuntu.com/certified/202006-27978 and https://ubuntu.com/certified/202006-27979 *Further information:* https://forums.lenovo.com/t5/Fedora/T14s-AMD-Trackpoint-almost-unusable/m-p/5064952?page=1 Discussion on the bug in the Lenovo forum. E.g. see comment 18 by Lenovo employee MarkRHPearson *My System:* Lenovo Thinkpad T14s (AMD) 20ujs00k00 Ubuntu 21.04 and 20.04 see entries in kernel.org bugzilla for logs. SRU justification: == [Impact] The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. [Fix] Ignore the buggy data reported by Elan TP firmware, make the TP usable. [Test] Tested on ThinkPad AMD X13 and users confirm on other platforms. [Where problems could occur] It's limited to specific Elan device, it may break the Elan Trackpoint. Jammy already got this commit in Ubuntu-5.15.0-12.12 Phoenix Huang (1): Input: elantench - fix misreporting trackpoint coordinates drivers/input/mouse/elantech.c | 13 + 1 file changed, 13 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936295/+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 1950644] Re: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1026.32 --- linux-oem-5.13 (5.13.0-1026.32) focal; urgency=medium [ Ubuntu: 5.13.0-25.26 ] * amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works (LP: #1956401) - drm/amdkfd: fix boot failure when iommu is disabled in Picasso. * OOB write on BPF_RINGBUF (LP: #1956585) - SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other than 0 -- Thadeu Lima de Souza Cascardo Fri, 07 Jan 2022 14:03:28 -0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Fix Released -- 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/1950644 Title: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Status in linux-azure source package in Trusty: New Status in linux-oem-5.10 source package in Trusty: New Status in linux-oem-5.13 source package in Trusty: New Status in linux-oem-5.14 source package in Trusty: New Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: New Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-azure source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-azure source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-azure source package in Jammy: New Status in linux-oem-5.10 source package in Jammy: Invalid Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Some uses of kernel_read_file_from_fd may lead to a WARN when the file is not opened for reading. The WARNING, however, is not present on earlier kernels, which will return a different error code. The fix, however, has been applied to upstream stable and may be worth so tests can PASS without much change. [Fix/Backport] The fix is trivial, but the backport for Focal and Bionic was picked up from 5.4.y upstream stable tree, because the function was moved to a different file. [Test case] The finit_module02 test case from LTP covers this. [Potential regression] kernel_read_file_from_fd is used for module loading and kexec, so there is where regressions might show up. = ubuntu_ltp / finit_module02 fails on Bionic Azure FIPS (4.15.0-2039.43), Bionic Azure (4.15.0-1127.140), Focal Azure (5.4.0-1064.67): tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+subscriptions -- Mailing list: https:
[Kernel-packages] [Bug 1954646] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1026.32 --- linux-oem-5.13 (5.13.0-1026.32) focal; urgency=medium [ Ubuntu: 5.13.0-25.26 ] * amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works (LP: #1956401) - drm/amdkfd: fix boot failure when iommu is disabled in Picasso. * OOB write on BPF_RINGBUF (LP: #1956585) - SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other than 0 -- Thadeu Lima de Souza Cascardo Fri, 07 Jan 2022 14:03:28 -0300 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Fix Released -- 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/1954646 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus show error "severity=Uncorrected (Non-Fatal)", and failed to probe. [Fix] Re-enable PCIe port LTR after reset or hotplug, and probe it properly. [Test] Verified on HW with TBT4 dock. it works fine. Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine. Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt. [Where problems could occur] PCI bus may break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954646/+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 1956867] Re: BUG: kernel NULL pointer dereference, address: 000000000000000c
*** This bug is a duplicate of bug 1956519 *** https://bugs.launchpad.net/bugs/1956519 Hi Matthew, that was quick! Yes, it appears to be sort of the same issue apart from that where Vadik's machine does not make it through the boot process mine does, but it will fail to shutdown or reboot... Oliver -- 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/1956867 Title: BUG: kernel NULL pointer dereference, address: 000c Status in linux package in Ubuntu: New Bug description: This bug has been introduced with the upgrade of linux- image-5.13.0-22-generic to linux-image-5.13.0-23-generic. One effect - the only one observed so far - is that my system does not reboot or shutdown anymore; a hard power cycle is required to recover for the next system boot. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-23-generic 5.13.0-23.23 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Sun Jan 9 14:15:57 2022 InstallationDate: Installed on 2021-10-08 (92 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: GIGABYTE GB-BRR7H-4800 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=3a66a17e-60e4-4005-864e-410313ceda0d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-08 (62 days ago) dmi.bios.date: 05/05/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: GB-BRR7H-4800 dmi.board.vendor: GIGABYTE dmi.board.version: 1.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:bd05/05/2021:br5.16:svnGIGABYTE:pnGB-BRR7H-4800:pvr1.x:rvnGIGABYTE:rnGB-BRR7H-4800:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:sku01: dmi.product.family: BRIX-00 dmi.product.name: GB-BRR7H-4800 dmi.product.sku: 01 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956867/+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 1956519] Re: kernel panic after upgrading to kernel 5.13.0-23
Hi Matthew, another big thank you from my side for the quick and perfect analysis! Being given the necessary instructions I will be more than happy to test the fixed kernel. Oliver -- 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/1956519 Title: kernel panic after upgrading to kernel 5.13.0-23 Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: In Progress Bug description: After upgrading my son's Asus PN50 with Ubuntu 21.10 to the latest kernel 5.13.0-23, I am no longer able to boot it normally. Kernel fails with the panic halfway through the boot process (which got overall suspiciously slow): [1.359465] BUG: kernel NULL pointer dereference, address: 000c [1.359498] #PF: supervisor write access in kernel mode [1.359519] #PF: error_code(0x0002) - not-present page [1.359540] PGD 0 P4D 0 [1.359553] Oops: 0002 [#1] SMP NOPTI [1.359569] CPU: 0 PID: 175 Comm: systemd-udevd Not tainted 5.13.0-23-generic #23-Ubuntu [1.359602] Hardware name: ASUSTeK COMPUTER INC. MINIPC PN50/PN50, BIOS 0623 05/13/2021 [1.359632] RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh] [1.359661] Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 00 00 00 e8 23 07 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 00 00 48 8d bb 80 01 00 00 48 c7 c6 20 6d [1.359729] RSP: 0018:bf71c099f9d8 EFLAGS: 00010246 [1.359750] RAX: RBX: RCX: [1.359777] RDX: 0020 RSI: c03cd249 RDI: a680004c [1.359804] RBP: bf71c099fa20 R08: R09: 0006 [1.359831] R10: bf71c0d0 R11: 0007 R12: 000fffe0 [1.359857] R13: 992bc3387cd8 R14: 992bc11560c8 R15: 992bc3387cd8 [1.359884] FS: 7ff0ec1a48c0() GS:992ebf60() knlGS: [1.359915] CS: 0010 DS: ES: CR0: 80050033 [1.359937] CR2: 000c CR3: 000102fd CR4: 00350ef0 [1.359964] Call Trace: [1.359976] ? __pci_set_master+0x5f/0xe0 [1.359997] amd_mp2_pci_probe+0xad/0x160 [amd_sfh] [1.360021] local_pci_probe+0x48/0x80 [1.360038] pci_device_probe+0x105/0x1c0 [1.360056] really_probe+0x24b/0x4c0 [1.360073] driver_probe_device+0xf0/0x160 [1.360091] device_driver_attach+0xab/0xb0 [1.360110] __driver_attach+0xb2/0x140 [1.360126] ? device_driver_attach+0xb0/0xb0 [1.360145] bus_for_each_dev+0x7e/0xc0 [1.360161] driver_attach+0x1e/0x20 [1.360177] bus_add_driver+0x135/0x1f0 [1.360194] driver_register+0x95/0xf0 [1.360210] ? 0xc03d2000 [1.360225] __pci_register_driver+0x57/0x60 [1.360242] amd_mp2_pci_driver_init+0x23/0x1000 [amd_sfh] [1.360266] do_one_initcall+0x48/0x1d0 [1.360284] ? kmem_cache_alloc_trace+0xfb/0x240 [1.360306] do_init_module+0x62/0x290 [1.360323] load_module+0xa8f/0xb10 [1.360340] __do_sys_finit_module+0xc2/0x120 [1.360359] __x64_sys_finit_module+0x18/0x20 [1.360377] do_syscall_64+0x61/0xb0 [1.361638] ? ksys_mmap_pgoff+0x135/0x260 [1.362883] ? exit_to_user_mode_prepare+0x37/0xb0 [1.364121] ? syscall_exit_to_user_mode+0x27/0x50 [1.365343] ? __x64_sys_mmap+0x33/0x40 [1.366550] ? do_syscall_64+0x6e/0xb0 [1.367749] ? do_syscall_64+0x6e/0xb0 [1.368923] ? do_syscall_64+0x6e/0xb0 [1.370079] ? syscall_exit_to_user_mode+0x27/0x50 [1.371227] ? do_syscall_64+0x6e/0xb0 [1.372359] ? exc_page_fault+0x8f/0x170 [1.373478] ? asm_exc_page_fault+0x8/0x30 [1.374584] entry_SYSCALL_64_after_hwframe+0x44/0xae [1.375684] RIP: 0033:0x7ff0ec73a94d [1.376767] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 64 0f 00 f7 d8 64 89 01 48 [1.377926] RSP: 002b:7ffd00724ba8 EFLAGS: 0246 ORIG_RAX: 0139 [1.379076] RAX: ffda RBX: 55e130084390 RCX: 7ff0ec73a94d [1.380225] RDX: RSI: 7ff0ec8ca3fe RDI: 0005 [1.381363] RBP: 0002 R08: R09: [1.382488] R10: 0005 R11: 0246 R12: 7ff0ec8ca3fe [1.383598] R13: 55e130083370 R14: 55e130084480 R15: 55e130086cb0 [1.384698] Modules linked in: ahci(+) libahci i2c_piix4(+) r8169(+) amd_sfh(+) i2c_hid_acpi realtek i2c_hid xhci_pci(+) xhci_pci_renesas wmi(+) video(+) fjes(+) hid [1.385841] CR2: 000c [1.386955] ---[ end trace b2ebcacf74b788da ]--- [
[Kernel-packages] [Bug 1933771] Re: Bluetooth headset random disconnects AX200
I'm using Ubuntu 21.10 with firmware 1.201.3 as well. I have the periodic drop out followed by a static corruption. I was hoping it was an issue with the bluetooth dongle I use, so I bought a new bluetooth 5.0 version, but the problem persists. It will be good for hours (sometimes days) and then it will start happening every few minutes. What is the time frame on a fix for this? Is downgrading the firmware the current solution? -- 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/1933771 Title: Bluetooth headset random disconnects AX200 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Hirsute: In Progress Bug description: [Impact] Using several different bluetooth headsets I find that the Bluetooth functionality of the built-in AX200 module of my motherboard keeps randomly disconnecting. I found that this has been fixed in recent Linux firmware updates, but I am not sure that fix has landed yet in Ubuntu Hirsute. Herewith I am posting the link to exactly the issue I am having: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155 And the Linux Firmware commit that resolves this: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180 A related Fedora bug: https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274 It's difficult to relate the upstream kernel version firmware version in which this was fixed (linux-firmware-20210511) to the version of the linux-firmware Ubuntu package (for me). Perhaps someone can comment on whether this has been merged in. I am still experiencing disconnects with 1.197.1 at least. -- Description: Ubuntu 21.04 Release: 21.04 linux-firmware: Installed: 1.197.1 Candidate: 1.197.1 I expected: Bluetooth headset to remain connected What happened: Bluetooth headset connects, then randomly disconnects and reconnects while playing media [Test Case] See above. [Fix] Update AX20x firmware blobs. [Where Problems Could Occur] New firmware blobs so previously working adapter might now fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1956982] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jeff Lane (bladernr) -- 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/1956982 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Please integrate this customer critical/reported fix that was submitted as a stand along patch: Accepted 11/29/21: Applied to 5.16/scsi-fixes, thanks! [1/1] lpfc: Fix nonrecovery of remote ports following an unsolicited LOGO https://git.kernel.org/mkp/scsi/c/0956ba63bd94 As well as this latest set of bug fix patches accepted upstream 12/6/2021: scsi: lpfc: Fix leaked lpfc_dmabuf mbox allocations with NPIV commitf0d3919697492950f57a26a1093aee53880d669d scsi: lpfc: Change return code on I/Os received during link bounce commit2e81b1a374da5d6024208c16c4a5224a70cafa64 scsi: lpfc: Fix lpfc_force_rscn ndlp kref imbalance commit7576d48c64f36f6fea9df2882f710a474fa35f40 scsi: lpfc: Fix NPIV port deletion crash commit8ed190a91950564775cbaae9e8e8083a69a8da23 scsi: lpfc: Trigger SLI4 firmware dump before doing driver cleanup commit7dd2e2a923173d637c272e483966be8e96a72b64 scsi: lpfc: Adjust CMF total bytes and rxmonitor commita6269f837045acb02904f31f05acde847ec8f8a7 scsi: lpfc: Cap CMF read bytes to MBPI commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 scsi: lpfc: Add additional debugfs support for CMF commit6014a2468f0e49194f612b1f09f99eacee0a409a scsi: lpfc: Update lpfc version to 14.0.0.4 commit4437503bfbec2f02b41b2492520fe627715889a7 Extended log info: -cover-letter.patch 0001-lpfc-Fix-leaked-lpfc_dmabuf-mbox-allocations-with-np.patch commitf0d3919697492950f57a26a1093aee53880d669d lpfc: Fix memory leaked lpfc_dmabuf mbox allocations Fix leaked lpfc_dmabuf allocations in an mbox. svn: r82112 bz: 249968 250131 0002-lpfc-Change-return-code-on-ios-received-during-link-.patch commit2e81b1a374da5d6024208c16c4a5224a70cafa64 lpfc: Group RPI_SUSPENDED error action with DID_REQUEUE Fix Medusa IO errors on Scope and Scale LIP test svn: r82348 bz: 247164 250466 Fix Medusa IO errors on Scope and Scale LIP test - build svn: r82377 bz: 247164 250466 0003-lpfc-Fix-lpfc_force_rscn-ndlp-kref-imbalance.patch commit7576d48c64f36f6fea9df2882f710a474fa35f40 lpfc: Fix lpfc_force_rscn ndlp kref imbalance Fix ndlp kref crash during lpfc_force_rscn svn: r82526 bz: 250692 250695 0004-lpfc-Fix-NPIV-port-deletion-crash.patch commit8ed190a91950564775cbaae9e8e8083a69a8da23 lpfc: Fix NPIV port deletion crash Fix crash when deleting a large number of vports. svn: r82120 bz: 240671 250158 Fix a log message formatting error introduced in svn r82120. svn: r82743 bz: 249968 250131 0005-lpfc-Trigger-SLI4-firmware-dump-before-doing-driver-.patch commit7dd2e2a923173d637c272e483966be8e96a72b64 lpfc: Trigger SLI4 firmware dump immediately without delays Trigger SLI4 firmware dump immediately without delays svn: r82770 bz: 250111 251061 0006-lpfc-Adjust-CMF-total-bytes-and-rxmonitor.patch commita6269f837045acb02904f31f05acde847ec8f8a7 lpfc: Adjust CMF total bytes and rxmonitor Adjust CMF total bytes and add to rxmonitor svn: r82429 bz: 250581 250587 0007-lpfc-Cap-CMF-read-bytes-to-MBPI.patch commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 lpfc: Cap CMF read bytes to MBPI Cap CMF read bytes to MBPI only for shortened timer intervals svn: r82483 bz: 250605 251274 0008-lpfc-Add-additional-debugfs-support-for-CMF.patch commit6014a2468f0e49194f612b1f09f99eacee0a409a lpfc: Add additional debugfs support for CMF Add debugfs support for CMF parameters svn: r82144 bz: 250206 250237 Coverity: CID 19805 Fix memory illegal access svn: r82349 bz: 250454 250465 0009-lpfc-Update-lpfc-version-to-14.0.0.4.patch commit4437503bfbec2f02b41b2492520fe627715889a7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956982/+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 1956998] [NEW] kvm SGX numa support
Public bug reported: The basic SGX patches were merged into Qemu release, the left NUMA function for SGX should be enabled. The patch1 implemented the SGX NUMA ACPI to enable NUMA in the SGX guest. Since Libvirt need detailed host SGX EPC sections info to decide how to allocate EPC sections for SGX NUMA guest, the SGXEPCSection list is introduced to show detailed sections info in the monitor or HMP interface. Please help review this patchset, the link also can be found: https://github.com/intel/qemu-sgx upstream Platform: Ice Lake qemu 6.2 110581238 numa: Enable numa for SGX EPC sections 4755927ae numa: Support SGX numa in the monitor and Libvirt interfaces d1889b360 doc: Add the SGX numa description ** 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/1956998 Title: kvm SGX numa support Status in linux package in Ubuntu: New Bug description: The basic SGX patches were merged into Qemu release, the left NUMA function for SGX should be enabled. The patch1 implemented the SGX NUMA ACPI to enable NUMA in the SGX guest. Since Libvirt need detailed host SGX EPC sections info to decide how to allocate EPC sections for SGX NUMA guest, the SGXEPCSection list is introduced to show detailed sections info in the monitor or HMP interface. Please help review this patchset, the link also can be found: https://github.com/intel/qemu-sgx upstream Platform: Ice Lake qemu 6.2 110581238 numa: Enable numa for SGX EPC sections 4755927ae numa: Support SGX numa in the monitor and Libvirt interfaces d1889b360 doc: Add the SGX numa description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956998/+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 1939210] Re: When using HWE, zfs-kmod and zfs user tools versions must match
I see a lot of people somehow subscribed to this bug. But only 17 registered as this bug affects them. Could i politely ask more people to vote for this issue. So it might be noticed before 22.04. Since we need a fix before then or we will live with this for 2 more years in the new LTS. Best regards, Darkyere -- 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/1939210 Title: When using HWE, zfs-kmod and zfs user tools versions must match Status in zfs-linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.2 LTS I ran into a problem recently (https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177) due to mismatched versions when HWE upgraded the kernel from 5.8 to 5.11 where the userspace tools don't match the zfs-kmod version. After the update the system ended up with zfs-0.8.3-1ubuntu12.12 and zfs- kmod-2.0.2-1ubuntu5 My understanding from asking in the OpenZFS github is that the two versions must match. This bug is to figure out what to do for those of us who use HWE and zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210/+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 1956982] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04
Hi Laurie, These do not appear to have even landed in mkp/scsi yet, I don't have a local copy of 5.16/scsi so I'm guessing they are there and will make their way into 5.16 at some point before release? Do you have an ETA on when these should land in 5.16 (either mainline, or linux-next) to give me an idea on when I can look at pulling them? ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1956982 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04 Status in linux package in Ubuntu: Incomplete Bug description: Please integrate this customer critical/reported fix that was submitted as a stand along patch: Accepted 11/29/21: Applied to 5.16/scsi-fixes, thanks! [1/1] lpfc: Fix nonrecovery of remote ports following an unsolicited LOGO https://git.kernel.org/mkp/scsi/c/0956ba63bd94 As well as this latest set of bug fix patches accepted upstream 12/6/2021: scsi: lpfc: Fix leaked lpfc_dmabuf mbox allocations with NPIV commitf0d3919697492950f57a26a1093aee53880d669d scsi: lpfc: Change return code on I/Os received during link bounce commit2e81b1a374da5d6024208c16c4a5224a70cafa64 scsi: lpfc: Fix lpfc_force_rscn ndlp kref imbalance commit7576d48c64f36f6fea9df2882f710a474fa35f40 scsi: lpfc: Fix NPIV port deletion crash commit8ed190a91950564775cbaae9e8e8083a69a8da23 scsi: lpfc: Trigger SLI4 firmware dump before doing driver cleanup commit7dd2e2a923173d637c272e483966be8e96a72b64 scsi: lpfc: Adjust CMF total bytes and rxmonitor commita6269f837045acb02904f31f05acde847ec8f8a7 scsi: lpfc: Cap CMF read bytes to MBPI commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 scsi: lpfc: Add additional debugfs support for CMF commit6014a2468f0e49194f612b1f09f99eacee0a409a scsi: lpfc: Update lpfc version to 14.0.0.4 commit4437503bfbec2f02b41b2492520fe627715889a7 Extended log info: -cover-letter.patch 0001-lpfc-Fix-leaked-lpfc_dmabuf-mbox-allocations-with-np.patch commitf0d3919697492950f57a26a1093aee53880d669d lpfc: Fix memory leaked lpfc_dmabuf mbox allocations Fix leaked lpfc_dmabuf allocations in an mbox. svn: r82112 bz: 249968 250131 0002-lpfc-Change-return-code-on-ios-received-during-link-.patch commit2e81b1a374da5d6024208c16c4a5224a70cafa64 lpfc: Group RPI_SUSPENDED error action with DID_REQUEUE Fix Medusa IO errors on Scope and Scale LIP test svn: r82348 bz: 247164 250466 Fix Medusa IO errors on Scope and Scale LIP test - build svn: r82377 bz: 247164 250466 0003-lpfc-Fix-lpfc_force_rscn-ndlp-kref-imbalance.patch commit7576d48c64f36f6fea9df2882f710a474fa35f40 lpfc: Fix lpfc_force_rscn ndlp kref imbalance Fix ndlp kref crash during lpfc_force_rscn svn: r82526 bz: 250692 250695 0004-lpfc-Fix-NPIV-port-deletion-crash.patch commit8ed190a91950564775cbaae9e8e8083a69a8da23 lpfc: Fix NPIV port deletion crash Fix crash when deleting a large number of vports. svn: r82120 bz: 240671 250158 Fix a log message formatting error introduced in svn r82120. svn: r82743 bz: 249968 250131 0005-lpfc-Trigger-SLI4-firmware-dump-before-doing-driver-.patch commit7dd2e2a923173d637c272e483966be8e96a72b64 lpfc: Trigger SLI4 firmware dump immediately without delays Trigger SLI4 firmware dump immediately without delays svn: r82770 bz: 250111 251061 0006-lpfc-Adjust-CMF-total-bytes-and-rxmonitor.patch commita6269f837045acb02904f31f05acde847ec8f8a7 lpfc: Adjust CMF total bytes and rxmonitor Adjust CMF total bytes and add to rxmonitor svn: r82429 bz: 250581 250587 0007-lpfc-Cap-CMF-read-bytes-to-MBPI.patch commit05116ef9c4b444f7fdbb56f9e13c2ec941726639 lpfc: Cap CMF read bytes to MBPI Cap CMF read bytes to MBPI only for shortened timer intervals svn: r82483 bz: 250605 251274 0008-lpfc-Add-additional-debugfs-support-for-CMF.patch commit6014a2468f0e49194f612b1f09f99eacee0a409a lpfc: Add additional debugfs support for CMF Add debugfs support for CMF parameters svn: r82144 bz: 250206 250237 Coverity: CID 19805 Fix memory illegal access svn: r82349 bz: 250454 250465 0009-lpfc-Update-lpfc-version-to-14.0.0.4.patch commit4437503bfbec2f02b41b2492520fe627715889a7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https:/
[Kernel-packages] [Bug 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
Hi @tjaalton and @vicamo: I tested the 5.14.20 from the mainline as suggested in comment #8, and it FAILED, where as 5.14.21 worked. FAIL 5.14.20-051420-generic "No Bluetooth adapters have been found" I added this to the table in comment #37. -- 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/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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
Re: [Kernel-packages] [Bug 1953689] Re: smartpqi: Update 20.04.4 to latest kernel.org patch level
Just an update, I've had to pull these into both Jammy and Impish (Jammy to avoid regressions since these were pulled from 5.16, so they should land in both 5.13 and 5.15 (22.04). They just got acked this morning. On Thu, Dec 16, 2021 at 5:10 PM Don Brace <1953...@bugs.launchpad.net> wrote: > > I updated the SRU Justification > > ** Description changed: > > SRU Justification: > > Impact: > - > + Update the smartpqi driver with latest kernel.org patches from git repo: > + git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > + > + These patches will align the Canonical smartpqi driver with kernel.org > + > > Fix: > This is targeted at 5.13 for 20.04.4 HWE > > Here is a list of patches that need applied to 20.04.4 to bring the > smartpqi up to date with kernel.org. > > - 64fc9015fbeb scsi: smartpqi: Switch to attribute groups > - 0ca190805784 scsi: smartpqi: Call scsi_done() directly > + > 605ae389ea02 scsi: smartpqi: Update version to 2.1.12-055 > 80982656b78e scsi: smartpqi: Add 3252-8i PCI id > d4dc6aea93cb scsi: smartpqi: Fix duplicate device nodes for tape changers > 987d35605b7e scsi: smartpqi: Fix boot failure during LUN rebuild > 28ca6d876c5a scsi: smartpqi: Add extended report physical LUNs > 4f3cefc3084d scsi: smartpqi: Avoid failing I/Os for offline devices > be76f90668d8 scsi: smartpqi: Add TEST UNIT READY check for SANITIZE > operation > 6ce1ddf53252 scsi: smartpqi: Update LUN reset handler > 5d1f03e6f49a scsi: smartpqi: Capture controller reason codes > 9ee5d6e9ac52 scsi: smartpqi: Add controller handshake during kdump > 819225b03dc7 scsi: smartpqi: Update device removal management > 5f492a7aa13b scsi: smartpqi: Replace one-element array with flexible-array > member > > These patches should all be upstream as of 5.16. > > Testcase: > - > + kdump tests. > + fio performance testing to demonstrate no performance regressions. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1953689 > > Title: > smartpqi: Update 20.04.4 to latest kernel.org patch level > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > SRU Justification: > > Impact: > Update the smartpqi driver with latest kernel.org patches from git repo: > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > These patches will align the Canonical smartpqi driver with kernel.org > > > Fix: > This is targeted at 5.13 for 20.04.4 HWE > > Here is a list of patches that need applied to 20.04.4 to bring the > smartpqi up to date with kernel.org. > > > 605ae389ea02 scsi: smartpqi: Update version to 2.1.12-055 > 80982656b78e scsi: smartpqi: Add 3252-8i PCI id > d4dc6aea93cb scsi: smartpqi: Fix duplicate device nodes for tape changers > 987d35605b7e scsi: smartpqi: Fix boot failure during LUN rebuild > 28ca6d876c5a scsi: smartpqi: Add extended report physical LUNs > 4f3cefc3084d scsi: smartpqi: Avoid failing I/Os for offline devices > be76f90668d8 scsi: smartpqi: Add TEST UNIT READY check for SANITIZE > operation > 6ce1ddf53252 scsi: smartpqi: Update LUN reset handler > 5d1f03e6f49a scsi: smartpqi: Capture controller reason codes > 9ee5d6e9ac52 scsi: smartpqi: Add controller handshake during kdump > 819225b03dc7 scsi: smartpqi: Update device removal management > 5f492a7aa13b scsi: smartpqi: Replace one-element array with flexible-array > member > > These patches should all be upstream as of 5.16. > > Testcase: > kdump tests. > fio performance testing to demonstrate no performance regressions. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953689/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main; > status=Incomplete; importance=Undecided; assignee=jeffrey.l...@canonical.com; > Launchpad-Bug-Tags: smartpqi > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: bladernr bracedon ubuntu-kernel-bot > Launchpad-Bug-Reporter: Don Brace (bracedon) > Launchpad-Bug-Modifier: Don Brace (bracedon) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: bladernr > -- Jeff Lane Engineering Manager IHV/OEM Alliances and Server Certification "Entropy isn't what it used to be." -- 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/1953689 Title: smartpqi: Update 20.04.4 to latest kernel.org patch level Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: Impact: Update the smartpqi driver with latest kernel.org patches from git repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git These patches will align the Canonical smartpqi driver with kernel.o
[Kernel-packages] [Bug 1957005] [NEW] keyboard and touchpad stopped working
Public bug reported: Onboard Keyboard and touchpad stopped working, but I notice that the Brightness controls (FN+F2/F3) still work. External USB keyboard and mouse work properly. luca@luca-SATELLITE-L850-1PD:~$ uname -a Linux luca-SATELLITE-L850-1PD 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-44-generic 5.11.0-44.48~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 10 21:27:14 2022 InstallationDate: Installed on 2020-05-26 (594 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "/proc/bus/input/devices" https://bugs.launchpad.net/bugs/1957005/+attachment/5553150/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1957005 Title: keyboard and touchpad stopped working Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Onboard Keyboard and touchpad stopped working, but I notice that the Brightness controls (FN+F2/F3) still work. External USB keyboard and mouse work properly. luca@luca-SATELLITE-L850-1PD:~$ uname -a Linux luca-SATELLITE-L850-1PD 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-44-generic 5.11.0-44.48~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 10 21:27:14 2022 InstallationDate: Installed on 2020-05-26 (594 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1957005/+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 1956882] Re: Ubuntu does not boot after upgrade to Linux 5.13-0-23
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956882 Title: Ubuntu does not boot after upgrade to Linux 5.13-0-23 Status in linux package in Ubuntu: Confirmed Bug description: After the latest upgrade to Linux 5.13.0-23 the disk shows some activity, but the screen remains black and powers off. To be sure I reinstalled Ubuntu from scratch and I have the same error again. My hardware is a Ryzen 3 2200G I only can boot from Linux 5.13.0-19. On the precious installation I could reboot from Linux 5.13.0-22, but -23 failed. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 9 16:11:04 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-09 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956882/+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 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
I was surprised to find a 5.14.0-1018 upgrade just a few minutes ago. I installed and tested; it FAILED, and I have updated the table in comment #37 as well. -- 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/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1951111] Re: [Jammy] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.3 for Ubuntu 22.04
** 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/195 Title: [Jammy] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.3 for Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: The purpose of this bug is to track the incremental patches needed in Ubuntu 22.04 for the Broadcom Emulex FC HBA lpfc driver that are committed to the 5.16 upstream kernel and not part of the 5.15 kernel that 22.04 is rebased to. Please integrate the following patches from the 5.16 kernel per James Smart the lpfc maintainter. James Smart Fri, Nov 12, 2:31 PM (4 days ago) to me, Dick, Justin, Teresa I would argue to take all of the patches in the following list (14.0.0.2 & 14.0.0.3 & a mbx cmd failure issue) -- james Applied to 5.16/scsi-queue, thanks! [1/8] lpfc: Revert LOG_TRACE_EVENT back to LOG_INIT prior to driver_resource_setup https://git.kernel.org/mkp/scsi/c/a516074c2026 [2/8] lpfc: Wait for successful restart of SLI3 adapter during host sg_reset https://git.kernel.org/mkp/scsi/c/d305c253af69 [3/8] lpfc: Correct sysfs reporting of loop support after SFP status change https://git.kernel.org/mkp/scsi/c/7a1dda943630 [4/8] lpfc: Fix use-after-free in lpfc_unreg_rpi() routine https://git.kernel.org/mkp/scsi/c/79b20beccea3 [5/8] lpfc: Allow PLOGI retry if previous PLOGI was aborted https://git.kernel.org/mkp/scsi/c/15af02d8a585 [6/8] lpfc: Fix link down processing to address NULL pointer dereference https://git.kernel.org/mkp/scsi/c/1854f53ccd88 [7/8] lpfc: Allow fabric node recovery if recovery is in progress before devloss https://git.kernel.org/mkp/scsi/c/af984c87293b [8/8] lpfc: Update lpfc version to 14.0.0.3 https://git.kernel.org/mkp/scsi/c/83c3a7beaef7 Applied to 5.16/scsi-queue, thanks! [1/1] lpfc: Fix mailbox command failure during driver initialization https://git.kernel.org/mkp/scsi/c/efe1dc571a5b Applied to 5.16/scsi-queue, thanks! [01/14] lpfc: Fix list_add corruption in lpfc_drain_txq https://git.kernel.org/mkp/scsi/c/99154581b05c [02/14] lpfc: Don't release final kref on Fport node while ABTS outstanding https://git.kernel.org/mkp/scsi/c/982fc3965d13 [03/14] lpfc: Fix premature rpi release for unsolicited TPLS and LS_RJT https://git.kernel.org/mkp/scsi/c/20d2279f90ce [04/14] lpfc: Fix hang on unload due to stuck fport node https://git.kernel.org/mkp/scsi/c/88f7702984e6 [05/14] lpfc: Fix rediscovery of tape device after issue lip https://git.kernel.org/mkp/scsi/c/3a874488d2e9 [06/14] lpfc: Don't remove ndlp on PRLI errors in P2P mode https://git.kernel.org/mkp/scsi/c/a864ee709bc0 [07/14] lpfc: Fix NVME I/O failover to non-optimized path https://git.kernel.org/mkp/scsi/c/b507357f7917 [08/14] lpfc: Fix FCP I/O flush functionality for TMF routines https://git.kernel.org/mkp/scsi/c/cd8a36a90bab [09/14] lpfc: Fix EEH support for NVME I/O https://git.kernel.org/mkp/scsi/c/25ac2c970be3 [10/14] lpfc: Adjust bytes received vales during cmf timer interval https://git.kernel.org/mkp/scsi/c/d5ac69b332d8 [11/14] lpfc: Fix I/O block after enabling managed congestion mode https://git.kernel.org/mkp/scsi/c/3ea998cbf9e7 [12/14] lpfc: Zero CGN stats only during initial driver load and stat reset https://git.kernel.org/mkp/scsi/c/afd63fa51149 [13/14] lpfc: Improve PBDE checks during SGL processing https://git.kernel.org/mkp/scsi/c/315b3fd13521 [14/14] lpfc: Update lpfc version to 14.0.0.2 https://git.kernel.org/mkp/scsi/c/0d6b26795bd2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+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 1957007] [NEW] Focal update: v5.4.165 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.4.165 upstream stable release
from git://git.kernel.org/
serial: tegra: Change lower tolerance baud rate limit for tegra20 and tegra30
ntfs: fix ntfs_test_inode and ntfs_init_locked_inode function type
HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
HID: google: add eel USB id
HID: add hid_is_usb() function to make it simpler for USB detection
HID: add USB_HID dependancy to hid-prodikeys
HID: add USB_HID dependancy to hid-chicony
HID: add USB_HID dependancy on some USB HID drivers
HID: bigbenff: prevent null pointer dereference
HID: wacom: fix problems when device is not a valid USB device
HID: check for valid USB device for many HID drivers
can: kvaser_usb: get CAN clock frequency from device
can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
stats->{rx,tx}_errors counter
can: sja1000: fix use after free in ems_pcmcia_add_card()
nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
selftests: netfilter: add a vrf+conntrack testcase
vrf: don't run conntrack on vrf with !dflt qdisc
bpf: Fix the off-by-two error in range markings
ice: ignore dropped packets during init
bonding: make tx_rebalance_counter an atomic
nfp: Fix memory leak in nfp_cpp_area_cache_add()
seg6: fix the iif in the IPv6 socket control block
udp: using datalen to cap max gso segments
iavf: restore MSI state on reset
iavf: Fix reporting when setting descriptor count
IB/hfi1: Correct guard on eager buffer deallocation
mm: bdi: initialize bdi_min_ratio when bdi is unregistered
ALSA: ctl: Fix copy of updated id with element read/write
ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
ALSA: pcm: oss: Fix negative period/buffer sizes
ALSA: pcm: oss: Limit the period size to 16MB
ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
btrfs: clear extent buffer uptodate when we fail to write it
btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
nfsd: Fix nsfd startup race (again)
tracefs: Have new files inherit the ownership of their parent
clk: qcom: regmap-mux: fix parent clock lookup
drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
can: pch_can: pch_can_rx_normal: fix use after free
can: m_can: Disable and ignore ELO interrupt
x86/sme: Explicitly map new EFI memmap table as encrypted
libata: add horkage for ASMedia 1092
wait: add wake_up_pollfree()
UBUNTU: SAUCE: binder: export __wake_up_pollfree for binder module
binder: use wake_up_pollfree()
signalfd: use wake_up_pollfree()
aio: keep poll requests on waitqueue until completed
aio: fix use-after-free due to missing POLLFREE handling
tracefs: Set all files to the same group ownership as the mount option
block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
qede: validate non LSO skb length
ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
i40e: Fix failed opcode appearing if handling messages from VF
i40e: Fix pre-set max number of queues for VF
mtd: rawnand: fsmc: Take instruction delay into account
mtd: rawnand: fsmc: Fix timing computation
dt-bindings: net: Reintroduce PHY no lane swap binding
tools build: Remove needless libpython-version feature check that breaks
test-all fast path
net: cdc_ncm: Allow for dwNtbOutMaxSize to be unset or zero
net: altera: set a couple error code in probe()
net: fec: only clear interrupt of handling queue in fec_enet_rx_queue()
net, neigh: clear whole pneigh_entry at alloc time
net/qla3xxx: fix an error code in ql_adapter_up()
Revert "UBUNTU: SAUCE: selftests: fib_tests: assign address to dummy1 for
rp_filter tests"
selftests/fib_tests: Rework fib_rp_filter_test()
USB: gadget: detect too-big endpoint 0 requests
USB: gadget: zero allocate endpoint 0 buffers
usb: core: config: fix validation of wMaxPacketValue entries
xhci: Remove CONFIG_USB_DEFAULT_PERSIST to prevent xHCI from runtime suspending
usb: core: config: using bit mask instead of individual bits
xhci: avoid race between disable slot command and host runtime suspend
iio: trigger: Fix reference counting
iio: trigger: stm32-timer: fix MODULE_ALIAS
iio: stk3310: Don't return error code in interrupt handler
iio: mma8452: Fix trigger reference couting
iio: ltr501: Don't return error code in trigger handler
iio: kxsd9: Don't return error code in trigger handler
iio: itg3200: Call iio_trigger_notify_done() on error
iio: dln2-adc: Fix lockdep complaint
iio: dln2: Check return value of devm_iio_trigger_register()
iio: at91-sama5d2: Fix incorrect sign extension
iio: adc: axp20x_adc: fix ch
[Kernel-packages] [Bug 1957008] [NEW] Focal update: v5.4.166 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.4.166 upstream stable release from git://git.kernel.org/ netfilter: selftest: conntrack_vrf.sh: fix file permission Linux 5.4.166 UBUNTU: upstream stable to v5.4.166 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.166 upstream stable release + from git://git.kernel.org/ -v5.4.166 upstream stable release -from git://git.kernel.org/ + netfilter: selftest: conntrack_vrf.sh: fix file permission + Linux 5.4.166 + UBUNTU: upstream stable to v5.4.166 -- 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/1957008 Title: Focal update: v5.4.166 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: 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.4.166 upstream stable release from git://git.kernel.org/ netfilter: selftest: conntrack_vrf.sh: fix file permission Linux 5.4.166 UBUNTU: upstream stable to v5.4.166 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957008/+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 1956518] Re: linux-firmware 1.187.24 may crash USB ports
apport information ** Tags added: apport-collected focal ** Description changed: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: alvaro 2225 F pulseaudio + /dev/snd/controlC0: alvaro 2225 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + Dependencies: + + DistroRelease: Ubuntu 20.04 + HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a + InstallationDate: Installed on 2014-10-25 (2634 days ago) + InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) + IwConfig: + lono wireless extensions. + + enp7s0no wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. B365M H + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux-firmware 1.187.24 + PackageArchitecture: all + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=es_ES.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-92-generic N/A + linux-backports-modules-5.4.0-92-generic N/A + linux-firmware1.187.24 + RfKill: + 2: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: focal + Uname: Linux 5.4.0-92-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) + UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video + _MarkForUpload: True + dmi.bios.date: 08/18/2020 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F4b + dmi.board.asset.tag: Default string + dmi.board.name: B365M H + 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: Default string + dmi.product.name: B365M H + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553160/+files/AlsaInfo.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS
[Kernel-packages] [Bug 1956518] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553163/+files/Lspci.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1956518] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553165/+files/Lsusb.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1956518] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553167/+files/Lsusb-v.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1956518] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553164/+files/Lspci-vt.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1956518] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553168/+files/ProcCpuinfo.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1956518] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553166/+files/Lsusb-t.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1956518] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553162/+files/CurrentDmesg.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1956518] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553161/+files/CRDA.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1956518] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553169/+files/ProcCpuinfoMinimal.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1956518] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553170/+files/ProcInterrupts.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1956518] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553174/+files/WifiSyslog.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1956518] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553172/+files/PulseList.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1956518] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553173/+files/UdevDb.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1956518] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553171/+files/ProcModules.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1956518] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1956518/+attachment/5553175/+files/acpidump.txt -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+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 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
** Also affects: kunpeng920/ubuntu-21.10 Importance: Undecided Status: New ** Also 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/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in kunpeng920 ubuntu-21.10 series: New Status in linux package in Ubuntu: New Status in linux source package in Impish: New Status in linux source package in Jammy: New Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+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 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) 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/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in kunpeng920 ubuntu-21.10 series: New Status in linux package in Ubuntu: New Status in linux source package in Impish: New Status in linux source package in Jammy: New Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+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
