[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute (arm64)
This memcg_test_3 failure on ARM64 instances is no longer causing cgroup_fj_* test to fail, it just timeout with 30 seconds threshold. Will need to test it again manually. -- 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/1836694 Title: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute (arm64) Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986907] 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 1986907 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 in Ubuntu. https://bugs.launchpad.net/bugs/1986907 Title: There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: 1. Power on SUT and boot into UEFI setup. 2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0. 3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC NVMe RAID disk. 4. Boot into OS then check system logs to check if there are any unexpected failed or error messages. (=> failed, there are failed messages in dmesg, /var/log/syslog, and /var/log/kern.log, showing: pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000] where 10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04) 10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04) 10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04) 10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04) ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986907/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986907] [NEW] There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS
Public bug reported: 1. Power on SUT and boot into UEFI setup. 2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0. 3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC NVMe RAID disk. 4. Boot into OS then check system logs to check if there are any unexpected failed or error messages. (=> failed, there are failed messages in dmesg, /var/log/syslog, and /var/log/kern.log, showing: pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000] where 10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04) 10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04) 10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04) 10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04) ) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Package changed: ubuntu => linux (Ubuntu) ** Also affects: linux (Ubuntu Jammy) 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/1986907 Title: There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: 1. Power on SUT and boot into UEFI setup. 2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0. 3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC NVMe RAID disk. 4. Boot into OS then check system logs to check if there are any unexpected failed or error messages. (=> failed, there are failed messages in dmesg, /var/log/syslog, and /var/log/kern.log, showing: pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000] where 10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04) 10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04) 10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04) 10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04) ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986907/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986907] [NEW] There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS
You have been subscribed to a public bug: 1. Power on SUT and boot into UEFI setup. 2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0. 3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC NVMe RAID disk. 4. Boot into OS then check system logs to check if there are any unexpected failed or error messages. (=> failed, there are failed messages in dmesg, /var/log/syslog, and /var/log/kern.log, showing: pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000] where 10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04) 10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04) 10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04) 10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04) ) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS https://bugs.launchpad.net/bugs/1986907 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986887] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609488/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A
[Kernel-packages] [Bug 1986887] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609490/+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/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic
[Kernel-packages] [Bug 1986887] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609485/+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/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A
[Kernel-packages] [Bug 1986887] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609481/+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/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A
[Kernel-packages] [Bug 1986887] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609491/+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/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions:
[Kernel-packages] [Bug 1986887] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609489/+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/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A
[Kernel-packages] [Bug 1986887] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609487/+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/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic
[Kernel-packages] [Bug 1986887] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609478/+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/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A
[Kernel-packages] [Bug 1986887] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609486/+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/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A
[Kernel-packages] [Bug 1986887] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609484/+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/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic
[Kernel-packages] [Bug 1986887] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609483/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A
[Kernel-packages] [Bug 1986887] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609479/+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/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A
[Kernel-packages] [Bug 1986887] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609482/+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/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A
[Kernel-packages] [Bug 1986887] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609477/+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/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A
[Kernel-packages] [Bug 1986887] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609476/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A
[Kernel-packages] [Bug 1986887] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1986887/+attachment/5609474/+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/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Confirmed Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A
[Kernel-packages] [Bug 1986887] Re: Machine Check: 0 Bank 5: bea0000000000108
apport information ** Tags added: apport-collected ** Description changed: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: play 1913 F pulseaudio + /dev/snd/controlC0: play 1913 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-06-05 (73 days ago) + InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + MachineType: To Be Filled By O.E.M. X570 Taichi + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.15.0-46-generic N/A + linux-backports-modules-5.15.0-46-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.4 + Tags: jammy + Uname: Linux 5.15.0-46-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 05/23/2022 + dmi.bios.release: 5.17 + dmi.bios.vendor: American
[Kernel-packages] [Bug 1986887] 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 1986887 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/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Incomplete Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986887] [NEW] Machine Check: 0 Bank 5: bea0000000000108
Public bug reported: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play 1913 F pulseaudio /dev/snd/controlC0: play 1913 F pulseaudio CRDA: N/A CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Wed Aug 17 22:33:23 2022 InstallationDate: Installed on 2022-06-05 (73 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. X570 Taichi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b0f603bd-3eca-4b1e-94c8-5296b86d15b3 ro quiet splash amdgpu.runpm=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 05/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.82 dmi.board.name: X570 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.82:bd05/23/2022:br5.17:svnToBeFilledByO.E.M.:pnX570Taichi:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: X570 Taichi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986887 Title: Machine Check: 0 Bank 5: bea00108 Status in linux package in Ubuntu: Incomplete Bug description: I have a recurring crash. It does not record MCE information to the log file, but is presented on the screen during the next boot. I can recreate the problem. 1) Start a steam game 2) Close the game 3) Let the monitor sleep 4) Wake up the computer and start the game *) It will crash with an MCE when it starts rendering the game after the start menus. This occurs in both games I've tried, Raft and No Man's Sky. I can prevent the computer from crashing by disabling display sleep after 10min. I've tried various kernel settings in an attempt to rectify this without success 1) set idle current in the BIOS 2) disabled C states 3) updated to the latest bios, actually a beta bios 4) enabling/disabling resizable bar This was working in 20.04, but started crashing after the kernel was updated in 20.04 as well. I went to 22.04 hoping it might have been resolved, but it continues to crash. Ryzen 3950X XFX 6600XT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: play
[Kernel-packages] [Bug 1986740] Re: Black screen with lines when booting kernel 5.14 to 5.18
** 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/1986740 Title: Black screen with lines when booting kernel 5.14 to 5.18 Status in linux package in Ubuntu: Confirmed Bug description: Operating system data: Linux 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 x86_64 x86_64 x86_64 x86_64 GNU/Linux Description: Ubuntu 22.04.1 LTS Release: 22.04 Just installed. When testing Ubuntu there was no problem. Device data: Dell Precision 5530 2in1 (Kaby Lake-G workstation) | Intel Core i7-8706G | Radeon WX Vega M GL, 4K UHD What happens: With kernel to 5.15: Before logging in, just after selecting the linux kernel from grub, the screen goes black, no ubuntu+dell loading screen, no nothing. With the black screen, random vertical and horizontal lines appear and move if the cursor moves. There is no way around this, and the only alternatives to change this is: 1. close the laptop lid (sleep mode) and restart. 2. Connect an HDMI to the USB-C port and then disconnect it. If either of the two steps is followed, the display corrects itself and works perfectly. This happened to me using - Ubuntu 20.04 with Linux 5.15.0.43-generic And now that I upgraded it also happens to me - Ubuntu 22.04.1 with Linux 5.15.0-46-generic - Ubuntu 22.04.1 with Linux 5.18.17-051817 - Ubuntu 22.04.1 with Linux 5.14.21-051421 The error did not appear in using - Ubuntu 20.04 with Linux 5.13.0-52-generic or earlier - Ubuntu 22.04.1 with Linux 5.13.0-051300 I will provide all the information you see necessary to solve the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986796] Re: amd64-microcode conflicts with linux-firmware
This was also detected by autopkgtests: https://autopkgtest.ubuntu.com/packages/v/vrms/kinetic/amd64 ** Changed in: amd64-microcode (Ubuntu) Importance: Undecided => High ** Changed in: amd64-microcode (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu) Status: New => Triaged ** Tags added: rls-kk-incoming update-excuse -- 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/1986796 Title: amd64-microcode conflicts with linux-firmware Status in amd64-microcode package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Triaged Bug description: Occurs on kubuntu, gnome and xfce versions of kinetic proposed -- most recent updates ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: amd64-microcode 3.20191218.1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Aug 17 08:07:09 2022 InstallationDate: Installed on 2022-06-10 (67 days ago) InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220610) SourcePackage: amd64-microcode UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1986796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970065] Re: System not going to be completly powered off
Same Problem here. Using 22.04.1 LTS with 5.15.0-47-generic on Acer Aspire E 17 Laptop, because I turned off plymouth I see the system hanging after displaying: shutdown[1]: Rebooting kvm: exiting hardware virtualization ctrl+alt+SysReq+b works! -- 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/1970065 Title: System not going to be completly powered off Status in linux package in Ubuntu: Confirmed Bug description: When i shutdown (Apr 23 23:15), it seems everything powered of except the keyboard lights. Then, i try to power on again, but, nothing happened because the notebook are still powered on. So, it's never powered off correctly? Now i force power off (Apr 23 23:20). After Start, the logs look like this: Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Stopped Create System Users. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: swapfile.swap: Deactivated successfully. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Deactivated swap /swapfile. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target Unmount All Filesystems. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: systemd-remount-fs.service: Deactivated successfully. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Stopped Remount Root and Kernel File Systems. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target System Shutdown. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target Late Shutdown Services. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: systemd-poweroff.service: Deactivated successfully. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Finished System Power Off. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target System Power Off. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Shutting down. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd-shutdown[1]: Syncing filesystems and block devices. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd-shutdown[1]: Sending SIGTERM to remaining processes... Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd-journald[258]: Journal stopped -- Boot 286bc7f0640748e9996bbc70b090eb57 -- Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: microcode: microcode updated early to revision 0xea, date = 2021-01-25 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Linux version 5.15.0-25-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #25-Ubuntu SMP Wed Mar 30 > Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=945f3621-37dd-40d0-be8d-295ac422c82f ro quiet splash vt.handoff=7 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: KERNEL supported cpus: Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Intel GenuineIntel Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: AMD AuthenticAMD Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Hygon HygonGenuine Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Centaur CentaurHauls Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: zhaoxin Shanghai Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: signal: max sigframe size: 2032 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-provided physical RAM map: Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 0x-0x00057fff] usable Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 0x00058000-0x00058fff] reserved Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 0x00059000-0x0009cfff] usable Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 0x0009d000-0x000f] reserved Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820:
[Kernel-packages] [Bug 1738272] Re: microcode packages, like firmware packages, should be in main
Override component to main firmware-sof 2.1.1-1ubuntu1 in kinetic: restricted/misc -> main firmware-sof-signed 2.1.1-1ubuntu1 in kinetic amd64: restricted/kernel/optional/100% -> main firmware-sof-signed 2.1.1-1ubuntu1 in kinetic arm64: restricted/kernel/optional/100% -> main firmware-sof-signed 2.1.1-1ubuntu1 in kinetic armhf: restricted/kernel/optional/100% -> main firmware-sof-signed 2.1.1-1ubuntu1 in kinetic i386: restricted/kernel/optional/100% -> main firmware-sof-signed 2.1.1-1ubuntu1 in kinetic ppc64el: restricted/kernel/optional/100% -> main firmware-sof-signed 2.1.1-1ubuntu1 in kinetic riscv64: restricted/kernel/optional/100% -> main firmware-sof-signed 2.1.1-1ubuntu1 in kinetic s390x: restricted/kernel/optional/100% -> main 8 publications overridden. ** Changed in: firmware-sof (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1738272 Title: microcode packages, like firmware packages, should be in main Status in firmware-sof package in Ubuntu: Fix Released Status in intel-microcode package in Ubuntu: Fix Released Status in iucode-tool package in Ubuntu: Fix Released Bug description: The MIR for intel-microcode and iucode-tool in LP: #139 requested that these packages be shipped in restricted. The iucode-tool package is free software, and is shipped in restricted only because of the circular recommends with intel-microcode. The intel-microcode package contains non-free software (free redistribution, but no source code). However, this code is not part of the OS; it runs /under/ the OS on the CPU, and is analogous to linux-firmware, which we do include in main. The question of suitability for restricted vs. main in Ubuntu was not examined as part of the previous MIR, and the security team signed off on it for "restricted or main as appropriate"; so I think the decision to put it in restricted was not based on a thorough examination of the facts by an archive admin, and does not represent a precedent that needs to be examined further. I believe that these two packages should be promoted to main for consistency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1738272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986848] Re: Kinetic update: v5.19.1 upstream stable release
** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Fix Committed -- 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/1986848 Title: Kinetic update: v5.19.1 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: 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: v5.19.1 upstream stable release from git://git.kernel.org/ block: fix default IO priority handling again tools/vm/slabinfo: Handle files in debugfs ACPI: video: Force backlight native for some TongFang devices ACPI: video: Shortening quirk list by identifying Clevo by board_name only ACPI: APEI: Better fix to avoid spamming the console with old error logs crypto: arm64/poly1305 - fix a read out-of-bound ata: sata_mv: Fixes expected number of resources now IRQs are gone arm64: set UXN on swapper page tables Bluetooth: hci_qca: Return wakeup for qca_wakeup Bluetooth: hci_bcm: Add BCM4349B1 variant Bluetooth: hci_bcm: Add DT compatible for CYW55572 dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding Bluetooth: btusb: Add support of IMC Networks PID 0x3568 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586 macintosh/adb: fix oob read in do_adb_query() function x86/speculation: Add RSB VM Exit protections x86/speculation: Add LFENCE to RSB fill sequence Linux 5.19.1 UBUNTU: Upstream stable to v5.19.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986865] Re: Kinetic update: v5.19.2 upstream stable release
** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Fix Committed -- 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/1986865 Title: Kinetic update: v5.19.2 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: 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: v5.19.2 upstream stable release from git://git.kernel.org/ *See the patch list (1165 patches) in comment#1 below. (So many patches, it overflows the Launchpad bug description field!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986865] Re: Kinetic update: v5.19.2 upstream stable release
Makefile: link with -z noexecstack --no-warn-rwx-segments x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments Revert "pNFS: nfs3_set_ds_client should set NFS_CS_NOPING" scsi: Revert "scsi: qla2xxx: Fix disk failure to rediscover" pNFS/flexfiles: Report RDMA connection errors to the server nfsd: eliminate the NFSD_FILE_BREAK_* flags ALSA: usb-audio: Add quirk for Behringer UMC202HD ALSA: bcd2000: Fix a UAF bug on the error path of probing ALSA: hda/realtek: Add quirk for Clevo NV45PZ ALSA: hda/realtek: Add quirk for HP Spectre x360 15-eb0xxx ALSA: hda/realtek: Add quirk for Lenovo Yoga9 14IAP7 ASoC: amd: yc: Update DMI table entries hwmon: (nct6775) Fix platform driver suspend regression wifi: mac80211_hwsim: fix race condition in pending packet wifi: mac80211_hwsim: add back erroneously removed cast wifi: mac80211_hwsim: use 32-bit skb cookie add barriers to buffer_uptodate and set_buffer_uptodate lockd: detect and reject lock arguments that overflow HID: hid-input: add Surface Go battery quirk HID: nintendo: Add missing array termination HID: wacom: Only report rotation for art pen HID: wacom: Don't register pad_input for touch switch KVM: nVMX: Snapshot pre-VM-Enter BNDCFGS for !nested_run_pending case KVM: nVMX: Snapshot pre-VM-Enter DEBUGCTL for !nested_run_pending case KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0 KVM: s390: pv: don't present the ecall interrupt twice KVM: Drop unused @gpa param from gfn=>pfn cache's __release_gpc() helper KVM: Put the extra pfn reference when reusing a pfn in the gpc cache KVM: Fully serialize gfn=>pfn cache refresh via mutex KVM: Fix multiple races in gfn=>pfn cache refresh KVM: Do not incorporate page offset into gfn=>pfn cache user address KVM: x86: Split kvm_is_valid_cr4() and export only the non-vendor bits KVM: nVMX: Let userspace set nVMX MSR to any _host_ supported value KVM: nVMX: Account for KVM reserved CR4 bits in consistency checks KVM: nVMX: Inject #UD if VMXON is attempted with incompatible CR0/CR4 KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP KVM: x86/mmu: Treat NX as a valid SPTE bit for NPT KVM: SVM: Disable SEV-ES support if MMIO caching is disable KVM: x86: Tag kvm_mmu_x86_module_init() with __init KVM: x86/mmu: Fully re-evaluate MMIO caching when SPTE masks change KVM: x86: do not report preemption if the steal time cache is stale KVM: x86: revalidate steal time cache if MSR value changes KVM: x86/xen: Initialize Xen timer only once KVM: x86/xen: Stop Xen timer before changing IRQ ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model ALSA: hda/cirrus - support for iMac 12,1 model ALSA: hda/realtek: Add quirk for another Asus K42JZ model ALSA: hda/realtek: Add a quirk for HP OMEN 15 (8786) mute LED LoongArch: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK tty: 8250: Add support for Brainboxes PX cards. tty: vt: initialize unicode screen buffer vfs: Check the truncate maximum size in inode_newsize_ok() fs: Add missing umask strip in vfs_tmpfile thermal: sysfs: Fix cooling_device_stats_setup() error code path fbcon: Fix boundary checks for fbcon=vc:n1-n2 parameters fbcon: Fix accelerated fbdev scrolling while logo is still shown usbnet: Fix linkwatch use-after-free on disconnect usbnet: smsc95xx: Fix deadlock on runtime resume fix short copy handling in copy_mc_pipe_to_iter() crypto: ccp - Use kzalloc for sev ioctl interfaces to prevent kernel memory leak ovl: drop WARN_ON() dentry is NULL in ovl_encode_fh() parisc: Fix device names in /proc/iomem parisc: Drop pa_swapper_pg_lock spinlock parisc: Check the return value of ioremap() in lba_driver_probe() parisc: io_pgetevents_time64() needs compat syscall in 32-bit compat mode riscv:uprobe fix SR_SPIE set/clear handling riscv: lib: uaccess: fix CSR_STATUS SR_SUM bit dt-bindings: riscv: fix SiFive l2-cache's cache-sets riscv: dts: starfive: correct number of external interrupts RISC-V: cpu_ops_spinwait.c should include head.h RISC-V: Declare cpu_ops_spinwait in RISC-V: kexec: Fixup use of smp_processor_id() in preemptible context RISC-V: Fixup get incorrect user mode PC for kernel mode regs RISC-V: Fixup schedule out issue in machine_crash_shutdown() RISC-V: Add modules to virtual kernel memory layout dump RISC-V: Fix counter restart during overflow for RV32 RISC-V: Fix SBI PMU calls for RV32 RISC-V: Update user page mapping only once during start wireguard: selftests: set CONFIG_NONPORTABLE on riscv32 rtc: rx8025: fix 12/24 hour mode detection on RX-8035 drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error drm/shmem-helper: Add missing vunmap on error drm/vc4: hdmi: Disable audio if dmas property is present but empty drm/ingenic: Use the highest possible DMA burst size drm/fb-helper: Fix out-of-bounds access drm/hyperv-drm: Include framebuffer and EDID headers drm/dp/mst: Read the extended DPCD capabilities during system resume
[Kernel-packages] [Bug 1986865] [NEW] Kinetic update: v5.19.2 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.19.2 upstream stable release from git://git.kernel.org/ *See the patch list (1165 patches) in comment#1 below. (So many patches, it overflows the Launchpad bug description field!) ** Affects: linux (Ubuntu) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Kinetic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1986865 Title: Kinetic update: v5.19.2 upstream stable release Status in linux package in Ubuntu: In Progress Status in linux source package in Kinetic: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.19.2 upstream stable release from git://git.kernel.org/ *See the patch list (1165 patches) in comment#1 below. (So many patches, it overflows the Launchpad bug description field!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986740] 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 1986740 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/1986740 Title: Black screen with lines when booting kernel 5.14 to 5.18 Status in linux package in Ubuntu: Incomplete Bug description: Operating system data: Linux 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 x86_64 x86_64 x86_64 x86_64 GNU/Linux Description: Ubuntu 22.04.1 LTS Release: 22.04 Just installed. When testing Ubuntu there was no problem. Device data: Dell Precision 5530 2in1 (Kaby Lake-G workstation) | Intel Core i7-8706G | Radeon WX Vega M GL, 4K UHD What happens: With kernel to 5.15: Before logging in, just after selecting the linux kernel from grub, the screen goes black, no ubuntu+dell loading screen, no nothing. With the black screen, random vertical and horizontal lines appear and move if the cursor moves. There is no way around this, and the only alternatives to change this is: 1. close the laptop lid (sleep mode) and restart. 2. Connect an HDMI to the USB-C port and then disconnect it. If either of the two steps is followed, the display corrects itself and works perfectly. This happened to me using - Ubuntu 20.04 with Linux 5.15.0.43-generic And now that I upgraded it also happens to me - Ubuntu 22.04.1 with Linux 5.15.0-46-generic - Ubuntu 22.04.1 with Linux 5.18.17-051817 - Ubuntu 22.04.1 with Linux 5.14.21-051421 The error did not appear in using - Ubuntu 20.04 with Linux 5.13.0-52-generic or earlier - Ubuntu 22.04.1 with Linux 5.13.0-051300 I will provide all the information you see necessary to solve the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986740] Re: Black screen with lines when booting kernel 5.14 to 5.18
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: focal jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986740 Title: Black screen with lines when booting kernel 5.14 to 5.18 Status in linux package in Ubuntu: New Bug description: Operating system data: Linux 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 x86_64 x86_64 x86_64 x86_64 GNU/Linux Description: Ubuntu 22.04.1 LTS Release: 22.04 Just installed. When testing Ubuntu there was no problem. Device data: Dell Precision 5530 2in1 (Kaby Lake-G workstation) | Intel Core i7-8706G | Radeon WX Vega M GL, 4K UHD What happens: With kernel to 5.15: Before logging in, just after selecting the linux kernel from grub, the screen goes black, no ubuntu+dell loading screen, no nothing. With the black screen, random vertical and horizontal lines appear and move if the cursor moves. There is no way around this, and the only alternatives to change this is: 1. close the laptop lid (sleep mode) and restart. 2. Connect an HDMI to the USB-C port and then disconnect it. If either of the two steps is followed, the display corrects itself and works perfectly. This happened to me using - Ubuntu 20.04 with Linux 5.15.0.43-generic And now that I upgraded it also happens to me - Ubuntu 22.04.1 with Linux 5.15.0-46-generic - Ubuntu 22.04.1 with Linux 5.18.17-051817 - Ubuntu 22.04.1 with Linux 5.14.21-051421 The error did not appear in using - Ubuntu 20.04 with Linux 5.13.0-52-generic or earlier - Ubuntu 22.04.1 with Linux 5.13.0-051300 I will provide all the information you see necessary to solve the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986857] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986857 Title: fan doesn't work Status in linux package in Ubuntu: Confirmed Bug description: The fan does not work in either the current version of ubuntu or previous (focal fossa). it was working a few months ago, so this may be new to this kernel, i didn't discover when it stopped working directly :( symptoms: gets very hot. no fan. eventually blackscreens while the power remains on. `sensors-detect` eventually outputs: ``` Sorry, no sensors were detected. This is relatively common on laptops, where thermal management is handled by ACPI rather than the OS. ``` `sensors` output is as follows: ``` jdub@compy4:~$ sudo sensors iwlwifi_1-virtual-0 Adapter: Virtual device temp1:+41.0°C asus-isa- Adapter: ISA adapter cpu_fan: 2900 RPM nvme-pci-0500 Adapter: PCI adapter Composite:+55.9°C (low = -5.2°C, high = +83.8°C) (crit = +87.8°C) BAT0-acpi-0 Adapter: ACPI interface in0: 15.83 V amdgpu-pci-0600 Adapter: PCI adapter vddgfx: 756.00 mV vddnb: 874.00 mV edge: +51.0°C slowPPT: 2.00 mW ucsi_source_psy_USBC000:001-isa- Adapter: ISA adapter in0: 0.00 V (min = +0.00 V, max = +0.00 V) curr1: 0.00 A (max = +0.00 A) k10temp-pci-00c3 Adapter: PCI adapter Tctl: +52.9°C nvme-pci-0400 Adapter: PCI adapter Composite:+32.9°C (low = -0.1°C, high = +76.8°C) (crit = +79.8°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+52.0°C (crit = +120.0°C) ``` Description: Ubuntu 22.04.1 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jdub 2341 F pulseaudio /dev/snd/controlC0: jdub 2341 F pulseaudio /dev/snd/controlC1: jdub 2341 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 17 12:51:23 2022 InstallationDate: Installed on 2021-04-08 (496 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA502IU_GA502IU ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=84a0282e-1a9f-4814-a551-45a4be446ec9 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (0 days ago) dmi.bios.date: 12/30/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA502IU.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA502IU dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA502IU.221:bd12/30/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA502IU_GA502IU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA502IU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus G15 dmi.product.name: ROG Zephyrus G15 GA502IU_GA502IU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986740] [NEW] Black screen with lines when booting kernel 5.14 to 5.18
You have been subscribed to a public bug: Operating system data: Linux 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 x86_64 x86_64 x86_64 x86_64 GNU/Linux Description: Ubuntu 22.04.1 LTS Release: 22.04 Just installed. When testing Ubuntu there was no problem. Device data: Dell Precision 5530 2in1 (Kaby Lake-G workstation) | Intel Core i7-8706G | Radeon WX Vega M GL, 4K UHD What happens: With kernel to 5.15: Before logging in, just after selecting the linux kernel from grub, the screen goes black, no ubuntu+dell loading screen, no nothing. With the black screen, random vertical and horizontal lines appear and move if the cursor moves. There is no way around this, and the only alternatives to change this is: 1. close the laptop lid (sleep mode) and restart. 2. Connect an HDMI to the USB-C port and then disconnect it. If either of the two steps is followed, the display corrects itself and works perfectly. This happened to me using - Ubuntu 20.04 with Linux 5.15.0.43-generic And now that I upgraded it also happens to me - Ubuntu 22.04.1 with Linux 5.15.0-46-generic - Ubuntu 22.04.1 with Linux 5.18.17-051817 - Ubuntu 22.04.1 with Linux 5.14.21-051421 The error did not appear in using - Ubuntu 20.04 with Linux 5.13.0-52-generic or earlier - Ubuntu 22.04.1 with Linux 5.13.0-051300 I will provide all the information you see necessary to solve the problem. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: blackscreen bot-comment display4k hidpi kernel-bug notlogin uhd -- Black screen with lines when booting kernel 5.14 to 5.18 https://bugs.launchpad.net/bugs/1986740 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986852] Re: Support SMBIOS 3.4 and 3.5 in Jammy for Hardware Enablement
** Description changed: Backport the support for SMBIOS 3.4 and 3.5 specifications in Ubuntu Kinetic (dmidecode 3.4) to Jammy (dmidecode 3.3) to enable new hardware in the LTS release per SRU policy [1]. [1] https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases + + P.S.: SRU template to be done; test package under evaluation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/1986852 Title: Support SMBIOS 3.4 and 3.5 in Jammy for Hardware Enablement Status in dmidecode package in Ubuntu: In Progress Status in dmidecode source package in Jammy: Invalid Status in dmidecode source package in Kinetic: In Progress Bug description: Backport the support for SMBIOS 3.4 and 3.5 specifications in Ubuntu Kinetic (dmidecode 3.4) to Jammy (dmidecode 3.3) to enable new hardware in the LTS release per SRU policy [1]. [1] https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases P.S.: SRU template to be done; test package under evaluation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986857] [NEW] fan doesn't work
Public bug reported: The fan does not work in either the current version of ubuntu or previous (focal fossa). it was working a few months ago, so this may be new to this kernel, i didn't discover when it stopped working directly :( symptoms: gets very hot. no fan. eventually blackscreens while the power remains on. `sensors-detect` eventually outputs: ``` Sorry, no sensors were detected. This is relatively common on laptops, where thermal management is handled by ACPI rather than the OS. ``` `sensors` output is as follows: ``` jdub@compy4:~$ sudo sensors iwlwifi_1-virtual-0 Adapter: Virtual device temp1:+41.0°C asus-isa- Adapter: ISA adapter cpu_fan: 2900 RPM nvme-pci-0500 Adapter: PCI adapter Composite:+55.9°C (low = -5.2°C, high = +83.8°C) (crit = +87.8°C) BAT0-acpi-0 Adapter: ACPI interface in0: 15.83 V amdgpu-pci-0600 Adapter: PCI adapter vddgfx: 756.00 mV vddnb: 874.00 mV edge: +51.0°C slowPPT: 2.00 mW ucsi_source_psy_USBC000:001-isa- Adapter: ISA adapter in0: 0.00 V (min = +0.00 V, max = +0.00 V) curr1: 0.00 A (max = +0.00 A) k10temp-pci-00c3 Adapter: PCI adapter Tctl: +52.9°C nvme-pci-0400 Adapter: PCI adapter Composite:+32.9°C (low = -0.1°C, high = +76.8°C) (crit = +79.8°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+52.0°C (crit = +120.0°C) ``` Description:Ubuntu 22.04.1 LTS Release:22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jdub 2341 F pulseaudio /dev/snd/controlC0: jdub 2341 F pulseaudio /dev/snd/controlC1: jdub 2341 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 17 12:51:23 2022 InstallationDate: Installed on 2021-04-08 (496 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA502IU_GA502IU ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=84a0282e-1a9f-4814-a551-45a4be446ec9 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (0 days ago) dmi.bios.date: 12/30/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA502IU.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA502IU dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA502IU.221:bd12/30/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA502IU_GA502IU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA502IU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus G15 dmi.product.name: ROG Zephyrus G15 GA502IU_GA502IU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986857 Title: fan doesn't work Status in linux package in Ubuntu: New Bug description: The fan does not work in either the current version of ubuntu or previous (focal fossa). it was working a few months ago, so this may be new to this kernel, i didn't discover when it stopped working directly :( symptoms: gets very hot. no fan. eventually blackscreens while the power remains on. `sensors-detect` eventually outputs: ``` Sorry, no sensors were detected. This is relatively common on laptops, where thermal management is handled by ACPI rather than the OS. ``` `sensors` output is as follows: ``` jdub@compy4:~$ sudo sensors iwlwifi_1-virtual-0 Adapter: Virtual device temp1:+41.0°C asus-isa- Adapter: ISA adapter cpu_fan: 2900 RPM nvme-pci-0500 Adapter: PCI adapter Composite:+55.9°C (low = -5.2°C, high = +83.8°C) (crit = +87.8°C) BAT0-acpi-0 Adapter: ACPI interface in0: 15.83 V amdgpu-pci-0600 Adapter: PCI adapter vddgfx: 756.00 mV vddnb: 874.00 mV edge: +51.0°C slowPPT: 2.00 mW ucsi_source_psy_USBC000:001-isa-
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
This is also affecting the MSI MEG Z690I Unify motherboard; can not boot
any live disk images of Ubuntu 22.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test source code: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package, then test grubx64.efi is under
“obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
[Kernel-packages] [Bug 1986852] [NEW] Support SMBIOS 3.4 and 3.5 in Jammy for Hardware Enablement
Public bug reported: Backport the support for SMBIOS 3.4 and 3.5 specifications in Ubuntu Kinetic (dmidecode 3.4) to Jammy (dmidecode 3.3) to enable new hardware in the LTS release per SRU policy [1]. [1] https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases ** Affects: dmidecode (Ubuntu) Importance: Undecided Assignee: Mauricio Faria de Oliveira (mfo) Status: In Progress ** Affects: dmidecode (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: dmidecode (Ubuntu Kinetic) Importance: Undecided Assignee: Mauricio Faria de Oliveira (mfo) Status: In Progress ** Tags: sts ** Also affects: dmidecode (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: dmidecode (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: dmidecode (Ubuntu Jammy) Status: New => Invalid ** Changed in: dmidecode (Ubuntu Kinetic) Status: New => In Progress ** Changed in: dmidecode (Ubuntu Kinetic) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/1986852 Title: Support SMBIOS 3.4 and 3.5 in Jammy for Hardware Enablement Status in dmidecode package in Ubuntu: In Progress Status in dmidecode source package in Jammy: Invalid Status in dmidecode source package in Kinetic: In Progress Bug description: Backport the support for SMBIOS 3.4 and 3.5 specifications in Ubuntu Kinetic (dmidecode 3.4) to Jammy (dmidecode 3.3) to enable new hardware in the LTS release per SRU policy [1]. [1] https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738272] Re: microcode packages, like firmware packages, should be in main
By the way, Debian created a new component, non-free-firmware, last month. I don't believe any Debian packages have switched to it yet. Based on this bug history, I'm guessing we'd want to automatically import those packages to universe then (or main where we want it part of our Canonical-supported set). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1738272 Title: microcode packages, like firmware packages, should be in main Status in firmware-sof package in Ubuntu: New Status in intel-microcode package in Ubuntu: Fix Released Status in iucode-tool package in Ubuntu: Fix Released Bug description: The MIR for intel-microcode and iucode-tool in LP: #139 requested that these packages be shipped in restricted. The iucode-tool package is free software, and is shipped in restricted only because of the circular recommends with intel-microcode. The intel-microcode package contains non-free software (free redistribution, but no source code). However, this code is not part of the OS; it runs /under/ the OS on the CPU, and is analogous to linux-firmware, which we do include in main. The question of suitability for restricted vs. main in Ubuntu was not examined as part of the previous MIR, and the security team signed off on it for "restricted or main as appropriate"; so I think the decision to put it in restricted was not based on a thorough examination of the facts by an archive admin, and does not represent a precedent that needs to be examined further. I believe that these two packages should be promoted to main for consistency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1738272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968062] Re: Jammy / Kinetic: Enable Hibernation for Xen Based Instance Types
** Changed in: linux-aws (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-aws (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1968062
Title:
Jammy / Kinetic: Enable Hibernation for Xen Based Instance Types
Status in linux-aws package in Ubuntu:
Fix Committed
Status in linux-aws source package in Jammy:
Fix Committed
Status in linux-aws source package in Kinetic:
Fix Committed
Bug description:
[Impact]
Hibernation currently fails for all AWS Xen instance types
(c3/c4/i3/m3/m4/r3/r4/t2) with all Jammy 5.15 and Kinetic 5.19 linux-
aws kernels.
When attempting to hibernate, the system gets stuck in
sync_inodes_one_sb() when processing the rootfs, fails to hibernate,
and shuts down. When you start the instance, it starts fresh, and does
not resume from the incomplete hibernation image. Networking is also
broken, and you cannot ssh in.
Upon review of the jammy/linux-aws git log, it appears that the kernel
is missing AWS hibernation enablement patches entirely. These need to
be included to get hibernation working.
[Fix]
Hibernation currently works on the Amazon Linux 2 5.15 Kernel:
https://github.com/amazonlinux/linux/tree/amazon-5.15.y/mainline
After careful review of the amazon-5.15.y/mainline branch, we have
found the below set of patches authored by Amazon AWS Hibernation team
to be minimally sufficient to get hibernation working on both Jammy
5.15 and Kinetic 5.19.
xen: Restore xen-pirqs on resume from hibernation
xen-netfront: call netif_device_attach on resume
xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs.
xen: restore pirqs on resume from hibernation.
block: xen-blkfront: consider new dom0 features on restore
x86: tsc: avoid system instability in hibernation
xen-blkfront: Fixed blkfront_restore to remove a call to negotiate_mq
Revert "xen: dont fiddle with event channel masking in suspend/resume"
PM / hibernate: update the resume offset on SNAPSHOT_SET_SWAP_AREA
x86/xen: close event channels for PIRQs in system core suspend callback
xen/events: add xen_shutdown_pirqs helper function
x86/xen: save and restore steal clock
xen/time: introduce xen_{save,restore}_steal_clock
xen-netfront: add callbacks for PM suspend and hibernation support
xen-blkfront: add callbacks for PM suspend and hibernation
x86/xen: add system core suspend and resume callbacks
x86/xen: Introduce new function to map HYPERVISOR_shared_info on Resume
xenbus: add freeze/thaw/restore callbacks support
xen/manage: introduce helper function to know the on-going suspend mode
xen/manage: keep track of the on-going suspend mode
These patches will be carried as SAUCE patches, and their subjects
marked with "UBUNTU: SAUCE [aws]". Their upstream is the Amazon
Hibernation team, with the repo being the Amazon Linux 2 kernel repo.
[Testcase]
1. Log into Amazon EC2.
2. Select Launch Instance.
3. Under Instance Type, select any from (c3/c4/i3/m3/m4/r3/r4/t2). I suggest
t2.medium.
4. Select the "Ubuntu 22.04 LTS HVM (SSD type)" AMI in the quicklaunch pane.
5. Select your SSH keypair.
6. In storage, select 20gb. Go to the advanced tab, and set Encrypted: Yes.
7. Under Advanced Settings for the instance, set "Stop - Hibernate" to Enable.
8. Create the Instance. SSH in.
9. Wait 5 minutes for hibinit-agent to create /swap-hibinit swapfile and
configure grub.
10. Start a screen session. Echo some text and then detach with ctrl-d.
11. Log out from instance.
12. In EC2, select "Instance State" > "Hibernate".
13. Wait 30 seconds to one minute. The state will go from "Stopping" to
"Stopped".
14. Start the instance again.
15. SSH in.
16. Attempt to resume screen session with "screen -r".
If you are not able to ssh into the instance, hibernation had failed.
If ssh works and the screen session is still running, hibernation was
successful.
Alternatively, the CPC team can run their Hibernation testsuite over
Jammy and Kinetic.
We have built test kernels for Jammy and Kinetic with the patches, and
they are available in the below ppa:
https://launchpad.net/~gerald-yang-tw/+archive/ubuntu/aws-hibernate-
test
If you try and hibernate and resume with the test kernels, hibernation
is successful.
[Where problems could occur]
We are adding a significant amount of code to the Xen subsystem,
spread across many commits. This code has not been mainlined, and is
instead maintained out of tree by the Amazon AWS Hibernation team.
The changes target hibernation, block devices, and clock devices,
specific to those used on AWS Xen instances. Most of these patches
have been applied to Xenial, Bionic, Focal and other series for a long
time, but some patches are new for 5.15 onward.
[Kernel-packages] [Bug 1986470] Re: linux-aws: Move zram to linux-modules
** Package changed: linux (Ubuntu Jammy) => linux-aws (Ubuntu Jammy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1986470 Title: linux-aws: Move zram to linux-modules Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Jammy: Fix Committed Status in linux-aws source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] Amazon has asked to include zram.ko in linux-modules-aws [Test Plan] Extract linux-modules-aws and search for zram.ko [Where things could go wrong] I see no possibility for regression here. [Other Info] SF: #00342563 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1986470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738272] Re: microcode packages, like firmware packages, should be in main
The Kernel Packages team already owns the firmware-sof package. Ubuntu Package Archive Administrators, please promote the package to the main component in Ubuntu 22.04 and Kinetic. ** Changed in: firmware-sof (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1738272 Title: microcode packages, like firmware packages, should be in main Status in firmware-sof package in Ubuntu: New Status in intel-microcode package in Ubuntu: Fix Released Status in iucode-tool package in Ubuntu: Fix Released Bug description: The MIR for intel-microcode and iucode-tool in LP: #139 requested that these packages be shipped in restricted. The iucode-tool package is free software, and is shipped in restricted only because of the circular recommends with intel-microcode. The intel-microcode package contains non-free software (free redistribution, but no source code). However, this code is not part of the OS; it runs /under/ the OS on the CPU, and is analogous to linux-firmware, which we do include in main. The question of suitability for restricted vs. main in Ubuntu was not examined as part of the previous MIR, and the security team signed off on it for "restricted or main as appropriate"; so I think the decision to put it in restricted was not based on a thorough examination of the facts by an archive admin, and does not represent a precedent that needs to be examined further. I believe that these two packages should be promoted to main for consistency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1738272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986834] Re: aws: Include videodev in linux-modules-aws
** Changed in: linux-aws (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1986834 Title: aws: Include videodev in linux-modules-aws Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Jammy: Fix Committed Status in linux-aws source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] The inclusion of the DKMS module v4l2loopback requires videodev infrastructure. It is easier to use if these modules are included by default in linux-modules-aws. [Test Plan] Extract linux-modules-aws and check for the presence of videodev.ko [Where things could go wrong] linux-modules-aws is becoming larger with each new inclusion. Disk space could become an issue on very small installations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1986834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768050] Re: package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status
This happened to me when I upgraded from 20.04 to 22.04 I have had to do this manually as I don't think any of the command lines are correct above. I actually lost my graphic interface in the process. So at black screen I started a new TTY (Ctr alt F2) I have gone to the folder /var/lib/dpkg I copied the diversions-old to a diversion_old.old Then the diversions to diversions-old Here was my diversions file: /usr/lib/x86_64-linux-gnu/libEGL.so /usr/lib/x86_64-linux-gnu/libEGL.so.distrib nvidia-340 /usr/share/dict/words /usr/share/dict/words.pre-dictionaries-common dictionaries-common /usr/lib/i386-linux-gnu/libGLESv2.so.2 /usr/lib/i386-linux-gnu/libGLESv2.so.2.distrib nvidia-340 /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 /usr/lib/x86_64-linux-gnu/libGLESv2.so.2.distrib nvidia-340 /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.distrib nvidia-340 /usr/bin/pg_config /usr/bin/pg_config.libpq-dev postgresql-common /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.distrib nvidia-340 /usr/share/vim/vim82/doc/help.txt /usr/share/vim/vim82/doc/help.txt.vim-tiny vim-runtime /usr/lib/x86_64-linux-gnu/libEGL.so.1 /usr/lib/x86_64-linux-gnu/libEGL.so.1.distrib nvidia-340 /usr/share/man/man1/sh.1.gz /usr/share/man/man1/sh.distrib.1.gz dash /usr/lib/i386-linux-gnu/libGLESv2.so /usr/lib/i386-linux-gnu/libGLESv2.so.distrib nvidia-340 /usr/lib/i386-linux-gnu/libEGL.so /usr/lib/i386-linux-gnu/libEGL.so.distrib nvidia-340 /usr/share/vim/vim82/doc/tags /usr/share/vim/vim82/doc/tags.vim-tiny vim-runtime /usr/lib/i386-linux-gnu/libGL.so /usr/lib/i386-linux-gnu/libGL.so.distrib nvidia-340 /usr/lib/x86_64-linux-gnu/libGL.so.1 /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib nvidia-340 /usr/lib/x86_64-linux-gnu/libGL.so /usr/lib/x86_64-linux-gnu/libGL.so.distrib nvidia-340 /usr/lib/i386-linux-gnu/libGLESv1_CM.so /usr/lib/i386-linux-gnu/libGLESv1_CM.so.distrib nvidia-340 /usr/share/aisleriot/cards/bonded.svg /usr/share/aisleriot/cards/bonded.svg.unbranded branding-ubuntu /usr/lib/i386-linux-gnu/libEGL.so.1 /usr/lib/i386-linux-gnu/libEGL.so.1.distrib nvidia-340 /usr/share/gnome-mahjongg/themes/postmodern.svg /usr/share/gnome-mahjongg/themes/postmodern.svg.unbranded branding-ubuntu /bin/sh /bin/sh.distrib dash /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1 /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.distrib nvidia-340 /usr/share/aisleriot/pixmaps/baize.png /usr/share/aisleriot/pixmaps/baize.png.unbranded branding-ubuntu /usr/share/aisleriot/pixmaps/slot.svg /usr/share/aisleriot/pixmaps/slot.svg.unbranded branding-ubuntu /usr/lib/x86_64-linux-gnu/libGLESv2.so /usr/lib/x86_64-linux-gnu/libGLESv2.so.distrib nvidia-340 /usr/lib/i386-linux-gnu/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so.1.distrib nvidia-340 I basically removed all the diversions for nvidia 340 (they are by groups of 3 lines) Then apt --fix-broken install Now it works -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1768050 Title: package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 (NOT FIXED) Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: There is a previous report, but I don't think this bug has been fixed, it is still there. When I execute "sudo ubuntu-drivers autoinstall" the driver does not installed. then I was told: "diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package" then I trace the bug and found it may be comes from libnvidia-gl-390 package and libnvidia-ifr1-390. and When I try to install only the libnvidia-gl-390 package, I've got: package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1768050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986848] [NEW] Kinetic update: v5.19.1 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.19.1 upstream stable release from git://git.kernel.org/ block: fix default IO priority handling again tools/vm/slabinfo: Handle files in debugfs ACPI: video: Force backlight native for some TongFang devices ACPI: video: Shortening quirk list by identifying Clevo by board_name only ACPI: APEI: Better fix to avoid spamming the console with old error logs crypto: arm64/poly1305 - fix a read out-of-bound ata: sata_mv: Fixes expected number of resources now IRQs are gone arm64: set UXN on swapper page tables Bluetooth: hci_qca: Return wakeup for qca_wakeup Bluetooth: hci_bcm: Add BCM4349B1 variant Bluetooth: hci_bcm: Add DT compatible for CYW55572 dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding Bluetooth: btusb: Add support of IMC Networks PID 0x3568 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586 macintosh/adb: fix oob read in do_adb_query() function x86/speculation: Add RSB VM Exit protections x86/speculation: Add LFENCE to RSB fill sequence Linux 5.19.1 UBUNTU: Upstream stable to v5.19.1 ** Affects: linux (Ubuntu) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Kinetic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.19.1 upstream stable release + from git://git.kernel.org/ -v5.19.1 upstream stable release -from git://git.kernel.org/ + block: fix default IO priority handling again + tools/vm/slabinfo: Handle files in debugfs + ACPI: video: Force backlight native for some TongFang devices + ACPI: video: Shortening quirk list by identifying Clevo by board_name only + ACPI: APEI: Better fix to avoid spamming the console with old error logs + crypto: arm64/poly1305 - fix a read out-of-bound + ata: sata_mv: Fixes expected number of resources now IRQs are gone + arm64: set UXN on swapper page tables + Bluetooth: hci_qca: Return wakeup for qca_wakeup + Bluetooth: hci_bcm: Add BCM4349B1 variant + Bluetooth: hci_bcm: Add DT compatible for CYW55572 + dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding + Bluetooth: btusb: Add support of IMC Networks PID 0x3568 + Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007 + Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675 + Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558 + Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587 + Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586 + macintosh/adb: fix oob read in do_adb_query() function + x86/speculation: Add RSB VM Exit protections + x86/speculation: Add LFENCE to RSB fill sequence + Linux 5.19.1 + UBUNTU: Upstream stable to v5.19.1 -- You received this bug notification because you are a member of Kernel Packages, which is
[Kernel-packages] [Bug 1986470] Re: linux-aws: Move zram to linux-modules
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1986470 Title: linux-aws: Move zram to linux-modules Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] Amazon has asked to include zram.ko in linux-modules-aws [Test Plan] Extract linux-modules-aws and search for zram.ko [Where things could go wrong] I see no possibility for regression here. [Other Info] SF: #00342563 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986834] [NEW] aws: Include videodev in linux-modules-aws
Public bug reported: SRU Justification [Impact] The inclusion of the DKMS module v4l2loopback requires videodev infrastructure. It is easier to use if these modules are included by default in linux-modules-aws. [Test Plan] Extract linux-modules-aws and check for the presence of videodev.ko [Where things could go wrong] linux-modules-aws is becoming larger with each new inclusion. Disk space could become an issue on very small installations. ** Affects: linux-aws (Ubuntu) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-aws (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-aws (Ubuntu Kinetic) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Package changed: linux (Ubuntu Jammy) => linux-aws (Ubuntu Jammy) ** Changed in: linux-aws (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-aws (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-aws (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux-aws (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Kinetic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Summary changed: - aws: Include videodev in linux-moduels-aws + aws: Include videodev in linux-modules-aws -- 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/1986834 Title: aws: Include videodev in linux-modules-aws Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Jammy: In Progress Status in linux-aws source package in Kinetic: In Progress Bug description: SRU Justification [Impact] The inclusion of the DKMS module v4l2loopback requires videodev infrastructure. It is easier to use if these modules are included by default in linux-modules-aws. [Test Plan] Extract linux-modules-aws and check for the presence of videodev.ko [Where things could go wrong] linux-modules-aws is becoming larger with each new inclusion. Disk space could become an issue on very small installations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1986834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986833] [NEW] PolarFire Icicle Kit: L2 Cache wrong interrupts in devicetree
Public bug reported: [Impact] The 5.19 kernel contains support for the PolarFire Icicle board. But booting with linux-image-5.19.0-1002-generic_5.19.0-1002.2_riscv64.deb fails. The cause is that the device-tree incorrectly specifies the PLIC interrupts used for the drivers/soc/sifive/sifive_l2_cache.c. A patch is available as https://lore.kernel.org/all/20220817132521.3159388-1-heinrich.schucha...@canonical.com/ [PATCH 1/1] riscv: dts: microchip: correct L2 cache interrupts This patch only changes the device-tree of the PolarFire Icicle Kit. Please, add the patch to the 5.19 and future kernels. [Test Plan] Use the SiFive Unmatched preinstalled image and install the 5.19 kernel. Try to boot on the Polarfire Icicle board. [Where problems could occur] The fix only concerns a board which has been unsupported by Ubuntu yet. In case of an incorrect fix the board might not boot or otherwise malfunction. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1986833 Title: PolarFire Icicle Kit: L2 Cache wrong interrupts in devicetree Status in linux-riscv package in Ubuntu: New Bug description: [Impact] The 5.19 kernel contains support for the PolarFire Icicle board. But booting with linux-image-5.19.0-1002-generic_5.19.0-1002.2_riscv64.deb fails. The cause is that the device-tree incorrectly specifies the PLIC interrupts used for the drivers/soc/sifive/sifive_l2_cache.c. A patch is available as https://lore.kernel.org/all/20220817132521.3159388-1-heinrich.schucha...@canonical.com/ [PATCH 1/1] riscv: dts: microchip: correct L2 cache interrupts This patch only changes the device-tree of the PolarFire Icicle Kit. Please, add the patch to the 5.19 and future kernels. [Test Plan] Use the SiFive Unmatched preinstalled image and install the 5.19 kernel. Try to boot on the Polarfire Icicle board. [Where problems could occur] The fix only concerns a board which has been unsupported by Ubuntu yet. In case of an incorrect fix the board might not boot or otherwise malfunction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1986833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986564] Re: RTL8188EU module fails on R8188EU: Can't _rtw_init_xmit_priv
Small addition: perhaps not clear from above: The most visable issue, no wireless interface shows up , neither with ifconfig -a, nor with iwconfig (for rtl8188eu on 5.17 oem kernel) regards, Arjan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1986564 Title: RTL8188EU module fails on R8188EU: Can't _rtw_init_xmit_priv Status in linux-signed-oem-5.17 package in Ubuntu: New Bug description: Hi, On my lenovo T430 i installed the linux-oem-22.04 to test out 5.17 kernel, to see if it solved the issue regarding intel AX210/AX211 suspend wake-up issue. I also tried my micro RTL8188 based usb wifi adapter, but it fails to initialize. It works fine on the ubuntu stock 5.15 kernel (and windows) On $ uname -a Linux T430-i7 5.17.0-1015-oem #16-Ubuntu SMP PREEMPT Mon Aug 8 19:09:19 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux loaded r8188eu module manual to set one-time debug options: sudo modprobe r8188eu debug=9 dmesg shows: ``` [ma aug 15 15:46:24 2022] r8188eu: module is from the staging directory, the quality is unknown, you have been warned. [ma aug 15 15:46:24 2022] Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0) [ma aug 15 15:46:24 2022] EEPROM ID = 0x8129 [ma aug 15 15:46:24 2022] usb 1-1.2: reset high-speed USB device number 3 using ehci-pci [ma aug 15 15:46:24 2022] usbcore: registered new interface driver r8188eu [ma aug 15 15:47:09 2022] usbcore: deregistering interface driver r8188eu [ma aug 15 15:47:23 2022] r8188eu: module is from the staging directory, the quality is unknown, you have been warned. [ma aug 15 15:47:23 2022] Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0) [ma aug 15 15:47:23 2022] R8188EU: _ConfigNormalChipOutEP_8188E OutEpQueueSel(0x05), OutEpNumber(2) [ma aug 15 15:47:23 2022] R8188EU: Boot from EFUSE, Autoload OK ! [ma aug 15 15:47:23 2022] R8188EU: bFWReady == false call reset 8051... [ma aug 15 15:47:23 2022] R8188EU: => _8051Reset88E(): 8051 reset success . [ma aug 15 15:47:23 2022] R8188EU: efuse_read_phymap_from_txpktbuf bcnhead:0 [ma aug 15 15:47:23 2022] R8188EU: efuse_read_phymap_from_txpktbuf len:139, lenc:139 [ma aug 15 15:47:23 2022] R8188EU: efuse_read_phymap_from_txpktbuf read count:137 [ma aug 15 15:47:23 2022] EEPROM ID = 0x8129 [ma aug 15 15:47:23 2022] R8188EU: Hal_ReadPowerSavingMode88E , bSupportRemoteWakeup(1) [ma aug 15 15:47:23 2022] R8188EU: ### PS params => power_mgnt(1), usbss_enable(0) ### [ma aug 15 15:47:23 2022] R8188EU: === Path 0, Channel 0 === [ma aug 15 15:47:23 2022] R8188EU: Index24G_CCK_Base[0] = 0x2e [ma aug 15 15:47:23 2022] R8188EU: Index24G_BW40_Base[0] = 0x33 [ma aug 15 15:47:23 2022] R8188EU: === Path 0, Channel 1 === [ma aug 15 15:47:23 2022] R8188EU: Index24G_CCK_Base[1] = 0x2e [ma aug 15 15:47:23 2022] R8188EU: Index24G_BW40_Base[1] = 0x33 [ma aug 15 15:47:23 2022] R8188EU: === Path 0, Channel 2 === [ma aug 15 15:47:23 2022] R8188EU: Index24G_CCK_Base[2] = 0x2e [ma aug 15 15:47:23 2022] R8188EU: Index24G_BW40_Base[2] = 0x33 [ma aug 15 15:47:23 2022] R8188EU: === Path 0, Channel 3 === [ma aug 15 15:47:23 2022] R8188EU: Index24G_CCK_Base[3] = 0x2d [ma aug 15 15:47:23 2022] R8188EU: Index24G_BW40_Base[3] = 0x33 [ma aug 15 15:47:23 2022] R8188EU: === Path 0, Channel 4 === [ma aug 15 15:47:23 2022] R8188EU: Index24G_CCK_Base[4] = 0x2d [ma aug 15 15:47:23 2022] R8188EU: Index24G_BW40_Base[4] = 0x33 [ma aug 15 15:47:23 2022] R8188EU: === Path 0, Channel 5 === [ma aug 15 15:47:23 2022] R8188EU: Index24G_CCK_Base[5] = 0x2d [ma aug 15 15:47:23 2022] R8188EU: Index24G_BW40_Base[5] = 0x33 [ma aug 15 15:47:23 2022] R8188EU: === Path 0, Channel 6 === [ma aug 15 15:47:23 2022] R8188EU: Index24G_CCK_Base[6] = 0x2d [ma aug 15 15:47:23 2022] R8188EU: Index24G_BW40_Base[6] = 0x33 [ma aug 15 15:47:23 2022] R8188EU: === Path 0, Channel 7 === [ma aug 15 15:47:23 2022] R8188EU: Index24G_CCK_Base[7] = 0x2d [ma aug 15 15:47:23 2022] R8188EU: Index24G_BW40_Base[7] = 0x33 [ma aug 15 15:47:23 2022] R8188EU: === Path 0, Channel 8 === [ma aug 15 15:47:23 2022] R8188EU: Index24G_CCK_Base[8] = 0x2d [ma aug 15 15:47:23 2022] R8188EU: Index24G_BW40_Base[8] = 0x33 [ma aug 15 15:47:23 2022] R8188EU: === Path 0, Channel 9 === [ma aug 15 15:47:23 2022] R8188EU: Index24G_CCK_Base[9] = 0x2c [ma aug 15 15:47:23 2022] R8188EU: Index24G_BW40_Base[9] = 0x32 [ma aug 15 15:47:23 2022] R8188EU: === Path 0, Channel 10 === [ma aug 15 15:47:23 2022] R8188EU: Index24G_CCK_Base[10] = 0x2c [ma aug 15 15:47:23 2022] R8188EU: Index24G_BW40_Base[10] = 0x32 [ma aug 15 15:47:23 2022] R8188EU: === Path 0, Channel 11 === [ma aug 15 15:47:23 2022] R8188EU: Index24G_CCK_Base[11] =
[Kernel-packages] [Bug 1986792] Re: There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS
Hi Conie, can you please run `apport-collect 1986792` as requested in comment #3 for this bug? Thanks Jeff -- 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/1986792 Title: There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS Status in linux package in Ubuntu: Incomplete Bug description: 1. Power on SUT and boot into UEFI setup. 2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0. 3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC NVMe RAID disk. 4. Boot into OS then check system logs to check if there are any unexpected failed or error messages. (=> failed, there are failed messages in dmesg, /var/log/syslog, and /var/log/kern.log, showing: pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000] where 10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04) 10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04) 10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04) 10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04) ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978820] Re: Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes
I can verify the fix is working with the released 5.15.0-43.46 -- 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/1978820 Title: Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Released Bug description: Platform: OpenStack Yoga, Ubuntu 22.04 Jammy, Kernel 5.15.0-37-generic Charmed Openstack deployment with HW Offload over Jammy series will look ok until Vault initialization phase, then after initializing Vault all DB-related apps will end up in block/error state over "Failed to connect to MYSQL". Connectivity testing between DB containers located on different nodes will show there is unexplained sporadic packet loss preventing proper communication between the DB related apps. This will happen when the following conditions are met: 1. Control plane (oam, internal spaces) is configured as vlan interfaces on the same OVS bridge used for data plane (over high speed NIC with HW Offload capabilities). 2. OVS was set with HW offload=true (will happen by OVN chrams after Vault initialization) 3. NIC was not yet set to "switchdev" mode (netplan file will be created by OVN chrams after Vault initialization, however will take affect only after node is rebooted) The root cause is the following missing kernel patch: https://patchwork.kernel.org/project/netdevbpf/patch/20220531205447.99236-3-sa...@kernel.org/ To reproduce: Deploy charmed openstack with HW offload while using control plane on the high speed NIC OVS bridge. Before initializing Vault login to one of the innoDB instances and ping the other 2 instances - all ok. Manually enable OVS HW Offload, ping will become inconsistent. Workaround: After the deployment bring-up phase, BEFORE enabling Vault, login to the nodes and manually create 150-charm-ovn.yaml (example below). Then reboot one node after another. When nodes recover proceed with Vault initialization to complete the deployment. #root@node3:/home/ubuntu# cat /etc/netplan/150-charm-ovn.yaml ### # [ WARNING ] # Configuration file maintained by Juju. Local changes may be overwritten. # Config managed by ovn-chassis charm ### network: version: 2 ethernets: ens1f0: virtual-function-count: 8 embedded-switch-mode: switchdev delay-virtual-functions-rebind: true ens1f1: virtual-function-count: 8 embedded-switch-mode: switchdev delay-virtual-functions-rebind: true --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 4 10:46 seq crw-rw 1 root audio 116, 33 Jul 4 10:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=UUID=db1801a9-daa1-4386-b2ec-c65a40bc5dd3 ro intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/05/2015 dmi.bios.release: 1.32 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrP89:bd03/05/2015:br1.32:efr2.53:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr:sku755258-B21: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 755258-B21 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1986743] Re: REQUEST add meson vdec firmware to arm64 linux-firmware package
Thanks for the note. I will send a patch upstream to fix the MODULE_FIRMWARE situation. -- 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/1986743 Title: REQUEST add meson vdec firmware to arm64 linux-firmware package Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Confirmed Status in linux-firmware source package in Kinetic: Confirmed Bug description: [Impact] 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 22.04.1 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 20220329.git681281e40ubuntu3.4 3) What you expected to happen Linux Firmware would include meson vdec blobs https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/meson/vdec 4) What happened instead Linux Firmware does not include meson vdec blobs [Test case] Load meson-vdec driver on HW that supports it and watch firmware load failure. [Fix] Include firmware blobs. [Where Problems Could Occur] This only affects very specific HW. And the blobs have shipped in older series but were dropped incorrectly in Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1986743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981328] Re: Azure: Fix the Focal Azure CVM kernel for VBS VMs
** Changed in: linux-azure-cvm (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-cvm in Ubuntu. https://bugs.launchpad.net/bugs/1981328 Title: Azure: Fix the Focal Azure CVM kernel for VBS VMs Status in linux-azure-cvm package in Ubuntu: Invalid Status in linux-azure-cvm source package in Focal: Fix Committed Bug description: SRU Justification [Impact] The latest 5.4-based linux-azure-cvm kernel (https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux- azure/+git/focal/tag/?h=Ubuntu-azure-cvm-5.4.0-1085.90%2bcvm2) works fine when it runs in an AMD SNP VM, but doesn't work when it runs in a VBS VM (for VBS, please refer to https://docs.microsoft.com/en- us/windows-hardware/design/device-experiences/oem-vbs) [Fix] https://github.com/dcui/linux-azure- cvm/commit/b262b15df05e06be0a43ecc4c72fb3b735a78fe7 [Test Case] Microsoft tested [Where things could go wrong] This could affect regular CVM instances [Other Info] SF: #00340455 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure-cvm/+bug/1981328/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986798] [NEW] Remove unused variable from i915 psr
Public bug reported:
[Impact]
Compiler warns unused variable after commit 0c1d6921b07c ("UBUNTU:
SAUCE: drm/i915/display/psr: Reinstate fix for TGL + AUO panel flicker")
[Fix]
The variable is unused, remove it.
[Test]
Compiler no longer warns about it.
[Where problems could occur]
Nothing.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Won't Fix
** Affects: linux (Ubuntu Jammy)
Importance: Low
Status: Confirmed
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Won't Fix
** Changed in: linux (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Low
--
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/1986798
Title:
Remove unused variable from i915 psr
Status in linux package in Ubuntu:
Won't Fix
Status in linux source package in Jammy:
Confirmed
Bug description:
[Impact]
Compiler warns unused variable after commit 0c1d6921b07c ("UBUNTU:
SAUCE: drm/i915/display/psr: Reinstate fix for TGL + AUO panel flicker")
[Fix]
The variable is unused, remove it.
[Test]
Compiler no longer warns about it.
[Where problems could occur]
Nothing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986798/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986792] 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 1986792 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/1986792 Title: There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS Status in linux package in Ubuntu: Incomplete Bug description: 1. Power on SUT and boot into UEFI setup. 2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0. 3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC NVMe RAID disk. 4. Boot into OS then check system logs to check if there are any unexpected failed or error messages. (=> failed, there are failed messages in dmesg, /var/log/syslog, and /var/log/kern.log, showing: pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000] where 10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04) 10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04) 10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04) 10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04) ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986792] Re: There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS
If the vmd feature is enabled, the messsage will be showed in syslog. ** Attachment added: "syslog dmesg kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986792/+attachment/5609272/+files/dmesg%2C%20syslog%2C%20and%20kern.log.zip -- 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/1986792 Title: There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS Status in linux package in Ubuntu: New Bug description: 1. Power on SUT and boot into UEFI setup. 2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0. 3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC NVMe RAID disk. 4. Boot into OS then check system logs to check if there are any unexpected failed or error messages. (=> failed, there are failed messages in dmesg, /var/log/syslog, and /var/log/kern.log, showing: pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000] where 10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04) 10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04) 10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04) 10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04) ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986792] Re: There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS
if intel vmd feature is disabled, it has "BAR 13: failed to assign" message in the syslog. ** Attachment added: "20220803_disable_VMD_logs.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986792/+attachment/5609273/+files/20220803_disable_VMD_logs.zip -- 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/1986792 Title: There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS Status in linux package in Ubuntu: New Bug description: 1. Power on SUT and boot into UEFI setup. 2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0. 3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC NVMe RAID disk. 4. Boot into OS then check system logs to check if there are any unexpected failed or error messages. (=> failed, there are failed messages in dmesg, /var/log/syslog, and /var/log/kern.log, showing: pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000] where 10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04) 10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04) 10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04) 10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04) ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986792] [NEW] There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS
Public bug reported: 1. Power on SUT and boot into UEFI setup. 2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0. 3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC NVMe RAID disk. 4. Boot into OS then check system logs to check if there are any unexpected failed or error messages. (=> failed, there are failed messages in dmesg, /var/log/syslog, and /var/log/kern.log, showing: pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000] where 10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04) 10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04) 10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04) 10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04) ) ** 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/1986792 Title: There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS Status in linux package in Ubuntu: New Bug description: 1. Power on SUT and boot into UEFI setup. 2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0. 3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC NVMe RAID disk. 4. Boot into OS then check system logs to check if there are any unexpected failed or error messages. (=> failed, there are failed messages in dmesg, /var/log/syslog, and /var/log/kern.log, showing: pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000] pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000] where 10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04) 10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04) 10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04) 10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04) ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986743] Re: REQUEST add meson vdec firmware to arm64 linux-firmware package
The upstream driver is broken in that it doesn't use the MODULE_FIRMWARE macro. ** Also affects: linux-firmware (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-firmware (Ubuntu Kinetic) Status: New => Confirmed ** Description changed: + [Impact] + 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 22.04.1 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 20220329.git681281e40ubuntu3.4 3) What you expected to happen Linux Firmware would include meson vdec blobs https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/meson/vdec 4) What happened instead Linux Firmware does not include meson vdec blobs + + [Test case] + + Load meson-vdec driver on HW that supports it and watch firmware load + failure. + + [Fix] + + Include firmware blobs. + + [Where Problems Could Occur] + + This only affects very specific HW. And the blobs have shipped in older + series but were dropped incorrectly in Jammy. -- 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/1986743 Title: REQUEST add meson vdec firmware to arm64 linux-firmware package Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Confirmed Status in linux-firmware source package in Kinetic: Confirmed Bug description: [Impact] 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 22.04.1 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 20220329.git681281e40ubuntu3.4 3) What you expected to happen Linux Firmware would include meson vdec blobs https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/meson/vdec 4) What happened instead Linux Firmware does not include meson vdec blobs [Test case] Load meson-vdec driver on HW that supports it and watch firmware load failure. [Fix] Include firmware blobs. [Where Problems Could Occur] This only affects very specific HW. And the blobs have shipped in older series but were dropped incorrectly in Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1986743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] Re: GPIO character device v1 API not enabled in kernel
** Changed in: linux-starfive-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-hwe-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-allwinner-5.17 (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-allwinner-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device v1 API not enabled in kernel Status in linux package in Ubuntu: Fix Committed Status in linux-allwinner-5.17 package in Ubuntu: Invalid Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-starfive-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-allwinner-5.17 source package in Jammy: Fix Committed Status in linux-hwe-5.17 source package in Jammy: Fix Committed Status in linux-starfive-5.17 source package in Jammy: Fix Committed Bug description: [Impact] * The libgpiod2 library and gpiod tools shipped in Jammy don't work. * These tools are meant to replace the old sysfs interface and be a better and more efficient way to manipulate GPIOs from userspace. Unfortunately the latest release is still using v1 of the character device kernel API which is not enabled in Ubuntu kernels. * This is Kent Gibsons reply on the linux-gpio mailing list: On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote: > Hi, > > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the > libgpiod package that we ship is still based on the latest version > 1.6.3 which does not implement the API v2. So I'd like to update > libgpiod, do you have any recommendations about what branch/sha1 I > should use? Do you plan to make a release that implements the API v2? > Firstly, libgpiod is Bart's library so he is the authority, but this is my understanding... TLDR: You should keep GPIO_CDEV_V1 enabled. v1 is deprecated from a development perspective, so all new feature development will occur on v2, and new applications should target v2. Existing apps targetting v1, be that directly or via libgpiod v1.6.3, will require GPIO_CDEV_V1 until they migrate to v2. The mainline kernel will continue to support v1 while userspace transitions. libgpiod v2 is in active development, and should reach its first release shortly. Note that it is NOT a plugin replacement for v1. It has a different API, for similar reasons to why we had to switch in the kernel, so apps will need to be actively migrated. I wouldn't suggest making any effort to package libgpiod v2 until Bart makes an official release. Cheers, Kent. [Test Plan] * Run gpioinfo on a machine with exposed GPIOs and check that it lists the GPIOs and doesn't error with gpioinfo: error creating line iterator: Invalid argument [Where problems could occur] * There may be code and scripts that hasn't been tested with a working libgpiod2/gpiod tools and uncover latent bugs. [Other Info] Original bug text: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s
[Kernel-packages] [Bug 1982716] Re: Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9
Enable -proposed channel on HP 440/450/640/650 G9 and install 5.14.0-1049-oem, mic mute and audio mute LEDs work fine on it. ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1982716 Title: Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9 Status in HWE Next: Fix Committed Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-hwe-5.17 source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] The audio mute key (F5) and mic-mute LED (F8) don't work on some HP 440/450/640/650 G9 laptops. [Fix] The HP ProBook 440/450 G9 and EliteBook 640/650 G9 have multiple motherboard design and they are using different subsystem ID of audio codec. Add the same quirk for other MBs. [Test] After applying the fix, the mute LEDs are working. [Where problems could occur] It's low risk as it's specific ID for HP new machines. If the HP ships other machines using same SSID, then the LED may not work on those machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] Re: GPIO character device v1 API not enabled in kernel
** Also affects: linux-starfive-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-starfive-5.17 (Ubuntu) Status: New => Invalid ** Changed in: linux-starfive-5.17 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device v1 API not enabled in kernel Status in linux package in Ubuntu: Fix Committed Status in linux-allwinner-5.17 package in Ubuntu: Invalid Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-starfive-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-allwinner-5.17 source package in Jammy: In Progress Status in linux-hwe-5.17 source package in Jammy: Fix Committed Status in linux-starfive-5.17 source package in Jammy: Fix Committed Bug description: [Impact] * The libgpiod2 library and gpiod tools shipped in Jammy don't work. * These tools are meant to replace the old sysfs interface and be a better and more efficient way to manipulate GPIOs from userspace. Unfortunately the latest release is still using v1 of the character device kernel API which is not enabled in Ubuntu kernels. * This is Kent Gibsons reply on the linux-gpio mailing list: On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote: > Hi, > > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the > libgpiod package that we ship is still based on the latest version > 1.6.3 which does not implement the API v2. So I'd like to update > libgpiod, do you have any recommendations about what branch/sha1 I > should use? Do you plan to make a release that implements the API v2? > Firstly, libgpiod is Bart's library so he is the authority, but this is my understanding... TLDR: You should keep GPIO_CDEV_V1 enabled. v1 is deprecated from a development perspective, so all new feature development will occur on v2, and new applications should target v2. Existing apps targetting v1, be that directly or via libgpiod v1.6.3, will require GPIO_CDEV_V1 until they migrate to v2. The mainline kernel will continue to support v1 while userspace transitions. libgpiod v2 is in active development, and should reach its first release shortly. Note that it is NOT a plugin replacement for v1. It has a different API, for similar reasons to why we had to switch in the kernel, so apps will need to be actively migrated. I wouldn't suggest making any effort to package libgpiod v2 until Bart makes an official release. Cheers, Kent. [Test Plan] * Run gpioinfo on a machine with exposed GPIOs and check that it lists the GPIOs and doesn't error with gpioinfo: error creating line iterator: Invalid argument [Where problems could occur] * There may be code and scripts that hasn't been tested with a working libgpiod2/gpiod tools and uncover latent bugs. [Other Info] Original bug text: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel
[Kernel-packages] [Bug 1953613] Re: GPIO character device v1 API not enabled in kernel
** Also affects: linux-hwe-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.17 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.17 (Ubuntu Jammy) Status: New => In Progress ** Also affects: linux-allwinner-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-allwinner-5.17 (Ubuntu) Status: New => Invalid ** Changed in: linux-allwinner-5.17 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device v1 API not enabled in kernel Status in linux package in Ubuntu: Fix Committed Status in linux-allwinner-5.17 package in Ubuntu: Invalid Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-allwinner-5.17 source package in Jammy: In Progress Status in linux-hwe-5.17 source package in Jammy: In Progress Bug description: [Impact] * The libgpiod2 library and gpiod tools shipped in Jammy don't work. * These tools are meant to replace the old sysfs interface and be a better and more efficient way to manipulate GPIOs from userspace. Unfortunately the latest release is still using v1 of the character device kernel API which is not enabled in Ubuntu kernels. * This is Kent Gibsons reply on the linux-gpio mailing list: On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote: > Hi, > > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the > libgpiod package that we ship is still based on the latest version > 1.6.3 which does not implement the API v2. So I'd like to update > libgpiod, do you have any recommendations about what branch/sha1 I > should use? Do you plan to make a release that implements the API v2? > Firstly, libgpiod is Bart's library so he is the authority, but this is my understanding... TLDR: You should keep GPIO_CDEV_V1 enabled. v1 is deprecated from a development perspective, so all new feature development will occur on v2, and new applications should target v2. Existing apps targetting v1, be that directly or via libgpiod v1.6.3, will require GPIO_CDEV_V1 until they migrate to v2. The mainline kernel will continue to support v1 while userspace transitions. libgpiod v2 is in active development, and should reach its first release shortly. Note that it is NOT a plugin replacement for v1. It has a different API, for similar reasons to why we had to switch in the kernel, so apps will need to be actively migrated. I wouldn't suggest making any effort to package libgpiod v2 until Bart makes an official release. Cheers, Kent. [Test Plan] * Run gpioinfo on a machine with exposed GPIOs and check that it lists the GPIOs and doesn't error with gpioinfo: error creating line iterator: Invalid argument [Where problems could occur] * There may be code and scripts that hasn't been tested with a working libgpiod2/gpiod tools and uncover latent bugs. [Other Info] Original bug text: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel
[Kernel-packages] [Bug 1986623] fstab.txt
apport information ** Attachment added: "fstab.txt" https://bugs.launchpad.net/bugs/1986623/+attachment/5609250/+files/fstab.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/1986623 Title: cryptsetup fails to decrypt root partion during boot Status in cryptsetup package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: During boot, cryptsetup fails to decrypt the root partition in a, seemingly, non-deterministic fashion. I know that the password is correct and that the keymap is not a fault either, because I have specifically chosen the very weak password "123456" for testing purposes. A hardware defect seems also rather unlikely as this behavior does not affect other Linux distributions or FreeBSD. Earlier Ubuntu versions do not seem to be affected either, as this bug appears to have been introduced during a kernel update in 20.04 and persists throughout 20.04-22.04. Unfortunately I cannot pinpoint the exact kernel update that introduced this bug. I have appended the output of cryptsetup when manually called from the initramfs shell. Here the second attempt succeeded in decrypting the root partition, however, it usually takes a lot more attempts to do so. As for some additional information, I can decrypt the same luks partition from a live USB without any problems whatsoever. echo 123456 | cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt # cryptsetup 2.4.3 processing "cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt" # Running command open. # Locking memory. # Installing SIGINT/SIGTERM handler. # Unblocking interruption on signal. # Allocating context for crypt device /dev/nvme0n1p3. # Trying to open and read device /dev/nvme0n1p3 with direct-io. # Initialising device-mapper backend library. # Trying to load any crypt type from device /dev/nvme0n1p3. # Crypto backend (OpenSSL 3.0.2 15 Mar 2022 [default]) initialized in cryptsetup library version 2.4.3. # Detected kernel Linux 5.15.0-46-generic x86_64. # Loading LUKS2 header (repair disabled). # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Trying to read primary LUKS2 header at offset 0x0. # Opening locked device /dev/nvme0n1p3 # Verifying locked device handle (bdev) # LUKS2 header version 2 of size 16384 bytes, checksum sha256. # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc (on-disk) # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc (in-memory) # Trying to read secondary LUKS2 header at offset 0x4000. # Reusing open ro fd on device /dev/nvme0n1p3 # LUKS2 header version 2 of size 16384 bytes, checksum sha256. # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c (on-disk) # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c (in-memory) # Device size 497776852992, offset 16777216. # Device /dev/nvme0n1p3 READ lock released. # PBKDF argon2id, time_ms 2000 (iterations 0), max_memory_kb 1048576, parallel_threads 4. # Activating volume nvme0n1p3_crypt using token (any type) -1. # dm version [ opencount flush ] [16384] (*1) # dm versions [ opencount flush ] [16384] (*1) # Detected dm-ioctl version 4.45.0. # Detected dm-crypt version 1.23.0. # Device-mapper backend running with UDEV support enabled. # dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1) No usable token is available. # STDIN descriptor passphrase entry requested. # Activating volume nvme0n1p3_crypt [keyslot -1] using passphrase. # dm versions [ opencount flush ] [16384] (*1) # dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1) # Keyslot 0 priority 1 != 2 (required), skipped. # Keyslot 1 priority 1 != 2 (required), skipped. # Trying to open LUKS2 keyslot 0. # Running keyslot key derivation. # Reading keyslot area [0x8000]. # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock released. # Verifying key from keyslot 0, digest 0. # Digest 0 (pbkdf2) verify failed with -1. # Trying to open LUKS2 keyslot 1. # Running keyslot key derivation. # Reading keyslot area [0x47000]. # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock released. # Verifying key from
[Kernel-packages] [Bug 1986623] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1986623/+attachment/5609249/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986623 Title: cryptsetup fails to decrypt root partion during boot Status in cryptsetup package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: During boot, cryptsetup fails to decrypt the root partition in a, seemingly, non-deterministic fashion. I know that the password is correct and that the keymap is not a fault either, because I have specifically chosen the very weak password "123456" for testing purposes. A hardware defect seems also rather unlikely as this behavior does not affect other Linux distributions or FreeBSD. Earlier Ubuntu versions do not seem to be affected either, as this bug appears to have been introduced during a kernel update in 20.04 and persists throughout 20.04-22.04. Unfortunately I cannot pinpoint the exact kernel update that introduced this bug. I have appended the output of cryptsetup when manually called from the initramfs shell. Here the second attempt succeeded in decrypting the root partition, however, it usually takes a lot more attempts to do so. As for some additional information, I can decrypt the same luks partition from a live USB without any problems whatsoever. echo 123456 | cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt # cryptsetup 2.4.3 processing "cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt" # Running command open. # Locking memory. # Installing SIGINT/SIGTERM handler. # Unblocking interruption on signal. # Allocating context for crypt device /dev/nvme0n1p3. # Trying to open and read device /dev/nvme0n1p3 with direct-io. # Initialising device-mapper backend library. # Trying to load any crypt type from device /dev/nvme0n1p3. # Crypto backend (OpenSSL 3.0.2 15 Mar 2022 [default]) initialized in cryptsetup library version 2.4.3. # Detected kernel Linux 5.15.0-46-generic x86_64. # Loading LUKS2 header (repair disabled). # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Trying to read primary LUKS2 header at offset 0x0. # Opening locked device /dev/nvme0n1p3 # Verifying locked device handle (bdev) # LUKS2 header version 2 of size 16384 bytes, checksum sha256. # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc (on-disk) # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc (in-memory) # Trying to read secondary LUKS2 header at offset 0x4000. # Reusing open ro fd on device /dev/nvme0n1p3 # LUKS2 header version 2 of size 16384 bytes, checksum sha256. # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c (on-disk) # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c (in-memory) # Device size 497776852992, offset 16777216. # Device /dev/nvme0n1p3 READ lock released. # PBKDF argon2id, time_ms 2000 (iterations 0), max_memory_kb 1048576, parallel_threads 4. # Activating volume nvme0n1p3_crypt using token (any type) -1. # dm version [ opencount flush ] [16384] (*1) # dm versions [ opencount flush ] [16384] (*1) # Detected dm-ioctl version 4.45.0. # Detected dm-crypt version 1.23.0. # Device-mapper backend running with UDEV support enabled. # dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1) No usable token is available. # STDIN descriptor passphrase entry requested. # Activating volume nvme0n1p3_crypt [keyslot -1] using passphrase. # dm versions [ opencount flush ] [16384] (*1) # dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1) # Keyslot 0 priority 1 != 2 (required), skipped. # Keyslot 1 priority 1 != 2 (required), skipped. # Trying to open LUKS2 keyslot 0. # Running keyslot key derivation. # Reading keyslot area [0x8000]. # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock released. # Verifying key from keyslot 0, digest 0. # Digest 0 (pbkdf2) verify failed with -1. # Trying to open LUKS2 keyslot 1. # Running keyslot key derivation. # Reading keyslot area [0x47000]. # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock released. #
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
** Also affects: linux-hwe-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-5.17 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Committed
** Changed in: linux-hwe-5.17 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-hwe-5.17 (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986623] Re: cryptsetup fails to decrypt root partion during boot
apport information ** Tags added: apport-collected jammy ** Description changed: During boot, cryptsetup fails to decrypt the root partition in a, seemingly, non-deterministic fashion. I know that the password is correct and that the keymap is not a fault either, because I have specifically chosen the very weak password "123456" for testing purposes. A hardware defect seems also rather unlikely as this behavior does not affect other Linux distributions or FreeBSD. Earlier Ubuntu versions do not seem to be affected either, as this bug appears to have been introduced during a kernel update in 20.04 and persists throughout 20.04-22.04. Unfortunately I cannot pinpoint the exact kernel update that introduced this bug. I have appended the output of cryptsetup when manually called from the initramfs shell. Here the second attempt succeeded in decrypting the root partition, however, it usually takes a lot more attempts to do so. As for some additional information, I can decrypt the same luks partition from a live USB without any problems whatsoever. echo 123456 | cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt # cryptsetup 2.4.3 processing "cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt" # Running command open. # Locking memory. # Installing SIGINT/SIGTERM handler. # Unblocking interruption on signal. # Allocating context for crypt device /dev/nvme0n1p3. # Trying to open and read device /dev/nvme0n1p3 with direct-io. # Initialising device-mapper backend library. # Trying to load any crypt type from device /dev/nvme0n1p3. # Crypto backend (OpenSSL 3.0.2 15 Mar 2022 [default]) initialized in cryptsetup library version 2.4.3. # Detected kernel Linux 5.15.0-46-generic x86_64. # Loading LUKS2 header (repair disabled). # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Trying to read primary LUKS2 header at offset 0x0. # Opening locked device /dev/nvme0n1p3 # Verifying locked device handle (bdev) # LUKS2 header version 2 of size 16384 bytes, checksum sha256. # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc (on-disk) # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc (in-memory) # Trying to read secondary LUKS2 header at offset 0x4000. # Reusing open ro fd on device /dev/nvme0n1p3 # LUKS2 header version 2 of size 16384 bytes, checksum sha256. # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c (on-disk) # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c (in-memory) # Device size 497776852992, offset 16777216. # Device /dev/nvme0n1p3 READ lock released. # PBKDF argon2id, time_ms 2000 (iterations 0), max_memory_kb 1048576, parallel_threads 4. # Activating volume nvme0n1p3_crypt using token (any type) -1. # dm version [ opencount flush ] [16384] (*1) # dm versions [ opencount flush ] [16384] (*1) # Detected dm-ioctl version 4.45.0. # Detected dm-crypt version 1.23.0. # Device-mapper backend running with UDEV support enabled. # dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1) No usable token is available. # STDIN descriptor passphrase entry requested. # Activating volume nvme0n1p3_crypt [keyslot -1] using passphrase. # dm versions [ opencount flush ] [16384] (*1) # dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1) # Keyslot 0 priority 1 != 2 (required), skipped. # Keyslot 1 priority 1 != 2 (required), skipped. # Trying to open LUKS2 keyslot 0. # Running keyslot key derivation. # Reading keyslot area [0x8000]. # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock released. # Verifying key from keyslot 0, digest 0. # Digest 0 (pbkdf2) verify failed with -1. # Trying to open LUKS2 keyslot 1. # Running keyslot key derivation. # Reading keyslot area [0x47000]. # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock released. # Verifying key from keyslot 1, digest 0. # Digest 0 (pbkdf2) verify failed with -1. # Releasing crypt device /dev/nvme0n1p3 context. # Releasing device-mapper backend. # Closing read only fd for /dev/nvme0n1p3. # Unlocking memory. Command failed with code -2 (no permission or bad passphrase). echo 123456 | cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt #
[Kernel-packages] [Bug 1986623] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1986623/+attachment/5609248/+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/1986623 Title: cryptsetup fails to decrypt root partion during boot Status in cryptsetup package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: During boot, cryptsetup fails to decrypt the root partition in a, seemingly, non-deterministic fashion. I know that the password is correct and that the keymap is not a fault either, because I have specifically chosen the very weak password "123456" for testing purposes. A hardware defect seems also rather unlikely as this behavior does not affect other Linux distributions or FreeBSD. Earlier Ubuntu versions do not seem to be affected either, as this bug appears to have been introduced during a kernel update in 20.04 and persists throughout 20.04-22.04. Unfortunately I cannot pinpoint the exact kernel update that introduced this bug. I have appended the output of cryptsetup when manually called from the initramfs shell. Here the second attempt succeeded in decrypting the root partition, however, it usually takes a lot more attempts to do so. As for some additional information, I can decrypt the same luks partition from a live USB without any problems whatsoever. echo 123456 | cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt # cryptsetup 2.4.3 processing "cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt" # Running command open. # Locking memory. # Installing SIGINT/SIGTERM handler. # Unblocking interruption on signal. # Allocating context for crypt device /dev/nvme0n1p3. # Trying to open and read device /dev/nvme0n1p3 with direct-io. # Initialising device-mapper backend library. # Trying to load any crypt type from device /dev/nvme0n1p3. # Crypto backend (OpenSSL 3.0.2 15 Mar 2022 [default]) initialized in cryptsetup library version 2.4.3. # Detected kernel Linux 5.15.0-46-generic x86_64. # Loading LUKS2 header (repair disabled). # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Trying to read primary LUKS2 header at offset 0x0. # Opening locked device /dev/nvme0n1p3 # Verifying locked device handle (bdev) # LUKS2 header version 2 of size 16384 bytes, checksum sha256. # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc (on-disk) # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc (in-memory) # Trying to read secondary LUKS2 header at offset 0x4000. # Reusing open ro fd on device /dev/nvme0n1p3 # LUKS2 header version 2 of size 16384 bytes, checksum sha256. # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c (on-disk) # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c (in-memory) # Device size 497776852992, offset 16777216. # Device /dev/nvme0n1p3 READ lock released. # PBKDF argon2id, time_ms 2000 (iterations 0), max_memory_kb 1048576, parallel_threads 4. # Activating volume nvme0n1p3_crypt using token (any type) -1. # dm version [ opencount flush ] [16384] (*1) # dm versions [ opencount flush ] [16384] (*1) # Detected dm-ioctl version 4.45.0. # Detected dm-crypt version 1.23.0. # Device-mapper backend running with UDEV support enabled. # dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1) No usable token is available. # STDIN descriptor passphrase entry requested. # Activating volume nvme0n1p3_crypt [keyslot -1] using passphrase. # dm versions [ opencount flush ] [16384] (*1) # dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1) # Keyslot 0 priority 1 != 2 (required), skipped. # Keyslot 1 priority 1 != 2 (required), skipped. # Trying to open LUKS2 keyslot 0. # Running keyslot key derivation. # Reading keyslot area [0x8000]. # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock released. # Verifying key from keyslot 0, digest 0. # Digest 0 (pbkdf2) verify failed with -1. # Trying to open LUKS2 keyslot 1. # Running keyslot key derivation. # Reading keyslot area [0x47000]. # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock
[Kernel-packages] [Bug 1986743] Re: REQUEST add meson vdec firmware to arm64 linux-firmware package
Oh it's a staging driver that wants it. -- 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/1986743 Title: REQUEST add meson vdec firmware to arm64 linux-firmware package Status in linux-firmware package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 22.04.1 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 20220329.git681281e40ubuntu3.4 3) What you expected to happen Linux Firmware would include meson vdec blobs https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/meson/vdec 4) What happened instead Linux Firmware does not include meson vdec blobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1986743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986743] Re: REQUEST add meson vdec firmware to arm64 linux-firmware package
These firmware blobs are excluded from the package because current kernels don't reference them. What kernel are you running and what HW do you have that needs it? Please run 'apport-bug 1986743' on the affected machine. -- 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/1986743 Title: REQUEST add meson vdec firmware to arm64 linux-firmware package Status in linux-firmware package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 22.04.1 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 20220329.git681281e40ubuntu3.4 3) What you expected to happen Linux Firmware would include meson vdec blobs https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/meson/vdec 4) What happened instead Linux Firmware does not include meson vdec blobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1986743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1986520] Re: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS
You can usually replicate that behavior by starting a few guests and instead of shutdown stopping the libvirt-guests service. If that works in your case as well it will easen having a look, so let me ask does that work for 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/1986520 Title: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hardware Configuration: Server MTM: Bona POR SE450 OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) BMC Version: 1.40 (Build ID: USX311E) UEFI Version: 1.03 (Build ID: CME105C) LXPM Version: 3.19 (Build ID: CML103A) CPU: Xeon Silver 4314 16C 135W 2.4GHz DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; HMA84GR7CJR4N-XNT4 DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2 IO Config: RAID: Intel VROC (VMD NVMe RAID) Premium SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 Ethernet Adapter SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter Storage: DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD PSU1: CFFv4 AC 1100W (Delta) 110V PSU2: CFFv4 AC 1100W (Delta) 110V M/B build version: PASS5 MB Steps: 1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk. 2. Install KVM features and desktop GUI. 3. Run "apt upgrade" to update packages. 4. Create a namespace on BPS DIMM App Direct Not Interleaved mode. 5. Run "virt-manager" then install Windows Server 2022 on the namespace. 6. Reboot Guest OS and Host OS to check if there is any unexpected error in system logs. (=> failed, there are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] ) Expected behaviors: There are no any unexpected errors in system logs. Current behaviors: There are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1986520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984034] Re: Backport patches needed to allow live migration under SEV
https://lists.ubuntu.com/archives/kernel-team/2022-August/132504.html https://lists.ubuntu.com/archives/kernel-team/2022-August/132508.html Patches have been sent to mailing list and applied. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1984034 Title: Backport patches needed to allow live migration under SEV Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Bug description: https://canonical.my.salesforce.com/5004K09oeuI Upstream (v5.16) patches needed to allow live migration of confidential VMs. [Impact] No support for live-migration of confidential VMs currently [Fix] Backport 5 patches from v5.16 [Test] GCP confirmed that live-migration works with these patches. [Regression Potential] This was never working so there should be low risk of regression. Most of the changes are KVM-related so could have an impact on KVM. However most of the changes are new code so risk is low. More details in the SF case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1984034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
