[Kernel-packages] [Bug 1851469] [NEW] Incorrect raspi2 snapcraft.yaml file
Public bug reported: [Impact] The current snapcraft.yaml file on the raspi2 branch is the one from the main/master kernel and not the raspi2 version. [Test Case] Compare snapcraft.yaml from the affected series with the version from bionic:linux-raspi2. [Fix] Update snapcraft.yaml. [Regression Potential] Low, since it's currently completely broken. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1851469 Title: Incorrect raspi2 snapcraft.yaml file Status in linux-raspi2 package in Ubuntu: New Bug description: [Impact] The current snapcraft.yaml file on the raspi2 branch is the one from the main/master kernel and not the raspi2 version. [Test Case] Compare snapcraft.yaml from the affected series with the version from bionic:linux-raspi2. [Fix] Update snapcraft.yaml. [Regression Potential] Low, since it's currently completely broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1851469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849022] Re: bionic/linux-oracle: 4.15.0-1028.31 -proposed tracker
4.15.0-1028.31 - oracle Regression test CMPL, RTB. Issue to note in oracle (amd64): ubuntu_kernel_selftests - raw_skew in timer (bug 1811194) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) apic-split timeouted (bug 1821390) access (bug 1831451) pmu (bug 1751000) port80 (bug 1748105) vmx (bug 1821394) vmx_apicv_test (bug 1827866) vmx_apic_passthrough_thread (bug 1822309) vmx_hlt_with_rvi_test (bug 1822308) ubunut_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ltp_acpi (bug 1830676) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01, statx04 (bug 1842266) fallocate05 (bug 1783880) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266) stime01 (bug 1845620) Skipped / blacklisted: * libhugetlbfs * ubuntu_seccomp ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1849022 Title: bionic/linux-oracle: 4.15.0-1028.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849855 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 23. October 2019 09:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1849021 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849022/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827980] Re: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM
Passed with Oracle B-4.15 (node VM.DenseIO1.8 / VM.Standard1.4) -- 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/1827980 Title: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM 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 timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -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_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV 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 ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (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:36:32 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/1827980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Passed with Oracle B-4.15 (node VM.DenseIO1.8 / VM.Standard1.4) -- 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 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 1848978] Re: CML: perf enabling for core
** Changed in: linux-oem-osp1 (Ubuntu Bionic) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided => High -- 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/1848978 Title: CML: perf enabling for core Status in intel: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: Confirmed Bug description: Description: CML perf enabling for core v5.4-rc3 1ffa6c04dae39776a3c222bdf88051e394386c01 9066288b2aab1804dc1eebec6ff88474363b89cb 9674b1cc0f94c34f76e58c102623a866836f269e Target Kernel: 5.4 Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1848978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848127] Comment bridged from LTC Bugzilla
--- Comment From pavsu...@in.ibm.com 2019-11-06 01:44 EDT--- root@ltc-wspoon11:~# add-apt-repository ppa:ubuntu-power-triage/lp1848127 More info: https://launchpad.net/~ubuntu-power-triage/+archive/ubuntu/lp1848127 Press [ENTER] to continue or Ctrl-c to cancel adding it. Get:1 file:/var/cuda-repo-10-1-local-10.1.152-418.67 InRelease Ign:1 file:/var/cuda-repo-10-1-local-10.1.152-418.67 InRelease Get:2 file:/var/cuda-repo-10-1-local-10.1.152-418.67 Release [574 B] Get:2 file:/var/cuda-repo-10-1-local-10.1.152-418.67 Release [574 B] Hit:4 http://us.ports.ubuntu.com/ubuntu-ports bionic InRelease Hit:5 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates InRelease Hit:6 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease Ign:7 http://ddebs.ubuntu.com bionic InRelease Hit:8 http://us.ports.ubuntu.com/ubuntu-ports bionic-backports InRelease Ign:9 http://ddebs.ubuntu.com bionic-updates InRelease Hit:10 http://ppa.launchpad.net/ubuntu-power-triage/lp1848127/ubuntu bionic InRelease Ign:11 http://ddebs.ubuntu.com bionic-proposed InRelease Hit:12 http://ddebs.ubuntu.com bionic Release Hit:14 http://ddebs.ubuntu.com bionic-updates Release Hit:16 http://ddebs.ubuntu.com bionic-proposed Release Reading package lists... Done root@ltc-wspoon11:~# apt-get update Get:1 file:/var/cuda-repo-10-1-local-10.1.152-418.67 InRelease Ign:1 file:/var/cuda-repo-10-1-local-10.1.152-418.67 InRelease Get:2 file:/var/cuda-repo-10-1-local-10.1.152-418.67 Release [574 B] Get:2 file:/var/cuda-repo-10-1-local-10.1.152-418.67 Release [574 B] Hit:4 http://us.ports.ubuntu.com/ubuntu-ports bionic InRelease Hit:5 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates InRelease Ign:6 http://ddebs.ubuntu.com bionic InRelease Hit:7 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease Hit:8 http://us.ports.ubuntu.com/ubuntu-ports bionic-backports InRelease Hit:9 http://ppa.launchpad.net/ubuntu-power-triage/lp1848127/ubuntu bionic InRelease Ign:10 http://ddebs.ubuntu.com bionic-updates InRelease Ign:11 http://ddebs.ubuntu.com bionic-proposed InRelease Hit:12 http://ddebs.ubuntu.com bionic Release Hit:14 http://ddebs.ubuntu.com bionic-updates Release Hit:16 http://ddebs.ubuntu.com bionic-proposed Release Reading package lists... Done root@ltc-wspoon11:~# apt-get install linux-image-unsigned-4.15.0-68-generic/bionic Reading package lists... Done Building dependency tree Reading state information... Done Selected version '4.15.0-68.77~lp1848127+build.1' (lp1848127:18.04/bionic [ppc64el]) for 'linux-image-unsigned-4.15.0-68-generic' The following additional packages will be installed: linux-modules-4.15.0-68-generic Suggested packages: fdutils linux-doc-4.15.0 | linux-source-4.15.0 linux-headers-4.15.0-68-generic The following NEW packages will be installed: linux-image-unsigned-4.15.0-68-generic linux-modules-4.15.0-68-generic 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 18.6 MB of archives. After this operation, 92.8 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://ppa.launchpad.net/ubuntu-power-triage/lp1848127/ubuntu bionic/main ppc64el linux-modules-4.15.0-68-generic ppc64el 4.15.0-68.77~lp1848127+build.1 [12.1 MB] Get:2 http://ppa.launchpad.net/ubuntu-power-triage/lp1848127/ubuntu bionic/main ppc64el linux-image-unsigned-4.15.0-68-generic ppc64el 4.15.0-68.77~lp1848127+build.1 [6,532 kB] Fetched 18.6 MB in 6s (3,277 kB/s) Selecting previously unselected package linux-modules-4.15.0-68-generic. (Reading database ... 183240 files and directories currently installed.) Preparing to unpack .../linux-modules-4.15.0-68-generic_4.15.0-68.77~lp1848127+build.1_ppc64el.deb ... Unpacking linux-modules-4.15.0-68-generic (4.15.0-68.77~lp1848127+build.1) ... Selecting previously unselected package linux-image-unsigned-4.15.0-68-generic. Preparing to unpack .../linux-image-unsigned-4.15.0-68-generic_4.15.0-68.77~lp1848127+build.1_ppc64el.deb ... Unpacking linux-image-unsigned-4.15.0-68-generic (4.15.0-68.77~lp1848127+build.1) ... Setting up linux-modules-4.15.0-68-generic (4.15.0-68.77~lp1848127+build.1) ... Setting up linux-image-unsigned-4.15.0-68-generic (4.15.0-68.77~lp1848127+build.1) ... I: /boot/vmlinux.old is now a symlink to vmlinux-4.15.0-66-generic I: /boot/initrd.img.old is now a symlink to initrd.img-4.15.0-66-generic I: /boot/vmlinux is now a symlink to vmlinux-4.15.0-68-generic I: /boot/initrd.img is now a symlink to initrd.img-4.15.0-68-generic Processing triggers for linux-image-unsigned-4.15.0-68-generic (4.15.0-68.77~lp1848127+build.1) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 4.15.0-68-generic Error! Your kernel headers for kernel 4.15.0-68-generic cannot be found. Please install the linux-headers-4.15.0-68-generic package, or use the --kernelsourcedir option to tell DKMS where it's located ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating
[Kernel-packages] [Bug 1824228] Re: ept test fails in kvm_unit_tests
Passed with Oracle B-4.15 (node VM.DenseIO1.8 / VM.Standard1.4) -- 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 400312
[Kernel-packages] [Bug 1751000] Re: pmu test in kvm-unit-test failed on X-hwe ARM64 system
The pmu failure could be found on Oracle B-4.15 as well:
Running 'kvm-ok'
INFO: /dev/kvm exists
KVM acceleration can be used
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/pmu'
BUILD_HEAD=e2c275c4
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 /tmp/tmp.p5vxZITKIQ -smp 1
-cpu host # -initrd /tmp/tmp.ndP8Idxxbw
enabling apic
paging enabled
cr0 = 80010011
cr3 = 45a000
cr4 = 20
PMU version: 2
GP counters: 4
GP counter width: 48
Mask length: 7
Fixed counters: 3
Fixed counter width: 48
PASS: core cycles-0
PASS: core cycles-1
PASS: core cycles-2
PASS: core cycles-3
PASS: instructions-0
PASS: instructions-1
PASS: instructions-2
PASS: instructions-3
PASS: ref cycles-0
PASS: ref cycles-1
PASS: ref cycles-2
PASS: ref cycles-3
PASS: llc refference-0
PASS: llc refference-1
PASS: llc refference-2
PASS: llc refference-3
PASS: llc misses-0
PASS: llc misses-1
PASS: llc misses-2
PASS: llc misses-3
PASS: branches-0
PASS: branches-1
PASS: branches-2
PASS: branches-3
PASS: branch misses-0
PASS: branch misses-1
PASS: branch misses-2
PASS: branch misses-3
PASS: fixed-0
PASS: fixed-1
PASS: fixed-2
PASS: rdpmc: cntr-0
PASS: rdpmc: fast-0
PASS: rdpmc: cntr-1
PASS: rdpmc: fast-1
PASS: rdpmc: cntr-2
PASS: rdpmc: fast-2
PASS: rdpmc: cntr-3
PASS: rdpmc: fast-3
FAIL: rdpmc: fixed cntr-0
PASS: rdpmc: fixed fast-0
FAIL: rdpmc: fixed cntr-1
PASS: rdpmc: fixed fast-1
FAIL: rdpmc: fixed cntr-2
PASS: rdpmc: fixed fast-2
FAIL: all counters
PASS: overflow: cntr-0
PASS: overflow: status-0
PASS: overflow: status clear-0
PASS: overflow: irq-0
PASS: overflow: cntr-1
PASS: overflow: status-1
PASS: overflow: status clear-1
PASS: overflow: irq-1
PASS: overflow: cntr-2
PASS: overflow: status-2
PASS: overflow: status clear-2
PASS: overflow: irq-2
PASS: overflow: cntr-3
PASS: overflow: status-3
PASS: overflow: status clear-3
PASS: overflow: irq-3
PASS: overflow: cntr-4
PASS: overflow: status-4
PASS: overflow: status clear-4
PASS: overflow: irq-4
PASS: cmask
SUMMARY: 67 tests, 4 unexpected failures
FAIL pmu (67 tests, 4 unexpected failures)
** Tags added: bionic linux-oracle
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Tags added: sru-20191021 ubuntu-kvm-unit-tests
** Tags added: 4.15
--
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/1751000
Title:
pmu test in kvm-unit-test failed on X-hwe ARM64 system
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Triaged
Bug description:
This failure could be found on both Moonshot and Cavium ThunderX ARM64
systems.
Steps:
1. Install necessary packages
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. TESTNAME=pmu TIMEOUT=90s ACCEL= ./arm/run arm/pmu.flat -smp 1
Result:
timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev
-display none -serial stdio -kernel arm/pmu.flat -smp 1 # -initrd
/tmp/tmp.H8ucGrg46U
INFO: PMU version: 3
INFO: pmu: PMU implementer/ID code/counters: 0(" ")/0/0
FAIL: pmu: Control register
Read 0 then 0.
FAIL: pmu: Monotonically increasing cycle count
instrs : cycles0 cycles1 ...
4:0
cycles not incrementing!
FAIL: pmu: Cycle/instruction ratio
SUMMARY: 3 tests, 3 unexpected failures
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic aarch64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: arm64
Date: Thu Feb 22 08:29:15 2018
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Feb 22 08:24 seq
crw-rw 1 root audio 116, 33 Feb 22 08:24 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: arm64
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:
CurrentDmesg:
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
[Kernel-packages] [Bug 1827979] Re: pcid in ubuntu_kvm_unit_tests failed on B-KVM
Passed with B-4.15 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/1827979 Title: pcid in ubuntu_kvm_unit_tests failed on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: FAIL pcid (3 tests, 1 unexpected failures) # TESTNAME=pcid TIMEOUT=90s ACCEL= ./x86/run x86/pcid.flat -smp 1 -cpu qemu64,+pcid 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/pcid.flat -smp 1 -cpu qemu64,+pcid # -initrd /tmp/tmp.a4xQyF7juj qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] enabling apic PASS: CPUID consistency PASS: Test on PCID when disabled FAIL: Test on INVPCID when disabled SUMMARY: 3 tests, 1 unexpected failures 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:31:38 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/1827979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831451] Re: access in ubuntu_kvm_unit_tests failed on Oracle X-4.15
On Oracle B-4.15, this is failing but showing a false-negative: Running 'kvm-ok' INFO: /dev/kvm exists KVM acceleration can be used '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/access' BUILD_HEAD=e2c275c4 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 /tmp/tmp.XgEpCZkIT8 -smp 1 -cpu host # -initrd /tmp/tmp.D1EaS2gEGt enabling apic starting test run CR4.PKE not available, disabling PKE tests qemu-system-x86_64: terminating on signal 15 from pid 11786 (timeout) .FAIL access (timeout; duration=90s) ** Summary changed: - access in ubuntu_kvm_unit_tests failed on Oracle X-4.15 + access in ubuntu_kvm_unit_tests failed on Oracle X/B-4.15 ** Tags added: bionic sru-20191021 -- 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/1831451 Title: access in ubuntu_kvm_unit_tests failed on Oracle X/B-4.15 Status in ubuntu-kernel-tests: New Status in linux-oracle package in Ubuntu: New Bug description: Need to run this on oracle manually to get the full output: TESTNAME=access TIMEOUT=90s ACCEL= ./x86/run x86/access.flat -smp 1 -cpu host FAIL access (timeout; duration=90s) But so far Oracle X-4.15 is the only cloud that's failing with this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
** Changed in: ubuntu-power-systems Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Disco) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => 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/1848127 Title: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [IMPACT] MCE test renders the system unresponsive on P9 open power hardware (Withersoon) [TEST] A test kernel is available in ppa:ubuntu-power-triage/lp1848127. Please see the [OTHER] section for test details and comment #7 for results with the PPA kernel. [FIX] IBM has identified the following patch that fixes this issue: commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee Author: Balbir Singh Date: Tue Aug 20 13:43:47 2019 +0530 powerpc/mce: Fix MCE handling for huge pages [REGRESSION POTENTIAL] The patch is applicable the powerpc architecture and limited in scope to MCE handling for huge pages. Patch does not touch any generic code. Regression if any is limited to powerpc MCE handling. [OTHER] == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v2.3-rc2-58-g59fd0743 buildroot-2019.02.2-17-g93b841d204 skiboot-v6.3-rc2 hostboot-19a436e occ-58e422d linux-5.0.9-openpower1-p3a4d5a4 petitboot-v1.10.3 machine-xml-a6f4df3 hostboot-binaries-hw043019a.940 capp-ucode-p9-dd2-v4 sbe-249671d hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs: 100 101 102 103 CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs: 104 105 106 107 CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs: 108 109 110 111 CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs: 112 113 114 115 CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs: 116 117 118 119 CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs: 120 121 122 123 CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs: 124 125 126 127 CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs: 128 129 130 131 CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs: 132 133 134 135 CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs: 136 137 138 139 CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs: 140 141 142 143
[Kernel-packages] [Bug 1844155] Re: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes
I completely missed the verification ping here in the sea of other kernel bug mail that I get. Will work with the LP team to get this verified as quickly as I can, but if you need to make a revert/ship call before I can, the patches should be pretty harmless even if they don't fix the bug, so I'd vote for keep and ship and we can fix later if we missed a bit. -- 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/1844155 Title: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux package in Debian: Fix Released Bug description: [Impact] The arm64 kernel allows one to run aarch32 processes on an aarch64 processor, using the standard 32/64-bit syscall compatibility. However this compat layer does not correctly validate the arguments of the sigaltstack syscall which can result in process failures. [Test Case] The simple reproducer from https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=904385 triggers a memory allocation error with the current Xenial 4.4 kernel. [Fix] Backport the following two upstream commits: 24951465cbd2 arm64: compat: Provide definition for COMPAT_SIGMINSTKSZ 22839869f21a signal: Introduce COMPAT_SIGMINSTKSZ for use in compat_sys_sigaltstack With these two commits, the reproducer no longer fails. [Regression Potential] Low. the modifications are trivial and the two patches have been in upstream for quite a while. [Original Description] This seems to have been fixed in 4.15 (finally), but is still an issue in the 4.4 kernel used on our builders, and possibly others as well (needs investigation). The original Debian bug report linked has more info, as well as the patchset on lkml at https://lkml.org/lkml/2018/7/25/409 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848978] Re: CML: perf enabling for core
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux-oem-osp1 (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/1848978 Title: CML: perf enabling for core Status in intel: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: Confirmed Bug description: Description: CML perf enabling for core v5.4-rc3 1ffa6c04dae39776a3c222bdf88051e394386c01 9066288b2aab1804dc1eebec6ff88474363b89cb 9674b1cc0f94c34f76e58c102623a866836f269e Target Kernel: 5.4 Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1848978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831449] Re: memory in ubuntu_kvm_unit_tests failed on Oracle X-4.15
Passed on VM.DenseIO1.8 and VM.Standard1.4 for Oracle B-4.15 ** Summary changed: - memory in ubuntu_kvm_unit_tests failed on Oracle X-4.15 + memory in ubuntu_kvm_unit_tests failed on Oracle X/B-4.15 -- 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/1831449 Title: memory in ubuntu_kvm_unit_tests failed on Oracle X/B-4.15 Status in ubuntu-kernel-tests: New Status in linux-oracle package in Ubuntu: New Bug description: Need to run this on oracle manually to get the full output: TESTNAME=memory TIMEOUT=90s ACCEL= ./x86/run x86/memory.flat -smp 1 -cpu host FAIL memory (8 tests, 2 unexpected failures) But so far Oracle X-4.15 is the only cloud that's failing with this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Testing phase-changed: Tuesday, 05. November 2019 23:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Testing phase-changed: Tuesday, 05. November 2019 23:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851464] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) 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/1851464 Title: Unable to install X-hwe-edge meta package Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: It works 4 days ago, but now when you try to install the meta package, it will fail with: $ sudo apt install linux-lowlatency-hwe-16.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-lowlatency-hwe-16.04-edge : Depends: linux-image-lowlatency-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed Depends: linux-headers-lowlatency-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt install linux-generic-hwe-16.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-generic-hwe-16.04-edge : Depends: linux-image-generic-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed Depends: linux-headers-generic-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-167-generic 4.4.0-167.196 ProcVersionSignature: User Name 4.4.0-167.196-generic 4.4.197 Uname: Linux 4.4.0-167-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 6 06:03 seq crw-rw 1 root audio 116, 33 Nov 6 06:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Nov 6 06:38:39 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R320 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-167-generic root=UUID=7e417b15-9c42-401c-b706-06eb693e6d19 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-167-generic N/A linux-backports-modules-4.4.0-167-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0DY523 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R320 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848978] Re: CML: perf enabling for core
** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848978 Title: CML: perf enabling for core Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: New Bug description: Description: CML perf enabling for core v5.4-rc3 1ffa6c04dae39776a3c222bdf88051e394386c01 9066288b2aab1804dc1eebec6ff88474363b89cb 9674b1cc0f94c34f76e58c102623a866836f269e Target Kernel: 5.4 Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1848978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851464] [NEW] Unable to install X-hwe-edge meta package
Public bug reported: It works 4 days ago, but now when you try to install the meta package, it will fail with: $ sudo apt install linux-lowlatency-hwe-16.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-lowlatency-hwe-16.04-edge : Depends: linux-image-lowlatency-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed Depends: linux-headers-lowlatency-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt install linux-generic-hwe-16.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-generic-hwe-16.04-edge : Depends: linux-image-generic-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed Depends: linux-headers-generic-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-167-generic 4.4.0-167.196 ProcVersionSignature: User Name 4.4.0-167.196-generic 4.4.197 Uname: Linux 4.4.0-167-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 6 06:03 seq crw-rw 1 root audio 116, 33 Nov 6 06:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Nov 6 06:38:39 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R320 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-167-generic root=UUID=7e417b15-9c42-401c-b706-06eb693e6d19 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-167-generic N/A linux-backports-modules-4.4.0-167-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0DY523 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R320 dmi.sys.vendor: Dell Inc. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: apport-bug i386 package-from-proposed uec-images xenial ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests 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/1851464 Title: Unable to install X-hwe-edge meta package Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: It works 4 days ago, but now when you try to install the meta package, it will fail with: $ sudo apt install linux-lowlatency-hwe-16.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-lowlatency-hwe-16.04-edge : Depends: linux-image-lowlatency-hwe-16.04-edge (= 4.15.0.67.84) but it is not going to be installed Depends:
[Kernel-packages] [Bug 1850886] Re: Auto-rotate is not working properly when system is booted up while not in its regular orientation
Hi Bin, Ok, I'll take note of this. Thank you very much! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1850886 Title: Auto-rotate is not working properly when system is booted up while not in its regular orientation Status in GNOME Shell: New Status in linux-meta-oem package in Ubuntu: Confirmed Bug description: [RELEASE VERSION] Description: Ubuntu 18.04.3 LTS Release: 18.04 [PACKAGE VERSION] linux-oem: Installed: 4.15.0.1057.61 Candidate: 4.15.0.1057.61 Version table: *** 4.15.0.1057.61 500 500 http://jp.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1004.2 500 500 http://jp.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [EXPECTED OUTPUT] Upon boot up with auto-rotation enabled, display should show the proper screen orientation of the system accordingly [ACTUAL OUTPUT] Auto-rotation is not working properly when system is booted up while not in its regular orientation [STEPS] 1. Make sure auto-rotation is enabled on the system 2. Before turning the system on, put it on tablet mode, with the inverted landscape rotation (the top part/the part with the camera is adjacent to the surface). The system should follow this orientation when the login screen appears. 3. Login to the system 4. Switch to the clam shell mode. The display suddenly becomes inverted/the opposite direction of the expected output. 5. Switch back to the tablet mode. The display also ends up being inverted/in the opposite direction of the expected output [REMARKS] *Using WHL *The system seems to be setting the orientation according to the orientation during boot up ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21 Uname: Linux 5.0.0-1024-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 14:23:14 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso InstallationDate: Installed on 2019-07-25 (98 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1850886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848127] Comment bridged from LTC Bugzilla
--- Comment From pavsu...@in.ibm.com 2019-11-06 01:01 EDT--- I have installed both the Bionic *and* Disco kernels available in PPA: https://launchpad.net/~ubuntu-power-triage/+archive/ubuntu/lp1848127 Then executed the MCE UE tests again on the machine with both the kernels. root@ltc-wspoon4:~# apt-get install linux-image-unsigned-5.0.0-33-generic/disco Reading package lists... Done Building dependency tree Reading state information... Done Selected version '5.0.0-33.35~lp1848127+build.1' (lp1848127:19.04/disco [ppc64el]) for 'linux-image-unsigned-5.0.0-33-generic' The following additional packages will be installed: linux-modules-5.0.0-33-generic Suggested packages: fdutils linux-doc-5.0.0 | linux-source-5.0.0 linux-headers-5.0.0-33-generic The following NEW packages will be installed: linux-image-unsigned-5.0.0-33-generic linux-modules-5.0.0-33-generic 0 upgraded, 2 newly installed, 0 to remove and 3 not upgraded. Need to get 20.7 MB of archives. After this operation, 106 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://ppa.launchpad.net/ubuntu-power-triage/lp1848127/ubuntu disco/main ppc64el linux-modules-5.0.0-33-generic ppc64el 5.0.0-33.35~lp1848127+build.1 [14.0 MB] Get:2 http://ppa.launchpad.net/ubuntu-power-triage/lp1848127/ubuntu disco/main ppc64el linux-image-unsigned-5.0.0-33-generic ppc64el 5.0.0-33.35~lp1848127+build.1 [6,748 kB] Fetched 20.7 MB in 13s (1,546 kB/s) Selecting previously unselected package linux-modules-5.0.0-33-generic. (Reading database ... 71699 files and directories currently installed.) Preparing to unpack .../linux-modules-5.0.0-33-generic_5.0.0-33.35~lp1848127+build.1_ppc64el.deb ... Unpacking linux-modules-5.0.0-33-generic (5.0.0-33.35~lp1848127+build.1) ... Selecting previously unselected package linux-image-unsigned-5.0.0-33-generic. Preparing to unpack .../linux-image-unsigned-5.0.0-33-generic_5.0.0-33.35~lp1848127+build.1_ppc64el.deb ... Unpacking linux-image-unsigned-5.0.0-33-generic (5.0.0-33.35~lp1848127+build.1) ... Setting up linux-modules-5.0.0-33-generic (5.0.0-33.35~lp1848127+build.1) ... Setting up linux-image-unsigned-5.0.0-33-generic (5.0.0-33.35~lp1848127+build.1) ... I: /boot/vmlinux is now a symlink to vmlinux-5.0.0-33-generic I: /boot/initrd.img is now a symlink to initrd.img-5.0.0-33-generic Processing triggers for linux-image-unsigned-5.0.0-33-generic (5.0.0-33.35~lp1848127+build.1) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.0.0-33-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinux-5.0.0-33-generic Found initrd image: /boot/initrd.img-5.0.0-33-generic Found linux image: /boot/vmlinux-5.0.0-32-generic Found initrd image: /boot/initrd.img-5.0.0-32-generic done root@ltc-wspoon4:~# uname -a Linux ltc-wspoon4 5.0.0-33-generic #35~lp1848127+build.1-Ubuntu SMP Mon Oct 28 20:12:03 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon4:~# cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco root@ltc-wspoon4:~# ./statedisable.sh ./statedisable.sh: line 10: /sys/devices/system/cpu/cpu*/cpuidle/state7/disable: No such file or directory ./statedisable.sh: line 11: /sys/devices/system/cpu/cpu*/cpuidle/state8/disable: No such file or directory root@ltc-wspoon4:~# ./run_workload.sh root@ltc-wspoon4:~# ./scom_addr_p9.sh 0x1001080c 6 EQ[ 1]: 0x1101080c EX[ 3]: 0x11010c0c C[ 6]: 0x3601080c root@ltc-wspoon4:~# getscom -c 0x8 0x11010c0c root@ltc-wspoon4:~# putscom -c 0x8 0x11010c0c 0c00 0c00 ltc-wspoon4 login: [ 442.228985] NIP [c019ae5c]: osq_lock+0x15c/0x230 [ 442.228985] Initiator: CPU [ 442.228986] Error type: UE [Load/Store] [ 442.228987] Effective address: c000201cc76a9600 [ 442.228988] Physical address: 201cc76a [ 442.228988] opal: Hardware platform error: Unrecoverable Machine Check exception [ 442.228989] CPU: 109 PID: 9095 Comm: find Tainted: G M 5.0.0-33-generic #35~lp1848127+build.1-Ubuntu [ 442.228990] NIP: c019ae5c LR: c0e000a0 CTR: c0446e30 [ 442.228991] REGS: c000201fff24bd70 TRAP: 0200 Tainted: G
[Kernel-packages] [Bug 1850886] Re: Auto-rotate is not working properly when system is booted up while not in its regular orientation
Grace, I tried the latest gnome-shell 3.34.1 on 5.2.0 kernel, this issue is fixed. So I thought the upstream already met this issue before. I will need more time to find the root cause and patches. It's a little hard to have a target date for me to resolve this issue, it also depends the people from the ubuntu desktop team, I will do my best and hope find related patches at this week. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1850886 Title: Auto-rotate is not working properly when system is booted up while not in its regular orientation Status in GNOME Shell: New Status in linux-meta-oem package in Ubuntu: Confirmed Bug description: [RELEASE VERSION] Description: Ubuntu 18.04.3 LTS Release: 18.04 [PACKAGE VERSION] linux-oem: Installed: 4.15.0.1057.61 Candidate: 4.15.0.1057.61 Version table: *** 4.15.0.1057.61 500 500 http://jp.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1004.2 500 500 http://jp.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [EXPECTED OUTPUT] Upon boot up with auto-rotation enabled, display should show the proper screen orientation of the system accordingly [ACTUAL OUTPUT] Auto-rotation is not working properly when system is booted up while not in its regular orientation [STEPS] 1. Make sure auto-rotation is enabled on the system 2. Before turning the system on, put it on tablet mode, with the inverted landscape rotation (the top part/the part with the camera is adjacent to the surface). The system should follow this orientation when the login screen appears. 3. Login to the system 4. Switch to the clam shell mode. The display suddenly becomes inverted/the opposite direction of the expected output. 5. Switch back to the tablet mode. The display also ends up being inverted/in the opposite direction of the expected output [REMARKS] *Using WHL *The system seems to be setting the orientation according to the orientation during boot up ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21 Uname: Linux 5.0.0-1024-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 14:23:14 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso InstallationDate: Installed on 2019-07-25 (98 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1850886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841730] Re: kernel error, crush ext4
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841730 Title: kernel error, crush ext4 Status in linux package in Ubuntu: Expired Bug description: Use kernel 5.0.0-25. dmesg in attachment belong second system. (first system) After update and reboot system start kernel 5.0.0-25 and after about 2 hours appear tiring and frize, after reboot kernel send error mount home partition, "fsck -f" return error file system. After that i reinstall system and format all partitions. (second system) after reinstall i installed all my applications and updates system, and get error againt, after load kernel 4.18.0-15 errors no appeared. I use gpd pocket 2. thank you for youre work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849019] Re: bionic/linux-kvm: 4.15.0-1049.49 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849855 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 22. October 2019 13:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- 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/1849019 Title: bionic/linux-kvm: 4.15.0-1049.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849855 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 22. October 2019 13:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823684] Re: Touchpad right click does not work as expected on Dell G7 7588
Hi Jan Johansson, your issue seems to be different, probably a 4.4 kernel regression. Can you please: 1. Open a new bug with "ubuntu-bug linux" command in your terminal (ctrl + alt + t) 2. Try to boot with an older kernel (prior than 4.4.0-166) from grub, to confirm if it works with older kernel. 3. Add your test result to the report opened in 1. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1823684 Title: Touchpad right click does not work as expected on Dell G7 7588 Status in linux-signed package in Ubuntu: Confirmed Bug description: The right button on the touchpad of this system does not work as expected, the click event will get treated as a regular left click. $ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ DELL0825:00 06CB:7E92 Touchpad id=12 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=11 [slave keyboard (3)] ↳ Intel HID 5 button arrayid=13 [slave keyboard (3)] ↳ Intel HID eventsid=14 [slave keyboard (3)] ↳ Dell WMI hotkeysid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] xev for left click and right click: ButtonPress event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 304106, (167,148), root:(357,319), state 0x10, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 304146, (167,148), root:(357,319), state 0x110, button 1, same_screen YES ButtonPress event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 309562, (167,148), root:(357,319), state 0x10, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 309563, (167,148), root:(357,319), state 0x110, button 1, same_screen YES ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 17:50:24 2019 InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1823684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847192] Re: drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL platforms
** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1847192 Title: drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL platforms Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: Since Bionic kernel doesn't support ICL platforms (i915), so these two patches will not be sent to Bionic kernel. [Impact] On the ICL platforms, the hdmi can't work well, the audio driver will print "azx_get_response timeout" randomly, then the whole audio doesn't work anymore. [Fix] Intel provide these two fixes to us, and we tested these two patches, it really fixed the issue. [Test Case] Boot and check the hdmi audio, then suspend and resume, check the hdmi audio, all work well. [Regression Risk] Low, Only enable the audio PIN and enable the clock for ICL. we tested on both ICL and non-ICL, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848490] Re: eoan: alsa/sof: Enable SOF_HDA link and codec
I tested 5.3.0-21-generic kernel on lenovo x1 carbon 7th, with the help of ucm and blacklist of snd_hda_intel and snd_soc_skl, all audio worked well. verification done. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1848490 Title: eoan: alsa/sof: Enable SOF_HDA link and codec Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] We tested the EOAN kernel on the LENOVO or Dell machines which have dmic directly connnected to PCH, the dmic didn't work. [Fix] We need to enable SOF_HDA link and codec, then the sof driver and Legacy HDA driver work together to make the dmic work. [Test Case] Install the latest 19.10 image, build a new kernel with this patch and replace the existing kernel, After installing the blacklist package (blacklist snd_hda_intel and snd_soc_skl) and ucm package, the dmic and all output devices (speaker/hdmi) work. [Regression Risk] Low, these configs are already enabled in the oem-b-osp1 kernel for a long time, and we tested it on many lenovo/dell machines witch have or have no dmic, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850896] Re: eoan/linux-raspi2: 5.3.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850486 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 01. November 2019 15:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- 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/1850896 Title: eoan/linux-raspi2: 5.3.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850486 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 01. November 2019 15:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838245] Re: dkms script is missing function find_module
The new feature landing missed that fix.
It impacts eoan and disco.
The bionic carried that fix , and Focal is supposed to just land latest code
from upstream, so they will not be impacted.
Sorry for inconvenient, I'll send a new patch to fix it on eoan and
disco today.
** Changed in: dkms
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1838245
Title:
dkms script is missing function find_module
Status in DKMS:
Confirmed
Status in dkms package in Ubuntu:
Confirmed
Status in dkms source package in Bionic:
Fix Released
Bug description:
update for SRU process:
[Impact]
1. dkms script is missing function find_module
2. priority of OBSOLETE_BY should higher than "force". #89
https://github.com/dell/dkms/issues/89
[Test case]
install the dkms which already patched (also can be found in my ppa[1])
1. install a dkms which for a kernel module system already installed.
e.g. ath10k of my testing ppa : [1]
1.1. the dkms can be installed well.
2. install a dkms which has OBSOLETE_BY and FORCE
e.g.ath10k of my testing ppa : [1] (source code in [2])
- the target dkms defined OBSOLETE_BY and FORCE
- user install dkms on a system which installed kernel version less than
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
- the dkms can be installed well.
[Regression potential]
medium as it touched the version sanity. This change correct the code logic
and land one more change from upstream as well.
The logic has been verified by #5 and me.
Building a kernel module using dkms in Linux Mint 19.1 shows the following
error:
Running module version sanity check.
/usr/sbin/dkms: Zeile 784: find_module: Befehl nicht gefunden
modinfo: ERROR: missing module or filename.
Checking the file the function is indeed missing and another user
confirmed, that it was removed at some point:
https://github.com/linuxmint/linuxmint/issues/142
Possible solution: Readd
find_module()
{
# tree = $1
# module = $2
find "$1" -name "$2$module_uncompressed_suffix" -o -name
"$2$module_suffix" -type f
return $?
}
as found in https://github.com/dell/dkms/blob/master/dkms
To manage notifications about this bug go to:
https://bugs.launchpad.net/dkms/+bug/1838245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847192] Re: drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL platforms
@Hui - Thanks for verifying this on Bionic. Could you please do the same for eoan? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847192 Title: drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL platforms Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: Since Bionic kernel doesn't support ICL platforms (i915), so these two patches will not be sent to Bionic kernel. [Impact] On the ICL platforms, the hdmi can't work well, the audio driver will print "azx_get_response timeout" randomly, then the whole audio doesn't work anymore. [Fix] Intel provide these two fixes to us, and we tested these two patches, it really fixed the issue. [Test Case] Boot and check the hdmi audio, then suspend and resume, check the hdmi audio, all work well. [Regression Risk] Low, Only enable the audio PIN and enable the clock for ICL. we tested on both ICL and non-ICL, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848788] Re: linux won't build when new virtualbox version is present on the archive
@Thadeu: Could you please verify this bug on the -proposed eoan kernel (5.3.0-21.22) and update this bug accordingly? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848788 Title: linux won't build when new virtualbox version is present on the archive Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in linux source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] linux won't build. [Test case] Test that linux will build. [Regression potential] Failure to build linux or missing modules. --- dkms packages are gone from the archive when new versions are uploaded. dkms-build grab them from the existing sources on the builder, which will work when the expected versions are present on any of the configured sources. virtualbox, however, right now, only grabs it from the main archive, preventing builds when they have been superseded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848490] Re: eoan: alsa/sof: Enable SOF_HDA link and codec
@Hui: Could you please mark this bug as verified if the eoan kernel in -proposed fixes the problem? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848490 Title: eoan: alsa/sof: Enable SOF_HDA link and codec Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] We tested the EOAN kernel on the LENOVO or Dell machines which have dmic directly connnected to PCH, the dmic didn't work. [Fix] We need to enable SOF_HDA link and codec, then the sof driver and Legacy HDA driver work together to make the dmic work. [Test Case] Install the latest 19.10 image, build a new kernel with this patch and replace the existing kernel, After installing the blacklist package (blacklist snd_hda_intel and snd_soc_skl) and ucm package, the dmic and all output devices (speaker/hdmi) work. [Regression Risk] Low, these configs are already enabled in the oem-b-osp1 kernel for a long time, and we tested it on many lenovo/dell machines witch have or have no dmic, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851447] Re: aufs-tools 4.14 FTBFS because of wrong SAUCE driver in the kernel
** Summary changed: - aufs-tools 4.9 FTBFS because of wrong SAUCE driver in the kernel + aufs-tools 4.14 FTBFS because of wrong SAUCE driver in the kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851447 Title: aufs-tools 4.14 FTBFS because of wrong SAUCE driver in the kernel Status in linux package in Ubuntu: Confirmed Bug description: The latest aufs-tools package synced from Debian fails to build in Ubuntu (but not in Debian) because the Ubuntu kernel package has aufs sauce patches and they are not at a compatible version. [...] dh_auto_install install -d /<>/aufs-tools-4.14\+20190211/debian/aufs-tools make -j4 install DESTDIR=/<>/aufs-tools-4.14\+20190211/debian/aufs-tools AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>/aufs-tools-4.14+20190211' cc -g -O2 -fdebug-prefix-map=/<>/aufs-tools-4.14+20190211=. -fstack-protector-strong -Wformat -Werror=format-security -O -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I./libau -DAUFHSM_CMD=\"/usr/bin/aufhsm\" -DMOUNT_CMD=\"/bin/mount\" -DUMOUNT_CMD=\"/bin/umount\" -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now ver.c -o ver ./ver Wrong version! aufs-util for aufs4.14 20190211, but aufs is 4.x-rcN-20190805. See README in detail and try git branch -a. make[1]: *** [Makefile:120: ver_test] Error 255 rm ver [...] (https://launchpad.net/ubuntu/+source/aufs- tools/1:4.14+20190211-1/+build/17953990) Please either update the aufs patches in the kernel tree, or else drop them. (My understanding is that we probably don't want to drop them because docker may use aufs as a backend; and while this is deprecated, there is currently no upgrade story for users currently using it.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849011] Re: bionic/linux-snapdragon: 4.15.0-1067.74 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849855 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 11:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1849010 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1849011 Title: bionic/linux-snapdragon: 4.15.0-1067.74 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849855 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 11:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1849010 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849022] Re: bionic/linux-oracle: 4.15.0-1028.31 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849855 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 23. October 2019 09:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1849021 variant: debs -- 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/1849022 Title: bionic/linux-oracle: 4.15.0-1028.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849855 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 23. October 2019 09:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1849021 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849022/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850483] Re: eoan/linux-oracle: 5.3.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 30. October 2019 20:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.3: bug 1851351 variant: debs -- 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/1850483 Title: eoan/linux-oracle: 5.3.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 30. October 2019 20:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.3: bug 1851351 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849682] Re: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting
@dannf: Ping for verification :) ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1849682 Title: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: This bug tracks the temporary revert of the upstream fix for a corruption issue. Bug 1850540 tracks the re-application of that fix once we have a full solution. Users of RAID0 arrays are susceptible to a corruption issue if: - The members of the RAID array are not all the same size[*] - Data has been written to the array while running kernels < 3.14 *and* >= 3.14. This is because of an change in v3.14 that accidentally changed how data was written - as described in the upstream commit message: https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9 To summarize, upstream is dealing with this by adding a versioned layout in v5.4, and that is being backported to stable kernels - which is why we're now seeing it. Layout version 1 is the pre-3.14 layout, version 2 is post 3.14. Mixing version 1 & version 2 layouts can cause corruption. However, unless a layout-version-aware kernel *created* the array, there's no way for the kernel to know which version(s) was used to write the existing data. This undefined mode is considered "Version 0", and the kernel will now refuse to start these arrays w/o user intervention. The user experience is pretty awful here. A user upgrades to the next SRU and all of a sudden their system stops at an (initramfs) prompt. A clueful user can spot something like the following in dmesg: Here's the message which , as you can see from the log in Comment #1, is hidden in a ton of other messages: [ 72.720232] md/raid0:md0: cannot assemble multi-zone RAID0 with default_layout setting [ 72.728149] md/raid0: please set raid.default_layout to 1 or 2 [ 72.733979] md: pers->run() failed ... mdadm: failed to start array /dev/md0: Unknown error 524 What that is trying to say is that you should determine if your data - specifically the data toward the end of your array - was most likely written with a pre-3.14 or post-3.14 kernel. Based on that, reboot with the kernel parameter raid0.default_layout=1 or raid0.default_layout=2 on the kernel command line. And note it should be *raid0.default_layout* not *raid.default_layout* as the message says - a fix for that message is now queued for stable: https://github.com/torvalds/linux/commit/3874d73e06c9b9dc15de0b7382fc223986d75571) IMHO, we should work with upstream to create a web page that clearly walks the user through this process, and update the error message to point to that page. I'd also like to see if we can detect this problem *before* the user reboots (debconf?) and help the user fix things. e.g. "We detected that you have RAID0 arrays that maybe susceptible to a corruption problem", guide the user to choosing a layout, and update the mdadm initramfs hook to poke the answer in via sysfs before starting the array on reboot. Note that it also seems like we should investigate backporting this to < 3.14 kernels. Imagine a user switching between the trusty HWE kernel and the GA kernel. References from users of other distros: https://blog.icod.de/2019/10/10/caution-kernel-5-3-4-and-raid0-default_layout/ https://www.linuxquestions.org/questions/linux-general-1/raid-arrays-not-assembling-4175662774/ [*] Which surprisingly is not the case reported in this bug - the user here had a raid0 of 8 identically-sized devices. I suspect there's a bug in the detection code somewhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847969] Re: [Packaging] Support building Flattened Image Tree (FIT) kernels
@shrirang: Ping for verification :) Thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847969 Title: [Packaging] Support building Flattened Image Tree (FIT) kernels Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Flexible and powerful format based on Flattened Image Tree -- FIT (similar to Flattened Device Tree). It allows the use of images with multiple components (several kernels, ramdisks, etc.), with contents protected by SHA1, MD5 or CRC32, etc. More details: https://gitlab.denx.de/u-boot/u-boot/blob/master/doc/uImage.FIT/howto.txt The packaging changes will add support for building a FIT kernel binary blob which can be subsequently signed. These FIT-signed kernels will be consumed by snapcraft recipes to build kernel snaps for platforms with U-Boot bootloader enforcing secure boot. [Regression Potential] Minimal. This bug is for tracking purposes only, do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851350] Re: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 - phase: Holding before Promote to Proposed - phase-changed: Tuesday, 05. November 2019 17:06 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 06. November 2019 01:46 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait + promote-to-proposed: Pending -- ready for review variant: debs -- 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/1851350 Title: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Ready for Promote to Proposed phase-changed: Wednesday, 06. November 2019 01:46 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851447] Re: aufs-tools 4.9 FTBFS because of wrong SAUCE driver in the kernel
** 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/1851447 Title: aufs-tools 4.9 FTBFS because of wrong SAUCE driver in the kernel Status in linux package in Ubuntu: Confirmed Bug description: The latest aufs-tools package synced from Debian fails to build in Ubuntu (but not in Debian) because the Ubuntu kernel package has aufs sauce patches and they are not at a compatible version. [...] dh_auto_install install -d /<>/aufs-tools-4.14\+20190211/debian/aufs-tools make -j4 install DESTDIR=/<>/aufs-tools-4.14\+20190211/debian/aufs-tools AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>/aufs-tools-4.14+20190211' cc -g -O2 -fdebug-prefix-map=/<>/aufs-tools-4.14+20190211=. -fstack-protector-strong -Wformat -Werror=format-security -O -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I./libau -DAUFHSM_CMD=\"/usr/bin/aufhsm\" -DMOUNT_CMD=\"/bin/mount\" -DUMOUNT_CMD=\"/bin/umount\" -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now ver.c -o ver ./ver Wrong version! aufs-util for aufs4.14 20190211, but aufs is 4.x-rcN-20190805. See README in detail and try git branch -a. make[1]: *** [Makefile:120: ver_test] Error 255 rm ver [...] (https://launchpad.net/ubuntu/+source/aufs- tools/1:4.14+20190211-1/+build/17953990) Please either update the aufs patches in the kernel tree, or else drop them. (My understanding is that we probably don't want to drop them because docker may use aufs as a backend; and while this is deprecated, there is currently no upgrade story for users currently using it.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850486] Re: eoan/linux: 5.3.0-21.22 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 30. October 2019 18:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1850485 eoan/linux-aws: bug 1850477 eoan/linux-azure: bug 1850480 eoan/linux-gcp: bug 1850481 eoan/linux-kvm: bug 1850482 eoan/linux-oracle: bug 1850483 eoan/linux-raspi2: bug 1850896 variant: debs -- 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/1850486 Title: eoan/linux: 5.3.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 30. October 2019 18:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1850485 eoan/linux-aws: bug 1850477 eoan/linux-azure: bug 1850480 eoan/linux-gcp: bug 1850481 eoan/linux-kvm: bug 1850482 eoan/linux-oracle: bug 1850483 eoan/linux-raspi2: bug 1850896 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850486] Re: eoan/linux: 5.3.0-21.22 -proposed tracker
There are 14 tests that show results as MISS, when in fact the test did run. Out of those tests, the ones that are expected to pass did in fact pass and the ones that were expected to fail did in fact fail. It's not clear to me why results are showing as MISS. Manually changing automated testing status to "fix released". ** Changed in: kernel-sru-workflow/automated-testing 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/1850486 Title: eoan/linux: 5.3.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 30. October 2019 18:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1850485 eoan/linux-aws: bug 1850477 eoan/linux-azure: bug 1850480 eoan/linux-gcp: bug 1850481 eoan/linux-kvm: bug 1850482 eoan/linux-oracle: bug 1850483 eoan/linux-raspi2: bug 1850896 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849031] Re: xenial/linux-gcp: 4.15.0-1048.51 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849855 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Wednesday, 23. October 2019 12:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1849028 xenial/linux-gcp/gke-kernel: bug 1849029 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1849031 Title: xenial/linux-gcp: 4.15.0-1048.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849855 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Wednesday, 23. October 2019 12:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1849028 xenial/linux-gcp/gke-kernel: bug 1849029 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849031] Re: xenial/linux-gcp: 4.15.0-1048.51 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1849031 Title: xenial/linux-gcp: 4.15.0-1048.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849855 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Wednesday, 23. October 2019 12:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1849028 xenial/linux-gcp/gke-kernel: bug 1849029 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851447] [NEW] aufs-tools 4.9 FTBFS because of wrong SAUCE driver in the kernel
Public bug reported: The latest aufs-tools package synced from Debian fails to build in Ubuntu (but not in Debian) because the Ubuntu kernel package has aufs sauce patches and they are not at a compatible version. [...] dh_auto_install install -d /<>/aufs-tools-4.14\+20190211/debian/aufs-tools make -j4 install DESTDIR=/<>/aufs-tools-4.14\+20190211/debian/aufs-tools AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>/aufs-tools-4.14+20190211' cc -g -O2 -fdebug-prefix-map=/<>/aufs-tools-4.14+20190211=. -fstack-protector-strong -Wformat -Werror=format-security -O -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I./libau -DAUFHSM_CMD=\"/usr/bin/aufhsm\" -DMOUNT_CMD=\"/bin/mount\" -DUMOUNT_CMD=\"/bin/umount\" -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now ver.c -o ver ./ver Wrong version! aufs-util for aufs4.14 20190211, but aufs is 4.x-rcN-20190805. See README in detail and try git branch -a. make[1]: *** [Makefile:120: ver_test] Error 255 rm ver [...] (https://launchpad.net/ubuntu/+source/aufs- tools/1:4.14+20190211-1/+build/17953990) Please either update the aufs patches in the kernel tree, or else drop them. (My understanding is that we probably don't want to drop them because docker may use aufs as a backend; and while this is deprecated, there is currently no upgrade story for users currently using it.) ** Affects: linux (Ubuntu) Importance: High Status: Incomplete ** Package changed: aufs-tools (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1851447 Title: aufs-tools 4.9 FTBFS because of wrong SAUCE driver in the kernel Status in linux package in Ubuntu: Incomplete Bug description: The latest aufs-tools package synced from Debian fails to build in Ubuntu (but not in Debian) because the Ubuntu kernel package has aufs sauce patches and they are not at a compatible version. [...] dh_auto_install install -d /<>/aufs-tools-4.14\+20190211/debian/aufs-tools make -j4 install DESTDIR=/<>/aufs-tools-4.14\+20190211/debian/aufs-tools AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>/aufs-tools-4.14+20190211' cc -g -O2 -fdebug-prefix-map=/<>/aufs-tools-4.14+20190211=. -fstack-protector-strong -Wformat -Werror=format-security -O -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I./libau -DAUFHSM_CMD=\"/usr/bin/aufhsm\" -DMOUNT_CMD=\"/bin/mount\" -DUMOUNT_CMD=\"/bin/umount\" -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now ver.c -o ver ./ver Wrong version! aufs-util for aufs4.14 20190211, but aufs is 4.x-rcN-20190805. See README in detail and try git branch -a. make[1]: *** [Makefile:120: ver_test] Error 255 rm ver [...] (https://launchpad.net/ubuntu/+source/aufs- tools/1:4.14+20190211-1/+build/17953990) Please either update the aufs patches in the kernel tree, or else drop them. (My understanding is that we probably don't want to drop them because docker may use aufs as a backend; and while this is deprecated, there is currently no upgrade story for users currently using it.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851447] 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 1851447 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/1851447 Title: aufs-tools 4.9 FTBFS because of wrong SAUCE driver in the kernel Status in linux package in Ubuntu: Incomplete Bug description: The latest aufs-tools package synced from Debian fails to build in Ubuntu (but not in Debian) because the Ubuntu kernel package has aufs sauce patches and they are not at a compatible version. [...] dh_auto_install install -d /<>/aufs-tools-4.14\+20190211/debian/aufs-tools make -j4 install DESTDIR=/<>/aufs-tools-4.14\+20190211/debian/aufs-tools AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>/aufs-tools-4.14+20190211' cc -g -O2 -fdebug-prefix-map=/<>/aufs-tools-4.14+20190211=. -fstack-protector-strong -Wformat -Werror=format-security -O -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I./libau -DAUFHSM_CMD=\"/usr/bin/aufhsm\" -DMOUNT_CMD=\"/bin/mount\" -DUMOUNT_CMD=\"/bin/umount\" -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now ver.c -o ver ./ver Wrong version! aufs-util for aufs4.14 20190211, but aufs is 4.x-rcN-20190805. See README in detail and try git branch -a. make[1]: *** [Makefile:120: ver_test] Error 255 rm ver [...] (https://launchpad.net/ubuntu/+source/aufs- tools/1:4.14+20190211-1/+build/17953990) Please either update the aufs patches in the kernel tree, or else drop them. (My understanding is that we probably don't want to drop them because docker may use aufs as a backend; and while this is deprecated, there is currently no upgrade story for users currently using it.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851447] [NEW] aufs-tools 4.9 FTBFS because of wrong SAUCE driver in the kernel
You have been subscribed to a public bug: The latest aufs-tools package synced from Debian fails to build in Ubuntu (but not in Debian) because the Ubuntu kernel package has aufs sauce patches and they are not at a compatible version. [...] dh_auto_install install -d /<>/aufs-tools-4.14\+20190211/debian/aufs-tools make -j4 install DESTDIR=/<>/aufs-tools-4.14\+20190211/debian/aufs-tools AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>/aufs-tools-4.14+20190211' cc -g -O2 -fdebug-prefix-map=/<>/aufs-tools-4.14+20190211=. -fstack-protector-strong -Wformat -Werror=format-security -O -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I./libau -DAUFHSM_CMD=\"/usr/bin/aufhsm\" -DMOUNT_CMD=\"/bin/mount\" -DUMOUNT_CMD=\"/bin/umount\" -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now ver.c -o ver ./ver Wrong version! aufs-util for aufs4.14 20190211, but aufs is 4.x-rcN-20190805. See README in detail and try git branch -a. make[1]: *** [Makefile:120: ver_test] Error 255 rm ver [...] (https://launchpad.net/ubuntu/+source/aufs- tools/1:4.14+20190211-1/+build/17953990) Please either update the aufs patches in the kernel tree, or else drop them. (My understanding is that we probably don't want to drop them because docker may use aufs as a backend; and while this is deprecated, there is currently no upgrade story for users currently using it.) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- aufs-tools 4.9 FTBFS because of wrong SAUCE driver in the kernel https://bugs.launchpad.net/bugs/1851447 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823684] Re: Touchpad right click does not work as expected on Dell G7 7588
user@machine:~$ grep -i touchpad /var/log/Xorg.0.log [15.043] (II) config/udev: Adding input device AlpsPS/2 ALPS DualPoint TouchPad (/dev/input/event6) [15.043] (**) AlpsPS/2 ALPS DualPoint TouchPad: Applying InputClass "evdev touchpad catchall" [15.043] (**) AlpsPS/2 ALPS DualPoint TouchPad: Applying InputClass "touchpad catchall" [15.043] (**) AlpsPS/2 ALPS DualPoint TouchPad: Applying InputClass "Default clickpad buttons" [15.045] (II) Using input driver 'synaptics' for 'AlpsPS/2 ALPS DualPoint TouchPad' [15.045] (**) AlpsPS/2 ALPS DualPoint TouchPad: always reports core events [15.116] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: x-axis range 0 - 1023 (res 0) [15.116] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: y-axis range 0 - 767 (res 0) [15.116] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: pressure range 0 - 127 [15.116] (II) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: device does not report finger width. [15.116] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: buttons: left right middle [15.116] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: Vendor 0x2 Product 0x8 [15.116] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: invalid finger width range. defaulting to 0 - 15 [15.116] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: touchpad found [15.116] (**) AlpsPS/2 ALPS DualPoint TouchPad: always reports core events [15.168] (II) XINPUT: Adding extended input device "AlpsPS/2 ALPS DualPoint TouchPad" (type: TOUCHPAD, id 14) [15.168] (**) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: (accel) MinSpeed is now constant deceleration 2.5 [15.168] (**) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: (accel) MaxSpeed is now 1.75 [15.168] (**) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: (accel) AccelFactor is now 0.156 [15.168] (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) keeping acceleration scheme 1 [15.168] (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration profile 1 [15.169] (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration factor: 2.000 [15.169] (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration threshold: 4 [15.169] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: touchpad found [15.170] (II) config/udev: Adding input device AlpsPS/2 ALPS DualPoint TouchPad (/dev/input/mouse1) [15.170] (**) AlpsPS/2 ALPS DualPoint TouchPad: Ignoring device from InputClass "touchpad ignore duplicates" user@machine:~$ lsmod Module Size Used by ufs73728 0 qnx4 16384 0 hfsplus 106496 0 hfs57344 0 minix 36864 0 ntfs 98304 0 msdos 20480 0 jfs 184320 0 xfs 974848 0 libcrc32c 16384 1 xfs rfcomm 69632 14 drbg 32768 1 ansi_cprng 16384 0 ctr16384 1 ccm20480 1 bnep 20480 2 arc4 16384 2 coretemp 16384 0 kvm_intel 176128 0 snd_hda_codec_analog16384 1 snd_hda_codec_generic77824 1 snd_hda_codec_analog kvm 552960 1 kvm_intel uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo iwl4965 114688 0 videobuf2_memops 16384 1 videobuf2_vmalloc irqbypass 16384 1 kvm videobuf2_v4l2 28672 1 uvcvideo iwlegacy 102400 1 iwl4965 snd_seq_midi 16384 0 videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 snd_seq_midi_event 16384 1 snd_seq_midi mac80211 737280 2 iwl4965,iwlegacy serio_raw 16384 0 videodev 180224 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 media 24576 2 uvcvideo,videodev snd_rawmidi32768 1 snd_seq_midi snd_hda_intel 40960 3 snd_hda_codec 135168 3 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec_analog thinkpad_acpi 94208 0 nvram 16384 1 thinkpad_acpi snd_hda_core 77824 4 snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_hda_codec_analog snd_hwdep 16384 1 snd_hda_codec lpc_ich24576 0 cfg80211 565248 3 iwl4965,iwlegacy,mac80211 joydev 20480 0 snd_pcm 106496 3 snd_hda_codec,snd_hda_intel,snd_hda_core btusb 45056 0 snd_seq69632 2 snd_seq_midi_event,snd_seq_midi btrtl 16384 1 btusb btbcm 16384 1 btusb btintel16384 1 btusb bluetooth 512000 39 bnep,btbcm,btrtl,btusb,rfcomm,btintel input_leds 16384 0 shpchp 36864 0 snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi ecdh_generic
[Kernel-packages] [Bug 1823684] Re: Touchpad right click does not work as expected on Dell G7 7588
user@machine:~$ xinput --list-props 14 Device 'AlpsPS/2 ALPS DualPoint TouchPad': Device Enabled (136): 1 Coordinate Transformation Matrix (138): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (265): 1 Device Accel Constant Deceleration (266): 2.50 Device Accel Adaptive Deceleration (267): 1.00 Device Accel Velocity Scaling (268):12.50 Synaptics Edges (290): 153, 870, 115, 652 Synaptics Finger (291): 12, 15, 0 Synaptics Tap Time (292): 180 Synaptics Tap Move (293): 56 Synaptics Tap Durations (294): 180, 100, 100 Synaptics ClickPad (295): 0 Synaptics Middle Button Timeout (296): 75 Synaptics Two-Finger Pressure (297):141 Synaptics Two-Finger Width (298): 7 Synaptics Scrolling Distance (299): 25, 25 Synaptics Edge Scrolling (300): 1, 0, 0 Synaptics Two-Finger Scrolling (301): 0, 0 Synaptics Move Speed (302): 1.00, 1.75, 0.156495, 0.00 Synaptics Off (303):0 Synaptics Locked Drags (304): 0 Synaptics Locked Drags Timeout (305): 5000 Synaptics Tap Action (306): 2, 3, 0, 0, 0, 0, 0 Synaptics Click Action (307): 1, 1, 0 Synaptics Circular Scrolling (308): 0 Synaptics Circular Scrolling Distance (309):0.10 Synaptics Circular Scrolling Trigger (310): 0 Synaptics Circular Pad (311): 0 Synaptics Palm Detection (312): 0 Synaptics Palm Dimensions (313):10, 100 Synaptics Coasting Speed (314): 20.00, 50.00 Synaptics Pressure Motion (315):15, 80 Synaptics Pressure Motion Factor (316): 1.00, 1.00 Synaptics Resolution Detect (317): 1 Synaptics Grab Event Device (318): 0 Synaptics Gestures (319): 1 Synaptics Capabilities (320): 1, 1, 1, 0, 0, 1, 0 Synaptics Pad Resolution (321): 1, 1 Synaptics Area (322): 0, 0, 0, 0 Synaptics Noise Cancellation (323): 6, 6 Device Product ID (256):2, 8 Device Node (257): "/dev/input/event6" user@machine:~$ xinput --list-props 15 Device 'AlpsPS/2 ALPS DualPoint Stick': Device Enabled (136): 1 Coordinate Transformation Matrix (138): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (265): 0 Device Accel Constant Deceleration (266): 1.00 Device Accel Adaptive Deceleration (267): 1.00 Device Accel Velocity Scaling (268):10.00 Device Product ID (256):2, 8 Device Node (257): "/dev/input/event5" Evdev Axis Inversion (269): 0, 0 Evdev Axes Swap (271): 0 Axis Labels (272): "Rel X" (146), "Rel Y" (147) Button Labels (273):"Button Left" (139), "Button Middle" (140), "Button Right" (141), "Button Wheel Up" (142), "Button Wheel Down" (143), "Button Horiz Wheel Left" (144), "Button Horiz Wheel Right" (145) Evdev Scrolling Distance (274): 0, 0, 0 Evdev Middle Button Emulation (275):1 Evdev Middle Button Timeout (276): 50 Evdev Third Button Emulation (277): 0 Evdev Third Button Emulation Timeout (278): 1000 Evdev Third Button Emulation Button (279): 3 Evdev Third Button Emulation Threshold (280): 20 Evdev Wheel Emulation (281):1 Evdev Wheel Emulation Axes (282): 6, 7, 4, 5 Evdev Wheel Emulation Inertia (283):10 Evdev Wheel Emulation Timeout (284):200 Evdev Wheel Emulation Button (285): 2 Evdev Drag Lock Buttons (286): 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1823684 Title: Touchpad right click does not work as expected on Dell G7 7588 Status in linux-signed package in Ubuntu: Confirmed Bug description: The right button on the touchpad of this system does not work as expected, the click event will get treated as a regular left click. $ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ DELL0825:00 06CB:7E92 Touchpad id=12 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)]
[Kernel-packages] [Bug 1851446] 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 1851446 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/1851446 Title: Backport MPLS patches from 5.3 to 4.15 Status in linux package in Ubuntu: Incomplete Bug description: Mellanox is requesting a backport of the following commit IDs from 5.3 back to 4.15. Netdevice HW MPLS features are not passed from device driver's netdevice to upper netdevice, specifically VLAN and bonding netdevice which are created by the kernel when needed. This prevents enablement and usage of HW offloads, such as TSO and checksumming for MPLS tagged traffic when running via VLAN or bonding interface. The patches introduce changes to the initialization steps of the VLAN and bonding netdevices to inherit the MPLS features from lower netdevices to allow the HW offloads. Ariel Levkovich (2): net: bonding: Inherit MPLS features from slave devices net: vlan: Inherit MPLS features from parent device drivers/net/bonding/bond_main.c | 11 +++ net/8021q/vlan_dev.c| 1 + 2 files changed, 12 insertions(+) https://www.mail-archive.com/netdev@vger.kernel.org/msg299084.html Commit IDs (All landed in 5.3) 600bb0318c18e9616d97ad123caaa7c5f7bf222c 8b6912a5019356d7adb1b8a146c9eef5e679bf98 2e770b507ccde8eedc129946e4b78ceed0a22df2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823684] Re: Touchpad right click does not work as expected on Dell G7 7588
I have Peach OSI Xubuntu 16.04 LTS 4.4.0-166 64bit A few days ago my right click Touschpad mouse button on my Thinkpad X300, worked fine, since monday evening it has not worked at all. Luckily both Touchpoint buttons and external mouse works. I booted my USB with multi tools including Peach OSI 14.04 LTS 32bit to see if problem persists and it does so either firmware of the buttons got corrupted, or the right mouse button suddently died. user@machine:~$ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=14 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Button id=8[slave keyboard (3)] ↳ UVC Camera (17ef:4807)id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)] ↳ ThinkPad Extra Buttonsid=16 [slave keyboard (3)] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1823684 Title: Touchpad right click does not work as expected on Dell G7 7588 Status in linux-signed package in Ubuntu: Confirmed Bug description: The right button on the touchpad of this system does not work as expected, the click event will get treated as a regular left click. $ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ DELL0825:00 06CB:7E92 Touchpad id=12 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=11 [slave keyboard (3)] ↳ Intel HID 5 button arrayid=13 [slave keyboard (3)] ↳ Intel HID eventsid=14 [slave keyboard (3)] ↳ Dell WMI hotkeysid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] xev for left click and right click: ButtonPress event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 304106, (167,148), root:(357,319), state 0x10, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 304146, (167,148), root:(357,319), state 0x110, button 1, same_screen YES ButtonPress event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 309562, (167,148), root:(357,319), state 0x10, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 309563, (167,148), root:(357,319), state 0x110, button 1, same_screen YES ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 17:50:24 2019 InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1823684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851446] [NEW] Backport MPLS patches from 5.3 to 4.15
Public bug reported: Mellanox is requesting a backport of the following commit IDs from 5.3 back to 4.15. Netdevice HW MPLS features are not passed from device driver's netdevice to upper netdevice, specifically VLAN and bonding netdevice which are created by the kernel when needed. This prevents enablement and usage of HW offloads, such as TSO and checksumming for MPLS tagged traffic when running via VLAN or bonding interface. The patches introduce changes to the initialization steps of the VLAN and bonding netdevices to inherit the MPLS features from lower netdevices to allow the HW offloads. Ariel Levkovich (2): net: bonding: Inherit MPLS features from slave devices net: vlan: Inherit MPLS features from parent device drivers/net/bonding/bond_main.c | 11 +++ net/8021q/vlan_dev.c| 1 + 2 files changed, 12 insertions(+) https://www.mail-archive.com/netdev@vger.kernel.org/msg299084.html Commit IDs (All landed in 5.3) 600bb0318c18e9616d97ad123caaa7c5f7bf222c 8b6912a5019356d7adb1b8a146c9eef5e679bf98 2e770b507ccde8eedc129946e4b78ceed0a22df2 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851446 Title: Backport MPLS patches from 5.3 to 4.15 Status in linux package in Ubuntu: New Bug description: Mellanox is requesting a backport of the following commit IDs from 5.3 back to 4.15. Netdevice HW MPLS features are not passed from device driver's netdevice to upper netdevice, specifically VLAN and bonding netdevice which are created by the kernel when needed. This prevents enablement and usage of HW offloads, such as TSO and checksumming for MPLS tagged traffic when running via VLAN or bonding interface. The patches introduce changes to the initialization steps of the VLAN and bonding netdevices to inherit the MPLS features from lower netdevices to allow the HW offloads. Ariel Levkovich (2): net: bonding: Inherit MPLS features from slave devices net: vlan: Inherit MPLS features from parent device drivers/net/bonding/bond_main.c | 11 +++ net/8021q/vlan_dev.c| 1 + 2 files changed, 12 insertions(+) https://www.mail-archive.com/netdev@vger.kernel.org/msg299084.html Commit IDs (All landed in 5.3) 600bb0318c18e9616d97ad123caaa7c5f7bf222c 8b6912a5019356d7adb1b8a146c9eef5e679bf98 2e770b507ccde8eedc129946e4b78ceed0a22df2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 - phase: Promote to Proposed - phase-changed: Monday, 04. November 2019 17:35 UTC + phase: Testing + phase-changed: Tuesday, 05. November 2019 23:31 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Testing phase-changed: Tuesday, 05. November 2019 23:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 - phase: Promote to Proposed - phase-changed: Tuesday, 05. November 2019 13:55 UTC + phase: Testing + phase-changed: Tuesday, 05. November 2019 23:31 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- 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/1850967 Title: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Testing phase-changed: Tuesday, 05. November 2019 23:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851350] Re: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 17:06 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait variant: debs -- 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/1851350 Title: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 17:06 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip
Same on physical HW (Medion with QuadCore) This seems to happen during mdadm run, every time a new initrd is being built. lsblk doesn't hag. blkid hangs. mdadm hangs. In this ps output, mdadm has been hung for almos two hours. jpc@quad:~$ ps -ft pts/4 ; date UIDPID PPID C STIME TTY TIME CMD root 7969 28631 0 20:29 pts/400:00:00 /bin/sh /var/lib/dpkg/info/linux-image-5.3.0-19-generic.postinst triggered l root 7970 7969 0 20:29 pts/400:00:00 sh /usr/lib/linux/triggers/5.3.0-19-generic root 7971 7970 0 20:29 pts/400:00:00 run-parts --report --exit-on-error --arg=5.3.0-19-generic --arg=/boot/vmlinu root 8047 7971 0 20:30 pts/400:00:00 /bin/sh -e /etc/kernel/postinst.d/initramfs-tools 5.3.0-19-generic /boot/vml root 8049 8047 0 20:30 pts/400:00:00 /bin/sh /usr/sbin/update-initramfs -c -k 5.3.0-19-generic -b /boot root 8051 8049 0 20:30 pts/400:00:00 /bin/sh /usr/sbin/mkinitramfs -o /boot/initrd.img-5.3.0-19-generic.new 5.3.0 root 18519 8051 0 20:30 pts/400:00:00 /bin/sh /usr/share/initramfs-tools/hooks/mdadm root 18642 18519 0 20:30 pts/400:00:00 /bin/sh /usr/share/mdadm/mkconf root 18648 18642 0 20:30 pts/400:00:00 /sbin/mdadm --examine --scan --config=partitions root 28631 17100 0 20:29 pts/400:00:00 /usr/bin/dpkg --force-overwrite --status-fd 112 --configure --pending [1499890.437313] INFO: task mdadm:18648 blocked for more than 120 seconds. [1499890.437318] Not tainted 5.0.0-31-generic #33-Ubuntu [1499890.437320] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [1499890.437322] mdadm D0 18648 18642 0x0080 [1499890.437325] Call Trace: [1499890.437335] __schedule+0x2d0/0x840 [1499890.437338] ? __switch_to_asm+0x41/0x70 [1499890.437340] ? __switch_to_asm+0x35/0x70 [1499890.437342] schedule+0x2c/0x70 [1499890.437344] schedule_timeout+0x258/0x360 [1499890.437346] wait_for_completion+0xb7/0x140 [1499890.437350] ? wake_up_q+0x80/0x80 [1499890.437358] __floppy_read_block_0+0x138/0x190 [floppy] [1499890.437362] ? floppy_cmos_show+0x30/0x30 [floppy] [1499890.437367] floppy_revalidate+0xf8/0x230 [floppy] [1499890.437370] check_disk_change+0x62/0x70 [1499890.437374] floppy_open+0x2ae/0x380 [floppy] [1499890.437376] __blkdev_get+0xe5/0x550 [1499890.437378] ? bd_acquire+0xd0/0xd0 [1499890.437380] blkdev_get+0x10c/0x330 [1499890.437382] ? bd_acquire+0xd0/0xd0 [1499890.437384] blkdev_open+0x92/0x100 [1499890.437386] do_dentry_open+0x143/0x3a0 [1499890.437389] vfs_open+0x2d/0x30 [1499890.437391] path_openat+0x2bf/0x1570 [1499890.437394] ? put_device+0x17/0x20 [1499890.437397] ? scsi_device_put+0x2b/0x30 [1499890.437400] do_filp_open+0x93/0x100 [1499890.437403] ? strncpy_from_user+0x57/0x1c0 [1499890.437405] ? __alloc_fd+0x46/0x150 [1499890.437407] do_sys_open+0x177/0x280 [1499890.437409] ? _cond_resched+0x19/0x30 [1499890.437412] __x64_sys_openat+0x20/0x30 [1499890.437415] do_syscall_64+0x5a/0x110 [1499890.437417] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1499890.437419] RIP: 0033:0x7f84b3cc8fdb [1499890.437426] Code: Bad RIP value. [1499890.437427] RSP: 002b:7ffd8cb8fed0 EFLAGS: 0246 ORIG_RAX: 0101 [1499890.437429] RAX: ffda RBX: 4000 RCX: 7f84b3cc8fdb [1499890.437431] RDX: 4000 RSI: 5563a1618b80 RDI: ff9c [1499890.437432] RBP: 5563a1618b80 R08: 1999 R09: [1499890.437433] R10: R11: 0246 R12: 4000 [1499890.437434] R13: R14: 0001 R15: 5563a1612a00 -- 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/1825413 Title: mdadm, mkfs, other io commands hang, stuck task, bad rip Status in linux package in Ubuntu: Confirmed Bug description: 1. disco 2. # apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.0.0.13.14 Candidate: 5.0.0.13.14 Version table: *** 5.0.0.13.14 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 3. installation completes sucessfully 4. Running an installation of Disco creating filesystems and probing things will hang (stuck task) every so often. When it happens, the kernel throws an oops and bad rip value. [ 967.810391] INFO: task mdadm:12213 blocked for more than 120 seconds. [ 967.811787] Tainted: P O 5.0.0-13-generic #14-Ubuntu [ 967.813330] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.815500] mdadm D0 12213 12207 0x [ 967.815503] Call Trace: [ 967.815509] __schedule+0x2d0/0x840 [ 967.815511] ? __switch_to_asm+0x40/0x70 [ 967.815512] ? __switch_to_asm+0x34/0x70 [ 967.815514]
[Kernel-packages] [Bug 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Stalled -- packages are in the wrong component + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- 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/1850967 Title: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Ongoing -- package copied to Proposed main:building,signed:building + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780590] Re: Add support for Realtek 8723DE wireless adapter
** Summary changed: - no wireless adapter was found ubuntu 18.04 + Add support for Realtek 8723DE wireless adapter -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1780590 Title: Add support for Realtek 8723DE wireless adapter Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-firmware source package in Disco: New Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-firmware source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Confirmed Status in linux-firmware source package in Focal: New Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] There's no in-kernel support for Realtek 8723DE, so users need to use out-of-tree DKMS which is not from Ubuntu archive. This has security implication and should be avoided. Also this provides pretty bad user experience. [Fix] Add support to Realtek 8723DE. All commits are cherry-picked from Realtek maintained repo: https://github.com/rtlwifi-linux/rtw88_8723de [Test] With the patch series applied, 8723DE can scan and connect to APs succesfully. Also did some S3 smoke test, it continues to work. [Regression Potential] Low. The device in question was never supported, and if there's any regression, we can count on Realtek Wireless team, thy are now pretty responsive on upstream mailing list. === Original Bug Report === recently I just installed ubuntu 18.04 lts in dual bot next to windows 10. Everything in the installation was fine until the moment to start session. The problem is that the wireless network card does not detect me and when entering the configuration I simply get an error message saying that no wireless adapter was found. I have already followed all the tutorials I found on the web. and update the driver of a github repository, and install how much program they told me to install and I still can not connect via wifi. I just do not know what to do. I have a laptop hp 14-bs004 came with windows 10 installed. The information on the network card is as follows: Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec: d723] Subsystem: Hewlett-Packard Company Device [103c: 8319] Control: I / O + Mem + BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap + 66MHz- UDF- FastB2B- ParErr- DEVSEL = fast> TAbort- SERR- Kernel modules: wl already install the most recent kernel, already intale driver driver realtek rtl8723be according to the instructions of the git repository. and nothing has worked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 7 22:57:40 2018 InstallationDate: Installed on 2018-07-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_MX.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Stalled -- packages are in the wrong component + promote-to-proposed: Ongoing -- package copied to Proposed main:building,signed:building regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Ongoing -- package copied to Proposed main:building,signed:building regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
The following packages ended up in the wrong component in the Proposed pocket: linux-restricted-modules-gcp-5.3 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-5.3.0-1007-gcp 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-gcp-edge 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-5.3.0-1007-gcp 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-gcp-edge 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-headers-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-image-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-modules-extra-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-tools-gcp-edge 5.3.0.1007.7 - is in main instead of universe Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => 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/1850967 Title: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- packages are in the wrong component regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
The following packages ended up in the wrong component in the Proposed pocket: linux-restricted-modules-azure-5.3 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-5.3.0-1006-azure 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-azure-edge 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-5.3.0-1006-azure 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-azure-edge 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-cloud-tools-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-headers-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-image-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-modules-extra-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-signed-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-signed-image-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-tools-azure-edge 5.3.0.1006.6 - is in main instead of universe Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- packages are in the wrong component regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => 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/1850967 Title: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- packages are in the wrong component regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- packages are in the wrong component regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851380] Re: root can lift kernel lockdown
I'm no expert in either kernel or C programming and I didn't test this
patch, but it looks good to me.
Also, the resulting code is quite similar to the one Fedora is currently using
- they accidentally fixed this bug in
https://src.fedoraproject.org/rpms/kernel/c/5df4c5562f191b434edf57e8c92b176baad37cba.
(Debian also seems to be affected:
https://salsa.debian.org/kernel-team/linux/blob/4dcfa860/debian/patches/features/all/lockdown/0002-Add-a-SysRq-option-to-lift-kernel-lockdown.patch)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851380
Title:
root can lift kernel lockdown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Invalid
Status in linux source package in Bionic:
Triaged
Status in linux source package in Disco:
Triaged
Status in linux source package in Eoan:
Triaged
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification
Impact: The kernel lockdown support adds a sysrq to allow a physically
present user to disable lockdown from the keyboard. A bug in the
implementation makes it possible to also lift lockdown by writing to
/proc/sysrq-trigger.
Fix: Correct the logic to disallow disabling lockdown via /proc/sysrq-
trigger.
Test Case: Write "x" to /proc/sysrq-trigger. When working properly
there should be no messages in dmesg about lifting lockdown, and
lockdown restrictions (e.g. loading unsigned modules) should remain in
effect.
Regression Potential: Anyone using /proc/sysrq-trigger to disable
lockdown will no longer be able to do so. Implementation bugs could
prevent use of the sysrq from the keyboard from disabling lockdown,
but this has been confrimed to still work with the fix in place.
---
Echoing "x" into /proc/sysrq-trigger disables kernel lockdown, even
though it shouldn't.
If I'm not mistaken, kernel lockdown is meant to create a barrier
between root and the kernel that can only be broken with physical
access to the system. It is automatically enabled when the system is
booted with UEFI Secure Boot, which is the case for me.
This should show the bug:
# echo "x" > /proc/sysrq-trigger
Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
Nov 05 14:58:15 panzersperre kernel: This sysrq operation is disabled from
userspace.
Nov 05 14:58:15 panzersperre kernel: Disabling Secure Boot restrictions
Nov 05 14:58:15 panzersperre kernel: Lifting lockdown
Note that it first says that the operation is disabled and then performs this
operation.
This should only be possible by physically pressing sysrq+x on an attached
keyboard.
I'm doing this on 4.15.0-68-generic on Ubuntu 18.04.3 LTS.
I have kernel.sysrq set to 1 - this is important to be able to trigger this
bug. (But I don't think it disqualifies this issue as non-security relevant
because root can trivially execute `sysctl kernel.sysrq=1`.)
I first learned about this by reading a blog post
(https://gehrcke.de/2019/09/running-an-ebpf-program-may-require-
lifting-the-kernel-lockdown/), so I'm not the first to notice this
behavior (even though this post doesn't say it's a bug).
Looking through drivers/tty/sysrq.c, I guess the problem is caused by
this if condition in __handle_sysrq:
554 │ /* Ban synthetic events from some sysrq functionality */
555 │ if ((from == SYSRQ_FROM_PROC || from ==
SYSRQ_FROM_SYNTHETIC) &&
556 │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
557 │ printk("This sysrq operation is disabled from
userspace.\n");
558 │ /*
559 │ * Should we check for enabled operations
(/proc/sysrq-trigger
560 │ * should not) and is the invoked operation enabled?
561 │ */
562 │ if (from == SYSRQ_FROM_KERNEL ||
sysrq_on_mask(op_p->enable_mask)) {
563 │ pr_cont("%s\n", op_p->action_msg);
564 │ console_loglevel = orig_log_level;
565 │ op_p->handler(key);
566 │ } else {
567 │ pr_cont("This sysrq operation is disabled.\n");
568 │ }
Note that `op_p->enable_mask & SYSRQ_DISABLE_USERSPACE` just causes a
printk and no change of behavior.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-68-generic 4.15.0-68.77
ProcVersionSignature: Ubuntu 4.15.0-68.77-generic 4.15.18
Uname: Linux 4.15.0-68-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: niklas 2442 F pulseaudio
/dev/snd/controlC0: niklas 2442 F pulseaudio
CurrentDesktop: KDE
Date: Tue Nov 5 14:58:33 2019
InstallationDate: Installed on 2015-12-11 (1424 days ago)
InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64
[Kernel-packages] [Bug 1851380] Re: root can lift kernel lockdown
** Description changed:
+ SRU Justification
+
+ Impact: The kernel lockdown support adds a sysrq to allow a physically
+ present user to disable lockdown from the keyboard. A bug in the
+ implementation makes it possible to also lift lockdown by writing to
+ /proc/sysrq-trigger.
+
+ Fix: Correct the logic to disallow disabling lockdown via /proc/sysrq-
+ trigger.
+
+ Test Case: Write "x" to /proc/sysrq-trigger. When working properly there
+ should be no messages in dmesg about lifting lockdown, and lockdown
+ restrictions (e.g. loading unsigned modules) should remain in effect.
+
+ Regression Potential: Anyone using /proc/sysrq-trigger to disable
+ lockdown will no longer be able to do so. Implementation bugs could
+ prevent use of the sysrq from the keyboard from disabling lockdown, but
+ this has been confrimed to still work with the fix in place.
+
+ ---
+
Echoing "x" into /proc/sysrq-trigger disables kernel lockdown, even
though it shouldn't.
If I'm not mistaken, kernel lockdown is meant to create a barrier
between root and the kernel that can only be broken with physical access
to the system. It is automatically enabled when the system is booted
with UEFI Secure Boot, which is the case for me.
This should show the bug:
- # echo "x" > /proc/sysrq-trigger
- Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
+ # echo "x" > /proc/sysrq-trigger
+ Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
Nov 05 14:58:15 panzersperre kernel: This sysrq operation is disabled from
userspace.
Nov 05 14:58:15 panzersperre kernel: Disabling Secure Boot restrictions
Nov 05 14:58:15 panzersperre kernel: Lifting lockdown
Note that it first says that the operation is disabled and then performs this
operation.
This should only be possible by physically pressing sysrq+x on an attached
keyboard.
I'm doing this on 4.15.0-68-generic on Ubuntu 18.04.3 LTS.
I have kernel.sysrq set to 1 - this is important to be able to trigger this
bug. (But I don't think it disqualifies this issue as non-security relevant
because root can trivially execute `sysctl kernel.sysrq=1`.)
I first learned about this by reading a blog post
(https://gehrcke.de/2019/09/running-an-ebpf-program-may-require-lifting-
the-kernel-lockdown/), so I'm not the first to notice this behavior
(even though this post doesn't say it's a bug).
Looking through drivers/tty/sysrq.c, I guess the problem is caused by
this if condition in __handle_sysrq:
- 554 │ /* Ban synthetic events from some sysrq functionality */
- 555 │ if ((from == SYSRQ_FROM_PROC || from ==
SYSRQ_FROM_SYNTHETIC) &&
- 556 │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
- 557 │ printk("This sysrq operation is disabled from
userspace.\n");
- 558 │ /*
- 559 │ * Should we check for enabled operations
(/proc/sysrq-trigger
- 560 │ * should not) and is the invoked operation enabled?
- 561 │ */
- 562 │ if (from == SYSRQ_FROM_KERNEL ||
sysrq_on_mask(op_p->enable_mask)) {
- 563 │ pr_cont("%s\n", op_p->action_msg);
- 564 │ console_loglevel = orig_log_level;
- 565 │ op_p->handler(key);
- 566 │ } else {
- 567 │ pr_cont("This sysrq operation is disabled.\n");
- 568 │ }
+ 554 │ /* Ban synthetic events from some sysrq functionality */
+ 555 │ if ((from == SYSRQ_FROM_PROC || from ==
SYSRQ_FROM_SYNTHETIC) &&
+ 556 │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
+ 557 │ printk("This sysrq operation is disabled from
userspace.\n");
+ 558 │ /*
+ 559 │ * Should we check for enabled operations
(/proc/sysrq-trigger
+ 560 │ * should not) and is the invoked operation enabled?
+ 561 │ */
+ 562 │ if (from == SYSRQ_FROM_KERNEL ||
sysrq_on_mask(op_p->enable_mask)) {
+ 563 │ pr_cont("%s\n", op_p->action_msg);
+ 564 │ console_loglevel = orig_log_level;
+ 565 │ op_p->handler(key);
+ 566 │ } else {
+ 567 │ pr_cont("This sysrq operation is disabled.\n");
+ 568 │ }
Note that `op_p->enable_mask & SYSRQ_DISABLE_USERSPACE` just causes a
printk and no change of behavior.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-68-generic 4.15.0-68.77
ProcVersionSignature: Ubuntu 4.15.0-68.77-generic 4.15.18
Uname: Linux 4.15.0-68-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC1: niklas 2442 F pulseaudio
- /dev/snd/controlC0: niklas 2442 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: niklas 2442 F pulseaudio
+ /dev/snd/controlC0: niklas 2442 F pulseaudio
CurrentDesktop: KDE
Date: Tue Nov
[Kernel-packages] [Bug 1851380] Re: root can lift kernel lockdown
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851380
Title:
root can lift kernel lockdown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Invalid
Status in linux source package in Bionic:
Triaged
Status in linux source package in Disco:
Triaged
Status in linux source package in Eoan:
Triaged
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification
Impact: The kernel lockdown support adds a sysrq to allow a physically
present user to disable lockdown from the keyboard. A bug in the
implementation makes it possible to also lift lockdown by writing to
/proc/sysrq-trigger.
Fix: Correct the logic to disallow disabling lockdown via /proc/sysrq-
trigger.
Test Case: Write "x" to /proc/sysrq-trigger. When working properly
there should be no messages in dmesg about lifting lockdown, and
lockdown restrictions (e.g. loading unsigned modules) should remain in
effect.
Regression Potential: Anyone using /proc/sysrq-trigger to disable
lockdown will no longer be able to do so. Implementation bugs could
prevent use of the sysrq from the keyboard from disabling lockdown,
but this has been confrimed to still work with the fix in place.
---
Echoing "x" into /proc/sysrq-trigger disables kernel lockdown, even
though it shouldn't.
If I'm not mistaken, kernel lockdown is meant to create a barrier
between root and the kernel that can only be broken with physical
access to the system. It is automatically enabled when the system is
booted with UEFI Secure Boot, which is the case for me.
This should show the bug:
# echo "x" > /proc/sysrq-trigger
Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
Nov 05 14:58:15 panzersperre kernel: This sysrq operation is disabled from
userspace.
Nov 05 14:58:15 panzersperre kernel: Disabling Secure Boot restrictions
Nov 05 14:58:15 panzersperre kernel: Lifting lockdown
Note that it first says that the operation is disabled and then performs this
operation.
This should only be possible by physically pressing sysrq+x on an attached
keyboard.
I'm doing this on 4.15.0-68-generic on Ubuntu 18.04.3 LTS.
I have kernel.sysrq set to 1 - this is important to be able to trigger this
bug. (But I don't think it disqualifies this issue as non-security relevant
because root can trivially execute `sysctl kernel.sysrq=1`.)
I first learned about this by reading a blog post
(https://gehrcke.de/2019/09/running-an-ebpf-program-may-require-
lifting-the-kernel-lockdown/), so I'm not the first to notice this
behavior (even though this post doesn't say it's a bug).
Looking through drivers/tty/sysrq.c, I guess the problem is caused by
this if condition in __handle_sysrq:
554 │ /* Ban synthetic events from some sysrq functionality */
555 │ if ((from == SYSRQ_FROM_PROC || from ==
SYSRQ_FROM_SYNTHETIC) &&
556 │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
557 │ printk("This sysrq operation is disabled from
userspace.\n");
558 │ /*
559 │ * Should we check for enabled operations
(/proc/sysrq-trigger
560 │ * should not) and is the invoked operation enabled?
561 │ */
562 │ if (from == SYSRQ_FROM_KERNEL ||
sysrq_on_mask(op_p->enable_mask)) {
563 │ pr_cont("%s\n", op_p->action_msg);
564 │ console_loglevel = orig_log_level;
565 │ op_p->handler(key);
566 │ } else {
567 │ pr_cont("This sysrq operation is disabled.\n");
568 │ }
Note that `op_p->enable_mask & SYSRQ_DISABLE_USERSPACE` just causes a
printk and no change of behavior.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-68-generic 4.15.0-68.77
ProcVersionSignature: Ubuntu 4.15.0-68.77-generic 4.15.18
Uname: Linux 4.15.0-68-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: niklas 2442 F pulseaudio
/dev/snd/controlC0: niklas 2442 F pulseaudio
CurrentDesktop: KDE
Date: Tue Nov 5 14:58:33 2019
InstallationDate: Installed on 2015-12-11 (1424 days ago)
InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: LENOVO 20E8S00600
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-68-generic
root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet
splash kaslr i915.alpha_support=1 vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-68-generic N/A
linux-backports-modules-4.15.0-68-generic N/A
linux-firmware 1.173.11
SourcePackage: linux
UpgradeStatus:
[Kernel-packages] [Bug 1851350] Re: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 17:06 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:depwait variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 17:06 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait variant: debs -- 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/1851350 Title: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 17:06 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
4.15: ovl_get_origin_fh detects zero sized files on lower paths and treats these a special zero sized "copied up but origin unknown" magic. [ 25.442916] ovl_check_origin: etc/.pwd.lock 2 [ 25.442918] ovl_get_origin_fh: 104 etc/.pwd.lock [ 25.442919] ovl_get_origin_fh: 107 res=0 [ 25.442920] ovl_get_origin_fh: 117 res == 0, return NULL [ 25.442921] ovl_get_origin: 179 fh = (null) 1 [ 25.442922] ovl_get_origin_fh: 104 etc/.pwd.lock [ 25.442922] ovl_get_origin_fh: 107 res=0 [ 25.442923] ovl_get_origin_fh: 117 res == 0, return NULL [ 25.442923] ovl_get_origin: 179 fh = (null) 1 5.3: the lower is / and hence is a directory hence the S_IFDIR origin return. [ 33.320630] ovl_get_fh: 112 dentry: etc/.pwd.lock name: trusted.overlay.origin [ 33.320632] ovl_get_fh: 115: res = 29 [ 33.320634] ovl_get_fh: 152: return fh = 6e71855c [ 33.320634] ovl_check_origin: 413 fh = 6e71855c [ 33.320635] ovl_check_origin_fh: 354 upperdentry = etc/.pwd.lock [ 33.320635] ovl_decode_real_fh: 174 [ 33.320769] ovl_decode_real_fh: 211 return dentry (OK) [ 33.320769] ovl_check_origin_fh: 360, i=0, origin = / [ 33.320770] ovl_check_origin_fh: level=0 upper: etc/.pwd.lock 100600, lower: / 40755 [ 33.320770] ovl_check_origin_fh: 380 goto invalid [ 33.320771] overlayfs: invalid origin (etc/.pwd.lock, ftype=8000, origin ftype=4000). [ 33.320773] ovl_check_origin: 422 err = -5 [ 33.320774] ovl_check_origin: 429, return -5 -- 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/1824407 Title: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Bionic: Confirmed Bug description: 1) Download focal subiquity pending image, or eoan release image 2) boot, and press ESC and edit boot command line (F6 in bios, e in UEFI) 3) After --- insert the following options break=top debug init=/bin/bash 4) Continue boot (Enter in BIOS, ctrl+x in UEFI) 5) in the initramfs execute: rm /scripts/casper-bottom/25adduser exit 6) you will be dropped into pivoted root filesystem, before systemd is execed as pid one 7) /run/initramfs/ will contain a debug log, showing how everything was mounted. Ie. cdrom mounted, squashfs losetup from there, then multilower overlay setup from them, moved to /root, and then pivot-root to /root done to finally end up as /. Underlying layers are moved into /cow for your convenience. 8) At this point modifying zero-byte length files, that exist in the lowest layer, but not the middle one, in certain ways, will results in them to be corrupted, after / is remounted. 9) Corruption examples (On both focal & eoan) cat /etc/.pwd.lock systemd-sysusers cat /etc/.pwd.lock mount -o remount / cat /etc/.pwd.lock overlayfs: invalid origin (etc/.pwd.lock, ftype=8000, origin ftype=4000) cat: /etc/.pwd.lock: Input/output error (Only on eoan) cat /etc/machine-id systemd-machine-id-setup cat /etc/machine-id mount -o remount / cat /etc/machine-id overlayfs: invalid origin (etc/machine-id, ftype=8000, origin ftype=4000) cat: /etc/machine-id: Input/output error Lots of things break once machine-id and .pwd.lock are corrupted. I.e. unable to dhcp, connect to dbus, add/remove/change users or groups, etc. We were unable to recreate the issue outside of booting things with casper. Ie. statically on a regular host machine without pivot-root. But hopefully booting to a quite state with nothing running is sufficient to reproduce this. Instead of booting with `bebroken init=/bin/bash` you can boot with `bebroken systemd.mask=systemd-remount-fs.service` this will complete the boot, with /etc/machine-id & .pwd.lock modified, meaning that remount of / will cause IO errors on those files. Currently, we are shipping two hacks in casper's 25adduser script to "rm" the offending files, and create them again on the upper rw layer. They then survive remount without i/o errors. However, we'd rather not ship those hacks, and have kernel overlay fixed to work correctly with multi-lower-dir and not corrupt files upon remounting /. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846288] Re: 5G connectivity on Intel AC9260 gradually diminishes during usage
Hi, just updating this, the backports solution did not work for me. At this point it is a serious enough problem to roll back and wait for a more durable fix. -- 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/1846288 Title: 5G connectivity on Intel AC9260 gradually diminishes during usage Status in linux package in Ubuntu: Confirmed Bug description: Intel AC9260 will connect to 5G WiFi without issue. However, after a few minutes of use, the connection will slow to a crawl and eventually time out until manually switched to a traditional WiFi. Other devices on the same 5G network do not experience this behavior. This behavior does not occur under 18.04LTS. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 23:15:35 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-10-01 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eric 1795 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-01 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) MachineType: Dell Inc. XPS 15 9570 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=cbdfb299-4ef9-49ab-adb8-0c346f806bb7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eric 1795 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-01 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) MachineType: Dell Inc. XPS 15 9570 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=cbdfb299-4ef9-49ab-adb8-0c346f806bb7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1851380] Re: root can lift kernel lockdown
** Information type changed from Private Security to Public Security
--
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/1851380
Title:
root can lift kernel lockdown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Invalid
Status in linux source package in Bionic:
Triaged
Status in linux source package in Disco:
Triaged
Status in linux source package in Eoan:
Triaged
Status in linux source package in Focal:
In Progress
Bug description:
Echoing "x" into /proc/sysrq-trigger disables kernel lockdown, even
though it shouldn't.
If I'm not mistaken, kernel lockdown is meant to create a barrier
between root and the kernel that can only be broken with physical
access to the system. It is automatically enabled when the system is
booted with UEFI Secure Boot, which is the case for me.
This should show the bug:
# echo "x" > /proc/sysrq-trigger
Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
Nov 05 14:58:15 panzersperre kernel: This sysrq operation is disabled from
userspace.
Nov 05 14:58:15 panzersperre kernel: Disabling Secure Boot restrictions
Nov 05 14:58:15 panzersperre kernel: Lifting lockdown
Note that it first says that the operation is disabled and then performs this
operation.
This should only be possible by physically pressing sysrq+x on an attached
keyboard.
I'm doing this on 4.15.0-68-generic on Ubuntu 18.04.3 LTS.
I have kernel.sysrq set to 1 - this is important to be able to trigger this
bug. (But I don't think it disqualifies this issue as non-security relevant
because root can trivially execute `sysctl kernel.sysrq=1`.)
I first learned about this by reading a blog post
(https://gehrcke.de/2019/09/running-an-ebpf-program-may-require-
lifting-the-kernel-lockdown/), so I'm not the first to notice this
behavior (even though this post doesn't say it's a bug).
Looking through drivers/tty/sysrq.c, I guess the problem is caused by
this if condition in __handle_sysrq:
554 │ /* Ban synthetic events from some sysrq functionality */
555 │ if ((from == SYSRQ_FROM_PROC || from ==
SYSRQ_FROM_SYNTHETIC) &&
556 │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
557 │ printk("This sysrq operation is disabled from
userspace.\n");
558 │ /*
559 │ * Should we check for enabled operations
(/proc/sysrq-trigger
560 │ * should not) and is the invoked operation enabled?
561 │ */
562 │ if (from == SYSRQ_FROM_KERNEL ||
sysrq_on_mask(op_p->enable_mask)) {
563 │ pr_cont("%s\n", op_p->action_msg);
564 │ console_loglevel = orig_log_level;
565 │ op_p->handler(key);
566 │ } else {
567 │ pr_cont("This sysrq operation is disabled.\n");
568 │ }
Note that `op_p->enable_mask & SYSRQ_DISABLE_USERSPACE` just causes a
printk and no change of behavior.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-68-generic 4.15.0-68.77
ProcVersionSignature: Ubuntu 4.15.0-68.77-generic 4.15.18
Uname: Linux 4.15.0-68-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: niklas 2442 F pulseaudio
/dev/snd/controlC0: niklas 2442 F pulseaudio
CurrentDesktop: KDE
Date: Tue Nov 5 14:58:33 2019
InstallationDate: Installed on 2015-12-11 (1424 days ago)
InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: LENOVO 20E8S00600
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-68-generic
root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet
splash kaslr i915.alpha_support=1 vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-68-generic N/A
linux-backports-modules-4.15.0-68-generic N/A
linux-firmware 1.173.11
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-07-05 (487 days ago)
dmi.bios.date: 09/26/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: JHET69WW (1.69 )
dmi.board.asset.tag: Not Available
dmi.board.name: Intel powered classmate PC
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrJHET69WW(1.69):bd09/26/2018:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad 11e
dmi.product.name: 20E8S00600
dmi.product.version: ThinkPad 11e
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1851412] Re: Verify kexec image signatures on arm64
** Information type changed from Private Security to Public Security
--
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/1851412
Title:
Verify kexec image signatures on arm64
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Disco:
Invalid
Status in linux source package in Eoan:
Invalid
Status in linux source package in Focal:
Invalid
Bug description:
While reviewing our kernel configs in Focal, I noticed that we produce
signed arm64 kernels since Disco but don't seem to be verifying any
signatures during kexec. Specifically, CONFIG_KEXEC_IMAGE_VERIFY_SIG
is not enabled.
== Disco ==
$ git grep CONFIG_KEXEC_IMAGE_VERIFY_SIG
debian.master/debian.master/config/annotations:CONFIG_KEXEC_IMAGE_VERIFY_SIG
policy<{'arm64': 'n'}>
debian.master/config/annotations:CONFIG_KEXEC_IMAGE_VERIFY_SIG
flag
debian.master/config/config.common.ubuntu:# CONFIG_KEXEC_IMAGE_VERIFY_SIG is
not set
== Eoan ==
$ git grep CONFIG_KEXEC_IMAGE_VERIFY_SIG debian.master/
debian.master/config/annotations:CONFIG_KEXEC_IMAGE_VERIFY_SIG
policy<{'arm64': 'n'}>
debian.master/config/annotations:CONFIG_KEXEC_IMAGE_VERIFY_SIG
flag
debian.master/config/config.common.ubuntu:# CONFIG_KEXEC_IMAGE_VERIFY_SIG is
not set
Looking at the Ubuntu-5.3.0-19.20 tag in Eoan, it looks like the
CONFIG_KEXEC_IMAGE_VERIFY_SIG option should be enabled to perform signature
verification of kexec images:
$ cat -n arch/arm64/kernel/kexec_image.c | tail -n 15
116#ifdef CONFIG_KEXEC_IMAGE_VERIFY_SIG
117static int image_verify_sig(const char *kernel, unsigned long
kernel_len)
118{
119return verify_pefile_signature(kernel, kernel_len, NULL,
120
VERIFYING_KEXEC_PE_SIGNATURE);
121}
122#endif
123
124const struct kexec_file_ops kexec_image_ops = {
125.probe = image_probe,
126.load = image_load,
127#ifdef CONFIG_KEXEC_IMAGE_VERIFY_SIG
128.verify_sig = image_verify_sig,
129#endif
130};
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851412/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841288] Re: does not create compressed dump on 5.0 or later kernels
I was able to verify both releases. *** Disco test, with kernel 5.0.0-32-generic *** Running kdump-tools/makedumpfile from -updates pocket : $ file vmcore.201911051825 vmcore.201911051825: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1 (SYSV), SVR4-style Running the -proposed packages for kdump-tools and makedumpfile, version 1:1.6.5-1ubuntu1.3 : $ file dump.201911051840 dump.201911051840: Kdump compressed dump v6, system Linux, node gpiccoli-ppc64, release 5.0.0-32-generic, version #34-Ubuntu SMP Wed Oct 2 02:06:32 UTC 2019, machine ppc64le, domain (none) *** Bionic test, with kernel 5.0.0-32-generic *** Running kdump-tools/makedumpfile from -updates pocket : $ file vmcore.201911051957 vmcore.201911051957: ELF 64-bit LSB core file 64-bit PowerPC or cisco 7500, version 1 (SYSV), SVR4-style Also, saw the following message in console while makedumpfile was trying to collect the compressed dump: "get_machdep_info_ppc64: Can't detect max_physmem_bits." Running the -proposed packages for kdump-tools and makedumpfile, version 1:1.6.5-1ubuntu1~18.04.3 : $ file dump.201911052003 dump.201911052003: Kdump compressed dump v6, system Linux, node bionic-ppc, release 5.0.0-32-generic, version #34~18.04.2-Ubuntu SMP Thu Oct 10 10:35:58 UTC 2019, machine ppc64le, domain (none) ** Tags removed: verification-needed verification-needed-bionic verification-needed-disco ** Tags added: verification-done verification-done-bionic verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1841288 Title: does not create compressed dump on 5.0 or later kernels Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Disco: Fix Committed Bug description: [Impact] On ppc64el, makedumpfile won't create compressed dumps, causing them to be very large. This affects any kernel later than 4.19 actually. [Test case] Crash a system with kdump-tools installed and enabled, by using the following sequence. Verify the created dumps are compressed by using file. This is the same test as the autopkgtest for makedumpfile. echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Regression potential] This is a small fix and should only impact ppc64el. Older kernels should still work, and should be tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1841288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)
I am having this issue with a DELL XPS 13 (Intel HD 620). -- 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/1848741 Title: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have graphics artefacts: screan tearing, pieces of the previous window appear in the newly opened window. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-08 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4
** Also affects: linux-raspi2 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Eoan) Status: New => Triaged ** Changed in: linux-raspi2 (Ubuntu Eoan) Importance: Undecided => High -- 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/1848790 Title: USB not working under arm64 on Pi4 Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Triaged Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
The following packages ended up in the wrong component in the Proposed pocket: linux-restricted-modules-azure-5.3 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-5.3.0-1006-azure 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-azure-edge 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-5.3.0-1006-azure 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-azure-edge 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-cloud-tools-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-headers-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-image-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-modules-extra-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-signed-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-signed-image-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-tools-azure-edge 5.3.0.1006.6 - is in main instead of universe Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + promote-to-proposed: Stalled -- packages are in the wrong component + regression-testing: Ongoing -- testing in progress + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- packages are in the wrong component regression-testing: Ongoing -- testing in progress
[Kernel-packages] [Bug 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
The following packages ended up in the wrong component in the Proposed pocket: linux-restricted-modules-gcp-5.3 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-5.3.0-1007-gcp 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-gcp-edge 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-5.3.0-1007-gcp 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-gcp-edge 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-headers-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-image-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-modules-extra-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-tools-gcp-edge 5.3.0.1007.7 - is in main instead of universe Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + promote-to-proposed: Stalled -- packages are in the wrong component + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress variant: debs -- 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/1850967 Title: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- packages are in the wrong component regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6
Ok, this is a complex matter. I just experienced this unpleasant feature on my laptop using the above described driver and hardware for the last two days. =>It seems to be a radio transmission issue.<= The Linux driver as well as the microcode of the WiFi device must be able to cope with the small frequency jumps of the access point. Yes, frequencies are =>NOT<= very stable. This is shown in the logs by the following messages: wpa_supplicant[971]: wlp1s0: CTRL-EVENT-SIGNAL- CHANGE. When this event occurs, your hardware must resync with the access point. The driver as well as the microcode of your WiFi device may or may not support such a frequency jump. In other term they may or may not be able to cope with the noise. The following log message shows that my system was not able to cope with it: iwlwifi :01:00.0: Microcode SW error detected. What actually solved the issue is re-configuring the access point. I limited the channel width on the 2.4 Ghz frequency to 20 Mhz to avoid interference with other access points in the area. In addition I defined a precise channel for the access. For the channel selection, prefer channel 1, 6 or 11, since they do not overlap. Now my connection is stable and my logs are clean. For the 5 Ghz network, these problem might not occur as frequently as on the 2.4 Ghz one, since it is less used. In case similar issues are faced, proceed similarly. Hope it helps, Illi Same comment was also posted in the dupplicate of this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1808389 Title: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 Status in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Committed Status in The Bionic Beaver: Confirmed Status in linux-firmware source package in Bionic: Fix Released Status in The Cosmic Cuttlefish: Confirmed Status in linux-firmware source package in Cosmic: Fix Released Bug description: SRU Justification: === [Impact] repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6. [Fix] New iwlwifi firmware fix it. [Test] Bug reporter verified with positive result. [Regression Potential] Upstream fix, low risk. Bug reporter confirms fix. Original bug report: = Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6. Firmware: 36.7596afd4.0 Dec 13 11:53:36 james-x1 kernel: [ 856.840159] wlp2s0: send auth to 60:38:e0:70:a2:11 (try 1/3) Dec 13 11:53:36 james-x1 kernel: [ 856.844875] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. Dec 13 11:53:36 james-x1 kernel: [ 856.845015] iwlwifi :02:00.0: Start IWL Error Log Dump: Dec 13 11:53:36 james-x1 kernel: [ 856.845018] iwlwifi :02:00.0: Status: 0x0100, count: 6 Dec 13 11:53:36 james-x1 kernel: [ 856.845021] iwlwifi :02:00.0: Loaded firmware version: 36.7596afd4.0 Dec 13 11:53:36 james-x1 kernel: [ 856.845024] iwlwifi :02:00.0: 0x1006 | ADVANCED_SYSASSERT Dec 13 11:53:36 james-x1 kernel: [ 856.845026] iwlwifi :02:00.0: 0x02F0 | trm_hw_status0 Dec 13 11:53:36 james-x1 kernel: [ 856.845029] iwlwifi :02:00.0: 0x | trm_hw_status1 Dec 13 11:53:36 james-x1 kernel: [ 856.845031] iwlwifi :02:00.0: 0x000248DC | branchlink2 Dec 13 11:53:36 james-x1 kernel: [ 856.845034] iwlwifi :02:00.0: 0x0003A7DA | interruptlink1 Dec 13 11:53:36 james-x1 kernel: [ 856.845036] iwlwifi :02:00.0: 0x | interruptlink2 Dec 13 11:53:36 james-x1 kernel: [ 856.845039] iwlwifi :02:00.0: 0xFEDA | data1 Dec 13 11:53:36 james-x1 kernel: [ 856.845041] iwlwifi :02:00.0: 0xDEADBEEF | data2 Dec 13 11:53:36 james-x1 kernel: [ 856.845044] iwlwifi :02:00.0: 0xDEADBEEF | data3 Dec 13 11:53:36 james-x1 kernel: [ 856.845046] iwlwifi :02:00.0: 0x0007E1DC | beacon time Dec 13 11:53:36 james-x1 kernel: [ 856.845048] iwlwifi :02:00.0: 0x003B0850 | tsf low Dec 13 11:53:36 james-x1 kernel: [ 856.845051] iwlwifi :02:00.0: 0x | tsf hi Dec 13 11:53:36 james-x1 kernel: [ 856.845053] iwlwifi :02:00.0: 0x | time gp1 Dec 13 11:53:36 james-x1 kernel: [ 856.845055] iwlwifi :02:00.0: 0x003B0852 | time gp2 Dec 13 11:53:36 james-x1 kernel: [ 856.845058] iwlwifi :02:00.0: 0x0001 | uCode revision type Dec 13 11:53:36 james-x1 kernel: [ 856.845060] iwlwifi :02:00.0: 0x0024 | uCode version major Dec 13 11:53:36 james-x1 kernel: [ 856.845063] iwlwifi :02:00.0: 0x7596AFD4 | uCode version minor Dec 13 11:53:36 james-x1 kernel: [ 856.845065] iwlwifi :02:00.0: 0x0230 | hw version Dec 13 11:53:36 james-x1 kernel: [ 856.845068] iwlwifi :02:00.0: 0x18489000 | board version Dec 13 11:53:36 james-x1 kernel: [ 856.845070] iwlwifi :02:00.0:
[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.
*** This bug is a duplicate of bug 1808389 *** https://bugs.launchpad.net/bugs/1808389 Ok, this is a complex matter. I just experienced this unpleasant feature on my laptop using the above described driver and hardware for the last two days. =>It seems to be a radio transmission issue.<= (and this is damned complex!) The Linux driver as well as the microcode of the WiFi device must be able to cope with the small frequency jumps of the access point. Yes, frequencies are =>NOT<= very stable. This is shown in the logs by the following messages: wpa_supplicant[971]: wlp1s0: CTRL-EVENT-SIGNAL- CHANGE. When this event occurs, your hardware must resync with the access point. The driver as well as the microcode of your WiFi device may or may not support such a frequency jump. In other term they may or may not be able to cope with the noise. The following log message shows that my system was not able to cope with it: iwlwifi :01:00.0: Microcode SW error detected. What actually solved the issue is re-configuring the access point. I limited the channel width on the 2.4 Ghz frequency to 20 Mhz to avoid interference with other access points in the area. In addition I defined a precise channel for the access. For the channel selection, prefer channel 1, 6 or 11, since they do not overlap. Now my connection is stable and my logs are clean. For the 5 Ghz network, these problem might not occur as frequently as on the 2.4 Ghz one, since it is less used. In case similar issues are faced, proceed similarly. Hope it helps, Illi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1804841 Title: iwlwifi Microcode SW error detected. Restarting 0x200. Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Incomplete Bug description: This seems to be a return of an existing bug, in newer hardware and microcode versions. Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78) Firmware version: 34.0.1 Description:Ubuntu 18.04.1 LTS Frequent errors as soon as I connect to wifi: Microcode SW error detected. Restarting 0x200. Expected to happen: Great and stable wifi like a couple of weeks ago What happens: very slow, intermittent internet access, lots of ping loss Found a suggestion of a workaround: adding these lines to /etc/NetworkManager/NetworkManager.conf [device] wifi.scan-rand-mac-address=no These lines were already there, not added by me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode] ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Nov 23 15:23:54 2018 Dependencies: InstallationDate: Installed on 2018-09-03 (81 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832151] Re: Unexpected CFS throttling
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1832151 Title: Unexpected CFS throttling Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: New Status in linux source package in Eoan: Incomplete Bug description: Basically, this issue: https://bugzilla.kernel.org/show_bug.cgi?id=198197 ..is affecting a cloud provider on a 4.15 kernel. Customer testing with a kernel that is patched with the fix (upstream: de53fd7aedb100f03e5d2231cfce0e4993282425 ) confirms that it resolves the issue. More details in the SalesForce ticket: https://canonical.my.salesforce.com/5003z1yUmC1 [Impact] * Aggressive throttling by CFS causes severe performance degradation in some cases. [Test Case] * This reproducer clearly shows the problem before the fix and shows no problem after the fix: https://gist.github.com/bobrik/2030ff040fad360327a5fab7a09c4ff1 [Regression Potential] * It touches core scheduler code so regression could be bad - but risk is low as the patch is accepted in mainline and tested separately by myself, the cloud provider, and at least 2 others. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- 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/1850967 Title: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851416] [NEW] Prime Profiles page could be better
Public bug reported: There are 4 possibly problem points, placement, names, tooltips, help. The 1st 3 are somewhat linked. The new profile, NVIDIA On-Demand is currently placed between the 2 previous & historical ones of NVIDIA.. & Intel.. The placement and name could lead one to believe that it's an app on demand or as needed similar to how optimus works in windows. This is clearly not the case & if picked produces a degraded experience for most users.. It should be the 3rd listed profile and if possible named more towards it's actual use case. There previously were 2 tooltips on hover, currently there still are just 2, the one designed for Intel now exposes only when hovered over NVIDIA On-Demand, hovering over Intel produces nothing NVIDIA On-Demand should get it's own tooltip. The Help button popup shows no info on what NVIDIA On-Demand is about or for, considering the vast majority of users should not use that profile it should be described, ect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-settings 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Nov 5 12:18:49 2019 InstallationDate: Installed on 2019-10-29 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191029.2) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-settings (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 nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1851416 Title: Prime Profiles page could be better Status in nvidia-settings package in Ubuntu: New Bug description: There are 4 possibly problem points, placement, names, tooltips, help. The 1st 3 are somewhat linked. The new profile, NVIDIA On-Demand is currently placed between the 2 previous & historical ones of NVIDIA.. & Intel.. The placement and name could lead one to believe that it's an app on demand or as needed similar to how optimus works in windows. This is clearly not the case & if picked produces a degraded experience for most users.. It should be the 3rd listed profile and if possible named more towards it's actual use case. There previously were 2 tooltips on hover, currently there still are just 2, the one designed for Intel now exposes only when hovered over NVIDIA On-Demand, hovering over Intel produces nothing NVIDIA On-Demand should get it's own tooltip. The Help button popup shows no info on what NVIDIA On-Demand is about or for, considering the vast majority of users should not use that profile it should be described, ect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-settings 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Nov 5 12:18:49 2019 InstallationDate: Installed on 2019-10-29 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191029.2) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1851416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303085/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory 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' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303087/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory 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' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] Re: Missing modules for cryptography and NFSv4
apport information ** Tags added: apport-collected bionic ** Description changed: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. - Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit - much. + Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. + --- + ProblemType: Bug + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory + 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' + CRDA: N/A + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 + InstallationDate: Installed on 2017-02-11 (996 days ago) + InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: Error: command ['lsusb'] failed with exit code 1: + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 + ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-1048-kvm N/A + linux-backports-modules-4.15.0-1048-kvm N/A + linux-firmware 1.173.9 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic + Uname: Linux 4.15.0-1048-kvm x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) + UserGroups: + + _MarkForUpload: False + dmi.bios.date: 04/01/2014 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: 1.10.2-1ubuntu1 + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-i440fx-xenial + dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: + dmi.product.name: Standard PC (i440FX + PIIX, 1996) + dmi.product.version: pc-i440fx-xenial + dmi.sys.vendor: QEMU ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303080/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l',
[Kernel-packages] [Bug 1851382] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303084/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory 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' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303083/+files/PciMultimedia.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/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory 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' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303081/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory 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' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303089/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory 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' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303088/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory 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' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303086/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory 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' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303082/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory 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' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851350] Re: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 - phase: Packaging - phase-changed: Tuesday, 05. November 2019 10:25 UTC + phase: Holding before Promote to Proposed + phase-changed: Tuesday, 05. November 2019 17:06 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait variant: debs -- 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/1851350 Title: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 17:06 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838245] Re: dkms script is missing function find_module
This changes seems to have been dropped in Ubuntu 19.10 and Focal.
** Changed in: dkms (Ubuntu)
Status: Fix Released => Confirmed
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1838245
Title:
dkms script is missing function find_module
Status in DKMS:
Fix Released
Status in dkms package in Ubuntu:
Confirmed
Status in dkms source package in Bionic:
Fix Released
Bug description:
update for SRU process:
[Impact]
1. dkms script is missing function find_module
2. priority of OBSOLETE_BY should higher than "force". #89
https://github.com/dell/dkms/issues/89
[Test case]
install the dkms which already patched (also can be found in my ppa[1])
1. install a dkms which for a kernel module system already installed.
e.g. ath10k of my testing ppa : [1]
1.1. the dkms can be installed well.
2. install a dkms which has OBSOLETE_BY and FORCE
e.g.ath10k of my testing ppa : [1] (source code in [2])
- the target dkms defined OBSOLETE_BY and FORCE
- user install dkms on a system which installed kernel version less than
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
- the dkms can be installed well.
[Regression potential]
medium as it touched the version sanity. This change correct the code logic
and land one more change from upstream as well.
The logic has been verified by #5 and me.
Building a kernel module using dkms in Linux Mint 19.1 shows the following
error:
Running module version sanity check.
/usr/sbin/dkms: Zeile 784: find_module: Befehl nicht gefunden
modinfo: ERROR: missing module or filename.
Checking the file the function is indeed missing and another user
confirmed, that it was removed at some point:
https://github.com/linuxmint/linuxmint/issues/142
Possible solution: Readd
find_module()
{
# tree = $1
# module = $2
find "$1" -name "$2$module_uncompressed_suffix" -o -name
"$2$module_suffix" -type f
return $?
}
as found in https://github.com/dell/dkms/blob/master/dkms
To manage notifications about this bug go to:
https://bugs.launchpad.net/dkms/+bug/1838245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827961] Re: Lenovo dock MAC Address pass through doesn't work in Ubuntu
https://lkml.org/lkml/2019/11/5/398 -- 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/1827961 Title: Lenovo dock MAC Address pass through doesn't work in Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Similar to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 the MAC address pass through does not work with a Lenovo Thunderbolt 3 Workstation Dock. The dock's network port is recognized and working but it has its own MAC address even though MAC Address pass through is enabled in the BIOS. This is the dock in question: https://www.lenovo.com/us/en/accessories-and-monitors/top-tech /Thunderbolt-WS-230W-dock-US/p/40AN0230US and the laptop is a Lenovo P1. Debug files attached. Please let me know if further info is required. Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rauer 2107 F pulseaudio /dev/snd/controlC1: rauer 2107 F pulseaudio /dev/snd/controlC0: rauer 2107 F pulseaudio CurrentDesktop: i3 Date: Mon May 6 19:34:26 2019 InstallationDate: Installed on 2019-04-09 (27 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 20MES1WH00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET39W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MES1WH00 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET39W(1.21):bd04/15/2019:svnLENOVO:pn20MES1WH00:pvrThinkPadP1:rvnLENOVO:rn20MES1WH00:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 dmi.product.name: 20MES1WH00 dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1 dmi.product.version: ThinkPad P1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:queued variant: debs -- 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/1850967 Title: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:queued variant: debs -- 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837525] Comment bridged from LTC Bugzilla
--- Comment From andreas.kreb...@de.ibm.com 2019-11-05 10:42 EDT--- (In reply to comment #16) > Rebuilding eoan gcc-9.2.1 and comparing test results between -march=zEC12 & > -march=z13 -mtune=z15 > > There appear to be (a) improved test results (FAIL->PASS) (b) not supported > tests anymore (PASS->missing) (c) regressed tests (PASS->FAIL). This needs > investigating. I will publish raw logs (massaged to reduce non-reproducible > directory names) shortly. Here are some highlights. ... I've applied a few patches fixing these issues to GCC mainline and GCC 9 branch: https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00282.html -- 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/1837525 Title: [20.04 FEAT] Set Architecture Level (ALS) to z13 Status in Ubuntu on IBM z Systems: Fix Committed Status in gcc-9 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Bug description: IBM requests to update the Architecture Level Set (ALS) as follow.. march=z13 mtune=z15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1837525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- package copied to Proposed lrm:building,signed:depwait variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed lrm:building,signed:depwait + promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait variant: debs -- 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/1850967 Title: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] 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 1851382 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/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Incomplete Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
