[Kernel-packages] [Bug 1985067] Re: kvm run failed Bad address
This patch is missing in QEMU: commit 8f013700ebf96edb4d481e4d2471c3ed246c58ef hw/riscv: virt: Exit if the user provided -bios in combination with KVM https://patchwork.kernel.org/project/qemu-devel/patch/20220422003656.1648121-19-alistair.fran...@opensource.wdc.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1985067 Title: kvm run failed Bad address Status in linux-starfive-5.17 package in Ubuntu: New Bug description: Running QEMU with linux-starfive-5.17 results in a crash: $ qemu-system-riscv64 -M virt -cpu host -accel kvm -m 4G -smp 4 -nographic -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/u-boot.bin -object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem -mem-prealloc -drive file=riscv64_2.img,format=raw,if=virtio -drive file=/mnt/cidata-riscv64-2.iso,format=raw,if=virtio,read-only=on -global driver=cfi.pflash01,property=secure,value=off -device virtio-net-pci,mac=00:00:00:00:01:01,netdev=eth0 -netdev user,id=eth0,hostfwd=tcp::8141-:22 -chardev socket,id=char1,server=on,path=/tmp/vsock2 -device virtio-net-pci,mac=00:00:00:00:01:02,netdev=eth1,mrg_rxbuf=off -netdev type=vhost-user,id=eth1,chardev=char1,vhostforce=on,queues=2 qemu-system-riscv64: -chardev socket,id=char1,server=on,path=/tmp/vsock2: info: QEMU waiting for connection on: disconnected:unix:/tmp/vsock2,server=on error: kvm run failed Bad address pc 80201738 mhartid mstatus 0002 mip mie mideleg medeleg mtvec mepc mcause mtval mscratch x0/zero x1/ra8000f38c x2/sp 801fee80 x3/gp x4/tp x5/t0801fee00 x6/t1 0001 x7/t2 x8/s0801fee90 x9/s1bf00 x10/a0 801fee90 x11/a1 x12/a2 0170 x13/a3 801ff000 x14/a4 0048 x15/a5 80201738 x16/a6 x17/a7 x18/s2 x19/s3 x20/s4 x21/s5 x22/s6 x23/s7 x24/s8 x25/s9 x26/s10 x27/s11 x28/t3 x29/t4 x30/t5 x31/t6 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 13:39 seq crw-rw 1 root audio 116, 33 Aug 11 13:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. Virtio network device +-02.0 Red Hat, Inc. Virtio network device +-03.0 Red Hat, Inc. Virtio block device \-04.0 Red Hat, Inc. Virtio block device Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: linux (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1004-starfive root=UUID=17bdec56-5406-45c4-9cfa-b72c62340cc7 ro default_hugepagesz=2M hugepagesz=2M hugepages=5120 ProcVersionSignature: Ubuntu 5.17.0-1004.5-starfive 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1004-starfive N/A linux-backports-modules-5.17.0-1004-starfive N/A linux-firmware20220711.gitdfa29317-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1004-starfive riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-starfive-5.17/+bug/1985067/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : http
[Kernel-packages] [Bug 1985067] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1985067/+attachment/5607881/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1985067 Title: kvm run failed Bad address Status in linux-starfive-5.17 package in Ubuntu: New Bug description: Running QEMU with linux-starfive-5.17 results in a crash: $ qemu-system-riscv64 -M virt -cpu host -accel kvm -m 4G -smp 4 -nographic -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/u-boot.bin -object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem -mem-prealloc -drive file=riscv64_2.img,format=raw,if=virtio -drive file=/mnt/cidata-riscv64-2.iso,format=raw,if=virtio,read-only=on -global driver=cfi.pflash01,property=secure,value=off -device virtio-net-pci,mac=00:00:00:00:01:01,netdev=eth0 -netdev user,id=eth0,hostfwd=tcp::8141-:22 -chardev socket,id=char1,server=on,path=/tmp/vsock2 -device virtio-net-pci,mac=00:00:00:00:01:02,netdev=eth1,mrg_rxbuf=off -netdev type=vhost-user,id=eth1,chardev=char1,vhostforce=on,queues=2 qemu-system-riscv64: -chardev socket,id=char1,server=on,path=/tmp/vsock2: info: QEMU waiting for connection on: disconnected:unix:/tmp/vsock2,server=on error: kvm run failed Bad address pc 80201738 mhartid mstatus 0002 mip mie mideleg medeleg mtvec mepc mcause mtval mscratch x0/zero x1/ra8000f38c x2/sp 801fee80 x3/gp x4/tp x5/t0801fee00 x6/t1 0001 x7/t2 x8/s0801fee90 x9/s1bf00 x10/a0 801fee90 x11/a1 x12/a2 0170 x13/a3 801ff000 x14/a4 0048 x15/a5 80201738 x16/a6 x17/a7 x18/s2 x19/s3 x20/s4 x21/s5 x22/s6 x23/s7 x24/s8 x25/s9 x26/s10 x27/s11 x28/t3 x29/t4 x30/t5 x31/t6 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 13:39 seq crw-rw 1 root audio 116, 33 Aug 11 13:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. Virtio network device +-02.0 Red Hat, Inc. Virtio network device +-03.0 Red Hat, Inc. Virtio block device \-04.0 Red Hat, Inc. Virtio block device Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: linux (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1004-starfive root=UUID=17bdec56-5406-45c4-9cfa-b72c62340cc7 ro default_hugepagesz=2M hugepagesz=2M hugepages=5120 ProcVersionSignature: Ubuntu 5.17.0-1004.5-starfive 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1004-starfive N/A linux-backports-modules-5.17.0-1004-starfive N/A linux-firmware20220711.gitdfa29317-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1004-starfive riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-starfive-5.17/+bug/1985067/+subscriptions -- Mailing list: https://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 1985067] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1985067/+attachment/5607880/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1985067 Title: kvm run failed Bad address Status in linux-starfive-5.17 package in Ubuntu: New Bug description: Running QEMU with linux-starfive-5.17 results in a crash: $ qemu-system-riscv64 -M virt -cpu host -accel kvm -m 4G -smp 4 -nographic -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/u-boot.bin -object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem -mem-prealloc -drive file=riscv64_2.img,format=raw,if=virtio -drive file=/mnt/cidata-riscv64-2.iso,format=raw,if=virtio,read-only=on -global driver=cfi.pflash01,property=secure,value=off -device virtio-net-pci,mac=00:00:00:00:01:01,netdev=eth0 -netdev user,id=eth0,hostfwd=tcp::8141-:22 -chardev socket,id=char1,server=on,path=/tmp/vsock2 -device virtio-net-pci,mac=00:00:00:00:01:02,netdev=eth1,mrg_rxbuf=off -netdev type=vhost-user,id=eth1,chardev=char1,vhostforce=on,queues=2 qemu-system-riscv64: -chardev socket,id=char1,server=on,path=/tmp/vsock2: info: QEMU waiting for connection on: disconnected:unix:/tmp/vsock2,server=on error: kvm run failed Bad address pc 80201738 mhartid mstatus 0002 mip mie mideleg medeleg mtvec mepc mcause mtval mscratch x0/zero x1/ra8000f38c x2/sp 801fee80 x3/gp x4/tp x5/t0801fee00 x6/t1 0001 x7/t2 x8/s0801fee90 x9/s1bf00 x10/a0 801fee90 x11/a1 x12/a2 0170 x13/a3 801ff000 x14/a4 0048 x15/a5 80201738 x16/a6 x17/a7 x18/s2 x19/s3 x20/s4 x21/s5 x22/s6 x23/s7 x24/s8 x25/s9 x26/s10 x27/s11 x28/t3 x29/t4 x30/t5 x31/t6 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 13:39 seq crw-rw 1 root audio 116, 33 Aug 11 13:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. Virtio network device +-02.0 Red Hat, Inc. Virtio network device +-03.0 Red Hat, Inc. Virtio block device \-04.0 Red Hat, Inc. Virtio block device Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: linux (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1004-starfive root=UUID=17bdec56-5406-45c4-9cfa-b72c62340cc7 ro default_hugepagesz=2M hugepagesz=2M hugepages=5120 ProcVersionSignature: Ubuntu 5.17.0-1004.5-starfive 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1004-starfive N/A linux-backports-modules-5.17.0-1004-starfive N/A linux-firmware20220711.gitdfa29317-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1004-starfive riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-starfive-5.17/+bug/1985067/+subscriptions -- Mailing list: https://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 1985067] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1985067/+attachment/5607882/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1985067 Title: kvm run failed Bad address Status in linux-starfive-5.17 package in Ubuntu: New Bug description: Running QEMU with linux-starfive-5.17 results in a crash: $ qemu-system-riscv64 -M virt -cpu host -accel kvm -m 4G -smp 4 -nographic -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/u-boot.bin -object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem -mem-prealloc -drive file=riscv64_2.img,format=raw,if=virtio -drive file=/mnt/cidata-riscv64-2.iso,format=raw,if=virtio,read-only=on -global driver=cfi.pflash01,property=secure,value=off -device virtio-net-pci,mac=00:00:00:00:01:01,netdev=eth0 -netdev user,id=eth0,hostfwd=tcp::8141-:22 -chardev socket,id=char1,server=on,path=/tmp/vsock2 -device virtio-net-pci,mac=00:00:00:00:01:02,netdev=eth1,mrg_rxbuf=off -netdev type=vhost-user,id=eth1,chardev=char1,vhostforce=on,queues=2 qemu-system-riscv64: -chardev socket,id=char1,server=on,path=/tmp/vsock2: info: QEMU waiting for connection on: disconnected:unix:/tmp/vsock2,server=on error: kvm run failed Bad address pc 80201738 mhartid mstatus 0002 mip mie mideleg medeleg mtvec mepc mcause mtval mscratch x0/zero x1/ra8000f38c x2/sp 801fee80 x3/gp x4/tp x5/t0801fee00 x6/t1 0001 x7/t2 x8/s0801fee90 x9/s1bf00 x10/a0 801fee90 x11/a1 x12/a2 0170 x13/a3 801ff000 x14/a4 0048 x15/a5 80201738 x16/a6 x17/a7 x18/s2 x19/s3 x20/s4 x21/s5 x22/s6 x23/s7 x24/s8 x25/s9 x26/s10 x27/s11 x28/t3 x29/t4 x30/t5 x31/t6 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 13:39 seq crw-rw 1 root audio 116, 33 Aug 11 13:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. Virtio network device +-02.0 Red Hat, Inc. Virtio network device +-03.0 Red Hat, Inc. Virtio block device \-04.0 Red Hat, Inc. Virtio block device Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: linux (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1004-starfive root=UUID=17bdec56-5406-45c4-9cfa-b72c62340cc7 ro default_hugepagesz=2M hugepagesz=2M hugepages=5120 ProcVersionSignature: Ubuntu 5.17.0-1004.5-starfive 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1004-starfive N/A linux-backports-modules-5.17.0-1004-starfive N/A linux-firmware20220711.gitdfa29317-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1004-starfive riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-starfive-5.17/+bug/1985067/+subscriptions -- Mailing list: https://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 1985067] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1985067/+attachment/5607879/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1985067 Title: kvm run failed Bad address Status in linux-starfive-5.17 package in Ubuntu: New Bug description: Running QEMU with linux-starfive-5.17 results in a crash: $ qemu-system-riscv64 -M virt -cpu host -accel kvm -m 4G -smp 4 -nographic -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/u-boot.bin -object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem -mem-prealloc -drive file=riscv64_2.img,format=raw,if=virtio -drive file=/mnt/cidata-riscv64-2.iso,format=raw,if=virtio,read-only=on -global driver=cfi.pflash01,property=secure,value=off -device virtio-net-pci,mac=00:00:00:00:01:01,netdev=eth0 -netdev user,id=eth0,hostfwd=tcp::8141-:22 -chardev socket,id=char1,server=on,path=/tmp/vsock2 -device virtio-net-pci,mac=00:00:00:00:01:02,netdev=eth1,mrg_rxbuf=off -netdev type=vhost-user,id=eth1,chardev=char1,vhostforce=on,queues=2 qemu-system-riscv64: -chardev socket,id=char1,server=on,path=/tmp/vsock2: info: QEMU waiting for connection on: disconnected:unix:/tmp/vsock2,server=on error: kvm run failed Bad address pc 80201738 mhartid mstatus 0002 mip mie mideleg medeleg mtvec mepc mcause mtval mscratch x0/zero x1/ra8000f38c x2/sp 801fee80 x3/gp x4/tp x5/t0801fee00 x6/t1 0001 x7/t2 x8/s0801fee90 x9/s1bf00 x10/a0 801fee90 x11/a1 x12/a2 0170 x13/a3 801ff000 x14/a4 0048 x15/a5 80201738 x16/a6 x17/a7 x18/s2 x19/s3 x20/s4 x21/s5 x22/s6 x23/s7 x24/s8 x25/s9 x26/s10 x27/s11 x28/t3 x29/t4 x30/t5 x31/t6 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 13:39 seq crw-rw 1 root audio 116, 33 Aug 11 13:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. Virtio network device +-02.0 Red Hat, Inc. Virtio network device +-03.0 Red Hat, Inc. Virtio block device \-04.0 Red Hat, Inc. Virtio block device Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: linux (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1004-starfive root=UUID=17bdec56-5406-45c4-9cfa-b72c62340cc7 ro default_hugepagesz=2M hugepagesz=2M hugepages=5120 ProcVersionSignature: Ubuntu 5.17.0-1004.5-starfive 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1004-starfive N/A linux-backports-modules-5.17.0-1004-starfive N/A linux-firmware20220711.gitdfa29317-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1004-starfive riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-starfive-5.17/+bug/1985067/+subscriptions -- Mailing list: https://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 1985067] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1985067/+attachment/5607877/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1985067 Title: kvm run failed Bad address Status in linux-starfive-5.17 package in Ubuntu: New Bug description: Running QEMU with linux-starfive-5.17 results in a crash: $ qemu-system-riscv64 -M virt -cpu host -accel kvm -m 4G -smp 4 -nographic -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/u-boot.bin -object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem -mem-prealloc -drive file=riscv64_2.img,format=raw,if=virtio -drive file=/mnt/cidata-riscv64-2.iso,format=raw,if=virtio,read-only=on -global driver=cfi.pflash01,property=secure,value=off -device virtio-net-pci,mac=00:00:00:00:01:01,netdev=eth0 -netdev user,id=eth0,hostfwd=tcp::8141-:22 -chardev socket,id=char1,server=on,path=/tmp/vsock2 -device virtio-net-pci,mac=00:00:00:00:01:02,netdev=eth1,mrg_rxbuf=off -netdev type=vhost-user,id=eth1,chardev=char1,vhostforce=on,queues=2 qemu-system-riscv64: -chardev socket,id=char1,server=on,path=/tmp/vsock2: info: QEMU waiting for connection on: disconnected:unix:/tmp/vsock2,server=on error: kvm run failed Bad address pc 80201738 mhartid mstatus 0002 mip mie mideleg medeleg mtvec mepc mcause mtval mscratch x0/zero x1/ra8000f38c x2/sp 801fee80 x3/gp x4/tp x5/t0801fee00 x6/t1 0001 x7/t2 x8/s0801fee90 x9/s1bf00 x10/a0 801fee90 x11/a1 x12/a2 0170 x13/a3 801ff000 x14/a4 0048 x15/a5 80201738 x16/a6 x17/a7 x18/s2 x19/s3 x20/s4 x21/s5 x22/s6 x23/s7 x24/s8 x25/s9 x26/s10 x27/s11 x28/t3 x29/t4 x30/t5 x31/t6 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 13:39 seq crw-rw 1 root audio 116, 33 Aug 11 13:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. Virtio network device +-02.0 Red Hat, Inc. Virtio network device +-03.0 Red Hat, Inc. Virtio block device \-04.0 Red Hat, Inc. Virtio block device Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: linux (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1004-starfive root=UUID=17bdec56-5406-45c4-9cfa-b72c62340cc7 ro default_hugepagesz=2M hugepagesz=2M hugepages=5120 ProcVersionSignature: Ubuntu 5.17.0-1004.5-starfive 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1004-starfive N/A linux-backports-modules-5.17.0-1004-starfive N/A linux-firmware20220711.gitdfa29317-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1004-starfive riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-starfive-5.17/+bug/1985067/+subscriptions -- Mailing list: https://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 1985067] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1985067/+attachment/5607878/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1985067 Title: kvm run failed Bad address Status in linux-starfive-5.17 package in Ubuntu: New Bug description: Running QEMU with linux-starfive-5.17 results in a crash: $ qemu-system-riscv64 -M virt -cpu host -accel kvm -m 4G -smp 4 -nographic -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/u-boot.bin -object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem -mem-prealloc -drive file=riscv64_2.img,format=raw,if=virtio -drive file=/mnt/cidata-riscv64-2.iso,format=raw,if=virtio,read-only=on -global driver=cfi.pflash01,property=secure,value=off -device virtio-net-pci,mac=00:00:00:00:01:01,netdev=eth0 -netdev user,id=eth0,hostfwd=tcp::8141-:22 -chardev socket,id=char1,server=on,path=/tmp/vsock2 -device virtio-net-pci,mac=00:00:00:00:01:02,netdev=eth1,mrg_rxbuf=off -netdev type=vhost-user,id=eth1,chardev=char1,vhostforce=on,queues=2 qemu-system-riscv64: -chardev socket,id=char1,server=on,path=/tmp/vsock2: info: QEMU waiting for connection on: disconnected:unix:/tmp/vsock2,server=on error: kvm run failed Bad address pc 80201738 mhartid mstatus 0002 mip mie mideleg medeleg mtvec mepc mcause mtval mscratch x0/zero x1/ra8000f38c x2/sp 801fee80 x3/gp x4/tp x5/t0801fee00 x6/t1 0001 x7/t2 x8/s0801fee90 x9/s1bf00 x10/a0 801fee90 x11/a1 x12/a2 0170 x13/a3 801ff000 x14/a4 0048 x15/a5 80201738 x16/a6 x17/a7 x18/s2 x19/s3 x20/s4 x21/s5 x22/s6 x23/s7 x24/s8 x25/s9 x26/s10 x27/s11 x28/t3 x29/t4 x30/t5 x31/t6 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 13:39 seq crw-rw 1 root audio 116, 33 Aug 11 13:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. Virtio network device +-02.0 Red Hat, Inc. Virtio network device +-03.0 Red Hat, Inc. Virtio block device \-04.0 Red Hat, Inc. Virtio block device Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: linux (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1004-starfive root=UUID=17bdec56-5406-45c4-9cfa-b72c62340cc7 ro default_hugepagesz=2M hugepagesz=2M hugepages=5120 ProcVersionSignature: Ubuntu 5.17.0-1004.5-starfive 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1004-starfive N/A linux-backports-modules-5.17.0-1004-starfive N/A linux-firmware20220711.gitdfa29317-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1004-starfive riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-starfive-5.17/+bug/1985067/+subscriptions -- Mailing list: https://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 1985067] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1985067/+attachment/5607876/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1985067 Title: kvm run failed Bad address Status in linux-starfive-5.17 package in Ubuntu: New Bug description: Running QEMU with linux-starfive-5.17 results in a crash: $ qemu-system-riscv64 -M virt -cpu host -accel kvm -m 4G -smp 4 -nographic -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/u-boot.bin -object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem -mem-prealloc -drive file=riscv64_2.img,format=raw,if=virtio -drive file=/mnt/cidata-riscv64-2.iso,format=raw,if=virtio,read-only=on -global driver=cfi.pflash01,property=secure,value=off -device virtio-net-pci,mac=00:00:00:00:01:01,netdev=eth0 -netdev user,id=eth0,hostfwd=tcp::8141-:22 -chardev socket,id=char1,server=on,path=/tmp/vsock2 -device virtio-net-pci,mac=00:00:00:00:01:02,netdev=eth1,mrg_rxbuf=off -netdev type=vhost-user,id=eth1,chardev=char1,vhostforce=on,queues=2 qemu-system-riscv64: -chardev socket,id=char1,server=on,path=/tmp/vsock2: info: QEMU waiting for connection on: disconnected:unix:/tmp/vsock2,server=on error: kvm run failed Bad address pc 80201738 mhartid mstatus 0002 mip mie mideleg medeleg mtvec mepc mcause mtval mscratch x0/zero x1/ra8000f38c x2/sp 801fee80 x3/gp x4/tp x5/t0801fee00 x6/t1 0001 x7/t2 x8/s0801fee90 x9/s1bf00 x10/a0 801fee90 x11/a1 x12/a2 0170 x13/a3 801ff000 x14/a4 0048 x15/a5 80201738 x16/a6 x17/a7 x18/s2 x19/s3 x20/s4 x21/s5 x22/s6 x23/s7 x24/s8 x25/s9 x26/s10 x27/s11 x28/t3 x29/t4 x30/t5 x31/t6 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 13:39 seq crw-rw 1 root audio 116, 33 Aug 11 13:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. Virtio network device +-02.0 Red Hat, Inc. Virtio network device +-03.0 Red Hat, Inc. Virtio block device \-04.0 Red Hat, Inc. Virtio block device Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: linux (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1004-starfive root=UUID=17bdec56-5406-45c4-9cfa-b72c62340cc7 ro default_hugepagesz=2M hugepagesz=2M hugepages=5120 ProcVersionSignature: Ubuntu 5.17.0-1004.5-starfive 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1004-starfive N/A linux-backports-modules-5.17.0-1004-starfive N/A linux-firmware20220711.gitdfa29317-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1004-starfive riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-starfive-5.17/+bug/1985067/+subscriptions -- Mailing list: https://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 1985067] Re: kvm run failed Bad address
apport information ** Tags added: apport-collected kinetic uec-images ** Description changed: Running QEMU with linux-starfive-5.17 results in a crash: $ qemu-system-riscv64 -M virt -cpu host -accel kvm -m 4G -smp 4 -nographic -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/u-boot.bin -object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem -mem-prealloc -drive file=riscv64_2.img,format=raw,if=virtio -drive file=/mnt/cidata-riscv64-2.iso,format=raw,if=virtio,read-only=on -global driver=cfi.pflash01,property=secure,value=off -device virtio-net-pci,mac=00:00:00:00:01:01,netdev=eth0 -netdev user,id=eth0,hostfwd=tcp::8141-:22 -chardev socket,id=char1,server=on,path=/tmp/vsock2 -device virtio-net-pci,mac=00:00:00:00:01:02,netdev=eth1,mrg_rxbuf=off -netdev type=vhost-user,id=eth1,chardev=char1,vhostforce=on,queues=2 qemu-system-riscv64: -chardev socket,id=char1,server=on,path=/tmp/vsock2: info: QEMU waiting for connection on: disconnected:unix:/tmp/vsock2,server=on error: kvm run failed Bad address pc 80201738 mhartid mstatus 0002 mip mie mideleg medeleg mtvec mepc mcause mtval mscratch x0/zero x1/ra8000f38c x2/sp 801fee80 x3/gp x4/tp x5/t0801fee00 x6/t1 0001 x7/t2 x8/s0801fee90 x9/s1bf00 x10/a0 801fee90 x11/a1 x12/a2 0170 x13/a3 801ff000 x14/a4 0048 x15/a5 80201738 x16/a6 x17/a7 x18/s2 x19/s3 x20/s4 x21/s5 x22/s6 x23/s7 x24/s8 x25/s9 x26/s10 x27/s11 x28/t3 x29/t4 x30/t5 x31/t6 + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Aug 11 13:39 seq + crw-rw 1 root audio 116, 33 Aug 11 13:39 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.22.0-0ubuntu4 + Architecture: riscv64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.10 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lspci-vt: + -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge + +-01.0 Red Hat, Inc. Virtio network device + +-02.0 Red Hat, Inc. Virtio network device + +-03.0 Red Hat, Inc. Virtio block device + \-04.0 Red Hat, Inc. Virtio block device + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Lsusb-t: + + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: + Package: linux (not installed) + PciMultimedia: + + ProcCpuinfoMinimal: + processor: 7 + hart : 7 + isa : rv64imafdcsuh + mmu : sv48 + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1004-starfive root=UUID=17bdec56-5406-45c4-9cfa-b72c62340cc7 ro default_hugepagesz=2M hugepagesz=2M hugepages=5120 + ProcVersionSignature: Ubuntu 5.17.0-1004.5-starfive 5.17.15 + RelatedPackageVersions: + linux-restricted-modules-5.17.0-1004-starfive N/A + linux-backports-modules-5.17.0-1004-starfive N/A + linux-firmware20220711.gitdfa29317-0ubuntu1 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: kinetic uec-images + Uname: Linux 5.17.0-1004-starfive riscv64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + acpidump: ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1985067/+attachment/5607875/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1985067 Title: kvm run failed Bad address Status in linux-starfive-5.17 package in Ubuntu: New Bug description: Running QEMU with linux-starfive-5.17 results in a crash: $ qemu-system-riscv64 -M virt -cpu host -accel kvm -m 4G -smp 4 -nographic -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/u-boot.bin -object memory-backend-file,id=mem,size=4096M,mem
[Kernel-packages] [Bug 1985067] [NEW] kvm run failed Bad address
Public bug reported: Running QEMU with linux-starfive-5.17 results in a crash: $ qemu-system-riscv64 -M virt -cpu host -accel kvm -m 4G -smp 4 -nographic -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/u-boot.bin -object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem -mem-prealloc -drive file=riscv64_2.img,format=raw,if=virtio -drive file=/mnt/cidata-riscv64-2.iso,format=raw,if=virtio,read-only=on -global driver=cfi.pflash01,property=secure,value=off -device virtio-net-pci,mac=00:00:00:00:01:01,netdev=eth0 -netdev user,id=eth0,hostfwd=tcp::8141-:22 -chardev socket,id=char1,server=on,path=/tmp/vsock2 -device virtio-net-pci,mac=00:00:00:00:01:02,netdev=eth1,mrg_rxbuf=off -netdev type=vhost-user,id=eth1,chardev=char1,vhostforce=on,queues=2 qemu-system-riscv64: -chardev socket,id=char1,server=on,path=/tmp/vsock2: info: QEMU waiting for connection on: disconnected:unix:/tmp/vsock2,server=on error: kvm run failed Bad address pc 80201738 mhartid mstatus 0002 mip mie mideleg medeleg mtvec mepc mcause mtval mscratch x0/zero x1/ra8000f38c x2/sp801fee80 x3/gp x4/tp x5/t0801fee00 x6/t10001 x7/t2 x8/s0801fee90 x9/s1bf00 x10/a0 801fee90 x11/a1 x12/a2 0170 x13/a3 801ff000 x14/a4 0048 x15/a5 80201738 x16/a6 x17/a7 x18/s2 x19/s3 x20/s4 x21/s5 x22/s6 x23/s7 x24/s8 x25/s9 x26/s10 x27/s11 x28/t3 x29/t4 x30/t5 x31/t6 ** Affects: linux-starfive-5.17 (Ubuntu) Importance: Undecided Status: New ** Tags: riscv64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1985067 Title: kvm run failed Bad address Status in linux-starfive-5.17 package in Ubuntu: New Bug description: Running QEMU with linux-starfive-5.17 results in a crash: $ qemu-system-riscv64 -M virt -cpu host -accel kvm -m 4G -smp 4 -nographic -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/u-boot.bin -object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem -mem-prealloc -drive file=riscv64_2.img,format=raw,if=virtio -drive file=/mnt/cidata-riscv64-2.iso,format=raw,if=virtio,read-only=on -global driver=cfi.pflash01,property=secure,value=off -device virtio-net-pci,mac=00:00:00:00:01:01,netdev=eth0 -netdev user,id=eth0,hostfwd=tcp::8141-:22 -chardev socket,id=char1,server=on,path=/tmp/vsock2 -device virtio-net-pci,mac=00:00:00:00:01:02,netdev=eth1,mrg_rxbuf=off -netdev type=vhost-user,id=eth1,chardev=char1,vhostforce=on,queues=2 qemu-system-riscv64: -chardev socket,id=char1,server=on,path=/tmp/vsock2: info: QEMU waiting for connection on: disconnected:unix:/tmp/vsock2,server=on error: kvm run failed Bad address pc 80201738 mhartid mstatus 0002 mip mie mideleg medeleg mtvec mepc mcause mtval mscratch x0/zero x1/ra8000f38c x2/sp 801fee80 x3/gp x4/tp x5/t0801fee00 x6/t1 0001 x7/t2 x8/s0801fee90 x9/s1bf00 x10/a0 801fee90 x11/a1 x12/a2 0170 x13/a3 801ff000 x14/a4 0048 x15/a5 80201738 x16/a6 x17/a7 x18/s2 x19/s3 x20/s4 x21/s5 x22/s6 x23/s7 x24/s8 x25/s9 x26/s10 x27/s11 x28/t3 x29/t4 x30/t5 x31/t6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-starfive-5.17/+bug/1985067/+subscri
[Kernel-packages] [Bug 1983474] Re: No HDMI output on Nezha board
The problem occurs for me for the 4k monitor described above. When I connect an FHD TV the output is correct. -- 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/1983474 Title: No HDMI output on Nezha board Status in linux-allwinner-5.17 package in Ubuntu: New Bug description: I followed the instructions in http://iso.qa.ubuntu.com/qatracker/milestones/437/builds/255006/testcases/1755/results The board does not provide HDMI output. Monitor: Samsung LU28R550UQRXEN (see appended EDID information) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.17.0-1003-allwinner. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Package: linux (not installed) PciMultimedia: ProcCpuinfo: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-allwinner root=LABEL=cloudimg-rootfs ro quiet splash ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-allwinner N/A linux-backports-modules-5.17.0-1003-allwinner N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: sunxi_cedrus Tags: jammy uec-images staging Uname: Linux 5.17.0-1003-allwinner riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1983474/+subscriptions -- Mailing list: https://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 1983474] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1983474/+attachment/5606713/+files/UdevDb.txt -- 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/1983474 Title: No HDMI output on Nezha board Status in linux-allwinner-5.17 package in Ubuntu: New Bug description: I followed the instructions in http://iso.qa.ubuntu.com/qatracker/milestones/437/builds/255006/testcases/1755/results The board does not provide HDMI output. Monitor: Samsung LU28R550UQRXEN (see appended EDID information) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.17.0-1003-allwinner. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Package: linux (not installed) PciMultimedia: ProcCpuinfo: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-allwinner root=LABEL=cloudimg-rootfs ro quiet splash ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-allwinner N/A linux-backports-modules-5.17.0-1003-allwinner N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: sunxi_cedrus Tags: jammy uec-images staging Uname: Linux 5.17.0-1003-allwinner riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1983474/+subscriptions -- Mailing list: https://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 1983474] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1983474/+attachment/5606714/+files/WifiSyslog.txt -- 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/1983474 Title: No HDMI output on Nezha board Status in linux-allwinner-5.17 package in Ubuntu: New Bug description: I followed the instructions in http://iso.qa.ubuntu.com/qatracker/milestones/437/builds/255006/testcases/1755/results The board does not provide HDMI output. Monitor: Samsung LU28R550UQRXEN (see appended EDID information) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.17.0-1003-allwinner. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Package: linux (not installed) PciMultimedia: ProcCpuinfo: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-allwinner root=LABEL=cloudimg-rootfs ro quiet splash ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-allwinner N/A linux-backports-modules-5.17.0-1003-allwinner N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: sunxi_cedrus Tags: jammy uec-images staging Uname: Linux 5.17.0-1003-allwinner riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1983474/+subscriptions -- Mailing list: https://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 1983474] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1983474/+attachment/5606712/+files/ProcModules.txt -- 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/1983474 Title: No HDMI output on Nezha board Status in linux-allwinner-5.17 package in Ubuntu: New Bug description: I followed the instructions in http://iso.qa.ubuntu.com/qatracker/milestones/437/builds/255006/testcases/1755/results The board does not provide HDMI output. Monitor: Samsung LU28R550UQRXEN (see appended EDID information) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.17.0-1003-allwinner. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Package: linux (not installed) PciMultimedia: ProcCpuinfo: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-allwinner root=LABEL=cloudimg-rootfs ro quiet splash ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-allwinner N/A linux-backports-modules-5.17.0-1003-allwinner N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: sunxi_cedrus Tags: jammy uec-images staging Uname: Linux 5.17.0-1003-allwinner riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1983474/+subscriptions -- Mailing list: https://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 1983474] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1983474/+attachment/5606708/+files/Lsusb.txt -- 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/1983474 Title: No HDMI output on Nezha board Status in linux-allwinner-5.17 package in Ubuntu: New Bug description: I followed the instructions in http://iso.qa.ubuntu.com/qatracker/milestones/437/builds/255006/testcases/1755/results The board does not provide HDMI output. Monitor: Samsung LU28R550UQRXEN (see appended EDID information) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.17.0-1003-allwinner. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Package: linux (not installed) PciMultimedia: ProcCpuinfo: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-allwinner root=LABEL=cloudimg-rootfs ro quiet splash ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-allwinner N/A linux-backports-modules-5.17.0-1003-allwinner N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: sunxi_cedrus Tags: jammy uec-images staging Uname: Linux 5.17.0-1003-allwinner riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1983474/+subscriptions -- Mailing list: https://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 1983474] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1983474/+attachment/5606709/+files/Lsusb-t.txt -- 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/1983474 Title: No HDMI output on Nezha board Status in linux-allwinner-5.17 package in Ubuntu: New Bug description: I followed the instructions in http://iso.qa.ubuntu.com/qatracker/milestones/437/builds/255006/testcases/1755/results The board does not provide HDMI output. Monitor: Samsung LU28R550UQRXEN (see appended EDID information) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.17.0-1003-allwinner. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Package: linux (not installed) PciMultimedia: ProcCpuinfo: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-allwinner root=LABEL=cloudimg-rootfs ro quiet splash ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-allwinner N/A linux-backports-modules-5.17.0-1003-allwinner N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: sunxi_cedrus Tags: jammy uec-images staging Uname: Linux 5.17.0-1003-allwinner riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1983474/+subscriptions -- Mailing list: https://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 1983474] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1983474/+attachment/5606711/+files/ProcInterrupts.txt -- 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/1983474 Title: No HDMI output on Nezha board Status in linux-allwinner-5.17 package in Ubuntu: New Bug description: I followed the instructions in http://iso.qa.ubuntu.com/qatracker/milestones/437/builds/255006/testcases/1755/results The board does not provide HDMI output. Monitor: Samsung LU28R550UQRXEN (see appended EDID information) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.17.0-1003-allwinner. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Package: linux (not installed) PciMultimedia: ProcCpuinfo: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-allwinner root=LABEL=cloudimg-rootfs ro quiet splash ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-allwinner N/A linux-backports-modules-5.17.0-1003-allwinner N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: sunxi_cedrus Tags: jammy uec-images staging Uname: Linux 5.17.0-1003-allwinner riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1983474/+subscriptions -- Mailing list: https://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 1983474] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1983474/+attachment/5606710/+files/Lsusb-v.txt -- 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/1983474 Title: No HDMI output on Nezha board Status in linux-allwinner-5.17 package in Ubuntu: New Bug description: I followed the instructions in http://iso.qa.ubuntu.com/qatracker/milestones/437/builds/255006/testcases/1755/results The board does not provide HDMI output. Monitor: Samsung LU28R550UQRXEN (see appended EDID information) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.17.0-1003-allwinner. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Package: linux (not installed) PciMultimedia: ProcCpuinfo: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-allwinner root=LABEL=cloudimg-rootfs ro quiet splash ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-allwinner N/A linux-backports-modules-5.17.0-1003-allwinner N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: sunxi_cedrus Tags: jammy uec-images staging Uname: Linux 5.17.0-1003-allwinner riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1983474/+subscriptions -- Mailing list: https://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 1983474] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1983474/+attachment/5606707/+files/CurrentDmesg.txt -- 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/1983474 Title: No HDMI output on Nezha board Status in linux-allwinner-5.17 package in Ubuntu: New Bug description: I followed the instructions in http://iso.qa.ubuntu.com/qatracker/milestones/437/builds/255006/testcases/1755/results The board does not provide HDMI output. Monitor: Samsung LU28R550UQRXEN (see appended EDID information) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.17.0-1003-allwinner. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Package: linux (not installed) PciMultimedia: ProcCpuinfo: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-allwinner root=LABEL=cloudimg-rootfs ro quiet splash ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-allwinner N/A linux-backports-modules-5.17.0-1003-allwinner N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: sunxi_cedrus Tags: jammy uec-images staging Uname: Linux 5.17.0-1003-allwinner riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1983474/+subscriptions -- Mailing list: https://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 1983474] AlsaDevices.txt
apport information ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1983474/+attachment/5606706/+files/AlsaDevices.txt -- 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/1983474 Title: No HDMI output on Nezha board Status in linux-allwinner-5.17 package in Ubuntu: New Bug description: I followed the instructions in http://iso.qa.ubuntu.com/qatracker/milestones/437/builds/255006/testcases/1755/results The board does not provide HDMI output. Monitor: Samsung LU28R550UQRXEN (see appended EDID information) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.17.0-1003-allwinner. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Package: linux (not installed) PciMultimedia: ProcCpuinfo: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-allwinner root=LABEL=cloudimg-rootfs ro quiet splash ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-allwinner N/A linux-backports-modules-5.17.0-1003-allwinner N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: sunxi_cedrus Tags: jammy uec-images staging Uname: Linux 5.17.0-1003-allwinner riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1983474/+subscriptions -- Mailing list: https://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 1983474] [NEW] No HDMI output on Nezha board
Public bug reported: I followed the instructions in http://iso.qa.ubuntu.com/qatracker/milestones/437/builds/255006/testcases/1755/results The board does not provide HDMI output. Monitor: Samsung LU28R550UQRXEN (see appended EDID information) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.17.0-1003-allwinner. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Package: linux (not installed) PciMultimedia: ProcCpuinfo: processor : 0 hart : 0 isa: rv64imafdc mmu: sv39 uarch : thead,c906 ProcCpuinfoMinimal: processor : 0 hart : 0 isa: rv64imafdc mmu: sv39 uarch : thead,c906 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-allwinner root=LABEL=cloudimg-rootfs ro quiet splash ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-allwinner N/A linux-backports-modules-5.17.0-1003-allwinner N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: sunxi_cedrus Tags: jammy uec-images staging Uname: Linux 5.17.0-1003-allwinner riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: ** Affects: linux-allwinner-5.17 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected iso-testing jammy riscv64 staging uec-images ** Attachment added: "edit.txt" https://bugs.launchpad.net/bugs/1983474/+attachment/5606705/+files/edit.txt ** Tags added: iso-testing riscv64 ** Tags added: apport-collected jammy staging uec-images ** Description changed: I followed the instructions in http://iso.qa.ubuntu.com/qatracker/milestones/437/builds/255006/testcases/1755/results The board does not provide HDMI output. Monitor: Samsung LU28R550UQRXEN (see appended EDID information) + --- + ProblemType: Bug + AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.17.0-1003-allwinner. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: riscv64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' + Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lspci: + + Lspci-vt: -[:00]- + Package: linux (not installed) + PciMultimedia: + + ProcCpuinfo: + processor: 0 + hart : 0 + isa : rv64imafdc + mmu : sv39 + uarch: thead,c906 + ProcCpuinfoMinimal: + processor: 0 + hart : 0 + isa : rv64imafdc + mmu : sv39 + uarch: thead,c906 + ProcEnviron: + TERM=vt220 + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-allwinner root=LABEL=cloudimg-rootfs ro quiet splash + ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15 + RelatedPackageVersions: + linux-restricted-modules-5.17.0-1003-allwinner N/A + linux-backports-modules-5.17.0-1003-allwinner N/A + linux-firmware 20220329.git681281e4-0ubuntu3.3 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + StagingDrivers: sunxi_cedrus + Tags: jammy uec-images staging + Uname: Linux 5.17.0-1003-allwinner riscv64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + acpidump: -- 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/1983474 Title: No HDMI output on Nezha board Status in linux-allwinner-5.17 package in Ubuntu
[Kernel-packages] [Bug 1980594] Re: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM
The patch be82abe6a76b ("RISC-V: KVM: Fix SRCU deadlock caused by
kvm_riscv_check_vcpu_requests()") is contained in Linux v5.19-rc7.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-starfive-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1980594
Title:
/usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM
Status in linux package in Ubuntu:
Confirmed
Status in linux-starfive-5.17 package in Ubuntu:
Confirmed
Bug description:
QEMU 7.0 supports KVM on RISC-V.
Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf.
That binary cannot be used to boot via qemu-system-riscv64 -kvm.
File u-boot produced by qemu-riscv64_smode_defconfig with
CONFIG_MTD_NOR_FLASH=n
CONFIG_CMD_NET=n
can be used to start U-Boot with qemu-system-riscv64 -kvm. But any
virtio access leads to a crash leaving QEMU unresponsive.
Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jul 10 19:58 seq
crw-rw 1 root audio 116, 33 Jul 10 19:58 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.22.0-0ubuntu4
Architecture: riscv64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
DistroRelease: Ubuntu 22.10
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci-vt:
-[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge
+-01.0 Red Hat, Inc. QEMU XHCI Host Controller
+-02.0 Red Hat, Inc. Virtio block device
\-03.0 Red Hat, Inc. Virtio block device
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
Package: linux-starfive-5.17 (not installed)
PciMultimedia:
ProcCpuinfoMinimal:
processor: 7
hart : 7
isa : rv64imafdcsuh
mmu : sv48
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive
root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M
hugepagesz=2M hugepages=2048 earlycon efi=debug
ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9
RelatedPackageVersions:
linux-restricted-modules-5.17.0-1003-starfive N/A
linux-backports-modules-5.17.0-1003-starfive N/A
linux-firmware20220621.git7b71b75b-0ubuntu1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: kinetic uec-images
Uname: Linux 5.17.0-1003-starfive riscv64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: False
acpidump:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions
--
Mailing list: https://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 1980594] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602245/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://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 1980594] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602246/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux-starfive-5.17 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://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 1980594] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602242/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://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 1980594] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602243/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://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 1980594] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602244/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://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 1980594] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602241/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://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 1980594] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602240/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://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 1980594] Re: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM
apport information ** Tags added: apport-collected kinetic uec-images ** Description changed: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jul 10 19:58 seq + crw-rw 1 root audio 116, 33 Jul 10 19:58 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.22.0-0ubuntu4 + Architecture: riscv64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.10 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lspci-vt: + -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge + +-01.0 Red Hat, Inc. QEMU XHCI Host Controller + +-02.0 Red Hat, Inc. Virtio block device + \-03.0 Red Hat, Inc. Virtio block device + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Lsusb-t: + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M + Package: linux-starfive-5.17 (not installed) + PciMultimedia: + + ProcCpuinfoMinimal: + processor: 7 + hart : 7 + isa : rv64imafdcsuh + mmu : sv48 + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug + ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 + RelatedPackageVersions: + linux-restricted-modules-5.17.0-1003-starfive N/A + linux-backports-modules-5.17.0-1003-starfive N/A + linux-firmware20220621.git7b71b75b-0ubuntu1 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: kinetic uec-images + Uname: Linux 5.17.0-1003-starfive riscv64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: False + acpidump: ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602239/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: De
[Kernel-packages] [Bug 1980594] Re: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM
** Package changed: u-boot (Ubuntu) => linux (Ubuntu) ** Also affects: linux-starfive-5.17 (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/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: New Status in linux-starfive-5.17 package in Ubuntu: New Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://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 1967889] Re: Raise CONFIG_NR_CPUS
The following patch sets reasonable values for CONFIG_NR_CPUS on RISC-V: [PATCH v3] RISC-V: Increase range and default value of NR_CPUS https://lore.kernel.org/all/20220420112408.155561-1-apa...@ventanamicro.com/ -- 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/1967889 Title: Raise CONFIG_NR_CPUS Status in linux-riscv package in Ubuntu: New Bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967889/+subscriptions -- Mailing list: https://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 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
As we are close to release date we should simply disable Load File2 protocol on ARM in Jammy: https://code.launchpad.net/~xypron/grub/+git/grub/+merge/419407 -- 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/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade Status in grub2 package in Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+subscriptions -- Mailing list: https://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 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
As long as the kernel stub does not invoke the SNP protocol itself it is safe for GRUB to assume that it is still in a good state when reaching the Load File2 protocol call. I am not aware of any requirement in the UEFI specification to leave the network adapter in a specific state on ExitBootServices(). -- 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/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade Status in grub2 package in Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+subscriptions -- Mailing list: https://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 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
As the log below shows grub_net_fini_hw() is called before entering the kernel and before the LoadFile2 protocol is executed: loader/efi/linux.c:478: kernel @ 0xf63d8000 net/net.c:1559: fs_close() name: /casper/vmlinuz net/net.c:1510: fs_open() name: /casper/initrd loader/efi/linux.c:396: LoadFile2 initrd loading protocol installed net/net.c:1819: grub_net_fini_hw() net/drivers/efi/efinet.c:232: efi_net close_card loader/efi/linux.c:141: Installed/updated FDT configuration table @ 0x0 loader/efi/linux.c:191: linux command line: 'BOOT_IMAGE=/casper/vmlinuz efi=debug earlyprintk url=https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/jammy-live-serv er-arm64.iso' loader/efi/peimage.c:215: PE-COFF header checked loader/efi/peimage.c:282: sections loaded loader/efi/peimage.c:493: no relocations loader/efi/peimage.c:709: Executing image loaded at 0xf364 Entry point 0xf55473c8 Size 0x02d9 EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: Generating empty DTB loader/efi/linux.c:348: Providing initrd via LOAD_FILE2_PROTOCOL net/net.c:1685: fs_read_real() name: /casper/initrd net/drivers/efi/efinet.c:169: efi_net open_card net/drivers/efi/efinet.c:75: Timeout: limit_time 50680, new_time 50681 error: couldn't send network packet. -- 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/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade Status in grub2 package in Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+subscriptions -- Mailing list: https://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 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
On riscv64 we cannot boot without the LoadFile2 protocol. So the short term fix of forcing to 0 must be architecture specific. Check for __riscv not defined. -- 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/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade Status in grub2 package in Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in grub2-unsigned package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+subscriptions -- Mailing list: https://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 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
** Tags added: fr-2245 -- 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/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade Status in grub2 package in Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in grub2-unsigned package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+subscriptions -- Mailing list: https://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 1967889] [NEW] Raise CONFIG_NR_CPUS
Public bug reported: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich ** 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/1967889 Title: Raise CONFIG_NR_CPUS Status in linux-riscv package in Ubuntu: New Bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967889/+subscriptions -- Mailing list: https://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 1967130] Re: rcu_sched detected stalls on CPUs/tasks
efi: Make efi_rts_work accessible to efi page fault handler https://lore.kernel.org/all/20200318090253.ga32...@duo.ucw.cz/T/#mcbd236122ec0ae61f1ee9c22b8d7910ffc2276a0 addressed a similar issue on x86. -- 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/1967130 Title: rcu_sched detected stalls on CPUs/tasks Status in linux-riscv package in Ubuntu: New Bug description: When running the riscv64 live installer (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy- live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly see rcu_sched stalls related to accessing the UEFI runtime: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu: 3-...0: (3 GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, t=15002 jiffies, g=155853, q=1286) Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1 state:R running task stack:0 pid: 3715 ppid: 2 flags:0x0008 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq efi_call_rts Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] __schedule+0x226/0x644 uname -a: Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 2022 riscv64 riscv64 riscv64 GNU/Linux --- ProblemType: Bug Architecture: riscv64 DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.1004.4 PackageArchitecture: riscv64 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 Uname: Linux 5.15.0-1004-generic riscv64 UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+subscriptions -- Mailing list: https://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 1967130] Re: rcu_sched detected stalls on CPUs/tasks
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+attachment/5574773/+files/dmesg -- 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/1967130 Title: rcu_sched detected stalls on CPUs/tasks Status in linux-riscv package in Ubuntu: New Bug description: When running the riscv64 live installer (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy- live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly see rcu_sched stalls related to accessing the UEFI runtime: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu: 3-...0: (3 GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, t=15002 jiffies, g=155853, q=1286) Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1 state:R running task stack:0 pid: 3715 ppid: 2 flags:0x0008 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq efi_call_rts Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] __schedule+0x226/0x644 uname -a: Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 2022 riscv64 riscv64 riscv64 GNU/Linux --- ProblemType: Bug Architecture: riscv64 DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.1004.4 PackageArchitecture: riscv64 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 Uname: Linux 5.15.0-1004-generic riscv64 UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+subscriptions -- Mailing list: https://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 1967130] Re: rcu_sched detected stalls on CPUs/tasks
apport information ** Tags added: apport-collected ** Description changed: When running the riscv64 live installer (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy- live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly see rcu_sched stalls related to accessing the UEFI runtime: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu: 3-...0: (3 GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, t=15002 jiffies, g=155853, q=1286) Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1 state:R running task stack:0 pid: 3715 ppid: 2 flags:0x0008 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq efi_call_rts Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] __schedule+0x226/0x644 uname -a: Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 2022 riscv64 riscv64 riscv64 GNU/Linux + --- + ProblemType: Bug + Architecture: riscv64 + DistroRelease: Ubuntu 22.04 + Package: linux-image-generic 5.15.0.1004.4 + PackageArchitecture: riscv64 + ProcEnviron: + TERM=vt220 + PATH=(custom, no user) + LANG=C.UTF-8 + Uname: Linux 5.15.0-1004-generic riscv64 + UserGroups: N/A + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1967130/+attachment/5574772/+files/Dependencies.txt -- 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/1967130 Title: rcu_sched detected stalls on CPUs/tasks Status in linux-riscv package in Ubuntu: New Bug description: When running the riscv64 live installer (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy- live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly see rcu_sched stalls related to accessing the UEFI runtime: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu: 3-...0: (3 GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, t=15002 jiffies, g=155853, q=1286) Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1 state:R running task stack:0 pid: 3715 ppid: 2 flags:0x0008 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq efi_call_rts Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] __schedule+0x226/0x644 uname -a: Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 2022 riscv64 riscv64 riscv64 GNU/Linux --- ProblemType: Bug Architecture: riscv64 DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.1004.4 PackageArchitecture: riscv64 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 Uname: Linux 5.15.0-1004-generic riscv64 UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+subscriptions -- Mailing list: https://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 1967130] [NEW] rcu_sched detected stalls on CPUs/tasks
Public bug reported: When running the riscv64 live installer (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy- live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly see rcu_sched stalls related to accessing the UEFI runtime: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu: 3-...0: (3 GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, t=15002 jiffies, g=155853, q=1286) Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1 state:R running task stack:0 pid: 3715 ppid: 2 flags:0x0008 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq efi_call_rts Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] __schedule+0x226/0x644 uname -a: Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 2022 riscv64 riscv64 riscv64 GNU/Linux --- ProblemType: Bug Architecture: riscv64 DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.1004.4 PackageArchitecture: riscv64 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 Uname: Linux 5.15.0-1004-generic riscv64 UserGroups: N/A _MarkForUpload: True ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected jammy riscv64 ** Attachment added: "kern.log" https://bugs.launchpad.net/bugs/1967130/+attachment/5574771/+files/kern.log -- 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/1967130 Title: rcu_sched detected stalls on CPUs/tasks Status in linux-riscv package in Ubuntu: New Bug description: When running the riscv64 live installer (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy- live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly see rcu_sched stalls related to accessing the UEFI runtime: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu: 3-...0: (3 GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, t=15002 jiffies, g=155853, q=1286) Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1 state:R running task stack:0 pid: 3715 ppid: 2 flags:0x0008 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq efi_call_rts Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] __schedule+0x226/0x644 uname -a: Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 2022 riscv64 riscv64 riscv64 GNU/Linux --- ProblemType: Bug Architecture: riscv64 DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.1004.4 PackageArchitecture: riscv64 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 Uname: Linux 5.15.0-1004-generic riscv64 UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+subscriptions -- Mailing list: https://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 1966978] [NEW] microchip/microchip-mpfs-icicle-kit.dtb missing
Public bug reported: Please, add microchip/microchip-mpfs-icicle-kit.dtb to the list of created device-trees. ** 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/1966978 Title: microchip/microchip-mpfs-icicle-kit.dtb missing Status in linux-riscv package in Ubuntu: New Bug description: Please, add microchip/microchip-mpfs-icicle-kit.dtb to the list of created device-trees. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1966978/+subscriptions -- Mailing list: https://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 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Also makes some systems unbootable if they display prompts
Works with nvidia 510 driver. So I set the issue to fixed release for this. Is there anybody using the 470 driver who could confirm it works there too? ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964305 Title: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Also makes some systems unbootable if they display prompts Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Bug description: Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Steps to reproduce: 1. Boot Ubuntu. 2. Press Ctrl+Alt+F4. Expected: VT to be displayed Observed: Monitor turns off. Notes: * This failure only happens in 5.15.0-22-generic. Kernel version 5.15.0-18-generic works fine. * I am currently using the nvidia-470 driver in case that's relevant. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Mar 9 14:33:12 2022 InstallationDate: Installed on 2021-11-05 (123 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305/+subscriptions -- Mailing list: https://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 1964335] Re: Excessive size of kernel modules on RISC-V - modules unstripped
Cf. "Why is .symtab so huge on riscv?" #1036 (https://github.com/riscv- collab/riscv-gnu-toolchain/issues/1036) -- 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/1964335 Title: Excessive size of kernel modules on RISC-V - modules unstripped Status in linux-riscv package in Ubuntu: In Progress Bug description: The size of kernel modules on RISC-V indicates that there is a build problem: kernel/drivers/ata/sata_mv.ko amd64: 81713 bytes arm64: 85505 bytes riscv64: 601417 bytes objdump -h shows that there is no section beyond 0xc6fc in the riscv64 file. The size of the sections matches what we see on the other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964335/+subscriptions -- Mailing list: https://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 1964335] Re: Excessive size of kernel modules on RISC-V - modules unstripped
Cf. [PATCH] UBUNTU: SAUCE: scripts/Makefile.modinst discard-locals from modules (https://lists.ubuntu.com/archives/kernel-team/2022-March/128534.html) ** Bug watch added: github.com/riscv-collab/riscv-gnu-toolchain/issues #1036 https://github.com/riscv-collab/riscv-gnu-toolchain/issues/1036 -- 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/1964335 Title: Excessive size of kernel modules on RISC-V - modules unstripped Status in linux-riscv package in Ubuntu: In Progress Bug description: The size of kernel modules on RISC-V indicates that there is a build problem: kernel/drivers/ata/sata_mv.ko amd64: 81713 bytes arm64: 85505 bytes riscv64: 601417 bytes objdump -h shows that there is no section beyond 0xc6fc in the riscv64 file. The size of the sections matches what we see on the other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964335/+subscriptions -- Mailing list: https://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 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
A different file was reported for me: Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to install new version of '/lib/firmware/ath11k/WCN6855/hw2.1/amss.bin': No such file or directory No apport report written because the error message indicates an issue on the local system $ ls /lib/firmware/ath11k/WCN6855/ -la total 12 drwxr-xr-x 3 root root 4096 Feb 18 17:28 . drwxr-xr-x 6 root root 4096 Jan 11 13:31 .. drwxr-xr-x 3 root root 4096 Mar 15 08:58 hw2.0 lrwxrwxrwx 1 root root5 Feb 17 08:51 hw2.1 -> hw2.0 The problem could be resolved locally via sudo rm /lib/firmware/ath11k/WCN6855 -rf After upgrading the symbolic link is gone: $ ls /lib/firmware/ath11k/WCN6855 -la total 16 drwxr-xr-x 4 root root 4096 Mar 15 09:00 . drwxr-xr-x 6 root root 4096 Mar 15 09:00 .. drwxr-xr-x 2 root root 4096 Mar 15 09:00 hw2.0 drwxr-xr-x 2 root root 4096 Mar 15 09:00 hw2.1 -- 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/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Confirmed Bug description: linux-firmware fails to upgrade with: unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg- new': No such file or directory $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: linux-firmware 1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/238 MB of archives. After this operation, 24.9 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 272091 files and directories currently installed.) Preparing to unpack .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-23-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Errors were encountered while processing: /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- Mailing list: https://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 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works)
The problem is reproducible with Nvidia driver 510.54, too. ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964305 Title: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Steps to reproduce: 1. Boot Ubuntu. 2. Press Ctrl+Alt+F4. Expected: VT to be displayed Observed: Monitor turns off. Notes: * This failure only happens in 5.15.0-22-generic. Kernel version 5.15.0-18-generic works fine. * I am currently using the nvidia-470 driver in case that's relevant. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Mar 9 14:33:12 2022 InstallationDate: Installed on 2021-11-05 (123 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305/+subscriptions -- Mailing list: https://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 1964384] Re: linux-image-5.15.0-22-generic does not boot
This seems to be a related bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305 [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic 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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works)
Is this related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384, no kernel log displayed while booting, no possibility to enter decryption password? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964305 Title: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Steps to reproduce: 1. Boot Ubuntu. 2. Press Ctrl+Alt+F4. Expected: VT to be displayed Observed: Monitor turns off. Notes: * This failure only happens in 5.15.0-22-generic. Kernel version 5.15.0-18-generic works fine. * I am currently using the nvidia-470 driver in case that's relevant. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Mar 9 14:33:12 2022 InstallationDate: Installed on 2021-11-05 (123 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305/+subscriptions -- Mailing list: https://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 1964384] Re: linux-image-5.15.0-22-generic does not boot
** Attachment added: "dmesg for 5.15.0-22-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+attachment/5567644/+files/dmesg.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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] Re: linux-image-5.15.0-22-generic does not boot
While nothing is shown on the display Linux seems still be waiting for keyboard input of the description key. If I type it in the system boots and sddm is the first thing displayed. The question remains why the KDE input mask for the encryption mask is not displayed and pressing the ESC key does not show the terminal style input. -- 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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567503/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567501/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567504/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567498/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567492/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567496/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567499/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567493/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567500/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567502/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567495/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567494/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567497/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567489/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567490/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567491/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567487/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567488/+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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567486/+files/AudioDevicesInUse.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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] Re: linux-image-5.15.0-22-generic does not boot
apport information ** Tags added: apport-collected jammy ** Description changed: linux-image-5.15.0-22-generic has been installed on my computer via apt- get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu78 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: KDE + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-05-26 (287 days ago) + InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) + MachineType: System manufacturer System Product Name + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash + ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-18-generic N/A + linux-backports-modules-5.15.0-18-generic N/A + linux-firmware 20220302.gitee0667aa-0ubuntu1 + RfKill: + + Tags: jammy + Uname: Linux 5.15.0-18-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo + _MarkForUpload: True + dmi.bios.date: 08/09/2021 + dmi.bios.release: 5.17 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 4021 + dmi.board.asset.tag: Default string + dmi.board.name: PRIME X570-PRO + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev X.0x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: System Product Name + dmi.product.sku: SKU + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1964384/+attachment/5567485/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Confirmed Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-26 (287 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm apt-cacher-ng cdrom dialout dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing lis
[Kernel-packages] [Bug 1964384] Re: linux-image-5.15.0-22-generic does not boot
** Attachment added: "Boot log for Linux version 5.15.0-18-generic (buildd@lcy02-amd64-041) that boots fine." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+attachment/5567440/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Incomplete Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964384] [NEW] linux-image-5.15.0-22-generic does not boot
Public bug reported: linux-image-5.15.0-22-generic has been installed on my computer via apt- get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "/usr/share/apport/dump_acpi_tables.py > acpi.dump" https://bugs.launchpad.net/bugs/1964384/+attachment/5567438/+files/acpi.dump -- 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/1964384 Title: linux-image-5.15.0-22-generic does not boot Status in linux package in Ubuntu: Incomplete Bug description: linux-image-5.15.0-22-generic has been installed on my computer via apt-get update today. It stops booting after a message "EFI stub: UEFI Secure Boot is enabled" The system boots fine with linux-image-5.15.0-18-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964384/+subscriptions -- Mailing list: https://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 1964335] Re: Excessive size of kernel modules on RISC-V - modules unstripped
** Changed in: linux-riscv (Ubuntu) Status: New => Confirmed -- 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/1964335 Title: Excessive size of kernel modules on RISC-V - modules unstripped Status in linux-riscv package in Ubuntu: Confirmed Bug description: The size of kernel modules on RISC-V indicates that there is a build problem: kernel/drivers/ata/sata_mv.ko amd64: 81713 bytes arm64: 85505 bytes riscv64: 601417 bytes objdump -h shows that there is no section beyond 0xc6fc in the riscv64 file. The size of the sections matches what we see on the other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964335/+subscriptions -- Mailing list: https://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 1964335] Re: Excessive size of kernel modules on RISC-V - modules unstripped
If I compile Linux v5.15.26 with RISC-V defconfig + CONFIG_SATA_MV=y, I get a drivers/ata/sata_mv.ko with 103960 bytes. With additionally CONFIG_MODULE_SIG=y after make modules_install: 104673 bytes. So the problems seems not to exist in upstream. -- 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/1964335 Title: Excessive size of kernel modules on RISC-V - modules unstripped Status in linux-riscv package in Ubuntu: New Bug description: The size of kernel modules on RISC-V indicates that there is a build problem: kernel/drivers/ata/sata_mv.ko amd64: 81713 bytes arm64: 85505 bytes riscv64: 601417 bytes objdump -h shows that there is no section beyond 0xc6fc in the riscv64 file. The size of the sections matches what we see on the other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964335/+subscriptions -- Mailing list: https://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 1964335] [NEW] Excessive size of kernel modules on RISC-V
Public bug reported: The size of kernel modules on RISC-V indicates that there is a build problem: kernel/drivers/ata/sata_mv.ko amd64: 81713 bytes arm64: 85505 bytes riscv64: 601417 bytes objdump -h shows that there is no section beyond 0xc6fc in the riscv64 file. The size of the sections matches what we see on the other architectures. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Tags: riscv64 -- 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/1964335 Title: Excessive size of kernel modules on RISC-V Status in linux-riscv package in Ubuntu: New Bug description: The size of kernel modules on RISC-V indicates that there is a build problem: kernel/drivers/ata/sata_mv.ko amd64: 81713 bytes arm64: 85505 bytes riscv64: 601417 bytes objdump -h shows that there is no section beyond 0xc6fc in the riscv64 file. The size of the sections matches what we see on the other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964335/+subscriptions -- Mailing list: https://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 1958374] Re: riscv: Improve support for the SiFive Unmatched board
** Summary changed:
- riscv: Improve support for the SiFive Unmathed board
+ riscv: Improve support for the SiFive Unmatched board
--
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/1958374
Title:
riscv: Improve support for the SiFive Unmatched board
Status in linux-riscv package in Ubuntu:
New
Bug description:
The following patches should be considered for inclusion into the
v5.15 linux-image-generic kernel for the Jammy release:
commit f6f7fbb89bf8dc9132fde55cfe67483138eea880
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:42 2021 +
riscv: dts: sifive unmatched: Link the tmp451 with its power supply
Fixes the following probe warning:
lm90 0-004c: Looking up vcc-supply from device tree
lm90 0-004c: Looking up vcc-supply property in node
/soc/i2c@1003/temperature-sensor@4c failed
lm90 0-004c: supply vcc not found, using dummy regulator
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit ad931d9b3b2e21586de8e6b34346d0a30c13721d
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:41 2021 +
riscv: dts: sifive unmatched: Fix regulator for board rev3
The existing values are rejected by the da9063 regulator driver, as they
are unachievable with the declared chip setup (non-merged vcore and bmem
are unable to provide the declared curent).
Fix voltages to match rev3 schematics, which also matches their boot-up
configuration within the chip's available precision.
Declare bcore1/bcore2 and bmem/bio as merged.
Set ldo09 and ldo10 as always-on as their consumers are not declared but
exist.
Drop ldo current limits as there is no current limit feature for these
regulators in the DA9063. Fixes warnings like:
DA9063_LDO3: Operation of current configuration missing
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit cd29cc8ad2540a4f9a0a3e174394d39e648ef941
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:39 2021 +
riscv: dts: sifive unmatched: Expose the PMIC sub-functions
These sub-functions are available in the chip revision on this board, so
expose them.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit 8120393b74b31bbaf293f59896de6b0d50febc48
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:38 2021 +
riscv: dts: sifive unmatched: Expose the board ID eeprom
Mark it as read-only as it is factory-programmed with identifying
information, and no executable nor configuration:
- eth MAC address
- board model (PCB version, BoM version)
- board serial number
Accidental modification would cause misidentification which could brick
the board, so marking read-only seem like both a safe and non-constraining
choice.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit ea81b91e4e256b0bb75d47ad3a5c230b2171a005
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:37 2021 +
riscv: dts: sifive unmatched: Name gpio lines
Follow the pin descriptions given in the version 3 of the board
schematics.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit 298d03c2d7f1b5daacb6d4f4053fd3d677d67087
Author: Bin Meng
Date: Wed Jun 16 15:46:45 2021 +0800
riscv: dts: unmatched: Add gpio card detect to mmc-spi-slot
Per HiFive Unmatched schematics, the card detect signal of the
micro SD card is connected to gpio pin #15, which should be
reflected in the DT via the property, as described in
Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt.
[1]
https://sifive.cdn.prismic.io/sifive/6a06d6c0-6e66-49b5-8e9e-e68ce76f4192_hifive-unmatched-schematics-v3.pdf
Signed-off-by: Bin Meng
Fixes: d573b5558abb ("riscv: dts: add initial board data for the SiFive
HiFive Unmatched")
Cc: sta...@vger.kernel.org
Signed-off-by: Palmer Dabbelt
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1958374/+subscriptions
--
Mailing list: https://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 1958374] [NEW] riscv: Improve support for the SiFive Unmathed board
Public bug reported:
The following patches should be considered for inclusion into the v5.15
linux-image-generic kernel for the Jammy release:
commit f6f7fbb89bf8dc9132fde55cfe67483138eea880
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:42 2021 +
riscv: dts: sifive unmatched: Link the tmp451 with its power supply
Fixes the following probe warning:
lm90 0-004c: Looking up vcc-supply from device tree
lm90 0-004c: Looking up vcc-supply property in node
/soc/i2c@1003/temperature-sensor@4c failed
lm90 0-004c: supply vcc not found, using dummy regulator
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit ad931d9b3b2e21586de8e6b34346d0a30c13721d
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:41 2021 +
riscv: dts: sifive unmatched: Fix regulator for board rev3
The existing values are rejected by the da9063 regulator driver, as they
are unachievable with the declared chip setup (non-merged vcore and bmem
are unable to provide the declared curent).
Fix voltages to match rev3 schematics, which also matches their boot-up
configuration within the chip's available precision.
Declare bcore1/bcore2 and bmem/bio as merged.
Set ldo09 and ldo10 as always-on as their consumers are not declared but
exist.
Drop ldo current limits as there is no current limit feature for these
regulators in the DA9063. Fixes warnings like:
DA9063_LDO3: Operation of current configuration missing
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit cd29cc8ad2540a4f9a0a3e174394d39e648ef941
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:39 2021 +
riscv: dts: sifive unmatched: Expose the PMIC sub-functions
These sub-functions are available in the chip revision on this board, so
expose them.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit 8120393b74b31bbaf293f59896de6b0d50febc48
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:38 2021 +
riscv: dts: sifive unmatched: Expose the board ID eeprom
Mark it as read-only as it is factory-programmed with identifying
information, and no executable nor configuration:
- eth MAC address
- board model (PCB version, BoM version)
- board serial number
Accidental modification would cause misidentification which could brick
the board, so marking read-only seem like both a safe and non-constraining
choice.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit ea81b91e4e256b0bb75d47ad3a5c230b2171a005
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:37 2021 +
riscv: dts: sifive unmatched: Name gpio lines
Follow the pin descriptions given in the version 3 of the board schematics.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit 298d03c2d7f1b5daacb6d4f4053fd3d677d67087
Author: Bin Meng
Date: Wed Jun 16 15:46:45 2021 +0800
riscv: dts: unmatched: Add gpio card detect to mmc-spi-slot
Per HiFive Unmatched schematics, the card detect signal of the
micro SD card is connected to gpio pin #15, which should be
reflected in the DT via the property, as described in
Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt.
[1]
https://sifive.cdn.prismic.io/sifive/6a06d6c0-6e66-49b5-8e9e-e68ce76f4192_hifive-unmatched-schematics-v3.pdf
Signed-off-by: Bin Meng
Fixes: d573b5558abb ("riscv: dts: add initial board data for the SiFive
HiFive Unmatched")
Cc: sta...@vger.kernel.org
Signed-off-by: Palmer Dabbelt
** Affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
** Tags: riscv64
** Package changed: linux-meta (Ubuntu) => linux-riscv (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1958374
Title:
riscv: Improve support for the SiFive Unmathed board
Status in linux-riscv package in Ubuntu:
New
Bug description:
The following patches should be considered for inclusion into the
v5.15 linux-image-generic kernel for the Jammy release:
commit f6f7fbb89bf8dc9132fde55cfe67483138eea880
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:42 2021 +
riscv: dts: sifive unmatched: Link the tmp451 with its power supply
Fixes the following probe warning:
lm90 0-004c: Looking up vcc-supply from device tree
lm90 0-004c: Looking up vcc-supply property in node
/soc/i2c@1003/temperature-sensor@4c failed
lm90 0-004c: supply vcc not found, using dummy regulator
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit ad931d9b3b2e21586de8e6b34346d0a30c13721d
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:41 2021 +
riscv: dts: sifive unmatched: Fix r
[Kernel-packages] [Bug 1861053] Re: fatrace doesn't trace on zfs filesystems
$ https://github.com/openzfs/zfs
$ cd zfs/
$ git grep -n fsnotify
shows that notification was never implemented.
So this works as designed. Closing as "invalid".
Best regards
Heinrich
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: fatrace (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861053
Title:
fatrace doesn't trace on zfs filesystems
Status in fatrace package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Invalid
Bug description:
Hello, fatrace in focal doesn't seem to work for me in focal.
Start fatrace in one terminal, and perform file operations in another
terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.
sarnold@millbarge:~$ sudo fatrace
[sudo] password for sarnold:
^Csarnold@millbarge:~$ sudo strace -yy fatrace
execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0
brk(NULL) = 0x55c9a1947000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid
argument)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0
mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) =
0x7f3539b15000
close(3) = 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) =
3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832
lseek(3, 64, SEEK_SET) = 64
read(3,
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
lseek(3, 848, SEEK_SET) = 848
read(3,
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
lseek(3, 880, SEEK_SET) = 880
read(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
68) = 68
fstat(3, {st_mode=S_IFREG|0755,
st_size=2025032, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f3539b13000
lseek(3, 64, SEEK_SET) = 64
read(3,
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
lseek(3, 848, SEEK_SET) = 848
read(3,
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
lseek(3, 880, SEEK_SET) = 880
read(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
68) = 68
mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE,
3, 0) = 0x7f3539922000
mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x25000) = 0x7f3539947000
mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE,
3, 0x19d000) = 0x7f3539abf000
mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x1e6000) = 0x7f3539b09000
mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0
mprotect(0x7f3539b09000, 12288, PROT_READ) = 0
mprotect(0x55c99fee8000, 4096, PROT_READ) = 0
mprotect(0x7f3539b53000, 4096, PROT_READ) = 0
munmap(0x7f3539b15000, 71040) = 0
getpid()= 120700
fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) =
3
brk(NULL) = 0x55c9a1947000
brk(0x55c9a1968000) = 0x55c9a1968000
openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) =
4
fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) =
1024
access("sysfs", F_OK) = -1 ENOENT (No such file or
directory)
access("proc", F_OK)= -1 ENOENT (No such file or
directory)
access("udev", F_OK)= -1 ENOENT (No such file or
directory)
access("devpts", F_OK) = -1 ENOENT (No such file or
directory)
access("tmpfs", F_OK) = -1 ENOENT (No such file or
directory)
access("rpool/ROOT/ubuntu", F_OK) = -1 ENOENT (No such file or
directory)
access("securityfs", F_OK) = -1 ENOENT (No such file or
directory)
access("tmpfs", F_OK) = -1 ENOENT (No such file or
directory)
access("tmpfs", F_OK) = -1 ENOENT (No such file or
directory)
access("tmpfs", F_OK) = -1 ENOENT (No such file or
directory)
access("cgroup2", F_OK) = -1 ENOENT (No such file or
directory)
access("cgr
[Kernel-packages] [Bug 1861053] Re: no fatrace output in focal
The fatrace code has the following comment:
/* Only consider mounts which have an actual device or bind mount
* point. The others are stuff like proc, sysfs, binfmt_misc etc. which
* are virtual and do not actually cause disk access. */
This is why tracing /run /proc /sys does not work.
As the software works as designed I think this bug can be closed.
--
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/1861053
Title:
no fatrace output in focal
Status in fatrace package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hello, fatrace in focal doesn't seem to work for me in focal.
Start fatrace in one terminal, and perform file operations in another
terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.
sarnold@millbarge:~$ sudo fatrace
[sudo] password for sarnold:
^Csarnold@millbarge:~$ sudo strace -yy fatrace
execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0
brk(NULL) = 0x55c9a1947000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid
argument)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0
mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) =
0x7f3539b15000
close(3) = 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) =
3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832
lseek(3, 64, SEEK_SET) = 64
read(3,
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
lseek(3, 848, SEEK_SET) = 848
read(3,
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
lseek(3, 880, SEEK_SET) = 880
read(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
68) = 68
fstat(3, {st_mode=S_IFREG|0755,
st_size=2025032, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f3539b13000
lseek(3, 64, SEEK_SET) = 64
read(3,
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
lseek(3, 848, SEEK_SET) = 848
read(3,
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
lseek(3, 880, SEEK_SET) = 880
read(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
68) = 68
mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE,
3, 0) = 0x7f3539922000
mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x25000) = 0x7f3539947000
mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE,
3, 0x19d000) = 0x7f3539abf000
mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x1e6000) = 0x7f3539b09000
mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0
mprotect(0x7f3539b09000, 12288, PROT_READ) = 0
mprotect(0x55c99fee8000, 4096, PROT_READ) = 0
mprotect(0x7f3539b53000, 4096, PROT_READ) = 0
munmap(0x7f3539b15000, 71040) = 0
getpid()= 120700
fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) =
3
brk(NULL) = 0x55c9a1947000
brk(0x55c9a1968000) = 0x55c9a1968000
openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) =
4
fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) =
1024
access("sysfs", F_OK) = -1 ENOENT (No such file or
directory)
access("proc", F_OK)= -1 ENOENT (No such file or
directory)
access("udev", F_OK)= -1 ENOENT (No such file or
directory)
access("devpts", F_OK) = -1 ENOENT (No such file or
directory)
access("tmpfs", F_OK) = -1 ENOENT (No such file or
directory)
access("rpool/ROOT/ubuntu", F_OK) = -1 ENOENT (No such file or
directory)
access("securityfs", F_OK) = -1 ENOENT (No such file or
directory)
access("tmpfs", F_OK) = -1 ENOENT (No such file or
directory)
access("tmpfs", F_OK) = -1 ENOENT (No such file or
directory)
access("tmpfs", F_OK) = -1 ENOENT (No such file or
directory)
access("cgroup2", F_OK) = -1 ENOENT (No such file or
directory)
access("cgroup", F_OK) = -1 ENOENT (No such file or
directory)
access("pstore", F_OK) = -1 ENOENT (No such file or
directory)
access("efivarfs", F_OK)= -1 ENOENT (No such file or
directory)
read(
[Kernel-packages] [Bug 1941950] Re: linux-riscv: missing kernel signature
The RISC-V platform specification requires UEFI. Secure boot is defined in the UEFI specification. With U-Boot, Shim, GRUB, and a signed kernel I am able demonstrate secure boot on RISC-V. I am upstreaming the necessary patches. Roots of trust for RISC-V are in active development but not yet available on commercial boards: Cf. https://riscv.org/wp-content/uploads/2019/03/15.05-RISC-V-Security-Multizone-v-TrustZone-3-12-19.pdf Canonical has started discussing with SiFive how a root of trust can be supplied. A boot ROM checking the first bootstage (U-Boot SPL) using a certificate from the OTP memory would be a good start. This only requires a software change on the vendor side. -- 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/1941950 Title: linux-riscv: missing kernel signature Status in linux-riscv package in Ubuntu: New Bug description: U-Boot and EDK II both support secure boot. But vmlinuz-5.11.0-1014-generic and vmlinuz-5.13.0-1002-generic are not signed via sbsign. Please, adjust the RISC-V build system to sign new kernels. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1941950/+subscriptions -- Mailing list: https://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 1941950] [NEW] linux-riscv: missing kernel signature
Public bug reported: U-Boot and EDK II both support secure boot. But vmlinuz-5.11.0-1014-generic and vmlinuz-5.13.0-1002-generic are not signed via sbsign. Please, adjust the RISC-V build system to sign new kernels. Best regards Heinrich ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Tags: riscv64 -- 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/1941950 Title: linux-riscv: missing kernel signature Status in linux-riscv package in Ubuntu: New Bug description: U-Boot and EDK II both support secure boot. But vmlinuz-5.11.0-1014-generic and vmlinuz-5.13.0-1002-generic are not signed via sbsign. Please, adjust the RISC-V build system to sign new kernels. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1941950/+subscriptions -- Mailing list: https://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 1938705] [NEW] dmidecode: not built on riscv64
Public bug reported: riscv64 is missinag in debian/control ** Affects: dmidecode (Ubuntu) Importance: Undecided Status: New ** Tags: fr-1546 ** Tags added: fr-1546 -- 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/1938705 Title: dmidecode: not built on riscv64 Status in dmidecode package in Ubuntu: New Bug description: riscv64 is missinag in debian/control To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1938705/+subscriptions -- Mailing list: https://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 1938699] Re: cpu-checker: riscv64 build missing
** Tags added: fr-1545 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to cpu-checker in Ubuntu. https://bugs.launchpad.net/bugs/1938699 Title: cpu-checker: riscv64 build missing Status in cpu-checker package in Ubuntu: New Bug description: cpu-checker builds fine for RISC-V once architecture riscv64 is added to debian/control. A patch for kvm-ok is needed to add a /dev/kvm check for the RISC-V architecture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpu-checker/+bug/1938699/+subscriptions -- Mailing list: https://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 1938699] [NEW] cpu-checker: riscv64 build missing
Public bug reported: cpu-checker builds fine for RISC-V once architecture riscv64 is added to debian/control. A patch for kvm-ok is needed to add a /dev/kvm check for the RISC-V architecture. ** Affects: cpu-checker (Ubuntu) Importance: Undecided Status: New ** Tags: riscv64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to cpu-checker in Ubuntu. https://bugs.launchpad.net/bugs/1938699 Title: cpu-checker: riscv64 build missing Status in cpu-checker package in Ubuntu: New Bug description: cpu-checker builds fine for RISC-V once architecture riscv64 is added to debian/control. A patch for kvm-ok is needed to add a /dev/kvm check for the RISC-V architecture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpu-checker/+bug/1938699/+subscriptions -- Mailing list: https://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 1937868] [NEW] linux-riscv: booting the kernel via the EFI stub with large initrd fails
Public bug reported: The Linux kernel currently requires that the initrd fits into the low 128 MiB which may fail due to reserved regions or large size of the initrd. A patch to resolve the issue has been included into linux-next: [PATCH 1/1] RISC-V: load initrd wherever it fits into memory https://lore.kernel.org/linux-efi/mhng-34467fe7-5a31-4c88-a5ad-6dea683fcfeb@palmerdabbelt-glaptop/T/#t https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20210723&id=c79e89ecaa246c880292ba68cbe08c9c30db77e3 Best regards Heinrich ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Tags: riscv64 ** Summary changed: - linux-riscv: booting the kernel via the EFI stub with large initrds fails + linux-riscv: booting the kernel via the EFI stub with large initrd fails -- 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/1937868 Title: linux-riscv: booting the kernel via the EFI stub with large initrd fails Status in linux-riscv package in Ubuntu: New Bug description: The Linux kernel currently requires that the initrd fits into the low 128 MiB which may fail due to reserved regions or large size of the initrd. A patch to resolve the issue has been included into linux-next: [PATCH 1/1] RISC-V: load initrd wherever it fits into memory https://lore.kernel.org/linux-efi/mhng-34467fe7-5a31-4c88-a5ad-6dea683fcfeb@palmerdabbelt-glaptop/T/#t https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20210723&id=c79e89ecaa246c880292ba68cbe08c9c30db77e3 Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1937868/+subscriptions -- Mailing list: https://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 1931432] Re: crash FTBFS on riscv64
#1935679 has a patch for the segfault. But additional work will be needed to enable building on RISC-V. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1931432 Title: crash FTBFS on riscv64 Status in crash package in Ubuntu: Confirmed Status in crash source package in Focal: Confirmed Status in crash source package in Groovy: Confirmed Bug description: Crash fails to build from source on riscv at least for Focal and Groovy, later releases may also be affected but I haven't confirm it. Examples of failed builds : Groovy : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630864 Focal : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.04.1/+build/21630885 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931432/+subscriptions -- Mailing list: https://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 1935679] Re: crash: build failure on RISC-V
*** This bug is a duplicate of bug 1931432 *** https://bugs.launchpad.net/bugs/1931432 ** This bug has been marked a duplicate of bug 1931432 crash FTBFS on riscv64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1935679 Title: crash: build failure on RISC-V Status in crash package in Ubuntu: New Bug description: version: 7.3.0-1ubuntu1 Building crash for RISC-V fails with a segfault. This segfault is due to missing support for architecture RISC-V in file configure.c. configure is used to update Makefile. It replaces "TARGET " by "(NULL)". A patch is at https://github.com/xypron/crash/commit/2391175c7936a3d873b7b7f1b6c6cae2f4c166b8 Current upstream crash uses an version 7.6 for gdb which does not support RISC-V. Patch series https://listman.redhat.com/archives/crash- utility/2021-March/msg00078.html provides an update to gdb 10.1. https://github.com/YustasSwamp/crash/tree/crash-gdb10.2-devel-temp provides patches for using gdb 10.2. For building we need command makeinfo which is provided by missing package texinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1935679/+subscriptions -- Mailing list: https://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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
After updating to linux-firmware commit d79c26779d45906 the problems persist on Lenovo Thinkpad E585: amdgpu :05:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1336 thread Xorg:cs0 pid 1862) -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://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 1935679] Re: crash: build failure on RISC-V
** Tags added: riscv64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1935679 Title: crash: build failure on RISC-V Status in crash package in Ubuntu: New Bug description: version: 7.3.0-1ubuntu1 Building crash for RISC-V fails with a segfault. This segfault is due to missing support for architecture RISC-V in file configure.c. configure is used to update Makefile. It replaces "TARGET " by "(NULL)". A patch is at https://github.com/xypron/crash/commit/2391175c7936a3d873b7b7f1b6c6cae2f4c166b8 Current upstream crash uses an version 7.6 for gdb which does not support RISC-V. Patch series https://listman.redhat.com/archives /crash-utility/2021-March/msg00078.html provides an update to gdb 10.1. https://github.com/YustasSwamp/crash/tree/crash-gdb10.2-devel-temp provides patches for using gdb 10.2. For building we need command makeinfo which is provided by missing package texinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1935679/+subscriptions -- Mailing list: https://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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
There is an upstream bug report https://bugzilla.kernel.org/show_bug.cgi?id=213391 Comment 9 suggest: "downgrade the firmware." Comment 15 claims: "20210315 seems to work fine here (on an E595)." ** Bug watch added: Linux Kernel Bug Tracker #213391 https://bugzilla.kernel.org/show_bug.cgi?id=213391 -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://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 1935679] Re: crash: build failure on RISC-V
The upstream issue for RISC-V support is https://github.com/crash- utility/crash/issues/89 ** Bug watch added: github.com/crash-utility/crash/issues #89 https://github.com/crash-utility/crash/issues/89 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1935679 Title: crash: build failure on RISC-V Status in crash package in Ubuntu: New Bug description: version: 7.3.0-1ubuntu1 Building crash for RISC-V fails with a segfault. This segfault is due to missing support for architecture RISC-V in file configure.c. configure is used to update Makefile. It replaces "TARGET " by "(NULL)". A patch is at https://github.com/xypron/crash/commit/2391175c7936a3d873b7b7f1b6c6cae2f4c166b8 Current upstream crash uses an version 7.6 for gdb which does not support RISC-V. Patch series https://listman.redhat.com/archives /crash-utility/2021-March/msg00078.html provides an update to gdb 10.1. https://github.com/YustasSwamp/crash/tree/crash-gdb10.2-devel-temp provides patches for using gdb 10.2. For building we need command makeinfo which is provided by missing package texinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1935679/+subscriptions -- Mailing list: https://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 1935679] Re: crash: build failure on RISC-V
Additionally to adjusting configure.c the following changes to the upstream source are needed: Add RISC-V to defs.h Create riscv64.c, unwind_riscv64.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1935679 Title: crash: build failure on RISC-V Status in crash package in Ubuntu: New Bug description: version: 7.3.0-1ubuntu1 Building crash for RISC-V fails with a segfault. This segfault is due to missing support for architecture RISC-V in file configure.c. configure is used to update Makefile. It replaces "TARGET " by "(NULL)". A patch is at https://github.com/xypron/crash/commit/2391175c7936a3d873b7b7f1b6c6cae2f4c166b8 Current upstream crash uses an version 7.6 for gdb which does not support RISC-V. Patch series https://listman.redhat.com/archives /crash-utility/2021-March/msg00078.html provides an update to gdb 10.1. https://github.com/YustasSwamp/crash/tree/crash-gdb10.2-devel-temp provides patches for using gdb 10.2. For building we need command makeinfo which is provided by missing package texinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1935679/+subscriptions -- Mailing list: https://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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Also affected: Ubuntu version: 21.04 Linux kernel: 5.11.0-22-generic x86_64 CPU model: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx GPU: 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c4) Laptop model: Lenovo Thinkpad E585 -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://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 1935679] Re: crash: build failure on RISC-V
makeinfo is provided in universe. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1935679 Title: crash: build failure on RISC-V Status in crash package in Ubuntu: New Bug description: version: 7.3.0-1ubuntu1 Building crash for RISC-V fails with a segfault. This segfault is due to missing support for architecture RISC-V in file configure.c. configure is used to update Makefile. It replaces "TARGET " by "(NULL)". A patch is at https://github.com/xypron/crash/commit/2391175c7936a3d873b7b7f1b6c6cae2f4c166b8 Current upstream crash uses an version 7.6 for gdb which does not support RISC-V. Patch series https://listman.redhat.com/archives /crash-utility/2021-March/msg00078.html provides an update to gdb 10.1. https://github.com/YustasSwamp/crash/tree/crash-gdb10.2-devel-temp provides patches for using gdb 10.2. For building we need command makeinfo which is provided by missing package texinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1935679/+subscriptions -- Mailing list: https://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 1935679] Re: crash: build failure on RISC-V
** Patch added: "0001-configure.c-add-RISC-V-architecture.patch" https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1935679/+attachment/5510055/+files/0001-configure.c-add-RISC-V-architecture.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1935679 Title: crash: build failure on RISC-V Status in crash package in Ubuntu: New Bug description: version: 7.3.0-1ubuntu1 Building crash for RISC-V fails with a segfault. This segfault is due to missing support for architecture RISC-V in file configure.c. configure is used to update Makefile. It replaces "TARGET " by "(NULL)". A patch is at https://github.com/xypron/crash/commit/2391175c7936a3d873b7b7f1b6c6cae2f4c166b8 Current upstream crash uses an version 7.6 for gdb which does not support RISC-V. Patch series https://listman.redhat.com/archives /crash-utility/2021-March/msg00078.html provides an update to gdb 10.1. https://github.com/YustasSwamp/crash/tree/crash-gdb10.2-devel-temp provides patches for using gdb 10.2. For building we need command makeinfo which is provided by missing package texinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1935679/+subscriptions -- Mailing list: https://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 1935679] [NEW] crash: build failure on RISC-V
Public bug reported: version: 7.3.0-1ubuntu1 Building crash for RISC-V fails with a segfault. This segfault is due to missing support for architecture RISC-V in file configure.c. configure is used to update Makefile. It replaces "TARGET " by "(NULL)". A patch is at https://github.com/xypron/crash/commit/2391175c7936a3d873b7b7f1b6c6cae2f4c166b8 Current upstream crash uses an version 7.6 for gdb which does not support RISC-V. Patch series https://listman.redhat.com/archives/crash- utility/2021-March/msg00078.html provides an update to gdb 10.1. https://github.com/YustasSwamp/crash/tree/crash-gdb10.2-devel-temp provides patches for using gdb 10.2. For building we need command makeinfo which is provided by missing package texinfo. ** Affects: crash (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1935679 Title: crash: build failure on RISC-V Status in crash package in Ubuntu: New Bug description: version: 7.3.0-1ubuntu1 Building crash for RISC-V fails with a segfault. This segfault is due to missing support for architecture RISC-V in file configure.c. configure is used to update Makefile. It replaces "TARGET " by "(NULL)". A patch is at https://github.com/xypron/crash/commit/2391175c7936a3d873b7b7f1b6c6cae2f4c166b8 Current upstream crash uses an version 7.6 for gdb which does not support RISC-V. Patch series https://listman.redhat.com/archives /crash-utility/2021-March/msg00078.html provides an update to gdb 10.1. https://github.com/YustasSwamp/crash/tree/crash-gdb10.2-devel-temp provides patches for using gdb 10.2. For building we need command makeinfo which is provided by missing package texinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1935679/+subscriptions -- Mailing list: https://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 1929594] [NEW] linux-image-5.11.0-1008-generic: cannot read initrd via EFI_LOAD_FILE2_PROTOCOL
Public bug reported: I am running on QEMU riscv64 with upstream OpenSBI and U-Boot. $ lsb_release -rd Description:Ubuntu 21.04 Release:21.04 In U-Boot I define a boot option and boot via UEFI: efidebug boot add -b 0001 Ubuntu virtio 0:1 boot/vmlinuz-5.11.0-1008-generic -i virtio 0:1 boot/initrd.img-5.11.0-1008-generic -s 'root=UUID=386038e2-e47c-49db-a74b-db2e730fa494 earlycon console=ttyS0' efidebug boot order 0001 bootefi bootmgr Loading the initial RAM disk fails due to a bug in the EFI kernel stub: U-Boot's implementation of the EFI_LOAD_FILE2_PROTOCOL is called with buffer=NULL, *buffer_size=0 and returns the buffer size and status code EFI_BUFFER_TOO_SMALL. Now the upstream kernel code would allocate the memory and call the protocol a second time. But the Ubuntu kernel does not allocate memory. I added '#define DEBUG 1' to U-Boot's efi_memory.c to efi_load_initrd.c to get more output: Linux version 5.11.0-1008-generic (buildd@riscv64-qemu-lcy01-015) (gcc (Ubuntu 10.3.0-1ubuntu1) EFI: Entry efi_load_file2_initrd(fffd98e8, fbe54f7c, 0, ff73f3e0, ) EFI: efi_add_memory_map_pg: 0xfe71f000 0x1 0 yes EFI: efi_add_memory_map_pg: 0xfe71e000 0x1 0 yes EFI: efi_add_memory_map_pg: 0xfe71f000 0x1 7 no EFI: efi_add_memory_map_pg: 0xfe71f000 0x1 0 yes EFI: efi_add_memory_map_pg: 0xfe71d000 0x1 0 yes EFI: efi_add_memory_map_pg: 0xfe71d000 0x1 7 no EFI: efi_add_memory_map_pg: 0xfe71f000 0x1 7 no EFI: efi_add_memory_map_pg: 0xfe71e000 0x1 7 no EFI: Call: f->close(f) EFI: 0 returned by f->close(f) EFI: Exit: efi_load_file2_initrd: 5 EFI stub: ERROR: Failed to load initrd! EFI: efi_add_memory_map_pg: 0xfe71f000 0x1 2 yes When using a Debian kernel everything works as expected: Linux version 5.10.0-7-riscv64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) EFI: Entry efi_load_file2_initrd(fffd98e8, fcd10afc, 0, ff73dd30, ) EFI: efi_add_memory_map_pg: 0xfe71f000 0x1 0 yes EFI: efi_add_memory_map_pg: 0xfe71e000 0x1 0 yes EFI: efi_add_memory_map_pg: 0xfe71f000 0x1 7 no EFI: efi_add_memory_map_pg: 0xfe71f000 0x1 0 yes EFI: efi_add_memory_map_pg: 0xfe71d000 0x1 0 yes EFI: efi_add_memory_map_pg: 0xfe71d000 0x1 7 no EFI: efi_add_memory_map_pg: 0xfe71f000 0x1 7 no EFI: efi_add_memory_map_pg: 0xfe71e000 0x1 7 no EFI: Call: f->close(f) EFI: 0 returned by f->close(f) EFI: Exit: efi_load_file2_initrd: 5 EFI: efi_add_memory_map_pg: 0x88c9d000 0x7562 2 yes EFI: Entry efi_load_file2_initrd(fffd98e8, fcd10afc, 0, ff73dd30, 88c9d000) EFI: efi_add_memory_map_pg: 0xfe71f000 0x1 0 yes EFI: efi_add_memory_map_pg: 0xfe71e000 0x1 0 yes EFI: efi_add_memory_map_pg: 0xfe71f000 0x1 7 no EFI: efi_add_memory_map_pg: 0xfe71f000 0x1 0 yes EFI: efi_add_memory_map_pg: 0xfe71d000 0x1 0 yes EFI: efi_add_memory_map_pg: 0xfe71d000 0x1 7 no EFI: efi_add_memory_map_pg: 0xfe71f000 0x1 7 no EFI: Call: f->read(f, &bs, (void *)(uintptr_t)buffer) EFI: 0 returned by f->read(f, &bs, (void *)(uintptr_t)buffer) EFI: efi_add_memory_map_pg: 0xfe71e000 0x1 7 no EFI: Call: f->close(f) EFI: 0 returned by f->close(f) EFI: Exit: efi_load_file2_initrd: 0 Best regards Heinrich ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-1008-generic 5.11.0-1008.8 Uname: Linux 5.10.0-7-riscv64 riscv64 ApportVersion: 2.20.11-0ubuntu65 Architecture: riscv64 CasperMD5CheckResult: unknown Date: Tue May 25 17:13:44 2021 ProcCpuinfoMinimal: processor : 2 hart : 1 isa: rv64imafdcsu mmu: sv48 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug hirsute riscv64 uec-images -- 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/1929594 Title: linux-image-5.11.0-1008-generic: cannot read initrd via EFI_LOAD_FILE2_PROTOCOL Status in linux-riscv package in Ubuntu: New Bug description: I am running on QEMU riscv64 with upstream OpenSBI and U-Boot. $ lsb_release -rd Description:Ubuntu 21.04 Release:21.04 In U-Boot I define a boot option and boot via UEFI: efidebug boot add -b 0001 Ubuntu virtio 0:1 boot/vmlinuz-5.11.0-1008-generic -i virtio 0:1 boot/initrd.img-5.11.0-1008-generic -s 'root=UUID=386038e2-e47c-49db-a74b-db2e730fa494 earlycon console=ttyS0' efidebug boot order 0001 bootefi bootmgr Loading the initial RAM disk fails due to a bug in the EFI kernel stub: U-Boot's implementation of the EFI_LOAD_FILE2_PROTOCOL is called with buffer=NULL, *buffer_size=0 and returns the buffer size and status code EFI_BUFFER_TOO_SMALL. Now the upstream kernel
[Kernel-packages] [Bug 405525] ✈The world's travel search engine Skyscanner compares millions of flights to find you the cheapest deal, fast.
Whether you want to go to Tenerife or Tokyo, we'll find low cost flights to get you there. We also find the cheapest hotels and car hire deals. Just dial: 888-369-2751. Skyscanner is free! When you find your flights and dial (888) 369-2751, we redirect your call through directly to the airline or travel agent.We never charge you commission. Nor do we add hidden fees. See more ways we put you first. Acclaimed flight comparison Skyscanner is an award winning site recommended by: The Independent, The Guardian, Which? Travel, BBC Radio 1 and more!Skyscanner has been consistently found to be comprehensive, fast, and the best way to find cheap flights. Just dial: 888-369-2751. Let’s get social! Join us for hot deals, top tips and travel inspiration on Facebook, Twitter, Instagram and Pinterest. Find the perfect place to stay The Trip by Skyscanner community has reviewed tens of thousands of hotels around the world so you can always find the perfect place to stay, based on your tribe and your price range. Simply select your destination, dial 888-369-2751, and you are off! And now Trip by Skyscanner searches all the top booking sites to make sure to always find you the lowest price. Check out some of our most popular destinations: Chicago-New York$175.52Los Angeles-San Francisco$103.72Los Angeles-New York$175.42Chicago-Los Angeles$325.63Miami-New York$96.00Atlanta-Chicago$100.47San Francisco-New York City$293.73New York City-Kingston$461.29Miami-Johannesburg$1016.01Chicago-Minneapolis$95.87Chicago-Washington DC$195.24New York City-Toronto$119.96Top Deal 55% Off: Skyscanner's Flight Deals. Primary: 888-369-2751. 24/7 Support. Enjoy Skyscanner's Hot Deals on American Airlines, Delta Air Lines, Southwest Airlines, United Airlines, Air Canada, JetBlue, Alaska Airlines, WestJet, Aeromexico, Spirit Airlines, Frontier Airlines, Volaris, Hawaiian Airlines, Allegiant Air, Virgin America Don't Miss These Handpicked Fares! Primary 888-369-2751. 24/7 Support -- 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/405525 Title: [Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA)] suspend/resume failure Status in linux package in Ubuntu: Expired Bug description: Under 8.10 suspend worked pretty much flawlessly. Installed Karmic as 9.04 my sound card would not work for some reason. may end up going back to 8.10 as My vid card is not supported anymore by ATI after that version. but that is not here nor there. tried to wake up my laptop like normal. system stayed at black screen. backlight sis not come on. I know this is alpha and I am not mad but I am reporting this so the developers know it. I have no idea what caused the problem but hopefully the bug catcher included stuff to help trace it. If not please delete this bug as I have no other Idea what could have caused it. Thanks for making a great product. I have used Ubuntu since 6.06 and have watched it get better and better every release (with exception to 9.04) ;) thanks again guys. ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: i386 Date: Mon Jul 27 17:10:03 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3a408910-86e2-46ec-a784-90545d8f3f2c InterpreterPath: /usr/bin/python2.6 MachineType: Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA) Package: linux-image-2.6.31-4-generic 2.6.31-4.22 ProcCmdLine: root=UUID=fe6d390e-5c59-40db-98f8-09dbdbd0b864 ro vga=792 ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.31-4.22-generic RelatedPackageVersions: linux-backports-modules-2.6.31-4-generic N/A SourcePackage: linux Tags: resume suspend Title: [Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA)] suspend/resume failure Uname: Linux 2.6.31-4-generic i686 UserGroups: dmi.bios.date: 02/24/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.name: 3096 dmi.board.vendor: Quanta dmi.board.version: 47.0E dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.24:bd02/24/2006:svnHewlett-Packard:pnHPPavilionze2000(EC205UA#ABA):pvrRev1:rvnQuanta:rn3096:rvr47.0E:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion ze2000 (EC205UA#ABA) dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/405525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
