[Kernel-packages] [Bug 1864284] Re: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug
** Changed in: linux-oem (Ubuntu Bionic) Status: In Progress => Fix Committed ** No longer affects: linux-oem (Ubuntu Eoan) ** No longer affects: linux-oem (Ubuntu Focal) ** No longer affects: linux-oem-osp1 (Ubuntu Eoan) ** No longer affects: linux-oem-osp1 (Ubuntu Focal) -- 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/1864284 Title: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-oem source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [SRU Justification] [Impact] USB devices attached to Dell WD19/WD19DC USB Type-C dock take up to nearly one minutes to be ready for use. [Fix] r8152 driver init process involves several for-loops that each may take up to 14 seconds to exit when USB port reset occurs during hotplug. This is still reproducible with latest v5.6-rc mainline kernel although the fail rate is much lower since v5.5-rc7. [Test Case] Verified on Dell WD19DC. [Regression Potential] Low. Just to exit the loop early when it should have been. == original bug description == Dell USB Type C docking WD19/WD19DC attaches additional peripherals as: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M |__ Port 1: Dev 11, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 3: Dev 12, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M where usb 2-1-3 is a hub connecting all USB Type-A/C ports on the dock. When hotplugging such dock with additional usb devices already attached on it, the probing process may reset usb 2.1 port, therefore r8152 ethernet device is also reset. However, in r8152 driver there are several for-loops that may take up to 14 seconds during the initialization for each in practice, and that has to be completed before USB may re-enumerate devices on the bus. As a result, devices attached to the dock will only be available after nearly 1 minute after the dock is plugged in. [ 216.388290] [250] r8152 2-1.4:1.0: usb_probe_interface [ 216.388292] [250] r8152 2-1.4:1.0: usb_probe_interface - got id [ 258.830410] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): PHY not ready [ 258.830460] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): Invalid header when reading pass-thru MAC addr [ 258.830464] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): Get ether addr fail This can be reproduced on all kernel versions up to latest v5.6-rc2, but after v5.5-rc7 the reproduce rate is dramatically lower to 1/30 or so while it was around 1/2. The time consuming for-loops are at: https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L3206 https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L5400 https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L5537 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-1037-oem-osp1 5.0.0-1037.42 ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21 Uname: Linux 5.0.0-1037-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 2014 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Feb 22 04:07:20 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-hodor+X95 InstallationDate: Installed on 2020-01-16 (37 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 IwConfig: enp1s0no wireless extensions. enxd8d090035306 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Latitude 3310 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 root=UUID=1ad036ce-aa29-4d5e-8692-d980d1a7140f ro "dyndbg=file drivers/usb/* +pt" log_buf_len=32M ignore_loglevel usbcore.quirks=0bda:0487:k RelatedPackageVersions: linux-restricted-modules-5.0.0-1037-oem-osp1 N/A linux-backports-modules-5.0.0-1037-oem-osp1 N/A linux-firmware
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
Just got this triggered with 5.4.0-15-generic #18-Ubuntu from focal-
proposed.
Logs below.
If you want me to run another kernel, or try patched kernels, I can do
that.
Kernel log:
8<
Feb 25 10:08:08 vesho kernel: i915 :00:02.0: GPU HANG: ecode
9:1:0x, hang on rcs0
Feb 25 10:08:08 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 25 10:08:08 vesho kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Feb 25 10:08:08 vesho kernel: i915 :00:02.0: Resetting chip for hang on rcs0
Feb 25 10:08:08 vesho kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Feb 25 10:08:08 vesho kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Feb 25 10:08:16 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 25 10:08:24 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 25 10:08:26 vesho kernel: GpuWatchdog[15034]: segfault at 0 ip
55af78399e32 sp 7f8b359414c0 error 6 in chrome[55af74453000+7287000]
Feb 25 10:08:26 vesho kernel: Code: 83 c3 e8 75 e9 41 8b 85 00 01 00 00 85 c0
0f 84 99 00 00 00 48 8d 3d 63 61 4b fb be 01 00 00 00 ba 03 00 00 00 e8 fe 17
a6 fe 04 25 00>
Feb 25 10:08:28 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
Feb 25 10:09:18 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 25 10:09:20 vesho kernel: i915 :00:02.0: GPU recovery timed out,
cancelling all in-flight rendering.
Feb 25 10:09:20 vesho kernel: i915 :00:02.0: Resetting chip for hang on rcs0
Feb 25 10:09:22 vesho kernel: i915 :00:02.0: GPU recovery timed out,
cancelling all in-flight rendering.
Feb 25 10:09:22 vesho kernel: i915 :00:02.0: Resetting chip for hang on rcs0
Feb 25 10:09:22 vesho kernel: fbcon: Taking over console
Feb 25 10:09:23 vesho kernel: Console: switching to colour frame buffer device
240x67
Feb 25 10:09:30 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 25 10:09:38 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
Feb 25 10:10:32 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 25 10:10:34 vesho kernel: i915 :00:02.0: GPU recovery timed out,
cancelling all in-flight rendering.
Feb 25 10:10:34 vesho kernel: i915 :00:02.0: Resetting chip for hang on rcs0
Feb 25 10:10:36 vesho kernel: i915 :00:02.0: GPU recovery timed out,
cancelling all in-flight rendering.
Feb 25 10:10:36 vesho kernel: i915 :00:02.0: Resetting chip for hang on rcs0
Feb 25 10:10:46 vesho kernel: GpuWatchdog[53827]: segfault at 0 ip
55f286b35e32 sp 7f396a9a24c0 error 6 in chrome[55f282bef000+7287000]
Feb 25 10:10:46 vesho kernel: Code: 83 c3 e8 75 e9 41 8b 85 00 01 00 00 85 c0
0f 84 99 00 00 00 48 8d 3d 63 61 4b fb be 01 00 00 00 ba 03 00 00 00 e8 fe 17
a6 fe 04 25 00>
Feb 25 10:10:56 vesho kernel: GpuWatchdog[53920]: segfault at 0 ip
555c042dee32 sp 7f446a7b24c0 error 6 in chrome[555c00398000+7287000]
Feb 25 10:10:56 vesho kernel: Code: 83 c3 e8 75 e9 41 8b 85 00 01 00 00 85 c0
0f 84 99 00 00 00 48 8d 3d 63 61 4b fb be 01 00 00 00 ba 03 00 00 00 e8 fe 17
a6 fe 04 25 00>
8<
/sys/class/drm/card0/error:
8<
GPU HANG: ecode 9:1:0x, hang on rcs0
Kernel: 5.4.0-15-generic x86_64
Driver: 20190822
Time: 1582618088 s 331762 us
Boottime: 57363 s 47980 us
Uptime: 834 s 211397 us
Epoch: 4297439752 jiffies (250 HZ)
Capture: 4297439752 jiffies; 8224 ms ago, 0 ms after epoch
Reset count: 0
Suspend count: 1
Platform: KABYLAKE
Subplatform: 0x0
PCI ID: 0x591b
PCI Revision: 0x04
PCI Subsystem: 1028:07bf
IOMMU enabled?: 1
DMC loaded: yes
DMC fw version: 1.4
GT awake: yes
RPM wakelock: yes
PM suspended: no
EIR: 0x
IER: 0x0808
GTIER[0]: 0x01010101
GTIER[1]: 0x01010101
GTIER[2]: 0x0070
GTIER[3]: 0x0101
PGTBL_ER: 0x
FORCEWAKE: 0x00010001
DERRMR: 0x2077efef
CCID: 0x
fence[0] =
fence[1] =
fence[2] =
fence[3] =
fence[4] =
fence[5] = a43f097074c0001
fence[6] =
fence[7] =
fence[8] =
fence[9] =
fence[10] =
fence[11] =
fence[12] =
fence[13] =
fence[14] =
fence[15] =
fence[16] =
fence[17] =
fence[18] =
fence[19] =
fence[20] =
fence[21] =
fence[22] =
fence[23] =
fence[24] =
fence[25] =
fence[26] =
fence[27] =
fence[28] =
fence[29] =
fence[30] =
fence[31] =
ERROR: 0x
DONE_REG: 0x
FAULT_TLB_DATA: 0x0019 0xf4bbf313
Num Pipes: 3
Pipe [0]:
Power: on
SRC: 077f0437
STAT:
Plane [0]:
CNTR: c4042400
STRIDE: 0026
SURF:
[Kernel-packages] [Bug 1864576] Re: alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon
** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oem (Ubuntu) ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Disco) Importance: Undecided Status: New ** No longer affects: linux-oem (Ubuntu Disco) ** No longer affects: linux (Ubuntu Disco) ** No longer affects: linux (Ubuntu Bionic) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Bionic) 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/1864576 Title: alsa/hda/realtek: fix a mute led regression on Lenovo X1 Carbon Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Eoan: New Status in linux source package in Focal: Incomplete Bug description: [Impact] The mute led couldn't work after applying the FIXUP_SPEAKER2_TO_DAC1. [Fix] Chain a fixup to let mute led work. [Test Case] boot the system, press mute button, the led will work. [Regression Risk] Low, this patch is specific to LENOVO X1 Carbon machines. And I tested this patch on Lenovo and Dell machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862588] Re: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels
Issue found on B-5.3 as well (5.3.0-41.33~18.04.1, node rizzo) -- 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/1862588 Title: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels Status in ubuntu-kernel-tests: Triaged Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-signed-oracle-5.0 package in Ubuntu: New Status in linux-aws source package in Bionic: New Status in linux-gcp source package in Bionic: New Status in linux-signed-oracle-5.0 source package in Bionic: New Bug description: Issue found on Oracle Bionic 5.0 (oracle : 5.0.0-1011.16 : amd64) [ RUN ] global.user_notification_basic seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 (18446744073709551615) == ret (0) seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == errno (0) global.user_notification_basic: Test failed at step #3 [ FAIL ] global.user_notification_basic This cannot be reproduced with the kselftest in older kernel, probably a test case issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-1011-oracle 5.0.0-1011.16 ProcVersionSignature: User Name 5.0.0-1011.16-oracle 5.0.21 Uname: Linux 5.0.0-1011-oracle x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Mon Feb 10 05:17:54 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oracle-5.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 kernel
Didn't see this issue with AWS-B-5.0 (5.0.0-1026.29-aws) and 5.3.0-41.33-generic on node rizzo. Found this failing with 5.3.0-1012.13~18.04.1-aws test failed with: # selftests: net: ip_defrag.sh not ok 18 selftests: net: ip_defrag.sh # exit=255 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826848 Title: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 kernel Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Status in linux source package in Eoan: Confirmed Bug description: Test failed becuase: ./ip_defrag: sendto overlap: 1400: Operation not permitted selftests: net: ip_defrag.sh ipv6 tx:17 gso:1 (fail) OK ipv4 defrag PASS seed = 1556203721 ipv4 defrag with overlaps PASS seed = 1556203722 ipv6 defrag seed = 1556203756 PASS ipv6 defrag with overlaps seed = 1556203756 ./ip_defrag: sendto overlap: 1400: Operation not permitted not ok 1..17 selftests: net: ip_defrag.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 kernel
Didn't see this issue with B-5.3 (5.3.0-41.33~18.04.1), node rizzo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826848 Title: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 kernel Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Status in linux source package in Eoan: Confirmed Bug description: Test failed becuase: ./ip_defrag: sendto overlap: 1400: Operation not permitted selftests: net: ip_defrag.sh ipv6 tx:17 gso:1 (fail) OK ipv4 defrag PASS seed = 1556203721 ipv4 defrag with overlaps PASS seed = 1556203722 ipv6 defrag seed = 1556203756 PASS ipv6 defrag with overlaps seed = 1556203756 ./ip_defrag: sendto overlap: 1400: Operation not permitted not ok 1..17 selftests: net: ip_defrag.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861238] Re: Root can lift kernel lockdown via USB/IP
** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oem (Ubuntu Xenial) ** No longer affects: linux-oem (Ubuntu Disco) ** No longer affects: linux-oem (Ubuntu Eoan) ** No longer affects: linux-oem (Ubuntu Focal) ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Fix Committed -- 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/1861238 Title: Root can lift kernel lockdown via USB/IP Status in linux package in Ubuntu: In Progress Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem 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: [Impact] It's possible to turn off kernel lockdown by emulating a USB keyboard via USB/IP and sending an Alt+SysRq+X key combination through it. Ubuntu's kernels have USB/IP enabled (CONFIG_USBIP_VHCI_HCD=m and CONFIG_USBIP_CORE=m) with signed usbip_core and vhci_hcd modules provided in the linux-extra-modules-* package. See the PoC here: https://github.com/xairy/unlockdown#method-1-usbip [Test Case] $ git clone https://github.com/xairy/unlockdown.git $ cd unlockdown/01-usbip/ $ sudo ./run.sh $ dmesg # Ensure there are no log entries talking about lifting lockdown: sysrq: SysRq : Disabling Secure Boot restrictions Lifting lockdown # You should see a SysRq help log entry because the Alt+SysRq+X # combination should be disabled sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(V) show-blocked-tasks(w) dump-ftrace-buffer(z) [Regression Potential] Some users may see a usability regression due to the Lockdown lift sysrq combination being removed. Some users are known to disable lockdown, using the sysrq combination, in order to perform some "dangerous" operation such as writing to an MSR. It is believed that this is a small number of users but it is impossible to know for sure. Users that rely on this functionality may need to permanently disable secure boot using 'mokutil --disable-validation'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863312] Re: bionic/linux-oem: 4.15.0-1074.84 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863350 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem - phase: Ready for Packaging - phase-changed: Saturday, 15. February 2020 04:08 UTC + phase: Packaging + phase-changed: Tuesday, 25. February 2020 09:00 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-lrm: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded variant: debs -- 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/1863312 Title: bionic/linux-oem: 4.15.0-1074.84 -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: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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 -- kernel-stable-master-bug: 1863350 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Packaging phase-changed: Tuesday, 25. February 2020 09:00 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
So far, I couldn't set up the ipv6 on my rpi3B+ board, I need to do more study. And I checked the eoan-proposed, the 1019 kernel is already there. If there is no this file in the folder /etc/apt/sources.list.d/ on your board, you could put this file to that folder and run sudo apt-get update Then you could install 1019 kernel to do the test. sudo apt install linux-image-(press tab), it will list 1019 kernel. ** Attachment added: "proposed.list" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5330815/+files/proposed.list -- 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/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) Status in linux-raspi2 package in Ubuntu: Incomplete Bug description: Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and network load. Happened a few times (every time) when I tried to download a gparted zip release (~350 MiB) directly to the SD card, and then finally when I tried to scp the finished download from a desktop onto RPi's card. Didn't collect information when it happened, but kept a copy of kern.log. Here's the relevant part: Feb 4 23:42:59 rpi3 kernel: [ 571.878359] [ cut here ] Feb 4 23:42:59 rpi3 kernel: [ 571.878420] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Feb 4 23:42:59 rpi3 kernel: [ 571.878550] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878557] Modules linked in: sit tunnel4 ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 Feb 4 23:42:59 rpi3 kernel: [ 571.878774] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu Feb 4 23:42:59 rpi3 kernel: [ 571.878781] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) Feb 4 23:42:59 rpi3 kernel: [ 571.878789] pstate: 6045 (nZCv daif +PAN -UAO) Feb 4 23:42:59 rpi3 kernel: [ 571.878800] pc : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878807] lr : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878812] sp : 1001bd60 Feb 4 23:42:59 rpi3 kernel: [ 571.878817] x29: 1001bd60 x28: 0140 Feb 4 23:42:59 rpi3 kernel: [ 571.878827] x27: x26: Feb 4 23:42:59 rpi3 kernel: [ 571.878836] x25: 8ecbefa4e000 x24: 305e0f529018 Feb 4 23:42:59 rpi3 kernel: [ 571.878845] x23: x22: 0001 Feb 4 23:42:59 rpi3 kernel: [ 571.878853] x21: 8ecbefa4e480 x20: 305e0f807000 Feb 4 23:42:59 rpi3 kernel: [ 571.878862] x19: x18: Feb 4 23:42:59 rpi3 kernel: [ 571.878871] x17: 10fd8218 x16: 305e0e30efb8 Feb 4 23:42:59 rpi3 kernel: [ 571.878879] x15: 8ecbf922a290 x14: Feb 4 23:42:59 rpi3 kernel: [ 571.87] x13: x12: 305e0f944000 Feb 4 23:42:59 rpi3 kernel: [ 571.878897] x11: 305e0f82d000 x10: Feb 4 23:42:59 rpi3 kernel: [ 571.878905] x9 : 0004 x8 : 017f Feb 4 23:42:59 rpi3 kernel: [ 571.878913] x7 : x6 : 0001 Feb 4 23:42:59 rpi3 kernel: [ 571.878921] x5 : x4 : 0008 Feb 4 23:42:59 rpi3 kernel: [ 571.878929] x3 : 305e0ee15750 x2 : 0004 Feb 4 23:42:59 rpi3 kernel: [ 571.878937] x1 : 6abb42c67c954600 x0 : Feb 4 23:42:59 rpi3 kernel: [ 571.878946] Call trace: Feb 4 23:42:59 rpi3 kernel: [ 571.878955] dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878967] call_timer_fn+0x3c/0x178 Feb 4 23:42:59 rpi3 kernel: [ 571.878977] __run_timers.part.0+0x200/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878985] run_timer_softirq+0x40/0x78 Feb 4 23:42:59 rpi3 kernel: [ 571.878995] __do_softirq+0x168/0x384 Feb 4 23:42:59 rpi3 kernel: [ 571.879007] irq_exit+0xb0/0xe8 Feb 4 23:42:59 rpi3 kernel: [ 57
[Kernel-packages] [Bug 1864084] Re: focal/linux-oracle: 5.4.0-1003.3 -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: 1864085 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Ready for Promote to Proposed phase-changed: Monday, 24. February 2020 13:06 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review 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/1864084 Title: focal/linux-oracle: 5.4.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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: Confirmed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle source package in Focal: 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: 1864085 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Ready for Promote to Proposed phase-changed: Monday, 24. February 2020 13:06 UTC reason: promote-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B
I confirm in my testing I get a hard kernel lockup with no log output. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864063 Title: vm-segv from ubuntu_stress_smoke_test failed on B Status in Stress-ng: Incomplete Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Bug description: Issue found on node onibi, with kernel 4.15.0-89.89/ 4.15.0-89.89~16.04.1 Reproduce rate: 2/2 on generic kernel, 2/2 on lowlatency kernel, 2/2 on X-hwe generic kernel Test hang with vm-segv: 05:58:36 DEBUG| [stdout] vm-addr PASSED 05:58:36 DEBUG| [stdout] vm-rw STARTING 05:58:41 DEBUG| [stdout] vm-rw RETURNED 0 05:58:41 DEBUG| [stdout] vm-rw PASSED 05:58:41 DEBUG| [stdout] vm-segv STARTING + ARCHIVE=/var/lib/jenkins/jobs/smoke__B_amd64-generic__using_onibi__for_kernel/builds/2/archive + scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -r ubuntu@onibi:kernel-test-results /var/lib/jenkins/jobs/smoke__B_amd64-generic__using_onibi__for_kernel/builds/2/archive To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1864063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864063 Title: vm-segv from ubuntu_stress_smoke_test failed on B Status in Stress-ng: Incomplete Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Bug description: Issue found on node onibi, with kernel 4.15.0-89.89/ 4.15.0-89.89~16.04.1 Reproduce rate: 2/2 on generic kernel, 2/2 on lowlatency kernel, 2/2 on X-hwe generic kernel Test hang with vm-segv: 05:58:36 DEBUG| [stdout] vm-addr PASSED 05:58:36 DEBUG| [stdout] vm-rw STARTING 05:58:41 DEBUG| [stdout] vm-rw RETURNED 0 05:58:41 DEBUG| [stdout] vm-rw PASSED 05:58:41 DEBUG| [stdout] vm-segv STARTING + ARCHIVE=/var/lib/jenkins/jobs/smoke__B_amd64-generic__using_onibi__for_kernel/builds/2/archive + scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -r ubuntu@onibi:kernel-test-results /var/lib/jenkins/jobs/smoke__B_amd64-generic__using_onibi__for_kernel/builds/2/archive To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1864063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864081] Re: focal/linux-azure: 5.4.0-1003.3 -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: 1864085 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Monday, 24. February 2020 12:53 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review 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/1864081 Title: focal/linux-azure: 5.4.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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: Confirmed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Focal: 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: 1864085 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Monday, 24. February 2020 12:53 UTC reason: promote-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864083] Re: focal/linux-kvm: 5.4.0-1002.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: 1864085 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Promote to Proposed phase-changed: Monday, 24. February 2020 12:54 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review 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/1864083 Title: focal/linux-kvm: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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: Confirmed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Focal: 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: 1864085 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Promote to Proposed phase-changed: Monday, 24. February 2020 12:54 UTC reason: promote-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864080] Re: focal/linux-aws: 5.4.0-1002.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: 1864085 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Ready for Promote to Proposed phase-changed: Monday, 24. February 2020 12:53 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review 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/1864080 Title: focal/linux-aws: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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: Confirmed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Focal: 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: 1864085 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Ready for Promote to Proposed phase-changed: Monday, 24. February 2020 12:53 UTC reason: promote-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864078] Re: focal/linux-raspi2: 5.4.0-1003.3 -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: 1864085 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Ready for Promote to Proposed phase-changed: Monday, 24. February 2020 12:52 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review trackers: focal/linux-raspi2/pi-kernel: bug 1864502 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/1864078 Title: focal/linux-raspi2: 5.4.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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: Confirmed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Focal: 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: 1864085 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Ready for Promote to Proposed phase-changed: Monday, 24. February 2020 12:52 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: focal/linux-raspi2/pi-kernel: bug 1864502 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860969] Re: ipsec interfaces: fix sending with bpf_redirect() / AF_PACKET sockets
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860969
Title:
ipsec interfaces: fix sending with bpf_redirect() / AF_PACKET sockets
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
New
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
Packets sent to a vti[6]/xfrm interface via bpf_redirect() or via an
AF_PACKET socket are dropped (no carrier).
This has been fixed in v5.5 by the following upstream commits
- 95224166a903 ("vti[6]: fix packet tx through bpf_redirect()")
- f042365dbffe ("xfrm interface: fix packet tx through bpf_redirect()")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=95224166a903
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f042365dbffe
The bug exists since the beginning of each driver.
== Fix ==
Backport the requested patches to Focal (5.4), Eoan (5.3), Bionic (4.15) and
Xenial (4.4).
== Risk of Regression ==
This patch affects only the cases described above (when no dst is
attached to the skb), thus the risk should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863337] Re: xenial/linux-oracle: 4.15.0-1034.37~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: 1863339 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Monday, 24. February 2020 21:32 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + 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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1863337 Title: xenial/linux-oracle: 4.15.0-1034.37~16.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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-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: 1863339 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Monday, 24. February 2020 21:32 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/1863337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863339] Re: bionic/linux-oracle: 4.15.0-1034.37 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** 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: 1863350 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Promote to Proposed - phase-changed: Monday, 24. February 2020 21:20 UTC + phase: Testing + phase-changed: Tuesday, 25. February 2020 09:00 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1863337 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/1863339 Title: bionic/linux-oracle: 4.15.0-1034.37 -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: 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: Confirmed 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: 1863350 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Tuesday, 25. February 2020 09:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1863337 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
No I have a laptop from a XMG, it is a German brand. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=0ca062da-7e8f-425a-88b
[Kernel-packages] [Bug 1864303] Re: Removing the e1000e module causes a crash
Since this also affect upstream stable, I asked stable maintainers to pull the fix: https://lkml.org/lkml/2020/2/25/262 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864303 Title: Removing the e1000e module causes a crash Status in linux package in Ubuntu: In Progress Bug description: I have a Lenovo x1 Carbon Gen5 and when it initially came out if you left the onboard NIC (e1000e) module loaded it would suck CPU/battery life so I have it removed in rc.local on boot. In 5.4 (also happens on 5.4.0.15.18 which I'm running from proposed right now), this is what happens when the module is unloaded: [ 608.979789] e1000e :00:1f.6 enp0s31f6: removed PHC [ 609.008352] [ cut here ] [ 609.008353] kernel BUG at drivers/pci/msi.c:375! [ 609.008358] invalid opcode: [#1] SMP PTI [ 609.008359] CPU: 0 PID: 6829 Comm: rmmod Tainted: P O 5.4.0-15-generic #18-Ubuntu [ 609.008360] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET59W (1.44 ) 11/25/2019 [ 609.008364] RIP: 0010:free_msi_irqs+0x17d/0x1b0 [ 609.008365] Code: 84 df fe ff ff 45 31 f6 eb 11 41 83 c6 01 44 39 73 14 0f 86 cc fe ff ff 8b 7b 10 44 01 f7 e8 ea c3 b6 ff 48 83 78 70 00 74 e0 <0f> 0b 49 8d b5 b0 00 00 00 e8 b5 7d b7 ff e9 cd fe ff ff 49 8b 78 [ 609.008366] RSP: 0018:a7d2072f7d40 EFLAGS: 00010286 [ 609.008367] RAX: 8bc9bfb49e00 RBX: 8bc9ad69c720 RCX: [ 609.008368] RDX: RSI: 0084 RDI: a9e65980 [ 609.008369] RBP: a7d2072f7d70 R08: 8bc9bb564db0 R09: 8bc9bb564df8 [ 609.008369] R10: R11: a9e65988 R12: 8bc9cb5272c0 [ 609.008370] R13: 8bc9cb527000 R14: R15: dead0100 [ 609.008371] FS: 7f188f1f9500() GS:8bc9ce20() knlGS: [ 609.008372] CS: 0010 DS: ES: CR0: 80050033 [ 609.008373] CR2: 7f6d1a6af060 CR3: 00046d9f8006 CR4: 003606f0 [ 609.008373] Call Trace: [ 609.008376] pci_disable_msi+0x100/0x130 [ 609.008385] e1000e_reset_interrupt_capability+0x52/0x60 [e1000e] [ 609.008389] e1000_remove+0xc4/0x180 [e1000e] [ 609.008391] pci_device_remove+0x3e/0xb0 [ 609.008394] device_release_driver_internal+0xf0/0x1d0 [ 609.008396] driver_detach+0x4c/0x8f [ 609.008397] bus_remove_driver+0x5c/0xd0 [ 609.008399] driver_unregister+0x31/0x50 [ 609.008400] pci_unregister_driver+0x40/0x90 [ 609.008405] e1000_exit_module+0x10/0x3c1 [e1000e] [ 609.008407] __x64_sys_delete_module+0x147/0x2b0 [ 609.008409] ? exit_to_usermode_loop+0xea/0x160 [ 609.008411] do_syscall_64+0x57/0x190 [ 609.008413] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 609.008414] RIP: 0033:0x7f188f345c9b [ 609.008416] Code: 73 01 c3 48 8b 0d f5 71 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 b0 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c5 71 0c 00 f7 d8 64 89 01 48 [ 609.008416] RSP: 002b:7fffc8d32e68 EFLAGS: 0206 ORIG_RAX: 00b0 [ 609.008418] RAX: ffda RBX: 561e1a391790 RCX: 7f188f345c9b [ 609.008419] RDX: 000a RSI: 0800 RDI: 561e1a3917f8 [ 609.008420] RBP: 7fffc8d32ec8 R08: R09: [ 609.008420] R10: 7f188f3c1ac0 R11: 0206 R12: 7fffc8d33090 [ 609.008422] R13: 7fffc8d3474a R14: 561e1a3912a0 R15: 561e1a391790 [ 609.008424] Modules linked in: thunderbolt rfcomm xfrm_user xfrm_algo l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ccm xt_comment xt_CHECKSUM xt_MASQUERADE ip6table_mangle ip6table_nat dummy iptable_mangle iptable_nat nf_tables nfnetlink bridge stp llc cmac algif_hash algif_skcipher af_alg bnep zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) joydev intel_rapl_msr mei_hdcp nls_iso8859_1 snd_seq_midi snd_seq_midi_event snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_intel snd_rawmidi kvm snd_intel_nhlt snd_hda_codec intel_cstate rmi_smbus intel_rapl_perf snd_hda_core snd_hwdep iwlmvm rmi_core mac80211 uvcvideo input_leds videobuf2_vmalloc videobuf2_memops btusb btrtl snd_pcm libarc4 serio_raw snd_seq btbcm intel_wmi_thunderbolt videobuf2_v4l2 btintel videobuf2_common wmi_bmof thinkpad_acpi bluetooth videodev nvram snd_seq_device ledtrig_audio [ 609.008447] iwlwifi mc snd_timer rtsx_pci_ms ecdh_generic ecc cfg80211 memstick snd mei_me ucsi_acpi typec_ucsi intel_xhci_usb_role_switch mei roles intel_pch_thermal typec soundcore acpi_pad mac_hid nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reje
[Kernel-packages] [Bug 1863343] Re: trusty/linux-azure: 4.15.0-1072.77~14.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: 1863344 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 24. February 2020 11:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863343 Title: trusty/linux-azure: 4.15.0-1072.77~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released 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: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed 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 Trusty: 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: 1863344 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 24. February 2020 11:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863312] Re: bionic/linux-oem: 4.15.0-1074.84 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863350 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem - phase: Packaging - phase-changed: Tuesday, 25. February 2020 09:00 UTC - reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + phase: Holding before Promote to Proposed + phase-changed: Tuesday, 25. February 2020 09:52 UTC variant: debs -- 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/1863312 Title: bionic/linux-oem: 4.15.0-1074.84 -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: New 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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 -- kernel-stable-master-bug: 1863350 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Tuesday, 25. February 2020 09:52 UTC variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864626] [NEW] nsleep-lat / set-timer-lat / inconsistency-check / raw_skew from timer in ubuntu_kernel_selftests timeout on B-5.3
You have been subscribed to a public bug: Test failed because of timeout: # selftests: timers: nsleep-lat # nsleep latency CLOCK_REALTIME [OK] # nsleep latency CLOCK_MONOTONIC[OK] # nsleep latency CLOCK_MONOTONIC_RAW[UNSUPPORTED] # nsleep latency CLOCK_REALTIME_COARSE [UNSUPPORTED] # nsleep latency CLOCK_MONOTONIC_COARSE [UNSUPPORTED] # nsleep latency CLOCK_BOOTTIME # not ok 3 selftests: timers: nsleep-lat # TIMEOUT # selftests: timers: set-timer-lat # not ok 4 selftests: timers: set-timer-lat # TIMEOUT # selftests: timers: inconsistency-check # Consistent CLOCK_REALTIME [OK] # Consistent CLOCK_MONOTONIC[OK] # Consistent CLOCK_PROCESS_CPUTIME_ID [OK] # Consistent CLOCK_THREAD_CPUTIME_ID[OK] # Consistent CLOCK_MONOTONIC_RAW# not ok 6 selftests: timers: inconsistency-check # TIMEOUT # selftests: timers: raw_skew # WARNING: ADJ_OFFSET in progress, this will cause inaccurate results # Estimating clock drift: # not ok 7 selftests: timers: raw_skew # TIMEOUT ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-40-generic 5.3.0-40.32~18.04.1 ProcVersionSignature: User Name 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 Date: Tue Feb 25 09:10:45 2020 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Assignee: Po-Hsu Lin (cypressyew) Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 5.3 amd64 apport-bug bionic sru-20200217 ubuntu-kernel-selftests uec-images -- nsleep-lat / set-timer-lat / inconsistency-check / raw_skew from timer in ubuntu_kernel_selftests timeout on B-5.3 https://bugs.launchpad.net/bugs/1864626 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863337] Re: xenial/linux-oracle: 4.15.0-1034.37~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** 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: 1863339 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Promote to Proposed - phase-changed: Monday, 24. February 2020 21:32 UTC + phase: Testing + phase-changed: Tuesday, 25. February 2020 10:16 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1863337 Title: xenial/linux-oracle: 4.15.0-1034.37~16.04.1 -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: 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: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed 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: 1863339 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Tuesday, 25. February 2020 10:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864626] Re: nsleep-lat / set-timer-lat / inconsistency-check / raw_skew from timer in ubuntu_kernel_selftests timeout on B-5.3
These tests can pass with timeout disabled in kselftest. Patch sent to upstream. https://lists.linaro.org/pipermail/linux-kselftest-mirror/2020-February/011036.html ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Package changed: linux-signed-hwe (Ubuntu) => linux (Ubuntu) ** Summary changed: - nsleep-lat / set-timer-lat / inconsistency-check / raw_skew from timer in ubuntu_kernel_selftests timeout on B-5.3 + nsleep-lat / set-timer-lat / inconsistency-check / raw_skew from timer in ubuntu_kernel_selftests timeout on 5.3 ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Summary changed: - nsleep-lat / set-timer-lat / inconsistency-check / raw_skew from timer in ubuntu_kernel_selftests timeout on 5.3 + nsleep-lat / set-timer-lat / inconsistency-check / raw_skew from timer in ubuntu_kernel_selftests timeout on 5.3 / 5.4 ** Tags added: 5.4 eoan focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864626 Title: nsleep-lat / set-timer-lat / inconsistency-check / raw_skew from timer in ubuntu_kernel_selftests timeout on 5.3 / 5.4 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: Test failed because of timeout: # selftests: timers: nsleep-lat # nsleep latency CLOCK_REALTIME [OK] # nsleep latency CLOCK_MONOTONIC[OK] # nsleep latency CLOCK_MONOTONIC_RAW[UNSUPPORTED] # nsleep latency CLOCK_REALTIME_COARSE [UNSUPPORTED] # nsleep latency CLOCK_MONOTONIC_COARSE [UNSUPPORTED] # nsleep latency CLOCK_BOOTTIME # not ok 3 selftests: timers: nsleep-lat # TIMEOUT # selftests: timers: set-timer-lat # not ok 4 selftests: timers: set-timer-lat # TIMEOUT # selftests: timers: inconsistency-check # Consistent CLOCK_REALTIME [OK] # Consistent CLOCK_MONOTONIC[OK] # Consistent CLOCK_PROCESS_CPUTIME_ID [OK] # Consistent CLOCK_THREAD_CPUTIME_ID[OK] # Consistent CLOCK_MONOTONIC_RAW# not ok 6 selftests: timers: inconsistency-check # TIMEOUT # selftests: timers: raw_skew # WARNING: ADJ_OFFSET in progress, this will cause inaccurate results # Estimating clock drift: # not ok 7 selftests: timers: raw_skew # TIMEOUT ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-40-generic 5.3.0-40.32~18.04.1 ProcVersionSignature: User Name 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 Date: Tue Feb 25 09:10:45 2020 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864626] 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 1864626 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Eoan) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864626 Title: nsleep-lat / set-timer-lat / inconsistency-check / raw_skew from timer in ubuntu_kernel_selftests timeout on 5.3 / 5.4 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: Test failed because of timeout: # selftests: timers: nsleep-lat # nsleep latency CLOCK_REALTIME [OK] # nsleep latency CLOCK_MONOTONIC[OK] # nsleep latency CLOCK_MONOTONIC_RAW[UNSUPPORTED] # nsleep latency CLOCK_REALTIME_COARSE [UNSUPPORTED] # nsleep latency CLOCK_MONOTONIC_COARSE [UNSUPPORTED] # nsleep latency CLOCK_BOOTTIME # not ok 3 selftests: timers: nsleep-lat # TIMEOUT # selftests: timers: set-timer-lat # not ok 4 selftests: timers: set-timer-lat # TIMEOUT # selftests: timers: inconsistency-check # Consistent CLOCK_REALTIME [OK] # Consistent CLOCK_MONOTONIC[OK] # Consistent CLOCK_PROCESS_CPUTIME_ID [OK] # Consistent CLOCK_THREAD_CPUTIME_ID[OK] # Consistent CLOCK_MONOTONIC_RAW# not ok 6 selftests: timers: inconsistency-check # TIMEOUT # selftests: timers: raw_skew # WARNING: ADJ_OFFSET in progress, this will cause inaccurate results # Estimating clock drift: # not ok 7 selftests: timers: raw_skew # TIMEOUT ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-40-generic 5.3.0-40.32~18.04.1 ProcVersionSignature: User Name 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 Date: Tue Feb 25 09:10:45 2020 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864633] [NEW] suspend/resume failure, fan making noise and nvidia-sim not working
Public bug reported: suspend/resume failure, pc fan is making noise on startup and Nvidia-sim command is not working ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-175-generic 4.4.0-175.205 ProcVersionSignature: Ubuntu 4.4.0-175.205-generic 4.4.211 Uname: Linux 4.4.0-175-generic x86_64 Annotation: This occurred during a previous suspend, and prevented the system from resuming properly. ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Tue Feb 25 11:28:24 2020 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2017-02-09 (1110 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InterpreterPath: /usr/bin/python3.5 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: linux-signed Title: suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops package-from-proposed resume suspend xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1864633 Title: suspend/resume failure, fan making noise and nvidia-sim not working Status in linux-signed package in Ubuntu: New Bug description: suspend/resume failure, pc fan is making noise on startup and Nvidia- sim command is not working ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-175-generic 4.4.0-175.205 ProcVersionSignature: Ubuntu 4.4.0-175.205-generic 4.4.211 Uname: Linux 4.4.0-175-generic x86_64 Annotation: This occurred during a previous suspend, and prevented the system from resuming properly. ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Tue Feb 25 11:28:24 2020 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2017-02-09 (1110 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InterpreterPath: /usr/bin/python3.5 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: linux-signed Title: suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1864633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812638] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails
On B-5.3 P8, test result is a bit different: # selftests: net: reuseport_bpf_numa # IPv4 UDP # send node 0, receive socket 0 # send node 1, receive socket 1 # libnuma: Warning: Cannot read node cpumask from sysfs # ./reuseport_bpf_numa: failed to pin to node: No such file or directory not ok 3 selftests: net: reuseport_bpf_numa # exit=1 ** Tags added: 2020 ** Tags removed: 2020 ** Tags added: sru-20200217 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812638 Title: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: Test failed with: $ sudo ./reuseport_bpf_numa ./reuseport_bpf_numa: no numa api support: Function not implemented Maybe this one should be skipped. selftests: reuseport_bpf_numa not ok 1..3 selftests: reuseport_bpf_numa [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 21 10:52 seq crw-rw 1 root audio 116, 33 Jan 21 10:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 21 11:06:26 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=6aaa11f6-d386-4c0c-b4b8-38e6c408980a ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd09/18/2012:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863989] Re: bad-altstack test from ubuntu_stress_smoke_test failed on Eoan zVM
@Colin, I have your keys imported, if you need please feel free to access this instance with ubuntu@kernel03 Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863989 Title: bad-altstack test from ubuntu_stress_smoke_test failed on Eoan zVM Status in Stress-ng: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Eoan zVM node kernel03 Test hung at bad-altstack test. Reproducible rate: 4 out of 4 attempts 02:36:12 DEBUG| [stdout] aiol STARTING 02:36:17 DEBUG| [stdout] aiol RETURNED 0 02:36:17 DEBUG| [stdout] aiol PASSED 02:36:17 DEBUG| [stdout] bad-altstack STARTING + ARCHIVE=/var/lib/jenkins/jobs/smoke__E_s390x.zVM-generic__using_kernel03__for_kernel/builds/3/archive + scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -r ubuntu@kernel03:kernel-test-results /var/lib/jenkins/jobs/smoke__E_s390x.zVM-generic__using_kernel03__for_kernel/builds/3/archive dmesg only shows: [ 102.352136] Adding 1048572k swap on /home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng/swap.img. Priority:-3 extents:95 across:26763272k SSFS [ 122.402895] NET: Registered protocol family 38 It looks like this is caused by OOM issue, x3270 console flushed with OOM error messages. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-41-generic 5.3.0-41.33 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.4 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Feb 20 06:06:04 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/mapper/kl03vg01-kl03root crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-5.3.0-41-generic N/A linux-backports-modules-5.3.0-41-generic N/A linux-firmware1.183.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-30 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1863989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864063 Title: vm-segv from ubuntu_stress_smoke_test failed on B Status in Stress-ng: Incomplete Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: Issue found on node onibi, with kernel 4.15.0-89.89/ 4.15.0-89.89~16.04.1 Reproduce rate: 2/2 on generic kernel, 2/2 on lowlatency kernel, 2/2 on X-hwe generic kernel Test hang with vm-segv: 05:58:36 DEBUG| [stdout] vm-addr PASSED 05:58:36 DEBUG| [stdout] vm-rw STARTING 05:58:41 DEBUG| [stdout] vm-rw RETURNED 0 05:58:41 DEBUG| [stdout] vm-rw PASSED 05:58:41 DEBUG| [stdout] vm-segv STARTING + ARCHIVE=/var/lib/jenkins/jobs/smoke__B_amd64-generic__using_onibi__for_kernel/builds/2/archive + scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -r ubuntu@onibi:kernel-test-results /var/lib/jenkins/jobs/smoke__B_amd64-generic__using_onibi__for_kernel/builds/2/archive To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1864063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863312] Re: bionic/linux-oem: 4.15.0-1074.84 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem - phase: Holding before Promote to Proposed - phase-changed: Tuesday, 25. February 2020 09:52 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 25. February 2020 11:51 UTC + reason: + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1863312 Title: bionic/linux-oem: 4.15.0-1074.84 -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: New 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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1863350 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Ready for Promote to Proposed phase-changed: Tuesday, 25. February 2020 11:51 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864005] Re: Fix AMD Stoney Ridge screen flickering under 4K resolution
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864005 Title: Fix AMD Stoney Ridge screen flickering under 4K resolution Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] Screen flickering/tearing when AMD Stoney Ridge outputs to 4K display. [Fix] Disable IOMMU on Stoney Ridge. [Test] Connect to 4K screen through DP or HDMI. Heavy flickering/tearing can be observed. The flickering/tearing is gone once the patch is applied. [Regression Potential] Low. This fix limits to one specific SoC. According to AMD, IOMMU isn't enabled for this SoC under Windows. So it's expected behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1864005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863331] Re: xenial/linux-fips: 4.4.0-1030.35 -proposed tracker
4.4.0-1030.35 - fips Regression test CMPL, RTB. 56 / 60 tests were run, missing: ubuntu_boot, ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in amd64: ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) vmx (bug 1821394) ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454) quotactl07 (bug 1864092) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) 52 / 56 tests were run, missing: ubuntu_boot, ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in ppc64le (P8): ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 320M on Xenial P8 (bug 1813863) ubuntu_ecryptfs - manually tested and passed ubuntu_fan_smoke_test - Failed to fetch file from http://ports.ubuntu.com (bug 1864140) ubuntu_ltp_syscalls - fanotify07 won't fix (bug 1775165) fallocate04, fallocate05, fsetxattr01, fdatasync03, fgetxattr01, fremovexattr01, fremovexattr02, fsync01, fsync04, fanotify13, fanotify14, fanotify15, lremovexattr01, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, setxattr01, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842270) fanotify06 (bug 1833028) fanotify10 (bug 1802454) move_pages12 (bug 1831043) quotactl07 (bug 1864092) ubuntu_seccomp - failed on D s390x / PowerPC (bug 1850904) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) 51 / 52 tests were run, missing: ubuntu_boot Issue to note in s390x (KVM): libhugetlbfs - brk_near_huge (bug 1653597) Address is not hugepage / Heap not on hugepages (bug 1864650) ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - test should be skipped for X s390x KVM ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454) quotactl07 (bug 1864092) ubuntu_seccomp - failed on D s390x / PowerPC (bug 1850904) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) ** 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/1863331 Title: xenial/linux-fips: 4.4.0-1030.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released 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: Fix Released 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 Xenial: 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: 1863338 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Thursday, 20. February 2020 17:52 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/1863331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862980] Re: i2c-HTIX5288:00: i2c_hid_get_input: incomplete report
When the system boots everything works fine. After a few time, the context menu open as if I had right-clicked and the left button starts to act like the right button. When it occurs, there is some messages in dmesg like: i2c_designware i2c_designware.7: i2c_dw_handle_tx_abort: lost arbitration i2c_designware i2c_designware.7: transfer terminated early - interrupt latency too high? So, I think the problem is related to i2c-designware-pci. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862980 Title: i2c-HTIX5288:00: i2c_hid_get_input: incomplete report Status in linux package in Ubuntu: Confirmed Bug description: The touchpad is spamming "i2c_hid_get_input: incomplete report" messages to dmesg and not working properly. Sometimes the left button acts like the right button. Sometimes it freezes completely. Also the keys to enable/disable touchpad (fn + f2) doesn't work. Also 'libinput list-devices' shows the following message: "event4 - HTIX5288:00 0911:5288 Touchpad: kernel bug: clickpad advertising right button" What's expected to happen? - The touchpad working properly. What's actually happening? - The touchpad not working properly. How to reproduce? - Start the computer and wait a few minutes. How to make the touchpad work normally for a few minutes (or seconds): - sudo rmmod i2c_hid && sudo modprobe i2c_hid ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username 1382 F pulseaudio Date: Wed Feb 12 13:11:15 2020 InstallationDate: Installed on 2020-02-02 (10 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) 300k Pixel Camera Bus 001 Device 004: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Positivo Tecnologia SA N1240 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=2656c128-b4f1-48e5-b1ef-79eea7a3280d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA dmi.bios.version: V1.09.X dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: N14DP6 dmi.board.vendor: Positivo Tecnologia SA dmi.board.version: 11139547 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Positivo Tecnologia SA dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: MASTER dmi.product.name: N1240 dmi.product.sku: 3052532 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Positivo Tecnologia SA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863331] Re: xenial/linux-fips: 4.4.0-1030.35 -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: 1863338 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Thursday, 20. February 2020 17:52 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/1863331 Title: xenial/linux-fips: 4.4.0-1030.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released 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: Fix Released 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 Xenial: 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: 1863338 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Thursday, 20. February 2020 17:52 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/1863331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864654] [NEW] [UBUNTU 20.04] change zipl man pages for the implemented secure-boot descripton
You have been subscribed to a public bug: An update of the man pages of the zipl tool is required, to document the implemented secure-boot configuration. Setting this feature to ship issue->only for tracking purposes as mandatory fix for Ubuntu 20.04 GA ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-184061 severity-critical targetmilestone-inin2004 -- [UBUNTU 20.04] change zipl man pages for the implemented secure-boot descripton https://bugs.launchpad.net/bugs/1864654 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864654] [NEW] [UBUNTU 20.04] change zipl man pages for the implemented secure-boot descripton
Public bug reported: An update of the man pages of the zipl tool is required, to document the implemented secure-boot configuration. Setting this feature to ship issue->only for tracking purposes as mandatory fix for Ubuntu 20.04 GA ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-184061 severity-critical targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-184061 severity-critical targetmilestone-inin2004 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864654 Title: [UBUNTU 20.04] change zipl man pages for the implemented secure-boot descripton Status in linux package in Ubuntu: New Bug description: An update of the man pages of the zipl tool is required, to document the implemented secure-boot configuration. Setting this feature to ship issue->only for tracking purposes as mandatory fix for Ubuntu 20.04 GA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863312] Re: bionic/linux-oem: 4.15.0-1074.84 -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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1863312 Title: bionic/linux-oem: 4.15.0-1074.84 -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: New 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1863350 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Tuesday, 25. February 2020 13:46 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864654] Re: [UBUNTU 20.04] change zipl man pages for the implemented secure-boot descripton
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: s390-tools (Ubuntu) Status: New => Incomplete ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Status: New => Incomplete ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: s390-tools (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864654 Title: [UBUNTU 20.04] change zipl man pages for the implemented secure-boot descripton Status in Ubuntu on IBM z Systems: Incomplete Status in s390-tools package in Ubuntu: Incomplete Bug description: An update of the man pages of the zipl tool is required, to document the implemented secure-boot configuration. Setting this feature to ship issue->only for tracking purposes as mandatory fix for Ubuntu 20.04 GA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1864654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863312] Re: bionic/linux-oem: 4.15.0-1074.84 -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: 1863350 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem - phase: Ready for Promote to Proposed - phase-changed: Tuesday, 25. February 2020 11:51 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 25. February 2020 13:46 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress variant: debs -- 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/1863312 Title: bionic/linux-oem: 4.15.0-1074.84 -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: New 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1863350 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Tuesday, 25. February 2020 13:46 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B
On a arm64 node we had some more useful console logs: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/arm64/l/linux/20200223_153549_99119@/log.gz [ 7400.666431] rcu_sched kthread starved for 240027 jiffies! g460241 c460240 f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0 ->cpu=1 [ 7426.939201] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [stress-ng-vm-se:29260] [ 7427.941599] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [stress-ng-vm-se:28674] [ 7580.664232] INFO: rcu_sched self-detected stall on CPU [ 7580.89] 3-...!: (284881 ticks this GP) idle=cfa/141/0 softirq=1720701/1720703 fq s=0 [ 7580.671124] (t=285031 jiffies g=460241 c=460240 q=979) [ 7580.672223] INFO: rcu_sched detected stalls on CPUs/tasks: [ 7580.673660] rcu_sched kthread starved for 285032 jiffies! g460241 c460240 f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0 ->cpu=1 [ 7580.675893] 3-...!: (284881 ticks this GP) idle=cfa/141/0 softirq=1720701/1720703 fqs=0 [ 7580.685152] [ 7580.686074] rcu_sched kthread starved for 285035 jiffies! g460241 c460240 f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0 ->cpu=1 [ 7606.937596] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [stress-ng-vm-se:29260] [ 7607.947991] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [stress-ng-vm-se:29259] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864063 Title: vm-segv from ubuntu_stress_smoke_test failed on B Status in Stress-ng: Incomplete Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: Issue found on node onibi, with kernel 4.15.0-89.89/ 4.15.0-89.89~16.04.1 Reproduce rate: 2/2 on generic kernel, 2/2 on lowlatency kernel, 2/2 on X-hwe generic kernel Test hang with vm-segv: 05:58:36 DEBUG| [stdout] vm-addr PASSED 05:58:36 DEBUG| [stdout] vm-rw STARTING 05:58:41 DEBUG| [stdout] vm-rw RETURNED 0 05:58:41 DEBUG| [stdout] vm-rw PASSED 05:58:41 DEBUG| [stdout] vm-segv STARTING + ARCHIVE=/var/lib/jenkins/jobs/smoke__B_amd64-generic__using_onibi__for_kernel/builds/2/archive + scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -r ubuntu@onibi:kernel-test-results /var/lib/jenkins/jobs/smoke__B_amd64-generic__using_onibi__for_kernel/builds/2/archive To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1864063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed
** Tags added: sru-20200217 -- 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/1834006 Title: cpuset_hotplug from controllers in ubuntu_ltp failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux source package in Disco: New Status in linux-aws source package in Disco: New Bug description: Issue found on node amaura: <<>> tag=cpuset_hotplug stime=1561372131 cmdline="cpuset_hotplug_test.sh" contacts="" analysis=exit <<>> incrementing stop cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, Expect: 0-7). cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded. <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=19 cstime=81 <<>> Test script: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-22-generic 4.18.0-22.23 ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 24 10:25 seq crw-rw 1 root audio 116, 33 Jun 24 10:25 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jun 24 10:30:59 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1719945] Re: Silently fails in Wayland session
I see "ERROR: Unable to find display on any available system" when starting with Wayland. Is there and update on this issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1719945 Title: Silently fails in Wayland session Status in nvidia-settings package in Ubuntu: Confirmed Bug description: I've got an nvidia/intel hybrid laptop. In a Wayland session nvidia- settings fails silently when started from the shell. When started from a terminal, it prints: ERROR: Unable to load info from any available system and then quits. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-settings 367.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 27 11:49:57 2017 InstallationDate: Installed on 2017-09-20 (7 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1719945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
I noticed that upstream v5.4.18 allowed me to adjust my screen brightness while Ubuntu-5.4-5.4.0-14.17 does not, which indicates an Ubuntu SAUCE patch as the culprit. I bisected between the two kernels and this was the result: $ git bisect good 3269788061d24e316633165608259de1c110b801 is the first bad commit commit 3269788061d24e316633165608259de1c110b801 Author: AceLan Kao Date: Thu Dec 12 17:07:44 2019 +0800 USUNTU: SAUCE: drm/i915: Force DPCD backlight mode on Dell Precision 4K sku BugLink: https://bugs.launchpad.net/bugs/1856134 This platform using DPCD aux to control backlight, so adding the first 3 OUI bytes to the quirk. Signed-off-by: AceLan Kao Signed-off-by: Seth Forshee :04 04 5eb20635c698b49ae34aece26e3ee9f24631ca72 0a3389d202d1306745004ff8837731f2ceda317e M drivers I'm no expert in this area but it looks to me like that commit is being too generic and a more specific device_id is needed to target that Dell device. Here's the information on my panel: $ edid-decode /sys/class/drm/card0-eDP-1/edid edid-decode (hex): 00 ff ff ff ff ff ff 00 26 cf 7f 05 00 00 00 00 00 1b 01 04 a5 1f 11 78 0a 1d 39 a7 50 47 97 27 13 4f 54 00 00 00 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 60 6d 80 c8 70 38 14 40 18 30 a5 00 35 ae 10 00 00 19 00 00 00 fe 00 4d 31 34 30 4e 56 46 37 20 52 30 20 0a 00 00 00 03 00 04 30 ff 05 3c 9d 2b 14 39 9d 00 00 00 00 00 00 03 00 06 18 ff 0f 3c 3b 2a 0b 39 3b 01 01 00 00 ad EDID version: 1.4 Manufacturer: IVO Model 1407 Serial Number 0 Made in year 2017 Digital display 8 bits per primary color channel DisplayPort interface Maximum image size: 31 cm x 17 cm Gamma: 2.20 Supported color formats: RGB 4:4:4, YCrCb 4:4:4 First detailed timing includes the native pixel format and preferred refresh rate Color Characteristics Red: 0.6523, 0.3134 Green: 0.2802, 0.5908 Blue: 0.1523, 0.0771 White: 0.3105, 0.3291 Established Timings I & II: none Standard Timings: none Detailed mode: Clock 280.000 MHz, 309 mm x 174 mm 1920 1944 1992 2120 ( 24 48 128) 1080 1090 1095 1100 ( 10 5 5) -hsync -vsync VertFreq: 120.069 Hz, HorFreq: 132.075 kHz Alphanumeric Data String: M140NVF7 R0 Manufacturer-Specified Display Descriptor (0x03): 00 03 00 04 30 ff 05 3c 9d 2b 14 39 9d 00 00 00 0..<.+.9 Manufacturer-Specified Display Descriptor (0x03): 00 03 00 06 18 ff 0f 3c 3b 2a 0b 39 3b 01 01 00 ...<;*.9;... Checksum: 0xad ** Changed in: linux-5.4 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1861521 Title: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled Status in linux-5.4 package in Ubuntu: Confirmed Status in linux-5.4 source package in Focal: Confirmed Bug description: After upgrading from Eoan (5.3.0-29.31) to Focal (5.4.0-12.15), I no longer have the ability to control the backlight brightness on my HP EliteBook 840 G5. When pressing the brightness hotkeys, the on-screen indicator pops up and shows that the brightness setting is being changed but the actual screen brightness is stuck on the lowest setting. This laptop has a built-in privacy screen. If I activate the privacy screen (fn-f2), then the actual screen brightness goes to the maximum setting and then I am able to dim and brighten the backlight as long as the privacy screen functionality is turned on. This is a regression from Eoan's 5.3.0-29.31 kernel where I was able to control the brightness with and without the privacy screen functionality being turned on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 11:42:16 2020 InstallationDate: Installed on 2019-06-24 (221 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-28 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1861521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
To provide further verification, I built Ubuntu-5.4-5.4.0-14.17 with a
single patch on top that reverts commit 3269788061d2 ("USUNTU: SAUCE:
drm/i915: Force DPCD backlight mode on Dell Precision 4K sku"). My
screen brightness controls are working again and I can undock from my
external monitor without having to forcibly reboot the system due to a
blank screen on my built-in monitor (I guess my screen brightness is
turned all the way down when I undock and I cannot adjust it).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1861521
Title:
[FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
Status in linux-5.4 package in Ubuntu:
Confirmed
Status in linux-5.4 source package in Focal:
Confirmed
Bug description:
After upgrading from Eoan (5.3.0-29.31) to Focal (5.4.0-12.15), I no
longer have the ability to control the backlight brightness on my HP
EliteBook 840 G5. When pressing the brightness hotkeys, the on-screen
indicator pops up and shows that the brightness setting is being
changed but the actual screen brightness is stuck on the lowest
setting.
This laptop has a built-in privacy screen. If I activate the privacy
screen (fn-f2), then the actual screen brightness goes to the maximum
setting and then I am able to dim and brighten the backlight as long
as the privacy screen functionality is turned on.
This is a regression from Eoan's 5.3.0-29.31 kernel where I was able
to control the brightness with and without the privacy screen
functionality being turned on.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 31 11:42:16 2020
InstallationDate: Installed on 2019-06-24 (221 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: Upgraded to focal on 2020-01-28 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1861521/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
** Tags added: champagne -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1861521 Title: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled Status in linux-5.4 package in Ubuntu: Confirmed Status in linux-5.4 source package in Focal: Confirmed Bug description: After upgrading from Eoan (5.3.0-29.31) to Focal (5.4.0-12.15), I no longer have the ability to control the backlight brightness on my HP EliteBook 840 G5. When pressing the brightness hotkeys, the on-screen indicator pops up and shows that the brightness setting is being changed but the actual screen brightness is stuck on the lowest setting. This laptop has a built-in privacy screen. If I activate the privacy screen (fn-f2), then the actual screen brightness goes to the maximum setting and then I am able to dim and brighten the backlight as long as the privacy screen functionality is turned on. This is a regression from Eoan's 5.3.0-29.31 kernel where I was able to control the brightness with and without the privacy screen functionality being turned on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 11:42:16 2020 InstallationDate: Installed on 2019-06-24 (221 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-28 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1861521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862776] Re: [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib)
** Description changed: * alsa-ucm-conf = Availability = Built for all supported architectures as it's an arch all binary. In sync with Debian. https://launchpad.net/ubuntu/+source/alsa-ucm-conf/1.2.1.2-2 = Rationale = It's providing data useful to alsa to know how to handle hardware = Security = No known CVEs. https://security-tracker.debian.org/tracker/source-package/alsa-ucm-conf https://launchpad.net/ubuntu/+source/alsa-ucm-conf/+cve = Quality assurance = - - Kernel Packages team needs to be subscribed. + - Kernel Packages is subscribed to the ubuntu source - no tests, the package provides data file only https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=alsa-ucm-conf = Dependencies = No universe binary dependencies, the package has no depends = Standards compliance = standard dh12 packaging = Maintenance = Maintained with alsa upstream and in Debian * alsa-topology-conf = Availability = Built for all supported architectures as it's an arch all binary. In sync with Debian. https://launchpad.net/ubuntu/+source/alsa-topology-conf/1.2.1-2 = Rationale = It's providing data useful to alsa to know how to handle hardware = Security = No known CVEs. https://security-tracker.debian.org/tracker/source-package/alsa-topology-conf https://launchpad.net/ubuntu/+source/alsa-topology-conff/+cve = Quality assurance = - - Kernel Packages team needs to be subscribed. + - Kernel Packages is subscribed to the ubuntu source - no tests, the package provides data file only https://bugs.launchpad.net/ubuntu/+source/alsa-topology-conf https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=alsa-topology-conf = Dependencies = No universe binary dependencies, the package has no depends = Standards compliance = standard dh12 packaging = Maintenance = Maintained with alsa upstream and in Debian -- You received this bug notification because you are a member of Kernel Packages, which is a bug assignee. https://bugs.launchpad.net/bugs/1862776 Title: [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib) Status in alsa-topology-conf package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Bug description: * alsa-ucm-conf = Availability = Built for all supported architectures as it's an arch all binary. In sync with Debian. https://launchpad.net/ubuntu/+source/alsa-ucm-conf/1.2.1.2-2 = Rationale = It's providing data useful to alsa to know how to handle hardware = Security = No known CVEs. https://security-tracker.debian.org/tracker/source-package/alsa-ucm-conf https://launchpad.net/ubuntu/+source/alsa-ucm-conf/+cve = Quality assurance = - Kernel Packages is subscribed to the ubuntu source - no tests, the package provides data file only https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=alsa-ucm-conf = Dependencies = No universe binary dependencies, the package has no depends = Standards compliance = standard dh12 packaging = Maintenance = Maintained with alsa upstream and in Debian * alsa-topology-conf = Availability = Built for all supported architectures as it's an arch all binary. In sync with Debian. https://launchpad.net/ubuntu/+source/alsa-topology-conf/1.2.1-2 = Rationale = It's providing data useful to alsa to know how to handle hardware = Security = No known CVEs. https://security-tracker.debian.org/tracker/source-package/alsa-topology-conf https://launchpad.net/ubuntu/+source/alsa-topology-conff/+cve = Quality assurance = - Kernel Packages is subscribed to the ubuntu source - no tests, the package provides data file only https://bugs.launchpad.net/ubuntu/+source/alsa-topology-conf https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=alsa-topology-conf = Dependencies = No universe binary dependencies, the package has no depends = Standards compliance = standard dh12 packaging = Maintenance = Maintained with alsa upstream and in Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-topology-conf/+bug/1862776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679208] Re: Zesty (4.10.0-14) won't boot on HP ProLiant DL360 Gen9 with intel_iommu=on
Christian, was this ever resolved? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679208 Title: Zesty (4.10.0-14) won't boot on HP ProLiant DL360 Gen9 with intel_iommu=on Status in linux package in Ubuntu: Incomplete Bug description: TL;DR - one of our HP ProLiant DL360 Gen9 fails to boot with intel_iommu=on - the Disk controller fails - Xenial seems to work for a while but then fails - Zesty 100% crashes on boot - An identical system seems to work, so need HW replace to finally confirm After reboot one sees a HW report like this: After the boot I see the HW telling me this on boot: Embedded RAID : Smart HBA H240ar Controller - Operation Failed - 1719-Slot 0 Drive Array - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13) I tried several things (In between always redeploy zesty with MAAS). I think my debugging might be helpful, but I wanted to keep the documentation in the bug in case you'd go another route or that others find useful information in here. 0. I retried what I did twice, fully reproducible That is: 0.1 install zesty 0.2 change grub default cmdline in /etc/default/grub.d/50- to add intel_iommu=on 0.3 sudo update-grub 0.4 reboot 1. I tried a Recovery boot from the boot options in gub. => Failed as well 2. iLO rebooted vis "request reboot" and as well via "full system reset" => both Failed 3. Reboot the system as deployed by MAAS # /proc/cmdline before that BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=2137c19a-d441-43fa-82e2-f2b7e3b2727b ro The orig grub.cfg is like http://paste.ubuntu.com/24305945/ It reboots as-is. => Reboot worked 4. without a change to anything in /etc run update-grub $ sudo update-grub Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-4.10.0-14-generic Found initrd image: /boot/initrd.img-4.10.0-14-generic Adding boot menu entry for EFI firmware configuration done There was no diff between the new grub.cfg and the one I saved. => Reboot worked 5. add the intel_iommu=on arg $ sudo sed -i 's/GRUB_CMDLINE_LINUX_DEFAULT=""/GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on"/' /etc/default/grub.d/50-curtin-settings.cfg $ sudo update-grub # Diff in grub.cfg really only is the iommu setting => Reboot Failed So this doesn't seem so much of a cloud-init/curtin/maas bug anymore to me - maybe intel_iommu bheaves different? - Check grub cfg pre/post - not change but the expected? 6. Install Xenial and do the same => Reboot working 7. Upgrade to Z Since the Xenial system just worked and one can assume that almost only kernel is working so early in the boot process I upgraded the working system with intel_iommu=on to Zesty. That would be 4.4.0-71-generic to 4.10.0-1 On this upgrade I finally saw my I/O errors again :-/ Note: these issues are hard to miss as they mount root as read-only. I wonder if they only ever appear with intel_iommu=on as this is the only combo I ever saw them, 8. Redeploy and upgrade to Z without intel_iommu=on enabled Then enable intel_iommu=on and reboot => Reboot Fail From here I rebooted into the Xenial kerenl (that since this is an update was still there) Here I saw: Loading Linux 4.4.0-71-generic ... Loading initial ramdisk ... error: invalid video mode specification `text'. Booting in blind mode Hrm, as outlined above the "blind mode" might be a red herring, but since this kernel worked before it might still be a red herring that swims in the initrd that got regenerated on the upgrade. => Xenial Kernel Reboot - works !! So "blind mode" is a red herring of some sort. But this might allow to find some logs => No This appears as if the Failing boot has never made it to the point to actually write anything. I see: 1. the original xenial 2. the upgraded zesty 3. NOT THE zesty+iommu 4. the xenial+iommu $ egrep 'kernel:.*(Linux version|Command line)' /var/log/syslog Apr 3 12:15:20 node-horsea kernel: [0.00] Linux version 4.4.0-71-generic (buildd@lcy01-05) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #92-Ubuntu SMP Fri Mar 24 12:59:01 UTC 2017 (Ubuntu 4.4.0-71.92-generic 4.4.49) Apr 3 12:15:20 node-horsea kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic root=UUID=2137c19a-d441-43fa-82e2-f2b7e3b2727b ro Apr 3 12:47:45 node-horsea kernel: [0.00] Linux version 4.10.0-14-generic (buildd@lcy01-01) (gcc version 6.3.0 20170221 (Ubuntu 6.3.0-8ubuntu1) ) #16-Ubuntu
[Kernel-packages] [Bug 1863312] Re: bionic/linux-oem: 4.15.0-1074.84 -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: 1863350 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Tuesday, 25. February 2020 13:46 UTC reason: - promote-to-proposed: Ongoing -- review in progress + 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1863312 Title: bionic/linux-oem: 4.15.0-1074.84 -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: New 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1863350 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Tuesday, 25. February 2020 13:46 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/1863312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
@smoser a looks merged b has not had any changes since 2018 and looks up-to-date in Focal. What am I missing? c I see a devel branch, is it assumed that it uses a packaging structure similar to cloud-init or can someone just grab and upload master? -- 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: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed 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 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
Note that the quirks in the debug output from comment #9 are 0x
because I've got still got commit 3269788061d2 ("USUNTU: SAUCE:
drm/i915: Force DPCD backlight mode on Dell Precision 4K sku") reverted
locally.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1861521
Title:
[FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
Status in linux-5.4 package in Ubuntu:
Confirmed
Status in linux-5.4 source package in Focal:
Confirmed
Bug description:
After upgrading from Eoan (5.3.0-29.31) to Focal (5.4.0-12.15), I no
longer have the ability to control the backlight brightness on my HP
EliteBook 840 G5. When pressing the brightness hotkeys, the on-screen
indicator pops up and shows that the brightness setting is being
changed but the actual screen brightness is stuck on the lowest
setting.
This laptop has a built-in privacy screen. If I activate the privacy
screen (fn-f2), then the actual screen brightness goes to the maximum
setting and then I am able to dim and brighten the backlight as long
as the privacy screen functionality is turned on.
This is a regression from Eoan's 5.3.0-29.31 kernel where I was able
to control the brightness with and without the privacy screen
functionality being turned on.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 31 11:42:16 2020
InstallationDate: Installed on 2019-06-24 (221 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: Upgraded to focal on 2020-01-28 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1861521/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863325] Re: bionic/linux-aws: 4.15.0-1061.65 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Friday, 21. February 2020 13:31 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-aws-fips: bug 1863317 bionic/linux-aws/aws-kernel: bug 1863315 xenial/linux-aws-hwe: bug 1863320 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/1863325 Title: bionic/linux-aws: 4.15.0-1061.65 -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: In Progress 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: 1863350 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Friday, 21. February 2020 13:31 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 1863317 bionic/linux-aws/aws-kernel: bug 1863315 xenial/linux-aws-hwe: bug 1863320 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
I enabled the KMS debug messages in the drm module:
$ cat /etc/modprobe.d/drm-debug.conf
options drm debug=0x04
$ sudo update-initramfs -u -k $(uname -r) && sudo reboot
...
Unfortunately, it doesn't look like my device_id is set after the
drm_dp_read_desc() in drm_dp_read_desc:
$ dmesg | grep -i OUI
[1.378026] [drm:drm_dp_read_desc [drm_kms_helper]] DP sink: OUI 38-ec-11
dev-ID HW-rev 0.0 SW-rev 0.0 quirks 0x
Hopefully the device_id is set for the Dell platform in bug #1856134 so
that commit 3269788061d2 ("USUNTU: SAUCE: drm/i915: Force DPCD backlight
mode on Dell Precision 4K sku") can be more specific to that device.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1861521
Title:
[FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
Status in linux-5.4 package in Ubuntu:
Confirmed
Status in linux-5.4 source package in Focal:
Confirmed
Bug description:
After upgrading from Eoan (5.3.0-29.31) to Focal (5.4.0-12.15), I no
longer have the ability to control the backlight brightness on my HP
EliteBook 840 G5. When pressing the brightness hotkeys, the on-screen
indicator pops up and shows that the brightness setting is being
changed but the actual screen brightness is stuck on the lowest
setting.
This laptop has a built-in privacy screen. If I activate the privacy
screen (fn-f2), then the actual screen brightness goes to the maximum
setting and then I am able to dim and brighten the backlight as long
as the privacy screen functionality is turned on.
This is a regression from Eoan's 5.3.0-29.31 kernel where I was able
to control the brightness with and without the privacy screen
functionality being turned on.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 31 11:42:16 2020
InstallationDate: Installed on 2019-06-24 (221 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: Upgraded to focal on 2020-01-28 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1861521/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863325] Re: bionic/linux-aws: 4.15.0-1061.65 -proposed tracker
SRU Bugs: https://bugs.launchpad.net/ubuntu-kernel-tests/+bugs?field.tag=sru-20200217+aws&field.tags_combinator=ALL ** Tags added: regression-testing-passed -- 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/1863325 Title: bionic/linux-aws: 4.15.0-1061.65 -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: In Progress 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: 1863350 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Friday, 21. February 2020 13:31 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 1863317 bionic/linux-aws/aws-kernel: bug 1863315 xenial/linux-aws-hwe: bug 1863320 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
a.) I gave the wrong link. ugh. It should have been: https://code.launchpad.net/~smoser/cloud-initramfs-tools/+git/cloud-initramfs-tools/+merge/379774 b.) the fixed link to 'a' probably makes more sense now. But basically you need a newer cloud-initramfs-tools to adjust for the fact that growpart needs flock now. cloud-initramfs-tools I believe is still a "native package". So it just has the packaging along side c.) you can use new-upstream-snapshot. cloud-utils is set to use the same basic workflow as cloud-init or curtin. I'm OK to upload cloud-initramfs-tools and also cloud-utils, but I think in both cases it makes sense to get someone from server team to do it. Just to have someone other than myself having done it. -- 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: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed 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 1846237] Comment bridged from LTC Bugzilla
--- Comment From iranna.an...@in.ibm.com 2020-02-25 10:58 EDT--- An update: One of my team member verified this bug on Ubuntu 20.04 and could successfully virsh dump for guest having 900G memory. So...based on these results we are OK to close this bug. Thanks! Here are the steps tried: -- Created and brought up a guest with 900GB memory and tried virsh dump root@ws-g48-2d81-host:~# virsh list --all Id Name State 1virt-tests-raji running -virt-tests-vm1shut off virt-tests-raji 8623a1dd-e043-4e2b-a75d-62a9cdead80e 943718400 943718400 root@ws-g48-2d81-host:~# virsh dump virt-tests-raji vmcore root@ws-g48-2d81-host:~# du -sh vmcore 4.3Gvmcore root@ws-g48-2d81-host:~# makedumpfile -d 15 vmcore dumpfile check_elf_format: Can't get valid ehdr. makedumpfile Failed. Encountered an issue with makedumpfile for the dump generated. Also tried the crash tool directly on the dump and crash failed too. Tried virsh dump with --live option and tried makedumpfile & crash on the dump and encountered the same failure. Tried virsh dump with --memory-only option. Since the memory of the VM was 900GB, dump was being taken for the whole 900GB memory, which was taking a long time to complete. Identified that "The crash utility no longer supports the default core dump file format of the virsh dump command and --memory-only option is needed to analyse the core dump file created by virsh dump" Tried the virsh dump with --memory-only option on a VM with lesser memory and was able to get the dump. Used crash to analyse the core dump and it worked successfully. root@ws-g48-2d81-host:~# virsh dump --memory-only --format=kdump-lzo virt-tests-vm1 vmcore_memory1 error: Failed to core dump domain virt-tests-vm1 to vmcore_memory1 error: invalid argument: unsupported dumpformat 'kdump-lzo' for this QEMU binary root@ws-g48-2d81-host:~# virsh dump --memory-only --format=kdump-zlib virt-tests-vm1 vmcore_memory1 Domain virt-tests-vm1 dumped to vmcore_memory1 root@ws-g48-2d81-host:~# du -sh vmcore_memory1 153M vmcore_memory1 root@ws-g48-2d81-host:~# crash vmcore_memory1 vmlinux-5.4.0-13-generic crash 7.2.8 Copyright (C) 2002-2020 Red Hat, Inc. Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation Copyright (C) 1999-2006 Hewlett-Packard Co Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited Copyright (C) 2006, 2007 VA Linux Systems Japan K.K. Copyright (C) 2005, 2011 NEC Corporation Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc. Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc. This program is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Enter "help copying" to see the conditions. This program has absolutely no warranty. Enter "help warranty" for details. crash: vmlinux-5.4.0-13-generic: no debugging data available -- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846237 Title: Kernel Panic while virsh dump of Guest with 300G RAM is triggered. Status in The Ubuntu-power-systems project: Invalid Status in libvirt package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: == Comment: #0 - HARIHARAN T. SUNDARESH REDDY - 2019-04-01 12:23:14 == ---Problem Description--- Kernel panic occurred when `virsh dump` is triggered on the guest with 300G of RAM. ---uname output--- Linux ltcgen6 4.15.0-1017.19-bz175922-ibm-gt #bz175922 SMP Thu Mar 21 09:34:09 CDT 2019 ppc64le ppc64le ppc64le GNU/Linux ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Define guest with 300G RAM, Start the guest 2. Run the following command `virsh dump ubuntui_hsr /home/vm.core --memory-only --live' 3. Wait for some time, kernel panic will be see in the console. --Log--- [ 1692.657251] INFO: task journal-offline:7763 blocked for more than 120 seconds. [ 1692.657251] INFO: task journal-offline:7763 blocked for more than 120 seconds. [ 1692.657754] Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.657754] Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.658220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1692.658220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1692.658839] Kernel panic - not syncing: hung_task: blocked tasks [ 1692.658839] Kernel panic - not syncing: hung_task: blocked tasks [ 1692.659238] CPU: 48 PID: 785 Comm: khungtaskd Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.659238] CPU: 48 PID: 785 Comm: khungtaskd Not tainted 4.15.
[Kernel-packages] [Bug 1864626] Re: nsleep-lat / set-timer-lat / inconsistency-check / raw_skew from timer in ubuntu_kernel_selftests timeout on 5.3 / 5.4
The time it need for each tests (tested on node rizzo with 5.3.0-40-generic): $ time sudo ./nsleep-lat nsleep latency CLOCK_REALTIME [OK] nsleep latency CLOCK_MONOTONIC[OK] nsleep latency CLOCK_MONOTONIC_RAW[UNSUPPORTED] nsleep latency CLOCK_REALTIME_COARSE [UNSUPPORTED] nsleep latency CLOCK_MONOTONIC_COARSE [UNSUPPORTED] nsleep latency CLOCK_BOOTTIME [OK] nsleep latency CLOCK_REALTIME_ALARM [OK] nsleep latency CLOCK_BOOTTIME_ALARM [OK] nsleep latency CLOCK_TAI [OK] # Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0 real2m7.350s user0m0.024s sys 0m0.000s $ time sudo ./set-timer-lat Setting timers for every 1 seconds CLOCK_REALTIME ABSTIME PERIODIC timer fired early: 0 : [OK] CLOCK_REALTIME ABSTIME PERIODIC max latency: 154950 ns : [OK] CLOCK_REALTIME RELTIME PERIODIC timer fired early: 0 : [OK] CLOCK_REALTIME RELTIME PERIODIC max latency: 155470 ns : [OK] CLOCK_REALTIME ABSTIME ONE-SHOT timer fired early: 0 : [OK] CLOCK_REALTIME ABSTIME ONE-SHOT max latency: 152090 ns : [OK] CLOCK_REALTIME ABSTIME ONE-SHOT count: 1 : [OK] CLOCK_REALTIME RELTIME ONE-SHOT timer fired early: 0 : [OK] CLOCK_REALTIME RELTIME ONE-SHOT max latency: 140419 ns : [OK] CLOCK_REALTIME RELTIME ONE-SHOT count: 1 : [OK] CLOCK_MONOTONICABSTIME PERIODIC timer fired early: 0 : [OK] CLOCK_MONOTONICABSTIME PERIODIC max latency: 153497 ns : [OK] CLOCK_MONOTONICRELTIME PERIODIC timer fired early: 0 : [OK] CLOCK_MONOTONICRELTIME PERIODIC max latency: 151476 ns : [OK] CLOCK_MONOTONICABSTIME ONE-SHOT timer fired early: 0 : [OK] CLOCK_MONOTONICABSTIME ONE-SHOT max latency: 149738 ns : [OK] CLOCK_MONOTONICABSTIME ONE-SHOT count: 1 : [OK] CLOCK_MONOTONICRELTIME ONE-SHOT timer fired early: 0 : [OK] CLOCK_MONOTONICRELTIME ONE-SHOT max latency: 140657 ns : [OK] CLOCK_MONOTONICRELTIME ONE-SHOT count: 1 : [OK] CLOCK_BOOTTIME ABSTIME PERIODIC timer fired early: 0 : [OK] CLOCK_BOOTTIME ABSTIME PERIODIC max latency: 153272 ns : [OK] CLOCK_BOOTTIME RELTIME PERIODIC timer fired early: 0 : [OK] CLOCK_BOOTTIME RELTIME PERIODIC max latency: 148789 ns : [OK] CLOCK_BOOTTIME ABSTIME ONE-SHOT timer fired early: 0 : [OK] CLOCK_BOOTTIME ABSTIME ONE-SHOT max latency: 146898 ns : [OK] CLOCK_BOOTTIME ABSTIME ONE-SHOT count: 1 : [OK] CLOCK_BOOTTIME RELTIME ONE-SHOT timer fired early: 0 : [OK] CLOCK_BOOTTIME RELTIME ONE-SHOT max latency: 139261 ns : [OK] CLOCK_BOOTTIME RELTIME ONE-SHOT count: 1 : [OK] CLOCK_REALTIME_ALARM ABSTIME PERIODIC timer fired early: 0 : [OK] CLOCK_REALTIME_ALARM ABSTIME PERIODIC max latency: 157077 ns : [OK] CLOCK_REALTIME_ALARM RELTIME PERIODIC timer fired early: 0 : [OK] CLOCK_REALTIME_ALARM RELTIME PERIODIC max latency: 151637 ns : [OK] CLOCK_REALTIME_ALARM ABSTIME ONE-SHOT timer fired early: 0 : [OK] CLOCK_REALTIME_ALARM ABSTIME ONE-SHOT max latency: 147835 ns : [OK] CLOCK_REALTIME_ALARM ABSTIME ONE-SHOT count: 1 : [OK] CLOCK_REALTIME_ALARM RELTIME ONE-SHOT timer fired early: 0 : [OK] CLOCK_REALTIME_ALARM RELTIME ONE-SHOT max latency: 138752 ns : [OK] CLOCK_REALTIME_ALARM RELTIME ONE-SHOT count: 1 : [OK] CLOCK_BOOTTIME_ALARM ABSTIME PERIODIC timer fired early: 0 : [OK] CLOCK_BOOTTIME_ALARM ABSTIME PERIODIC max latency: 155109 ns : [OK] CLOCK_BOOTTIME_ALARM RELTIME PERIODIC timer fired early: 0 : [OK] CLOCK_BOOTTIME_ALARM RELTIME PERIODIC max latency: 150989 ns : [OK] CLOCK_BOOTTIME_ALARM ABSTIME ONE-SHOT timer fired early: 0 : [OK] CLOCK_BOOTTIME_ALARM ABSTIME ONE-SHOT max latency: 147849 ns : [OK] CLOCK_BOOTTIME_ALARM ABSTIME ONE-SHOT count: 1 : [OK] CLOCK_BOOTTIME_ALARM RELTIME ONE-SHOT timer fired early: 0 : [OK] CLOCK_BOOTTIME_ALARM RELTIME ONE-SHOT max latency: 141602 ns : [OK] CLOCK_BOOTTIME_ALARM RELTIME ONE-SHOT count: 1 : [OK] CLOCK_TAI ABSTIME PERIODIC timer fired early: 0 : [OK] CLOCK_TAI ABSTIME PERIODIC max latency: 152173 ns : [OK] CLOCK_TAI RELTIME PERIODIC timer fired early: 0 : [OK] CLOCK_TAI RELTIME PERIODIC max latency: 147688 ns : [OK] CLOCK_TAI ABSTIME ONE-SHOT timer fired early: 0 : [OK] CLOCK_TAI ABSTIME ONE-SHOT max latency: 145860 ns : [OK] CLOCK_TAI ABSTIME ONE-SHOT count: 1 : [OK] CLOCK_TAI RELTIME ONE-SHOT timer fired early:
[Kernel-packages] [Bug 1864669] [NEW] [linux-azure] overlayfs regression - internal getxattr operations without sepolicy checking
Public bug reported:
Bug description and repro:
Run the following commands on host instances:
Prepare the overlayfs directories:
$ cd /tmp
$ mkdir -p base/dir1/dir2 upper olwork merged
$ touch base/dir1/dir2/file
$ chown -R 10:10 base upper olwork merged
Verify that the directory is owned by user 10:
$ ls -al merged/
total 8
drwxr-xr-x 2 10 10 4096 Nov 1 07:08 .
drwxrwxrwt 16 root root 4096 Nov 1 07:08 ..
We use lxc-usernsexec to start a new shell as user 10.
$ lxc-usernsexec -m b:0:10:1 -- /bin/bash
$$ ls -al merged/
total 8
drwxr-xr-x 2 root root4096 Nov 1 07:08 .
drwxrwxrwt 16 nobody nogroup 4096 Nov 1 07:08 ..
Notice that the ownership of . and .. has changed because the new shell is
running as the remapped user.
Now, mount the overlayfs as an unprivileged user in the new shell. This is the
key to trigger the bug.
$$ mount -t overlay -o lowerdir=base,upperdir=upper,workdir=olwork none merged
$$ ls -al merged/dir1/dir2/file
-rw-r--r-- 1 root root 0 Nov 1 07:09 merged/dir1/dir2/file
We can see the file in the base layer from the mount directory. Now trigger the
bug:
$$ rm -rf merged/dir1/dir2/
$$ mkdir merged/dir1/dir2
$$ ls -al merged/dir1/dir2
total 12
drwxr-xr-x 2 root root 4096 Nov 1 07:10 .
drwxr-xr-x 1 root root 4096 Nov 1 07:10 ..
File does not show up in the newly created dir2 as expected. But it will
reappear after we remount the filesystem (or any other means that might evict
the cached dentry, such as attempt to delete the parent directory):
$$ umount merged
$$ mount -t overlay -o lowerdir=base,upperdir=upper,workdir=olwork none merged
$$ ls -al merged/dir1/dir2
total 12
drwxr-xr-x 1 root root 4096 Nov 1 07:10 .
drwxr-xr-x 1 root root 4096 Nov 1 07:10 ..
-rw-r--r-- 1 root root0 Nov 1 07:09 file
$$ exit
$
This is a recent kernel regression. I tried the above step on an old
kernel (4.4.0-1072-aws) but cannot reproduce.
I looked up linux source code and figured out where the "regression" is coming
from. The issue lies in how overlayfs checks the "opaque" flag from the
underlying upper-level filesystem. It checks the "trusted.overlay.opaque"
extended attribute to decide whether to hide the directory content from the
lower level. The logic are different in 4.4 and 4.15 kernel.
In 4.4: https://elixir.bootlin.com/linux/v4.4/source/fs/overlayfs/super.c#L255
static bool ovl_is_opaquedir(struct dentry *dentry)
{
int res;
char val;
struct inode *inode = dentry->d_inode;
if (!S_ISDIR(inode->i_mode) || !inode->i_op->getxattr)
return false;
res = inode->i_op->getxattr(dentry, OVL_XATTR_OPAQUE, &val, 1);
if (res == 1 && val == 'y')
return true;
return false;
}
In 4.15: https://elixir.bootlin.com/linux/v4.15/source/fs/overlayfs/util.c#L349
static bool ovl_is_opaquedir(struct dentry *dentry)
{
return ovl_check_dir_xattr(dentry, OVL_XATTR_OPAQUE);
}
bool ovl_check_dir_xattr(struct dentry *dentry, const char *name)
{
int res;
char val;
if (!d_is_dir(dentry))
return false;
res = vfs_getxattr(dentry, name, &val, 1);
if (res == 1 && val == 'y')
return true;
return false;
}
The 4.4 version simply uses the internal i_node callback inode->i_op->getxattr
from the host filesystem, which doesn't perform any permission check. While the
4.15 version calls the VFS interface vfs_getxattr that performs bunch of
permission checks before the calling the internal insecure callback
__vfs_getxattr:
See https://elixir.bootlin.com/linux/v4.15/source/fs/xattr.c#L317
ssize_t
vfs_getxattr(struct dentry *dentry, const char *name, void *value, size_t size)
{
struct inode *inode = dentry->d_inode;
int error;
error = xattr_permission(inode, name, MAY_READ);
if (error)
return error;
error = security_inode_getxattr(dentry, name);
if (error)
return error;
if (!strncmp(name, XATTR_SECURITY_PREFIX,
XATTR_SECURITY_PREFIX_LEN)) {
const char *suffix = name + XATTR_SECURITY_PREFIX_LEN;
int ret = xattr_getsecurity(inode, suffix, value, size);
/*
* Only overwrite the return value if a security module
* is actually active.
*/
if (ret == -EOPNOTSUPP)
goto nolsm;
return ret;
}
nolsm:
return __vfs_getxattr(dentry, inode, name, value, size);
}
In 4.15, ovl_is_opaquedir is called by the following caller:
ovl_is_opaquedir <-
ovl_lookup_single() <-
ovl_lookup_layer <-
ovl_lookup,
ovl_lookup is the entry point for directory listing in overlayfs. Importantly,
it assumes the filesystem mounter's credential to perform all internal lookup
operations:
struct dentry *ovl_lookup(struct inode *dir, struct dentry *de
[Kernel-packages] [Bug 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]pad the short frame before sending to the hardware Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Bionic: In Progress Bug description: The hardware can not handle short frames below or equal to 32 bytes. [Impact] The system may hang or endless event log in /var/log/syslog [Fix] Cherry-pick or backport the upstream fix 36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before sending to the hardware [Test Case] Send a frame less than 33 bytes. [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] The hardware can not handle short frames below or equal to 32 bytes according to the hardware user manual, and it will trigger a RAS error when the frame's length is below 33 bytes. [Steps to Reproduce] 1.send a frame less than 33 bytes. [Actual Results] a RAS occurs [Expected Results] no RAS [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] pads the SKB when skb->len is below 33 bytes before sending it to hardware. net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860320] 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 1860320 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/1860320 Title: [hns3-0120]pad the short frame before sending to the hardware Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Bug description: The hardware can not handle short frames below or equal to 32 bytes. [Impact] The system may hang or endless event log in /var/log/syslog [Fix] Cherry-pick or backport the upstream fix 36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before sending to the hardware [Test Case] Send a frame less than 33 bytes. [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] The hardware can not handle short frames below or equal to 32 bytes according to the hardware user manual, and it will trigger a RAS error when the frame's length is below 33 bytes. [Steps to Reproduce] 1.send a frame less than 33 bytes. [Actual Results] a RAS occurs [Expected Results] no RAS [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] pads the SKB when skb->len is below 33 bytes before sending it to hardware. net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Patch added: "debdiff showing the changes to upload to fix the bug." https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5330894/+files/cloud-utils_0.31-6_to_0.31-7.debdiff -- 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: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed 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 1834875] Re: cloud-init growpart race with udev
@Scott, cloud-utils isn't quite new-upstream-snapshot out of the box; the debian dir does not contain the changelog; however, I think I've got this sorted out. I've a MP I can put up; but it only will show the add of the changelog file. I'll attach a debdiff and a source package. -- 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: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed 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 1834875] Re: cloud-init growpart race with udev
** Attachment added: "tarball of source package to upload" https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5330895/+files/cloud-utils_0.31-7-gd99b2d76-source.tar.xz -- 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: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed 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 1864626] Re: nsleep-lat / set-timer-lat / inconsistency-check / raw_skew from timer in ubuntu_kernel_selftests timeout on 5.3 / 5.4
V2 submitted: https://lists.linaro.org/pipermail/linux-kselftest-mirror/2020-February/011044.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864626 Title: nsleep-lat / set-timer-lat / inconsistency-check / raw_skew from timer in ubuntu_kernel_selftests timeout on 5.3 / 5.4 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: Test failed because of timeout: # selftests: timers: nsleep-lat # nsleep latency CLOCK_REALTIME [OK] # nsleep latency CLOCK_MONOTONIC[OK] # nsleep latency CLOCK_MONOTONIC_RAW[UNSUPPORTED] # nsleep latency CLOCK_REALTIME_COARSE [UNSUPPORTED] # nsleep latency CLOCK_MONOTONIC_COARSE [UNSUPPORTED] # nsleep latency CLOCK_BOOTTIME # not ok 3 selftests: timers: nsleep-lat # TIMEOUT # selftests: timers: set-timer-lat # not ok 4 selftests: timers: set-timer-lat # TIMEOUT # selftests: timers: inconsistency-check # Consistent CLOCK_REALTIME [OK] # Consistent CLOCK_MONOTONIC[OK] # Consistent CLOCK_PROCESS_CPUTIME_ID [OK] # Consistent CLOCK_THREAD_CPUTIME_ID[OK] # Consistent CLOCK_MONOTONIC_RAW# not ok 6 selftests: timers: inconsistency-check # TIMEOUT # selftests: timers: raw_skew # WARNING: ADJ_OFFSET in progress, this will cause inaccurate results # Estimating clock drift: # not ok 7 selftests: timers: raw_skew # TIMEOUT ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-40-generic 5.3.0-40.32~18.04.1 ProcVersionSignature: User Name 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 Date: Tue Feb 25 09:10:45 2020 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863989] Re: bad-altstack test from ubuntu_stress_smoke_test failed on Eoan zVM
** Changed in: stress-ng Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: stress-ng 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/1863989 Title: bad-altstack test from ubuntu_stress_smoke_test failed on Eoan zVM Status in Stress-ng: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Eoan zVM node kernel03 Test hung at bad-altstack test. Reproducible rate: 4 out of 4 attempts 02:36:12 DEBUG| [stdout] aiol STARTING 02:36:17 DEBUG| [stdout] aiol RETURNED 0 02:36:17 DEBUG| [stdout] aiol PASSED 02:36:17 DEBUG| [stdout] bad-altstack STARTING + ARCHIVE=/var/lib/jenkins/jobs/smoke__E_s390x.zVM-generic__using_kernel03__for_kernel/builds/3/archive + scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -r ubuntu@kernel03:kernel-test-results /var/lib/jenkins/jobs/smoke__E_s390x.zVM-generic__using_kernel03__for_kernel/builds/3/archive dmesg only shows: [ 102.352136] Adding 1048572k swap on /home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng/swap.img. Priority:-3 extents:95 across:26763272k SSFS [ 122.402895] NET: Registered protocol family 38 It looks like this is caused by OOM issue, x3270 console flushed with OOM error messages. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-41-generic 5.3.0-41.33 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.4 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Feb 20 06:06:04 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/mapper/kl03vg01-kl03root crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-5.3.0-41-generic N/A linux-backports-modules-5.3.0-41-generic N/A linux-firmware1.183.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-30 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1863989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846237] Re: Kernel Panic while virsh dump of Guest with 300G RAM is triggered.
Thx Iranna for the reply and positive feedback. With that I'm changing the status to Fix Released. ** Changed in: libvirt (Ubuntu) Status: Invalid => Fix Released ** Changed in: ubuntu-power-systems Status: Invalid => 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/1846237 Title: Kernel Panic while virsh dump of Guest with 300G RAM is triggered. Status in The Ubuntu-power-systems project: Fix Released Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: == Comment: #0 - HARIHARAN T. SUNDARESH REDDY - 2019-04-01 12:23:14 == ---Problem Description--- Kernel panic occurred when `virsh dump` is triggered on the guest with 300G of RAM. ---uname output--- Linux ltcgen6 4.15.0-1017.19-bz175922-ibm-gt #bz175922 SMP Thu Mar 21 09:34:09 CDT 2019 ppc64le ppc64le ppc64le GNU/Linux ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Define guest with 300G RAM, Start the guest 2. Run the following command `virsh dump ubuntui_hsr /home/vm.core --memory-only --live' 3. Wait for some time, kernel panic will be see in the console. --Log--- [ 1692.657251] INFO: task journal-offline:7763 blocked for more than 120 seconds. [ 1692.657251] INFO: task journal-offline:7763 blocked for more than 120 seconds. [ 1692.657754] Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.657754] Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.658220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1692.658220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1692.658839] Kernel panic - not syncing: hung_task: blocked tasks [ 1692.658839] Kernel panic - not syncing: hung_task: blocked tasks [ 1692.659238] CPU: 48 PID: 785 Comm: khungtaskd Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.659238] CPU: 48 PID: 785 Comm: khungtaskd Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.659835] Call Trace: [ 1692.659835] Call Trace: [ 1692.660025] [c08fd0eefbf8] [c0cea13c] dump_stack+0xb0/0xf4 (unreliable) [ 1692.660025] [c08fd0eefbf8] [c0cea13c] dump_stack+0xb0/0xf4 (unreliable) [ 1692.660564] [c08fd0eefc38] [c0110020] panic+0x148/0x328 [ 1692.660564] [c08fd0eefc38] [c0110020] panic+0x148/0x328 [ 1692.661004] [c08fd0eefcd8] [c0233a08] watchdog+0x2c8/0x420 [ 1692.661004] [c08fd0eefcd8] [c0233a08] watchdog+0x2c8/0x420 [ 1692.661429] [c08fd0eefdb8] [c0140068] kthread+0x1a8/0x1b0 [ 1692.661429] [c08fd0eefdb8] [c0140068] kthread+0x1a8/0x1b0 [ 1692.661881] [c08fd0eefe28] [c000b654] ret_from_kernel_thread+0x5c/0x88 [ 1692.661881] [c08fd0eefe28] [c000b654] ret_from_kernel_thread+0x5c/0x88 [ 1692.662439] Sending IPI to other CPUs [ 1692.662439] Sending IPI to other CPUs [ 1693.971250] IPI complete [ 1693.971250] IPI complete [ 1694.122536] kexec: Starting switchover sequence. [ 1694.122536] kexec: Starting switchover sequence. [ 1827.285354188,3] PHB#0003[0:3]: CRESET: Unexpected slot state 0102, resetting... [ 1831.426449832,3] PHB#0030[8:0]: CRESET: Unexpected slot state 0102, resetting... [ 1832.158844758,3] PHB#0033[8:3]: CRESET: Unexpected slot state 0102, resetting... [ 1832.403055326,3] PHB#0034[8:4]: CRESET: Unexpected slot state 0102, resetting... [1.924644] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [1.924644] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [1.924647] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [1.924647] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [1.991351] vio vio: uevent: failed to send synthetic uevent [1.991351] vio vio: uevent: failed to send synthetic uevent [2.524824] nouveau 0004:04:00.0: unknown chipset (14a1) [2.524824] nouveau 0004:04:00.0: unknown chipset (14a1) [2.525314] nouveau 0004:05:00.0: unknown chipset (14a1) [2.525314] nouveau 0004:05:00.0: unknown chipset (14a1) [2.525831] nouveau 0035:03:00.0: unknown chipset (14a1) [2.525831] nouveau 0035:03:00.0: unknown chipset (14a1) [2.526315] nouveau 0035:04:00.0: unknown chipset (14a1) [2.526315] nouveau 0035:04:00.0: unknown chipset (14a1) /dev/sda2
[Kernel-packages] [Bug 1863989] Re: bad-altstack test from ubuntu_stress_smoke_test failed on Eoan zVM
@Sam. Can you re-run the test and if it's OK then I no longer require the instance kernel03. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863989 Title: bad-altstack test from ubuntu_stress_smoke_test failed on Eoan zVM Status in Stress-ng: Invalid Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Eoan zVM node kernel03 Test hung at bad-altstack test. Reproducible rate: 4 out of 4 attempts 02:36:12 DEBUG| [stdout] aiol STARTING 02:36:17 DEBUG| [stdout] aiol RETURNED 0 02:36:17 DEBUG| [stdout] aiol PASSED 02:36:17 DEBUG| [stdout] bad-altstack STARTING + ARCHIVE=/var/lib/jenkins/jobs/smoke__E_s390x.zVM-generic__using_kernel03__for_kernel/builds/3/archive + scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -r ubuntu@kernel03:kernel-test-results /var/lib/jenkins/jobs/smoke__E_s390x.zVM-generic__using_kernel03__for_kernel/builds/3/archive dmesg only shows: [ 102.352136] Adding 1048572k swap on /home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng/swap.img. Priority:-3 extents:95 across:26763272k SSFS [ 122.402895] NET: Registered protocol family 38 It looks like this is caused by OOM issue, x3270 console flushed with OOM error messages. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-41-generic 5.3.0-41.33 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.4 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Feb 20 06:06:04 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/mapper/kl03vg01-kl03root crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-5.3.0-41-generic N/A linux-backports-modules-5.3.0-41-generic N/A linux-firmware1.183.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-30 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1863989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863989] Re: bad-altstack test from ubuntu_stress_smoke_test failed on Eoan zVM
This is probably fixed with commit: https://kernel.ubuntu.com/git/ubuntu /autotest-client- tests.git/commit/?id=4db07fef60449c786364638d7978b239676624eb I've run this a few times with the fix above and can't reproduce this issue. ** Changed in: ubuntu-kernel-tests Status: New => Fix Committed ** Changed in: stress-ng Status: New => Invalid ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863989 Title: bad-altstack test from ubuntu_stress_smoke_test failed on Eoan zVM Status in Stress-ng: Invalid Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Eoan zVM node kernel03 Test hung at bad-altstack test. Reproducible rate: 4 out of 4 attempts 02:36:12 DEBUG| [stdout] aiol STARTING 02:36:17 DEBUG| [stdout] aiol RETURNED 0 02:36:17 DEBUG| [stdout] aiol PASSED 02:36:17 DEBUG| [stdout] bad-altstack STARTING + ARCHIVE=/var/lib/jenkins/jobs/smoke__E_s390x.zVM-generic__using_kernel03__for_kernel/builds/3/archive + scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -r ubuntu@kernel03:kernel-test-results /var/lib/jenkins/jobs/smoke__E_s390x.zVM-generic__using_kernel03__for_kernel/builds/3/archive dmesg only shows: [ 102.352136] Adding 1048572k swap on /home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng/swap.img. Priority:-3 extents:95 across:26763272k SSFS [ 122.402895] NET: Registered protocol family 38 It looks like this is caused by OOM issue, x3270 console flushed with OOM error messages. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-41-generic 5.3.0-41.33 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.4 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Feb 20 06:06:04 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/mapper/kl03vg01-kl03root crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-5.3.0-41-generic N/A linux-backports-modules-5.3.0-41-generic N/A linux-firmware1.183.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-30 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1863989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Oh, I had the URL wrong (archive.ubuntu instead of ports...). Installed .1019 kernel, headers, etc... issue persists with the new kernel - dmesg attached. ** Attachment added: "dmesg-1019.txt" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5330924/+files/dmesg-1019.txt -- 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/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) Status in linux-raspi2 package in Ubuntu: Incomplete Bug description: Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and network load. Happened a few times (every time) when I tried to download a gparted zip release (~350 MiB) directly to the SD card, and then finally when I tried to scp the finished download from a desktop onto RPi's card. Didn't collect information when it happened, but kept a copy of kern.log. Here's the relevant part: Feb 4 23:42:59 rpi3 kernel: [ 571.878359] [ cut here ] Feb 4 23:42:59 rpi3 kernel: [ 571.878420] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Feb 4 23:42:59 rpi3 kernel: [ 571.878550] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878557] Modules linked in: sit tunnel4 ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 Feb 4 23:42:59 rpi3 kernel: [ 571.878774] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu Feb 4 23:42:59 rpi3 kernel: [ 571.878781] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) Feb 4 23:42:59 rpi3 kernel: [ 571.878789] pstate: 6045 (nZCv daif +PAN -UAO) Feb 4 23:42:59 rpi3 kernel: [ 571.878800] pc : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878807] lr : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878812] sp : 1001bd60 Feb 4 23:42:59 rpi3 kernel: [ 571.878817] x29: 1001bd60 x28: 0140 Feb 4 23:42:59 rpi3 kernel: [ 571.878827] x27: x26: Feb 4 23:42:59 rpi3 kernel: [ 571.878836] x25: 8ecbefa4e000 x24: 305e0f529018 Feb 4 23:42:59 rpi3 kernel: [ 571.878845] x23: x22: 0001 Feb 4 23:42:59 rpi3 kernel: [ 571.878853] x21: 8ecbefa4e480 x20: 305e0f807000 Feb 4 23:42:59 rpi3 kernel: [ 571.878862] x19: x18: Feb 4 23:42:59 rpi3 kernel: [ 571.878871] x17: 10fd8218 x16: 305e0e30efb8 Feb 4 23:42:59 rpi3 kernel: [ 571.878879] x15: 8ecbf922a290 x14: Feb 4 23:42:59 rpi3 kernel: [ 571.87] x13: x12: 305e0f944000 Feb 4 23:42:59 rpi3 kernel: [ 571.878897] x11: 305e0f82d000 x10: Feb 4 23:42:59 rpi3 kernel: [ 571.878905] x9 : 0004 x8 : 017f Feb 4 23:42:59 rpi3 kernel: [ 571.878913] x7 : x6 : 0001 Feb 4 23:42:59 rpi3 kernel: [ 571.878921] x5 : x4 : 0008 Feb 4 23:42:59 rpi3 kernel: [ 571.878929] x3 : 305e0ee15750 x2 : 0004 Feb 4 23:42:59 rpi3 kernel: [ 571.878937] x1 : 6abb42c67c954600 x0 : Feb 4 23:42:59 rpi3 kernel: [ 571.878946] Call trace: Feb 4 23:42:59 rpi3 kernel: [ 571.878955] dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878967] call_timer_fn+0x3c/0x178 Feb 4 23:42:59 rpi3 kernel: [ 571.878977] __run_timers.part.0+0x200/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878985] run_timer_softirq+0x40/0x78 Feb 4 23:42:59 rpi3 kernel: [ 571.878995] __do_softirq+0x168/0x384 Feb 4 23:42:59 rpi3 kernel: [ 571.879007] irq_exit+0xb0/0xe8 Feb 4 23:42:59 rpi3 kernel: [ 571.879020] __handle_domain_irq+0x70/0xc0 Feb 4 23:42:59 rpi3 kernel: [ 571.879028] bcm2836_arm_irqchip_handle_irq+0x74/0xe0 Feb 4 23:42:59 rpi3 kernel: [ 571.879037] el1_irq+0x108/0x200 Feb 4 23:42:59 rpi3 kernel: [ 571.879050] arch_cpu_idle+0
[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
I'm ready to put the workaround to ec2-hibinit-agent, but it would be much better if the kernel could be fixed. ** Also affects: ec2-hibinit-agent (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: ec2-hibinit-agent (Ubuntu Focal) Status: New => In Progress -- 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/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Bionic: New Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: New Status in linux-aws source package in Eoan: New Status in ec2-hibinit-agent source package in Focal: In Progress Status in linux-aws source package in Focal: New Bug description: The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
In the proposed workaround there is a 15s sleep before the module reload. Is it needed and if so is this a lowest safe choice? -- 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/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Bionic: New Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: New Status in linux-aws source package in Eoan: New Status in ec2-hibinit-agent source package in Focal: In Progress Status in linux-aws source package in Focal: New Bug description: The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862215] Re: Failure to boot with LVM + encrypted root disk
Running cat /proc/modules gives: i915 i2c_algo_bit crc32_pclmul drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse sdhci_pci cqhci sdhci lpc_ich i2c_i801 ahci drm libahci e1000e wmi video (There may be a transcription error or 2 in there, so photo is at http://ovh.themcphails.uk/index.php/s/t94YwXRktqrYHsb ) Certainly no evidence of dm-crypt or similar. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1862215 Title: Failure to boot with LVM + encrypted root disk Status in linux-5.4 package in Ubuntu: Confirmed Bug description: Attempting to boot linux-image-5.4.0-12-generic and it failed to find my LVM VG. -9 worked without issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.12.15 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 17:20:45 2020 InstallationDate: Installed on 2016-11-01 (1192 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-5.4 UpgradeStatus: Upgraded to focal on 2020-01-20 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1862215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864392] Re: WiFi not working
apport information ** Tags added: apport-collected ** Description changed: No WiFi APs are detected. It's like the driver doesn't recognize the hardware. I tried reinstalling it, but it didn't work. Please fix this ASAP. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: backport-iwlwifi-dkms 7906-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 23 18:43:16 2020 InstallationDate: Installed on 2020-01-19 (35 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: backport-iwlwifi-dkms UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.4 + Architecture: amd64 + CurrentDesktop: KDE + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2020-01-19 (37 days ago) + InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Package: linux + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 + Tags: eoan + Uname: Linux 5.3.0-29-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1864392/+attachment/5330968/+files/Dependencies.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/1864392 Title: WiFi not working Status in backport-iwlwifi-dkms package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No WiFi APs are detected. It's like the driver doesn't recognize the hardware. I tried reinstalling it, but it didn't work. Please fix this ASAP. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: backport-iwlwifi-dkms 7906-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 23 18:43:16 2020 InstallationDate: Installed on 2020-01-19 (35 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: backport-iwlwifi-dkms UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1864392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864392] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1864392/+attachment/5330970/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864392 Title: WiFi not working Status in backport-iwlwifi-dkms package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No WiFi APs are detected. It's like the driver doesn't recognize the hardware. I tried reinstalling it, but it didn't work. Please fix this ASAP. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: backport-iwlwifi-dkms 7906-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 23 18:43:16 2020 InstallationDate: Installed on 2020-01-19 (35 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: backport-iwlwifi-dkms UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1864392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864392] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1864392/+attachment/5330969/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864392 Title: WiFi not working Status in backport-iwlwifi-dkms package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No WiFi APs are detected. It's like the driver doesn't recognize the hardware. I tried reinstalling it, but it didn't work. Please fix this ASAP. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: backport-iwlwifi-dkms 7906-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 23 18:43:16 2020 InstallationDate: Installed on 2020-01-19 (35 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: backport-iwlwifi-dkms UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1864392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864392] Re: WiFi not working
apport information ** Description changed: No WiFi APs are detected. It's like the driver doesn't recognize the hardware. I tried reinstalling it, but it didn't work. Please fix this ASAP. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: backport-iwlwifi-dkms 7906-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 23 18:43:16 2020 InstallationDate: Installed on 2020-01-19 (35 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: backport-iwlwifi-dkms UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.4 + Architecture: amd64 + CurrentDesktop: KDE + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2020-01-19 (37 days ago) + InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Package: linux + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 + Tags: eoan + Uname: Linux 5.3.0-29-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1864392/+attachment/5330984/+files/Dependencies.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/1864392 Title: WiFi not working Status in backport-iwlwifi-dkms package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No WiFi APs are detected. It's like the driver doesn't recognize the hardware. I tried reinstalling it, but it didn't work. Please fix this ASAP. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: backport-iwlwifi-dkms 7906-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 23 18:43:16 2020 InstallationDate: Installed on 2020-01-19 (35 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: backport-iwlwifi-dkms UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1864392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@list
[Kernel-packages] [Bug 1864392] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1864392/+attachment/5330985/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864392 Title: WiFi not working Status in backport-iwlwifi-dkms package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No WiFi APs are detected. It's like the driver doesn't recognize the hardware. I tried reinstalling it, but it didn't work. Please fix this ASAP. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: backport-iwlwifi-dkms 7906-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 23 18:43:16 2020 InstallationDate: Installed on 2020-01-19 (35 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: backport-iwlwifi-dkms UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1864392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864392] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1864392/+attachment/5330986/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864392 Title: WiFi not working Status in backport-iwlwifi-dkms package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No WiFi APs are detected. It's like the driver doesn't recognize the hardware. I tried reinstalling it, but it didn't work. Please fix this ASAP. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: backport-iwlwifi-dkms 7906-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 23 18:43:16 2020 InstallationDate: Installed on 2020-01-19 (35 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: backport-iwlwifi-dkms UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1864392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860320 Title: [hns3-0120]pad the short frame before sending to the hardware Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Bug description: The hardware can not handle short frames below or equal to 32 bytes. [Impact] The system may hang or endless event log in /var/log/syslog [Fix] Cherry-pick or backport the upstream fix 36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before sending to the hardware [Test Case] Send a frame less than 33 bytes. [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] The hardware can not handle short frames below or equal to 32 bytes according to the hardware user manual, and it will trigger a RAS error when the frame's length is below 33 bytes. [Steps to Reproduce] 1.send a frame less than 33 bytes. [Actual Results] a RAS occurs [Expected Results] no RAS [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] pads the SKB when skb->len is below 33 bytes before sending it to hardware. net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
this seemed to "just work" for me. http://paste.ubuntu.com/p/93dWDPZfZT/ -- 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: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed 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 1834875] Re: cloud-init growpart race with udev
** Merge proposal linked: https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/+merge/379851 -- 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: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed 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
Re: [Kernel-packages] [Bug 1834875] Re: cloud-init growpart race with udev
On Tue, Feb 25, 2020 at 2:35 PM Scott Moser wrote: > this seemed to "just work" for me. > http://paste.ubuntu.com/p/93dWDPZfZT/ Ah, I didn't check that there was an existing ubuntu/devel branch. Sorry. I've pushed a MR here: https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/+merge/379851 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1834875 > > Title: > cloud-init growpart race with udev > > To manage notifications about this bug go to: > https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions > -- 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: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed 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 1863339] Re: bionic/linux-oracle: 4.15.0-1034.37 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1863339 Title: bionic/linux-oracle: 4.15.0-1034.37 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Tuesday, 25. February 2020 09:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1863337 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863337] Re: xenial/linux-oracle: 4.15.0-1034.37~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1863337 Title: xenial/linux-oracle: 4.15.0-1034.37~16.04.1 -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: 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in 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: 1863339 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Tuesday, 25. February 2020 10:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864710] [NEW] Eoan update: upstream stable patchset 2020-02-25
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: upstream stable patchset 2020-02-25 Ported from the following upstream stable releases: v4.19.100, v5.4.16 from git://git.kernel.org/ firestream: fix memory leaks gtp: make sure only SOCK_DGRAM UDP sockets are accepted ipv6: sr: remove SKB_GSO_IPXIP6 on End.D* actions net: bcmgenet: Use netif_tx_napi_add() for TX NAPI net: cxgb3_main: Add CAP_NET_ADMIN check to CHELSIO_GET_MEM net: ip6_gre: fix moving ip6gre between namespaces net, ip6_tunnel: fix namespaces move net, ip_tunnel: fix namespaces move net: rtnetlink: validate IFLA_MTU attribute in rtnl_create_link() net_sched: fix datalen for ematch net-sysfs: Fix reference count leak in rx|netdev_queue_add_kobject net-sysfs: fix netdev_queue_add_kobject() breakage net-sysfs: Call dev_hold always in netdev_queue_add_kobject net-sysfs: Call dev_hold always in rx_queue_add_kobject net-sysfs: Fix reference count leak net: usb: lan78xx: Add .ndo_features_check Revert "udp: do rmem bulk free even if the rx sk queue is empty" tcp_bbr: improve arithmetic division in bbr_update_bw() tcp: do not leave dangling pointers in tp->highest_sack tun: add mutex_unlock() call and napi.skb clearing in tun_get_user() afs: Fix characters allowed into cell names hwmon: (adt7475) Make volt2reg return same reg as reg2volt input hwmon: (core) Do not use device managed functions for memory allocations PCI: Mark AMD Navi14 GPU rev 0xc5 ATS as broken tracing: trigger: Replace unneeded RCU-list traversals Input: keyspan-remote - fix control-message timeouts Revert "Input: synaptics-rmi4 - don't increment rmiaddr for SMBus transfers" ARM: 8950/1: ftrace/recordmcount: filter relocation types mmc: tegra: fix SDR50 tuning override mmc: sdhci: fix minimum clock rate for v3 controller Input: pm8xxx-vib - fix handling of separate enable register Input: sur40 - fix interface sanity checks Input: gtco - fix endpoint sanity check Input: aiptek - fix endpoint sanity check Input: pegasus_notetaker - fix endpoint sanity check Input: sun4i-ts - add a check for devm_thermal_zone_of_sensor_register netfilter: nft_osf: add missing check for DREG attribute hwmon: (nct7802) Fix voltage limits to wrong registers scsi: RDMA/isert: Fix a recently introduced regression related to logout tracing: xen: Ordered comparison of function pointers do_last(): fetch directory ->i_mode and ->i_uid before it's too late net/sonic: Add mutual exclusion for accessing shared state net/sonic: Clear interrupt flags immediately net/sonic: Use MMIO accessors net/sonic: Fix interface error stats collection net/sonic: Fix receive buffer handling net/sonic: Avoid needless receive descriptor EOL flag updates net/sonic: Improve receive descriptor status flag check net/sonic: Fix receive buffer replenishment net/sonic: Quiesce SONIC before re-initializing descriptor memory net/sonic: Fix command register usage net/sonic: Fix CAM initialization net/sonic: Prevent tx watchdog timeout tracing: Fix histogram code when expression has same var as value libertas: Fix two buffer overflows at parsing bss descriptor media: v4l2-ioctl.c: zero reserved fields for S/TRY_FMT netfilter: ipset: use bitmap infrastructure completely netfilter: nf_tables: add __nft_chain_type_get() net/x25: fix nonblocking connect drivers/base/node.c: simplify unregister_memory_block_under_nodes() net_sched: use validated TCA_KIND attribute in tc_new_tfilter() airo: Fix possible info leak in AIROOLDIOCTL/SIOCDEVPRIVATE airo: Add missing CAP_NET_ADMIN check in AIROOLDIOCTL/SIOCDEVPRIVATE mlxsw: spectrum_acl: Fix use-after-free during reload fou: Fix IPv6 netlink policy net/mlx5: Fix lowest FDB pool size net/mlx5: Update the list of the PCI supported devices ipv4: Detect rollover in specific fib table dump ceph: hold extra reference to r_parent over life of request drm/i915: Align engine->uabi_class/instance with i915_drm.h PM: hibernate: fix crashes with init_on_free=1 powerpc/mm/hash: Fix sharing context ids between kernel & userspace powerpc/xive: Discard ESB load value when interrupt is invalid XArray: Fix infinite loop with entry at ULONG_MAX XArray: Fix xa_find_after with multi-index entries XArray: Fix xas_find returning too many entries iommu/vt-d: Call __dmar_remove_one_dev_info with valid pointer mmc: sdhci_am654: Remove Inverted Write Protect flag mmc: sdhci_am654: Reset Command and Data line after tuning mlxsw: switchx2: Do not modify cloned SKBs during xmit net/tls: fix async operation lib: Reduce user_access_begin() boundaries in strncpy_from_
[Kernel-packages] [Bug 1864710] Re: Eoan update: upstream stable patchset 2020-02-25
** 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: + upstream stable patchset 2020-02-25 -upstream stable patchset 2020-02-25 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.19.100, v5.4.16 + + from git://git.kernel.org/ + + firestream: fix memory leaks + gtp: make sure only SOCK_DGRAM UDP sockets are accepted + ipv6: sr: remove SKB_GSO_IPXIP6 on End.D* actions + net: bcmgenet: Use netif_tx_napi_add() for TX NAPI + net: cxgb3_main: Add CAP_NET_ADMIN check to CHELSIO_GET_MEM + net: ip6_gre: fix moving ip6gre between namespaces + net, ip6_tunnel: fix namespaces move + net, ip_tunnel: fix namespaces move + net: rtnetlink: validate IFLA_MTU attribute in rtnl_create_link() + net_sched: fix datalen for ematch + net-sysfs: Fix reference count leak in rx|netdev_queue_add_kobject + net-sysfs: fix netdev_queue_add_kobject() breakage + net-sysfs: Call dev_hold always in netdev_queue_add_kobject + net-sysfs: Call dev_hold always in rx_queue_add_kobject + net-sysfs: Fix reference count leak + net: usb: lan78xx: Add .ndo_features_check + Revert "udp: do rmem bulk free even if the rx sk queue is empty" + tcp_bbr: improve arithmetic division in bbr_update_bw() + tcp: do not leave dangling pointers in tp->highest_sack + tun: add mutex_unlock() call and napi.skb clearing in tun_get_user() + afs: Fix characters allowed into cell names + hwmon: (adt7475) Make volt2reg return same reg as reg2volt input + hwmon: (core) Do not use device managed functions for memory allocations + PCI: Mark AMD Navi14 GPU rev 0xc5 ATS as broken + tracing: trigger: Replace unneeded RCU-list traversals + Input: keyspan-remote - fix control-message timeouts + Revert "Input: synaptics-rmi4 - don't increment rmiaddr for SMBus transfers" + ARM: 8950/1: ftrace/recordmcount: filter relocation types + mmc: tegra: fix SDR50 tuning override + mmc: sdhci: fix minimum clock rate for v3 controller + Input: pm8xxx-vib - fix handling of separate enable register + Input: sur40 - fix interface sanity checks + Input: gtco - fix endpoint sanity check + Input: aiptek - fix endpoint sanity check + Input: pegasus_notetaker - fix endpoint sanity check + Input: sun4i-ts - add a check for devm_thermal_zone_of_sensor_register + netfilter: nft_osf: add missing check for DREG attribute + hwmon: (nct7802) Fix voltage limits to wrong registers + scsi: RDMA/isert: Fix a recently introduced regression related to logout + tracing: xen: Ordered comparison of function pointers + do_last(): fetch directory ->i_mode and ->i_uid before it's too late + net/sonic: Add mutual exclusion for accessing shared state + net/sonic: Clear interrupt flags immediately + net/sonic: Use MMIO accessors + net/sonic: Fix interface error stats collection + net/sonic: Fix receive buffer handling + net/sonic: Avoid needless receive descriptor EOL flag updates + net/sonic: Improve receive descriptor status flag check + net/sonic: Fix receive buffer replenishment + net/sonic: Quiesce SONIC before re-initializing descriptor memory + net/sonic: Fix command register usage + net/sonic: Fix CAM initialization + net/sonic: Prevent tx watchdog timeout + tracing: Fix histogram code when expression has same var as value + libertas: Fix two buffer overflows at parsing bss descriptor + media: v4l2-ioctl.c: zero reserved fields for S/TRY_FMT + netfilter: ipset: use bitmap infrastructure completely + netfilter: nf_tables: add __nft_chain_type_get() + net/x25: fix nonblocking connect + drivers/base/node.c: simplify unregister_memory_block_under_nodes() + net_sched: use validated TCA_KIND attribute in tc_new_tfilter() + airo: Fix possible info leak in AIROOLDIOCTL/SIOCDEVPRIVATE + airo: Add missing CAP_NET_ADMIN check in AIROOLDIOCTL/SIOCDEVPRIVATE + mlxsw: spectrum_acl: Fix use-after-free during reload + fou: Fix IPv6 netlink policy + net/mlx5: Fix lowest FDB pool size + net/mlx5: Update the list of the PCI supported devices + ipv4: Detect rollover in specific fib table dump + ceph: hold extra reference to r_parent over
[Kernel-packages] [Bug 1864715] [NEW] linux-raspi2: -proposed tracker
Public bug reported: 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 -- replaces: bug 1863305 variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: Invalid ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-raspi2 (Ubuntu Bionic) Importance: Medium Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2020.02.17-2 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Bionic) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-security Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-updates Importance: Undecided => Medium ** Changed i
[Kernel-packages] [Bug 1864717] [NEW] linux-snapdragon: -proposed tracker
Public bug reported: 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 -- replaces: bug 1863310 variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: Invalid ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: linux-snapdragon (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-snapdragon (Ubuntu Bionic) Importance: Medium Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2020.02.17-2 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux-snapdragon (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-snapdragon (Ubuntu Bionic) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-security Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-updates Importance: Undecided => Medi
[Kernel-packages] [Bug 1863312] Re: bionic/linux-oem: 4.15.0-1074.84 -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: 1863350 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Tuesday, 25. February 2020 13:46 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1863312 Title: bionic/linux-oem: 4.15.0-1074.84 -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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1863350 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Tuesday, 25. February 2020 13:46 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/1863312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864715] Re: linux-raspi2: -proposed tracker
** Changed in: kernel-sru-workflow Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Bionic) Status: Confirmed => Invalid -- 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/1864715 Title: linux-raspi2: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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 -- replaces: bug 1863305 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864717] Re: linux-snapdragon: -proposed tracker
** Changed in: kernel-sru-workflow Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-snapdragon (Ubuntu Bionic) Status: Confirmed => Invalid -- 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/1864717 Title: linux-snapdragon: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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 -- replaces: bug 1863310 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864080] Re: focal/linux-aws: 5.4.0-1002.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => 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: 1864085 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Ready for Promote to Proposed - phase-changed: Monday, 24. February 2020 12:53 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 25. February 2020 21:26 UTC reason: - promote-to-proposed: Stalled -- ready for review + 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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1864080 Title: focal/linux-aws: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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 Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Focal: 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: 1864085 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Promote to Proposed phase-changed: Tuesday, 25. February 2020 21:26 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/1864080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864081] Re: focal/linux-azure: 5.4.0-1003.3 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => 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: 1864085 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Promote to Proposed - phase-changed: Monday, 24. February 2020 12:53 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 25. February 2020 21:31 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Pending -- package copied to Proposed signed:retry-needed 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/1864081 Title: focal/linux-azure: 5.4.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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 Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Focal: 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: 1864085 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Tuesday, 25. February 2020 21:31 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:retry-needed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864084] Re: focal/linux-oracle: 5.4.0-1003.3 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => 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: 1864085 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Ready for Promote to Proposed - phase-changed: Monday, 24. February 2020 13:06 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 25. February 2020 21:31 UTC reason: - promote-to-proposed: Stalled -- ready for review + 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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1864084 Title: focal/linux-oracle: 5.4.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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 Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle source package in Focal: 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: 1864085 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Tuesday, 25. February 2020 21:31 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/1864084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864717] Re: linux-snapdragon: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live ** Tags removed: kernel-sru-cycle-2020.02.17-2 -- 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/1864717 Title: linux-snapdragon: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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 -- replaces: bug 1863310 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864715] Re: linux-raspi2: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live ** Tags removed: kernel-sru-cycle-2020.02.17-2 -- 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/1864715 Title: linux-raspi2: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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 -- replaces: bug 1863305 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864083] Re: focal/linux-kvm: 5.4.0-1002.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => 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: 1864085 packages: main: linux-kvm meta: linux-meta-kvm - phase: Ready for Promote to Proposed - phase-changed: Monday, 24. February 2020 12:54 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 25. February 2020 21:41 UTC reason: - promote-to-proposed: Stalled -- ready for review + 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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1864083 Title: focal/linux-kvm: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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 Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Focal: 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: 1864085 packages: main: linux-kvm meta: linux-meta-kvm phase: Promote to Proposed phase-changed: Tuesday, 25. February 2020 21:41 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/1864083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864726] [NEW] linux-raspi2: -proposed tracker
Public bug reported: 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 -- replaces: bug 1863305 variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-raspi2 (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2020.02.17-2 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Bionic) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-security Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-updates Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-upda
[Kernel-packages] [Bug 1864732] [NEW] linux-aws-fips: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864734 replaces: bug 1863317 variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-signing-to-proposed Importance: Medium Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2020.02.17-2 kernel-sru-derivative-of-1864734 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-signing-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided =>
