[Kernel-packages] [Bug 1822308] Re: vmx_hlt_with_rvi_test in kvm_unit_tests fails
Failed on Oracle B-4.15 Passed on Oracle B-5.0 ** Tags added: sru-20191021 ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1822308 Title: vmx_hlt_with_rvi_test in kvm_unit_tests fails Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: TESTNAME=vmx_hlt_with_rvi_test TIMEOUT=10 ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append vmx_hlt_with_rvi_test FAIL vmx_hlt_with_rvi_test (timeout; duration=10) Detailed report will be appended here later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830084] Re: ubuntu_kernel_selftests ftrace fails
Can be found on Oracle B-5.0 as well. ** Tags added: sru-20191021 ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- 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/1830084 Title: ubuntu_kernel_selftests ftrace fails Status in ubuntu-kernel-tests: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-gcp package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: Confirmed Status in linux-gcp source package in Disco: Confirmed Status in linux-oracle source package in Disco: New Bug description: Cloud: Azure Series: Disco Kernel: 5.0.0-1007.7 linux-azure Instance: Standard_D2_v3 and others. 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > /proc/sys/net/ipv4/conf/all/accept_local'' 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done for 'all'. 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13 05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest 05/20 14:24:27 DEBUG| utils:0153| [stdout] 05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal number: 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests === 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file check 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for tracers 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock test 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing check 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the ringbuffer size 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing setting 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and trace_marker 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic event - add/remove kprobe events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic event - add/remove synthetic events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic event - selective clear (compatibility) 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic event - generic clear event 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - enable/disable with event level files 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - restricts events based on pid 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - enable/disable with subsystem level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - enable/disable with top level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [16] Test trace_printk from module 05/20 14:24:36 DEBUG| utils:0153| [stdout] -e [UNRESOLVED] 05/20 14:24:36 DEBUG|
[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4
To test this, is there an sd card image of ubuntu for pi4 I can flash? -- 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 1848983] Re: bionic/linux-aws-5.0: 5.0.0-1020.22~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: 1848984 packages: lrm: linux-restricted-modules-aws-5.0 main: linux-aws-5.0 meta: linux-meta-aws-5.0 phase: Testing phase-changed: Wednesday, 23. October 2019 16:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - 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/1848983 Title: bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -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 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 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: 1848984 packages: lrm: linux-restricted-modules-aws-5.0 main: linux-aws-5.0 meta: linux-meta-aws-5.0 phase: Testing phase-changed: Wednesday, 23. October 2019 16:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848983] Re: bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -proposed tracker
5.0.0-1020.22~18.04.1 - aws Regression test CMPL, RTB. Issue to note in arm64 (aws): ubuntu_kernel_selftests - msg_zerocopy in net on some nodes (bug 1812620) ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) cgroup_fj_* failure caused by memcg_test_3 (bug 1836694) hugemmap05* / hugemmap06 (bug 1851606) getaddrinfo_01 (bug 1829995) ubuntu_ltp_syscalls - msgstress03 on some nodes (bug 1783881) Skipped / blacklisted: * libhugetlbfs * tsc * ubuntu_32_on_64 * ubuntu_seccomp * ubuntu_sysdig_smoke_test Issue to note in x86_64 (aws): tsc - failed on i3.metal ubuntu_kernel_selftests - msg_zerocopy in net on some nodes (bug 1812620) ubuntu_kvm_unit_tests - vmx on i3.metal (1821394) ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) cpuset_hotplug (bug 1834006) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) leapsec_timer (bug 1829971) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) cve-2017-17053 (bug 1830011) ltp_acpi (bug 1829982) ubuntu_ltp_syscalls - msgstress03 on some nodes (bug 1783881) Skipped / blacklisted: * libhugetlbfs ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1848983 Title: bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -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 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 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: 1848984 packages: lrm: linux-restricted-modules-aws-5.0 main: linux-aws-5.0 meta: linux-meta-aws-5.0 phase: Testing phase-changed: Wednesday, 23. October 2019 16:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849484]
The folks over at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484 are saying they think that bug is the same as this one, but I don't think it is. What do you think? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have an LG ultra-wide (2560x1080) monitor. Sometimes when I plug it into my laptop, whose screen was working fine before I plugged it in, both screens go black but nothing else happens. I can still see the mouse cursor and move it between the two monitors (sometimes in the correct location configuration I've configured, sometimes not), but nothing is rendered on the screens. Sometimes when I plug the monitor in, it comes on, but the resolution is wrong. Sometimes it is actually recognized and configured correctly. Frequently I have to unplug the monitor and plug it back in three times or more before it is recognized correctly. I wish it just worked right the first time. :-/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 08:34:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (40 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago) --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jik3196 F pulseaudio /dev/snd/pcmC1D0p: jik3196 F...m pulseaudio /dev/snd/controlC0: jik3196 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292] InstallationDate: Installed on 2019-09-12 (45 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan ubuntu Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Kernel-packages] [Bug 1813877] Re: Can't adjust brightness on DELL UHD dGPU AIO
** Description changed: [Impact] The dell-uart-backlight driver has been loaded, but the backlight is controller by graphics driver instead of scalar IC. The old way to determinate weather the driver should be loaded is not working anymore, since the behavior of scalar command, show firmware version, is not the same as old platforms. [Fix] Using more a reliable command, get_scalar_status, to check if scalar is in charge of the AIO backlight. + For the old platforms which don't have the new command, I add a list to list them all and use the old way to determinate the scalar IC. [Test] - Verified on new Dell AIO platforms. + Verified on old and new Dell AIO platforms. [Regression Potential] Low. The quirk lists all old platforms which use the old way to check if scalar IC is in use. So, it won't change the behavior on old platforms, and apply the new method on new platforms. ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Cosmic) ** No longer affects: linux-oem (Ubuntu Cosmic) ** No longer affects: linux-oem (Ubuntu Disco) ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Eoan) Importance: Undecided Status: New ** No longer affects: linux-oem (Ubuntu Eoan) ** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Assignee: AceLan Kao (acelankao) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813877 Title: Can't adjust brightness on DELL UHD dGPU AIO Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: In Progress Status in linux source package in Eoan: New Bug description: [Impact] The dell-uart-backlight driver has been loaded, but the backlight is controller by graphics driver instead of scalar IC. The old way to determinate weather the driver should be loaded is not working anymore, since the behavior of scalar command, show firmware version, is not the same as old platforms. [Fix] Using more a reliable command, get_scalar_status, to check if scalar is in charge of the AIO backlight. For the old platforms which don't have the new command, I add a list to list them all and use the old way to determinate the scalar IC. [Test] Verified on old and new Dell AIO platforms. [Regression Potential] Low. The quirk lists all old platforms which use the old way to check if scalar IC is in use. So, it won't change the behavior on old platforms, and apply the new method on new platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1813877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850654] Re: update-initramfs complains of missing amdgpu firmware files
Hello Seth, or anyone else affected, Accepted linux-firmware into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.183.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Eoan) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: New Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Committed Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849598] Re: [SRU][B/OEM-B/OEM-OSP1/D/E] Add RTL8822cu bluetooth support
Hello AaronMa, or anyone else affected, Accepted linux-firmware into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.183.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Eoan) Status: New => Fix Committed -- 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/1849598 Title: [SRU][B/OEM-B/OEM-OSP1/D/E] Add RTL8822cu bluetooth support Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-firmware source package in Bionic: New Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Disco: New Status in linux-firmware source package in Disco: New Status in linux-oem source package in Disco: New Status in linux source package in Eoan: New Status in linux-firmware source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: New Bug description: SRU justification: [Impact] Current kernel and firmware lack support of rtl8822cu Bluetooth. [Fix] Add and update the Bluetooth driver and firmware of rtl8822cu. [Test] Verified on hardware. Tests results are good. [Regression Potential] Low. Add new bt chip ID; Add the new firmware and config to enable new bt chip. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1849598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Hello manuel, or anyone else affected, Accepted linux-firmware into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.183.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Eoan) Status: New => Fix Committed -- 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: Fix Committed 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
[Kernel-packages] [Bug 1850739] Re: Revert the firmware update for sound/sof
Hello Hui, or anyone else affected, Accepted linux-firmware into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.183.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Eoan) Status: New => Fix Committed -- 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/1850739 Title: Revert the firmware update for sound/sof Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Disco: New Status in linux-firmware source package in Eoan: Fix Committed Bug description: SRU Justification Impact: An update to the sound sof firmware does not set the PV bit for cometlake, and thus will not load. This is a regression on cometlake platforms. Fix: Revert the update. Test Case: Check that the firmware will load on affected platforms. Regression Potential: This fixes a regression on cometlake paltforms, but will regress the platforms fixed by the patch being reverted. --- I submitted a firmware update for sound/sof, the tracking bug number is: https://bugs.launchpad.net/bugs/1847250 Recently we found this update introduced one problem for cometlake platforms, cometlake need to check PV bit when loading the firmware, but this update doesn't set the PV bit for cometlake, as a result, on cometlake platforms, it always fails to load the firmware. So we should revert this update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1850739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849051] Re: xenial/linux: 4.4.0-167.196 -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: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 22. October 2019 16:04 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: trusty/linux-aws: bug 1849048 trusty/linux-lts-xenial: bug 1849049 xenial/linux-aws: bug 1849041 xenial/linux-fips: bug 1849047 xenial/linux-kvm: bug 1849042 xenial/linux-raspi2: bug 1849044 xenial/linux-snapdragon: bug 1849046 xenial/linux/caracalla-kernel: bug 1849036 xenial/linux/pc-kernel: bug 1849037 xenial/linux/stlouis-kernel: bug 1849038 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/1849051 Title: xenial/linux: 4.4.0-167.196 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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 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 package in Ubuntu: Invalid Status in linux 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 22. October 2019 16:04 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 trackers: trusty/linux-aws: bug 1849048 trusty/linux-lts-xenial: bug 1849049 xenial/linux-aws: bug 1849041 xenial/linux-fips: bug 1849047 xenial/linux-kvm: bug 1849042 xenial/linux-raspi2: bug 1849044 xenial/linux-snapdragon: bug 1849046 xenial/linux/caracalla-kernel: bug 1849036 xenial/linux/pc-kernel: bug 1849037 xenial/linux/stlouis-kernel: bug 1849038 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849051/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849046] Re: xenial/linux-snapdragon: 4.4.0-1129.137 -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: 1849051 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 10:06 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: xenial/linux-snapdragon/dragonboard-kernel: bug 1849045 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/1849046 Title: xenial/linux-snapdragon: 4.4.0-1129.137 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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: Fix Released 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 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: 1849051 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 10:06 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 trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1849045 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849041] Re: xenial/linux-aws: 4.4.0-1097.108 -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: 1849051 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 22. October 2019 15:16 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-aws/aws-kernel: bug 1849040 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1849041 Title: xenial/linux-aws: 4.4.0-1097.108 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1849051 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 22. October 2019 15:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1849040 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849042] Re: xenial/linux-kvm: 4.4.0-1061.68 -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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1849042 Title: xenial/linux-kvm: 4.4.0-1061.68 -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: Fix Released 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 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: 1849051 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 22. October 2019 15:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849042] Re: xenial/linux-kvm: 4.4.0-1061.68 -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: 1849051 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 22. October 2019 15:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - 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/1849042 Title: xenial/linux-kvm: 4.4.0-1061.68 -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: Fix Released 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 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: 1849051 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 22. October 2019 15:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849046] Re: xenial/linux-snapdragon: 4.4.0-1129.137 -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-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1849046 Title: xenial/linux-snapdragon: 4.4.0-1129.137 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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: Fix Released 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 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: 1849051 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 10:06 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 trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1849045 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
I didn't mean actually random, and I think clock-based would be entirely fine, but my paranoia about stacking two things with identical superblocks might be just paranoia too. I dunno. -- You 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 1849051] Re: xenial/linux: 4.4.0-167.196 -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 in Ubuntu. https://bugs.launchpad.net/bugs/1849051 Title: xenial/linux: 4.4.0-167.196 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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 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 package in Ubuntu: Invalid Status in linux 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 22. October 2019 16:04 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 trackers: trusty/linux-aws: bug 1849048 trusty/linux-lts-xenial: bug 1849049 xenial/linux-aws: bug 1849041 xenial/linux-fips: bug 1849047 xenial/linux-kvm: bug 1849042 xenial/linux-raspi2: bug 1849044 xenial/linux-snapdragon: bug 1849046 xenial/linux/caracalla-kernel: bug 1849036 xenial/linux/pc-kernel: bug 1849037 xenial/linux/stlouis-kernel: bug 1849038 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849051/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849041] Re: xenial/linux-aws: 4.4.0-1097.108 -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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1849041 Title: xenial/linux-aws: 4.4.0-1097.108 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1849051 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 22. October 2019 15:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1849040 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777238] Re: video lag - Every 5 seconds a freeze frame when playing video of any source
Hi, I haven't read through this entire report, but I stumbled across it when searching for 'stutter every 5 sexonds'. I too had the issue, across many distros + compositors with Kodi (I didn't really test anything else). I have enabled the tear free option in a xorg.conf and the issue has disappeared. Might be worth you guys trying. https://askubuntu.com/questions/1066722/intel-screen-tearing- ubuntu-18-04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777238 Title: video lag - Every 5 seconds a freeze frame when playing video of any source Status in linux package in Ubuntu: Confirmed Bug description: The problem exists for months and I didn't find a good answer on it. It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind the video the sounds continues, but the video stops), youtube, Hangouts and every software where video is played. I experienced that there are 2 things that can break it: - if I move the mouse out and in on the affected window (it doesn't work in full screen) - if I open the system monitor, the problem also disappears other people also face with this problem: https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194 https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04 Ubuntu 4.15.0-23.25-generic 4.15.18 it was upgraded from 16.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 16 14:34:26 2018 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2016-08-04 (680 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vandor 3436 F pulseaudio /dev/snd/controlC1: vandor 3436 F pulseaudio /dev/snd/controlC0: vandor 3436 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c InstallationDate: Installed on 2016-08-04 (681 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849855] Re: bionic/linux: 4.15.0-68.77 -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 in Ubuntu. https://bugs.launchpad.net/bugs/1849855 Title: bionic/linux: 4.15.0-68.77 -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-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 package in Ubuntu: Invalid Status in linux 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1850799, bug 1851507 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849855] Re: bionic/linux: 4.15.0-68.77 -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: Tuesday, 29. October 2019 13:37 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-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 - bionic/linux-oem: bug 1851507, bug 1850799 + bionic/linux-oem: bug 1850799, bug 1851507 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 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/1849855 Title: bionic/linux: 4.15.0-68.77 -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-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 package in Ubuntu: Invalid Status in linux 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1850799, bug 1851507 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850574] Re: disco/linux: 5.0.0-34.36 -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:14 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-bluefield: bug 1849002 bionic/linux-hwe: bug 1850587 bionic/linux-oem-osp1: bug 1849001 disco/linux-aws: bug 1848984 disco/linux-azure: bug 1848989 disco/linux-gcp: bug 1848995 disco/linux-kvm: bug 1848996 disco/linux-oracle: bug 1848998 disco/linux-raspi2: bug 1848981 disco/linux-snapdragon: bug 1848999 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/1850574 Title: disco/linux: 5.0.0-34.36 -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-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 package in Ubuntu: Invalid Status in linux source package in Disco: 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:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1849002 bionic/linux-hwe: bug 1850587 bionic/linux-oem-osp1: bug 1849001 disco/linux-aws: bug 1848984 disco/linux-azure: bug 1848989 disco/linux-gcp: bug 1848995 disco/linux-kvm: bug 1848996 disco/linux-oracle: bug 1848998 disco/linux-raspi2: bug 1848981 disco/linux-snapdragon: bug 1848999 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850574] Re: disco/linux: 5.0.0-34.36 -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 in Ubuntu. https://bugs.launchpad.net/bugs/1850574 Title: disco/linux: 5.0.0-34.36 -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-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 package in Ubuntu: Invalid Status in linux source package in Disco: 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:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1849002 bionic/linux-hwe: bug 1850587 bionic/linux-oem-osp1: bug 1849001 disco/linux-aws: bug 1848984 disco/linux-azure: bug 1848989 disco/linux-gcp: bug 1848995 disco/linux-kvm: bug 1848996 disco/linux-oracle: bug 1848998 disco/linux-raspi2: bug 1848981 disco/linux-snapdragon: bug 1848999 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848996] Re: disco/linux-kvm: 5.0.0-1021.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 kernel-stable-master-bug: 1850574 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Wednesday, 23. October 2019 09:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - 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/1848996 Title: disco/linux-kvm: 5.0.0-1021.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: 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: Fix Released 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 Disco: 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: 1850574 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Wednesday, 23. October 2019 09:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848996/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848998] Re: disco/linux-oracle: 5.0.0-1006.10 -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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1848998 Title: disco/linux-oracle: 5.0.0-1006.10 -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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Disco: 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: 1850574 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 23. October 2019 09:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.0: bug 1848997 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848997] Re: bionic/linux-oracle-5.0: 5.0.0-1006.10~18.04.2 -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: 1848998 packages: lrm: linux-restricted-modules-oracle-5.0 main: linux-oracle-5.0 meta: linux-meta-oracle-5.0 signed: linux-signed-oracle-5.0 phase: Testing phase-changed: Friday, 01. November 2019 22:46 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 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/1848997 Title: bionic/linux-oracle-5.0: 5.0.0-1006.10~18.04.2 -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: 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: 1848998 packages: lrm: linux-restricted-modules-oracle-5.0 main: linux-oracle-5.0 meta: linux-meta-oracle-5.0 signed: linux-signed-oracle-5.0 phase: Testing phase-changed: Friday, 01. November 2019 22:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1848997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848995] Re: disco/linux-gcp: 5.0.0-1024.24 -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: 1850574 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 24. October 2019 15:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1848992 bionic/linux-gke-5.0: bug 1848994 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/1848995 Title: disco/linux-gcp: 5.0.0-1024.24 -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 Disco: 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: 1850574 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 24. October 2019 15:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1848992 bionic/linux-gke-5.0: bug 1848994 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848997] Re: bionic/linux-oracle-5.0: 5.0.0-1006.10~18.04.2 -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 in Ubuntu. https://bugs.launchpad.net/bugs/1848997 Title: bionic/linux-oracle-5.0: 5.0.0-1006.10~18.04.2 -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: 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: 1848998 packages: lrm: linux-restricted-modules-oracle-5.0 main: linux-oracle-5.0 meta: linux-meta-oracle-5.0 signed: linux-signed-oracle-5.0 phase: Testing phase-changed: Friday, 01. November 2019 22:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1848997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848999] Re: disco/linux-snapdragon: 5.0.0-1025.26 -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: 1850574 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 15:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED - 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-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1848999 Title: disco/linux-snapdragon: 5.0.0-1025.26 -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: Incomplete 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-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: 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: 1850574 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 15:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848998] Re: disco/linux-oracle: 5.0.0-1006.10 -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: 1850574 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 23. October 2019 09:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.0: bug 1848997 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/1848998 Title: disco/linux-oracle: 5.0.0-1006.10 -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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Disco: 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: 1850574 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 23. October 2019 09:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.0: bug 1848997 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848999] Re: disco/linux-snapdragon: 5.0.0-1025.26 -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-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1848999 Title: disco/linux-snapdragon: 5.0.0-1025.26 -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: Incomplete 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-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: 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: 1850574 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 15:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848995] Re: disco/linux-gcp: 5.0.0-1024.24 -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/1848995 Title: disco/linux-gcp: 5.0.0-1024.24 -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 Disco: 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: 1850574 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 24. October 2019 15:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1848992 bionic/linux-gke-5.0: bug 1848994 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848996] Re: disco/linux-kvm: 5.0.0-1021.22 -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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1848996 Title: disco/linux-kvm: 5.0.0-1021.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: 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: Fix Released 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 Disco: 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: 1850574 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Wednesday, 23. October 2019 09:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848996/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848992] Re: bionic/linux-gcp: 5.0.0-1024.24~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: 1848995 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 24. October 2019 14:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-edge: bug 1848991 bionic/linux-gcp/gcp-kernel: bug 1848990 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/1848992 Title: bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -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-gcp package in Ubuntu: Invalid Status in linux-gcp 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: 1848995 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 24. October 2019 14:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-edge: bug 1848991 bionic/linux-gcp/gcp-kernel: bug 1848990 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848992] Re: bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -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/1848992 Title: bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -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-gcp package in Ubuntu: Invalid Status in linux-gcp 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: 1848995 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 24. October 2019 14:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-edge: bug 1848991 bionic/linux-gcp/gcp-kernel: bug 1848990 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848989] Re: disco/linux-azure: 5.0.0-1024.25 -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: 1850574 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Wednesday, 23. October 2019 09:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1848987 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1848989 Title: disco/linux-azure: 5.0.0-1024.25 -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 stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: 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: 1850574 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Wednesday, 23. October 2019 09:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1848987 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848989] Re: disco/linux-azure: 5.0.0-1024.25 -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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1848989 Title: disco/linux-azure: 5.0.0-1024.25 -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 stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: 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: 1850574 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Wednesday, 23. October 2019 09:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1848987 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Maybe after the proposed kernel is verified To test -proposed kernel, with the old arm64 image: edit /etc/apt/sources.list and add below to that file: deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed main restricted deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed universe deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed multiverse sudo apt-get update sudo apt install linux-image-5.3.0-1011-raspi2 sudo reboot Then the image will run the proposed kernel, and users could check it by 'uname -a', it will show 5.3.0-1011 -- 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 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test
** Changed in: linux (Ubuntu Eoan) Status: Confirmed => In Progress ** Changed in: ubuntu-kernel-tests Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu Disco) Importance: Undecided => High ** Changed in: linux (Ubuntu Eoan) 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/1849281 Title: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Confirmed Status in linux source package in Eoan: In Progress Bug description: SRU Justification Impact: We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER. Fix: The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of the former ifndef's scope. Regression Potential: Limited to seccomp selftests. Test Case: Compile the selftests on a kernel that supports SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds. Target Kernels: All current LTS kernels with access to a 5.0 kernel. Patches: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848987] Re: bionic/linux-azure: 5.0.0-1024.25~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: 1848989 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 24. October 2019 14:12 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: bionic/linux-azure-edge: bug 1848986 bionic/linux-azure/azure-kernel: bug 1848985 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1848987 Title: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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: 1848989 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 24. October 2019 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1848986 bionic/linux-azure/azure-kernel: bug 1848985 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851216] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Disco) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1851216 Title: System hangs at early boot Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Confirmed Status in linux-oem source package in Bionic: In Progress Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: Confirmed Status in linux-oem source package in Disco: New Status in linux-oem-osp1 source package in Disco: New Bug description: After upgrading kernel to linux-image-4.15.0-1061 (proposed), system hangs at very beginning of booting, leaving Grub messages "loading..." on the console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1060-oem 4.15.0-1060.69 ProcVersionSignature: Ubuntu 4.15.0-1060.69-oem 4.15.18 Uname: Linux 4.15.0-1060-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: u 1977 F...m pulseaudio /dev/snd/pcmC1D0p: u 1977 F...m pulseaudio /dev/snd/controlC0: u 1977 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 4 17:15:56 2019 InstallationDate: Installed on 2019-11-04 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Precision 5530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1060-oem root=UUID=baa02b0a-d18f-41d2-9e2b-2d057742013c ro mem_sleep_default=deep nvidia-drm.modeset=1 quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-1060-oem N/A linux-backports-modules-4.15.0-1060-oem N/A linux-firmware 1.173.9 SourcePackage: linux-oem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0184M4 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd06/27/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0184M4:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848987] Re: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1848987 Title: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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: 1848989 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 24. October 2019 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1848986 bionic/linux-azure/azure-kernel: bug 1848985 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851216] Re: System hangs at early boot
Confirmed that patch alone fixes this issue. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Disco) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1851216 Title: System hangs at early boot Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Confirmed Status in linux-oem source package in Bionic: In Progress Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: Confirmed Status in linux-oem source package in Disco: New Status in linux-oem-osp1 source package in Disco: New Bug description: After upgrading kernel to linux-image-4.15.0-1061 (proposed), system hangs at very beginning of booting, leaving Grub messages "loading..." on the console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1060-oem 4.15.0-1060.69 ProcVersionSignature: Ubuntu 4.15.0-1060.69-oem 4.15.18 Uname: Linux 4.15.0-1060-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: u 1977 F...m pulseaudio /dev/snd/pcmC1D0p: u 1977 F...m pulseaudio /dev/snd/controlC0: u 1977 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 4 17:15:56 2019 InstallationDate: Installed on 2019-11-04 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Precision 5530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1060-oem root=UUID=baa02b0a-d18f-41d2-9e2b-2d057742013c ro mem_sleep_default=deep nvidia-drm.modeset=1 quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-1060-oem N/A linux-backports-modules-4.15.0-1060-oem N/A linux-firmware 1.173.9 SourcePackage: linux-oem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0184M4 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd06/27/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0184M4:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848983] Re: bionic/linux-aws-5.0: 5.0.0-1020.22~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: 1848984 packages: lrm: linux-restricted-modules-aws-5.0 main: linux-aws-5.0 meta: linux-meta-aws-5.0 phase: Testing phase-changed: Wednesday, 23. October 2019 16:17 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 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/1848983 Title: bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -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 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: 1848984 packages: lrm: linux-restricted-modules-aws-5.0 main: linux-aws-5.0 meta: linux-meta-aws-5.0 phase: Testing phase-changed: Wednesday, 23. October 2019 16:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1848983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848984] Re: disco/linux-aws: 5.0.0-1020.22 -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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1848984 Title: disco/linux-aws: 5.0.0-1020.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: 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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: 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: 1850574 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Wednesday, 23. October 2019 10:19 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1848983 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848984] Re: disco/linux-aws: 5.0.0-1020.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 kernel-stable-master-bug: 1850574 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Wednesday, 23. October 2019 10:19 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1848983 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1848984 Title: disco/linux-aws: 5.0.0-1020.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: 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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: 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: 1850574 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Wednesday, 23. October 2019 10:19 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1848983 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848983] Re: bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -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 in Ubuntu. https://bugs.launchpad.net/bugs/1848983 Title: bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -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 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: 1848984 packages: lrm: linux-restricted-modules-aws-5.0 main: linux-aws-5.0 meta: linux-meta-aws-5.0 phase: Testing phase-changed: Wednesday, 23. October 2019 16:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1848983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848981] Re: disco/linux-raspi2: 5.0.0-1021.21 -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: 1850574 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 23. October 2019 10:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED - 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-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848981 Title: disco/linux-raspi2: 5.0.0-1021.21 -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: Incomplete 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 Disco: 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: 1850574 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 23. October 2019 10:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848981] Re: disco/linux-raspi2: 5.0.0-1021.21 -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-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848981 Title: disco/linux-raspi2: 5.0.0-1021.21 -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: Incomplete 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 Disco: 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: 1850574 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 23. October 2019 10:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851216] Re: System hangs at early boot
First known working commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c8c4076723daca08bf35ccd68f22ea1c6219e207 "x86/timer: Skip PIT initialization on modern chipsets" (in v5.3-rc1) ** Changed in: linux-oem (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1851216 Title: System hangs at early boot Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: In Progress Bug description: After upgrading kernel to linux-image-4.15.0-1061 (proposed), system hangs at very beginning of booting, leaving Grub messages "loading..." on the console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1060-oem 4.15.0-1060.69 ProcVersionSignature: Ubuntu 4.15.0-1060.69-oem 4.15.18 Uname: Linux 4.15.0-1060-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: u 1977 F...m pulseaudio /dev/snd/pcmC1D0p: u 1977 F...m pulseaudio /dev/snd/controlC0: u 1977 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 4 17:15:56 2019 InstallationDate: Installed on 2019-11-04 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Precision 5530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1060-oem root=UUID=baa02b0a-d18f-41d2-9e2b-2d057742013c ro mem_sleep_default=deep nvidia-drm.modeset=1 quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-1060-oem N/A linux-backports-modules-4.15.0-1060-oem N/A linux-firmware 1.173.9 SourcePackage: linux-oem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0184M4 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd06/27/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0184M4:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1851216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851590] 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 1851590 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/1851590 Title: crypto error/warning when running update-initramfs on 5.0.0-34.36 Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: New Bug description: Warning were encountered when running update-initramfs on the new disco kernel, see comment in https://bugs.launchpad.net/ubuntu/+source /linux-gke-5.0/+bug/1847641/comments/6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851590] Re: crypto error/warning when running update-initramfs on 5.0.0-34.36
I don't believe this is anything new with the -34 kernel. I accidentally installed the -32 kernel because I didn't save the sources.list file with -proposed enabled and it gave me the same error. It appears to be because the image is not set up for encryption and the cryptsetup- initramfs package is installed. This appears to be more of an OS image issue than kernel. Console output: root@disco:/home/ubuntu# apt update Get:1 http://security.ubuntu.com/ubuntu disco-security InRelease [97.5 kB] ... Get:47 http://archive.ubuntu.com/ubuntu disco-backports/multiverse amd64 c-n-f Metadata [116 B] Fetched 17.1 MB in 5s (3111 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 43 packages can be upgraded. Run 'apt list --upgradable' to see them. root@disco:/home/ubuntu# uname -a Linux disco 5.0.0-31-generic #33-Ubuntu SMP Mon Sep 30 18:51:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@disco:/home/ubuntu# apt install linux-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: amd64-microcode crda intel-microcode iucode-tool iw libdbus-glib-1-2 libnl-genl-3-200 linux-firmware linux-headers-5.0.0-32 linux-headers-5.0.0-32-generic linux-headers-generic linux-headers-virtual linux-image-5.0.0-32-generic linux-image-generic linux-image-virtual linux-modules-5.0.0-32-generic linux-modules-extra-5.0.0-32-generic linux-virtual thermald wireless-regdb Suggested packages: fdutils linux-doc-5.0.0 | linux-source-5.0.0 linux-tools The following NEW packages will be installed: amd64-microcode crda intel-microcode iucode-tool iw libdbus-glib-1-2 libnl-genl-3-200 linux-firmware linux-generic linux-headers-5.0.0-32 linux-headers-5.0.0-32-generic linux-image-5.0.0-32-generic linux-image-generic linux-modules-5.0.0-32-generic linux-modules-extra-5.0.0-32-generic thermald wireless-regdb The following packages will be upgraded: linux-headers-generic linux-headers-virtual linux-image-virtual linux-virtual 4 upgraded, 17 newly installed, 0 to remove and 24 not upgraded. Need to get 148 MB of archives. After this operation, 796 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 libnl-genl-3-200 amd64 3.4.0-1 [11.1 kB] Get:2 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 wireless-regdb all 2018.05.09-0ubuntu1 [11.0 kB] Get:3 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 iw amd64 5.0.1-1 [87.7 kB] Get:4 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 crda amd64 3.18-1build1 [63.5 kB] Get:5 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 iucode-tool amd64 2.3.1-1 [45.6 kB] Get:6 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 libdbus-glib-1-2 amd64 0.110-4 [58.7 kB] Get:7 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-firmware all 1.178.3 [78.2 MB] Get:8 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-modules-5.0.0-32-generic amd64 5.0.0-32.34 [13.8 MB] Get:9 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-image-5.0.0-32-generic amd64 5.0.0-32.34 [8424 kB] Get:10 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-modules-extra-5.0.0-32-generic amd64 5.0.0-32.34 [33.5 MB] Get:11 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 intel-microcode amd64 3.20190618.0ubuntu0.19.04.1 [1922 kB] Get:12 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 amd64-microcode amd64 3.20181128.1ubuntu1 [32.3 kB] Get:13 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-image-generic amd64 5.0.0.32.33 [2368 B] Get:14 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-virtual amd64 5.0.0.32.33 [1860 B] Get:15 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-image-virtual amd64 5.0.0.32.33 [2344 B] Get:16 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-headers-virtual amd64 5.0.0.32.33 [1844 B] Get:17 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-headers-5.0.0-32 all 5.0.0-32.34 [10.8 MB] Get:18 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-headers-5.0.0-32-generic amd64 5.0.0-32.34 [1246 kB] Get:19 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-headers-generic amd64 5.0.0.32.33 [2324 B] Get:20 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-generic amd64 5.0.0.32.33 [1868 B] Get:21 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 thermald amd64 1.8.0-1ubuntu1 [187 kB] Fetched 148 MB in 5s (32.1 MB/s) Selecting previously unselected package libnl-genl-3-200:amd64. (Reading database ... 60203 files and directories
[Kernel-packages] [Bug 1851590] Re: crypto error/warning when running update-initramfs on 5.0.0-34.36
** Changed in: linux-gke-5.0 (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gke-5.0 (Ubuntu) ** No longer affects: linux-gke-5.0 (Ubuntu Disco) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851590 Title: crypto error/warning when running update-initramfs on 5.0.0-34.36 Status in linux package in Ubuntu: New Status in linux source package in Disco: New Bug description: Warning were encountered when running update-initramfs on the new disco kernel, see comment in https://bugs.launchpad.net/ubuntu/+source /linux-gke-5.0/+bug/1847641/comments/6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847641] Re: fdatasync performance regression on 5.0 kernels
** Tags removed: verification-needed-disco verification-needed-eoan ** Tags added: verification-bionic-disco verification-bionic-eoan ** Tags removed: verification-bionic-disco verification-bionic-eoan ** Tags added: verification-needed-disco verification-needed-eoan ** Tags removed: verification-needed-disco verification-needed-eoan ** Tags added: verification-done-disco 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/1847641 Title: fdatasync performance regression on 5.0 kernels Status in linux package in Ubuntu: Fix Committed Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-gke-5.0 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-gke-5.0 source package in Eoan: Invalid Bug description: More info in salesforce: https://canonical.my.salesforce.com/5003z20tIcX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847641] Re: fdatasync performance regression on 5.0 kernels
Disco verification: SUCCESS (except for crypt error not seen on Eoan when running update-initramfs) The package did experience a crypt error while the finish scripts were running update-initramfs: update-initramfs: Generating /boot/initrd.img-5.0.0-34-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. I1107 01:20:47.416048 1 iotest.go:34] Starting loop... I1107 01:20:47.416130 1 iotest.go:38] Generating chunk done. Took: 35.664µs I1107 01:20:47.416180 1 iotest.go:45] Writing chunk done. Took: 39.66µs I1107 01:20:47.418845 1 iotest.go:49] Fdatasync done. Took: 2.655269ms I1107 01:20:48.419035 1 iotest.go:34] Starting loop... I1107 01:20:48.419118 1 iotest.go:38] Generating chunk done. Took: 35.264µs I1107 01:20:48.419179 1 iotest.go:45] Writing chunk done. Took: 48.533µs I1107 01:20:48.421913 1 iotest.go:49] Fdatasync done. Took: 2.717937ms I1107 01:20:49.422100 1 iotest.go:34] Starting loop... I1107 01:20:49.422178 1 iotest.go:38] Generating chunk done. Took: 28.414µs I1107 01:20:49.42 1 iotest.go:45] Writing chunk done. Took: 31.93µs I1107 01:20:49.424807 1 iotest.go:49] Fdatasync done. Took: 2.5748ms I1107 01:20:50.425013 1 iotest.go:34] Starting loop... I1107 01:20:50.425100 1 iotest.go:38] Generating chunk done. Took: 26.333µs I1107 01:20:50.425153 1 iotest.go:45] Writing chunk done. Took: 35.647µs I1107 01:20:50.429562 1 iotest.go:49] Fdatasync done. Took: 4.399009ms I1107 01:20:51.429771 1 iotest.go:34] Starting loop... I1107 01:20:51.429857 1 iotest.go:38] Generating chunk done. Took: 35.83µs I1107 01:20:51.429900 1 iotest.go:45] Writing chunk done. Took: 30.646µs I1107 01:20:51.432736 1 iotest.go:49] Fdatasync done. Took: 2.828024ms # uname -a Linux cnewcomer-1573089286 5.0.0-34-generic #36-Ubuntu SMP Wed Oct 30 05:16:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847641 Title: fdatasync performance regression on 5.0 kernels Status in linux package in Ubuntu: Fix Committed Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-gke-5.0 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-gke-5.0 source package in Eoan: Invalid Bug description: More info in salesforce: https://canonical.my.salesforce.com/5003z20tIcX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847641] Re: fdatasync performance regression on 5.0 kernels
Eoan Verification: SUCCESS Eoan: I1107 01:13:14.719551 1 iotest.go:34] Starting loop... I1107 01:13:14.719636 1 iotest.go:38] Generating chunk done. Took: 29.737µs I1107 01:13:14.719693 1 iotest.go:45] Writing chunk done. Took: 44.206µs I1107 01:13:14.723320 1 iotest.go:49] Fdatasync done. Took: 3.616042ms I1107 01:13:15.723595 1 iotest.go:34] Starting loop... I1107 01:13:15.723664 1 iotest.go:38] Generating chunk done. Took: 26.125µs I1107 01:13:15.723709 1 iotest.go:45] Writing chunk done. Took: 32.533µs I1107 01:13:15.726895 1 iotest.go:49] Fdatasync done. Took: 3.177235ms I1107 01:13:16.727150 1 iotest.go:34] Starting loop... I1107 01:13:16.727263 1 iotest.go:38] Generating chunk done. Took: 17.628µs I1107 01:13:16.727331 1 iotest.go:45] Writing chunk done. Took: 37.676µs I1107 01:13:16.730810 1 iotest.go:49] Fdatasync done. Took: 3.468056ms I1107 01:13:17.731056 1 iotest.go:34] Starting loop... I1107 01:13:17.731140 1 iotest.go:38] Generating chunk done. Took: 36.62µs I1107 01:13:17.731186 1 iotest.go:45] Writing chunk done. Took: 33.776µs I1107 01:13:17.734490 1 iotest.go:49] Fdatasync done. Took: 3.294855ms I1107 01:13:18.734697 1 iotest.go:34] Starting loop... I1107 01:13:18.734782 1 iotest.go:38] Generating chunk done. Took: 28.668µs I1107 01:13:18.734832 1 iotest.go:45] Writing chunk done. Took: 36.553µs I1107 01:13:18.737912 1 iotest.go:49] Fdatasync done. Took: 3.070391ms # uname -a Linux cnewcomer-1573088148 5.3.0-21-generic #22-Ubuntu SMP Tue Oct 29 22:55:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847641 Title: fdatasync performance regression on 5.0 kernels Status in linux package in Ubuntu: Fix Committed Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-gke-5.0 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-gke-5.0 source package in Eoan: Invalid Bug description: More info in salesforce: https://canonical.my.salesforce.com/5003z20tIcX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
** Also affects: linux-raspi2 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Eoan) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Committed Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834875] Re: cloud-init growpart race with udev
flock will not block inotify or udev events being emitted. See https://github.com/systemd/systemd/blob/master/src/udev/udevd.c#L322 https://github.com/systemd/systemd/blob/master/src/udev/udevd.c#L409 it will prevent udevd from running the rules against it. Thus effectively the event will be fired and done, but nothing actually executed for it. " /* apply rules, create node, symlinks */" Also, most importantly udevd also takes locks on devices, thus if one cannot take a lock on it, it means it shouldn't be touched yet as udevd is still processing it. Yeah, i read code and ioctls both call, and I have no idea which one is better, or what the difference is. If partx works, cool. But also, I thought udev should be updating partition tables all by itself. I somehow wonder if we even need partx call, if we properly flock the device and trigger udev after everything is done. Udev rules should be safe to be retriggered like that. But also, we should retrigger the expected events which have been skipped. So does growpart create partition? move it? delete/recreate one? i.e does ADD happen? or like REMOVE & ADD? or maybe it's like just MOVE or CHANGE? Do we have logs of the emitted events already? Don't like flags, as then we'll have to supported forever =) maybe env variable? or like simply change in focal and compare focal vs eoan? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: New Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
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
[Kernel-packages] [Bug 1851350] Re: bionic/linux-aws-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-aws-5.3 5.3.0-1006.6~18.04.1 - is in universe instead of multiverse linux-modules-nvidia-390-5.3.0-1006-aws 5.3.0-1006.6~18.04.1 - is in universe instead of multiverse linux-modules-nvidia-390-aws-wip 5.3.0-1006.6~18.04.1 - is in universe instead of multiverse linux-modules-nvidia-430-5.3.0-1006-aws 5.3.0-1006.6~18.04.1 - is in universe instead of multiverse linux-modules-nvidia-430-aws-wip 5.3.0-1006.6~18.04.1 - is in universe instead of multiverse 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/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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Promote to Proposed phase-changed: Wednesday, 06. November 2019 09:25 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/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: 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 promote-to-proposed series: Incomplete 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid 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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Promote to Proposed phase-changed: Wednesday, 06. November 2019 09:25 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/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
** Also affects: dkms (Ubuntu Focal)
Importance: Critical
Status: Confirmed
** Also affects: dkms (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: dkms (Ubuntu Eoan)
Status: New => Triaged
** Changed in: dkms (Ubuntu Focal)
Status: Confirmed => Triaged
--
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:
Triaged
Status in dkms source package in Bionic:
Fix Released
Status in dkms source package in Eoan:
Triaged
Status in dkms source package in Focal:
Triaged
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 1851351] Re: bionic/linux-oracle-5.3: 5.3.0-1005.5~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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Promote to Proposed phase-changed: Wednesday, 06. November 2019 20:58 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/1851351 Title: bionic/linux-oracle-5.3: 5.3.0-1005.5~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: 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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Promote to Proposed phase-changed: Wednesday, 06. November 2019 20:58 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/1851351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
When I'm more awake tomorrow I'll send a patch upstream as a suggested fix and see if we can get a good solution on the UUIDs worked out. -- You 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 1849917] Re: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem)
Additional dmesg output, right after the problem appears for the first time (sometime after booting, definitely not related to suspend as I supposed in my first message). ** Attachment added: "dmesg-2.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+attachment/5303375/+files/dmesg-2.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/1849917 Title: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 19.10 from 19.04 I noticed the mouse moves unequally/choppy. I did a fresh install (deleting and overwriting 19.04 with 19.10). For example: When I want to go to a button the cursor sometimes stops on the way to it and moves on milliseconds later. In Ubuntu Ubuntu 19.04 (which is my daily driver for now) this behavior is not present. Please let me now if I can add some further information. lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 All available system updates were installed. No extensions added additionally. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 06:23:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-20 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
I thought all lowerdirs must be read-only, and the first one in the stack will win. Even if there are same ones down the stack it shouldn't matter. But I guess needs testing. I wouldn't want to use random, as that will eat entropy on early boot of Ubuntu Core systems. Do we need a separate upstream issue to create uuid in the squashfs Superblock? On Wed, 6 Nov 2019, 21:21 Adam Conrad, wrote: > While there may be arguments for synthesizing UUIDs in various fs > drivers, or creating them in the first place in fs-creation tools, I > agree that if overlayfs has a hard dependency on UUIDs for uniquely > identifying layers, it needs to fill in the gaps where the previous > tools/drivers failed to provide. > > So, yeah, I think Colin's on the right track here with making overlayfs > itself fix its own use-case, which will cover any future filesystem/tool > that otherwise fails to UUID itself. > > My only review of the above is that you might want to mix a monotonic or > random seed in with your superblock when generating your fake UUIDs, in > case someone does something like stacking multiple empties on top of > each other, or some other madness where you effectively have the same > superblock more than once at the RO level, but need to identify them as > different. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824407 > > Title: > remount of multilower moved pivoted-root overlayfs root, results in > I/O errors on some modified files > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824407/+subscriptions > -- You 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
Re: [Kernel-packages] [Bug 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
At least it doesn't mangle email notifications! Such that in email code is readable. On Wed, 6 Nov 2019, 18:50 Colin Ian King, <1824...@bugs.launchpad.net> wrote: > Just love the way launchpad mangles pasted code. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824407 > > Title: > remount of multilower moved pivoted-root overlayfs root, results in > I/O errors on some modified files > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824407/+subscriptions > -- You 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 1851351] Re: bionic/linux-oracle-5.3: 5.3.0-1005.5~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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Promote to Proposed phase-changed: Wednesday, 06. November 2019 20:58 UTC reason: - promote-to-proposed: Stalled -- review in progress + 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/1851351 Title: bionic/linux-oracle-5.3: 5.3.0-1005.5~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: 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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Promote to Proposed phase-changed: Wednesday, 06. November 2019 20:58 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/1851351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851469] Re: Incorrect raspi2 snapcraft.yaml file
** Changed in: linux-raspi2 (Ubuntu Disco) Status: New => In Progress ** Changed in: linux-raspi2 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-raspi2 (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux-raspi2 (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: linux-raspi2 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-raspi2 (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux-raspi2 (Ubuntu Disco) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-raspi2 (Ubuntu Eoan) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-raspi2 (Ubuntu Focal) Assignee: (unassigned) => Juerg Haefliger (juergh) -- 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: In Progress Status in linux-raspi2 source package in Disco: In Progress Status in linux-raspi2 source package in Eoan: In Progress Status in linux-raspi2 source package in Focal: In Progress 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. Try to snap the kernel: $ snapcraft --target-arch=armhf [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 1851506] Re: Add GeminiLake support on Intel int340x thermal device
** Changed in: linux-oem (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux-oem (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux-oem (Ubuntu Bionic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1851506 Title: Add GeminiLake support on Intel int340x thermal device Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-oem source package in Bionic: In Progress Bug description: [Impact] Intel GLK systems may overheat and trigger a shutdown when doing CPU stress test. It's because the CPU thermal zone is missing. [Fix] Add missing ID to let int340x device work. [Test] With the patch, the thermal zone "TCPU" is corretly created. In conjunction with latest thermald, the system doesn't get shutdown by overheating anymore. [Regression Potenial] Minimal. This patch only adds a missing ID, no functional change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1851506/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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: 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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Promote to Proposed phase-changed: Wednesday, 06. November 2019 09:25 UTC reason: - promote-to-proposed: Stalled -- review in progress + 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/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: Fix Committed 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: Promote to Proposed phase-changed: Wednesday, 06. November 2019 09:25 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/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 1849917] Re: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem)
And the dmesg. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+attachment/5303370/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849917 Title: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 19.10 from 19.04 I noticed the mouse moves unequally/choppy. I did a fresh install (deleting and overwriting 19.04 with 19.10). For example: When I want to go to a button the cursor sometimes stops on the way to it and moves on milliseconds later. In Ubuntu Ubuntu 19.04 (which is my daily driver for now) this behavior is not present. Please let me now if I can add some further information. lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 All available system updates were installed. No extensions added additionally. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 06:23:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-20 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849917] Re: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem)
I'm affected by what seems to be the same bug or a very similar one. Also Ubuntu 19.10 fresh install. Additional information from what I have observed on my machine : - It's not only the cursor that stutters but the whole machine freezes for an instant. It's most noticeable while scrolling or watching videos. - it does not start right away. Maybe after suspend ? I'm not yet sure. - I have the same information re the Inter wireless 8260 driver than mentioned by the other user (namely that it does not function). - On the other hand, I have tried disabling Wifi but it did not seem to have any effect (I will check again). Here are the dmesg and lpsci text files. Thanks for your help. ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+attachment/5303369/+files/lspcik.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/1849917 Title: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 19.10 from 19.04 I noticed the mouse moves unequally/choppy. I did a fresh install (deleting and overwriting 19.04 with 19.10). For example: When I want to go to a button the cursor sometimes stops on the way to it and moves on milliseconds later. In Ubuntu Ubuntu 19.04 (which is my daily driver for now) this behavior is not present. Please let me now if I can add some further information. lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 All available system updates were installed. No extensions added additionally. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 06:23:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-20 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851550] Re: Eoan update: 5.3.9 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + * io_uring: fix up O_NONBLOCK handling for sockets + * dm snapshot: introduce account_start_copy() and account_end_copy() + * dm snapshot: rework COW throttling to fix deadlock + * Btrfs: fix inode cache block reserve leak on failure to allocate data space + * btrfs: qgroup: Always free PREALLOC META reserve in btrfs_delalloc_release_extents() + * iio: adc: meson_saradc: Fix memory allocation order + * iio: fix center temperature of bmc150-accel-core + * libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature + * perf tests: Avoid raising SEGV using an obvious NULL dereference + * perf map: Fix overlapped map handling + * perf script brstackinsn: Fix recovery from LBR/binary mismatch + * perf jevents: Fix period for Intel fixed counters + * perf tools: Propagate get_cpuid() error + * perf annotate: Propagate perf_env__arch() error + * perf annotate: Fix the signedness of failure returns + * perf annotate: Propagate the symbol__annotate() error return + * perf annotate: Fix arch specific ->init() failure errors + * perf annotate: Return appropriate error code for allocation failures + * perf annotate: Don't return -1 for error when doing BPF disassembly + * staging: rtl8188eu: fix null dereference when kzalloc fails + * RDMA/siw: Fix serialization issue in write_space() + * RDMA/hfi1: Prevent memory leak in sdma_init + * RDMA/iw_cxgb4: fix SRQ access from dump_qp() + * RDMA/iwcm: Fix a lock inversion issue + * HID: hyperv: Use in-place iterator API in the channel callback + * kselftest: exclude failed TARGETS from runlist + * selftests/kselftest/runner.sh: Add 45 second timeout per test + * nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request + * arm64: cpufeature: Effectively expose FRINT capability to userspace + * arm64: Fix incorrect irqflag restore for priority masking for compat + * arm64: ftrace: Ensure synchronisation in PLT setup for Neoverse-N1 #1542419 + * tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()' + * tty: serial: rda: Fix the link time qualifier of 'rda_uart_exit()' + * serial/sifive: select SERIAL_EARLYCON + * tty: n_hdlc: fix build on SPARC + * misc: fastrpc: prevent memory leak in fastrpc_dma_buf_attach + * RDMA/core: Fix an error handling path in 'res_get_common_doit()' + * RDMA/cm: Fix memory leak in cm_add/remove_one + * RDMA/nldev: Reshuffle the code to avoid need to rebind QP in error path + * RDMA/mlx5: Do not allow rereg of a ODP MR + * RDMA/mlx5: Order num_pending_prefetch properly with synchronize_srcu + * RDMA/mlx5: Add missing synchronize_srcu() for MW cases + * gpio: max77620: Use correct unit for debounce times + * fs: cifs: mute -Wunused-const-variable message + * arm64: vdso32: Fix broken compat vDSO build warnings + * arm64: vdso32: Detect binutils support for dmb ishld + * serial: mctrl_gpio: Check for NULL pointer + * serial: 8250_omap: Fix gpio check for auto RTS/CTS + * arm64: Default to building compat vDSO with clang when CONFIG_CC_IS_CLANG + * arm64: vdso32: Don't use KBUILD_CPPFLAGS unconditionally + * efi/cper: Fix endianness of PCIe class code + * efi/x86: Do not clean dummy variable in kexec path + * MIPS: include: Mark __cmpxchg as __always_inline + * riscv: avoid kernel hangs when trapped in BUG() + * riscv: avoid sending a SIGTRAP to a user thread trapped in WARN() + * riscv: Correct the handling of unexpected ebreak in do_trap_break() + * x86/xen: Return from panic notifier + * ocfs2: clear zero in unaligned direct IO + * fs: ocfs2: fix possible null-pointer dereferences in ocfs2_xa_prepare_entry() + * fs: ocfs2: fix a possible null-pointer dereference in ocfs2_write_end_nolock() + * fs: ocfs2: fix a possible null-pointer dereference in ocfs2_info_scan_inode_alloc() + * btrfs: silence maybe-uninitialized warning in clone_range + * arm64: armv8_deprecated: Checking return value for memory allocation + * x86/cpu: Add Comet Lake to the Intel CPU models header + * sched/fair: Scale bandwidth quota and period without losing quota/period ratio precision + * sched/vtime: Fix
[Kernel-packages] [Bug 1851549] Re: Xenial update: 4.4.199 upstream stable release
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ * scsi: ufs: skip shutdown if hba is not powered
+ * scsi: megaraid: disable device when probe failed after enabled device
+ * scsi: qla2xxx: Fix unbound sleep in fcport delete path.
+ * ARM: OMAP2+: Fix missing reset done flag for am3 and am43
+ * ARM: dts: am4372: Set memory bandwidth limit for DISPC
+ * nl80211: fix null pointer dereference
+ * mips: Loongson: Fix the link time qualifier of 'serial_exit()'
+ * net: hisilicon: Fix usage of uninitialized variable in function
mdio_sc_cfg_reg_write()
+ * namespace: fix namespace.pl script to support relative paths
+ * loop: Add LOOP_SET_DIRECT_IO to compat ioctl
+ * net: bcmgenet: Fix RGMII_MODE_EN value for GENET v1/2/3
+ * net: bcmgenet: Set phydev->dev_flags only for internal PHYs
+ * sctp: change sctp_prot .no_autobind with true
+ * net: avoid potential infinite loop in tc_ctl_action()
+ * ipv4: Return -ENETUNREACH if we can't create route but saddr is valid
+ * memfd: Fix locking when tagging pins
+ * USB: legousbtower: fix memleak on disconnect
+ * usb: udc: lpc32xx: fix bad bit shift operation
+ * USB: serial: ti_usb_3410_5052: fix port-close races
+ * USB: ldusb: fix memleak on disconnect
+ * USB: usblp: fix use-after-free on disconnect
+ * USB: ldusb: fix read info leaks
+ * scsi: core: try to get module before removing device
+ * ASoC: rsnd: Reinitialize bit clock inversion flag for every format setting
+ * cfg80211: wext: avoid copying malformed SSIDs
+ * mac80211: Reject malformed SSID elements
+ * drm/edid: Add 6 bpc quirk for SDC panel in Lenovo G50
+ * scsi: zfcp: fix reaction on bit error threshold notification
+ * mm/slub: fix a deadlock in show_slab_objects()
+ * xtensa: drop EXPORT_SYMBOL for outs*/ins*
+ * parisc: Fix vmap memory leak in ioremap()/iounmap()
+ * CIFS: avoid using MID 0x
+ * btrfs: block-group: Fix a memory leak due to missing btrfs_put_block_group()
+ * memstick: jmb38x_ms: Fix an error handling path in 'jmb38x_ms_probe()'
+ * cpufreq: Avoid cpufreq_suspend() deadlock on system shutdown
+ * xen/netback: fix error path of xenvif_connect_data()
+ * PCI: PM: Fix pci_power_up()
+ * net: sched: Fix memory exposure from short TCA_U32_SEL
+ * RDMA/cxgb4: Do not dma memory off of the stack
+ * Linux 4.4.198
+ * UBUNTU: upstream stable to v4.4.198
+ * dm snapshot: use mutex instead of rw_semaphore
+ * dm snapshot: introduce account_start_copy() and account_end_copy()
+ * dm snapshot: rework COW throttling to fix deadlock
+ * dm: Use kzalloc for all structs with embedded biosets/mempools
+ * sc16is7xx: Fix for "Unexpected interrupt: 8"
+ * x86/cpu: Add Atom Tremont (Jacobsville)
+ * scripts/setlocalversion: Improve -dirty check with git-status
--no-optional-locks
+ * usb: handle warm-reset port requests on hub resume
+ * exec: load_script: Do not exec truncated interpreter path
+ * iio: fix center temperature of bmc150-accel-core
+ * perf map: Fix overlapped map handling
+ * RDMA/iwcm: Fix a lock inversion issue
+ * fs: cifs: mute -Wunused-const-variable message
+ * serial: mctrl_gpio: Check for NULL pointer
+ * efi/cper: Fix endianness of PCIe class code
+ * efi/x86: Do not clean dummy variable in kexec path
+ * fs: ocfs2: fix possible null-pointer dereferences in
ocfs2_xa_prepare_entry()
+ * fs: ocfs2: fix a possible null-pointer dereference in
ocfs2_info_scan_inode_alloc()
+ * MIPS: fw: sni: Fix out of bounds init of o32 stack
+ * NFSv4: Fix leak of clp->cl_acceptor string
+ * tracing: Initialize iter->seq after zeroing in tracing_read_pipe()
+ * USB: legousbtower: fix a signedness bug in tower_probe()
+ * thunderbolt: Use 32-bit writes when writing ring producer/consumer
+ * fuse: flush dirty data/metadata before non-truncate setattr
+ * fuse: truncate pending writes on O_TRUNC
+ * ALSA: bebob: Fix prototype of helper function to return negative value
+ * UAS: Revert commit 3ae62a42090f ("UAS: fix alignment of scatter/gather
segments")
+ * USB: gadget: Reject endpoints with 0 maxpacket value
+ * USB: ldusb: fix ring-buffer locking
+ * USB: ldusb: fix control-message timeout
+ *
[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working
>From the bug history, this looks like an old bug that was fixed in Ubuntu (Bionic or cosmic?) a while ago, then upstreamed to linux-stable, then brought back to disco and eoan. The bug itself was not opened against eoan or disco, and so I don't think re-verification is needed on those 2 series. Therefore, I will mark the bug as "verification-done" for D and E. ** Tags removed: verification-needed-disco verification-needed-eoan ** Tags added: verification-done-disco 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/1795292 Title: ELAN469D touch pad not working Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844155] Re: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes
Thanks @adconrad This is the only outstanding issue for Xenial. I think we can wait another day or so before we have to make a final decision. I'll wait until tomorrow and then mark it as verified if you haven't already done so by then. -- You 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 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
While there may be arguments for synthesizing UUIDs in various fs drivers, or creating them in the first place in fs-creation tools, I agree that if overlayfs has a hard dependency on UUIDs for uniquely identifying layers, it needs to fill in the gaps where the previous tools/drivers failed to provide. So, yeah, I think Colin's on the right track here with making overlayfs itself fix its own use-case, which will cover any future filesystem/tool that otherwise fails to UUID itself. My only review of the above is that you might want to mix a monotonic or random seed in with your superblock when generating your fake UUIDs, in case someone does something like stacking multiple empties on top of each other, or some other madness where you effectively have the same superblock more than once at the RO level, but need to identify them as different. -- You 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 1851351] Re: bionic/linux-oracle-5.3: 5.3.0-1005.5~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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 06. November 2019 16:56 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 06. November 2019 20:58 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- review 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/1851351 Title: bionic/linux-oracle-5.3: 5.3.0-1005.5~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: In Progress 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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Promote to Proposed phase-changed: Wednesday, 06. November 2019 20:58 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851351] Re: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851351 Title: bionic/linux-oracle-5.3: 5.3.0-1005.5~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: In Progress 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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Promote to Proposed phase-changed: Wednesday, 06. November 2019 20:58 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849027] Re: xenial/linux-azure: 4.15.0-1062.67 -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-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 22. October 2019 15:49 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1849026 xenial/linux-azure-edge: bug 1849025 xenial/linux-azure/azure-kernel: bug 1849024 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1849027 Title: xenial/linux-azure: 4.15.0-1062.67 -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 stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 22. October 2019 15:49 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1849026 xenial/linux-azure-edge: bug 1849025 xenial/linux-azure/azure-kernel: bug 1849024 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849021] Re: xenial/linux-oracle: 4.15.0-1028.31~16.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: 1849022 packages: 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 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/1849021 Title: xenial/linux-oracle: 4.15.0-1028.31~16.04.1 -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-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1849022 packages: 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: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** 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: - 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: 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 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: 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 1849021] Re: xenial/linux-oracle: 4.15.0-1028.31~16.04.1 -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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1849021 Title: xenial/linux-oracle: 4.15.0-1028.31~16.04.1 -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-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1849022 packages: 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: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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/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-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: 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 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: 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 1849027] Re: xenial/linux-azure: 4.15.0-1062.67 -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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1849027 Title: xenial/linux-azure: 4.15.0-1062.67 -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 stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 22. October 2019 15:49 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1849026 xenial/linux-azure-edge: bug 1849025 xenial/linux-azure/azure-kernel: bug 1849024 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849855] Re: bionic/linux: 4.15.0-68.77 -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: Tuesday, 29. October 2019 13:37 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-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 - bionic/linux-oem: bug 1850799, bug 1851507 + bionic/linux-oem: bug 1851507, bug 1850799 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 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/1849855 Title: bionic/linux: 4.15.0-68.77 -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-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 package in Ubuntu: Invalid Status in linux 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 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-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1851507, bug 1850799 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** 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: - 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: Fix Released 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: 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 1851550] Re: Eoan update: 5.3.9 upstream stable release
These were skipped since they've already been applied: * arm64: dts: qcom: Add Lenovo Miix 630 * arm64: dts: qcom: Add HP Envy x2 * arm64: dts: qcom: Add Asus NovaGo TP370QL * rtw88: Fix misuse of GENMASK macro * s390/pci: fix MSI message data * thunderbolt: Correct path indices for PCIe tunnel * thunderbolt: Use 32-bit writes when writing ring producer/consumer * ath6kl: fix a NULL-ptr-deref bug in ath6kl_usb_alloc_urb_from_pipe() -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851550 Title: Eoan update: 5.3.9 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.3.9 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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/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-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: Fix Released 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: 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 1851549] Re: Xenial update: 4.4.199 upstream stable release
These patches were skipped as they have already been applied: * ath6kl: fix a NULL-ptr-deref bug in ath6kl_usb_alloc_urb_from_pipe() * rtlwifi: Fix potential overflow on P2P code -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851549 Title: Xenial update: 4.4.199 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.199 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849016] Re: bionic/linux-aws: 4.15.0-1053.55 -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: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 22. October 2019 13:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1849014 bionic/linux-aws/aws-kernel: bug 1849013 xenial/linux-aws-hwe: bug 1849015 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1849016 Title: bionic/linux-aws: 4.15.0-1053.55 -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 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-aws package in Ubuntu: Invalid Status in linux-aws 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-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 22. October 2019 13:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1849014 bionic/linux-aws/aws-kernel: bug 1849013 xenial/linux-aws-hwe: bug 1849015 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849016] Re: bionic/linux-aws: 4.15.0-1053.55 -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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1849016 Title: bionic/linux-aws: 4.15.0-1053.55 -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 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-aws package in Ubuntu: Invalid Status in linux-aws 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-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 22. October 2019 13:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1849014 bionic/linux-aws/aws-kernel: bug 1849013 xenial/linux-aws-hwe: bug 1849015 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Just love the way launchpad mangles pasted code. -- You 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 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
blkid /dev/nvme0n1p1: LABEL="ESP" UUID="B407-D3BC" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="fb8a1f92-fbd6-4ce2-ade4-0a11bdbaf74b" ah, but that UUID is actually fat serial number / volume-id Sets the volume ID of the newly created filesystem; VOLUME-ID is a 32-bit hexadecimal number (for example, 2e24ec82). The default is a number which depends on the filesystem creation time. It would be nice if squashfs had UUID support, and like blkid /dev/loop* printed them, and kernel used them, etc. -- You 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 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
I was thinking of a more generalized overlayfs solution that detects if
file systems don't initialize the superblock uuid and overlayfs
improvises by generating the internal overlayfs uuid, something like:
diff --git a/fs/overlayfs/copy_up.c b/fs/overlayfs/copy_up.c
index 698d112bdb17..da3faaf68d69 100644
--- a/fs/overlayfs/copy_up.c
+++ b/fs/overlayfs/copy_up.c
@@ -248,6 +248,7 @@ struct ovl_fh *ovl_encode_real_fh(struct dentry *real, bool
is_upper)
void *buf;
int buflen = MAX_HANDLE_SZ;
uuid_t *uuid = >d_sb->s_uuid;
+ static const uuid_t z_uuid;
buf = kmalloc(buflen, GFP_KERNEL);
if (!buf)
@@ -289,7 +290,22 @@ struct ovl_fh *ovl_encode_real_fh(struct dentry *real,
bool is_upper)
if (is_upper)
fh->flags |= OVL_FH_FLAG_PATH_UPPER;
fh->len = fh_len;
- fh->uuid = *uuid;
+
+ if (uuid_equal(uuid, _uuid)) {
+ struct super_block *sb = real->d_sb;
+ u16 hash;
+
+ pr_warn("ovl_encode_real_fh: ZERO UUID, generating one from
superblock\n");
+
+ memcpy(>uuid.b[0], >s_magic, 8);
+ memcpy(>uuid.b[8], >s_dev, 6);
+ hash = ((long)sb ^ (long)sb->s_fs_info) >> 12;
+ memcpy(>uuid.b[14], , 2);
+ } else {
+ fh->uuid = *uuid;
+ }
+
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
There is mkfs-time of the filesystem superblock, which could be converted to a timebased UUID. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
I think kernel already generates some faked up UUIDs, i.e. i think there is something for like FAT and DOS partition table, either fs uuid, or like partition table uuid, partition uuid, partition type uuid, some such. They are "shorter" than normal, and less unique, but at least something. Should we request squashfs userspace tooling and kernel to start having a UUID in the squashfs? We do use squashfs a lot, all the snaps and all the installer media. -- You 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 1851549] [NEW] Xenial update: 4.4.199 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.199 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Connor Kuehl (connork) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Xenial) Importance: Critical => Medium ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851549 Title: Xenial update: 4.4.199 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.199 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
