[Kernel-packages] [Bug 1871590] Re: Kernel 5.3 fails to boot on Inspiron 15 3000 running Ubuntu 18.04 since 2020-03-22 update
Oh, just now I noticed that "earlycon=efifb", I've missed that... It will take some time until I will have access to that computer again thorugh... -- 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/1871590 Title: Kernel 5.3 fails to boot on Inspiron 15 3000 running Ubuntu 18.04 since 2020-03-22 update Status in linux package in Ubuntu: Incomplete Bug description: Hi, Here's update that broke boot on that Inspiron 15 3000: Start-Date: 2020-03-22 16:11:26 Commandline: aptdaemon role='role-commit-packages' sender=':1.89' Install: linux-image-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, automatic), linux-headers-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, autom atic), linux-modules-extra-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, automatic), linux-headers-5.3.0-42:amd64 (5.3.0-42.34~18.04.1, automat ic), linux-modules-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, automatic) Upgrade: linux-libc-dev:amd64 (4.15.0-88.88, 4.15.0-91.92), grub-common:amd64 (2.02-2ubuntu8.14, 2.02-2ubuntu8.15), libicu60:amd64 (60.2-3ubun tu3, 60.2-3ubuntu3.1), linux-headers-generic-hwe-18.04:amd64 (5.3.0.40.97, 5.3.0.42.99), grub2-common:amd64 (2.02-2ubuntu8.14, 2.02-2ubuntu8.1 5), skypeforlinux:amd64 (8.57.0.116, 8.58.0.93), apport:amd64 (2.20.9-0ubuntu7.11, 2.20.9-0ubuntu7.12), grub-efi-amd64-bin:amd64 (2.02-2ubuntu 8.14, 2.02-2ubuntu8.15), python3-apport:amd64 (2.20.9-0ubuntu7.11, 2.20.9-0ubuntu7.12), linux-image-generic-hwe-18.04:amd64 (5.3.0.40.97, 5.3. 0.42.99), grub-efi-amd64:amd64 (2.02-2ubuntu8.14, 2.02-2ubuntu8.15), apport-gtk:amd64 (2.20.9-0ubuntu7.11, 2.20.9-0ubuntu7.12), grub-efi-amd64 -signed:amd64 (1.93.15+2.02-2ubuntu8.14, 1.93.16+2.02-2ubuntu8.15), libsgutils2-2:amd64 (1.42-2ubuntu1.18.04.1, 1.42-2ubuntu1.18.04.2), python 3-problem-report:amd64 (2.20.9-0ubuntu7.11, 2.20.9-0ubuntu7.12) End-Date: 2020-03-22 16:12:50 Kernel 4.15 works fine though. None of 5.3.x releases managed to boot - it just hangs on loading initrd. Tried to reinstall grub, grub-efi; tried running update-grub, grub- insall, reinstalling 5.3 pacakges (from LiveCD), etc, but nothing helped. Ubuntu is installed on NVME, maybe it gives the problems? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1434 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-glk+X36 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-12 (372 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Inspiron 3582 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=deb0fd33-d5dc-4831-ac22-6990511c0550 ro mem_sleep_default=deep quiet splash ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-96-generic N/A linux-backports-modules-4.15.0-96-generic N/A linux-firmware 1.173.17 Tags: bionic Uname: Linux 4.15.0-96-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: Inspiron 3582 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd03/06/2019:svnDellInc.:pnInspiron3582:pvr1.2.1:rvnDellInc.:rnInspiron3582:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 3582 dmi.product.version: 1.2.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827982] Re: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / Oracle-4.15
Can be reproduced on B-oracle-5.3 5.3.0-1015.16~18.04.1 Failed with VM.Standard2.16 ** Tags added: sru-20200406 ** Tags added: 5.3 oracle -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1827982 Title: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / Oracle-4.15 Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Test timeouted. # TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # -initrd /tmp/tmp.ouYfwUEdq5 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic cpus = 2 qemu-system-x86_64: terminating on signal 15 from pid 2224 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:39:16 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824228] Re: ept test fails in kvm_unit_tests
Found on Oracle Bionic 5.3 5.3.0-1015.16~18.04.1 ** Tags added: sru-20200406 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1824228 Title: ept test fails in kvm_unit_tests Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Disco: New Status in linux-kvm source package in Disco: New Status in linux-oracle source package in Disco: New Status in linux-azure source package in Eoan: New Status in linux-kvm source package in Eoan: New Status in linux-oracle source package in Eoan: New Bug description: Reproducible: Yes, Series: cosmic Kernel: "linux-azure 4.18.0-1015.15" Steps: 1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib 2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3.) cd kvm-unit-tests; ./configure; make 4.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append "ept_access*" timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd /tmp/tmp.RcwfbGP5Ou enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: ept_access_test_not_present Test suite: ept_access_test_read_only Test suite: ept_access_test_write_only Test suite: ept_access_test_read_write Test suite: ept_access_test_execute_only Test suite: ept_access_test_read_execute Test suite: ept_access_test_write_execute Test suite: ept_access_test_read_write_execute Test suite: ept_access_test_reserved_bits Test suite: ept_access_test_ignored_bits Test suite: ept_access_test_paddr_not_present_ad_disabled Test suite: ept_access_test_paddr_not_present_ad_enabled Host skipping test: EPT AD bits not supported. Test suite: ept_access_test_paddr_read_only_ad_disabled EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312 Test suite: ept_access_test_paddr_read_only_ad_enabled Host skipping test: EPT AD bits not supported. Test suite: ept_access_test_paddr_read_write Test suite: ept_access_test_paddr_read_write_execute Test suite: ept_access_test_paddr_read_execute_ad_disabled EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab - ''''''''''''''1010'1011 - 171 RHS: 0x00aa - ''''''''''''''1010'1010 - 170 STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab - ''''''''''''''1010'1011 - 171 RHS: 0x00aa - ''''''''''''''1010'1010 - 170 STACK: 40f328 40f8fb 40fb0b 40fdfc 401577 4039d0
[Kernel-packages] [Bug 1871590] Re: Kernel 5.3 fails to boot on Inspiron 15 3000 running Ubuntu 18.04 since 2020-03-22 update
Strangely, after wall of text, it just asks to press any key, and then returns back to Grub... Did I set parameters wrong? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871590 Title: Kernel 5.3 fails to boot on Inspiron 15 3000 running Ubuntu 18.04 since 2020-03-22 update Status in linux package in Ubuntu: Incomplete Bug description: Hi, Here's update that broke boot on that Inspiron 15 3000: Start-Date: 2020-03-22 16:11:26 Commandline: aptdaemon role='role-commit-packages' sender=':1.89' Install: linux-image-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, automatic), linux-headers-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, autom atic), linux-modules-extra-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, automatic), linux-headers-5.3.0-42:amd64 (5.3.0-42.34~18.04.1, automat ic), linux-modules-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, automatic) Upgrade: linux-libc-dev:amd64 (4.15.0-88.88, 4.15.0-91.92), grub-common:amd64 (2.02-2ubuntu8.14, 2.02-2ubuntu8.15), libicu60:amd64 (60.2-3ubun tu3, 60.2-3ubuntu3.1), linux-headers-generic-hwe-18.04:amd64 (5.3.0.40.97, 5.3.0.42.99), grub2-common:amd64 (2.02-2ubuntu8.14, 2.02-2ubuntu8.1 5), skypeforlinux:amd64 (8.57.0.116, 8.58.0.93), apport:amd64 (2.20.9-0ubuntu7.11, 2.20.9-0ubuntu7.12), grub-efi-amd64-bin:amd64 (2.02-2ubuntu 8.14, 2.02-2ubuntu8.15), python3-apport:amd64 (2.20.9-0ubuntu7.11, 2.20.9-0ubuntu7.12), linux-image-generic-hwe-18.04:amd64 (5.3.0.40.97, 5.3. 0.42.99), grub-efi-amd64:amd64 (2.02-2ubuntu8.14, 2.02-2ubuntu8.15), apport-gtk:amd64 (2.20.9-0ubuntu7.11, 2.20.9-0ubuntu7.12), grub-efi-amd64 -signed:amd64 (1.93.15+2.02-2ubuntu8.14, 1.93.16+2.02-2ubuntu8.15), libsgutils2-2:amd64 (1.42-2ubuntu1.18.04.1, 1.42-2ubuntu1.18.04.2), python 3-problem-report:amd64 (2.20.9-0ubuntu7.11, 2.20.9-0ubuntu7.12) End-Date: 2020-03-22 16:12:50 Kernel 4.15 works fine though. None of 5.3.x releases managed to boot - it just hangs on loading initrd. Tried to reinstall grub, grub-efi; tried running update-grub, grub- insall, reinstalling 5.3 pacakges (from LiveCD), etc, but nothing helped. Ubuntu is installed on NVME, maybe it gives the problems? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1434 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-glk+X36 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-12 (372 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Inspiron 3582 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=deb0fd33-d5dc-4831-ac22-6990511c0550 ro mem_sleep_default=deep quiet splash ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-96-generic N/A linux-backports-modules-4.15.0-96-generic N/A linux-firmware 1.173.17 Tags: bionic Uname: Linux 4.15.0-96-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: Inspiron 3582 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd03/06/2019:svnDellInc.:pnInspiron3582:pvr1.2.1:rvnDellInc.:rnInspiron3582:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 3582 dmi.product.version: 1.2.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867623] Re: vmx_host_state_area in ubuntu_kvm_unit_tests generates kernel traces on B-oracle-5.3
Test suite can finish on B-oracle-5.3 now. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-oracle (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1867623 Title: vmx_host_state_area in ubuntu_kvm_unit_tests generates kernel traces on B-oracle-5.3 Status in ubuntu-kernel-tests: Fix Released Status in linux-oracle package in Ubuntu: Invalid Bug description: Instance: VM.Standard.2.16 Kernel: 5.3.0-1011-oracle $ sudo ./vmx_host_state_area BUILD_HEAD=4671e4ba timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.5eo0pN79fr -smp 1 -cpu host,+vmx -append vmx_host_state_area_test # -initrd /tmp/tmp.x05eknzWqQ enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_host_state_area_test PASS: HOST_CR0 8021: vmlaunch succeeds PASS: HOST_CR0 80010030: vmlaunch fails PASS: HOST_CR0 80010030: VMX inst error is 8 (actual 8) PASS: HOST_CR0 80010011: vmlaunch fails PASS: HOST_CR0 80010011: VMX inst error is 8 (actual 8) PASS: HOST_CR0 10031: vmlaunch fails PASS: HOST_CR0 10031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 180010031: vmlaunch fails PASS: HOST_CR0 180010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 280010031: vmlaunch fails PASS: HOST_CR0 280010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 480010031: vmlaunch fails PASS: HOST_CR0 480010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 880010031: vmlaunch fails PASS: HOST_CR0 880010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 1080010031: vmlaunch fails PASS: HOST_CR0 1080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 2080010031: vmlaunch fails PASS: HOST_CR0 2080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 4080010031: vmlaunch fails PASS: HOST_CR0 4080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 8080010031: vmlaunch fails PASS: HOST_CR0 8080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 10080010031: vmlaunch fails PASS: HOST_CR0 10080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 20080010031: vmlaunch fails PASS: HOST_CR0 20080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 40080010031: vmlaunch fails PASS: HOST_CR0 40080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 80080010031: vmlaunch fails PASS: HOST_CR0 80080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 100080010031: vmlaunch fails PASS: HOST_CR0 100080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 200080010031: vmlaunch fails PASS: HOST_CR0 200080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 400080010031: vmlaunch fails PASS: HOST_CR0 400080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 800080010031: vmlaunch fails PASS: HOST_CR0 800080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 180010031: vmlaunch fails PASS: HOST_CR0 180010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 280010031: vmlaunch fails PASS: HOST_CR0 280010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 480010031: vmlaunch fails PASS: HOST_CR0 480010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 880010031: vmlaunch fails PASS: HOST_CR0 880010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 1080010031: vmlaunch fails PASS: HOST_CR0 1080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 2080010031: vmlaunch fails PASS: HOST_CR0 2080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 4080010031: vmlaunch fails PASS: HOST_CR0 4080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 8080010031: vmlaunch fails PASS: HOST_CR0 8080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 10080010031: vmlaunch fails PASS: HOST_CR0 10080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 20080010031: vmlaunch fails PASS: HOST_CR0 20080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 40080010031: vmlaunch fails PASS: HOST_CR0 40080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 80080010031: vmlaunch fails PASS: HOST_CR0 80080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 100080010031: vmlaunch fails PASS: HOST_CR0 100080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 200080010031: vmlaunch fails PASS: HOST_CR0 200080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 400080010031: vmlaunch fails PASS: HOST_CR0 400080010031: VMX inst error is 8 (actual 8) PASS: HOST_CR0 800080010031: vmlaunch fails PASS: HOST_CR0 800080010031: VMX inst error is 8 (actual 8) FAIL: HOST_CR4 2000: vmlaunch succeeds
[Kernel-packages] [Bug 1874186] Re: vmx_vmcs_shadow_test from ubunut_kvm_unit_tests timeout on E-KVM
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: 5.3 sru-20200406 ubuntu-kvm-unit-tests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1874186 Title: vmx_vmcs_shadow_test from ubunut_kvm_unit_tests timeout on E-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Issue found on E-KVM 5.3.0-1016.17-kvm and can be reproduced on 5.3.0-1015-kvm as well, thus this is not a regression. PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: shadowed for VMWRITE (in 21056 cycles) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: ALU flags after VMWRITE (1) are as expected (1) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: shadowed for VMREAD (in 20236 cycles) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: ALU flags after VMREAD (1) are as expected (1) qemu-system-x86_64: terminating on signal 15 from pid 2874 (timeout) FAIL vmx_vmcs_shadow_test (timeout; duration=180) Need to test it with a longer timeout setting. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1015-kvm 5.3.0-1015.16 ProcVersionSignature: User Name 5.3.0-1015.16-kvm 5.3.18 Uname: Linux 5.3.0-1015-kvm x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Wed Apr 22 04:37:11 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1874186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874186] [NEW] vmx_vmcs_shadow_test from ubunut_kvm_unit_tests timeout on E-KVM
Public bug reported: Issue found on E-KVM 5.3.0-1016.17-kvm and can be reproduced on 5.3.0-1015-kvm as well, thus this is not a regression. PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: shadowed for VMWRITE (in 21056 cycles) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: ALU flags after VMWRITE (1) are as expected (1) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: shadowed for VMREAD (in 20236 cycles) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: ALU flags after VMREAD (1) are as expected (1) qemu-system-x86_64: terminating on signal 15 from pid 2874 (timeout) FAIL vmx_vmcs_shadow_test (timeout; duration=180) Need to test it with a longer timeout setting. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1015-kvm 5.3.0-1015.16 ProcVersionSignature: User Name 5.3.0-1015.16-kvm 5.3.18 Uname: Linux 5.3.0-1015-kvm x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Wed Apr 22 04:37:11 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: 5.3 amd64 apport-bug eoan sru-20200406 ubuntu-kvm-unit-tests uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1874186 Title: vmx_vmcs_shadow_test from ubunut_kvm_unit_tests timeout on E-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Issue found on E-KVM 5.3.0-1016.17-kvm and can be reproduced on 5.3.0-1015-kvm as well, thus this is not a regression. PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: shadowed for VMWRITE (in 21056 cycles) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: ALU flags after VMWRITE (1) are as expected (1) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: shadowed for VMREAD (in 20236 cycles) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: ALU flags after VMREAD (1) are as expected (1) qemu-system-x86_64: terminating on signal 15 from pid 2874 (timeout) FAIL vmx_vmcs_shadow_test (timeout; duration=180) Need to test it with a longer timeout setting. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1015-kvm 5.3.0-1015.16 ProcVersionSignature: User Name 5.3.0-1015.16-kvm 5.3.18 Uname: Linux 5.3.0-1015-kvm x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Wed Apr 22 04:37:11 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1874186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module
Attached is proof the VM is using VGA=std for the ppc64el test. ** Attachment added: "Proof VM is running VGA=std on ppc64el" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872863/+attachment/5357796/+files/Screenshot%20from%202020-04-22%2015-14-04.png -- 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/1872863 Title: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device, as the efifb driver yields an unreadable garbled screen. See the attached image. The correct framebuffer driver to use in this situation is bochs-drm, and modprobing it from a HWE kernel fixes the issues. bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in LP #1378648 due to bochs-drm causing problems in a PowerKVM machine. This problem appears to be fixed now, and bochs-drm has been re-enabled for Disco and up, in LP #1795857 and has been proven safe. This has also come up again in LP #1823152, as well as chatter on LP #1795857 to get this enabled on Bionic. The customer which is experiencing this issue cannot switch to VGA=qxl as a workaround, and must use VGA=std, hence I suggest we re-enable bochs-drm for Bionic. [Fix] I noticed on Focal, if you boot, the framebuffer is initially efifb: [ 0.603716] efifb: probing for efifb [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1 [ 0.603736] efifb: scrolling: redraw [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 0.604462] Console: switching to colour frame buffer device 100x37 [ 0.605829] fb0: EFI VGA frame buffer device This soon changes to bochs-drm about a second later: [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 0: 0xc000 -> 0xc0ff [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 2: 0xc1c8c000 -> 0xc1c8cfff [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100) [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA [ 0.939085] Console: switching to colour dummy device 80x25 [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5. [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000. [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB [ 0.942081] [TTM] Initializing pool allocator [ 0.942089] [TTM] Initializing DMA pool allocator [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 GB/10.0 GiB) [ 0.944019] [drm] Found EDID data blob. [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on minor 0 [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device [ 0.947712] Console: switching to colour frame buffer device 128x48 On bionic, the framebuffer never changes from efifb, since the bochs- drm kernel module is not built, and it is also present on the module banlist in /etc/modprobe.d/blacklist-framebuffer.conf bochs-drm needs to be enabled to be built in the kernel config, and removed from the module blacklist in kmod. [Testcase] Create a new QEMU/KVM virtual machine, I used virt-manager. Before you install the OS, check the box to modify settings before install. In the "Overview" tab, enable EFI by setting the firmware to "UEFI x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd". Set the video device to qxl while you install Bionic. Once the install is done, reboot, do a "apt update" and "apt upgrade", to ensure you have grub2 2.02-2ubuntu8.15 installed. Shut the VM down, and set the video device to VGA. Or VGA=std if you use the QEMU command line. Start the VM up, and the screen will be garbled. See attached picture. If you install my test packages, which are available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test Instructions to install (on a bionic system): 1) sudo add-apt-repository ppa:mruffell/sf272653-test 2) sudo apt-get update 3) sudo apt install linux-image-unsigned-4.15.0-96-generic linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod 4) sudo reboot 5) uname -rv
[Kernel-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module
I have verified that enabling the bochs-drm kernel module on bionic does not cause any regressions for PowerKVM machines when the video device is VGA=std. TLDR: See Screenshot: https://launchpadlibrarian.net/475658598/Screenshot%20from%202020-04-22%2015-14-13.png This is in response to the main cause of regression concern, LP #1378648, which got bochs-drm disabled in the first place, on yakkety. On Christian's advice, I created a ppc64el instance on Canonistack, with the m1.medium flavor and c8c120bd-3d55-4e2d-8cc5-93039a62524f image (ubuntu/ubuntu-bionic-18.04-ppc64el-server-20200407-disk1.img). >From there, I installed the KVM packages and a xfce4 desktop, and got xrdp working. I then installed virt-manager. I modprobed the kvm_pr kernel module on my instance to enable nested kvm on ppc64el. >From there, I installed Ubuntu 18.04.4 Server ppc64el, using virt- manager. The "Machine Type" was pseries-2.12, and the Video Model was set to "VGA" [1]. [1]: https://launchpadlibrarian.net/475658622/Screenshot%20from%202020-04-22%2015-14-04.png Upon booting, the system was using the Open Firmware frame buffer: [0.888072] Using unsupported 800x600 vga at 20008100, depth=32, pitch=3200 [0.890480] Console: switching to colour frame buffer device 100x37 [0.892181] fb0: Open Firmware frame buffer device on /pci@8002000/vga@6 $ cat /proc/fb 0 OFfb vga Which is what LP #1378648 wanted. I then enabled my ppa where my test packages were built: https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test and installed new kmod and 4.15.0-96-generic test builds with bochs-drm enabled in the kernel config, and removed from the kmod blacklist. I then rebooted, and found that system boots successfully, and does not get hung up at the bug in LP #1378648, indicating that it has been fixed before 4.15. I checked "lsmod" and bochs-drm has been loaded, and looking at dmesg, initially the Open Firmware frame buffer device is used, and later in the boot, bochs-drm is loaded, and takes over the frame buffer. See screenshot [2] for proof that bochs-drm is running and functions correctly in virt-manager. [2]: https://launchpadlibrarian.net/475658598/Screenshot%20from%202020-04-22%2015-14-13.png A complete dmesg from this boot can be found here [3]. [3] https://paste.ubuntu.com/p/Q8V7fKnRzz/ Interesting parts: [0.893046] Using unsupported 800x600 vga at 20008100, depth=32, pitch=3200 [0.895482] Console: switching to colour frame buffer device 100x37 [0.897270] fb0: Open Firmware frame buffer device on /pci@8002000/vga@6 ... [2.041835] checking generic (20008100 1d4c00) vs hw (20008100 100) [2.041836] fb: switching to bochsdrmfb from OFfb vga [2.042568] Console: switching to colour dummy device 80x25 [2.045581] [drm] Found bochs VGA, ID 0xb0c5. [2.046100] [drm] Framebuffer size 16384 kB @ 0x20008100, mmio @ 0x20008200. [2.058141] [TTM] Zone kernel: Available graphics memory: 504512 kiB [2.058883] [TTM] Initializing pool allocator [2.059372] [TTM] Initializing DMA pool allocator [2.074890] Console: switching to colour frame buffer device 128x48 [2.089805] bochs-drm :00:06.0: fb0: bochsdrmfb frame buffer device [2.090549] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:06.0 on minor 0 $ cat /proc/fb 0 bochsdrmfb With good dmesg outputs, and positive test results in virt-manager, I am happy to say that enabling bochs-drm will not cause any regressions on ppc64el, and with that, I hope it satisfies your request for testing. -- 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/1872863 Title: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device, as the efifb driver yields an unreadable garbled screen. See the attached image. The correct framebuffer driver to use in this situation is bochs-drm, and modprobing it from a HWE kernel fixes the issues. bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in LP #1378648 due to bochs-drm causing problems in a PowerKVM machine. This problem appears to be fixed now, and bochs-drm has been re-enabled for Disco and up, in LP #1795857 and has been proven safe. This has also come up again in LP #1823152, as well as chatter on LP #1795857 to get this enabled on Bionic. The
[Kernel-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module
Attached is screenshot proof that bochs-drm functions correctly on 4.15.0-96-generic ppc64el, and does not cause any regressions when bochs-drm is enabled on ppc64el. ** Attachment added: "bochs-drm functions correctly on ppc64el" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872863/+attachment/5357795/+files/Screenshot%20from%202020-04-22%2015-14-13.png -- 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/1872863 Title: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device, as the efifb driver yields an unreadable garbled screen. See the attached image. The correct framebuffer driver to use in this situation is bochs-drm, and modprobing it from a HWE kernel fixes the issues. bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in LP #1378648 due to bochs-drm causing problems in a PowerKVM machine. This problem appears to be fixed now, and bochs-drm has been re-enabled for Disco and up, in LP #1795857 and has been proven safe. This has also come up again in LP #1823152, as well as chatter on LP #1795857 to get this enabled on Bionic. The customer which is experiencing this issue cannot switch to VGA=qxl as a workaround, and must use VGA=std, hence I suggest we re-enable bochs-drm for Bionic. [Fix] I noticed on Focal, if you boot, the framebuffer is initially efifb: [ 0.603716] efifb: probing for efifb [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1 [ 0.603736] efifb: scrolling: redraw [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 0.604462] Console: switching to colour frame buffer device 100x37 [ 0.605829] fb0: EFI VGA frame buffer device This soon changes to bochs-drm about a second later: [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 0: 0xc000 -> 0xc0ff [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 2: 0xc1c8c000 -> 0xc1c8cfff [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100) [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA [ 0.939085] Console: switching to colour dummy device 80x25 [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5. [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000. [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB [ 0.942081] [TTM] Initializing pool allocator [ 0.942089] [TTM] Initializing DMA pool allocator [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 GB/10.0 GiB) [ 0.944019] [drm] Found EDID data blob. [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on minor 0 [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device [ 0.947712] Console: switching to colour frame buffer device 128x48 On bionic, the framebuffer never changes from efifb, since the bochs- drm kernel module is not built, and it is also present on the module banlist in /etc/modprobe.d/blacklist-framebuffer.conf bochs-drm needs to be enabled to be built in the kernel config, and removed from the module blacklist in kmod. [Testcase] Create a new QEMU/KVM virtual machine, I used virt-manager. Before you install the OS, check the box to modify settings before install. In the "Overview" tab, enable EFI by setting the firmware to "UEFI x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd". Set the video device to qxl while you install Bionic. Once the install is done, reboot, do a "apt update" and "apt upgrade", to ensure you have grub2 2.02-2ubuntu8.15 installed. Shut the VM down, and set the video device to VGA. Or VGA=std if you use the QEMU command line. Start the VM up, and the screen will be garbled. See attached picture. If you install my test packages, which are available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test Instructions to install (on a bionic system): 1) sudo add-apt-repository ppa:mruffell/sf272653-test 2) sudo apt-get update 3) sudo apt install linux-image-unsigned-4.15.0-96-generic linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic
[Kernel-packages] [Bug 1874093] Re: Xenial update: 4.4.219 upstream stable release
Please note that the following patches have been skipped as they were already
applied to xenial/linux:
* slcan: Don't transmit uninitialized stack data in padding
* xen-netfront: Fix mismatched rtnl_unlock
* xen-netfront: Update features after registering netdev
The following patch needed some context adjustment:
* l2tp: fix duplicate session creation
All the other patches applied cleanly.
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ 4.4.219 upstream stable release
+ from git://git.kernel.org/
-4.4.219 upstream stable release
-from git://git.kernel.org/
+ The following patches from the 4.4.219 stable release shall be applied:
+ * drm/bochs: downgrade pci_request_region failure from error to warning
+ * ipv4: fix a RCU-list lock in fib_triestat_seq_show
+ * net, ip_tunnel: fix interface lookup with no key
+ * sctp: fix possibly using a bad saddr with a given dst
+ * l2tp: Correctly return -EBADF from pppol2tp_getname.
+ * net: l2tp: Make l2tp_ip6 namespace aware
+ * l2tp: fix race in l2tp_recv_common()
+ * l2tp: ensure session can't get removed during pppol2tp_session_ioctl()
+ * l2tp: fix duplicate session creation
+ * l2tp: Refactor the codes with existing macros instead of literal number
+ * l2tp: ensure sessions are freed after their PPPOL2TP socket
+ * l2tp: fix race between l2tp_session_delete() and l2tp_tunnel_closeall()
+ * usb: gadget: uac2: Drop unused device qualifier descriptor
+ * usb: gadget: printer: Drop unused device qualifier descriptor
+ * padata: always acquire cpu_hotplug_lock before pinst->lock
+ * mm: mempolicy: require at least one nodeid for MPOL_PREFERRED
+ * net: stmmac: dwmac1000: fix out-of-bounds mac address reg setting
+ * slcan: Don't transmit uninitialized stack data in padding
+ * random: always use batched entropy for get_random_u{32,64}
+ * tools/accounting/getdelays.c: fix netlink attribute length
+ * power: supply: axp288_charger: Fix unchecked return value
+ * xen-netfront: Fix mismatched rtnl_unlock
+ * xen-netfront: Update features after registering netdev
+ * ASoC: jz4740-i2s: Fix divider written at incorrect offset in register
+ * IB/hfi1: Call kobject_put() when kobject_init_and_add() fails
+ * Bluetooth: RFCOMM: fix ODEBUG bug in rfcomm_dev_ioctl
+ * RDMA/cm: Update num_paths in cma_resolve_iboe_route error flow
+ * clk: qcom: rcg: Return failure for RCG update
+ * drm_dp_mst_topology: fix broken drm_dp_sideband_parse_remote_dpcd_read()
+ * Linux 4.4.219
--
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/1874093
Title:
Xenial update: 4.4.219 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
New
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
4.4.219 upstream stable release
from git://git.kernel.org/
The following patches from the 4.4.219 stable release shall be applied:
* drm/bochs: downgrade pci_request_region failure from error to warning
* ipv4: fix a RCU-list lock in fib_triestat_seq_show
* net, ip_tunnel: fix interface lookup with no key
* sctp: fix possibly using a bad saddr with a given dst
* l2tp: Correctly return -EBADF from pppol2tp_getname.
* net: l2tp: Make l2tp_ip6 namespace aware
* l2tp: fix race in l2tp_recv_common()
* l2tp: ensure session can't get removed during pppol2tp_session_ioctl()
* l2tp: fix duplicate session creation
* l2tp: Refactor the codes with existing macros instead of literal number
* l2tp: ensure sessions are freed after their PPPOL2TP socket
* l2tp: fix
[Kernel-packages] [Bug 1865406] Re: Add support to test 5.0 Bionic kernel
** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865406 Title: Add support to test 5.0 Bionic kernel Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: For Bionic-5.0 hwe kernel, the requested meta package "linux-generic- hwe-18.04-5.0" from the test request is not available: sudo DEBIAN_FRONTEND=noninteractive UCF_FORCE_CONFFNEW=1 apt-get install --yes linux-generic-hwe-18.04-5.0 ShellError Raised Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package linux-generic-hwe-18.04-5.0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-76-generic 4.15.0-76.86 ProcVersionSignature: User Name 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 2 03:09 seq crw-rw 1 root audio 116, 33 Mar 2 03:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Mar 2 03:12:05 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-76-generic N/A linux-backports-modules-4.15.0-76-generic N/A linux-firmware 1.173.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
I created a Ubuntu 19.10 VM via "Quick Create..." and still can not reproduce the long delay of > 1 minute: the VM can boot up to the Xorg GUI desktop in 26 seconds. My Windows 10 has the same version info: Version 1909 (OS Build 18363.778). At the grub screen, can you press 'e' and, manually edit the kernel parameter: please remove the "quiet splash $vt_handoff" and add "ignore_loglevel sysrq_always_enabled". You may want to enable the serial console logging by adding the kernel parameter "console=ttyS0", and attach putty (Run as Administrator) to the named pipe \\.\pipe\debug_slow_vm, assuming you configure the VM serial console by "Set-VMComPort -VMName your_vm_name -number 1 -path \\.\pipe\debug_slow_vm"). This way, you should get more messages on the VM serial console when the VM boots up. When you see the long delay, you can press SysRQ+w (i.e. the Right Alt + SysRq + w) to show the blocked processes, if any. This may provide more info about the long delay. BTW, here I assume your have a keyboard that has the SysRq key. :-) It looks systemd can be configured to use "--log-level=debug --default- standard-output=kmsg --default-standard-error=kmsg", which may provide more info as well, if we check 'dmesg' and/or the VM serial console. -- 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/1848534 Title: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: AFter upgrade system shows graphic artefacts for a moment and then text cursor for about minute (it looks like hanged) and then starts. In 19.04 startup required 1 or 2 seconds. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 17:42:27 2019 InstallationDate: Installed on 2019-07-04 (104 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeLspcitxt: VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InstallationDate: Installed on 2019-07-04 (105 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: xorg-server (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash video=hyperv_fb:1900x900 elevator=noop vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 RfKill: Tags: eoan ubuntu Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual
[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
It looks #48 shows some service is causing the long delay -- can you try 'systemctl list-jobs' to see active jobs, as the "Hint" says? :-) -- 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/1848534 Title: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: AFter upgrade system shows graphic artefacts for a moment and then text cursor for about minute (it looks like hanged) and then starts. In 19.04 startup required 1 or 2 seconds. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 17:42:27 2019 InstallationDate: Installed on 2019-07-04 (104 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeLspcitxt: VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InstallationDate: Installed on 2019-07-04 (105 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: xorg-server (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash video=hyperv_fb:1900x900 elevator=noop vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 RfKill: Tags: eoan ubuntu Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1718761] Re: It's not possible to use OverlayFS (mount -t overlay) to stack directories on a ZFS volume
I ran into this exactly as smoser described using using overlay in a
container that is backed by zfs via lxd. I believe this will become
more prevalent as people start to use zfs root with Focal 20.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1718761
Title:
It's not possible to use OverlayFS (mount -t overlay) to stack
directories on a ZFS volume
Status in zfs-linux package in Ubuntu:
Confirmed
Bug description:
-- Configuration
# echo -e $(grep VERSION= /etc/os-release)\\nSIGNATURE=\"$(cat
/proc/version_signature)\"
VERSION="16.04.3 LTS (Xenial Xerus)"
SIGNATURE="Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17"
# dpkg --list | grep zfs
ii libzfs2linux0.6.5.6-0ubuntu18
ii zfs-doc 0.6.5.6-0ubuntu18
ii zfs-initramfs 0.6.5.6-0ubuntu18
ii zfs-zed 0.6.5.6-0ubuntu18
ii zfsutils-linux 0.6.5.6-0ubuntu18
-- Fault: Creating an overlay of multiple directories on a ZFS volume
does not work
# df /var/tmp
Filesystem Type 1K-blocks Used Available Use% Mounted on
tank07/var/tmp zfs 129916288 128 129916160 1% /var/tmp
# mkdir /var/tmp/{lower,middle,upper,workdir,overlay}
# mount -t overlay overlay
-olowerdir=/var/tmp/middle:/var/tmp/lower,upperdir=/var/tmp/upper,workdir=/var/tmp/workdir
/var/tmp/overlay
mount: wrong fs type, bad option, bad superblock on overlay,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
# dmesg|tail -1
[276328.438284] overlayfs: filesystem on '/var/tmp/upper' not supported as
upperdir
-- Control test 1: Creating an overlay of multiple directories on
another filesystem works
# df /tmp
Filesystem Type 1K-blocks Used Available Use% Mounted on
tmpfs tmpfs 1048576 133492915084 13% /tmp
# mkdir /tmp/{lower,middle,upper,workdir,overlay}
# mount -t overlay overlay
-olowerdir=/tmp/middle:/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/workdir
/tmp/overlay
# mount | grep overlay
overlay on /tmp/overlay type overlay
(rw,relatime,lowerdir=/tmp/middle:/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/workdir)
-- Control test 2: Creating an overlay using AuFS works on ZFS volume
and elsewhere
# mount -t aufs -obr=/tmp/lower:/tmp/middle:/tmp/upper:/tmp/workdir none
/tmp/overlay
# mount -t aufs
-obr=/var/tmp/lower:/var/tmp/middle:/var/tmp/upper:/var/tmp/workdir none
/var/tmp/overlay
# mount | grep aufs
none on /var/tmp/overlay type aufs (rw,relatime,si=9ead1ecae778b250)
none on /tmp/overlay type aufs (rw,relatime,si=9ead1ec9257d1250)
-- Remark
While the use of AuFS can be used as a workaround in the above scenario, AuFS
in turn will not work with [fuse.]glusterfs mounts (this has been documented
elsewhere). Given that OverlayFS is part of the (upstream) kernel and Ubuntu
now officially supports ZFS, the above should be fixed.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 18 16:12 seq
crw-rw 1 root audio 116, 33 Sep 18 16:12 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
Lspci: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: Red Hat KVM
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine:
BOOT_IMAGE=/ROOT/ubuntu1604@/boot/vmlinuz-4.10.0-35-generic
root=ZFS=tank07/ROOT/ubuntu1604 ro
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
RelatedPackageVersions:
linux-restricted-modules-4.10.0-35-generic N/A
linux-backports-modules-4.10.0-35-generic N/A
linux-firmware 1.157.12
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial
Uname: Linux 4.10.0-35-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.9.1-5.el7_3.3
dmi.chassis.type: 1
dmi.chassis.vendor: Red Hat
dmi.chassis.version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.9.1-5.el7_3.3:bd04/01/2014:svnRedHat:pnKVM:pvrRHEL7.3.0PC(i440FX+PIIX,1996):cvnRedHat:ct1:cvrRHEL7.3.0PC(i440FX+PIIX,1996):
dmi.product.name: KVM
dmi.product.version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
dmi.sys.vendor: Red Hat
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1
[Kernel-packages] [Bug 1873965] Re: booting into recovery mode hangs under 20.04
I have been able to eliminate the focal 5.4.0-26-generic kernel packages as the origin of this bug. Manually installing those onto an installation of Ubuntu 19.10, produced a fully functional boot. More importantly the recovery mode boot from grub worked fine. So the problem under 20.04 would appear to be something outside of the kernel itself. -- 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/1873965 Title: booting into recovery mode hangs under 20.04 Status in linux-meta package in Ubuntu: New Bug description: On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery mode from grub hangs on loading of the ramdisk with the Recovery Menu dialog never appearing. This problem doesn't exist for a fresh install of Ubuntu 18.04 updated to the current package updates. In that case, the Recovery Menu appears as expected. This bug in Ubuntu 20.04 was reproduced for both an existing Ubuntu 19.10 installation dist-upgraded to Ubuntu 20.04 as well as for a fresh install of Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Ok, fixed the bug tasks and re-opened the bug as we still need this kernel to get signed. ** Changed in: linux-kvm (Ubuntu) Status: Fix Released => Triaged ** Changed in: cloud-images Assignee: Roufique Hossain (roufique) => (unassigned) ** Changed in: linux-kvm (Ubuntu) Assignee: Roufique Hossain (roufique) => (unassigned) ** Changed in: cloud-bl-tutorials Status: Confirmed => Invalid ** Changed in: cloud-bl-tutorials Status: Invalid => New ** Changed in: cloud-bl-tutorials Remote watch: Email to roufique@rtat # => None ** Project changed: cloud-bl-tutorials => linux (Ubuntu) ** No longer affects: linux (Ubuntu) ** Changed in: cloud-images Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 -
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Merge proposal linked: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+merge/382712 -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed-5.4 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Merge proposal unlinked: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+merge/382712 -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed-5.4 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
This bug may also be affecting focal-server-cloudimg builds at:
https://cloud-images.ubuntu.com/focal/.
See: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1874147
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in grub2 package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in grub2 package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-azure (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in grub2 package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Hmm, actually, CONFIG_EFI_STUB is the one we were missing and I'm not seeing that in your VM either, which makes me wonder how it was booted in the first place :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs Status in Cloud-Bio-Linux Tutorials: Confirmed Status in cloud-images: Confirmed Status in linux-kvm package in Ubuntu: Fix Released Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 3FBEEA98 0047, LDTR - IDTR - 3F2D8018
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Thanks Louis, so our testing may in fact have been accurate and things regressed afterwards :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs Status in Cloud-Bio-Linux Tutorials: Confirmed Status in cloud-images: Confirmed Status in linux-kvm package in Ubuntu: Fix Released Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 3FBEEA98 0047, LDTR - IDTR - 3F2D8018 0FFF, TR - FXSAVE_STATE - 3FF1C290
[Kernel-packages] [Bug 1873965] Re: booting into recovery mode hangs under 20.04
This problem doesn't exist for current Ubuntu 19.10 under its 5.3.0-46-generic kernel. The recovery mode boots fine on the same hardware. -- 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/1873965 Title: booting into recovery mode hangs under 20.04 Status in linux-meta package in Ubuntu: New Bug description: On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery mode from grub hangs on loading of the ramdisk with the Recovery Menu dialog never appearing. This problem doesn't exist for a fresh install of Ubuntu 18.04 updated to the current package updates. In that case, the Recovery Menu appears as expected. This bug in Ubuntu 20.04 was reproduced for both an existing Ubuntu 19.10 installation dist-upgraded to Ubuntu 20.04 as well as for a fresh install of Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Saw the same hanging issues constantly with IntelliJ Idea using 5.3.0-46. Rolling back to 5.3.0-45 resolves the freezing for now. Came here from: https://youtrack.jetbrains.com/issue/JBR-2269 -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor:
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
@MasterCATZ, please check this with the 20.04 5.4 kernel. If it's still an issue could you please file a separate kernel bug for your corruption issue? ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. The exlcusion range limit register needs to contain the base-address of the last page that is part of the range, as bits 0-11 of this register are treated as 0xfff by the hardware for comparisons. So correctly set the exclusion range in the hardware to the last page which is _in_ the range. [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly These can be picked from my branches here: Bionic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic 1823037-amd_iommu-cherrypick b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range in iova-domain ee4a87e6b7fe7e039c1f02c50c53da63e4270732 iommu/amd: Set exclusion range correctly Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic 1823037-amd_iommu-cherrypick 0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range in iova-domain fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range correctly Disco: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco 1823037-amd_iommu-cherrypick 6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range correctly Note Disco only required f1cd47fe12 as the first patch was already picked in LP: #1830934 Not necessary for Eoan as these are already upstream in 5.2-rc1 [Regression Risk] Low,this adds memory protection to the driver and has already been applied upstream and tested by Dell for 24 hours with no failures noted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
This bug was fixed in the package ubiquity - 20.04.15 --- ubiquity (20.04.15) focal; urgency=medium [ Dimitri John Ledkov ] * check-kernels: install the right nvidia modules for the OEM kernel. (LP: #1873867) [ Iain Lane ] * language, partman, prepare: Factor out sensible-browser launching and use it (LP: #1874070) -- Dimitri John Ledkov Tue, 21 Apr 2020 16:07:58 +0100 ** Changed in: ubiquity (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in linux source package in Focal: Incomplete Status in nvidia-graphics-drivers-440 source package in Focal: Fix Released Status in ubiquity source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874124] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1874124 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu Eoan) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874124 Title: Add hw timestamps to received skbs in peak_canfd Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw timestamps were added to received messages in the peak_canfd driver. Backport the patch so users of our kernels can make use of the timestamps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874122] Re: Add Mute LED support for an HP Pavilion x360 Convertible 14-cd0xxx
** Description changed: Mute LED isn't on after the audio output is muted. + + Others: + https://bugs.launchpad.net/bugs/1871090 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: caravena 1849 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: caravena 1849 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 14:24:52 2020 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: - lono wireless extensions. - - enx000ec6c82c3f no wireless extensions. + lono wireless extensions. + + enx000ec6c82c3f no wireless extensions. MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-26-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-26-generic N/A - linux-backports-modules-5.4.0-26-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-26-generic N/A + linux-backports-modules-5.4.0-26-generic N/A + linux-firmware1.187 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2018-12-02 (505 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP -- 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/1874122 Title: Add Mute LED support for an HP Pavilion x360 Convertible 14-cd0xxx Status in linux package in Ubuntu: Confirmed Bug description: Mute LED isn't on after the audio output is muted. Others: https://bugs.launchpad.net/bugs/1871090 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1849 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 14:24:52 2020 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. enx000ec6c82c3f no wireless extensions. MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-26-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2018-12-02 (505 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version:
[Kernel-packages] [Bug 1874057] Re: [UBUNTU 20.04] s390x/pci: do not allow to create more pci functions than configured via CONFIG_PCI_NR_FUNCTIONS
The mentioned commit from 5.7 does not simply apply to focal master-
next:
cherry-pick says:
Auto-merging arch/s390/pci/pci.c
CONFLICT (content): Merge conflict in arch/s390/pci/pci.c
Auto-merging arch/s390/include/asm/pci.h
warning: inexact rename detection was skipped due to too many files.
warning: you may want to set your merge.renamelimit variable to at least 2342
and retry the command.
error: could not apply 969ae01bab2f... s390/pci: Fix zpci_alloc_domain() over
allocation
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add ' or 'git rm '
hint: and commit the result with 'git commit'
with status:
On branch master-next
Your branch is ahead of 'origin/master-next' by 2 commits.
(use "git push" to publish your local commits)
You are currently cherry-picking commit 969ae01bab2f.
(fix conflicts and run "git cherry-pick --continue")
(use "git cherry-pick --skip" to skip this patch)
(use "git cherry-pick --abort" to cancel the cherry-pick operation)
Changes to be committed:
modified: arch/s390/include/asm/pci.h
Unmerged paths:
(use "git add ..." to mark resolution)
both modified: arch/s390/pci/pci.c
and the git diff is:
diff --cc arch/s390/pci/pci.c
index 6105b1b6e49b,2b90a90aa81d..
--- a/arch/s390/pci/pci.c
+++ b/arch/s390/pci/pci.c
@@@ -39,11 -40,12 +39,12 @@@
static LIST_HEAD(zpci_list);
static DEFINE_SPINLOCK(zpci_list_lock);
- static DECLARE_BITMAP(zpci_domain, ZPCI_NR_DEVICES);
+ static DECLARE_BITMAP(zpci_domain, ZPCI_DOMAIN_BITMAP_SIZE);
static DEFINE_SPINLOCK(zpci_domain_lock);
+ static unsigned int zpci_num_domains_allocated;
#define ZPCI_IOMAP_ENTRIES\
- min(((unsigned long) ZPCI_NR_DEVICES * PCI_STD_NUM_BARS / 2), \
+ min(((unsigned long) ZPCI_NR_DEVICES * PCI_BAR_COUNT / 2), \
ZPCI_IOMAP_MAX_ENTRIES)
static DEFINE_SPINLOCK(zpci_iomap_lock);
@@@ -606,59 -608,22 +607,63 @@@ void pcibios_disable_device(struct pci_
zpci_debug_exit_device(zdev);
}
+#ifdef CONFIG_HIBERNATE_CALLBACKS
+static int zpci_restore(struct device *dev)
+{
+ struct pci_dev *pdev = to_pci_dev(dev);
+ struct zpci_dev *zdev = to_zpci(pdev);
+ int ret = 0;
+
+ if (zdev->state != ZPCI_FN_STATE_ONLINE)
+ goto out;
+
+ ret = clp_enable_fh(zdev, ZPCI_NR_DMA_SPACES);
+ if (ret)
+ goto out;
+
+ zpci_map_resources(pdev);
+ zpci_register_ioat(zdev, 0, zdev->start_dma, zdev->end_dma,
+ (u64) zdev->dma_table);
+
+out:
+ return ret;
+}
+
+static int zpci_freeze(struct device *dev)
+{
+ struct pci_dev *pdev = to_pci_dev(dev);
+ struct zpci_dev *zdev = to_zpci(pdev);
+
+ if (zdev->state != ZPCI_FN_STATE_ONLINE)
+ return 0;
+
+ zpci_unregister_ioat(zdev, 0);
+ zpci_unmap_resources(pdev);
+ return clp_disable_fh(zdev);
+}
+
+struct dev_pm_ops pcibios_pm_ops = {
+ .thaw_noirq = zpci_restore,
+ .freeze_noirq = zpci_freeze,
+ .restore_noirq = zpci_restore,
+ .poweroff_noirq = zpci_freeze,
+};
+#endif /* CONFIG_HIBERNATE_CALLBACKS */
+
static int zpci_alloc_domain(struct zpci_dev *zdev)
{
+ spin_lock(_domain_lock);
+ if (zpci_num_domains_allocated > (ZPCI_NR_DEVICES - 1)) {
+ spin_unlock(_domain_lock);
+ pr_err("Adding PCI function %08x failed because the configured
limit of %d is reached\n",
+ zdev->fid, ZPCI_NR_DEVICES);
+ return -ENOSPC;
+ }
+
if (zpci_unique_uid) {
zdev->domain = (u16) zdev->uid;
- if (zdev->domain >= ZPCI_NR_DEVICES)
- return 0;
-
- spin_lock(_domain_lock);
if (test_bit(zdev->domain, zpci_domain)) {
spin_unlock(_domain_lock);
- pr_err("Adding PCI function %08x failed because domain
%04x is already assigned\n",
- zdev->fid, zdev->domain);
return -EEXIST;
}
set_bit(zdev->domain, zpci_domain);
@@@ -665,14 -631,14 +671,21 @@@
spin_unlock(_domain_lock);
return 0;
}
-
- spin_lock(_domain_lock);
+ /*
+* We can always auto allocate domains below ZPCI_NR_DEVICES.
+* There is either a free domain or we have reached the maximum in
+* which case we would have bailed earlier.
+*/
zdev->domain = find_first_zero_bit(zpci_domain, ZPCI_NR_DEVICES);
++<<< HEAD
+ if (zdev->domain == ZPCI_NR_DEVICES) {
+ spin_unlock(_domain_lock);
+ return -ENOSPC;
+ }
++===
++>>> 969ae01bab2f... s390/pci: Fix zpci_alloc_domain() over allocation
set_bit(zdev->domain, zpci_domain);
+ zpci_num_domains_allocated++;
[Kernel-packages] [Bug 1871090] Re: Add Mute LED support for an HP laptop
@Kai-Heng Feng This feature did not work for me. Please see LP #1874122 -- 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/1871090 Title: Add Mute LED support for an HP laptop Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Mute LED isn't on after the audio output is muted. [Fix] Use HDA codec to control GPIO 4 to enable mute LED support. [Test] After applying the patch, mute LED works with mute hotkey or disable sound in Gnome Control Center. [Regression Potential] Low. This fix only target at one specific laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1871090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871090] Re: Add Mute LED support for an HP laptop
@Kai-Heng Feng This feature did not work for me. Please see LP: #1874122 -- 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/1871090 Title: Add Mute LED support for an HP laptop Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Mute LED isn't on after the audio output is muted. [Fix] Use HDA codec to control GPIO 4 to enable mute LED support. [Test] After applying the patch, mute LED works with mute hotkey or disable sound in Gnome Control Center. [Regression Potential] Low. This fix only target at one specific laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1871090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874124] [NEW] Add hw timestamps to received skbs in peak_canfd
Public bug reported: In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw timestamps were added to received messages in the peak_canfd driver. Backport the patch so users of our kernels can make use of the timestamps. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) 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/1874124 Title: Add hw timestamps to received skbs in peak_canfd Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Eoan: New Status in linux source package in Focal: New Bug description: In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw timestamps were added to received messages in the peak_canfd driver. Backport the patch so users of our kernels can make use of the timestamps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874122] Re: Add Mute LED support for an HP Pavilion x360 Convertible 14-cd0xxx
** Summary changed: - Add Mute LED support for an HP laptop x360 pavilion + Add Mute LED support for an HP Pavilion x360 Convertible 14-cd0xxx -- 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/1874122 Title: Add Mute LED support for an HP Pavilion x360 Convertible 14-cd0xxx Status in linux package in Ubuntu: Confirmed Bug description: Mute LED isn't on after the audio output is muted. Others: https://bugs.launchpad.net/bugs/1871090 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1849 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 14:24:52 2020 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. enx000ec6c82c3f no wireless extensions. MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-26-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2018-12-02 (505 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874122] [NEW] Add Mute LED support for an HP Pavilion x360 Convertible 14-cd0xxx
Public bug reported: Mute LED isn't on after the audio output is muted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1849 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 14:24:52 2020 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. enx000ec6c82c3f no wireless extensions. MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-26-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2018-12-02 (505 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874122 Title: Add Mute LED support for an HP Pavilion x360 Convertible 14-cd0xxx Status in linux package in Ubuntu: Confirmed Bug description: Mute LED isn't on after the audio output is muted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1849 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 14:24:52 2020 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. enx000ec6c82c3f no wireless extensions. MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-26-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2018-12-02 (505 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
udev source package last existed in precise. systemd-udevd is now shipped in src:systemd, please file all future udev bugs against systemd as a starting point. ** Package changed: udev (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => Balint Reczey (rbalint) -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed-5.4 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874122] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874122 Title: Add Mute LED support for an HP Pavilion x360 Convertible 14-cd0xxx Status in linux package in Ubuntu: Confirmed Bug description: Mute LED isn't on after the audio output is muted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1849 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 14:24:52 2020 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. enx000ec6c82c3f no wireless extensions. MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-26-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2018-12-02 (505 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874057] Re: [UBUNTU 20.04] s390x/pci: do not allow to create more pci functions than configured via CONFIG_PCI_NR_FUNCTIONS
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)
--
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/1874057
Title:
[UBUNTU 20.04] s390x/pci: do not allow to create more pci functions
than configured via CONFIG_PCI_NR_FUNCTIONS
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
PCI Functions with UIDs >128 are currently not accounted correctly in
the s390x/pci code. Furthermore, the code allows that more than
CONFIG_PCI_NR_FUNCTIONS are created. This can lead to issues with data
structures which were only allocated for CONFIG_PCI_NR_FUNCTIONS.
This has been fixed in the following upstream commit:
969ae01bab2fe938b4c8324836038b5ac1c78fac
("s390/pci: Fix zpci_alloc_domain() over allocation")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874057/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
This bug was fixed in the package nvidia-graphics-drivers-440 - 440.82+really.440.64-0ubuntu5 --- nvidia-graphics-drivers-440 (440.82+really.440.64-0ubuntu5) focal; urgency=medium * Reverse the order of the versions of nvidia-dkms-440 in the dependency list, so that apt will default to the real package instead of picking an lrm package at "random" which won't necessarily match the target kernel. LP: #1873867. -- Steve Langasek Tue, 21 Apr 2020 08:17:20 -0700 ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in linux source package in Focal: Incomplete Status in nvidia-graphics-drivers-440 source package in Focal: Fix Released Status in ubiquity source package in Focal: Confirmed Status in ubuntu-drivers-common source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871090] Re: Add Mute LED support for an HP laptop
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871090 Title: Add Mute LED support for an HP laptop Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Mute LED isn't on after the audio output is muted. [Fix] Use HDA codec to control GPIO 4 to enable mute LED support. [Test] After applying the patch, mute LED works with mute hotkey or disable sound in Gnome Control Center. [Regression Potential] Low. This fix only target at one specific laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1871090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871590] Re: Kernel 5.3 fails to boot on Inspiron 15 3000 running Ubuntu 18.04 since 2020-03-22 update
** Attachment added: "Boot output using requested arguments" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871590/+attachment/5357667/+files/video20200419_213816827.mp4 -- 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/1871590 Title: Kernel 5.3 fails to boot on Inspiron 15 3000 running Ubuntu 18.04 since 2020-03-22 update Status in linux package in Ubuntu: Incomplete Bug description: Hi, Here's update that broke boot on that Inspiron 15 3000: Start-Date: 2020-03-22 16:11:26 Commandline: aptdaemon role='role-commit-packages' sender=':1.89' Install: linux-image-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, automatic), linux-headers-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, autom atic), linux-modules-extra-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, automatic), linux-headers-5.3.0-42:amd64 (5.3.0-42.34~18.04.1, automat ic), linux-modules-5.3.0-42-generic:amd64 (5.3.0-42.34~18.04.1, automatic) Upgrade: linux-libc-dev:amd64 (4.15.0-88.88, 4.15.0-91.92), grub-common:amd64 (2.02-2ubuntu8.14, 2.02-2ubuntu8.15), libicu60:amd64 (60.2-3ubun tu3, 60.2-3ubuntu3.1), linux-headers-generic-hwe-18.04:amd64 (5.3.0.40.97, 5.3.0.42.99), grub2-common:amd64 (2.02-2ubuntu8.14, 2.02-2ubuntu8.1 5), skypeforlinux:amd64 (8.57.0.116, 8.58.0.93), apport:amd64 (2.20.9-0ubuntu7.11, 2.20.9-0ubuntu7.12), grub-efi-amd64-bin:amd64 (2.02-2ubuntu 8.14, 2.02-2ubuntu8.15), python3-apport:amd64 (2.20.9-0ubuntu7.11, 2.20.9-0ubuntu7.12), linux-image-generic-hwe-18.04:amd64 (5.3.0.40.97, 5.3. 0.42.99), grub-efi-amd64:amd64 (2.02-2ubuntu8.14, 2.02-2ubuntu8.15), apport-gtk:amd64 (2.20.9-0ubuntu7.11, 2.20.9-0ubuntu7.12), grub-efi-amd64 -signed:amd64 (1.93.15+2.02-2ubuntu8.14, 1.93.16+2.02-2ubuntu8.15), libsgutils2-2:amd64 (1.42-2ubuntu1.18.04.1, 1.42-2ubuntu1.18.04.2), python 3-problem-report:amd64 (2.20.9-0ubuntu7.11, 2.20.9-0ubuntu7.12) End-Date: 2020-03-22 16:12:50 Kernel 4.15 works fine though. None of 5.3.x releases managed to boot - it just hangs on loading initrd. Tried to reinstall grub, grub-efi; tried running update-grub, grub- insall, reinstalling 5.3 pacakges (from LiveCD), etc, but nothing helped. Ubuntu is installed on NVME, maybe it gives the problems? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1434 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-glk+X36 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-12 (372 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Inspiron 3582 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=deb0fd33-d5dc-4831-ac22-6990511c0550 ro mem_sleep_default=deep quiet splash ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-96-generic N/A linux-backports-modules-4.15.0-96-generic N/A linux-firmware 1.173.17 Tags: bionic Uname: Linux 4.15.0-96-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: Inspiron 3582 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd03/06/2019:svnDellInc.:pnInspiron3582:pvr1.2.1:rvnDellInc.:rnInspiron3582:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 3582 dmi.product.version: 1.2.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
For 6 months I have been using the raspberry pi kernel grafted onto the rest of Ubuntu to get V3D. It is a shame that 6 month later this is still not fixed. If you can supply a recipe for the building the official ubuntu kernel for the pi I would be willing to try and fix it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Triaged Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1860800] Re: Ubuntu 19.10 doesn't shutdown
Thank you again for your answer. I switched back to Linux Mint 19.3 Cinnamon having the same issue. Is there also a mainline kernel available for this distribution? leonard-linux On Apr 9 2020, at 8:49 am, Kai-Heng Feng wrote: > Please test latest mainline kernel: > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/ If mainline kernel > doesn't work, usually there are some driver prevent the system from shutting > down. Unload driver one by one to see which one is the culprit. -- You > received this bug notification because you are subscribed to the bug report. > https://bugs.launchpad.net/bugs/1860800 Title: Ubuntu 19.10 doesn't shutdown > Status in linux package in Ubuntu: Confirmed Bug description: Hello guys, I > can't shutdown Ubuntu 19.10. When I try, the shutdown screen appears. The > first two dots below the ubuntu logo, turn orange and then it freezes. Reboot > works fine. The debug-shell is no use, because at the freeze point I can't > type in commands. When I press ESC to see what's going on during shutdown, > the last message to appear ist "[Some weird number] reboot: power down. Last > time I pressed ESC during shutdown the "weird number" was 85.270119. I also > tried to shutdown with the terminal commands "sudo shut down now", "sudo shutdown -P now", "sudo shutdown -h now", "poweroff" and "sudo poweroff -f". All of them had the effect as describe above except the command "sudo poweroff -f". After I typed in the command, I authenticated and following messages appeared: "Powering off...". At this point it freezed. I could still see the desktop and every visible window, but I couldn't perform any actions; not even keyboard shortcuts worked. It also did not help to change 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"' in /etc/default/grub to 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"' and run "update-grub". Once the following command combo did work: "sudo swapoff -a && systemctl poweroff", but the I reinstalled Ubuntu and now it doesn't work any more. In the application "Additional Drivers" I selected the proprietary and tested driver of NVIDIA, but I can't to this for my WLAN-Card (correct word?), because the "Additional Drivers" says it's not working, but my WLAN works fine. I've got only Bluetooth problems. The displayed name of the WLAN-Card is: "Intel Corporation: Wireless 7260 (Dual Band Wireless-AC 7260)". I also tried to manually install a driver it didn't help. When I wake up the laptop, a black screen appears with some error messages, but only for a very short time so I can't make a photo of it. I tried once and the text was unreadable. I have the latest BIOS and my Computer model is MSI PX60 2QD. It doesn't work with Arch Linux either. Thanks for your help :) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: leonard 1724 F pulseaudio /dev/snd/controlC1: leonard 1724 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-18 (7 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. PX60 2QD NonfreeKernelModules: nvidia_modeset nvidia Packa ge: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=04df7493-393f-447e-bfb3-3dc43c2ee645 ro quiet splash acpi=force vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware 1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H6IMS.110 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H6 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi .modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H6IMS.110:bd11/03/2015:svnMicro-StarInternationalCo.,Ltd.:pnPX602QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H6:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: PX60 2QD dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860800/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1836742] Re: Please enable CONFIG_PMIC_OPREGION and it's components to resolve issues with enabling integrated display on some BayTrail/CherryTrail-based devices
Still issue in focal with current kernel from repo. ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836742 Title: Please enable CONFIG_PMIC_OPREGION and it's components to resolve issues with enabling integrated display on some BayTrail/CherryTrail- based devices Status in linux package in Ubuntu: Confirmed Bug description: Please enable CONFIG_PMIC_OPREGION and it's components (CONFIG_CRC_PMIC_OPREGION, CONFIG_XPOWER_PMIC_OPREGION, CONFIG_BXT_WC_PMIC_OPREGION, CONFIG_CHT_WC_PMIC_OPREGION, CONFIG_CHT_DC_TI_PMIC_OPREGION). On GPD Win 1 and GPD Pocket 1 this should allow to use integrated display when external display is connected. More details is here: https://github.com/torvalds/linux/commit/7b5618f4b834330a052958db934c3dffad4a15c2 https://github.com/torvalds/linux/commit/4e8052af858a6ea2cf656bdb6dbcf16dd87a39c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection
I can also confirm that kernel 5.4.0-26 solved the problem. Retested and all as should be. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863761] Re: CONFIG_HID_SENSOR_HUB=m makes keyboard unusable on Lenovo Yoga C630 WOS with -snapdragon kernel
** Changed in: linux (Ubuntu) Status: Expired => Confirmed ** Summary changed: - CONFIG_HID_SENSOR_HUB=m makes keyboard unusable on Lenovo Yoga C630 WOS with -snapdragon kernel + CONFIG_HID_SENSOR_HUB=m makes keyboard unusable on Lenovo Yoga C630 WOS -- 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/1863761 Title: CONFIG_HID_SENSOR_HUB=m makes keyboard unusable on Lenovo Yoga C630 WOS Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_HID_SENSOR_HUB=m makes keyboard unusable on Lenovo Yoga C630 WOS with -snapdragon kernel. More details is here: https://lists.linaro.org/pipermail/aarch64-laptops/2020-February/000163.html https://lists.linaro.org/pipermail/aarch64-laptops/2020-February/000164.html https://lists.linaro.org/pipermail/aarch64-laptops/2020-February/000165.html https://lists.linaro.org/pipermail/aarch64-laptops/2020-February/000166.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
As 5.5 is more stable on my Dell XPS 13 than 5.4 with Intel iGPU (i915)
I did the following one-liner to install the latest version of Linux Kernel 5.5
on Ubuntu 20.04
which curl >/dev/null 2>&1 || sudo apt-get install -qq -y curl; for
version in $(curl -sL https://kernel.ubuntu.com/~kernel-ppa/mainline/ |
tac | grep -Pom1 '(?<=")v5\.5\.[0-9]+/'); do for deb in $(curl -sL
https://kernel.ubuntu.com/~kernel-ppa/mainline/${version} | grep -Pom4
'(?<=")linux-(headers|image-
unsigned|modules)-5\.5\.[^"]+[0-9]+(-generic_5\.5\.|_5\.5\.)[^"]+.(amd64|all)\.deb');
do curl -sLo ${deb} https://kernel.ubuntu.com/~kernel-
ppa/mainline/${version}/${deb}; debs="${debs} ${deb}"; done; sudo dpkg
-i ${debs}; done
--
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/1868551
Title:
Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4)
i915_active_acquire
Status in linux package in Ubuntu:
Confirmed
Bug description:
uname -a
Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
Codename: focal
[ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040
[ 2556.956084] #PF: supervisor read access in kernel mode
[ 2556.956084] #PF: error_code(0x) - not-present page
[ 2556.956085] PGD 0 P4D 0
[ 2556.956088] Oops: [#1] SMP NOPTI
[ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic
#17-Ubuntu
[ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0
10/03/2019
[ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915]
[ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f
1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38
48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31
[ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286
[ 2556.956165] RAX: RBX: 983831d3e480 RCX:
[ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI:
0008
[ 2556.956167] RBP: ac17c13279e0 R08: R09:
98382d6b6520
[ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12:
983783475200
[ 2556.956169] R13: 0008 R14: 983783475200 R15:
98382d6b6400
[ 2556.956170] FS: 7f9031c28f00() GS:98383e50()
knlGS:
[ 2556.956171] CS: 0010 DS: ES: CR0: 80050033
[ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4:
003606e0
[ 2556.956173] Call Trace:
[ 2556.956199] i915_active_ref+0x24/0x200 [i915]
[ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915]
[ 2556.956245] eb_submit+0xff/0x440 [i915]
[ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915]
[ 2556.956271] ? sock_def_readable+0x40/0x70
[ 2556.956274] ? __kmalloc_node+0x205/0x320
[ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915]
[ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
[ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm]
[ 2556.956338] drm_ioctl+0x234/0x3d0 [drm]
[ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
[ 2556.956361] ? vfs_writev+0xc3/0xf0
[ 2556.956363] do_vfs_ioctl+0x407/0x670
[ 2556.956365] ? fput+0x13/0x15
[ 2556.956367] ? __sys_recvmsg+0x88/0xa0
[ 2556.956369] ksys_ioctl+0x67/0x90
[ 2556.956371] __x64_sys_ioctl+0x1a/0x20
[ 2556.956373] do_syscall_64+0x57/0x190
[ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 2556.956377] RIP: 0033:0x7f9032b3f68b
[ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48
[ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX:
0010
[ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX:
7f9032b3f68b
[ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI:
000d
[ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09:
[ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12:
7f9022a4f460
[ 2556.956384] R13: R14: 7ffee39a0090 R15:
000d
[ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE
xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat
typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6
nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables
iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda
[Kernel-packages] [Bug 1863939] Re: Linux 5.4.0-14 from focal repo does not boot on Lenovo Yoga C630 WOS, while Linux 5.4.0 from mainline PPA does boot
** 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/1863939 Title: Linux 5.4.0-14 from focal repo does not boot on Lenovo Yoga C630 WOS, while Linux 5.4.0 from mainline PPA does boot Status in linux package in Ubuntu: Confirmed Bug description: Hello! I found that both of generic and snapdragon kernels from focal repository (5.4.0-14-generic and 5.4.0-14-snapdragon was tested) does not boot on Lenovo Yoga C630 WOS. Boot process hang at "Loading device tree blob..." (which means I can not provide apport report, because I can not boot kernel from focal repository, and apport refuse to collect information with other kernels). At the same time snapdragon kernel from https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.4.20/ boot mostly fine (albeit with https://bugzilla.kernel.org/show_bug.cgi?id=204685 and https://bugs.launchpad.net/bugs/1863761 ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874113] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874113 Title: IPv6 not working Status in linux package in Ubuntu: Confirmed Bug description: IPv6 worked with 20.04 kernel 5.4.0-21-generic After upgrading it does not work. Not sure if it is kernel related or something else. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-25-generic 5.4.0-25.29 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-25-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip Date: Tue Apr 21 19:44:10 2020 InstallationDate: Installed on 2020-04-13 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: MSI MS-7885 ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=UUID=e798385b-96fa-4adf-9304-6f3a3a61a9b3 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99S SLI PLUS (MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd11/05/2014:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99SSLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7885 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863939] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1863939 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863939 Title: Linux 5.4.0-14 from focal repo does not boot on Lenovo Yoga C630 WOS, while Linux 5.4.0 from mainline PPA does boot Status in linux package in Ubuntu: Confirmed Bug description: Hello! I found that both of generic and snapdragon kernels from focal repository (5.4.0-14-generic and 5.4.0-14-snapdragon was tested) does not boot on Lenovo Yoga C630 WOS. Boot process hang at "Loading device tree blob..." (which means I can not provide apport report, because I can not boot kernel from focal repository, and apport refuse to collect information with other kernels). At the same time snapdragon kernel from https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.4.20/ boot mostly fine (albeit with https://bugzilla.kernel.org/show_bug.cgi?id=204685 and https://bugs.launchpad.net/bugs/1863761 ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Following up my question; we should see both events in all kernels. The first event is when the /dev/bcache0 is joined with a cache device, and emitts the CACHED_UUID value in the uevent; the UUID is the *backing device bcache metadata UUID* it is not related to the content contained within the backing device; this CACHED_UUID is symlinked at /dev/bcache /by-uuid Once /dev/bcache0 is created, blkid will scan the contents of /dev/bcache0 which contains an ext4 filesystem and the FS_UUID is symlinked at /dev/disk/by-uuid. CACHED_UUID != FS_UUID /dev/bcache/by-uuid != /dev/disk/by-uuid I speculate that udev has a bug where it's only looking at the basename of the symlink target and removing any other 'by-uuid' link against the device when it needs to account for the full path of the symlink since the bcache/by-uuid is different than the disk/by-uuid. -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed-5.4 package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863939] Re: Linux 5.4.0-14 from focal repo does not boot on Lenovo Yoga C630 WOS, while Linux 5.4.0 from mainline PPA does boot
See bug description. ** Changed in: linux (Ubuntu) Status: Expired => 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/1863939 Title: Linux 5.4.0-14 from focal repo does not boot on Lenovo Yoga C630 WOS, while Linux 5.4.0 from mainline PPA does boot Status in linux package in Ubuntu: Confirmed Bug description: Hello! I found that both of generic and snapdragon kernels from focal repository (5.4.0-14-generic and 5.4.0-14-snapdragon was tested) does not boot on Lenovo Yoga C630 WOS. Boot process hang at "Loading device tree blob..." (which means I can not provide apport report, because I can not boot kernel from focal repository, and apport refuse to collect information with other kernels). At the same time snapdragon kernel from https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.4.20/ boot mostly fine (albeit with https://bugzilla.kernel.org/show_bug.cgi?id=204685 and https://bugs.launchpad.net/bugs/1863761 ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874113] Re: IPv6 not working
Had to disable IPv6 by: sysctl -w net.ipv6.conf.all.disable_ipv6=1 To be able to upload bug report -- 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/1874113 Title: IPv6 not working Status in linux package in Ubuntu: New Bug description: IPv6 worked with 20.04 kernel 5.4.0-21-generic After upgrading it does not work. Not sure if it is kernel related or something else. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-25-generic 5.4.0-25.29 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-25-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip Date: Tue Apr 21 19:44:10 2020 InstallationDate: Installed on 2020-04-13 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: MSI MS-7885 ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=UUID=e798385b-96fa-4adf-9304-6f3a3a61a9b3 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99S SLI PLUS (MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd11/05/2014:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99SSLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7885 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874113] [NEW] IPv6 not working
Public bug reported: IPv6 worked with 20.04 kernel 5.4.0-21-generic After upgrading it does not work. Not sure if it is kernel related or something else. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-25-generic 5.4.0-25.29 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-25-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip Date: Tue Apr 21 19:44:10 2020 InstallationDate: Installed on 2020-04-13 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: MSI MS-7885 ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=UUID=e798385b-96fa-4adf-9304-6f3a3a61a9b3 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99S SLI PLUS (MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd11/05/2014:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99SSLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7885 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874113 Title: IPv6 not working Status in linux package in Ubuntu: New Bug description: IPv6 worked with 20.04 kernel 5.4.0-21-generic After upgrading it does not work. Not sure if it is kernel related or something else. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-25-generic 5.4.0-25.29 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-25-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip Date: Tue Apr 21 19:44:10 2020 InstallationDate: Installed on 2020-04-13 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: MSI MS-7885 ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=UUID=e798385b-96fa-4adf-9304-6f3a3a61a9b3 ro RelatedPackageVersions:
[Kernel-packages] [Bug 1871835] Re: [MIR] linux-raspi
Override component to main linux-raspi 5.4.0-1008.8 in focal: universe/devel -> main linux-buildinfo-5.4.0-1008-raspi 5.4.0-1008.8 in focal arm64: universe/kernel/optional/100% -> main linux-buildinfo-5.4.0-1008-raspi 5.4.0-1008.8 in focal armhf: universe/kernel/optional/100% -> main linux-headers-5.4.0-1008-raspi 5.4.0-1008.8 in focal arm64: universe/devel/optional/100% -> main linux-headers-5.4.0-1008-raspi 5.4.0-1008.8 in focal armhf: universe/devel/optional/100% -> main linux-image-5.4.0-1008-raspi 5.4.0-1008.8 in focal arm64: universe/kernel/optional/100% -> main linux-image-5.4.0-1008-raspi 5.4.0-1008.8 in focal armhf: universe/kernel/optional/100% -> main linux-modules-5.4.0-1008-raspi 5.4.0-1008.8 in focal arm64: universe/kernel/optional/100% -> main linux-modules-5.4.0-1008-raspi 5.4.0-1008.8 in focal armhf: universe/kernel/optional/100% -> main linux-raspi-headers-5.4.0-1008 5.4.0-1008.8 in focal arm64: universe/devel/optional/100% -> main linux-raspi-headers-5.4.0-1008 5.4.0-1008.8 in focal armhf: universe/devel/optional/100% -> main linux-raspi-tools-5.4.0-1008 5.4.0-1008.8 in focal arm64: universe/devel/optional/100% -> main linux-raspi-tools-5.4.0-1008 5.4.0-1008.8 in focal armhf: universe/devel/optional/100% -> main linux-tools-5.4.0-1008-raspi 5.4.0-1008.8 in focal arm64: universe/devel/optional/100% -> main linux-tools-5.4.0-1008-raspi 5.4.0-1008.8 in focal armhf: universe/devel/optional/100% -> main 15 publications overridden. ** Changed in: linux-raspi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1871835 Title: [MIR] linux-raspi Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Bug description: [Availability] The package is already in universe. [Rationale] The package is a core component on all supported Raspberry Pi images, both classic and core as it is responsible for pulling in the Raspberry Pi-specific kernel and headers. [Security] The raspi kernel is a derivative of the main/generic kernel (it's the same code-base with raspi specific patches and config changes). The kernel team track CVEs for the main kernel and do CVE respins of the Pi kernel in parallel with the main kernel (and all its other derivatives) if they think that a particular CVE affects the Pi kernel. They currently don't track Pi specific CVEs. [Quality assurance] There are no outstanding bugs which significantly affect the usability (i.e. our images boot successfully on all supported pi models), but there are high priority bugs open against our Pi kernel which we are actively working through (e.g. LP: #1857760). [Dependencies] There are no special dependencies compared to the main kernel package. [Standards Compliance] There are no differences in standards compliance to the main kernel package. [Maintenance] The package will be maintained by the kernel team. [Background information] As mentioned, this package is already used for all our pi images, so we are effectively already treating it as a package from main. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi/+bug/1871835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871835] Re: [MIR] linux-raspi
Override component to main linux-meta-raspi 5.4.0.1008.8 in focal: universe/devel -> main linux-headers-raspi 5.4.0.1008.8 in focal arm64: universe/kernel/optional/100% -> main linux-headers-raspi 5.4.0.1008.8 in focal armhf: universe/kernel/optional/100% -> main linux-headers-raspi2 5.4.0.1008.8 in focal arm64: universe/metapackages/optional/100% -> main linux-headers-raspi2 5.4.0.1008.8 in focal armhf: universe/metapackages/optional/100% -> main linux-image-raspi 5.4.0.1008.8 in focal arm64: universe/kernel/optional/100% -> main linux-image-raspi 5.4.0.1008.8 in focal armhf: universe/kernel/optional/100% -> main linux-image-raspi2 5.4.0.1008.8 in focal arm64: universe/metapackages/optional/100% -> main linux-image-raspi2 5.4.0.1008.8 in focal armhf: universe/metapackages/optional/100% -> main linux-raspi 5.4.0.1008.8 in focal arm64: main/kernel/optional/100% -> main linux-raspi 5.4.0.1008.8 in focal arm64: universe/kernel/optional/100% -> main linux-raspi 5.4.0.1008.8 in focal armhf: main/kernel/optional/100% -> main linux-raspi 5.4.0.1008.8 in focal armhf: universe/kernel/optional/100% -> main linux-raspi2 5.4.0.1008.8 in focal arm64: universe/metapackages/optional/100% -> main linux-raspi2 5.4.0.1008.8 in focal armhf: universe/metapackages/optional/100% -> main linux-tools-raspi 5.4.0.1008.8 in focal arm64: universe/kernel/optional/100% -> main linux-tools-raspi 5.4.0.1008.8 in focal armhf: universe/kernel/optional/100% -> main linux-tools-raspi2 5.4.0.1008.8 in focal arm64: universe/metapackages/optional/100% -> main linux-tools-raspi2 5.4.0.1008.8 in focal armhf: universe/metapackages/optional/100% -> main 17 publications overridden; 2 publications remained the same. ** Changed in: linux-meta-raspi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1871835 Title: [MIR] linux-raspi Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Bug description: [Availability] The package is already in universe. [Rationale] The package is a core component on all supported Raspberry Pi images, both classic and core as it is responsible for pulling in the Raspberry Pi-specific kernel and headers. [Security] The raspi kernel is a derivative of the main/generic kernel (it's the same code-base with raspi specific patches and config changes). The kernel team track CVEs for the main kernel and do CVE respins of the Pi kernel in parallel with the main kernel (and all its other derivatives) if they think that a particular CVE affects the Pi kernel. They currently don't track Pi specific CVEs. [Quality assurance] There are no outstanding bugs which significantly affect the usability (i.e. our images boot successfully on all supported pi models), but there are high priority bugs open against our Pi kernel which we are actively working through (e.g. LP: #1857760). [Dependencies] There are no special dependencies compared to the main kernel package. [Standards Compliance] There are no differences in standards compliance to the main kernel package. [Maintenance] The package will be maintained by the kernel team. [Background information] As mentioned, this package is already used for all our pi images, so we are effectively already treating it as a package from main. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi/+bug/1871835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection
confirm: kernel 5.4.0-26 solved the problem -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Same as Grzegorz Dabrowski: I can reproduce this bug by starting a call via zoom.us. It occurs very quickly and then sometimes calms down to an acceptable level. Attached /sys/class/drm/card0/error ** Attachment added: "Content of /sys/class/drm/card0/error" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+attachment/5357634/+files/sys-class-drm-card0-error.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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date:
[Kernel-packages] [Bug 1874111] [NEW] Focal update: v5.4.34 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.34 upstream stable release from git://git.kernel.org/ amd-xgbe: Use __napi_schedule() in BH context hsr: check protocol version in hsr_newlink() l2tp: Allow management of tunnels and session in user namespace net: dsa: mt7530: fix tagged frames pass-through in VLAN-unaware mode net: ipv4: devinet: Fix crash when add/del multicast IP with autojoin net: ipv6: do not consider routes via gateways for anycast address check net: phy: micrel: use genphy_read_status for KSZ9131 net: qrtr: send msgs from local of same id as broadcast net: revert default NAPI poll timeout to 2 jiffies net: tun: record RX queue in skb before do_xdp_generic() net: dsa: mt7530: move mt7623 settings out off the mt7530 net: ethernet: mediatek: move mt7623 settings out off the mt7530 net/mlx5: Fix frequent ioread PCI access during recovery net/mlx5e: Add missing release firmware call net/mlx5e: Fix nest_level for vlan pop action net/mlx5e: Fix pfnum in devlink port attribute net: stmmac: dwmac-sunxi: Provide TX and RX fifo sizes ovl: fix value of i_ino for lower hardlink corner case scsi: ufs: Fix ufshcd_hold() caused scheduling while atomic platform/chrome: cros_ec_rpmsg: Fix race with host event jbd2: improve comments about freeing data buffers whose page mapping is NULL acpi/nfit: improve bounds checking for 'func' perf report: Fix no branch type statistics report issue pwm: pca9685: Fix PWM/GPIO inter-operation ext4: fix incorrect group count in ext4_fill_super error message ext4: fix incorrect inodes per group in error message clk: at91: sam9x60: fix usb clock parents clk: at91: usb: use proper usbs_mask ARM: dts: imx7-colibri: fix muxing of usbc_det pin arm64: dts: librem5-devkit: add a vbus supply to usb0 usb: dwc3: gadget: Don't clear flags before transfer ended ASoC: Intel: mrfld: fix incorrect check on p->sink ASoC: Intel: mrfld: return error codes when an error occurs ALSA: hda/realtek - Enable the headset mic on Asus FX505DT ALSA: usb-audio: Filter error from connector kctl ops, too ALSA: usb-audio: Don't override ignore_ctl_error value from the map ALSA: usb-audio: Don't create jack controls for PCM terminals ALSA: usb-audio: Check mapping at creating connector controls, too arm64: vdso: don't free unallocated pages keys: Fix proc_keys_next to increase position index tracing: Fix the race between registering 'snapshot' event trigger and triggering 'snapshot' operation btrfs: check commit root generation in should_ignore_root nl80211: fix NL80211_ATTR_FTM_RESPONDER policy mac80211: fix race in ieee80211_register_hw() mac80211_hwsim: Use kstrndup() in place of kasprintf() net/mlx5e: Encapsulate updating netdev queues into a function net/mlx5e: Rename hw_modify to preactivate net/mlx5e: Use preactivate hook to set the indirection table drm/amd/powerplay: force the trim of the mclk dpm_levels if OD is enabled drm/amdgpu: fix the hw hang during perform system reboot and reset i2c: designware: platdrv: Remove DPM_FLAG_SMART_SUSPEND flag on BYT and CHT ext4: do not zeroout extents beyond i_disksize irqchip/ti-sci-inta: Fix processing of masked irqs x86/resctrl: Preserve CDP enable over CPU hotplug x86/resctrl: Fix invalid attempt at removing the default resource group scsi: target: remove boilerplate code scsi: target: fix hang when multiple threads try to destroy the same iscsi session x86/microcode/AMD: Increase microcode PATCH_MAX_SIZE Linux 5.4.34 UBUNTU: upstream stable to v5.4.34 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of
[Kernel-packages] [Bug 1851676] Re: dmidecode does not byte-swap for SMBIOS >= 2.6
Hey both, Was this experiment run with VMWare version 11 and higher? Also /sys/class/dmi/id/product_uuid and /sys/class/dmi/id/product_uuid should not match up if the problem is being exhibited. Cheers -- 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/1851676 Title: dmidecode does not byte-swap for SMBIOS >= 2.6 Status in dmidecode package in Ubuntu: Incomplete Bug description: Hi, On VMWare 6.5 and higher (HW version 13 and higher) when decoding /sys/class/dmi/id/product_serial dmidecode produces an output whereby the first 16 characters have been reversed in comparison to /sys/class/dmi/id/product_uuid. This manifests itself by breaking provisioning in Kubernetes and could cause other issues down the line. Other OS such as redhat have already patched this in their releases. A demonstration of the issue can be found in this pastebin: https://pastebin.canonical.com/p/qRfrpHXwGs/ VMWare Issue: https://kb.vmware.com/s/article/53609 Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1851676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862831] Re: hciattach on rpi4 times out on first attempt
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1862831 ** Tags added: iso-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1862831 Title: hciattach on rpi4 times out on first attempt Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Eoan: New Bug description: I've observed this in both armhf and arm64 on: 19.10.1-server 18.04.4-server core18 It does not seem to happen on rpi3, only on rpi4. If you want to use Bluetooth on rpi, one must first run: $ sudo hciattach /dev/ttyAMA0 bcm43xx 921600 noflow On RPI4, this results in a timeout on the first attempt. Reattempting it right after will work though, 100% of the times I've tried it. In the failed attempt, the output is: bcm43xx_init Initialization timed out. And the following is the only new message to show up in dmesg when this fails: [ 270.303691] uart-pl011 fe201000.serial: no DMA platform data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1862831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851676] Re: dmidecode does not byte-swap for SMBIOS >= 2.6
Hi Pedro, As Christian mentioned above, we tried to reproduce the issue on bionic but were not able to. Interestingly, when I was looking at the package we ship on bionic, I noticed that the patch you mentioned on comment #6 is already included on dmidecode 3.1. Actually, if you look at the upstream repository, you can verify that the patch has been there since version 2.10 (from 2008). Could you please provide a bit more information on how to reproduce the failure? Thanks! ** Changed in: dmidecode (Ubuntu) Status: New => Incomplete -- 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/1851676 Title: dmidecode does not byte-swap for SMBIOS >= 2.6 Status in dmidecode package in Ubuntu: Incomplete Bug description: Hi, On VMWare 6.5 and higher (HW version 13 and higher) when decoding /sys/class/dmi/id/product_serial dmidecode produces an output whereby the first 16 characters have been reversed in comparison to /sys/class/dmi/id/product_uuid. This manifests itself by breaking provisioning in Kubernetes and could cause other issues down the line. Other OS such as redhat have already patched this in their releases. A demonstration of the issue can be found in this pastebin: https://pastebin.canonical.com/p/qRfrpHXwGs/ VMWare Issue: https://kb.vmware.com/s/article/53609 Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1851676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected
These are my dmesg and alsa-base.conf dmesg: [0.00] microcode: microcode updated early to revision 0x38, date = 2019- 01-15 [0.00] Linux version 5.3.0-46-generic (buildd@lgw01-amd64-003) (gcc vers ion 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #38-Ubuntu SMP Fri Mar 27 17:37:05 U TC 2020 (Ubuntu 5.3.0-46.38-generic 5.3.18) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID =6648ead1-09e3-461e-a036-5cb58e11ab8b ro quiet splash vt.handoff=7 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point regi sters' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' [0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' [0.00] x86/fpu: xstate_offset[3]: 576, xstate_sizes[3]: 64 [0.00] x86/fpu: xstate_offset[4]: 640, xstate_sizes[4]: 64 [0.00] x86/fpu: Enabled xstate features 0x1b, context size is 704 bytes, using 'compacted' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009e7ff] usable [0.00] BIOS-e820: [mem 0x0009e800-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x0fff] usable [0.00] BIOS-e820: [mem 0x1000-0x12150fff] reserved [0.00] BIOS-e820: [mem 0x12151000-0x67b4] usable [0.00] BIOS-e820: [mem 0x67b5-0x67b50fff] ACPI NVS [0.00] BIOS-e820: [mem 0x67b51000-0x67b6afff] reserved [0.00] BIOS-e820: [mem 0x67b6b000-0x67ba6fff] usable [0.00] BIOS-e820: [mem 0x67ba7000-0x68ba6fff] ACPI NVS [0.00] BIOS-e820: [mem 0x68ba7000-0x7822efff] usable [0.00] BIOS-e820: [mem 0x7822f000-0x7aebefff] reserved [0.00] BIOS-e820: [mem 0x7aebf000-0x7afbefff] ACPI NVS [0.00] BIOS-e820: [mem 0x7afbf000-0x7affefff] ACPI data [0.00] BIOS-e820: [mem 0x7afff000-0x7aff] usable [0.00] BIOS-e820: [mem 0x7b00-0x7fff] reserved [0.00] BIOS-e820: [mem 0xd000-0xd0ff] reserved [0.00] BIOS-e820: [mem 0xe000-0xe3ff] reserved [0.00] BIOS-e820: [mem 0xfe042000-0xfe044fff] reserved [0.00] BIOS-e820: [mem 0xfe90-0xfe902fff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed01000-0xfed01fff] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff80-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00017fff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 3.0 present. [0.00] DMI: LENOVO 80XR/LNVNB161216, BIOS 5RCN30WW 10/23/2017 [0.00] tsc: Detected 1094.400 MHz processor [0.005258] e820: update [mem 0x-0x0fff] usable ==> reserved [0.005263] e820: remove [mem 0x000a-0x000f] usable [0.005284] last_pfn = 0x18 max_arch_pfn = 0x4 [0.005292] MTRR default type: uncachable [0.005294] MTRR fixed ranges enabled: [0.005298] 0-9 write-back [0.005300] A-B uncachable [0.005303] C-F write-protect [0.005305] MTRR variable ranges enabled: [0.005309] 0 base 00 mask 7F8000 write-back [0.005312] 1 base 007C00 mask 7FFC00 uncachable [0.005315] 2 base 007B00 mask 7FFF00 uncachable [0.005318] 3 base 01 mask 7F8000 write-back [0.005321] 4 base 00FFC0 mask 70FFC0 write-combining [0.005323] 5 disabled [0.005325] 6 disabled [0.005326] 7 disabled [0.005328] 8 disabled [0.005329] 9 disabled [0.005441] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.005538] last_pfn = 0x7b000 max_arch_pfn = 0x4 [0.015545] check: Scanning 1 areas for low memory corruption [0.015556] Using GB pages for direct mapping [0.015562] BRK [0x140e01000, 0x140e01fff] PGTABLE [0.015567] BRK [0x140e02000, 0x140e02fff] PGTABLE [0.015570] BRK [0x140e03000, 0x140e03fff] PGTABLE [0.015694] BRK [0x140e04000, 0x140e04fff] PGTABLE [0.015997] BRK [0x140e05000, 0x140e05fff] PGTABLE [0.016094] BRK [0x140e06000, 0x140e06fff] PGTABLE [0.016196] BRK
[Kernel-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubiquity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: In Progress Status in ubiquity package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in linux source package in Focal: Incomplete Status in nvidia-graphics-drivers-440 source package in Focal: In Progress Status in ubiquity source package in Focal: Confirmed Status in ubuntu-drivers-common source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873481] Re: Focal update: v5.4.33 upstream stable release
The commit "ACPI: EC: Do not clear boot_ec_is_ecdt in acpi_ec_add()"
subsequently gets reverted upstream in v5.4.34, so dropping it from this
patch set.
--
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/1873481
Title:
Focal update: v5.4.33 upstream stable release
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.33 upstream stable release
from git://git.kernel.org/
ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
ARM: dts: Fix dm814x Ethernet by changing to use rgmii-id mode
bpf: Fix deadlock with rq_lock in bpf_send_signal()
iwlwifi: mvm: Fix rate scale NSS configuration
Input: tm2-touchkey - add support for Coreriver TC360 variant
soc: fsl: dpio: register dpio irq handlers after dpio create
rxrpc: Abstract out the calculation of whether there's Tx space
rxrpc: Fix call interruptibility handling
net: stmmac: platform: Fix misleading interrupt error msg
net: vxge: fix wrong __VA_ARGS__ usage
hinic: fix a bug of waitting for IO stopped
hinic: fix the bug of clearing event queue
hinic: fix out-of-order excution in arm cpu
hinic: fix wrong para of wait_for_completion_timeout
hinic: fix wrong value of MIN_SKB_LEN
selftests/net: add definition for SOL_DCCP to fix compilation errors for old
libc
cxgb4/ptp: pass the sign of offset delta in FW CMD
drm/scheduler: fix rare NULL ptr race
cfg80211: Do not warn on same channel at the end of CSA
qlcnic: Fix bad kzalloc null test
i2c: st: fix missing struct parameter description
i2c: pca-platform: Use platform_irq_get_optional
media: rc: add keymap for Videostrong KII Pro
cpufreq: imx6q: Fixes unwanted cpu overclocking on i.MX6ULL
staging: wilc1000: avoid double unlocking of 'wilc->hif_cs' mutex
media: venus: hfi_parser: Ignore HEVC encoding for V1
firmware: arm_sdei: fix double-lock on hibernate with shared events
null_blk: Fix the null_add_dev() error path
null_blk: Handle null_add_dev() failures properly
null_blk: fix spurious IO errors after failed past-wp access
media: imx: imx7_mipi_csis: Power off the source when stopping streaming
media: imx: imx7-media-csi: Fix video field handling
xhci: bail out early if driver can't accress host in resume
ACPI: EC: Do not clear boot_ec_is_ecdt in acpi_ec_add()
x86: Don't let pgprot_modify() change the page encryption bit
dma-mapping: Fix dma_pgprot() for unencrypted coherent pages
block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
debugfs: Check module state before warning in {full/open}_proxy_open()
irqchip/versatile-fpga: Handle chained IRQs properly
time/sched_clock: Expire timer in hardirq context
media: allegro: fix type of gop_length in channel_create message
sched: Avoid scale real weight down to zero
selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
PCI/switchtec: Fix init_completion race condition with poll_wait()
block, bfq: move forward the getting of an extra ref in bfq_bfqq_move
media: i2c: video-i2c: fix build errors due to 'imply hwmon'
libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
pstore/platform: fix potential mem leak if pstore_init_fs failed
gfs2: Do log_flush in gfs2_ail_empty_gl even if ail list is empty
gfs2: Don't demote a glock until its revokes are written
cpufreq: imx6q: fix error handling
x86/boot: Use unsigned comparison for addresses
efi/x86: Ignore the memory attributes table on i386
genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
block: Fix use-after-free issue accessing struct io_cq
media: i2c: ov5695: Fix power on and off sequences
usb: dwc3: core: add support for disabling SS instances in park mode
irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
md: check arrays is suspended in mddev_detach before call quiesce operations
firmware: fix a double abort case with fw_load_sysfs_fallback
spi: spi-fsl-dspi: Replace interruptible wait queue with a simple completion
locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
block, bfq: fix use-after-free in bfq_idle_slice_timer_body
btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is at
least queued
btrfs: remove a BUG_ON() from merge_reloc_roots()
[Kernel-packages] [Bug 1873965] Re: booting into recovery mode hangs under 20.04
Oddly, so far I have not found a Ubuntu mainline kernel build that doesn't show the problem. 5.3.18-050318-generic 5.4.0-050400-generic 5.4.25-050425-generic 5.4.28-050428-generic 5.6.6-050606-generic all produce the hang at loading the ramdisk when booting the recovery kernel with the default use of nomodesetunder Ubuntu 18.04. The stock 5.3.0-46-generic kernel installed by bionics updates doesn't have this problem. So I am guessing this problem must be either a dropped patch in the kernels used by Ubuntu 20.04 or a change in configuration options in the kernels between 18.04 and 20.04. -- 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/1873965 Title: booting into recovery mode hangs under 20.04 Status in linux-meta package in Ubuntu: New Bug description: On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery mode from grub hangs on loading of the ramdisk with the Recovery Menu dialog never appearing. This problem doesn't exist for a fresh install of Ubuntu 18.04 updated to the current package updates. In that case, the Recovery Menu appears as expected. This bug in Ubuntu 20.04 was reproduced for both an existing Ubuntu 19.10 installation dist-upgraded to Ubuntu 20.04 as well as for a fresh install of Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851676] Re: dmidecode does not byte-swap for SMBIOS >= 2.6
FYI: 19.04: ii dmidecode 3.2-2amd64SMBIOS/DMI table decoder $ sudo cat /sys/class/dmi/id/product_serial VMware-42 18 59 50 7a fe ee b9-86 41 a6 c8 5a 5a 23 a6 $ sudo dmidecode | grep -i serial | grep VM Serial Number: VMware-42 18 59 50 7a fe ee b9-86 41 a6 c8 5a 5a 23 a6 Bionic: ii dmidecode 3.1-1 amd64 SMBIOS/DMI table decoder $ sudo cat /sys/class/dmi/id/product_serial VMware-42 18 ac 2f fd b1 53 1b-8d ba ba ce ed cd d5 4b $ sudo dmidecode | grep -i serial | grep VM Serial Number: VMware-42 18 ac 2f fd b1 53 1b-8d ba ba ce ed cd d5 4b I can not see the issue over here at least -- 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/1851676 Title: dmidecode does not byte-swap for SMBIOS >= 2.6 Status in dmidecode package in Ubuntu: New Bug description: Hi, On VMWare 6.5 and higher (HW version 13 and higher) when decoding /sys/class/dmi/id/product_serial dmidecode produces an output whereby the first 16 characters have been reversed in comparison to /sys/class/dmi/id/product_uuid. This manifests itself by breaking provisioning in Kubernetes and could cause other issues down the line. Other OS such as redhat have already patched this in their releases. A demonstration of the issue can be found in this pastebin: https://pastebin.canonical.com/p/qRfrpHXwGs/ VMWare Issue: https://kb.vmware.com/s/article/53609 Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1851676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874104] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015 5k 27" iMac. The new 5.4 kernel was installed and has been updated a few times. The former LTS kernel (4.15) was retained. When I start up the computer with the new kernel, the process is very slow and it takes about 2 1/2 minutes to get to a working desktop. Doing the same startup with the old 4.15 kernel (in the 20.04 beta) takes approximately 25 seconds to a working desktop. Similarly, changing display settings, waking from sleep and shutting down the computer all take several minutes with the 5.4 kernel, vs 10-30 seconds with the 4.15 kernel. To provide more information, I tried starting up this computer with the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to the 4.15 LTS kernel. I suspect that the problem relates to the Radeon m9 390x video card in my iMac, but I have no idea what might have changed in the newer kernels to affect their compatibility with this iMac. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-25-generic 5.4.0-25.29 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mfox 2497 F pulseaudio /dev/snd/controlC0: mfox 2497 F pulseaudio /dev/snd/controlC1: mfox 2497 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 10:55:18 2020 HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a InstallationDate: Installed on 2018-05-09 (712 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. iMac17,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: \boot\vmlinuz-5.4.0-25-generic ro root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead initrd=boot\initrd.img-5.4.0-25-generic RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 176.0.0.0.0 dmi.board.name: Mac-B809C3757DA9BB8D dmi.board.vendor: Apple Inc. dmi.board.version: iMac17,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-B809C3757DA9BB8D dmi.modalias: dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D: dmi.product.family: iMac17,1 dmi.product.name: iMac17,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
So, this looks like the bug to me: Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: bcache0: /usr/lib/udev/rules.d/60-persistent-storage.rules:112 LINK 'disk/by-uuid/30b28bee-6a1e-423d-9d53-32c78ba5454a' Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: bcache0: Updating old name, '/dev/bcache/by-uuid/1522715e-a390-40db-8d47-06fb728014e5' no longer belonging to '/devices/virtual/block/bcache0' Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: bcache0: No reference left, removing '/dev/bcache/by-uuid/1522715e-a390-40db-8d47-06fb728014e5' Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: bcache0: Handling device node '/dev/bcache0', devnum=b251:0 In Focal, the second event is valid, but 60-persistent-storage.rules has no rules that touch /dev/bcache/by-uuid; they don't even use the same ENV value ... so why would the by-uuid symlink rule in 60-persistent-storage.rules remove a link it doesn't have a rule for? -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed-5.4 package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Do we have any more information on why we now get two events in Focal? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed-5.4 package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
nvidia-driver-440 also currently has this dependency: nvidia-dkms-440 (= 440.64-0ubuntu3) | nvidia-dkms-440 (= 440.82+really.440.64-0ubuntu4) The first branch is satisfied by the lrm packages and the second branch is satisfied by the real nvidia-dkms-440 package, which means that apt install nvidia will always select some lrm provider but not necessarily the one that matches your kernel. We should reverse this order so that apt picks the "safe" default of the real nvidia-dkms package. This will become obsolete with the next upload of nvidia, since the real and virtual package versions will again line up. ** Also affects: ubuntu-meta (Ubuntu Focal) Importance: Undecided Status: Fix Committed ** Also affects: ubiquity (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: Confirmed ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: In Progress Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in linux source package in Focal: Incomplete Status in nvidia-graphics-drivers-440 source package in Focal: In Progress Status in ubiquity source package in Focal: New Status in ubuntu-drivers-common source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874104] [NEW] Very slow boot, wake from sleep and shutdown with 5.4 kernel
Public bug reported: I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015 5k 27" iMac. The new 5.4 kernel was installed and has been updated a few times. The former LTS kernel (4.15) was retained. When I start up the computer with the new kernel, the process is very slow and it takes about 2 1/2 minutes to get to a working desktop. Doing the same startup with the old 4.15 kernel (in the 20.04 beta) takes approximately 25 seconds to a working desktop. Similarly, changing display settings, waking from sleep and shutting down the computer all take several minutes with the 5.4 kernel, vs 10-30 seconds with the 4.15 kernel. To provide more information, I tried starting up this computer with the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to the 4.15 LTS kernel. I suspect that the problem relates to the Radeon m9 390x video card in my iMac, but I have no idea what might have changed in the newer kernels to affect their compatibility with this iMac. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-25-generic 5.4.0-25.29 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mfox 2497 F pulseaudio /dev/snd/controlC0: mfox 2497 F pulseaudio /dev/snd/controlC1: mfox 2497 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 10:55:18 2020 HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a InstallationDate: Installed on 2018-05-09 (712 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. iMac17,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: \boot\vmlinuz-5.4.0-25-generic ro root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead initrd=boot\initrd.img-5.4.0-25-generic RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 176.0.0.0.0 dmi.board.name: Mac-B809C3757DA9BB8D dmi.board.vendor: Apple Inc. dmi.board.version: iMac17,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-B809C3757DA9BB8D dmi.modalias: dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D: dmi.product.family: iMac17,1 dmi.product.name: iMac17,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "SystemD critical chain and blame outputs: 5.4 vs 4.15 kernel" https://bugs.launchpad.net/bugs/1874104/+attachment/5357597/+files/SystemD%20report_Ubuntu_20.04beta_late_2015_iMac.odt -- 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/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel Status in linux package in Ubuntu: New Bug description: I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015 5k 27" iMac. The new 5.4 kernel was installed and has been updated a few times. The former LTS kernel (4.15) was retained. When I start up the computer with the new kernel, the process is very slow and it takes about 2 1/2 minutes to get to a working desktop. Doing the same startup with the old 4.15 kernel (in the 20.04 beta) takes approximately 25 seconds to a working desktop. Similarly, changing display settings, waking from sleep and shutting down the computer all take several minutes with the 5.4 kernel, vs 10-30 seconds with the 4.15 kernel. To provide more information, I tried starting up this computer with the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to the 4.15 LTS kernel. I suspect that the problem relates to the Radeon m9 390x video card in my iMac, but I have no idea what might have changed in the newer kernels to affect their compatibility with this iMac. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-25-generic 5.4.0-25.29 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27
[Kernel-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection
This bug was fixed in the package linux - 5.4.0-26.30 --- linux (5.4.0-26.30) focal; urgency=medium * focal/linux: 5.4.0-26.30 -proposed tracker (LP: #1873882) * Packaging resync (LP: #1786013) - update dkms package versions * swap storms kills interactive use (LP: #1861359) - SAUCE: drm/i915: prevent direct writeback from the shrinker * 5.4.0-24.28 does not seem to apply rtprio, whereas -21 does. (LP: #1873315) - [Config] lowlatency: turn off RT_GROUP_SCHED * [RTL810xE] No ethernet connection (LP: #1871182) - net: phy: realtek: fix handling of RTL8105e-integrated PHY -- Andrea Righi Mon, 20 Apr 2020 18:33:49 +0200 ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873315] Re: 5.4.0-24.28 does not seem to apply rtprio, whereas -21 does.
This bug was fixed in the package linux - 5.4.0-26.30 --- linux (5.4.0-26.30) focal; urgency=medium * focal/linux: 5.4.0-26.30 -proposed tracker (LP: #1873882) * Packaging resync (LP: #1786013) - update dkms package versions * swap storms kills interactive use (LP: #1861359) - SAUCE: drm/i915: prevent direct writeback from the shrinker * 5.4.0-24.28 does not seem to apply rtprio, whereas -21 does. (LP: #1873315) - [Config] lowlatency: turn off RT_GROUP_SCHED * [RTL810xE] No ethernet connection (LP: #1871182) - net: phy: realtek: fix handling of RTL8105e-integrated PHY -- Andrea Righi Mon, 20 Apr 2020 18:33:49 +0200 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873315 Title: 5.4.0-24.28 does not seem to apply rtprio, whereas -21 does. Status in linux package in Ubuntu: Fix Released Bug description: Impact: Software that requires RT priority is not working anymore since we turned on RT_GROUP_SCHED: commit 9b039fc517876d312e7fa0955571101a299c91f5 Author: Seth Forshee Date: Mon Apr 6 07:11:44 2020 -0500 UBUNTU: [Config] CONFIG_RT_GROUP_SCHED=y This is wanted by docker, and the original reason for disabling it no longer applied. Performance testing shows no noticible impact when the option is enabled. We already hit this issue in the past (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731), but nowadays reverting RT_GROUP_SCHED back to off would regress Docker and since RT privileges are usually required by audio/multimedia software, it probably make sense to revert this change only for -lowlatency (and keep the rest as is) and encourage people to use -lowlatency if they hit this problem. Fix: Apply the attached patch Regression potential: None, only -lowlatency is impacted, -generic doesn't change. -- I'm using the xwax package on a Dell XPS 13 (9370) 20.04, which requires rtprio privileges: [daniel@reef ~ ]$ sudo cat /etc/security/limits.d/audio.conf @audio - rtprio 99 [daniel@reef ~ ]$ This worked fine for the past releases of Ubuntu up until the move from linux-image-5.4.0-21-generic to linux-image-5.4.0-24-generic. Today I'm seeing: Launching realtime thread to handle devices... sched_setscheduler: Operation not permitted Failed to get realtime priorities Booting the previous kernel makes it work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2905 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 18:57:21 2020 InstallationDate: Installed on 2018-04-14 (733 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-08 (39 days ago) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] Re: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter
** Description changed: - Description will follow + Today, the enumeration of PCI functions on s390x does not reflect which + functions belongs to which physical adapter. + + Layout of a PCI function address on Linux: + :00:00.0 + ::. + + On s390x, each function is presented as individual root complex today, + e.g.: + + PCHID 0100 VF1 :00:00.0 + PCHID 0100 VF23 0001:00:00.0 + PCHID 0200 VF1 0002:00:00.0 + OCHID 0100 VF17 0003:00:00.0 + + On other platforms, the addresses correctly reflect the actual HW + configuration. Some device drivers (mlx5 for Mellanox adapters) group + functions of one physical adapter by checking which PCI functions have + identical values for ::. We need to use the + same enumeration scheme to achieve this functionality on s390x. + + In this case, the two physical functions of a Mellanox adapter need to + get function number 0 and 1, and all virtual functions need to use the + same : numbers with function/device numbers counting + up. + + Required result (example with 4 VFs per PF): + + PCHID 0100 PF 0 :00:00.0 + PCHID 0100 PF 1 :00:00.1 + PCHID 0100 PF 0 VF 0 :00:00.2 + PCHID 0100 PF 0 VF 1 :00:00.3 + PCHID 0100 PF 0 VF 2 :00:00.4 + PCHID 0100 PF 0 VF 3 :00:00.5 + PCHID 0100 PF 1 VF 0 :00:00.6 + PCHID 0100 PF 1 VF 1 :00:00.7 + PCHID 0100 PF 1 VF 2 :00:00.8 + PCHID 0100 PF 1 VF 3 :00:00.9 + + PCHID 0200 PF 0 0001:00:00.0 ** Also affects: ubuntu-z-systems 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use
This bug was fixed in the package linux - 5.4.0-26.30
---
linux (5.4.0-26.30) focal; urgency=medium
* focal/linux: 5.4.0-26.30 -proposed tracker (LP: #1873882)
* Packaging resync (LP: #1786013)
- update dkms package versions
* swap storms kills interactive use (LP: #1861359)
- SAUCE: drm/i915: prevent direct writeback from the shrinker
* 5.4.0-24.28 does not seem to apply rtprio, whereas -21 does. (LP: #1873315)
- [Config] lowlatency: turn off RT_GROUP_SCHED
* [RTL810xE] No ethernet connection (LP: #1871182)
- net: phy: realtek: fix handling of RTL8105e-integrated PHY
-- Andrea Righi Mon, 20 Apr 2020 18:33:49
+0200
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861359
Title:
swap storms kills interactive use
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
[Impact]
The i915 shrinker can make the system unresponsive and kill
interactive performance by swapping out dirty objects to reclaim more
memory.
[Test case]
The problem can be easily reproduced running an I/O intensive writer,
for example:
$ dd if=/dev/zero of=/tmp/zero bs=1G count=32
When the system is running out of memory and the i915 shrinker is
called we can experience noticeable lags in the normal interactive
activities (mouse not responding for 5-10 seconds, screen not
refreshing, etc.).
[Fix]
Avoid the lags by preventing to swap out dirty objects in the i915
shrinker (other cached objects can still be reclaimed).
[Regression potential]
The right fix would be to backport commit 2850748ef876 ("drm/i915:
Pull i915_vma_pin under the vm->mutex"), available in v5.5+. However
the backport is not trivial and the risk to introduce other bugs is
high.
A simple change like this (it's basically a one-liner that removes a
flag) can be a reasonable compromise to prevent the problem and avoid
the risk of introducing other bugs.
[Original report]
Hello, several times since upgrading to focal from 19.04 I've found my
computer entirely unresponsive for periods of twenty or thirty
seconds. No mouse movement, no keyboard input, the screen output does
not change.
My computer was using swap space and despite very slow writeout speeds
well below what the NVME drive can handle, the computer was unusable.
I've captured some vmstat 1 output and top output that I started
collecting during the event. (Normally one very long painful period is
followed by several shorter periods of uselessness.)
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
Date: Wed Jan 29 23:44:05 2020
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-12-generic.
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sarnold2734 F pulseaudio
/dev/snd/controlC1: sarnold2734 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
Mixer name : 'Realtek ALC285'
Components : 'HDA:10ec0285,17aa225c,0012
HDA:8086280b,80860101,0010'
Controls : 53
Simple ctrls : 15
Card1.Amixer.info:
Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at
usb-:00:14.0-4.2.4, high speed'
Mixer name : 'USB Mixer'
Components : 'USB17ef:306f'
Controls : 9
Simple ctrls : 4
DistroRelease: Ubuntu 20.04
HibernationDevice: RESUME=none
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: LENOVO 20KHCTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
RelatedPackageVersions:
linux-restricted-modules-5.4.0-12-generic N/A
linux-backports-modules-5.4.0-12-generic N/A
linux-firmware
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
This bug was fixed in the package linux-kvm - 5.4.0-1009.9 --- linux-kvm (5.4.0-1009.9) focal; urgency=medium * focal/linux-kvm: 5.4.0-1009.9 -proposed tracker (LP: #1873934) * multipathd.service fails to start with linux-kvm kernel (LP: #1873912) - [Config] Enable dm-multipath modules * Make linux-kvm bootable in LXD VMs (LP: #1873809) - [Config] CONFIG_EFI_STUB=y - [Config] Enable vsocket config options -- Seth Forshee Mon, 20 Apr 2020 14:30:41 -0500 ** Changed in: linux-kvm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs Status in Cloud-Bio-Linux Tutorials: Confirmed Status in cloud-images: Confirmed Status in linux-kvm package in Ubuntu: Fix Released Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS -
[Kernel-packages] [Bug 1873912] Re: multipathd.service fails to start with linux-kvm kernel
This bug was fixed in the package linux-kvm - 5.4.0-1009.9 --- linux-kvm (5.4.0-1009.9) focal; urgency=medium * focal/linux-kvm: 5.4.0-1009.9 -proposed tracker (LP: #1873934) * multipathd.service fails to start with linux-kvm kernel (LP: #1873912) - [Config] Enable dm-multipath modules * Make linux-kvm bootable in LXD VMs (LP: #1873809) - [Config] CONFIG_EFI_STUB=y - [Config] Enable vsocket config options -- Seth Forshee Mon, 20 Apr 2020 14:30:41 -0500 ** Changed in: linux-kvm (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1873912 Title: multipathd.service fails to start with linux-kvm kernel Status in linux-kvm package in Ubuntu: Fix Released Bug description: SRU Justification Impact: multipath-tools is installed by default in server images. With the linux-kvm kernel, multipathd.service fails to start because we do not build dm-multipath in linux-kvm. Fix: Enable the dm-multipath modules in linux-kvm. Test Case: Booting the kvm kernel with these modules enabled allows multipathd.service to start successfully. Regression Potential: This adds a new module which is loaded my multipathd.service. However it's not really going to be utilized unless it is wanted, and as this module is shipped with our other kernels without issue the risk of regressions is low. --- When doing a dist-upgrade in a vm running the linux-kvm kernel, multipath-tools failed because multipathd.service failed to start. Setting up multipath-tools (0.8.3-1ubuntu2) ... Job for multipathd.service failed because the control process exited with error code. See "systemctl status multipathd.service" and "journalctl -xe" for details. invoke-rc.d: initscript multipath-tools, action "start" failed. ● multipathd.service - Device-Mapper Multipath Device Controller Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2020-04-20 16:49:35 UTC; 7ms ago TriggeredBy: ● multipathd.socket Process: 800 ExecStartPre=/sbin/modprobe -a scsi_dh_alua scsi_dh_emc scsi_dh_rdac dm-multipath (code=exited, status=1/FAILURE) Process: 801 ExecStart=/sbin/multipathd -d -s (code=exited, status=1/FAILURE) Main PID: 801 (code=exited, status=1/FAILURE) Status: "configure" Apr 20 16:49:35 ff-kvm modprobe[800]: modprobe: WARNING: Module scsi_dh_emc not found in directory /lib/modules/5.4.0-1008-kvm Apr 20 16:49:35 ff-kvm modprobe[800]: modprobe: WARNING: Module scsi_dh_rdac not found in directory /lib/modules/5.4.0-1008-kvm Apr 20 16:49:35 ff-kvm modprobe[800]: modprobe: WARNING: Module dm-multipath not found in directory /lib/modules/5.4.0-1008-kvm Apr 20 16:49:35 ff-kvm multipathd[801]: start up Apr 20 16:49:35 ff-kvm multipathd[801]: read /etc/multipath.conf Apr 20 16:49:35 ff-kvm multipathd[801]: DM multipath kernel driver not loaded Apr 20 16:49:35 ff-kvm multipathd[801]: DM multipath kernel driver not loaded Apr 20 16:49:35 ff-kvm systemd[1]: multipathd.service: Main process exited, code=exited, status=1/FAILURE Apr 20 16:49:35 ff-kvm systemd[1]: multipathd.service: Failed with result 'exit-code'. Apr 20 16:49:35 ff-kvm systemd[1]: Failed to start Device-Mapper Multipath Device Controller. dpkg: error processing package multipath-tools (--configure): installed multipath-tools package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of ubuntu-server: ubuntu-server depends on multipath-tools; however: Package multipath-tools is not configured yet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: multipath-tools 0.8.3-1ubuntu2 ProcVersionSignature: User Name 5.4.0-1008.8-kvm 5.4.30 Uname: Linux 5.4.0-1008-kvm x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 20 16:57:37 2020 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: multipath-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1873912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874057] Re: [UBUNTU 20.04] s390x/pci: do not allow to create more pci functions than configured via CONFIG_PCI_NR_FUNCTIONS
Patch just landed on 5.7:
git tag --contains 969ae01bab2f | grep ^v
v5.7-rc1
v5.7-rc2
** Description changed:
- Description will follow
+ PCI Functions with UIDs >128 are currently not accounted correctly in
+ the s390x/pci code. Furthermore, the code allows that more than
+ CONFIG_PCI_NR_FUNCTIONS are created. This can lead to issues with data
+ structures which were only allocated for CONFIG_PCI_NR_FUNCTIONS.
+
+ This has been fixed in the following upstream commit:
+
+ 969ae01bab2fe938b4c8324836038b5ac1c78fac
+ ("s390/pci: Fix zpci_alloc_domain() over allocation")
--
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/1874057
Title:
[UBUNTU 20.04] s390x/pci: do not allow to create more pci functions
than configured via CONFIG_PCI_NR_FUNCTIONS
Status in linux package in Ubuntu:
New
Bug description:
PCI Functions with UIDs >128 are currently not accounted correctly in
the s390x/pci code. Furthermore, the code allows that more than
CONFIG_PCI_NR_FUNCTIONS are created. This can lead to issues with data
structures which were only allocated for CONFIG_PCI_NR_FUNCTIONS.
This has been fixed in the following upstream commit:
969ae01bab2fe938b4c8324836038b5ac1c78fac
("s390/pci: Fix zpci_alloc_domain() over allocation")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874057/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874062] Re: [UBUNTU 20.04] Performance floating interrupt
** Description changed: - Description will follow + With the introduction of CPU directed interrupts the kernel parameter pci=force_floating was introduced to fall back to the previous behavior using floating irqs. + Furthermore this fallback is used on machines lacking support for directed interrupts. + + However we were still setting the affinity in that case, both in + __irq_alloc_descs() and via the irq_set_affinity callback in struct + irq_chip. + + This setting of the affinity leads to a performance regression in + streaming workloads which can be seen with e.g. by an iperf streaming + test between two LPARs using ConnectX-5 based nics. + + In some tests the performance would drop to 20% of the performance with + older kernels. ** Also affects: ubuntu-z-systems 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/1874062 Title: [UBUNTU 20.04] Performance floating interrupt Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: With the introduction of CPU directed interrupts the kernel parameter pci=force_floating was introduced to fall back to the previous behavior using floating irqs. Furthermore this fallback is used on machines lacking support for directed interrupts. However we were still setting the affinity in that case, both in __irq_alloc_descs() and via the irq_set_affinity callback in struct irq_chip. This setting of the affinity leads to a performance regression in streaming workloads which can be seen with e.g. by an iperf streaming test between two LPARs using ConnectX-5 based nics. In some tests the performance would drop to 20% of the performance with older kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874055] Re: [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO instructions are available
** Description changed: - Description will follow + One of the PCI enhancements on Z15 are the enhanced PCI load/store + instructions which can be executed directly from user space code. When + these instructions are available and preexisting user space code still + uses the old s390_pci_mmio_write/read system calls, the system calls + fail with an "Unable to handle kernel pointer dereference in virtual + kernel address space" in the kernel. This issue affects distributions + which have the enablement for Z15 PCI enhancements and where customers + run workloads which accesses PCI adapters from user space, e.g. RDMA + applications. To solve this, the system call implementation needs to be + enhanced to provide to execute enhanced PCI load/store instructions on + behalf of the user space application making use of the mappings into its + virtual address space ** Also affects: ubuntu-z-systems 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/1874055 Title: [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO instructions are available Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: One of the PCI enhancements on Z15 are the enhanced PCI load/store instructions which can be executed directly from user space code. When these instructions are available and preexisting user space code still uses the old s390_pci_mmio_write/read system calls, the system calls fail with an "Unable to handle kernel pointer dereference in virtual kernel address space" in the kernel. This issue affects distributions which have the enablement for Z15 PCI enhancements and where customers run workloads which accesses PCI adapters from user space, e.g. RDMA applications. To solve this, the system call implementation needs to be enhanced to provide to execute enhanced PCI load/store instructions on behalf of the user space application making use of the mappings into its virtual address space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873965] Re: booting into recovery mode hangs under 20.04
Interestingly, installing the mainline Ubuntu 5.4.25 generic kernel packages on Ubuntu 18.04 produces the same bug of nomodeset preventing the recovery dialog from appearing. -- 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/1873965 Title: booting into recovery mode hangs under 20.04 Status in linux-meta package in Ubuntu: New Bug description: On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery mode from grub hangs on loading of the ramdisk with the Recovery Menu dialog never appearing. This problem doesn't exist for a fresh install of Ubuntu 18.04 updated to the current package updates. In that case, the Recovery Menu appears as expected. This bug in Ubuntu 20.04 was reproduced for both an existing Ubuntu 19.10 installation dist-upgraded to Ubuntu 20.04 as well as for a fresh install of Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865406] Re: Add support to test 5.0 Bionic kernel
https://kernel.ubuntu.com/git/ubuntu/kernel- testing.git/commit/?id=65872ca505880d6e1ac529c0d85e5130c7f8fd84 -- 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/1865406 Title: Add support to test 5.0 Bionic kernel Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Bug description: For Bionic-5.0 hwe kernel, the requested meta package "linux-generic- hwe-18.04-5.0" from the test request is not available: sudo DEBIAN_FRONTEND=noninteractive UCF_FORCE_CONFFNEW=1 apt-get install --yes linux-generic-hwe-18.04-5.0 ShellError Raised Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package linux-generic-hwe-18.04-5.0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-76-generic 4.15.0-76.86 ProcVersionSignature: User Name 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 2 03:09 seq crw-rw 1 root audio 116, 33 Mar 2 03:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Mar 2 03:12:05 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-76-generic N/A linux-backports-modules-4.15.0-76-generic N/A linux-firmware 1.173.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874093] [NEW] Xenial update: 4.4.219 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.219 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) 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/1874093 Title: Xenial update: 4.4.219 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.219 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850238] Re: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1047.52
---
linux-oem-osp1 (5.0.0-1047.52) bionic; urgency=medium
* bionic/linux-oem-osp1: 5.0.0-1047.52 -proposed tracker (LP:
#1869351)
* ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent
kernels (LP: #1850238)
- i2c: nvidia-gpu: Handle timeout correctly in gpu_i2c_check_status()
* All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- Revert "UBUNTU: SAUCE: Input: i8042 - Fix the selftest retry logic"
- SAUCE: Input: i8042 - fix the selftest retry logic
[ Ubuntu: 5.0.0-45.49 ]
* disco/linux: 5.0.0-45.49 -proposed tracker (LP: #1868954)
* Missing wireless network interface after kernel 5.3.0-43 upgrade with eoan
(LP: #1868442)
- iwlwifi: mvm: Do not require PHY_SKU NVM section for 3168 devices
[ Ubuntu: 5.0.0-44.48 ]
* disco/linux: 5.0.0-44.48 -proposed tracker (LP: #1867284)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
* Disco update: upstream stable patchset 2020-03-10 (LP: #1866858)
- Revert "drm/sun4i: dsi: Change the start delay calculation"
- ovl: fix lseek overflow on 32bit
- kernel/module: Fix memleak in module_add_modinfo_attrs()
- media: iguanair: fix endpoint sanity check
- ocfs2: fix oops when writing cloned file
- x86/cpu: Update cached HLE state on write to TSX_CTRL_CPUID_CLEAR
- udf: Allow writing to 'Rewritable' partitions
- printk: fix exclusive_console replaying
- iwlwifi: mvm: fix NVM check for 3168 devices
- sparc32: fix struct ipc64_perm type definition
- cls_rsvp: fix rsvp_policy
- gtp: use __GFP_NOWARN to avoid memalloc warning
- l2tp: Allow duplicate session creation with UDP
- net: hsr: fix possible NULL deref in hsr_handle_frame()
- net_sched: fix an OOB access in cls_tcindex
- net: stmmac: Delete txtimer in suspend()
- bnxt_en: Fix TC queue mapping.
- tcp: clear tp->total_retrans in tcp_disconnect()
- tcp: clear tp->delivered in tcp_disconnect()
- tcp: clear tp->data_segs{in|out} in tcp_disconnect()
- tcp: clear tp->segs_{in|out} in tcp_disconnect()
- rxrpc: Fix use-after-free in rxrpc_put_local()
- rxrpc: Fix insufficient receive notification generation
- rxrpc: Fix missing active use pinning of rxrpc_local object
- rxrpc: Fix NULL pointer deref due to call->conn being cleared on
disconnect
- media: uvcvideo: Avoid cyclic entity chains due to malformed USB
descriptors
- mfd: dln2: More sanity checking for endpoints
- ipc/msg.c: consolidate all xxxctl_down() functions
- tracing: Fix sched switch start/stop refcount racy updates
- rcu: Avoid data-race in rcu_gp_fqs_check_wake()
- brcmfmac: Fix memory leak in brcmf_usbdev_qinit
- usb: typec: tcpci: mask event interrupts when remove driver
- usb: gadget: legacy: set max_speed to super-speed
- usb: gadget: f_ncm: Use atomic_t to track in-flight request
- usb: gadget: f_ecm: Use atomic_t to track in-flight request
- ALSA: usb-audio: Fix endianess in descriptor validation
- ALSA: dummy: Fix PCM format loop in proc output
- mm/memory_hotplug: fix remove_memory() lockdep splat
- mm: move_pages: report the number of non-attempted pages
- media/v4l2-core: set pages dirty upon releasing DMA buffers
- media: v4l2-core: compat: ignore native command codes
- media: v4l2-rect.h: fix v4l2_rect_map_inside() top/left adjustments
- lib/test_kasan.c: fix memory leak in kmalloc_oob_krealloc_more()
- irqdomain: Fix a memory leak in irq_domain_push_irq()
- platform/x86: intel_scu_ipc: Fix interrupt support
- ALSA: hda: Add Clevo W65_67SB the power_save blacklist
- KVM: arm64: Correct PSTATE on exception entry
- KVM: arm/arm64: Correct CPSR on exception entry
- KVM: arm/arm64: Correct AArch32 SPSR on exception entry
- KVM: arm64: Only sign-extend MMIO up to register width
- MIPS: fix indentation of the 'RELOCS' message
- MIPS: boot: fix typo in 'vmlinux.lzma.its' target
- s390/mm: fix dynamic pagetable upgrade for hugetlbfs
- powerpc/xmon: don't access ASDR in VMs
- powerpc/pseries: Advance pfn if section is not present in
lmb_is_removable()
- smb3: fix signing verification of large reads
- PCI: tegra: Fix return value check of pm_runtime_get_sync()
- mmc: spi: Toggle SPI polarity, do not hardcode it
- ACPI: video: Do not export a non working backlight interface on MSI
MS-7721
boards
- ACPI / battery: Deal with design or full capacity being reported as -1
- ACPI / battery: Use design-cap for capacity calculations if full-cap is
not
available
- ACPI / battery: Deal better with neither design nor full capacity not
being
reported
- alarmtimer: Unregister wakeup source when module get fails
- ubifs: Reject unsupported ioctl flags explicitly
[Kernel-packages] [Bug 1850238] Re: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1047.52
---
linux-oem-osp1 (5.0.0-1047.52) bionic; urgency=medium
* bionic/linux-oem-osp1: 5.0.0-1047.52 -proposed tracker (LP:
#1869351)
* ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent
kernels (LP: #1850238)
- i2c: nvidia-gpu: Handle timeout correctly in gpu_i2c_check_status()
* All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- Revert "UBUNTU: SAUCE: Input: i8042 - Fix the selftest retry logic"
- SAUCE: Input: i8042 - fix the selftest retry logic
[ Ubuntu: 5.0.0-45.49 ]
* disco/linux: 5.0.0-45.49 -proposed tracker (LP: #1868954)
* Missing wireless network interface after kernel 5.3.0-43 upgrade with eoan
(LP: #1868442)
- iwlwifi: mvm: Do not require PHY_SKU NVM section for 3168 devices
[ Ubuntu: 5.0.0-44.48 ]
* disco/linux: 5.0.0-44.48 -proposed tracker (LP: #1867284)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
* Disco update: upstream stable patchset 2020-03-10 (LP: #1866858)
- Revert "drm/sun4i: dsi: Change the start delay calculation"
- ovl: fix lseek overflow on 32bit
- kernel/module: Fix memleak in module_add_modinfo_attrs()
- media: iguanair: fix endpoint sanity check
- ocfs2: fix oops when writing cloned file
- x86/cpu: Update cached HLE state on write to TSX_CTRL_CPUID_CLEAR
- udf: Allow writing to 'Rewritable' partitions
- printk: fix exclusive_console replaying
- iwlwifi: mvm: fix NVM check for 3168 devices
- sparc32: fix struct ipc64_perm type definition
- cls_rsvp: fix rsvp_policy
- gtp: use __GFP_NOWARN to avoid memalloc warning
- l2tp: Allow duplicate session creation with UDP
- net: hsr: fix possible NULL deref in hsr_handle_frame()
- net_sched: fix an OOB access in cls_tcindex
- net: stmmac: Delete txtimer in suspend()
- bnxt_en: Fix TC queue mapping.
- tcp: clear tp->total_retrans in tcp_disconnect()
- tcp: clear tp->delivered in tcp_disconnect()
- tcp: clear tp->data_segs{in|out} in tcp_disconnect()
- tcp: clear tp->segs_{in|out} in tcp_disconnect()
- rxrpc: Fix use-after-free in rxrpc_put_local()
- rxrpc: Fix insufficient receive notification generation
- rxrpc: Fix missing active use pinning of rxrpc_local object
- rxrpc: Fix NULL pointer deref due to call->conn being cleared on
disconnect
- media: uvcvideo: Avoid cyclic entity chains due to malformed USB
descriptors
- mfd: dln2: More sanity checking for endpoints
- ipc/msg.c: consolidate all xxxctl_down() functions
- tracing: Fix sched switch start/stop refcount racy updates
- rcu: Avoid data-race in rcu_gp_fqs_check_wake()
- brcmfmac: Fix memory leak in brcmf_usbdev_qinit
- usb: typec: tcpci: mask event interrupts when remove driver
- usb: gadget: legacy: set max_speed to super-speed
- usb: gadget: f_ncm: Use atomic_t to track in-flight request
- usb: gadget: f_ecm: Use atomic_t to track in-flight request
- ALSA: usb-audio: Fix endianess in descriptor validation
- ALSA: dummy: Fix PCM format loop in proc output
- mm/memory_hotplug: fix remove_memory() lockdep splat
- mm: move_pages: report the number of non-attempted pages
- media/v4l2-core: set pages dirty upon releasing DMA buffers
- media: v4l2-core: compat: ignore native command codes
- media: v4l2-rect.h: fix v4l2_rect_map_inside() top/left adjustments
- lib/test_kasan.c: fix memory leak in kmalloc_oob_krealloc_more()
- irqdomain: Fix a memory leak in irq_domain_push_irq()
- platform/x86: intel_scu_ipc: Fix interrupt support
- ALSA: hda: Add Clevo W65_67SB the power_save blacklist
- KVM: arm64: Correct PSTATE on exception entry
- KVM: arm/arm64: Correct CPSR on exception entry
- KVM: arm/arm64: Correct AArch32 SPSR on exception entry
- KVM: arm64: Only sign-extend MMIO up to register width
- MIPS: fix indentation of the 'RELOCS' message
- MIPS: boot: fix typo in 'vmlinux.lzma.its' target
- s390/mm: fix dynamic pagetable upgrade for hugetlbfs
- powerpc/xmon: don't access ASDR in VMs
- powerpc/pseries: Advance pfn if section is not present in
lmb_is_removable()
- smb3: fix signing verification of large reads
- PCI: tegra: Fix return value check of pm_runtime_get_sync()
- mmc: spi: Toggle SPI polarity, do not hardcode it
- ACPI: video: Do not export a non working backlight interface on MSI
MS-7721
boards
- ACPI / battery: Deal with design or full capacity being reported as -1
- ACPI / battery: Use design-cap for capacity calculations if full-cap is
not
available
- ACPI / battery: Deal better with neither design nor full capacity not
being
reported
- alarmtimer: Unregister wakeup source when module get fails
- ubifs: Reject unsupported ioctl flags explicitly
[Kernel-packages] [Bug 1866581] Re: The voice recording function cannot work while connecting a headset on a Dell machine
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1047.52
---
linux-oem-osp1 (5.0.0-1047.52) bionic; urgency=medium
* bionic/linux-oem-osp1: 5.0.0-1047.52 -proposed tracker (LP:
#1869351)
* ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent
kernels (LP: #1850238)
- i2c: nvidia-gpu: Handle timeout correctly in gpu_i2c_check_status()
* All PS/2 ports on PS/2 Serial add-in bracket are not working after S3
(LP: #1866734)
- Revert "UBUNTU: SAUCE: Input: i8042 - Fix the selftest retry logic"
- SAUCE: Input: i8042 - fix the selftest retry logic
[ Ubuntu: 5.0.0-45.49 ]
* disco/linux: 5.0.0-45.49 -proposed tracker (LP: #1868954)
* Missing wireless network interface after kernel 5.3.0-43 upgrade with eoan
(LP: #1868442)
- iwlwifi: mvm: Do not require PHY_SKU NVM section for 3168 devices
[ Ubuntu: 5.0.0-44.48 ]
* disco/linux: 5.0.0-44.48 -proposed tracker (LP: #1867284)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
* Disco update: upstream stable patchset 2020-03-10 (LP: #1866858)
- Revert "drm/sun4i: dsi: Change the start delay calculation"
- ovl: fix lseek overflow on 32bit
- kernel/module: Fix memleak in module_add_modinfo_attrs()
- media: iguanair: fix endpoint sanity check
- ocfs2: fix oops when writing cloned file
- x86/cpu: Update cached HLE state on write to TSX_CTRL_CPUID_CLEAR
- udf: Allow writing to 'Rewritable' partitions
- printk: fix exclusive_console replaying
- iwlwifi: mvm: fix NVM check for 3168 devices
- sparc32: fix struct ipc64_perm type definition
- cls_rsvp: fix rsvp_policy
- gtp: use __GFP_NOWARN to avoid memalloc warning
- l2tp: Allow duplicate session creation with UDP
- net: hsr: fix possible NULL deref in hsr_handle_frame()
- net_sched: fix an OOB access in cls_tcindex
- net: stmmac: Delete txtimer in suspend()
- bnxt_en: Fix TC queue mapping.
- tcp: clear tp->total_retrans in tcp_disconnect()
- tcp: clear tp->delivered in tcp_disconnect()
- tcp: clear tp->data_segs{in|out} in tcp_disconnect()
- tcp: clear tp->segs_{in|out} in tcp_disconnect()
- rxrpc: Fix use-after-free in rxrpc_put_local()
- rxrpc: Fix insufficient receive notification generation
- rxrpc: Fix missing active use pinning of rxrpc_local object
- rxrpc: Fix NULL pointer deref due to call->conn being cleared on
disconnect
- media: uvcvideo: Avoid cyclic entity chains due to malformed USB
descriptors
- mfd: dln2: More sanity checking for endpoints
- ipc/msg.c: consolidate all xxxctl_down() functions
- tracing: Fix sched switch start/stop refcount racy updates
- rcu: Avoid data-race in rcu_gp_fqs_check_wake()
- brcmfmac: Fix memory leak in brcmf_usbdev_qinit
- usb: typec: tcpci: mask event interrupts when remove driver
- usb: gadget: legacy: set max_speed to super-speed
- usb: gadget: f_ncm: Use atomic_t to track in-flight request
- usb: gadget: f_ecm: Use atomic_t to track in-flight request
- ALSA: usb-audio: Fix endianess in descriptor validation
- ALSA: dummy: Fix PCM format loop in proc output
- mm/memory_hotplug: fix remove_memory() lockdep splat
- mm: move_pages: report the number of non-attempted pages
- media/v4l2-core: set pages dirty upon releasing DMA buffers
- media: v4l2-core: compat: ignore native command codes
- media: v4l2-rect.h: fix v4l2_rect_map_inside() top/left adjustments
- lib/test_kasan.c: fix memory leak in kmalloc_oob_krealloc_more()
- irqdomain: Fix a memory leak in irq_domain_push_irq()
- platform/x86: intel_scu_ipc: Fix interrupt support
- ALSA: hda: Add Clevo W65_67SB the power_save blacklist
- KVM: arm64: Correct PSTATE on exception entry
- KVM: arm/arm64: Correct CPSR on exception entry
- KVM: arm/arm64: Correct AArch32 SPSR on exception entry
- KVM: arm64: Only sign-extend MMIO up to register width
- MIPS: fix indentation of the 'RELOCS' message
- MIPS: boot: fix typo in 'vmlinux.lzma.its' target
- s390/mm: fix dynamic pagetable upgrade for hugetlbfs
- powerpc/xmon: don't access ASDR in VMs
- powerpc/pseries: Advance pfn if section is not present in
lmb_is_removable()
- smb3: fix signing verification of large reads
- PCI: tegra: Fix return value check of pm_runtime_get_sync()
- mmc: spi: Toggle SPI polarity, do not hardcode it
- ACPI: video: Do not export a non working backlight interface on MSI
MS-7721
boards
- ACPI / battery: Deal with design or full capacity being reported as -1
- ACPI / battery: Use design-cap for capacity calculations if full-cap is
not
available
- ACPI / battery: Deal better with neither design nor full capacity not
being
reported
- alarmtimer: Unregister wakeup source when module get fails
- ubifs: Reject unsupported ioctl flags explicitly
[Kernel-packages] [Bug 1874062] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-04-21 09:50 EDT--- This setting of the affinity leads to a performance regression in streaming workloads which can be seen with e.g. by an iperf streaming test between two LPARs using ConnectX-5 based nics. In some tests the performance would drop to 20% of the performance with older kernels. -- 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/1874062 Title: [UBUNTU 20.04] Performance floating interrupt Status in linux package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874057] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-04-21 09:56 EDT---
PCI Functions with UIDs >128 are currently not accounted correctly in the
s390x/pci code. Furthermore, the code allows that more than
CONFIG_PCI_NR_FUNCTIONS are created. This can lead to issues with data
structures which were only allocated for CONFIG_PCI_NR_FUNCTIONS.
This has been fixed in the following upstream commit:
969ae01bab2fe938b4c8324836038b5ac1c78fac ("s390/pci: Fix
zpci_alloc_domain() over allocation")
--
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/1874057
Title:
[UBUNTU 20.04] s390x/pci: do not allow to create more pci functions
than configured via CONFIG_PCI_NR_FUNCTIONS
Status in linux package in Ubuntu:
New
Bug description:
Description will follow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874057/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-04-21 09:53 EDT--- Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in linux package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874055] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-04-21 09:41 EDT--- One of the PCI enhancements on Z15 are the enhanced PCI load/store instructions which can be executed directly from user space code. When these instructions are available and preexisting user space code still uses the old s390_pci_mmio_write/read system calls, the system calls fail with an "Unable to handle kernel pointer dereference in virtual kernel address space" in the kernel. This issue affects distributions which have the enablement for Z15 PCI enhancements and where customers run workloads which accesses PCI adapters from user space, e.g. RDMA applications. To solve this, the system call implementation needs to be enhanced to provide to execute enhanced PCI load/store instructions on behalf of the user space application making use of the mappings into its virtual address space -- 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/1874055 Title: [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO instructions are available Status in linux package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
** Merge proposal linked: https://code.launchpad.net/~ubuntu-installer/ubiquity/+git/ubiquity/+merge/382677 -- 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/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874062] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-04-21 09:45 EDT--- With the introduction of CPU directed interrupts the kernel parameter pci=force_floating was introduced to fall back to the previous behavior using floating irqs. Furthermore this fallback is used on machines lacking support for directed interrupts. However we were still setting the affinity in that case, both in __irq_alloc_descs() and via the irq_set_affinity callback in struct irq_chip. -- 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/1874062 Title: [UBUNTU 20.04] Performance floating interrupt Status in linux package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic on Dell XPS 13 9370
Same issue here.
Tried latest firmware (WLAN.RM.4.4.1-00151-QCARMSWPZ-2) but no
improvement .
--
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/1807974
Title:
Wireless regularly breaking (ath10k firmware crashed!) after upgrade
to Cosmic on Dell XPS 13 9370
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
Cosmic. A handful of times per day, my wireless stops working ("?"
appears in the icon in Network Manager). Turning wireless off and then
on again, or suspending and waking the machine up, makes the wireless
work again.
dmesg output is as follows:
$ dmesg | grep ath10k
[ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid
6317c652-4817-4fdd-b6d7-c7b8336e493f)
[ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[ 6646.270369] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
[ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800 29 29 106 107
[ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00 20 19 18 19
[ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000 8 8 10 8
[ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
[ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 6 6
[ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
[ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
[ 6647.239340] ath10k_pci :02:00.0: device successfully recovered
[17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid
03393f2f-0ce1-4017-b711-40dd14f2ec11)
[17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[17641.848065] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
[17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800 6 6 243 244
[17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00 53 52 51 52
[17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5
[17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
[17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 30 30
[17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
[17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
[17642.835601] ath10k_pci :02:00.0: device successfully recovered
[17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
[17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118
I do not recall having any wireless issues before I upgraded (when
this machine was running Bionic).
Bug #1730331 - ath10k_pci: firmware crashed!
Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
could be related, but appear to be related to earlier releases, whereas my
issue has appeared/become much worse on Cosmic.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-11-generic 4.18.0-11.12
ProcVersionSignature: Ubuntu
[Kernel-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot
Perhaps we need some udev plumbing expertise to resolve this. -- 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/1729145 Title: /dev/bcache/by-uuid links not created after reboot Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Bug description: 1. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 2. $ apt-cache policy linux-image-`uname -r` linux-image-4.13.0-16-generic: Installed: 4.13.0-16.19 Candidate: 4.13.0-16.19 Version table: *** 4.13.0-16.19 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3. After creating some bcache devices and rebooting /dev/bcache/by-uuid/ -> ../../bcacheN symlinks point to the current bcache device which is caching the dev.uuid found after creating a backing device. 4. /dev/bcache/by-uuid does not exist and there are not symlinks underneath It appears that since the initramfs loads the bcache module which probes and finds all of the cache devices and backing devices then once the rootfs is mounted and udev gets to run, the bcache kernel module does not emit the CACHED_UUID value into the environment if the underlying devices are already registered. In dmesg, one can see that prior to mounting the rootfs, we see bcache register events: [5.333973] bcache: register_bdev() registered backing device vdb2 [5.354138] bcache: register_bdev() registered backing device vdb4 [5.365665] bcache: register_bdev() registered backing device vdb3 [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 entries, seq 1 [5.428683] bcache: register_cache() registered cache device vdb1 then rootfs ismounted and systemd starts systemd-udev [9.350889] systemd[1]: Listening on udev Kernel Socket. And then the coldplug replay of kernel events triggers /lib/udev/rules.d/69-bcache.rules which invokes /lib/udev/bcache-register which writes the device name (/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the bcache kernel driver attempting to register the block device. However, there is already a bcache device associated already and registration fails [ 11.173141] bcache: register_bcache() error opening /dev/vdb2: device already registered [ 11.184617] bcache: register_bcache() error opening /dev/vdb3: device already registered [ 11.199130] bcache: register_bcache() error opening /dev/vdb1: device already registered [ 11.271694] bcache: register_bcache() error opening /dev/vdb4: device already registered The problem then is that only a kernel call to bch_cached_dev_run() which happens like this: bcache_register() register_bdev() bch_cached_dev_run() kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env); where env includes: "DRIVER=bcache", kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid), NULL, NULL, }; Since that event is not emitted for any previously registered device, then the symlink will not be created. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 31 22:09 seq crw-rw 1 root audio 116, 33 Oct 31 22:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Nov 1 01:39:01 2017 Ec2AMI: ami-030b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware
[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot
Ignore my above 2 comments, posted these to the wrong bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729145 Title: /dev/bcache/by-uuid links not created after reboot Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Bug description: 1. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 2. $ apt-cache policy linux-image-`uname -r` linux-image-4.13.0-16-generic: Installed: 4.13.0-16.19 Candidate: 4.13.0-16.19 Version table: *** 4.13.0-16.19 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3. After creating some bcache devices and rebooting /dev/bcache/by-uuid/ -> ../../bcacheN symlinks point to the current bcache device which is caching the dev.uuid found after creating a backing device. 4. /dev/bcache/by-uuid does not exist and there are not symlinks underneath It appears that since the initramfs loads the bcache module which probes and finds all of the cache devices and backing devices then once the rootfs is mounted and udev gets to run, the bcache kernel module does not emit the CACHED_UUID value into the environment if the underlying devices are already registered. In dmesg, one can see that prior to mounting the rootfs, we see bcache register events: [5.333973] bcache: register_bdev() registered backing device vdb2 [5.354138] bcache: register_bdev() registered backing device vdb4 [5.365665] bcache: register_bdev() registered backing device vdb3 [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 entries, seq 1 [5.428683] bcache: register_cache() registered cache device vdb1 then rootfs ismounted and systemd starts systemd-udev [9.350889] systemd[1]: Listening on udev Kernel Socket. And then the coldplug replay of kernel events triggers /lib/udev/rules.d/69-bcache.rules which invokes /lib/udev/bcache-register which writes the device name (/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the bcache kernel driver attempting to register the block device. However, there is already a bcache device associated already and registration fails [ 11.173141] bcache: register_bcache() error opening /dev/vdb2: device already registered [ 11.184617] bcache: register_bcache() error opening /dev/vdb3: device already registered [ 11.199130] bcache: register_bcache() error opening /dev/vdb1: device already registered [ 11.271694] bcache: register_bcache() error opening /dev/vdb4: device already registered The problem then is that only a kernel call to bch_cached_dev_run() which happens like this: bcache_register() register_bdev() bch_cached_dev_run() kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env); where env includes: "DRIVER=bcache", kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid), NULL, NULL, }; Since that event is not emitted for any previously registered device, then the symlink will not be created. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 31 22:09 seq crw-rw 1 root audio 116, 33 Oct 31 22:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Nov 1 01:39:01 2017 Ec2AMI: ami-030b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware
[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot
For older releases such as bionic we have one event: UDEV [1304.304437] change /devices/virtual/block/bcache0 (block) .ID_FS_TYPE_NEW= ACTION=change CACHED_LABEL= CACHED_UUID=0192e0a7-9d8e-4771-9bb1-d730a2f66a9d DEVLINKS=/dev/bcache/by-uuid/0192e0a7-9d8e-4771-9bb1-d730a2f66a9d DEVNAME=/dev/bcache0 DEVPATH=/devices/virtual/block/bcache0 DEVTYPE=disk DRIVER=bcache ID_FS_TYPE= MAJOR=251 MINOR=0 SEQNUM=4384 SUBSYSTEM=block TAGS=:systemd: USEC_INITIALIZED=1304237024 that creates the expected symlink. - For focal, instead we get two events: UDEV [2763.370729] change /devices/virtual/block/bcache0 (block) ACTION=change DEVPATH=/devices/virtual/block/bcache0 SUBSYSTEM=block DRIVER=bcache CACHED_UUID=1522715e-a390-40db-8d47-06fb728014e5 CACHED_LABEL= DEVNAME=/dev/bcache0 DEVTYPE=disk SEQNUM=5523 USEC_INITIALIZED=2763323504 .ID_FS_TYPE_NEW= ID_FS_TYPE= MAJOR=251 MINOR=0 DEVLINKS=/dev/bcache/by-uuid/1522715e-a390-40db-8d47-06fb728014e5 TAGS=:systemd: KERNEL[2784.362374] change /devices/virtual/block/bcache0 (block) ACTION=change DEVPATH=/devices/virtual/block/bcache0 SUBSYSTEM=block SYNTH_UUID=0 DEVNAME=/dev/bcache0 DEVTYPE=disk SEQNUM=5524 MAJOR=251 MINOR=0 UDEV [2784.433618] change /devices/virtual/block/bcache0 (block) ACTION=change DEVPATH=/devices/virtual/block/bcache0 SUBSYSTEM=block SYNTH_UUID=0 DEVNAME=/dev/bcache0 DEVTYPE=disk SEQNUM=5524 USEC_INITIALIZED=2763323504 ID_FS_UUID=30b28bee-6a1e-423d-9d53-32c78ba5454a ID_FS_UUID_ENC=30b28bee-6a1e-423d-9d53-32c78ba5454a ID_FS_VERSION=1.0 ID_FS_TYPE=ext4 ID_FS_USAGE=filesystem .ID_FS_TYPE_NEW=ext4 MAJOR=251 MINOR=0 DEVLINKS=/dev/disk/by-uuid/30b28bee-6a1e-423d-9d53-32c78ba5454a TAGS=:systemd: This performs: pr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: Processing device (SEQNUM=5523, ACTION=change) Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: Removing watch Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: value '[dmi/id]sys_vendor' is 'QEMU' Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: value '[dmi/id]sys_vendor' is 'QEMU' Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: /usr/lib/udev/rules.d/60-persistent-storage.rules:109 Importing properties from results of builtin command 'blkid' Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: Probe /dev/bcache0 with raid and offset=0 Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: /usr/lib/udev/rules.d/69-bcache.rules:16 Importing properties from results of 'probe-bcache -o udev /dev/bcache0' Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: Starting 'probe-bcache -o udev /dev/bcache0' Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: Successfully forked off '(spawn)' as PID 1912. Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: Process 'probe-bcache -o udev /dev/bcache0' succeeded. Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: /usr/lib/udev/rules.d/69-bcache.rules:27 LINK 'bcache/by-uuid/1522715e-a390-40db-8d47-06fb728014e5' Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: Handling device node '/dev/bcache0', devnum=b251:0 Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: Preserve already existing symlink '/dev/block/251:0' to '../bcache0' Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: Creating symlink '/dev/bcache/by-uuid/1522715e-a390-40db-8d47-06fb728014e5' to '../../bcache0' Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: sd-device: Created db file '/run/udev/data/b251:0' for '/devices/virtual/block/bcache0' Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: Adding watch on '/dev/bcache0' Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: sd-device: Created db file '/run/udev/data/b251:0' for '/devices/virtual/block/bcache0' Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: Device (SEQNUM=5523, ACTION=change) processed Apr 21 14:15:22 ubuntu-focal systemd-udevd[1870]: bcache0: sd-device-monitor: Passed 388 byte to netlink monitor followed by the extra action: Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: bcache0: Processing device (SEQNUM=5524, ACTION=change) Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: bcache0: Removing watch Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: value '[dmi/id]sys_vendor' is 'QEMU' Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: value '[dmi/id]sys_vendor' is 'QEMU' Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: bcache0: /usr/lib/udev/rules.d/60-persistent-storage.rules:109 Importing properties from results of builtin command 'blkid' Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: bcache0: Probe /dev/bcache0 with raid and offset=0 Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: bcache0: /usr/lib/udev/rules.d/60-persistent-storage.rules:112 LINK 'disk/by-uuid/30b28bee-6a1e-423d-9d53-32c78ba5454a' Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: bcache0: Updating old name, '/dev/bcache/by-uuid/1522715e-a390-40db-8d47-06fb728014e5' no longer belonging to
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
The good news is that the bcache events are reaching udev, however the /usr/lib/udev/rules.d/60-persistent-storage.rules rules may need to be modified to ignore bcache specific events. -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed-5.4 package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
