[Kernel-packages] [Bug 1968519] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1968519 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968519 Title: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04 Status in linux package in Ubuntu: Incomplete Bug description: Description: When we install Ubuntu 22.04, the physical VGA displayer show black screen. It can only show rarely boot logs just for few seconds after kebyboard Enter key be pressed to install Ubuntu OS, and then the physical VGA displayer keeps black screen, but the XCC remote KVM monitor can show the boot log and the GUI interface. Produce Steps: 1. Connect a physical VGA displayer. 2. Fresh install Ubuntu22.04 on a server that integrated Matrox MGA G200-family. 3. When the install menu comes out, press keyboard Enter key, the physical VGA displayer just get the signal for few seconds and then the monitor go to black screen. Configuration: Systems：Lenovo SR590, SR650, SR630 with magag200 as GFX OS:jammy-live-server20220405-amd64.iso CPU:Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz UEFI:3.30 (Build ID: IVE178D) XCC:1.30 (Build ID: PDL114N) HDD:1.00TB 7.2K 6Gbps SATA 3.5" HD Actual results: The VGA display keep the black screen, during Ubuntu 22.04 installation. Expected results: The VGA display is OK when install the Ubuntu 22.04 in a server that integrated Matrox MGA G200-family video processor Additional info: 1. The issue can be reproduced 100% in the server that integrated Matrox MGA G200-family platforms. 2. Both UEFI mode and legacy mode are failed. 3. After we finish installing Ubuntu OS through XCC remote KVM monitor, and reboot the system, the physical VGA displayer still show nothing after a few seconds. 4. We did more tests, modified the cmdline of the kernel, add "nomodeset", the VGA displayer display well. 5. This issue could be found on both Intel and AMD platforms , which have onboard video chip as mgag200, also called pilot 4. 6. Upstream kernel patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc1=147696720eca12ae48d020726208b9a61cdd80bc (drm/mgag200: Select clock in PLL update functions) probalby resovle the issue on BIOS legacy mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968519/+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 1968519] [NEW] [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04
Public bug reported: Description: When we install Ubuntu 22.04, the physical VGA displayer show black screen. It can only show rarely boot logs just for few seconds after kebyboard Enter key be pressed to install Ubuntu OS, and then the physical VGA displayer keeps black screen, but the XCC remote KVM monitor can show the boot log and the GUI interface. Produce Steps: 1. Connect a physical VGA displayer. 2. Fresh install Ubuntu22.04 on a server that integrated Matrox MGA G200-family. 3. When the install menu comes out, press keyboard Enter key, the physical VGA displayer just get the signal for few seconds and then the monitor go to black screen. Configuration: Systems：Lenovo SR590, SR650, SR630 with magag200 as GFX OS:jammy-live-server20220405-amd64.iso CPU:Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz UEFI:3.30 (Build ID: IVE178D) XCC:1.30 (Build ID: PDL114N) HDD:1.00TB 7.2K 6Gbps SATA 3.5" HD Actual results: The VGA display keep the black screen, during Ubuntu 22.04 installation. Expected results: The VGA display is OK when install the Ubuntu 22.04 in a server that integrated Matrox MGA G200-family video processor Additional info: 1. The issue can be reproduced 100% in the server that integrated Matrox MGA G200-family platforms. 2. Both UEFI mode and legacy mode are failed. 3. After we finish installing Ubuntu OS through XCC remote KVM monitor, and reboot the system, the physical VGA displayer still show nothing after a few seconds. 4. We did more tests, modified the cmdline of the kernel, add "nomodeset", the VGA displayer display well. 5. This issue could be found on both Intel and AMD platforms , which have onboard video chip as mgag200, also called pilot 4. 6. Upstream kernel patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc1=147696720eca12ae48d020726208b9a61cdd80bc (drm/mgag200: Select clock in PLL update functions) probalby resovle the issue on BIOS legacy mode. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1968519 Title: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04 Status in linux package in Ubuntu: Incomplete Bug description: Description: When we install Ubuntu 22.04, the physical VGA displayer show black screen. It can only show rarely boot logs just for few seconds after kebyboard Enter key be pressed to install Ubuntu OS, and then the physical VGA displayer keeps black screen, but the XCC remote KVM monitor can show the boot log and the GUI interface. Produce Steps: 1. Connect a physical VGA displayer. 2. Fresh install Ubuntu22.04 on a server that integrated Matrox MGA G200-family. 3. When the install menu comes out, press keyboard Enter key, the physical VGA displayer just get the signal for few seconds and then the monitor go to black screen. Configuration: Systems：Lenovo SR590, SR650, SR630 with magag200 as GFX OS:jammy-live-server20220405-amd64.iso CPU:Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz UEFI:3.30 (Build ID: IVE178D) XCC:1.30 (Build ID: PDL114N) HDD:1.00TB 7.2K 6Gbps SATA 3.5" HD Actual results: The VGA display keep the black screen, during Ubuntu 22.04 installation. Expected results: The VGA display is OK when install the Ubuntu 22.04 in a server that integrated Matrox MGA G200-family video processor Additional info: 1. The issue can be reproduced 100% in the server that integrated Matrox MGA G200-family platforms. 2. Both UEFI mode and legacy mode are failed. 3. After we finish installing Ubuntu OS through XCC remote KVM monitor, and reboot the system, the physical VGA displayer still show nothing after a few seconds. 4. We did more tests, modified the cmdline of the kernel, add "nomodeset", the VGA displayer display well. 5. This issue could be found on both Intel and AMD platforms , which have onboard video chip as mgag200, also called pilot 4. 6. Upstream kernel patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc1=147696720eca12ae48d020726208b9a61cdd80bc (drm/mgag200: Select clock in PLL update functions) probalby resovle the issue on BIOS legacy mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968519/+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 1950778] Re: Ubuntu 20.04.3 generates IO error message during FIO stress.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1950778 Title: Ubuntu 20.04.3 generates IO error message during FIO stress. Status in linux package in Ubuntu: Expired Bug description: With fio stress on Powerstore fcoe drives (lun) attached by using Qlogic QL41000 series controller, ubuntu 20.04.3 on MX740c blade server generates below mentioned i/o errors. Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1523]:13: Error detection CQE, xid=0x7bd Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1525]:13: err_warn_bitmap=0040: Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1529]:13: tx_buff_off=, rx_buff_off=, rx_id=041b Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1523]:3: Error detection CQE, xid=0x34d Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1525]:3: err_warn_bitmap=0040: Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1529]:3: tx_buff_off=, rx_buff_off=, rx_id=01f7 Steps to reproduce. 1. Configure QL41000 series controller on MX MX740c blade server. 2. Configure APM3246 array directly connected to chassis module MX9116n. 3. Install Ubuntu 20.04.3 in any local drive. 4. start I/O by using fio : # fio FileSystemCreateSingle/fio_test.cfg then we can observe error message in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950778/+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 1959514] Re: USB keyboard / mouse not powered on after boot
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1959514 Title: USB keyboard / mouse not powered on after boot Status in linux package in Ubuntu: Expired Bug description: I use two monitors with USB hub feature. My keyboard and mouse are plugged into one of those monitors. After Ubuntu boots, the keyboard and the mouse are dead. I have to unplug the monitor's USB cable from the computer and plug it back in, then the keyboard and the mouse are detected and powered on. This happens in Ubuntu consistently, with all recent kernel updates. Never happens in Fedora 35 or Windows 11 on same hardware (i.e. the keyboard and the mouse are immediately usable after boot). Ubuntu version: 21.10 Kernel version: 5.13.0-27-generic Happened with earlier kernel versions too. The output of dmesg and lsusb is attached. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kman 2223 F pulseaudio /dev/snd/controlC1: kman 2223 F pulseaudio /dev/snd/controlC2: kman 2223 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-03-14 (696 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: ASUS System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: ro root=UUID=fb4dae8c-3c06-494a-b0b1-bdf6404d8d04 nvidia-drm.modeset=1 quiet splash LANG=en_US.UTF-8 initrd=boot\initrd.img-5.13.0-28-generic ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-10 (122 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/02/2021 dmi.bios.release: 20.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd11/02/2021:br20.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959514/+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 1968402] Re: Ubuntu 20.04.3 boots to black screen, no TTY available
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1968402 Title: Ubuntu 20.04.3 boots to black screen, no TTY available Status in gdm: New Status in gnome-session: New Status in grub: New Status in os-prober-efi/trunk: New Status in shim: New Status in subiquity: New Status in tty: New Status in grub2 package in Ubuntu: New Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-450 package in Ubuntu: New Status in wayland package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: A fresh attempted install failed utterly, just as 20.04.1 failed two years ago. Has anyone been paying attention? Ubuntu 20.04.3 burned just now to a USB stick and attempted to be installed. The first fail was that the stick booted to a couple of impenetrable boot-time messages and hung. Really. I'm not making this up. It didn't just open the installer, as it should. The second fail was having just to guess that rebooting and trying another GRUB menu option might work and give that a try. Really. I'm not making this up, either. The installer was entirely incapable of providing any direction The third failure was that the installer was incapable of detecting the video configuration and proceeding accordingly. This is 20.04.3, the third attempt at getting this right, and it still fails. The fourth fail was an error message insisting on a designation of where root should be, even after the destination partition already had been specified. The fifth failure was that no obvious means existed to satisfy the installer about the root specification, which of course already had been made by specifying the destination partition. All one could do was to see whether a context menu existed for any object on the screen that might possibly drill down through a few layers to something approximating what the content of the error message suggested. The sixth failure was that no GRUB menu appeared during boot, notwithstanding that the EFI system partition had clearly been identified in the installer. The seventh failure was that the machine booted only to a black screen with a non-blinking _ midway toward the upper left. No login screen/display manager. No GUI at all. Just this little _. The eighth failure was that Ctrl-alt-f2, ctrl-alt-f5-f12 have no effect. No TTY is available. There is no way whatsoever to interact with the system. Expected behavior: The software would install and the computer would work. Actual behavior: The installer bricked my workstation. Obviously, no debug information is available BECAUSE THE SOFTWARE FAILED. This post is being made from a borrowed Windows laptop. Any thoughts about how to get a working system would be appreciated. I am not optimistic about the prospects for 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1968402/+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 1963835] Re: Message: "Error! Arguments and are not specified." when upgrading
** Changed in: dkms (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1963835 Title: Message: "Error! Arguments and are not specified." when upgrading Status in dkms package in Ubuntu: Fix Released Status in dkms package in Debian: Fix Released Bug description: Running pre-release Xubuntu 22.04. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy Linux willem-Aspire-A315-53 5.15.0-18-generic #18-Ubuntu SMP Fri Jan 21 14:57:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux After upgrading from 21.04 tot 22.04 I did: sudo apt update && sudo apt full-upgrade I saw this message in the output: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v All the output: willem@willem-Aspire-A315-53:~$ sudo apt update && sudo apt full-upgrade [sudo] wachtwoord voor willem: Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. 0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd. Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. De volgende pakketten zullen VERWIJDERD worden: linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic 0 opgewaardeerd, 0 nieuw geïnstalleerd, 4 te verwijderen en 0 niet opgewaardeerd. Na deze bewerking zal er 428 MB schijfruimte vrijkomen. Wilt u doorgaan? [J/n] (Database wordt ingelezen ... 402831 bestanden en mappen momenteel geïnstalleerd .) linux-headers-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-extra-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-image-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ..] /etc/kernel/prerm.d/dkms: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.13.0-30-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-18-generic Found initrd image: /boot/initrd.img-5.15.0-18-generic Found linux image: /boot/vmlinuz-5.13.0-32-generic Found initrd image: /boot/initrd.img-5.13.0-32-generic Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found Ubuntu 21.10 (21.10) on /dev/sda2 Found Zorin OS 16 (16) on /dev/sda5 Adding boot menu entry for UEFI Firmware Settings ... done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1963835/+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 1968499] [NEW] CPU spikes from touchpad interrupt even if deactivated
Public bug reported: Since upgrade to kernel 5.15 I have problems with irq/204-rmi4_sm which fires extreme CPU spike (10-20% shown in top) if the touchpad of my Lenovo Thinkpad Extreme is touched in any way. The touchpad is disabled in BIOS as well as in X configuration. Unfortunately I can not easily step back to prior kernel for testing since the upgrade was done in a release migration towards 22.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-lowlatency 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-lowlatency 5.15.27 Uname: Linux 5.15.0-23-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Apr 10 21:41:53 2022 InstallationDate: Installed on 2019-12-19 (843 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-lowlatency UpgradeStatus: Upgraded to jammy on 2022-04-07 (3 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-04-09T11:41:02.383904 ** Affects: linux-signed-lowlatency (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/1968499 Title: CPU spikes from touchpad interrupt even if deactivated Status in linux-signed-lowlatency package in Ubuntu: New Bug description: Since upgrade to kernel 5.15 I have problems with irq/204-rmi4_sm which fires extreme CPU spike (10-20% shown in top) if the touchpad of my Lenovo Thinkpad Extreme is touched in any way. The touchpad is disabled in BIOS as well as in X configuration. Unfortunately I can not easily step back to prior kernel for testing since the upgrade was done in a release migration towards 22.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-lowlatency 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-lowlatency 5.15.27 Uname: Linux 5.15.0-23-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Apr 10 21:41:53 2022 InstallationDate: Installed on 2019-12-19 (843 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-lowlatency UpgradeStatus: Upgraded to jammy on 2022-04-07 (3 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-04-09T11:41:02.383904 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/1968499/+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 1968480] Re: kernel: usb_set_interface failed (-113)
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968480 Title: kernel: usb_set_interface failed (-113) Status in linux package in Ubuntu: Invalid Bug description: My webcam ID 046d:0826 Logitech, Inc. HD Webcam C525 has always worked well with Ubuntu. But after some update on 21.10, the microphone recording from the webcam stopped working. The recording starts working if you replug usb or make usbreset. On ubuntu 22.04 bug is still present. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: navycat1738 F pulseaudio /dev/snd/controlC2: navycat1738 F pulseaudio /dev/snd/controlC1: navycat1738 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Apr 10 17:45:35 2022 InstallationDate: Installed on 2022-04-09 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220407) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=96b12ce3-6254-469d-af5e-611471d8887a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:skuPROJECT_SUB_TAG: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968480/+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 1968483] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968483 Title: 22.04 beta live cd hangs Status in linux package in Ubuntu: Confirmed Bug description: Thinkpad t510. Create live CD and then boot. Shortly after desktop launched the session hangs due to the intel_iommu being set to on. If I change boot line to intel_iommu=off the live session works correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob 20717 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Sun Apr 10 08:28:37 2022 MachineType: LENOVO 4384AJ9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=fee8c01f-ad0a-4c46-a956-7d692183fffc ro quiet splash intel_iommu=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.release: 1.82 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET92WW (1.52 ) dmi.board.name: 4384AJ9 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:br1.82:efr1.33:svnLENOVO:pn4384AJ9:pvrThinkPadT510:rvnLENOVO:rn4384AJ9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T510 dmi.product.name: 4384AJ9 dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968483/+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 1968483] [NEW] 22.04 beta live cd hangs
Public bug reported: Thinkpad t510. Create live CD and then boot. Shortly after desktop launched the session hangs due to the intel_iommu being set to on. If I change boot line to intel_iommu=off the live session works correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob 20717 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Sun Apr 10 08:28:37 2022 MachineType: LENOVO 4384AJ9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=fee8c01f-ad0a-4c46-a956-7d692183fffc ro quiet splash intel_iommu=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.release: 1.82 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET92WW (1.52 ) dmi.board.name: 4384AJ9 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:br1.82:efr1.33:svnLENOVO:pn4384AJ9:pvrThinkPadT510:rvnLENOVO:rn4384AJ9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T510 dmi.product.name: 4384AJ9 dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1968483 Title: 22.04 beta live cd hangs Status in linux package in Ubuntu: New Bug description: Thinkpad t510. Create live CD and then boot. Shortly after desktop launched the session hangs due to the intel_iommu being set to on. If I change boot line to intel_iommu=off the live session works correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob 20717 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Sun Apr 10 08:28:37 2022 MachineType: LENOVO 4384AJ9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=fee8c01f-ad0a-4c46-a956-7d692183fffc ro quiet splash intel_iommu=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.release: 1.82 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET92WW (1.52 ) dmi.board.name: 4384AJ9 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:br1.82:efr1.33:svnLENOVO:pn4384AJ9:pvrThinkPadT510:rvnLENOVO:rn4384AJ9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T510 dmi.product.name: 4384AJ9 dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968483/+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 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
I applied same test plan on 5.15.0-25-generic with and without the feature patchset on CX6-dx. In both cases the test kernel had the the problematic patch from (bug https://bugs.launchpad.net/bugs/1967754) reverted. I got the exact same results as in comment #6 so the patch set does not introduce a degradation. -- 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/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Add support for software steering on cx7 [Test Case] configure software steering on cx7 setup run asap testing (reference https://github.com/Mellanox/ovs-tests) [Regression Potential] TBD [Other Info] Feature patchset: All patches are cleanly applied on Jamy master-next beside these two who add minor conflicts due to context difference. net/mlx5: Introduce software defined steering capabilities net/mlx5: DR, Add support for matching on #fixes 624bf42c2e39 net/mlx5: DR, Fix querying eswitch manager vport for ECPF 0aec12d97b20 net/mlx5: DR, Fix slab-out-of-bounds in mlx5_cmd_dr_create_fte 9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately #CX7 SMFS support 6862c787c7e8 net/mlx5: DR, Add support for ConnectX-7 steering 638a07f1090e net/mlx5: DR, Refactor ste_ctx handling for STE v0/1 75a3926ca6a4 net/mlx5: DR, Rename action modify fields to reflect naming in HW spec bdc3ab5795a6 net/mlx5: DR, Fix handling of different actions on the same STE in STEv1 11659ef8d28e net/mlx5: DR, Remove unneeded comments 5c422bfad2fb net/mlx5: DR, Add support for matching on Internet Header Length (IHL) #dependencies: 60dc0ef674ec net/mlx5: VLAN push on RX, pop on TX 8348b71ccd92 net/mlx5: Introduce software defined steering capabilities #depencecies: #SW STEERING DEBUG DUMP aa36c94853b2 net/mlx5: Set SMFS as a default steering mode if device supports it 4ff725e1d4ad net/mlx5: DR, Ignore modify TTL if device doesn't support it cc2295cd54e4 net/mlx5: DR, Improve steering for empty or RX/TX-only matchers f59464e257bd net/mlx5: DR, Add support for matching on geneve_tlv_option_0_exist field 09753babaf46 net/mlx5: DR, Support matching on tunnel headers 0 and 1 8c2b4fee9c4b net/mlx5: DR, Add misc5 to match_param structs 0f2a6c3b9219 net/mlx5: Add misc5 flow table match parameters b54128275ef8 net/mlx5: DR, Warn on failure to destroy objects due to refcount e3a0f40b2f90 net/mlx5: DR, Add support for UPLINK destination type 9222f0b27da2 net/mlx5: DR, Add support for dumping steering info 7766c9b922fe net/mlx5: DR, Add missing reserved fields to dr_match_param 89cdba3224f0 net/mlx5: DR, Add check for flex parser ID value 08fac109f7bb net/mlx5: DR, Rename list field in matcher struct to list_node 32e9bd585307 net/mlx5: DR, Remove unused struct member in matcher c3fb0e280b4c net/mlx5: DR, Fix lower case macro prefix "mlx5_" to "MLX5_" 84dfac39c61f net/mlx5: DR, Fix error flow in creating matcher 58a606dba708 net/mlx5: Introduce new uplink destination type 455832d49666 net/mlx5: DR, Fix check for unsupported fields in match param 9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately #SW STEERING SF 515ce2ffa621 net/mlx5: DR, init_next_match only if needed 5dde00a73048 net/mlx5: DR, Fix typo 'offeset' to 'offset' 1ffd498901c1 net/mlx5: DR, Increase supported num of actions to 32 11a45def2e19 net/mlx5: DR, Add support for SF vports c0e90fc2ccaa net/mlx5: DR, Support csum recalculation flow table on SFs ee1887fb7cdd net/mlx5: DR, Align error messages for failure to obtain vport caps dd4acb2a0954 net/mlx5: DR, Add missing query for vport 0 7ae8ac9a5820 net/mlx5: DR, Replace local WIRE_PORT macro with the existing MLX5_VPORT_UPLINK f9f93bd55ca6 net/mlx5: DR, Fix vport number data type to u16 c228dce26222 net/mlx5: DR, Fix code indentation in dr_ste_v1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+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 1968480] [NEW] kernel: usb_set_interface failed (-113)
Public bug reported: My webcam ID 046d:0826 Logitech, Inc. HD Webcam C525 has always worked well with Ubuntu. But after some update on 21.10, the microphone recording from the webcam stopped working. The recording starts working if you replug usb or make usbreset. On ubuntu 22.04 bug is still present. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: navycat1738 F pulseaudio /dev/snd/controlC2: navycat1738 F pulseaudio /dev/snd/controlC1: navycat1738 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Apr 10 17:45:35 2022 InstallationDate: Installed on 2022-04-09 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220407) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=96b12ce3-6254-469d-af5e-611471d8887a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:skuPROJECT_SUB_TAG: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish jammy ** Tags added: impish ** 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/1968480 Title: kernel: usb_set_interface failed (-113) Status in linux package in Ubuntu: Confirmed Bug description: My webcam ID 046d:0826 Logitech, Inc. HD Webcam C525 has always worked well with Ubuntu. But after some update on 21.10, the microphone recording from the webcam stopped working. The recording starts working if you replug usb or make usbreset. On ubuntu 22.04 bug is still present. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: navycat1738 F pulseaudio /dev/snd/controlC2: navycat1738 F pulseaudio /dev/snd/controlC1: navycat1738 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Apr 10 17:45:35 2022 InstallationDate: Installed on 2022-04-09 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220407) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=96b12ce3-6254-469d-af5e-611471d8887a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:skuPROJECT_SUB_TAG: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION
[Kernel-packages] [Bug 1968475] [NEW] Fix broken HDMI audio on AMD PRO VII after S3
Public bug reported: [Impact] DP/HDMI audio on AMD PRO VII stops working after S3. [Fix] Ensure HDA function is suspended before ASIC reset so the subsequent resume can be carried out successfully. [Test] With the patch applied, DP/HDMI audio continues to work after S3. [Where problems could occur] The suspend_noirq phase should not trigger any interrupt, so if amdgpu_asic_reset() somehow raised IRQ, it can break the system. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Low Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Low Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Low Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1964736 sutton ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Tags added: oem-priority originate-from-1964736 sutton -- 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/1968475 Title: Fix broken HDMI audio on AMD PRO VII after S3 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed 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: Confirmed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] DP/HDMI audio on AMD PRO VII stops working after S3. [Fix] Ensure HDA function is suspended before ASIC reset so the subsequent resume can be carried out successfully. [Test] With the patch applied, DP/HDMI audio continues to work after S3. [Where problems could occur] The suspend_noirq phase should not trigger any interrupt, so if amdgpu_asic_reset() somehow raised IRQ, it can break the system. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968475/+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 1968469] [NEW] ILITEK_ILI9881C panel driver missing
Public bug reported: the current 5.15.0-1004-raspi kernel for 22.04 does not enable the CONFIG_DRM_PANEL_ILITEK_ILI9881C=m option, thus such touchscreen panels can not be used the cutiepi (https://cutiepi.io/) project does use this hardware for their pi based tablets. booting ubuntu 22.04 on such a tablet is only possible with an external HDMI monitor attached at this moment. it would be nice if Ubuntu could work OOTB on this hardware. while the jammy kernel seems to already ship the required dtb overlay "cutiepi-panel.dtbo", the modules this overlay uses are not there. below is a Kconfig commit outlining the required options: https://github.com/cutiepi- io/linux/commit/de6774dca11b815e647fa08d71f3eac9009c2dff ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1968469 Title: ILITEK_ILI9881C panel driver missing Status in linux-raspi package in Ubuntu: New Bug description: the current 5.15.0-1004-raspi kernel for 22.04 does not enable the CONFIG_DRM_PANEL_ILITEK_ILI9881C=m option, thus such touchscreen panels can not be used the cutiepi (https://cutiepi.io/) project does use this hardware for their pi based tablets. booting ubuntu 22.04 on such a tablet is only possible with an external HDMI monitor attached at this moment. it would be nice if Ubuntu could work OOTB on this hardware. while the jammy kernel seems to already ship the required dtb overlay "cutiepi-panel.dtbo", the modules this overlay uses are not there. below is a Kconfig commit outlining the required options: https://github.com/cutiepi- io/linux/commit/de6774dca11b815e647fa08d71f3eac9009c2dff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1968469/+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 1965605] Re: HUAWEI matebook x pro 2022 led screen backlight do not work with ubuntu 20.x also 21.10
Hi, The backlight issue is solved, just replace 'nomodeset' with 'i915.enable_psr=0' in grub, then backlight adjustment and screen flicker problem are both OK. ACPI still have a lot red alert message, but they do not bring obvoius bad effect by now, so this bug report could be closed. releate topic : https://wiki.archlinux.org/title/intel_graphics B.R. -- 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/1965605 Title: HUAWEI matebook x pro 2022 led screen backlight do not work with ubuntu 20.x also 21.10 Status in linux package in Ubuntu: Confirmed Bug description: linux-modules-5.13.0-37-generic also recent kernel such as 5.16.x LCD backlight control key do not work,dmesg report a lot of ACPI error, I have no idea if these errors related with this problem. Here is the dmesg logs : --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gpmn 4421 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-03-19 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: HUAWEI MRG-WXX Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=63fdfb74-7fb4-47e8-ada6-2f605a114c46 ro quiet splash nomodeset vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.187.29 Tags: focal Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 1/19/2022 dmi.bios.release: 2.18 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.18 dmi.board.asset.tag: N/A dmi.board.name: MRG-WXX-PCB-B1 dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 2.18 dmi.modalias: dmi:bvnHUAWEI:bvr2.18:bd1/19/2022:br2.18:efr2.18:svnHUAWEI:pnMRG-WXX:pvrM1010:rvnHUAWEI:rnMRG-WXX-PCB-B1:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC233: dmi.product.family: MateBook X dmi.product.name: MRG-WXX dmi.product.sku: C233 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965605/+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 1967727] Re: Random screen blanks with "CPU pipe B FIFO underrun" error
I have same problem. i update to 22.04 from 20.04. i update kernel to 5.15.0-25-generic, still having problem my computer is thinkpad t480s, connect to external monitor by type-c or thunderbolt 3, both have this kind of problem -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967727 Title: Random screen blanks with "CPU pipe B FIFO underrun" error Status in linux package in Ubuntu: Confirmed Bug description: On a clean 22.04 install, the screen randomly blanks once in a while for a couple of seconds, then comes back. I see the following message in dmesg when it happens: [ 6614.338572] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 10:16:27 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW 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.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967727/+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
