[Kernel-packages] [Bug 2000228] Re: Add initial support for Mediatek Genio boards
** Description changed: [Impact] - Add initial support for Mediatek Genio boards + Add initial support for Mediatek Genio boards (mt8195_demo, mt8365-evk, mt8390-evk, and mt8395-evk) mt8195-demo: https://github.com/alsa-project/alsa-ucm-conf/commit/7e2dbf2158bb2acd7bdf101acf5b49ec7400c6c9 https://github.com/alsa-project/alsa-ucm-conf/commit/445c079665979802d50b237fe5a55be82ffd0bd9 mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 [Where problems could occur] Audio function doesn't work on Mediatek mt8195 demo platform. Play audio by aplay and gnome sound test: 1. HDMI audio: Pass 2. Headset: Pass [Test Case] Verify audio function (headset & hdmi audio) on Mediatek mt8195 demo platform. [Regression Potential] Add initial support for Mediatek mt8195 demo platform. There should be no risk. ** Description changed: [Impact] Add initial support for Mediatek Genio boards (mt8195_demo, mt8365-evk, mt8390-evk, and mt8395-evk) mt8195-demo: https://github.com/alsa-project/alsa-ucm-conf/commit/7e2dbf2158bb2acd7bdf101acf5b49ec7400c6c9 https://github.com/alsa-project/alsa-ucm-conf/commit/445c079665979802d50b237fe5a55be82ffd0bd9 mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 + + mt8390-evk: (Still under review) + https://github.com/alsa-project/alsa-ucm-conf/pull/321 + + mt8395-evk: (Still under review) + https://github.com/alsa-project/alsa-ucm-conf/pull/322 [Where problems could occur] Audio function doesn't work on Mediatek mt8195 demo platform. Play audio by aplay and gnome sound test: 1. HDMI audio: Pass 2. Headset: Pass [Test Case] Verify audio function (headset & hdmi audio) on Mediatek mt8195 demo platform. [Regression Potential] Add initial support for Mediatek mt8195 demo platform. There should be no risk. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2000228 Title: Add initial support for Mediatek Genio boards Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Add initial support for Mediatek Genio boards (mt8195_demo, mt8365-evk, mt8390-evk, and mt8395-evk) mt8195-demo: https://github.com/alsa-project/alsa-ucm-conf/commit/7e2dbf2158bb2acd7bdf101acf5b49ec7400c6c9 https://github.com/alsa-project/alsa-ucm-conf/commit/445c079665979802d50b237fe5a55be82ffd0bd9 mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 mt8390-evk: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 mt8395-evk: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/322 [Where problems could occur] Audio function doesn't work on Mediatek mt8195 demo platform. Play audio by aplay and gnome sound test: 1. HDMI audio: Pass 2. Headset: Pass [Test Case] Verify audio function (headset & hdmi audio) on Mediatek mt8195 demo platform. [Regression Potential] Add initial support for Mediatek mt8195 demo platform. There should be no risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+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 315803] 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 315803 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/315803 Title: USB Storage drive fails to mount Status in linux package in Ubuntu: Incomplete Bug description: Upon fresh installation of Ubuntu Hardy (8.04) Inserting a USB storage device causes it to mount automatically. After about 2 days and several reboots no USB storage devices can be mounted. The USB drive appears in the "Places" menu, but will not mount. An error dialog states: "Invalid mount option" I traced the problem to my /etc/fstab file: proc/proc procdefaults0 0 # /dev/sdb1 UUID=4bffd628-caac-4c1b-b55c-806a039d19bc / ext3 relatime,errors=remount-ro 0 1 # /dev/sdb5 UUID=5c8e9f6a-b5ce-444a-bbe6-29325fa41d05 noneswapsw 0 0 /dev/sdc1 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 /dev/scd0 /media/cdrom1 udf,iso9660 user,noauto,exec,utf8 0 0 /dev/scd1 /media/cdrom2 udf,iso9660 user,noauto,exec,utf8 0 0 I have a backup of my /etc/fstab file from the fresh installed state: proc/proc procdefaults0 0 # /dev/sdb1 UUID=4bffd628-caac-4c1b-b55c-806a039d19bc / ext3 relatime,errors=remount-ro 0 1 # /dev/sdb5 UUID=5c8e9f6a-b5ce-444a-bbe6-29325fa41d05 noneswapsw 0 0 /dev/scd0 /media/cdrom1 udf,iso9660 user,noauto,exec,utf8 0 0 /dev/scd1 /media/cdrom2 udf,iso9660 user,noauto,exec,utf8 0 0 Note: The backed up fstab file does not contain the following line: /dev/sdc1 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 This line was not added by me, and I have not installed any new packages or applications at or before the time of this problem. Commenting or removing this line from the fstab file fixes the problem and allows the USB drive to be mounted again. I suspect that leaving the usb drive plugged in and then rebooting caused the additional mounting instruction to be added to the fstab file upon boot. Workaround: Unmount and unplug any external usb drives BEFORE booting or re-booting Ubuntu. This exact issue has occurred with both my Laptop as well as my Desktop both running the same Ubuntu release (8.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/315803/+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 1876234] 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 1876234 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/1876234 Title: tty/usb0 not work at node mcu esp8266 Status in linux package in Ubuntu: Incomplete Bug description: node mcu not attech To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876234/+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 2017268] Re: mouse and keyboard stopped working
[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/2017268 Title: mouse and keyboard stopped working Status in linux package in Ubuntu: Expired Bug description: Using ubuntu - turning my computer on, neither my mouse nor keyboard work anymore at login screen. I have dual-boot with windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017268/+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 2000228] Re: Add initial support for Mediatek Genio boards
** Summary changed: - Add initial support for Mediatek mt8195 demo platform + Add initial support for Mediatek Genio boards ** Tags added: originate-from-2007249 originate-from-2013432 originate- from-2022024 ** Description changed: [Impact] - Add initial support for Mediatek mt8195 demo platform + Add initial support for Mediatek Genio boards + + mt8195-demo: https://github.com/alsa-project/alsa-ucm-conf/commit/7e2dbf2158bb2acd7bdf101acf5b49ec7400c6c9 https://github.com/alsa-project/alsa-ucm-conf/commit/445c079665979802d50b237fe5a55be82ffd0bd9 + + mt8365-evk: + https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 [Where problems could occur] Audio function doesn't work on Mediatek mt8195 demo platform. Play audio by aplay and gnome sound test: 1. HDMI audio: Pass 2. Headset: Pass [Test Case] Verify audio function (headset & hdmi audio) on Mediatek mt8195 demo platform. [Regression Potential] Add initial support for Mediatek mt8195 demo platform. There should be no risk. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2000228 Title: Add initial support for Mediatek Genio boards Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Add initial support for Mediatek Genio boards mt8195-demo: https://github.com/alsa-project/alsa-ucm-conf/commit/7e2dbf2158bb2acd7bdf101acf5b49ec7400c6c9 https://github.com/alsa-project/alsa-ucm-conf/commit/445c079665979802d50b237fe5a55be82ffd0bd9 mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 [Where problems could occur] Audio function doesn't work on Mediatek mt8195 demo platform. Play audio by aplay and gnome sound test: 1. HDMI audio: Pass 2. Headset: Pass [Test Case] Verify audio function (headset & hdmi audio) on Mediatek mt8195 demo platform. [Regression Potential] Add initial support for Mediatek mt8195 demo platform. There should be no risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+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 1876234] Re: tty/usb0 not work at node mcu esp8266
** Package changed: usbview (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876234 Title: tty/usb0 not work at node mcu esp8266 Status in linux package in Ubuntu: New Bug description: node mcu not attech To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876234/+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 311050] 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 311050 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/311050 Title: usb device Creative Nomad_Muvo not mountable Status in linux package in Ubuntu: Incomplete Bug description: I see that you have changed your triage process (ref bug #240211). Nevertheless, I also have a Creative MuVo 128 that is not visible to my Hardy system - although it does mount on Fedora 9. I'm running on an old Dell Dimension 2300 and I'm pretty sure that this used to work. ProblemType: Bug Architecture: i386 Date: Tue Dec 23 23:07:10 2008 Dependencies: DistroRelease: Ubuntu 8.10 Package: linux None [modified: /var/lib/dpkg/info/linux.list] PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta Uname: Linux 2.6.24-22-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/311050/+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 311050] Re: usb device Creative Nomad_Muvo not mountable
** Package changed: usbview (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/311050 Title: usb device Creative Nomad_Muvo not mountable Status in linux package in Ubuntu: Incomplete Bug description: I see that you have changed your triage process (ref bug #240211). Nevertheless, I also have a Creative MuVo 128 that is not visible to my Hardy system - although it does mount on Fedora 9. I'm running on an old Dell Dimension 2300 and I'm pretty sure that this used to work. ProblemType: Bug Architecture: i386 Date: Tue Dec 23 23:07:10 2008 Dependencies: DistroRelease: Ubuntu 8.10 Package: linux None [modified: /var/lib/dpkg/info/linux.list] PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta Uname: Linux 2.6.24-22-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/311050/+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 315803] Re: USB Storage drive fails to mount
** Package changed: usbview (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/315803 Title: USB Storage drive fails to mount Status in linux package in Ubuntu: New Bug description: Upon fresh installation of Ubuntu Hardy (8.04) Inserting a USB storage device causes it to mount automatically. After about 2 days and several reboots no USB storage devices can be mounted. The USB drive appears in the "Places" menu, but will not mount. An error dialog states: "Invalid mount option" I traced the problem to my /etc/fstab file: proc/proc procdefaults0 0 # /dev/sdb1 UUID=4bffd628-caac-4c1b-b55c-806a039d19bc / ext3 relatime,errors=remount-ro 0 1 # /dev/sdb5 UUID=5c8e9f6a-b5ce-444a-bbe6-29325fa41d05 noneswapsw 0 0 /dev/sdc1 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 /dev/scd0 /media/cdrom1 udf,iso9660 user,noauto,exec,utf8 0 0 /dev/scd1 /media/cdrom2 udf,iso9660 user,noauto,exec,utf8 0 0 I have a backup of my /etc/fstab file from the fresh installed state: proc/proc procdefaults0 0 # /dev/sdb1 UUID=4bffd628-caac-4c1b-b55c-806a039d19bc / ext3 relatime,errors=remount-ro 0 1 # /dev/sdb5 UUID=5c8e9f6a-b5ce-444a-bbe6-29325fa41d05 noneswapsw 0 0 /dev/scd0 /media/cdrom1 udf,iso9660 user,noauto,exec,utf8 0 0 /dev/scd1 /media/cdrom2 udf,iso9660 user,noauto,exec,utf8 0 0 Note: The backed up fstab file does not contain the following line: /dev/sdc1 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 This line was not added by me, and I have not installed any new packages or applications at or before the time of this problem. Commenting or removing this line from the fstab file fixes the problem and allows the USB drive to be mounted again. I suspect that leaving the usb drive plugged in and then rebooting caused the additional mounting instruction to be added to the fstab file upon boot. Workaround: Unmount and unplug any external usb drives BEFORE booting or re-booting Ubuntu. This exact issue has occurred with both my Laptop as well as my Desktop both running the same Ubuntu release (8.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/315803/+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 2015608] Re: cannot hotplug a cpu for ubuntu23.04 VM running on ESXi
This issue is fixed in kernel-6.2.0-23-generic of Ubuntu 23.04. But Cpu-Hotplug starts to fail in kernel-5.19.0-45-generic of Ubuntu22.04.2 and Ubuntu 22.10, it works well in kernel-5.19.0-43-generic. -- 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/2015608 Title: cannot hotplug a cpu for ubuntu23.04 VM running on ESXi Status in linux package in Ubuntu: Confirmed Bug description: hot-plugging a cpu for ubuntu23.04 vm running on ESXi is failed, below logs is reported in kern.log 2023-04-07T22:10:15.427140+00:00 vmware-server kernel: [ 123.514678] APIC: NR_CPUS/possible_cpus limit of 3 reached. Processor 3/0x6 ignored. 2023-04-07T22:10:15.427903+00:00 vmware-server kernel: [ 123.514682] ACPI: Unable to map lapic to logical cpu number === running "chcpu -e 4", "chcpu: CPU 4 does not exist" after reboot the VM, the hot-plugged cpu can be detected by default. === other information: This isue cannot be reproduced in ubuntu22.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015608/+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 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration.
** Package changed: linux (Ubuntu) => linux-hwe-5.15 (Ubuntu) ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2024500/+attachment/5681057/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2024500/+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 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration.
** Description changed: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes - No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 - --- + + + + --- ProblemType: Bug AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Jun 20 21:15 seq - crw-rw 1 root audio 116, 33 Jun 20 21:15 timer + total 0 + crw-rw 1 root audio 116, 1 Jun 20 21:15 seq + crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: - + ProcEnviron: - TERM=screen-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: - linux-restricted-modules-5.15.0-75-generic N/A - linux-backports-modules-5.15.0-75-generic N/A - linux-firmware 1.187.39 + linux-restricted-modules-5.15.0-75-generic N/A + linux-backports-modules-5.15.0-75-generic N/A + linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro -- 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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip
[Kernel-packages] [Bug 2024501] 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 2024501
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/2024501
Title:
Kernel 5.15.0-75 refuses to boot
Status in linux package in Ubuntu:
Incomplete
Bug description:
Linux Mint 21.1 Vera
Failiure to find root partition on /dev/sda4 in section 0.400438 of boot
sequence
Not syncing / (NB not including /home or /timeshift)
[ 0.400438} VFS: Cannot open root device "sda4" or unknown-block {0,0}:
error -6
MSI A320M-A Pro (MS-7C51) motherboard BIOS 1.60 5/16/2022
[ 0.416709] ---[ end Kernel panic - not syncing: VFS:Unable to mount root fs
on unknown-block {0,0} ]---
Have to revert to previous kernel in grub menu:
andybiker@greenroom:~$ cat version.log
Ubuntu 5.15.0-73.80-generic 5.15.98
andybiker@greenroom:~$ lsb_release -rd
Description: Linux Mint 21.1
Release: 21.1
Trying to install apport...
andybiker@greenroom:~$ sudo apt install apport
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
apport is already the newest version (2.20.11-0ubuntu82.5).
The following packages were automatically installed and are no longer
required:
linux-headers-5.15.0-70 linux-headers-5.15.0-70-generic
linux-headers-5.15.0-71 linux-headers-5.15.0-71-generic
linux-headers-5.15.0-72 linux-headers-5.15.0-72-generic
linux-image-5.15.0-70-generic linux-image-5.15.0-71-generic
linux-image-5.15.0-72-generic linux-modules-5.15.0-70-generic
linux-modules-5.15.0-71-generic linux-modules-5.15.0-72-generic
linux-modules-extra-5.15.0-70-generic linux-modules-extra-5.15.0-71-generic
linux-modules-extra-5.15.0-72-generic
Use 'sudo apt autoremove' to remove them.
0 to upgrade, 0 to newly install, 0 to remove and 25 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up linux-image-5.15.0-75-generic (5.15.0-75.82) ...
Processing triggers for linux-image-5.15.0-75-generic (5.15.0-75.82) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.15.0-75-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-75-generic
W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_gpu_info.bin
for m
odule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for
modul
e amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_rlc.bin for
mod
ule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec2.bin for
mo
dule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec.bin for
mod
ule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_me.bin for
modu
le amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_pfp.bin for
mod
ule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_ce.bin for
modu
le amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma1.bin
for m
odule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma.bin for
mo
dule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for
mod
ule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module
amdg
pu
I: The initramfs will attempt to resume from /dev/sda6
I: (UUID=20f57141-9055-4011-bbd1-942a31be2659)
I: Set the RESUME variable to override this.
zstd: error 25 : Write error : No space left on device (cannot write
compressed
block)
E: mkinitramfs failure zstd -q -1 -T0 25
update-initramfs: failed for /boot/initrd.img-5.15.0-75-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.15.0-75-generic (--configure):
installed linux-image-5.15.0-75-generic package post-installation script
subpro
cess returned error exit status 1
Errors were encountered while processing:
linux-image-5.15.0-75-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
To manage notifications about this bug go to:
[Kernel-packages] [Bug 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
Test kernel with the additional overlayfs fix applied: https://kernel.ubuntu.com/~arighi/lp2016398/ -- 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/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Bug description: Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem actually results in success I then built a Kubuntu Lunar VM, and was able to replicate it on not just my system. When I built and install the vanilla kernel with bindeb-pkg, and then I boot the vanilla kernel, I can't replicate it, the second filesystem unmounts. When I reboot the VM, and start the default distribution kernel, I am able to replicate the issue, the second filesystem being unable to unmount, with "target is busy" with no files open according to standard usermode tools, when chroot is called on it I tried to look at patches in git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar and git log --oneline --grep="sauce" but none of them really look relevant. I could be VERY wrong in this matter though SUMMARY: Long story short, (I am VERY sorry about the length:) I make an overlayfs, I make a second overlayfs with the first overlayfs as the second one's lowerdir, I chroot into the second overlayfs, and then later I can't unmount the second one as it says "Target is busy", but the user mode tools don't show any files open at all. If I mount the second overlayfs, and then unmount it without ever chroot-ing into it I AM able to unmount it The attached script should replicate the issue This doesn't seem to happen on the vanilla Linux kernel, with the same as close as possible config that Ubuntu uses Thanks ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nerdopolis 3007 F wireplumber /dev/snd/controlC0: nerdopolis 3007 F wireplumber /dev/snd/seq:nerdopolis 3003 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Apr 15 19:08:48 2023 InstallationDate: Installed on 2023-04-09 (6 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230408) MachineType: ASRock B650M PG Riptide ProcFB: 0 amdgpudrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 2024500] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681058/+files/acpidump.txt ** 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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681056/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681052/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681057/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681050/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681055/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681051/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681054/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681053/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681049/+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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681048/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681046/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681047/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration.
apport information ** Tags added: apport-collected focal ** Description changed: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jun 20 21:15 seq + crw-rw 1 root audio 116, 33 Jun 20 21:15 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.27 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + MachineType: Supermicro AS -2124BT-HNTR + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 astdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 + ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-75-generic N/A + linux-backports-modules-5.15.0-75-generic N/A + linux-firmware 1.187.39 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal + Uname: Linux 5.15.0-75-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 09/23/2022 + dmi.bios.release: 5.22 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2.5 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: H12DST-B + dmi.board.vendor: Supermicro + dmi.board.version: 1.00A + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 1 + dmi.chassis.vendor: Supermicro + dmi.chassis.version: 0123456789 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: AS -2124BT-HNTR + dmi.product.sku: To be filled by O.E.M. + dmi.product.version: 0123456789 + dmi.sys.vendor: Supermicro ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681045/+files/CRDA.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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color
[Kernel-packages] [Bug 2024500] 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 2024500 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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Incomplete Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, Guest hangs after migration.
compute37 apport ** Attachment added: "compute37 apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+attachment/5681032/+files/compute37-apport.txt ** Description changed: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes - Not seeing the issue using the following kernels: + No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 -- 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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Incomplete Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, Guest hangs after migration.
libvirt version (nova-libvirt)[root@compute81 /]# dpkg -l | grep libvirt ii libvirt-clients 6.0.0-0ubuntu8.16 amd64Programs for the libvirt library ii libvirt-daemon 6.0.0-0ubuntu8.16 amd64Virtualization daemon ii libvirt-daemon-driver-qemu 6.0.0-0ubuntu8.16 amd64Virtualization daemon QEMU connection driver ii libvirt-daemon-system6.0.0-0ubuntu8.16 amd64Libvirt daemon configuration files ii libvirt-daemon-system-systemd6.0.0-0ubuntu8.16 amd64Libvirt daemon configuration files (systemd) ii libvirt0:amd64 6.0.0-0ubuntu8.16 amd64library for interfacing with different virtualization systems qemu version (nova-libvirt)[root@compute81 /]# dpkg -l | grep qemu ii ipxe-qemu1.0.0+git-20190109.133f4c4-0ubuntu3.2 all PXE boot firmware - ROM images for qemu ii ipxe-qemu-256k-compat-efi-roms 1.0.0+git-20150424.a25a16d-0ubuntu4 all PXE boot firmware - Compat EFI ROM images for qemu ii libvirt-daemon-driver-qemu 6.0.0-0ubuntu8.16 amd64Virtualization daemon QEMU connection driver ii qemu-block-extra:amd64 1:4.2-3ubuntu6.24 amd64extra block backend modules for qemu-system and qemu-utils ii qemu-kvm 1:4.2-3ubuntu6.24 amd64QEMU Full virtualization on x86 hardware ii qemu-slof20191209+dfsg-1 all Slimline Open Firmware -- QEMU PowerPC version ii qemu-system 1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries ii qemu-system-arm 1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (arm) ii qemu-system-common 1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (common files) ii qemu-system-data 1:4.2-3ubuntu6.24 all QEMU full system emulation (data files) ii qemu-system-mips 1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (mips) ii qemu-system-misc 1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (miscellaneous) ii qemu-system-ppc 1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (ppc) ii qemu-system-s390x1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (s390x) ii qemu-system-sparc1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (sparc) ii qemu-system-x86 1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (x86) ** Summary changed: - KVM: after upgrading the kernel to 5.15.0-75, Guest hangs after migration. + KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. -- 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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Incomplete Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, Guest hangs after migration.
compute81 apport ** Description changed: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. - First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux - When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes - No issue using the following kernels: + Not seeing the issue using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 ** Attachment added: "compute81-apport.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+attachment/5681031/+files/compute81-apport.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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Incomplete Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2024501] [NEW] Kernel 5.15.0-75 refuses to boot
Public bug reported:
Linux Mint 21.1 Vera
Failiure to find root partition on /dev/sda4 in section 0.400438 of boot
sequence
Not syncing / (NB not including /home or /timeshift)
[ 0.400438} VFS: Cannot open root device "sda4" or unknown-block {0,0}: error
-6
MSI A320M-A Pro (MS-7C51) motherboard BIOS 1.60 5/16/2022
[ 0.416709] ---[ end Kernel panic - not syncing: VFS:Unable to mount root fs
on unknown-block {0,0} ]---
Have to revert to previous kernel in grub menu:
andybiker@greenroom:~$ cat version.log
Ubuntu 5.15.0-73.80-generic 5.15.98
andybiker@greenroom:~$ lsb_release -rd
Description:Linux Mint 21.1
Release:21.1
Trying to install apport...
andybiker@greenroom:~$ sudo apt install apport
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
apport is already the newest version (2.20.11-0ubuntu82.5).
The following packages were automatically installed and are no longer required:
linux-headers-5.15.0-70 linux-headers-5.15.0-70-generic
linux-headers-5.15.0-71 linux-headers-5.15.0-71-generic
linux-headers-5.15.0-72 linux-headers-5.15.0-72-generic
linux-image-5.15.0-70-generic linux-image-5.15.0-71-generic
linux-image-5.15.0-72-generic linux-modules-5.15.0-70-generic
linux-modules-5.15.0-71-generic linux-modules-5.15.0-72-generic
linux-modules-extra-5.15.0-70-generic linux-modules-extra-5.15.0-71-generic
linux-modules-extra-5.15.0-72-generic
Use 'sudo apt autoremove' to remove them.
0 to upgrade, 0 to newly install, 0 to remove and 25 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up linux-image-5.15.0-75-generic (5.15.0-75.82) ...
Processing triggers for linux-image-5.15.0-75-generic (5.15.0-75.82) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.15.0-75-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-75-generic
W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_gpu_info.bin for m
odule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for modul
e amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_rlc.bin for mod
ule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec2.bin for mo
dule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec.bin for mod
ule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_me.bin for modu
le amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_pfp.bin for mod
ule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_ce.bin for modu
le amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma1.bin for m
odule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma.bin for mo
dule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for mod
ule amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdg
pu
I: The initramfs will attempt to resume from /dev/sda6
I: (UUID=20f57141-9055-4011-bbd1-942a31be2659)
I: Set the RESUME variable to override this.
zstd: error 25 : Write error : No space left on device (cannot write compressed
block)
E: mkinitramfs failure zstd -q -1 -T0 25
update-initramfs: failed for /boot/initrd.img-5.15.0-75-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.15.0-75-generic (--configure):
installed linux-image-5.15.0-75-generic package post-installation script subpro
cess returned error exit status 1
Errors were encountered while processing:
linux-image-5.15.0-75-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "grub advanced boot screen output"
https://bugs.launchpad.net/bugs/2024501/+attachment/5681033/+files/5.15.0-75.jpg
--
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/2024501
Title:
Kernel 5.15.0-75 refuses to boot
Status in linux package in Ubuntu:
New
Bug description:
Linux Mint 21.1 Vera
Failiure to find root partition on /dev/sda4 in section 0.400438 of boot
sequence
Not syncing / (NB not including /home or /timeshift)
[ 0.400438} VFS: Cannot open root device "sda4" or unknown-block {0,0}:
error -6
MSI A320M-A Pro (MS-7C51) motherboard BIOS 1.60 5/16/2022
[ 0.416709] ---[ end Kernel panic - not syncing: VFS:Unable to mount root fs
on unknown-block {0,0} ]---
Have to revert to previous kernel in grub menu:
andybiker@greenroom:~$ cat version.log
Ubuntu 5.15.0-73.80-generic 5.15.98
andybiker@greenroom:~$ lsb_release -rd
Description: Linux Mint 21.1
Release:
[Kernel-packages] [Bug 2024500] [NEW] KVM: after upgrading the kernel to 5.15.0-75, Guest hangs after migration.
Public bug reported: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes Not seeing the issue using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 ** 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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, Guest hangs after migration. Status in linux package in Ubuntu: New Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes Not seeing the issue using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+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 2008774] Re: Ubuntu 22.04 not waking up after second suspend
I also have this problem, in Ubuntu 23.04. See https://askubuntu.com/questions/1464731/ubuntu-23-04-wont-wake-from- suspend. I'm using a Lenovo legion Y520, with Intel / Radeon. With wayland, couldn't install drivers using amdgpu-install because dkms module won't compile with 6.2 kernels. #17 could you somehow configure the suspend so that our command is run automatically when suspending for inactivity? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 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.19/+bug/2008774/+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 2024427] Re: potential S3 issue for amdgpu Navi 31/Navi33
Need details (symptoms, reproduce steps) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Incomplete ** Changed in: linux (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Mantic) Status: Invalid => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2024427 Title: potential S3 issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-firmware source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: Incomplete Status in linux source package in Lunar: New Status in linux-firmware source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Invalid Status in linux-firmware source package in Mantic: New Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+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 2024427] Re: potential S3 issue for amdgpu Navi 31/Navi33
All the nominated commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Mantic) Status: New => Invalid -- 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/2024427 Title: potential S3 issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-firmware source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: Incomplete Status in linux source package in Lunar: New Status in linux-firmware source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Invalid Status in linux-firmware source package in Mantic: New Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+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 2024479] 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 2024479 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 ** Changed in: linux (Ubuntu Focal) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on arm64 when offset is not specified Status in kexec-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in kexec-tools source package in Focal: New Status in linux source package in Focal: Incomplete Status in kexec-tools source package in Jammy: New Status in linux source package in Jammy: Incomplete Bug description: [Description] kdump fails on arm64, on machines with a lot of memory when offeset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel regions. To address this issue the following upstrem commits are needed: From the kernel side : commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified From kexec-tools commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the 5.15 hwe focal kernel will be fixed. [Test] You need a machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump and trigger a crash. It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. [Regression Potential] [Other] Commits to backport JAMMY: kernel: a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified kexec: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions FOCAL: kernel (5.15 hwe kernel): a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified 4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel() 8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed 5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64 944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef kexec: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions 2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions 64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available) f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes
[Kernel-packages] [Bug 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
** Tags added: patch -- 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/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Bug description: Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem actually results in success I then built a Kubuntu Lunar VM, and was able to replicate it on not just my system. When I built and install the vanilla kernel with bindeb-pkg, and then I boot the vanilla kernel, I can't replicate it, the second filesystem unmounts. When I reboot the VM, and start the default distribution kernel, I am able to replicate the issue, the second filesystem being unable to unmount, with "target is busy" with no files open according to standard usermode tools, when chroot is called on it I tried to look at patches in git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar and git log --oneline --grep="sauce" but none of them really look relevant. I could be VERY wrong in this matter though SUMMARY: Long story short, (I am VERY sorry about the length:) I make an overlayfs, I make a second overlayfs with the first overlayfs as the second one's lowerdir, I chroot into the second overlayfs, and then later I can't unmount the second one as it says "Target is busy", but the user mode tools don't show any files open at all. If I mount the second overlayfs, and then unmount it without ever chroot-ing into it I AM able to unmount it The attached script should replicate the issue This doesn't seem to happen on the vanilla Linux kernel, with the same as close as possible config that Ubuntu uses Thanks ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nerdopolis 3007 F wireplumber /dev/snd/controlC0: nerdopolis 3007 F wireplumber /dev/snd/seq:nerdopolis 3003 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Apr 15 19:08:48 2023 InstallationDate: Installed on 2023-04-09 (6 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230408) MachineType: ASRock B650M PG Riptide ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgkubuntu-root ro quiet splash amdgpu.sg_display=0
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@giuliano69 HI, Sir Now I have linux-headers-5.19.0-45-generic' can you provide solutions again step by step so I can run my Camera Device THanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ignis_ADH dmi.board.vendor: ADL dmi.board.version: V1.06
[Kernel-packages] [Bug 2024427] Re: potential S3 issue for amdgpu Navi 31/Navi33
** Changed in: linux-firmware (Ubuntu Mantic) Status: New => Invalid -- 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/2024427 Title: potential S3 issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: New Status in linux-firmware source package in Lunar: New Status in linux-firmware source package in Mantic: Invalid Bug description: amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+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 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
This patch should fix this bug without breaking the behavior of /proc/self/map_files. Can you give it a try? I can also prepare a test kernel if you need. ** Patch added: "0001-UBUNTU-SAUCE-overlayfs-fix-reference-count-mismatch.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016398/+attachment/5681016/+files/0001-UBUNTU-SAUCE-overlayfs-fix-reference-count-mismatch.patch -- 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/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Bug description: Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem actually results in success I then built a Kubuntu Lunar VM, and was able to replicate it on not just my system. When I built and install the vanilla kernel with bindeb-pkg, and then I boot the vanilla kernel, I can't replicate it, the second filesystem unmounts. When I reboot the VM, and start the default distribution kernel, I am able to replicate the issue, the second filesystem being unable to unmount, with "target is busy" with no files open according to standard usermode tools, when chroot is called on it I tried to look at patches in git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar and git log --oneline --grep="sauce" but none of them really look relevant. I could be VERY wrong in this matter though SUMMARY: Long story short, (I am VERY sorry about the length:) I make an overlayfs, I make a second overlayfs with the first overlayfs as the second one's lowerdir, I chroot into the second overlayfs, and then later I can't unmount the second one as it says "Target is busy", but the user mode tools don't show any files open at all. If I mount the second overlayfs, and then unmount it without ever chroot-ing into it I AM able to unmount it The attached script should replicate the issue This doesn't seem to happen on the vanilla Linux kernel, with the same as close as possible config that Ubuntu uses Thanks ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nerdopolis 3007 F wireplumber /dev/snd/controlC0: nerdopolis 3007 F wireplumber /dev/snd/seq:nerdopolis 3003 F pipewire CasperMD5CheckResult: pass
[Kernel-packages] [Bug 2024302]
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Tags added: no-boot-space -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2024302 Title: package linux-image-5.15.0-75-generic 5.15.0-75.82~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux-signed-hwe-5.15 package in Ubuntu: Invalid Bug description: TBD losing time hackers sell out brasin damge disabiliti AI ml ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-75-generic 5.15.0-75.82~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.27 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 17 13:05:11 2023 ErrorMessage: installed linux-image-5.15.0-75-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-15 (214 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: linux-signed-hwe-5.15 Title: package linux-image-5.15.0-75-generic 5.15.0-75.82~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to focal on 2023-03-15 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2024302/+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 2024302] Re: package linux-image-5.15.0-75-generic 5.15.0-75.82~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: linux-signed-hwe-5.15 (Ubuntu) Status: New => Invalid ** Changed in: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2024302 Title: package linux-image-5.15.0-75-generic 5.15.0-75.82~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux-signed-hwe-5.15 package in Ubuntu: Invalid Bug description: TBD losing time hackers sell out brasin damge disabiliti AI ml ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-75-generic 5.15.0-75.82~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.27 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 17 13:05:11 2023 ErrorMessage: installed linux-image-5.15.0-75-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-15 (214 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: linux-signed-hwe-5.15 Title: package linux-image-5.15.0-75-generic 5.15.0-75.82~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to focal on 2023-03-15 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2024302/+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 2024479] [NEW] kdump fails on arm64 when offset is not specified
Public bug reported: [Description] kdump fails on arm64, on machines with a lot of memory when offeset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel regions. To address this issue the following upstrem commits are needed: >From the kernel side : commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified >From kexec-tools commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the 5.15 hwe focal kernel will be fixed. [Test] You need a machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump and trigger a crash. It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. [Regression Potential] [Other] Commits to backport JAMMY: kernel: a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified kexec: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions FOCAL: kernel (5.15 hwe kernel): a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified 4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel() 8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed 5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64 944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef kexec: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions 2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions 64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available) f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: kexec-tools (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: kexec-tools (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: kexec-tools (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/2024479 Title: kdump fails on arm64 when offset is not specified Status in kexec-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in kexec-tools source package in Focal: New Status in linux source package in Focal: New Status in kexec-tools source package in Jammy: New Status in linux source package in Jammy: New Bug description: [Description] kdump fails on arm64, on machines with a lot of memory when offeset is not specified, e.g when
[Kernel-packages] [Bug 2023503] Re: package linux-modules-nvidia-515-5.19.0-43-generic (not installed) failed to install/upgrade: 已安装 linux-modules-nvidia-515-5.19.0-43-generic 软件包 post-installation 脚
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 linux-restricted-modules-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2023503 Title: package linux-modules-nvidia-515-5.19.0-43-generic (not installed) failed to install/upgrade: 已安装 linux-modules- nvidia-515-5.19.0-43-generic 软件包 post-installation 脚本 子进程返回错误状态 127 Status in linux-restricted-modules-hwe-5.19 package in Ubuntu: New Bug description: package linux-modules-nvidia-515-5.19.0-43-generic (not installed) failed to install/upgrade: 已安装 linux-modules- nvidia-515-5.19.0-43-generic 软件包 post-installation 脚本 子进程返回错误状态 127 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-515-5.19.0-43-generic (not installed) ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jun 12 00:53:14 2023 ErrorMessage: 已安装 linux-modules-nvidia-515-5.19.0-43-generic 软件包 post-installation 脚本 子进程返回错误状态 127 InstallationDate: Installed on 2022-10-21 (233 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-restricted-modules-hwe-5.19 Title: package linux-modules-nvidia-515-5.19.0-43-generic (not installed) failed to install/upgrade: 已安装 linux-modules-nvidia-515-5.19.0-43-generic 软件包 post-installation 脚本 子进程返回错误状态 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.19/+bug/2023503/+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 2024279] Re: package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-45-generic package post-installation script subpr
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2024279 Title: package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-45-generic package post- installation script subprocess returned error exit status 135 Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: The OS started crashing and the browser stopped working first and then the files. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Jun 17 13:20:59 2023 DuplicateSignature: package:linux-image-5.19.0-45-generic:5.19.0-45.46~22.04.1 Setting up linux-image-5.19.0-45-generic (5.19.0-45.46~22.04.1) ... Bus error (core dumped) dpkg: error processing package linux-image-5.19.0-45-generic (--configure): installed linux-image-5.19.0-45-generic package post-installation script subprocess returned error exit status 135 ErrorMessage: installed linux-image-5.19.0-45-generic package post-installation script subprocess returned error exit status 135 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-signed-hwe-5.19 Title: package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-45-generic package post-installation script subprocess returned error exit status 135 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.19/+bug/2024279/+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 2024279] Re: package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-45-generic package post-installation script subpr
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 linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2024279 Title: package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-45-generic package post- installation script subprocess returned error exit status 135 Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: The OS started crashing and the browser stopped working first and then the files. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Jun 17 13:20:59 2023 DuplicateSignature: package:linux-image-5.19.0-45-generic:5.19.0-45.46~22.04.1 Setting up linux-image-5.19.0-45-generic (5.19.0-45.46~22.04.1) ... Bus error (core dumped) dpkg: error processing package linux-image-5.19.0-45-generic (--configure): installed linux-image-5.19.0-45-generic package post-installation script subprocess returned error exit status 135 ErrorMessage: installed linux-image-5.19.0-45-generic package post-installation script subprocess returned error exit status 135 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-signed-hwe-5.19 Title: package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-45-generic package post-installation script subprocess returned error exit status 135 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.19/+bug/2024279/+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 2020627] Re: upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia and Morocco
linux-firmware SRU:
* https://lists.ubuntu.com/archives/kernel-team/2023-June/140531.html (jammy)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ iwlwifi takes firmware updates to support WiFi 6E in Malaysia and
+ Morocco. The models in concern are AX210 (iwlwifi-ty-a0-gf-a0-*), AX211
+ (iwlwifi-so-a0-gf-a0-*) and AX411 (iwlwifi-so-a0-gf4-a0-*).
+
+ [Fix]
+
+ pnvm along with the ucode firmware from upstream commit 5bc279fb161d
+ ("iwlwifi: update core69 and core72 firmwares for So device") are
+ required. While the pnvm and ucode blobs may not be upgraded
+ simultaneously in one single commit, those involved in the upgrade path
+ are also pulled.
+
+ [Test Case]
+
+ Use `iw` to enumerate supported WiFi 6E band:
+
+ $ iw reg get
+ global
+ country : DFS-FCC
+ ...
+ (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
+
+ [Where problems could occur]
+
+ Currently linux-5.15 has FW API 66, linux-hwe-5.19 or above has 72,
+ linux-6.3 has 74, and linux-unstable (v6.4) or above has 78, so this
+ will update iwlwifi firmware usage for kernels <= 6.2 in Jammy, e.g.
+ linux-oem-6.1, linux-5.15.
+
+ [Other Info]
+
+ Blobs with FW APIs >= 72 do no harm to jammy kernels, but will be
+ referenced in oem-6.5 if planned.
+
+ These commits have been included in linux-firmware/lunar, so only Jammy
+ is nominated for fix.
+
+ == original bug report ==
+
AX210:
-72 ucode:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0-72.ucode?id=4309412c0d872897dc913c7d2797bb5ce05893ad
pnvm:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81
AX211:
-72 ucode:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f
pnvm:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81
AX411:
-72 ucode:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f
pnvm:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0.pnvm?id=78a8782a9e51e502a6ed267d270c6925fb738805
--
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/2020627
Title:
upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia
and Morocco
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Jammy:
In Progress
Bug description:
[SRU Justification]
[Impact]
iwlwifi takes firmware updates to support WiFi 6E in Malaysia and
Morocco. The models in concern are AX210 (iwlwifi-ty-a0-gf-a0-*),
AX211 (iwlwifi-so-a0-gf-a0-*) and AX411 (iwlwifi-so-a0-gf4-a0-*).
[Fix]
pnvm along with the ucode firmware from upstream commit 5bc279fb161d
("iwlwifi: update core69 and core72 firmwares for So device") are
required. While the pnvm and ucode blobs may not be upgraded
simultaneously in one single commit, those involved in the upgrade
path are also pulled.
[Test Case]
Use `iw` to enumerate supported WiFi 6E band:
$ iw reg get
global
country : DFS-FCC
...
(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
[Where problems could occur]
Currently linux-5.15 has FW API 66, linux-hwe-5.19 or above has 72,
linux-6.3 has 74, and linux-unstable (v6.4) or above has 78, so this
will update iwlwifi firmware usage for kernels <= 6.2 in Jammy, e.g.
linux-oem-6.1, linux-5.15.
[Other Info]
Blobs with FW APIs >= 72 do no harm to jammy kernels, but will be
referenced in oem-6.5 if planned.
These commits have been included in linux-firmware/lunar, so only
Jammy is nominated for fix.
== original bug report ==
AX210:
-72 ucode:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0-72.ucode?id=4309412c0d872897dc913c7d2797bb5ce05893ad
pnvm:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81
AX211:
-72 ucode:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f
pnvm:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81
AX411:
-72 ucode:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f
pnvm:
[Kernel-packages] [Bug 2024469] [NEW] Mantic update: v6.3.6 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: v6.3.6 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Mantic) 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 Mantic) 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/2024469 Title: Mantic update: v6.3.6 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: 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: v6.3.6 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024469/+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 2024470] [NEW] Mantic update: v6.3.7 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: v6.3.7 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Mantic) 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 Mantic) 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/2024470 Title: Mantic update: v6.3.7 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: 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: v6.3.7 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024470/+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 2024471] [NEW] Mantic update: v6.3.8 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: v6.3.8 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Mantic) 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 Mantic) 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/2024471 Title: Mantic update: v6.3.8 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: 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: v6.3.8 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024471/+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 1952006] Re: [TGL][ADL] ACRN hypervisor support
** Also affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-intel-iotg (Ubuntu) Status: New => Invalid ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: hwe-next ** No longer affects: linux (Ubuntu) ** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => Fix Released ** No longer affects: linux (Ubuntu Jammy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1952006 Title: [TGL][ADL] ACRN hypervisor support Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: Fix Released Bug description: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable ACRN hypervisor [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/1952006/+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 2020702] Re: Jammy update: v6.1.30 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2020702
Title:
Jammy update: v6.1.30 upstream stable release
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
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:
v6.1.30 upstream stable release
from git://git.kernel.org/
Linux 6.1.30
drm/amdgpu: reserve the old gc_11_0_*_mes.bin
drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
drm/amdgpu: declare firmware for new MES 11.0.4
crypto: testmgr - fix RNG performance in fuzz tests
remoteproc: imx_dsp_rproc: Fix kernel test robot sparse warning
rethook, fprobe: do not trace rethook related functions
rethook: use preempt_{disable, enable}_notrace in rethook_trampoline_handler
arm64: mte: Do not set PG_mte_tagged if tags were not initialized
s390/qdio: fix do_sqbs() inline assembly constraint
s390/crypto: use vector instructions only if available for ChaCha20
s390/dasd: fix command reject error on ESE devices
nilfs2: fix use-after-free bug of nilfs_root in nilfs_evict_inode()
powerpc/64s/radix: Fix soft dirty tracking
tpm/tpm_tis: Disable interrupts for more Lenovo devices
powerpc/iommu: Incorrect DDW Table is referenced for SR-IOV device
powerpc/iommu: DMA address offset is incorrectly calculated with 2MB TCEs
dt-bindings: ata: ahci-ceva: Cover all 4 iommus entries
drm/amdgpu/gfx11: update gpu_clock_counter logic
drm/amdgpu: refine get gpu clock counter method
drm/amdgpu/gfx11: Adjust gfxoff before powergating on gfx11 as well
drm/amdgpu/gfx10: Disable gfxoff before disabling powergating.
drm/amdgpu/gmc11: implement get_vbios_fb_size()
drm/amd/pm: fix possible power mode mismatch between driver and PMFW
ceph: force updating the msg pointer in non-split case
vc_screen: reload load of struct vc_data pointer in vcs_write() to avoid UAF
thunderbolt: Clear registers properly when auto clear isn't in use
serial: qcom-geni: fix enabling deactivated interrupt
serial: 8250_exar: Add support for USR298x PCI Modems
serial: Add support for Advantech PCI-1611U card
mm: fix zswap writeback race condition
maple_tree: make maple state reusable after mas_empty_area()
statfs: enforce statfs[64] structure initialization
KVM: Fix vcpu_array[0] races
ksmbd: fix global-out-of-bounds in smb2_find_context_vals
ksmbd: fix wrong UserName check in session_user
ksmbd: allocate one more byte for implied bcc[0]
ksmbd: smb2: Allow messages padded to 8byte boundary
SMB3: drop reference to cfile before sending oplock break
SMB3: Close all deferred handles of inode in case of handle lease break
wifi: rtw88: use work to update rate to avoid RCU warning
can: kvaser_pciefd: Disable interrupts in probe error path
can: kvaser_pciefd: Do not send EFLUSH command on TFD interrupt
can: kvaser_pciefd: Clear listen-only bit if not explicitly requested
can: kvaser_pciefd: Empty SRB buffer in probe
can: kvaser_pciefd: Call request_irq() before enabling interrupts
can: kvaser_pciefd: Set CAN_STATE_STOPPED in kvaser_pciefd_stop()
can: isotp: recvmsg(): allow MSG_CMSG_COMPAT flag
can: j1939: recvmsg(): allow MSG_CMSG_COMPAT flag
ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop
ALSA: hda/realtek: Add quirk for HP EliteBook G10 laptops
ALSA: hda/realtek: Add quirk for 2nd ASUS GU603
ALSA: hda/realtek: Add a quirk for HP EliteDesk 805
ALSA: hda/realtek: Add quirk for Clevo L140AU
ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table
ALSA: hda: Fix Oops by 9.1 surround channel names
xhci: Fix incorrect tracking of free space on transfer rings
xhci-pci: Only run d3cold avoidance quirk for s2idle
Revert "usb: gadget: udc: core: Invoke usb_gadget_connect only when started"
Revert "usb: gadget: udc: core: Prevent redundant calls to pullup"
usb: typec: altmodes/displayport: fix pin_assignment_show
usb: gadget: u_ether: Fix host MAC address case
usb: dwc3: debugfs: Resume dwc3 before accessing registers
usb: dwc3: gadget: Improve dwc3_gadget_suspend() and dwc3_gadget_resume()
USB: UHCI: adjust zhaoxin UHCI controllers OverCurrent bit value
usb-storage: fix deadlock when a scsi command timeouts more than once
USB: usbtmc: Fix direction for 0-length ioctl control messages
ALSA:
[Kernel-packages] [Bug 2021945] Re: Jammy update: v6.1.31 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2021945 Title: Jammy update: v6.1.31 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed 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: v6.1.31 upstream stable release from git://git.kernel.org/ Linux 6.1.31 net: phy: mscc: add VSC8502 to MODULE_DEVICE_TABLE 3c589_cs: Fix an error handling path in tc589_probe() net/smc: Reset connection when trying to use SMCRv2 fails. regulator: mt6359: add read check for PMIC MT6359 firmware: arm_ffa: Set reserved/MBZ fields to zero in the memory descriptors arm64: dts: imx8mn-var-som: fix PHY detection bug by adding deassert delay net/mlx5: Devcom, serialize devcom registration net/mlx5: Devcom, fix error flow in mlx5_devcom_register_device net/mlx5: Collect command failures data only for known commands net/mlx5: Fix error message when failing to allocate device memory net/mlx5: DR, Check force-loopback RC QP capability independently from RoCE net/mlx5: Handle pairing of E-switch via uplink un/load APIs net/mlx5: DR, Fix crc32 calculation to work on big-endian (BE) CPUs net/mlx5e: do as little as possible in napi poll when budget is 0 net/mlx5e: Use correct encap attribute during invalidation net/mlx5e: Fix deadlock in tc route query code net/mlx5e: Fix SQ wake logic in ptp napi_poll context platform/mellanox: mlxbf-pmc: fix sscanf() error checking forcedeth: Fix an error handling path in nv_probe() sctp: fix an issue that plpmtu can never go to complete state cxl: Wait Memory_Info_Valid before access memory related info ASoC: Intel: avs: Access path components under lock ASoC: Intel: avs: Fix declaration of enum avs_channel_config ASoC: Intel: Skylake: Fix declaration of enum skl_ch_cfg x86/show_trace_log_lvl: Ensure stack pointer is aligned, again xen/pvcalls-back: fix double frees with pvcalls_new_active_socket() x86/pci/xen: populate MSI sysfs entries ARM: dts: imx6qdl-mba6: Add missing pvcie-supply regulator coresight: Fix signedness bug in tmc_etr_buf_insert_barrier_packet() platform/x86: ISST: Remove 8 socket limit regulator: pca9450: Fix BUCK2 enable_mask fs: fix undefined behavior in bit shift for SB_NOUSER firmware: arm_ffa: Fix FFA device names for logical partitions firmware: arm_ffa: Check if ffa_driver remove is present before executing optee: fix uninited async notif value power: supply: sbs-charger: Fix INHIBITED bit for Status reg power: supply: bq24190: Call power_supply_changed() after updating input current power: supply: bq25890: Call power_supply_changed() after updating input current or voltage power: supply: bq27xxx: After charger plug in/out wait 0.5s for things to stabilize power: supply: bq27xxx: Ensure power_supply_changed() is called on current sign changes power: supply: bq27xxx: Move bq27xxx_battery_update() down power: supply: bq27xxx: Add cache parameter to bq27xxx_battery_current_and_status() power: supply: bq27xxx: Fix poll_interval handling and races on remove power: supply: bq27xxx: Fix I2C IRQ race on remove power: supply: bq27xxx: Fix bq27xxx_battery_update() race condition power: supply: mt6360: add a check of devm_work_autocancel in mt6360_charger_probe power: supply: leds: Fix blink to LED on transition cifs: mapchars mount option ignored ipv6: Fix out-of-bounds access in ipv6_find_tlv() lan966x: Fix unloading/loading of the driver bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps bpf: Fix mask generation for 32-bit narrow loads of 64-bit fields octeontx2-pf: Fix TSOv6 offload selftests: fib_tests: mute cleanup error message drm: fix drmm_mutex_init() net: fix skb leak in __skb_tstamp_tx() ASoC: lpass: Fix for KASAN use_after_free out of bounds media: radio-shark: Add endpoint checks USB: sisusbvga: Add endpoint checks USB: core: Add routines for endpoint checks in old drivers udplite: Fix NULL pointer dereference in __sk_mem_raise_allocated(). net: fix stack overflow when LRO is disabled for virtual interfaces fbdev: udlfb: Fix endpoint check debugobjects: Don't wake up kswapd from fill_pool() irqchip/mips-gic: Use raw spinlock for gic_lock irqchip/mips-gic: Don't touch
[Kernel-packages] [Bug 2023264] Re: Jammy update: v6.1.32 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2023264
Title:
Jammy update: v6.1.32 upstream stable release
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
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:
v6.1.32 upstream stable release
from git://git.kernel.org/
Linux 6.1.32
tools headers UAPI: Sync the linux/in.h with the kernel sources
netfilter: ctnetlink: Support offloaded conntrack entry deletion
cpufreq: amd-pstate: Add ->fast_switch() callback
cpufreq: amd-pstate: Update policy->cur in amd_pstate_adjust_perf()
block: fix bio-cache for passthru IO
Revert "thermal/drivers/mellanox: Use generic thermal_zone_get_trip()
function"
bluetooth: Add cmd validity checks at the start of hci_sock_ioctl()
drm/amd: Don't allow s0ix on APUs older than Raven
octeontx2-af: Add validation for lmac type
RDMA/rxe: Fix the error "trying to register non-static key in
rxe_cleanup_task"
wifi: iwlwifi: mvm: fix potential memory leak
wifi: iwlwifi: mvm: support wowlan info notification version 2
wifi: rtw89: correct 5 MHz mask setting
net: phy: mscc: enable VSC8501/2 RGMII RX clock
page_pool: fix inconsistency for page_pool_ring_[un]lock()
net: page_pool: use in_softirq() instead
vfio/type1: check pfn valid before converting to struct page
blk-mq: fix race condition in active queue accounting
bpf, sockmap: Incorrectly handling copied_seq
bpf, sockmap: Wake up polling after data copy
bpf, sockmap: TCP data stall on recv before accept
bpf, sockmap: Handle fin correctly
bpf, sockmap: Improved check for empty queue
bpf, sockmap: Reschedule is now done through backlog
bpf, sockmap: Convert schedule_work into delayed_work
bpf, sockmap: Pass skb ownership through read_skb
gpio-f7188x: fix chip name and pin count on Nuvoton chip
net/mlx5: E-switch, Devcom, sync devcom events and devcom comp register
tls: rx: strp: preserve decryption status of skbs when needed
tls: rx: strp: factor out copying skb data
tls: rx: strp: force mixed decrypted records into copy mode
tls: rx: strp: fix determining record length in copy mode
tls: rx: strp: set the skb->len of detached / CoW'ed skbs
tls: rx: device: fix checking decryption status
platform/x86/amd/pmf: Fix CnQF and auto-mode after resume
selftests/bpf: Fix pkg-config call building sign-file
firmware: arm_ffa: Fix usage of partition info get count flag
ipv{4,6}/raw: fix output xfrm lookup wrt protocol
inet: Add IP_LOCAL_PORT_RANGE socket option
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2023264/+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 2021572] Re: dGPU cannot resume because system firmware stuck in IPCS method
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2021572 Title: dGPU cannot resume because system firmware stuck in IPCS method Status in HWE Next: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] When a dGPU on a laptop is in PCIe D3cold and TBT port is connected to a monitor via a cable, unplugging the cable will make the dGPU unable to resume to D0. [Fix] There's a part of system firmware, IOM, need the driver to disconnect all TBT/Type-C phy to let dGPU function normally. [Test] With the fix applied, the dGPU continues to work after replugging video cable many times. [Where problems could occur] The fix is composed of several overhaul, so it's likely to regression i915 GFX driver. To limit the impact, only target OEM kernel for now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2021572/+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 2024126] Re: eDP power on flow enhancement to speed up kernel boot time
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2024126 Title: eDP power on flow enhancement to speed up kernel boot time Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] eDP power on flow enhancement to speed up kernel boot time. This commit is recommended by Intel. [Fix] The commit below is from 6.2-rc1 36d357169891 drm/i915/edp: wait power off delay at driver remove to optimize probe [Test] No [Where problems could occur] The assumption of the patch should be always correct, we don't have to wait the panel to be powered off when boots up, the panel power should has been switched off right before boots up. And the panel_power_off_time value will be set to the desired value in wait_panel_power_cycle(). So, should be pretty safe to include this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2024126/+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 2024166] Re: Jammy update: v6.1.34 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2024166 Title: Jammy update: v6.1.34 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed 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: v6.1.34 upstream stable release from git://git.kernel.org/ Linux 6.1.34 Revert "staging: rtl8192e: Replace macro RTL_PCI_DEVICE with PCI_DEVICE" wifi: rtw88: correct PS calculation for SUPPORTS_DYNAMIC_PS wifi: rtw89: correct PS calculation for SUPPORTS_DYNAMIC_PS ext4: only check dquot_initialize_needed() when debugging Revert "ext4: don't clear SB_RDONLY when remounting r/w until quota is re-enabled" ksmbd: check the validation of pdu_size in ksmbd_conn_handler_loop ksmbd: fix out-of-bound read in parse_lease_state() ksmbd: fix out-of-bound read in deassemble_neg_contexts() vhost_vdpa: support PACKED when setting-getting vring_base vhost: support PACKED when setting-getting vring_base vduse: avoid empty string for dev name riscv: fix kprobe __user string arg print fault issue soundwire: stream: Add missing clear of alloc_slave_rt eeprom: at24: also select REGMAP riscv: mm: Ensure prot of VM_WRITE and VM_EXEC must be readable i2c: sprd: Delete i2c adapter in .remove's error path gpio: sim: fix memory corruption when adding named lines and unnamed hogs firmware: arm_ffa: Set handle field to zero in memory descriptor i2c: mv64xxx: Fix reading invalid status value in atomic mode arm64: dts: imx8mn-beacon: Fix SPI CS pinmux blk-mq: fix blk_mq_hw_ctx active request accounting ASoC: simple-card-utils: fix PCM constraint error check ASoC: mediatek: mt8195: fix use-after-free in driver remove path ASoC: mediatek: mt8195-afe-pcm: Convert to platform remove callback returning void arm64: dts: imx8-ss-dma: assign default clock rate for lpuarts arm64: dts: imx8qm-mek: correct GPIOs for USDHC2 CD and WP signals arm64: dts: qcom: sc7180-lite: Fix SDRAM freq for misidentified sc7180-lite boards ASoC: codecs: wsa881x: do not set can_multi_write flag ASoC: codecs: wsa883x: do not set can_multi_write flag ARM: dts: at91: sama7g5ek: fix debounce delay property for shdwc ARM: at91: pm: fix imbalanced reference counter for ethernet devices arm64: dts: qcom: sc8280xp: Flush RSC sleep & wake votes mm: page_table_check: Ensure user pages are not slab pages mm: page_table_check: Make it dependent on EXCLUSIVE_SYSTEM_RAM usb: usbfs: Use consistent mmap functions usb: usbfs: Enforce page requirements for mmap pinctrl: meson-axg: add missing GPIOA_18 gpio group soc: qcom: icc-bwmon: fix incorrect error code passed to dev_err_probe() virtio_net: use control_buf for coalesce params rbd: get snapshot context after exclusive lock is ensured to be held rbd: move RBD_OBJ_FLAG_COPYUP_ENABLED flag setting tee: amdtee: Add return_origin to 'struct tee_cmd_load_ta' Bluetooth: hci_qca: fix debugfs registration Bluetooth: fix debugfs registration Bluetooth: Fix use-after-free in hci_remove_ltk/hci_remove_irk s390/dasd: Use correct lock while counting channel queue length ceph: fix use-after-free bug for inodes when flushing capsnaps selftests: mptcp: update userspace pm subflow tests selftests: mptcp: update userspace pm addr tests mptcp: update userspace pm infos mptcp: add address into userspace pm list mptcp: only send RM_ADDR in nl_cmd_remove can: j1939: avoid possible use-after-free when j1939_can_rx_register fails can: j1939: change j1939_netdev_lock type to mutex can: j1939: j1939_sk_send_loop_abort(): improved error queue handling in J1939 Socket wifi: iwlwifi: mvm: Fix -Warray-bounds bug in iwl_mvm_wait_d3_notif() drm/amd/display: Reduce sdp bw after urgent to 90% drm/amd/pm: Fix power context allocation in SMU13 drm/amdgpu: change reserved vram info print drm/amdgpu: fix xclk freq on CHIP_STONEY drm/amd/pm: conditionally disable pcie lane switching for some sienna_cichlid SKUs drm/i915/gt: Use the correct error value when kernel_context() fails ALSA: hda/realtek: Add quirks for Asus ROG 2024 laptops using CS35L41 ALSA: hda/realtek: Add Lenovo P3 Tower platform ALSA: hda/realtek: Add a quirk for HP Slim Desktop S01 ALSA: ice1712,ice1724: fix the kcontrol->id
[Kernel-packages] [Bug 2024165] Re: Jammy update: v6.1.33 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2024165
Title:
Jammy update: v6.1.33 upstream stable release
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
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:
v6.1.33 upstream stable release
from git://git.kernel.org/
Linux 6.1.33
ext4: enable the lazy init thread when remounting read/write
selftests: mptcp: join: avoid using 'cmp --bytes'
selftests: mptcp: simult flows: skip if MPTCP is not supported
selftests: mptcp: diag: skip if MPTCP is not supported
arm64: efi: Use SMBIOS processor version to key off Ampere quirk
tls: rx: strp: don't use GFP_KERNEL in softirq context
xfs: verify buffer contents when we skip log replay
drm/amd/display: Have Payload Properly Created After Resume
iommu/amd/pgtbl_v2: Fix domain max address
tpm, tpm_tis: Request threaded interrupt handler
regmap: Account for register length when chunking
fs/ntfs3: Validate MFT flags before replaying logs
KEYS: asymmetric: Copy sig and digest in public_key_verify_signature()
ksmbd: fix multiple out-of-bounds read during context decoding
ksmbd: fix slab-out-of-bounds read in smb2_handle_negotiate
ksmbd: fix incorrect AllocationSize set in smb2_get_info
ksmbd: fix UAF issue from opinfo->conn
ksmbd: fix credit count leakage
KVM: x86: Account fastpath-only VM-Exits in vCPU stats
KVM: arm64: Populate fault info for watchpoint
test_firmware: fix the memory leak of the allocated firmware buffer
test_firmware: fix a memory leak with reqs buffer
powerpc/xmon: Use KSYM_NAME_LEN in array size
serial: cpm_uart: Fix a COMPILE_TEST dependency
serial: 8250_tegra: Fix an error handling path in tegra_uart_probe()
fbcon: Fix null-ptr-deref in soft_cursor
ext4: add lockdep annotations for i_data_sem for ea_inode's
ext4: disallow ea_inodes with extended attributes
ext4: set lockdep subclass for the ea_inode in ext4_xattr_inode_cache_find()
ext4: add EA_INODE checking to ext4_iget()
mptcp: fix active subflow finalization
mptcp: fix connect timeout handling
selftests: mptcp: userspace pm: skip if MPTCP is not supported
selftests: mptcp: sockopt: skip if MPTCP is not supported
selftests: mptcp: join: skip if MPTCP is not supported
selftests: mptcp: pm nl: skip if MPTCP is not supported
selftests: mptcp: connect: skip if MPTCP is not supported
tracing/probe: trace_probe_primary_from_call(): checked list_first_entry
tracing/histograms: Allow variables to have some modifiers
tracing/timerlat: Always wakeup the timerlat thread
mtdchar: mark bits of ioctl handler noinline
selinux: don't use make's grouped targets feature yet
io_uring: undeprecate epoll_ctl support
riscv: perf: Fix callchain parse error with kernel tracepoint events
tpm, tpm_tis: correct tpm_tis_flags enumeration values
iommu/amd: Fix domain flush size when syncing iotlb
powerpc/iommu: Limit number of TCEs to 512 for H_STUFF_TCE hcall
block: fix revalidate performance regression
phy: qcom-qmp-pcie-msm8996: fix init-count imbalance
phy: qcom-qmp-combo: fix init-count imbalance
btrfs: fix csum_tree_block page iteration to avoid tripping on
-Werror=array-bounds
tty: serial: fsl_lpuart: use UARTCTRL_TXINV to send break instead of
UARTCTRL_SBK
mmc: pwrseq: sd8787: Fix WILC CHIP_EN and RESETN toggling order
mmc: vub300: fix invalid response handling
x86/mtrr: Revert 90b926e68f50 ("x86/pat: Fix pat_x_mtrr_type() for MTRR
disabled case")
drm/amd/pm: reverse mclk and fclk clocks levels for renoir
drm/amd/pm: reverse mclk and fclk clocks levels for yellow carp
drm/amd/pm: reverse mclk clocks levels for SMU v13.0.5
drm/amd/pm: resolve reboot exception for si oland
drm/amd/pm: reverse mclk and fclk clocks levels for vangogh
drm/amd/pm: reverse mclk and fclk clocks levels for SMU v13.0.4
drm/amdgpu: enable tmz by default for GC 11.0.1
ata: libata-scsi: Use correct device no in ata_find_dev()
scsi: stex: Fix gcc 13 warnings
misc: fastrpc: reject new invocations during device removal
misc: fastrpc: return -EPIPE to invocations on device removal
md/raid5: fix miscalculation of 'end_sector' in raid5_read_one_chunk()
usb: gadget: f_fs: Add unbind event before functionfs_unbind
usb: cdns3: fix
[Kernel-packages] [Bug 2024273] Re: Fix eDP only displays 3/4 area after switching to mirror mode with external HDMI 4K monitor
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2024273 Title: Fix eDP only displays 3/4 area after switching to mirror mode with external HDMI 4K monitor Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] Panel on laptops connect to some 4K monitors via HDMI only display 3/4 area on eDP after switching to mirror mode. [Fix] Backport a fix from Intel on https://cgit.freedesktop.org/drm-tip/commit/?id=a2da67028cd05516343533c1609fcaf037237fed. [Test] 1. Power on the laptop 2. Connect a 4K monitor (4k Benq EL2870U, 4k HP z27Kg3, 2k ASUS PA27AC) to the laptop with HDMI cable. 3. Switch to mirror mode from default Joint Mode 4. Verify there's no obvious blank space on the leftmost/rightmost side of the laptop's panel. [Where problems could occur] Only observed after connecting with some particular 4K monitors. It's a generic fix to accept arbitrary refresh rate for more advanced panels. Should be low risk to old machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024273/+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 2024449] Re: Fix audio white noise while play from HDMI/DP port on AMD W6300 gfx
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2024449 Title: Fix audio white noise while play from HDMI/DP port on AMD W6300 gfx Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] When playing audio from HDMI/DP port on AMD W6300 gfx, there's always white noise. It will disappear after suspend/resume. Disabling ASPM on W6300 also fix this. [Fix] Backport a fix from AMD on https://www.spinics.net/lists/amd-gfx/msg93796.html https://www.spinics.net/lists/amd-gfx/msg93797.html [Test] 1. Power on the Desktop installed with AMD W6300 gfx 2. Connect a monitor with either HDMI or DP cable. 3. Change the audio output port to HDMI/DP and play audio. 4. Verify if there's noise from the audio output [Where problems could occur] Only observed on AMD W6300. The fix revise the ASPM L1 inactivily time out on NAVI10 GPU series. The impact should be only for this particular GPU series. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024449/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@raj Ubuntu 22 comes with 5.19 kernel. Driver https://github.com/Kvalme/uvc.git only for 6.2 and 6.3 kernels. Try to use @giuliano69 #0 sulution with his bash script. Or try to use #19 solution and below posts. I only try to compile this module on 6.2.0 kernel. -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06
[Kernel-packages] [Bug 2018448] Re: Flickering screen on lenovo x1 carbon 10th, fault errors in dmesg
The other thing I changed was move to wayland, due to an unrelated problem, so maybe that was the fix? Anyway, end result is the same, the flickering is gone. ** Changed in: linux (Ubuntu) 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/2018448 Title: Flickering screen on lenovo x1 carbon 10th, fault errors in dmesg Status in linux package in Ubuntu: Fix Released Bug description: Hi, in lunar (haven't tried others yet), the laptop screen flickers every few minutes, and I get these errors in dmesg when that happens: [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 googling found some hits, but this one seems promising, as it's recent, and has the exact same error message: https://www.spinics.net/lists/intel-gfx/msg317397.html If that is not applied in the lunar kernel, and someone builds me one with the patch applied, I can easily try it. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andreas4727 F pipewire andreas4730 F wireplumber /dev/snd/seq:andreas4727 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 4 07:51:38 2023 MachineType: LENOVO 21CC0093BR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 03/02/2023 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET72W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CC0093BR dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrN3AET72W(1.37):bd03/02/2023:br1.37:efr1.18:svnLENOVO:pn21CC0093BR:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CC0093BR:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CC_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CC0093BR dmi.product.sku: LENOVO_MT_21CC_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018448/+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 2018448] Re: Flickering screen on lenovo x1 carbon 10th, fault errors in dmesg
I'm currently on 6.2.0-23 on Lunar, official update, and I don't see the flickering anymore. I haven't checked if the patch mentioned earlier in the bug is applied, but I'm happy with this update and will close the bug. -- 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/2018448 Title: Flickering screen on lenovo x1 carbon 10th, fault errors in dmesg Status in linux package in Ubuntu: Fix Released Bug description: Hi, in lunar (haven't tried others yet), the laptop screen flickers every few minutes, and I get these errors in dmesg when that happens: [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 [qui mai 4 22:07:56 2023] i915 :00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x0080 googling found some hits, but this one seems promising, as it's recent, and has the exact same error message: https://www.spinics.net/lists/intel-gfx/msg317397.html If that is not applied in the lunar kernel, and someone builds me one with the patch applied, I can easily try it. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andreas4727 F pipewire andreas4730 F wireplumber /dev/snd/seq:andreas4727 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 4 07:51:38 2023 MachineType: LENOVO 21CC0093BR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 03/02/2023 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET72W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CC0093BR dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrN3AET72W(1.37):bd03/02/2023:br1.37:efr1.18:svnLENOVO:pn21CC0093BR:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CC0093BR:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CC_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CC0093BR dmi.product.sku: LENOVO_MT_21CC_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018448/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@BlindB0 I installed Ubuntu 22 Lts version and now showing me this ake -C /lib/modules/5.19.0-45-generic/build M=/home/raj/uvc modules make[1]: Entering directory '/usr/src/linux-headers-5.19.0-45-generic' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0 You are using: gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0 CC [M] /home/raj/uvc/uvc_driver.o /home/raj/uvc/uvc_driver.c:23:10: fatal error: media/v4l2-uvc.h: No such file or directory 23 | #include | ^~ compilation terminated. make[2]: *** [scripts/Makefile.build:257: /home/raj/uvc/uvc_driver.o] Error 1 make[1]: *** [Makefile:1857: /home/raj/uvc] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.19.0-45-generic' make: *** [Makefile:8: all] Error 2 -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash
[Kernel-packages] [Bug 2023986] Re: Drivers not working using kernel linux-image-6.2.0-1003-oracle
Sorry for the second post just for an upload. I don't understand how to upload multiple files, if possible. The file is just copy of upgrade request failure in terminal. ** Attachment added: "Upgrade kernel failure.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oracle/+bug/2023986/+attachment/5680966/+files/Upgrade%20kernel%20failure.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2023986 Title: Drivers not working using kernel linux-image-6.2.0-1003-oracle Status in linux-signed-oracle package in Ubuntu: Confirmed Bug description: My Ubuntu 23.04 installed two kernels linux-image-6.2.0-1003-oracle and linux-image-6.2.0-1003-lowlatency using software updater along with other updates. After install and restart, most drivers including wifi, bluetooth, touchpad and ethernet stopped working. Rebooting using 6.2.0-1003-lowlatency or 6.2.0-20-generic solved the driver issues. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-1003-oracle 6.2.0-1003.3 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 Uname: Linux 6.2.0-1003-lowlatency x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 15 16:34:56 2023 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oracle/+bug/2023986/+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 2023986] Re: Drivers not working using kernel linux-image-6.2.0-1003-oracle
I sure would like to see what command they used to undo the hasty incomplete update. I am having essentially, if not the same issue. Using the same workaround. Some drivers are broke. Can't update anything. ** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oracle/+bug/2023986/+attachment/5680965/+files/history.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2023986 Title: Drivers not working using kernel linux-image-6.2.0-1003-oracle Status in linux-signed-oracle package in Ubuntu: Confirmed Bug description: My Ubuntu 23.04 installed two kernels linux-image-6.2.0-1003-oracle and linux-image-6.2.0-1003-lowlatency using software updater along with other updates. After install and restart, most drivers including wifi, bluetooth, touchpad and ethernet stopped working. Rebooting using 6.2.0-1003-lowlatency or 6.2.0-20-generic solved the driver issues. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-1003-oracle 6.2.0-1003.3 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 Uname: Linux 6.2.0-1003-lowlatency x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 15 16:34:56 2023 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oracle/+bug/2023986/+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 2024449] 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 2024449 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 ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2024449 Title: Fix audio white noise while play from HDMI/DP port on AMD W6300 gfx Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-oem-6.1 source package in Jammy: In Progress Bug description: [Impact] When playing audio from HDMI/DP port on AMD W6300 gfx, there's always white noise. It will disappear after suspend/resume. Disabling ASPM on W6300 also fix this. [Fix] Backport a fix from AMD on https://www.spinics.net/lists/amd-gfx/msg93796.html https://www.spinics.net/lists/amd-gfx/msg93797.html [Test] 1. Power on the Desktop installed with AMD W6300 gfx 2. Connect a monitor with either HDMI or DP cable. 3. Change the audio output port to HDMI/DP and play audio. 4. Verify if there's noise from the audio output [Where problems could occur] Only observed on AMD W6300. The fix revise the ASPM L1 inactivily time out on NAVI10 GPU series. The impact should be only for this particular GPU series. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024449/+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 2024449] Re: Fix audio white noise while play from HDMI/DP port on AMD W6300 gfx
** Tags added: oem-priority originate-from-2012625 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2024449 Title: Fix audio white noise while play from HDMI/DP port on AMD W6300 gfx Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-oem-6.1 source package in Jammy: In Progress Bug description: [Impact] When playing audio from HDMI/DP port on AMD W6300 gfx, there's always white noise. It will disappear after suspend/resume. Disabling ASPM on W6300 also fix this. [Fix] Backport a fix from AMD on https://www.spinics.net/lists/amd-gfx/msg93796.html https://www.spinics.net/lists/amd-gfx/msg93797.html [Test] 1. Power on the Desktop installed with AMD W6300 gfx 2. Connect a monitor with either HDMI or DP cable. 3. Change the audio output port to HDMI/DP and play audio. 4. Verify if there's noise from the audio output [Where problems could occur] Only observed on AMD W6300. The fix revise the ASPM L1 inactivily time out on NAVI10 GPU series. The impact should be only for this particular GPU series. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024449/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@raj I just try to compile driver on clean Ubuntu 23.04 with 6.2.0-23-generic kernel. Got the same error. With quick googling found this solution: apt install dwarves cp /sys/kernel/btf/vmlinux /usr/lib/modules/`uname -r`/build/ So, with this steps I can compile it without errors: sudo apt-get install dwarves build-essential sudo cp /sys/kernel/btf/vmlinux /usr/lib/modules/`uname -r`/build/ git clone https://github.com/Kvalme/uvc.git cd ./uvc/ git checkout 5ea688c make Hope it help you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably
[Kernel-packages] [Bug 2024449] [NEW] Fix audio white noise while play from HDMI/DP port on AMD W6300 gfx
Public bug reported: [Impact] When playing audio from HDMI/DP port on AMD W6300 gfx, there's always white noise. It will disappear after suspend/resume. Disabling ASPM on W6300 also fix this. [Fix] Backport a fix from AMD on https://www.spinics.net/lists/amd-gfx/msg93796.html https://www.spinics.net/lists/amd-gfx/msg93797.html [Test] 1. Power on the Desktop installed with AMD W6300 gfx 2. Connect a monitor with either HDMI or DP cable. 3. Change the audio output port to HDMI/DP and play audio. 4. Verify if there's noise from the audio output [Where problems could occur] Only observed on AMD W6300. The fix revise the ASPM L1 inactivily time out on NAVI10 GPU series. The impact should be only for this particular GPU series. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024449 Title: Fix audio white noise while play from HDMI/DP port on AMD W6300 gfx Status in linux package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: In Progress Bug description: [Impact] When playing audio from HDMI/DP port on AMD W6300 gfx, there's always white noise. It will disappear after suspend/resume. Disabling ASPM on W6300 also fix this. [Fix] Backport a fix from AMD on https://www.spinics.net/lists/amd-gfx/msg93796.html https://www.spinics.net/lists/amd-gfx/msg93797.html [Test] 1. Power on the Desktop installed with AMD W6300 gfx 2. Connect a monitor with either HDMI or DP cable. 3. Change the audio output port to HDMI/DP and play audio. 4. Verify if there's noise from the audio output [Where problems could occur] Only observed on AMD W6300. The fix revise the ASPM L1 inactivily time out on NAVI10 GPU series. The impact should be only for this particular GPU series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024449/+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 1968604] Re: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug
I've done some limited testing with a USB dongle that has that chip and was able to establish a BT connection. ** Tags added: verification-done-jammy verification-done-kinetic verification-done-lunar -- 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/1968604 Title: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-firmware source package in Lunar: Fix Committed Bug description: [Impact] I have usb bluetooth 5.0 dongle which uses Realtek RTL8761B chip. 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio USB adapter very often stops working, can't connect or find other bluetooth devices. The adapter can't work even after reboots. The following entries appear in the log: апр 11 13:47:14 desktop kernel: Bluetooth: hci0: command 0x2005 tx timeout апр 11 13:47:16 desktop kernel: Bluetooth: hci0: command 0x2041 tx timeout апр 11 13:47:18 desktop kernel: Bluetooth: hci0: command 0x2042 tx timeout Firmware loaded correctly, but something is not working. апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814 1) I use: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) linux-firmware: 20220329.git681281e4-0ubuntu1 3) What you expected to happen? I expect a well working bluetooth adapter. 4) What happened instead? My bluetooth adapter may work, may not. The adapter may stop finding and connecting to other devices. I've found the same bug https://bugzilla.kernel.org/show_bug.cgi?id=214111#c1 I've downloaded Windows's archive http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2021/05/ca0e770c-6a5d-4de0-b37a-f4b91cccd8c3_7778831d2b9d721cf94d5a8d8c0676ff1b96c874.cab I've unpacked file rtl8761b_mp_chip_bt40_fw_asic_rom_patch_new.dll and replaced /usr/lib/firmware/rtl_bt/rtl8761bu_fw.bin and deleted rtl8761bu_config.bin After I changed firmware my usb dongle work fine. Could you change firmware rtl8761bu_fw.bin rtl8761bu_config.bin to other correct version? Could you move Realtek's rtl_bt firmware or RTL8761B's firmware into separate packages. I will remove the RTL8761B firmware package and put them manually. bluetoothctl --version bluetoothctl: 5.64 hci0: Type: Primary Bus: USB BD Address: 00:E0:4C:FC:E2:03 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:5751 acl:49 sco:0 events:489 errors:0 TX bytes:219114 acl:398 sco:0 commands:83 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'desktop' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x97b LMP Version: 5.1 (0xa) Subversion: 0xec43 Manufacturer: Realtek Semiconductor Corporation (93) rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Realtek's worker updated these bad firmware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=45dc5f0b8e2f2d43312d22511cb26658b9ee2c80 [Test Case] Connect to and use a bluetooth device connected to a RTL8761B base USB BT controller. [Fix] Use latest rtl8761bu firmware blobs updates from linux-firmware. [Where Problems Could Occur] These firmwares are specific for the rtl8671b chips. So users of USB or UART BT controllers based on that chip could see problems when trying to connect to and use bluetooth devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1968604/+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 2023638] Re: Various backlight issues with the 6.0 kernel
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2023638 Title: Various backlight issues with the 6.0 kernel Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] There are some new patches for new method to decide which backlight driver should be registered introduced since 6.1. And we backport some of them to 6.0-oem kernel which are not enough to solved all backlight issues. 1. dell_laptop created a non-working backlight driver before nvidia is loaded, that leads to the system can't adjust the display brightness. 2. acpi_backlight0 sometimes will be generated together with intel_backlight. [Fix] Below 2 commits from v6.3-rc6 prevent the acpi_backlight from being registered automatically e506731c8f35 ACPI: video: Make acpi_backlight=video work independent from GPU driver 78dfc9d1d1ab ACPI: video: Add auto_detect arg to __acpi_video_get_backlight_type() Below patch prevents platform driver(dell_laptop) from creating backlight driver after win8. https://patchwork.kernel.org/project/linux-acpi/patch/20230608091258.7963-1-hdego...@redhat.com/ [Test] Verified on the dell platform which reports this issue. [Where problems could occur] The assumption of the not-yet-upstreamed commit regarding backlight control is that, after Windows 8, all laptop backlights are controlled either by ACPI or the native graphics driver. It impacts the laptops that do not follow the assumption and will lead to broken backlight interface. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023638/+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 2023946] Re: Nvidia 530 kernel driver is not installed/built
Incomplete: We'll need to see the DKMS build logs to determine which package is to blame. -- 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/2023946 Title: Nvidia 530 kernel driver is not installed/built Status in dkms package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-530 package in Ubuntu: Incomplete Bug description: ``` $ uname -a Linux khteh-p17-2i 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. ``` ``` $ prime-select query on-demand ``` ``` $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd25B8sv17AAsd22DEbc03sc00i00 vendor : NVIDIA Corporation model: GA107GLM [RTX A2000 Mobile] driver : nvidia-driver-510 - distro non-free driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-515-open - distro non-free driver : nvidia-driver-515-server - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-530 - distro non-free recommended driver : nvidia-driver-525-server - distro non-free driver : nvidia-driver-530-open - distro non-free driver : nvidia-driver-515 - distro non-free driver : nvidia-driver-470 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin ``` ``` $ dpkg -l | grep -i nvidia ii libaccinj64-11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA ACCINJ Library (64-bit) ii libcu++-dev 1.8.1-2 all NVIDIA C++ Standard Library ii libcublas11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLAS Library ii libcublaslt11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLASLt Library ii libcudart11.0:amd64 11.8.89~11.8.0-3 amd64NVIDIA CUDA Runtime Library ii libcufft10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFT Library ii libcufftw10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFTW Library ii libcuinj64-11.8:amd64 11.8.87~11.8.0-3 amd64NVIDIA CUINJ Library (64-bit) ii libcupti-dev:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface development files ii libcupti-doc 11.8.87~11.8.0-3 all NVIDIA CUDA Profiler Tools Interface documentation ii libcupti11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface runtime library ii libcurand10:amd64 11.1.1+~10.3.0.86~11.8.0-3 amd64NVIDIA cuRAND Library ii libcusolver11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVER Library ii libcusolvermg11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVERmg Library ii libcusparse11:amd64 11.7.5.86~11.8.0-3 amd64NVIDIA cuSPARSE Library ii libnppc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives core runtime library ii libnppial11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Arithmetic and Logic ii libnppicc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Color Conversion ii libnppidei11:amd6411.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Data Exchange and Initialization ii libnppif11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Filters ii libnppig11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Geometry transforms ii libnppim11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Morphological operations ii
[Kernel-packages] [Bug 2023946] Re: Nvidia 530 kernel driver is not installed/built
Why the kernels are installed isn't really important, just a curiosity. The nvidia driver should build and install more reliably regardless... ** Also affects: dkms (Ubuntu) Importance: Undecided Status: New ** Changed in: dkms (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-530 (Ubuntu) Status: Confirmed => Incomplete -- 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/2023946 Title: Nvidia 530 kernel driver is not installed/built Status in dkms package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-530 package in Ubuntu: Incomplete Bug description: ``` $ uname -a Linux khteh-p17-2i 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. ``` ``` $ prime-select query on-demand ``` ``` $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd25B8sv17AAsd22DEbc03sc00i00 vendor : NVIDIA Corporation model: GA107GLM [RTX A2000 Mobile] driver : nvidia-driver-510 - distro non-free driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-515-open - distro non-free driver : nvidia-driver-515-server - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-530 - distro non-free recommended driver : nvidia-driver-525-server - distro non-free driver : nvidia-driver-530-open - distro non-free driver : nvidia-driver-515 - distro non-free driver : nvidia-driver-470 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin ``` ``` $ dpkg -l | grep -i nvidia ii libaccinj64-11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA ACCINJ Library (64-bit) ii libcu++-dev 1.8.1-2 all NVIDIA C++ Standard Library ii libcublas11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLAS Library ii libcublaslt11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLASLt Library ii libcudart11.0:amd64 11.8.89~11.8.0-3 amd64NVIDIA CUDA Runtime Library ii libcufft10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFT Library ii libcufftw10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFTW Library ii libcuinj64-11.8:amd64 11.8.87~11.8.0-3 amd64NVIDIA CUINJ Library (64-bit) ii libcupti-dev:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface development files ii libcupti-doc 11.8.87~11.8.0-3 all NVIDIA CUDA Profiler Tools Interface documentation ii libcupti11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface runtime library ii libcurand10:amd64 11.1.1+~10.3.0.86~11.8.0-3 amd64NVIDIA cuRAND Library ii libcusolver11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVER Library ii libcusolvermg11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVERmg Library ii libcusparse11:amd64 11.7.5.86~11.8.0-3 amd64NVIDIA cuSPARSE Library ii libnppc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives core runtime library ii libnppial11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Arithmetic and Logic ii libnppicc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Color Conversion ii libnppidei11:amd6411.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Data Exchange and Initialization ii libnppif11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Filters ii libnppig11:amd64 11.8.0.86~11.8.0-3
[Kernel-packages] [Bug 2024443] [NEW] pi-kernel 5.15 on UC22 is missing most staging modules
Public bug reported: i recently recommended a TP-Link TL-WN722N to an UbuntuCore customer asking for a recommendation of a USB wifi adapter with external antenna for the RPi since i use this card in various RPi projects ... trying it on UC22 it turns out that the module driving this card is not included in the pi-kernel snap. in fact the staging dir seems to mostly be empty ... the same kernel on classic includes the needed r8188eu.ko module via the linux-modules-extra package. it seems like we do not include linux-modules-extra in the 5.15 pi- kernel snap at all which is a regression compared to former pi-kernel snaps where this wifi card works fine. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Description changed: i recently recommended a TP-Link TL-WN722N to an UbuntuCore customer asking for a recommendation of a USB wifi adapter with external antenna for the RPi since i use this card on various RPi projects ... - trying it on UC22 it tuns out that the module driving this card is not included in the pi-kernel snap. - in fact the staging dir seems to mostly be empty ... the same kernel on classic includes the needed r8188eu.ko mpodule via the linux-modules-extra package. + trying it on UC22 it tuns out that the module driving this card is not included in the pi-kernel snap. + in fact the staging dir seems to mostly be empty ... the same kernel on classic includes the needed r8188eu.ko module via the linux-modules-extra package. it seems like we do not include linux-modules-extra in the 5.15 pi- kernel snap at all which is a regression compared to former pi-kernel snaps where this wifi card works fine. ** Description changed: i recently recommended a TP-Link TL-WN722N to an UbuntuCore customer asking for a recommendation of a USB wifi adapter with external antenna - for the RPi since i use this card on various RPi projects ... + for the RPi since i use this card in various RPi projects ... - trying it on UC22 it tuns out that the module driving this card is not included in the pi-kernel snap. + trying it on UC22 it turns out that the module driving this card is not included in the pi-kernel snap. in fact the staging dir seems to mostly be empty ... the same kernel on classic includes the needed r8188eu.ko module via the linux-modules-extra package. it seems like we do not include linux-modules-extra in the 5.15 pi- kernel snap at all which is a regression compared to former pi-kernel snaps where this wifi card works fine. -- 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/2024443 Title: pi-kernel 5.15 on UC22 is missing most staging modules Status in linux-raspi package in Ubuntu: New Bug description: i recently recommended a TP-Link TL-WN722N to an UbuntuCore customer asking for a recommendation of a USB wifi adapter with external antenna for the RPi since i use this card in various RPi projects ... trying it on UC22 it turns out that the module driving this card is not included in the pi-kernel snap. in fact the staging dir seems to mostly be empty ... the same kernel on classic includes the needed r8188eu.ko module via the linux-modules-extra package. it seems like we do not include linux-modules-extra in the 5.15 pi- kernel snap at all which is a regression compared to former pi-kernel snaps where this wifi card works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2024443/+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 2020627] Re: upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia and Morocco
** Tags added: oem-priority originate-from-1988278 somerville -- 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/2020627 Title: upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia and Morocco Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: In Progress Bug description: AX210: -72 ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0-72.ucode?id=4309412c0d872897dc913c7d2797bb5ce05893ad pnvm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81 AX211: -72 ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f pnvm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81 AX411: -72 ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f pnvm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0.pnvm?id=78a8782a9e51e502a6ed267d270c6925fb738805 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020627/+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 2020627] Re: upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia and Morocco
The linux/lunar has firmware API 72, and linux-firmware/lunar (and newer) has all the required revisions already. ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Description changed: - https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- - firmware.git/commit/iwlwifi- - so-a0-gf-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f + AX210: + -72 ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0-72.ucode?id=4309412c0d872897dc913c7d2797bb5ce05893ad + pnvm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81 + + AX211: + -72 ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f + pnvm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81 + + AX411: + -72 ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f + pnvm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0.pnvm?id=78a8782a9e51e502a6ed267d270c6925fb738805 -- 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/2020627 Title: upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia and Morocco Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: In Progress Bug description: AX210: -72 ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0-72.ucode?id=4309412c0d872897dc913c7d2797bb5ce05893ad pnvm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81 AX211: -72 ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f pnvm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81 AX411: -72 ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f pnvm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0.pnvm?id=78a8782a9e51e502a6ed267d270c6925fb738805 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2020627/+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 2012366] Re: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade
After updating the kernel to: 5.19.0-45-generic #46~22.04.1 The problem NMI-lock has (so far) not showed: No alarm in ILO, blue light instead of Red flashing light on the server. I submitted the updated from the cli of apport on the server. I am not sure why these updates have been submitted like so, it seems like a lot of unnecessary update-comments - Maybe I did something wrong -- 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/2012366 Title: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After distro upgrade to new LTS "22" from 20 the HP microserver shows a critical NMI event in ILO Unrecoverable System Error (NMI) has occurred. System Firmware will log additional details in a separate IML entry if possible no hp modules are loaded except hpilo: lsmod |grep hp hpilo 24576 0 Despite the server is flashing "red" the System is functional. A few minutes after boot the kernel shows 4-5 of these kernel panics (see full log) but continue to run ok, the NMI flag in ILO appears simultaneously to this kernel error. this issue was not present before the distro-upgrade. [ 739.516183] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. [ 739.516190] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-67-generic #74-Ubuntu [ 739.516194] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 739.516196] RIP: 0010:mwait_idle_with_hints.constprop.0+0x4f/0xa0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 23:54 seq crw-rw 1 root audio 116, 33 Mar 20 23:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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 Date: Tue Mar 21 09:20:20 2023 InstallationDate: Installed on 2022-02-16 (397 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-03-20 (0 days ago) dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.82:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku712317-421: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 19 16:38 seq crw-rw 1 root audio 116, 33 Jun 19 16:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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 CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-16 (488 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17
[Kernel-packages] [Bug 2012366] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2012366/+attachment/5680926/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012366 Title: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After distro upgrade to new LTS "22" from 20 the HP microserver shows a critical NMI event in ILO Unrecoverable System Error (NMI) has occurred. System Firmware will log additional details in a separate IML entry if possible no hp modules are loaded except hpilo: lsmod |grep hp hpilo 24576 0 Despite the server is flashing "red" the System is functional. A few minutes after boot the kernel shows 4-5 of these kernel panics (see full log) but continue to run ok, the NMI flag in ILO appears simultaneously to this kernel error. this issue was not present before the distro-upgrade. [ 739.516183] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. [ 739.516190] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-67-generic #74-Ubuntu [ 739.516194] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 739.516196] RIP: 0010:mwait_idle_with_hints.constprop.0+0x4f/0xa0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 23:54 seq crw-rw 1 root audio 116, 33 Mar 20 23:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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 Date: Tue Mar 21 09:20:20 2023 InstallationDate: Installed on 2022-02-16 (397 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-03-20 (0 days ago) dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.82:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku712317-421: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 19 16:38 seq crw-rw 1 root audio 116, 33 Jun 19 16:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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 CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-16 (488 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 2012366] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2012366/+attachment/5680929/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012366 Title: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After distro upgrade to new LTS "22" from 20 the HP microserver shows a critical NMI event in ILO Unrecoverable System Error (NMI) has occurred. System Firmware will log additional details in a separate IML entry if possible no hp modules are loaded except hpilo: lsmod |grep hp hpilo 24576 0 Despite the server is flashing "red" the System is functional. A few minutes after boot the kernel shows 4-5 of these kernel panics (see full log) but continue to run ok, the NMI flag in ILO appears simultaneously to this kernel error. this issue was not present before the distro-upgrade. [ 739.516183] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. [ 739.516190] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-67-generic #74-Ubuntu [ 739.516194] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 739.516196] RIP: 0010:mwait_idle_with_hints.constprop.0+0x4f/0xa0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 23:54 seq crw-rw 1 root audio 116, 33 Mar 20 23:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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 Date: Tue Mar 21 09:20:20 2023 InstallationDate: Installed on 2022-02-16 (397 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-03-20 (0 days ago) dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.82:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku712317-421: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 19 16:38 seq crw-rw 1 root audio 116, 33 Jun 19 16:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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 CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-16 (488 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 2012366] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2012366/+attachment/5680927/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012366 Title: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After distro upgrade to new LTS "22" from 20 the HP microserver shows a critical NMI event in ILO Unrecoverable System Error (NMI) has occurred. System Firmware will log additional details in a separate IML entry if possible no hp modules are loaded except hpilo: lsmod |grep hp hpilo 24576 0 Despite the server is flashing "red" the System is functional. A few minutes after boot the kernel shows 4-5 of these kernel panics (see full log) but continue to run ok, the NMI flag in ILO appears simultaneously to this kernel error. this issue was not present before the distro-upgrade. [ 739.516183] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. [ 739.516190] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-67-generic #74-Ubuntu [ 739.516194] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 739.516196] RIP: 0010:mwait_idle_with_hints.constprop.0+0x4f/0xa0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 23:54 seq crw-rw 1 root audio 116, 33 Mar 20 23:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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 Date: Tue Mar 21 09:20:20 2023 InstallationDate: Installed on 2022-02-16 (397 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-03-20 (0 days ago) dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.82:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku712317-421: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 19 16:38 seq crw-rw 1 root audio 116, 33 Jun 19 16:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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 CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-16 (488 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 2012366] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2012366/+attachment/5680928/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012366 Title: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After distro upgrade to new LTS "22" from 20 the HP microserver shows a critical NMI event in ILO Unrecoverable System Error (NMI) has occurred. System Firmware will log additional details in a separate IML entry if possible no hp modules are loaded except hpilo: lsmod |grep hp hpilo 24576 0 Despite the server is flashing "red" the System is functional. A few minutes after boot the kernel shows 4-5 of these kernel panics (see full log) but continue to run ok, the NMI flag in ILO appears simultaneously to this kernel error. this issue was not present before the distro-upgrade. [ 739.516183] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. [ 739.516190] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-67-generic #74-Ubuntu [ 739.516194] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 739.516196] RIP: 0010:mwait_idle_with_hints.constprop.0+0x4f/0xa0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 23:54 seq crw-rw 1 root audio 116, 33 Mar 20 23:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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 Date: Tue Mar 21 09:20:20 2023 InstallationDate: Installed on 2022-02-16 (397 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-03-20 (0 days ago) dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.82:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku712317-421: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 19 16:38 seq crw-rw 1 root audio 116, 33 Jun 19 16:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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 CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-16 (488 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 2012366] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2012366/+attachment/5680924/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012366 Title: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After distro upgrade to new LTS "22" from 20 the HP microserver shows a critical NMI event in ILO Unrecoverable System Error (NMI) has occurred. System Firmware will log additional details in a separate IML entry if possible no hp modules are loaded except hpilo: lsmod |grep hp hpilo 24576 0 Despite the server is flashing "red" the System is functional. A few minutes after boot the kernel shows 4-5 of these kernel panics (see full log) but continue to run ok, the NMI flag in ILO appears simultaneously to this kernel error. this issue was not present before the distro-upgrade. [ 739.516183] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. [ 739.516190] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-67-generic #74-Ubuntu [ 739.516194] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 739.516196] RIP: 0010:mwait_idle_with_hints.constprop.0+0x4f/0xa0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 23:54 seq crw-rw 1 root audio 116, 33 Mar 20 23:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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 Date: Tue Mar 21 09:20:20 2023 InstallationDate: Installed on 2022-02-16 (397 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-03-20 (0 days ago) dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.82:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku712317-421: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 19 16:38 seq crw-rw 1 root audio 116, 33 Jun 19 16:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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 CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-16 (488 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Error: [Errno 2] No
[Kernel-packages] [Bug 2012366] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2012366/+attachment/5680921/+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/2012366 Title: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After distro upgrade to new LTS "22" from 20 the HP microserver shows a critical NMI event in ILO Unrecoverable System Error (NMI) has occurred. System Firmware will log additional details in a separate IML entry if possible no hp modules are loaded except hpilo: lsmod |grep hp hpilo 24576 0 Despite the server is flashing "red" the System is functional. A few minutes after boot the kernel shows 4-5 of these kernel panics (see full log) but continue to run ok, the NMI flag in ILO appears simultaneously to this kernel error. this issue was not present before the distro-upgrade. [ 739.516183] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. [ 739.516190] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-67-generic #74-Ubuntu [ 739.516194] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 739.516196] RIP: 0010:mwait_idle_with_hints.constprop.0+0x4f/0xa0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 23:54 seq crw-rw 1 root audio 116, 33 Mar 20 23:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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 Date: Tue Mar 21 09:20:20 2023 InstallationDate: Installed on 2022-02-16 (397 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-03-20 (0 days ago) dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.82:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku712317-421: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 19 16:38 seq crw-rw 1 root audio 116, 33 Jun 19 16:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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 CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-16 (488 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 2012366] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2012366/+attachment/5680925/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012366 Title: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After distro upgrade to new LTS "22" from 20 the HP microserver shows a critical NMI event in ILO Unrecoverable System Error (NMI) has occurred. System Firmware will log additional details in a separate IML entry if possible no hp modules are loaded except hpilo: lsmod |grep hp hpilo 24576 0 Despite the server is flashing "red" the System is functional. A few minutes after boot the kernel shows 4-5 of these kernel panics (see full log) but continue to run ok, the NMI flag in ILO appears simultaneously to this kernel error. this issue was not present before the distro-upgrade. [ 739.516183] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. [ 739.516190] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-67-generic #74-Ubuntu [ 739.516194] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 739.516196] RIP: 0010:mwait_idle_with_hints.constprop.0+0x4f/0xa0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 23:54 seq crw-rw 1 root audio 116, 33 Mar 20 23:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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 Date: Tue Mar 21 09:20:20 2023 InstallationDate: Installed on 2022-02-16 (397 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-03-20 (0 days ago) dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.82:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku712317-421: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 19 16:38 seq crw-rw 1 root audio 116, 33 Jun 19 16:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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 CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-16 (488 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Error: [Errno 2] No such file
[Kernel-packages] [Bug 2012366] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2012366/+attachment/5680923/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012366 Title: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After distro upgrade to new LTS "22" from 20 the HP microserver shows a critical NMI event in ILO Unrecoverable System Error (NMI) has occurred. System Firmware will log additional details in a separate IML entry if possible no hp modules are loaded except hpilo: lsmod |grep hp hpilo 24576 0 Despite the server is flashing "red" the System is functional. A few minutes after boot the kernel shows 4-5 of these kernel panics (see full log) but continue to run ok, the NMI flag in ILO appears simultaneously to this kernel error. this issue was not present before the distro-upgrade. [ 739.516183] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. [ 739.516190] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-67-generic #74-Ubuntu [ 739.516194] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 739.516196] RIP: 0010:mwait_idle_with_hints.constprop.0+0x4f/0xa0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 23:54 seq crw-rw 1 root audio 116, 33 Mar 20 23:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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 Date: Tue Mar 21 09:20:20 2023 InstallationDate: Installed on 2022-02-16 (397 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-03-20 (0 days ago) dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.82:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku712317-421: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 19 16:38 seq crw-rw 1 root audio 116, 33 Jun 19 16:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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 CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-16 (488 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 2012366] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2012366/+attachment/5680922/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012366 Title: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After distro upgrade to new LTS "22" from 20 the HP microserver shows a critical NMI event in ILO Unrecoverable System Error (NMI) has occurred. System Firmware will log additional details in a separate IML entry if possible no hp modules are loaded except hpilo: lsmod |grep hp hpilo 24576 0 Despite the server is flashing "red" the System is functional. A few minutes after boot the kernel shows 4-5 of these kernel panics (see full log) but continue to run ok, the NMI flag in ILO appears simultaneously to this kernel error. this issue was not present before the distro-upgrade. [ 739.516183] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. [ 739.516190] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-67-generic #74-Ubuntu [ 739.516194] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 739.516196] RIP: 0010:mwait_idle_with_hints.constprop.0+0x4f/0xa0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 23:54 seq crw-rw 1 root audio 116, 33 Mar 20 23:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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 Date: Tue Mar 21 09:20:20 2023 InstallationDate: Installed on 2022-02-16 (397 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-03-20 (0 days ago) dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.82:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku712317-421: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 19 16:38 seq crw-rw 1 root audio 116, 33 Jun 19 16:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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 CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-16 (488 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 2012366] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2012366/+attachment/5680919/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012366 Title: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After distro upgrade to new LTS "22" from 20 the HP microserver shows a critical NMI event in ILO Unrecoverable System Error (NMI) has occurred. System Firmware will log additional details in a separate IML entry if possible no hp modules are loaded except hpilo: lsmod |grep hp hpilo 24576 0 Despite the server is flashing "red" the System is functional. A few minutes after boot the kernel shows 4-5 of these kernel panics (see full log) but continue to run ok, the NMI flag in ILO appears simultaneously to this kernel error. this issue was not present before the distro-upgrade. [ 739.516183] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. [ 739.516190] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-67-generic #74-Ubuntu [ 739.516194] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 739.516196] RIP: 0010:mwait_idle_with_hints.constprop.0+0x4f/0xa0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 23:54 seq crw-rw 1 root audio 116, 33 Mar 20 23:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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 Date: Tue Mar 21 09:20:20 2023 InstallationDate: Installed on 2022-02-16 (397 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-03-20 (0 days ago) dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.82:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku712317-421: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 19 16:38 seq crw-rw 1 root audio 116, 33 Jun 19 16:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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 CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-16 (488 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 2012366] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2012366/+attachment/5680920/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012366 Title: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After distro upgrade to new LTS "22" from 20 the HP microserver shows a critical NMI event in ILO Unrecoverable System Error (NMI) has occurred. System Firmware will log additional details in a separate IML entry if possible no hp modules are loaded except hpilo: lsmod |grep hp hpilo 24576 0 Despite the server is flashing "red" the System is functional. A few minutes after boot the kernel shows 4-5 of these kernel panics (see full log) but continue to run ok, the NMI flag in ILO appears simultaneously to this kernel error. this issue was not present before the distro-upgrade. [ 739.516183] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. [ 739.516190] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-67-generic #74-Ubuntu [ 739.516194] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 739.516196] RIP: 0010:mwait_idle_with_hints.constprop.0+0x4f/0xa0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 23:54 seq crw-rw 1 root audio 116, 33 Mar 20 23:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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 Date: Tue Mar 21 09:20:20 2023 InstallationDate: Installed on 2022-02-16 (397 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-03-20 (0 days ago) dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.82:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku712317-421: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 19 16:38 seq crw-rw 1 root audio 116, 33 Jun 19 16:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 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 CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-16 (488 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 2020627] Re: upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia and Morocco
** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2020627 Title: upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia and Morocco Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: New Bug description: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/iwlwifi- so-a0-gf-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2020627/+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 2012366] Re: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade
apport information ** Tags added: apport-collected ** Description changed: After distro upgrade to new LTS "22" from 20 the HP microserver shows a critical NMI event in ILO Unrecoverable System Error (NMI) has occurred. System Firmware will log additional details in a separate IML entry if possible no hp modules are loaded except hpilo: lsmod |grep hp hpilo 24576 0 Despite the server is flashing "red" the System is functional. A few minutes after boot the kernel shows 4-5 of these kernel panics (see full log) but continue to run ok, the NMI flag in ILO appears simultaneously to this kernel error. this issue was not present before the distro- upgrade. [ 739.516183] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. [ 739.516190] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-67-generic #74-Ubuntu [ 739.516194] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 [ 739.516196] RIP: 0010:mwait_idle_with_hints.constprop.0+0x4f/0xa0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 23:54 seq crw-rw 1 root audio 116, 33 Mar 20 23:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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 Date: Tue Mar 21 09:20:20 2023 InstallationDate: Installed on 2022-02-16 (397 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-03-20 (0 days ago) dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.82:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku712317-421: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jun 19 16:38 seq + crw-rw 1 root audio 116, 33 Jun 19 16:38 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu82.5 + 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 + CurrentDmesg: + Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized + + This incident has been reported. + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-02-16 (488 days ago) + InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + MachineType: HP ProLiant MicroServer Gen8 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash + ProcFB: 0 mgag200drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro + ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 + RelatedPackageVersions: + linux-restricted-modules-5.19.0-45-generic N/A + linux-backports-modules-5.19.0-45-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.13 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: jammy + Uname: Linux 5.19.0-45-generic x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: Upgraded to jammy on 2023-03-20 (91 days ago) + UserGroups: adm cdrom dip docker lxd plugdev sudo + _MarkForUpload: False + dmi.bios.date: 04/04/2019 + dmi.bios.vendor: HP + dmi.bios.version: J06
[Kernel-packages] [Bug 2024431] 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 2024431 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/2024431 Title: 5.15.0-75 hdmi monitor no signal Status in linux package in Ubuntu: Incomplete Bug description: Laptop with 2 external screens (1x HDMI, 1x VGA) On 5.15.0-75 HDMI monitors receive no signal (tested with 2 different monitors) Works with 5.15.0-73 > cat /proc/version_signature Ubuntu 5.15.0-73.80-generic 5.15.98 > inxi -bG System: Host: HESSEL-MSI-MINT Kernel: 5.15.0-73-generic x86_64 bits: 64 Desktop: Cinnamon 5.6.8 Distro: Linux Mint 21.1 Vera Machine: Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0 serial: Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015 Battery: ID-1: BAT1 charge: 39.5 Wh (100.0%) condition: 39.5/57.7 Wh (68.4%) CPU: Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1975 min/max: 800/3500 Graphics: Device-1: Intel 4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Device-2: NVIDIA GM107M [GeForce GTX 850M] driver: N/A Device-3: Suyin USB 2.0 Webcam Device type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1: 1920x1080~60Hz 2: 1080x1920~60Hz 3: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 21.3.7 Amber Network: Device-1: Qualcomm Atheros Killer E220x Gigabit Ethernet driver: alx Device-2: Intel Wireless 3160 driver: iwlwifi Device-3: Intel Bluetooth wireless interface type: USB driver: btusb Drives: Local Storage: total: 685.61 GiB used: 442.02 GiB (64.5%) Info: Processes: 379 Uptime: 10m Memory: 15.37 GiB used: 5.01 GiB (32.6%) Shell: Bash inxi: 3.3.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024431/+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 2024434] [NEW] Pi Camera 3 not working with Lunar
Public bug reported: Attempting to use a Pi Camera 3 with Lunar results in: $ sudo libcamera-hello Made X/EGL preview window [0:01:28.143741115] [2014] INFO Camera camera_manager.cpp:299 libcamera v0.0.4 [0:01:28.200294746] [2018] ERROR RPI raspberrypi.cpp:1279 Failed to register camera imx708: -2 ERROR: *** no cameras available *** When using the v8 raspberrypi kernel on Lunar, the camera works just fine so the Lunar raspi kernel is missing some required config options and/or patches. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Lunar) 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/2024434 Title: Pi Camera 3 not working with Lunar Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Lunar: New Bug description: Attempting to use a Pi Camera 3 with Lunar results in: $ sudo libcamera-hello Made X/EGL preview window [0:01:28.143741115] [2014] INFO Camera camera_manager.cpp:299 libcamera v0.0.4 [0:01:28.200294746] [2018] ERROR RPI raspberrypi.cpp:1279 Failed to register camera imx708: -2 ERROR: *** no cameras available *** When using the v8 raspberrypi kernel on Lunar, the camera works just fine so the Lunar raspi kernel is missing some required config options and/or patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2024434/+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 2024431] [NEW] 5.15.0-75 hdmi monitor no signal
Public bug reported: Laptop with 2 external screens (1x HDMI, 1x VGA) On 5.15.0-75 HDMI monitors receive no signal (tested with 2 different monitors) Works with 5.15.0-73 > cat /proc/version_signature Ubuntu 5.15.0-73.80-generic 5.15.98 > inxi -bG System: Host: HESSEL-MSI-MINT Kernel: 5.15.0-73-generic x86_64 bits: 64 Desktop: Cinnamon 5.6.8 Distro: Linux Mint 21.1 Vera Machine: Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0 serial: Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015 Battery: ID-1: BAT1 charge: 39.5 Wh (100.0%) condition: 39.5/57.7 Wh (68.4%) CPU: Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1975 min/max: 800/3500 Graphics: Device-1: Intel 4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Device-2: NVIDIA GM107M [GeForce GTX 850M] driver: N/A Device-3: Suyin USB 2.0 Webcam Device type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1: 1920x1080~60Hz 2: 1080x1920~60Hz 3: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 21.3.7 Amber Network: Device-1: Qualcomm Atheros Killer E220x Gigabit Ethernet driver: alx Device-2: Intel Wireless 3160 driver: iwlwifi Device-3: Intel Bluetooth wireless interface type: USB driver: btusb Drives: Local Storage: total: 685.61 GiB used: 442.02 GiB (64.5%) Info: Processes: 379 Uptime: 10m Memory: 15.37 GiB used: 5.01 GiB (32.6%) Shell: Bash inxi: 3.3.13 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/2024431/+attachment/5680912/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024431 Title: 5.15.0-75 hdmi monitor no signal Status in linux package in Ubuntu: New Bug description: Laptop with 2 external screens (1x HDMI, 1x VGA) On 5.15.0-75 HDMI monitors receive no signal (tested with 2 different monitors) Works with 5.15.0-73 > cat /proc/version_signature Ubuntu 5.15.0-73.80-generic 5.15.98 > inxi -bG System: Host: HESSEL-MSI-MINT Kernel: 5.15.0-73-generic x86_64 bits: 64 Desktop: Cinnamon 5.6.8 Distro: Linux Mint 21.1 Vera Machine: Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0 serial: Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015 Battery: ID-1: BAT1 charge: 39.5 Wh (100.0%) condition: 39.5/57.7 Wh (68.4%) CPU: Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1975 min/max: 800/3500 Graphics: Device-1: Intel 4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Device-2: NVIDIA GM107M [GeForce GTX 850M] driver: N/A Device-3: Suyin USB 2.0 Webcam Device type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1: 1920x1080~60Hz 2: 1080x1920~60Hz 3: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 21.3.7 Amber Network: Device-1: Qualcomm Atheros Killer E220x Gigabit Ethernet driver: alx Device-2: Intel Wireless 3160 driver: iwlwifi Device-3: Intel Bluetooth wireless interface type: USB driver: btusb Drives: Local Storage: total: 685.61 GiB used: 442.02 GiB (64.5%) Info: Processes: 379 Uptime: 10m Memory: 15.37 GiB used: 5.01 GiB (32.6%) Shell: Bash inxi: 3.3.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024431/+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 2024432] [NEW] net/sched: act_ct: Fix promotion of offloaded unreplied tuple
Public bug reported: * Explain the bug(s) Currently UNREPLIED and UNASSURED connections are added to the nf flow table. This causes the following connection packets to be processed by the flow table which then skips conntrack_in(), and thus such the connections will remain UNREPLIED and UNASSURED even if reply traffic is then seen. Even still, the unoffloaded reply packets are the ones triggering hardware update from new to established state, and if there aren't any to triger an update and/or previous update was missed, hardware can get out of sync with sw and still mark packets as new. * brief explanation of fixes 1) Not skipping conntrack_in() for UNASSURED packets, but still refresh for hardware, as before the cited patch. 2) Try and force a refresh by reply-direction packets that update the hardware rules from new to established state. 3) Remove any bidirectional flows that didn't failed to update in hardware for re-insertion as bidirectional once any new packet arrives. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a UDP single sided connection, e.g iperf without a server: on mlx5 VF2 iperf -t 1 -c -u -b 10pps Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi udp and see no iperf udp packets. Dump conntrack with relevant ip: cat /proc/net/nf_conntrack | grep -i | grep "\[UNREPLIED\]" | grep -q "\[OFFLOAD\]" If tuple appears, tuple was offloaded, yet unreplied. * What it could break. The connections remain UNREPLIED and UNASSURED even if reply traffic is seen ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2024432 Title: net/sched: act_ct: Fix promotion of offloaded unreplied tuple Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the bug(s) Currently UNREPLIED and UNASSURED connections are added to the nf flow table. This causes the following connection packets to be processed by the flow table which then skips conntrack_in(), and thus such the connections will remain UNREPLIED and UNASSURED even if reply traffic is then seen. Even still, the unoffloaded reply packets are the ones triggering hardware update from new to established state, and if there aren't any to triger an update and/or previous update was missed, hardware can get out of sync with sw and still mark packets as new. * brief explanation of fixes 1) Not skipping conntrack_in() for UNASSURED packets, but still refresh for hardware, as before the cited patch. 2) Try and force a refresh by reply-direction packets that update the hardware rules from new to established state. 3) Remove any bidirectional flows that didn't failed to update in hardware for re-insertion as bidirectional once any new packet arrives. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a UDP single sided connection, e.g iperf without a server: on mlx5 VF2 iperf -t 1 -c -u -b 10pps Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi udp and see no iperf udp packets. Dump conntrack with relevant ip: cat /proc/net/nf_conntrack | grep -i | grep "\[UNREPLIED\]" | grep -q "\[OFFLOAD\]" If tuple appears, tuple was offloaded, yet unreplied. * What it could break. The connections remain UNREPLIED and UNASSURED even if reply traffic is seen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2024432/+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 2018979] Re: Update the 525 UDA NVIDIA driver series in Bionic, Focal, and Kinetic, Lunar
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.116.04-0ubuntu0.22.04.1 --- nvidia-graphics-drivers-525 (525.116.04-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream release (LP: #2018979). -- Alberto Milone Thu, 11 May 2023 09:18:34 + ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2018979 Title: Update the 525 UDA NVIDIA driver series in Bionic, Focal, and Kinetic, Lunar Status in nvidia-graphics-drivers-525 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525 source package in Lunar: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2018979/+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 2018566] Re: A deadlock issue in scsi rescan task while resuming from S3
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2018566 Title: A deadlock issue in scsi rescan task while resuming from S3 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] During the S3 stress test, the system sometimes hangs when resuming. This is due to the SCSI rescan task being unable to acquire the mutex lock during the resumption from S3. The mutex lock has already been acquired by EH and is waiting for the device to be ready for a rescan. Unfortunately, the mutex lock is never released by either party, leading to a deadlock. [Fix] Kaiheng submitted a patch to fix this issue which defers the rescan if the disk is still suspended so the resume process of the disk device can proceed. https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/ Since the patch has not been accepted by the upstream yet, so submit it to the OEM kernel for now. The similiar patch has been included in v6.4-rc7 6aa0365a3c85 ata: libata-scsi: Avoid deadlock on rescan after device resume [Test] Verified on the machines by me and ODM. [Where problems could occur] It only defers the rescan task, and should not have any impact to current systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2018566/+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 2024427] [NEW] potential S3 issue for amdgpu Navi 31/Navi33
Public bug reported: amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2024123 somerville ** Also affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Tags added: oem-priority originate-from-2024123 somerville -- 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/2024427 Title: potential S3 issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: New Status in linux-firmware source package in Lunar: New Status in linux-firmware source package in Mantic: New Bug description: amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+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
