[Kernel-packages] [Bug 1820557] Re: Chelsio T5/T6 kernel modules missing in 4.18.0-1013
Mark as "Incomplete" for question in comment #2. ** Changed in: linux-azure (Ubuntu) Status: New => Incomplete -- 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/1820557 Title: Chelsio T5/T6 kernel modules missing in 4.18.0-1013 Status in linux-azure package in Ubuntu: Incomplete Bug description: Installed the linux-azure package, and the VF Chelsio T520-CR device became unclaimed. When into the path '/lib/modules/4.18.0-1013-azure/kernel/drivers/net/ethernet/' and was a little surprised to not see a Chelsio folder. Has Chelsio been removed from Ubuntu support in the linux-azure package? Test platform: Hyper-V 2019 Server Role with Ubuntu Server 18.04.2(HVE) guest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1820557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817740] Re: Disable ZFS
** Changed in: linux-azure (Ubuntu) Status: New => Invalid -- 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/1817740 Title: Disable ZFS Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Fix Released Bug description: [Impact] ZFS was not supposed to be enabled on linux-azure for trusty from the start. There is no ZFS tooling in trusty anyway. [Regression potential] Some user will complain they cannot mount their ZFS now with that kernel. They can just install a different kernel then, as this one was not supposed to be used like that. [Test case] zfs is disabled on the files after copy-files is run. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1817740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838601] Re: kernel update 5.0.0-23 breaks scroll mouse in xorg
Yes, but it's essentially the same one as linux in Disco. -- 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/1838601 Title: kernel update 5.0.0-23 breaks scroll mouse in xorg Status in linux package in Ubuntu: Confirmed Bug description: Just updated 18.04 to kernel 5.0.0-23 and scrolling with mouse wheel does not work or works very slowly. Mouse is Microsoft Wireless Optical Mouse 3000 connected via USB to wireless receiver. Rebooting system into kernel 4.18.0-25 and everything works correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Wed Jul 31 22:53:44 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-24-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2019-04-05 (118 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 2347GBU ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=c840a596-f648-4a82-98f4-70137859c633 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET73WW (2.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GBU dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2347GBU:pvrThinkPadT430:rvnLENOVO:rn2347GBU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GBU dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791794] Re: linux-azure: build and include the tcm_loop module to the main kernel package
** Changed in: linux-azure (Ubuntu) Status: In Progress => Invalid -- 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/1791794 Title: linux-azure: build and include the tcm_loop module to the main kernel package Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Fix Released Bug description: Azure users rely on the tcm_loop module. Since linux-azure doesn't install the extra package by default, the module should be included to the main package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1791794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812123] Re: Upstream Commits Needed for DPDK on Azure
** Changed in: linux-azure (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1812123
Title:
Upstream Commits Needed for DPDK on Azure
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Bug description:
The following two patches are related to multi-queue. They are needed
in the linux-azure kernels for DPDK to work properly on Azure.
b5679cebf780 ("vmbus: fix subchannel removal")
5e3c420dcca5 ("uio_hv_generic: set callbacks on open")
Both commits have also been cc'd to upstream stable. Commit 5e3c420dcca5 is
in mainline as of v4.20. Commit b5679cebf780 is still in linux-next.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1812123/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706165] Re: linux-azure: disable unused modules in the -extra package
** Changed in: linux-azure (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-azure (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1706165 Title: linux-azure: disable unused modules in the -extra package Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Fix Released Bug description: SRU Justification: Impact: Currently the linux-image-extra-*-azure package contains many unused modules. Fix: Remove modules that are not use in Azure. Testcase: not applied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1706165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698367] Re: Rebase linux-azure to 4.11
** Changed in: linux-azure (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-azure (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1698367 Title: Rebase linux-azure to 4.11 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Fix Released Bug description: SRU Justification: Impact: The support for Hyper-V and Azure is under heavy development and due to this reason it's necessary to keep the Azure kernel as closest to upstream as possible in order to get access to the latest features and bug fixes. Fix: Rebase the Azure kernel to the latest 4.11 artful kernel in proposed. Testcase: It's necessary to run a smoke test and check if any performance regression was caused. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1698367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1699157] Re: Re-enable -extra package for linux-azure
** Changed in: linux-azure (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-azure (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1699157 Title: Re-enable -extra package for linux-azure Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Fix Released Bug description: SRU Justification: Impact: It's necessary to ship some drivers that will not be included by default. Fix: Re-enable the -extra package for linux-azure. Testcase: The -extra package should be built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1699157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838610] [NEW] The 3.13 kernel for Precise ESM does not provide the expected version number
Public bug reported: The linux-generic-lts-trusty meta package on Precise will give you: linux-base linux-headers-3.13.0-172 linux-headers-3.13.0-172-generic linux-headers-generic-lts-trusty linux-image-3.13.0-172-generic linux-image-generic-lts-trusty linux-modules-3.13.0-172-generic And the kernel version returned from uname -a shows: Linux precise-testing 3.13.0-172-generic #1-Ubuntu SMP Sat Jul 6 10:46:56 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux This is breaking the automation as we're expecting the kernel version: 3.13.0-172.223~12.04.1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: trusty -- 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/1838610 Title: The 3.13 kernel for Precise ESM does not provide the expected version number Status in linux package in Ubuntu: Incomplete Bug description: The linux-generic-lts-trusty meta package on Precise will give you: linux-base linux-headers-3.13.0-172 linux-headers-3.13.0-172-generic linux-headers-generic-lts-trusty linux-image-3.13.0-172-generic linux-image-generic-lts-trusty linux-modules-3.13.0-172-generic And the kernel version returned from uname -a shows: Linux precise-testing 3.13.0-172-generic #1-Ubuntu SMP Sat Jul 6 10:46:56 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux This is breaking the automation as we're expecting the kernel version: 3.13.0-172.223~12.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838610] 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 1838610 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 ** Tags added: trusty -- 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/1838610 Title: The 3.13 kernel for Precise ESM does not provide the expected version number Status in linux package in Ubuntu: Incomplete Bug description: The linux-generic-lts-trusty meta package on Precise will give you: linux-base linux-headers-3.13.0-172 linux-headers-3.13.0-172-generic linux-headers-generic-lts-trusty linux-image-3.13.0-172-generic linux-image-generic-lts-trusty linux-modules-3.13.0-172-generic And the kernel version returned from uname -a shows: Linux precise-testing 3.13.0-172-generic #1-Ubuntu SMP Sat Jul 6 10:46:56 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux This is breaking the automation as we're expecting the kernel version: 3.13.0-172.223~12.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838533] Re: Bionic linux 4.15.0-56.62 fails to build with CONFIG_NVM disabled
** Changed in: linux-azure (Ubuntu Xenial)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1838533
Title:
Bionic linux 4.15.0-56.62 fails to build with CONFIG_NVM disabled
Status in linux package in Ubuntu:
Invalid
Status in linux-azure package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Invalid
Status in linux-azure source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux-azure source package in Bionic:
Invalid
Bug description:
[Impact]
When compiling bionic linux 4.15.0-56.62 with CONFIG_NVM disabled, it
fails with:
make[5]: *** [drivers/nvme/host/core.o] Error 1
make[5]: *** Waiting for unfinished jobs
In file included from
/tmp/kernel-kleber-57dc2e6-NQe1/build/drivers/nvme/host/multipath.c:15:0:
/tmp/kernel-kleber-57dc2e6-NQe1/build/drivers/nvme/host/nvme.h: In function
'nvme_nvm_register_sysfs':
/tmp/kernel-kleber-57dc2e6-NQe1/build/drivers/nvme/host/nvme.h:502:6: error:
'ctrl' undeclared (first use in this function)
if (ctrl->subsys->cmic & (1 << 3))
^
/tmp/kernel-kleber-57dc2e6-NQe1/build/drivers/nvme/host/nvme.h:502:6: note:
each undeclared identifier is reported only once for each function it appears in
[Fix]
The culprit seems to be this patch:
commit 993f70b886c0062fb5ec7c3c556d074bb3380b9d
Author: Christoph Hellwig
Date: Tue Nov 20 16:57:54 2018 +0100
nvme: warn when finding multi-port subsystems without multipathing
enabled
BugLink: https://bugs.launchpad.net/bugs/1837161
[ Upstream commit 14a1336e6fff47dd1028b484d6c802105c58e2ee ]
[...]
--- a/drivers/nvme/host/nvme.h
+++ b/drivers/nvme/host/nvme.h
@@ -499,6 +499,9 @@ static inline int nvme_nvm_register(struct nvme_ns *ns,
char *disk_name,
static inline void nvme_nvm_unregister(struct nvme_ns *ns) {};
static inline int nvme_nvm_register_sysfs(struct nvme_ns *ns)
{
+ if (ctrl->subsys->cmic & (1 << 3))
+ dev_warn(ctrl->device,
+"Please enable CONFIG_NVME_MULTIPATH for full support of multi-port
devices.\n");
return 0;
}
which is adding the new lines to a different function than the
original upstream commit:
--- a/drivers/nvme/host/nvme.h
+++ b/drivers/nvme/host/nvme.h
@@ -531,6 +531,9 @@ static inline void nvme_mpath_check_last_path(struct
nvme_ns *ns)
static inline int nvme_mpath_init(struct nvme_ctrl *ctrl,
struct nvme_id_ctrl *id)
{
+ if (ctrl->subsys->cmic & (1 << 3))
+ dev_warn(ctrl->device,
+"Please enable CONFIG_NVME_MULTIPATH for full support of multi-port
devices.\n");
return 0;
}
This patch was probably wrongly backported for bug #1837161 from
linux-4.19.y stable and not needed since bionic/linux lacks commit
0d0b660f214d (nvme: add ANA support) which introduced
nvme_mpath_init(). The fix is to revert this patch.
[Test Case]
Disabled kernel config CONFIG_NVM and compile the kernel.
[Regression Potential]
Low. The patch was wrongly backported and can be safely reverted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838533/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838395] Re: disco/linux: 5.0.0-24.25 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => 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/1838395 Title: disco/linux: 5.0.0-24.25 -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 package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838393 (bionic/linux-hwe), bug 1838398 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837565 (linux-aws), bug 1837567 (linux-azure), bug 1837571 (linux-gcp), bug 1837572 (linux-kvm), bug 1837573 (linux-snapdragon) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Thursday, 01. August 2019 06:40 UTC reason: promote-to-proposed: Pending -- package copies requested to Proposed lrm:missing,meta:missing,signed:missing trackers: bionic/linux-hwe: bug 1838393 bionic/linux-oem-osp1: bug 1838398 disco/linux-aws: bug 1837565 disco/linux-azure: bug 1837567 disco/linux-gcp: bug 1837571 disco/linux-kvm: bug 1837572 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836202] Re: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker
*** This bug is a duplicate of bug 1837569 *** https://bugs.launchpad.net/bugs/1837569 ** This bug has been marked a duplicate of bug 1837569 bionic/linux-gke-5.0: 5.0.0-1012.12~18.04.2 -proposed tracker -- 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/1836202 Title: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836201 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834891 packages: main: linux-gke-5.0 meta: linux-meta-gke-5.0 signed: linux-signed-gke-5.0 phase: Holding before Release phase-changed: Tuesday, 23. July 2019 09:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- Nvidia objects not found -- current-driver-5.0.0-1011-gke-d1809-0-amd64 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838575] Re: passthrough devices cause >17min boot delay
Summary: As I mentioned before (on the other bug that I referred). The problem is that with a PT device it needs to reset and map the VDIO devices. So with >0 PT devices attached it needs an init that scales with memory size of the guest (see my fast results with PT but small guest memory). As I outlined before the "fix" for that is either: - (admin) use Huge pages (1G if possible) for the very huge guest which will make this way more efficient. - (kernel development) get the kernel to use more cores for this initialization (currently 1) Last time we disussed this Nvidia said they consider 1G Hugepages as recommended setup for huge guests (due to the benefits). But not for guests in general (due to the complexity managing the memory). I don't know where it ended, btu I expect it to be in some guidelines. That is why I wondered about th elack of hueg pages in the spec to test qemu passthrough perf if you remember. I don't think there is much more qemu can do at this point (at least I'd not know), but we can use this re-discovery of this issue as a chance. If you want to dive (or ask one of your teammates) into the kernel side to check if it could be made multi-cpu initialization for better scaling. I'm adding a kernel task for your consideration. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: qemu (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: qemu (Ubuntu) Status: Confirmed => 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/1838575 Title: passthrough devices cause >17min boot delay Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Adding passthrough devices to a guest introduces a boot delay of > 17 minutes. During this time libvirt reports the guest to be "paused". The delay does not seem to scale with the # of hostdevs - that is, 1 hostdev causes about a 17min delay, while 16 only bumps that up to ~18min. Removing all hostdevs avoids the delay. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838395] Re: disco/linux: 5.0.0-24.25 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838393 (bionic/linux-hwe), bug 1838398 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837565 (linux-aws), bug 1837567 (linux-azure), bug 1837571 (linux-gcp), bug 1837572 (linux-kvm), bug 1837573 (linux-snapdragon) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Thursday, 01. August 2019 06:40 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Pending -- package copies requested to Proposed lrm:missing,meta:missing,signed:missing trackers: bionic/linux-hwe: bug 1838393 bionic/linux-oem-osp1: bug 1838398 disco/linux-aws: bug 1837565 disco/linux-azure: bug 1837567 disco/linux-gcp: bug 1837571 disco/linux-kvm: bug 1837572 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838393 (bionic/linux-hwe), bug 1838398 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837565 (linux-aws), bug 1837567 (linux-azure), bug 1837571 (linux-gcp), bug 1837572 (linux-kvm), bug 1837573 (linux-snapdragon) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Thursday, 01. August 2019 06:40 UTC reason: - promote-to-proposed: Pending -- package copies requested to Proposed lrm:missing,meta:missing,signed:missing + promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-hwe: bug 1838393 bionic/linux-oem-osp1: bug 1838398 disco/linux-aws: bug 1837565 disco/linux-azure: bug 1837567 disco/linux-gcp: bug 1837571 disco/linux-kvm: bug 1837572 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 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/1838395 Title: disco/linux: 5.0.0-24.25 -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 package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838393 (bionic/linux-hwe), bug 1838398 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837565 (linux-aws), bug 1837567 (linux-azure), bug 1837571 (linux-gcp), bug 1837572 (linux-kvm), bug 1837573 (linux-snapdragon) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Thursday, 01. August 2019 06:40 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-hwe: bug 1838393 bionic/linux-oem-osp1: bug 1838398 disco/linux-aws: bug 1837565 disco/linux-azure: bug 1837567 disco/linux-gcp: bug 1837571 disco/linux-kvm: bug 1837572 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838395/+subscriptions -- Ma
[Kernel-packages] [Bug 1837563] Re: disco/linux-raspi2: 5.0.0-1014.14 -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) => Łukasz Zemczak (sil2100) -- 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/1837563 Title: disco/linux-raspi2: 5.0.0-1014.14 -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-meta 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Thursday, 01. August 2019 08:25 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/1837563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838395] Re: disco/linux: 5.0.0-24.25 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838393 (bionic/linux-hwe), bug 1838398 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837565 (linux-aws), bug 1837567 (linux-azure), bug 1837571 (linux-gcp), bug 1837572 (linux-kvm), bug 1837573 (linux-snapdragon) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Thursday, 01. August 2019 06:40 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-hwe: bug 1838393 bionic/linux-oem-osp1: bug 1838398 disco/linux-aws: bug 1837565 disco/linux-azure: bug 1837567 disco/linux-gcp: bug 1837571 disco/linux-kvm: bug 1837572 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 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/1838395 Title: disco/linux: 5.0.0-24.25 -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 package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838393 (bionic/linux-hwe), bug 1838398 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837565 (linux-aws), bug 1837567 (linux-azure), bug 1837571 (linux-gcp), bug 1837572 (linux-kvm), bug 1837573 (linux-snapdragon) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Thursday, 01. August 2019 06:40 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-hwe: bug 1838393 bionic/linux-oem-osp1: bug 1838398 disco/linux-aws: bug 1837565 disco/linux-azure: bug 1837567 disco/linux-gcp: bug 1837571 disco/linux-kvm: bug 1837572 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837563] Re: disco/linux-raspi2: 5.0.0-1014.14 -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: 1838395 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 31. July 2019 21:37 UTC + phase: Promote to Proposed + phase-changed: Thursday, 01. August 2019 08:25 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-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1837563 Title: disco/linux-raspi2: 5.0.0-1014.14 -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-meta 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Thursday, 01. August 2019 08:25 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/1837563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838590] Re: Update thermald to 1.9 release
Thanks Mario, I've been tracking the progress of thermald for some weeks now, so it's on my radar. I need to also roll in some packaging improvements, so I'll try and get this done some time next week. Colin ** Changed in: thermald (Ubuntu) Importance: Wishlist => Medium ** Changed in: thermald (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1838590 Title: Update thermald to 1.9 release Status in dptfxtract package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: The thermald 1.9 release was just tagged, and has potential to help quite a bit with platform performance on some newer platforms when run with kernel 5.3. It would be nice to update eoan to this new release. > - The major change in this version is the active power limits adjustment. This will be useful to improve performance on some newer platform. But this will will lead to increase in CPU and other temperatures. Hence this is important to run dptfxtract version 1.4.1 tool to get performance sensitive thermal limits (https://github.com/intel/dptfxtract/commits/v1.4.1). If the default configuration picked up by thermald is not optimal, user can select other less aggressive configuration. Refer to the README here https://github.com/intel/dptfxtract/blob/master/README.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dptfxtract/+bug/1838590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838610] Re: The 3.13 kernel for Precise ESM does not provide the expected version number
It does appear for other series we include the ~12.04.1 bit in the uname -a output: Linux kowtow-b64 5.0.0-21-generic #22~18.04.1-Ubuntu SMP Thu Jul 4 17:25:00 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux But it is likely best to use /proc/version_signature in preference to this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838610 Title: The 3.13 kernel for Precise ESM does not provide the expected version number Status in linux package in Ubuntu: Incomplete Bug description: The linux-generic-lts-trusty meta package on Precise will give you: linux-base linux-headers-3.13.0-172 linux-headers-3.13.0-172-generic linux-headers-generic-lts-trusty linux-image-3.13.0-172-generic linux-image-generic-lts-trusty linux-modules-3.13.0-172-generic And the kernel version returned from uname -a shows: Linux precise-testing 3.13.0-172-generic #1-Ubuntu SMP Sat Jul 6 10:46:56 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux This is breaking the automation as we're expecting the kernel version: 3.13.0-172.223~12.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838575] Re: passthrough devices cause >17min boot delay
Naive question: can we tweak the hugepage file settings at run time via /proc/sys/vm/nr_hugepages and not require the kernel parameters? -- 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/1838575 Title: passthrough devices cause >17min boot delay Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Adding passthrough devices to a guest introduces a boot delay of > 17 minutes. During this time libvirt reports the guest to be "paused". The delay does not seem to scale with the # of hostdevs - that is, 1 hostdev causes about a 17min delay, while 16 only bumps that up to ~18min. Removing all hostdevs avoids the delay. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837622] Re: xenial/linux-azure: 4.15.0-1053.58 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed 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 backports: bug 1837621 (trusty/linux-azure) derivatives: bug 1837619 (azure-kernel), bug 1837620 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1837626 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Packaging - phase-changed: Wednesday, 31. July 2019 13:15 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 01. August 2019 08:35 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait trackers: trusty/linux-azure: bug 1837621 xenial/linux-azure-edge: bug 1837620 xenial/linux-azure/azure-kernel: bug 1837619 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/1837622 Title: xenial/linux-azure: 4.15.0-1053.58 -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: 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837621 (trusty/linux-azure) derivatives: bug 1837619 (azure-kernel), bug 1837620 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1837626 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 01. August 2019 08:35 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait trackers: trusty/linux-azure: bug 1837621 xenial/linux-azure-edge: bug 1837620 xenial/linux-azure/azure-kernel: bug 1837619 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838575] Re: passthrough devices cause >17min boot delay
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) 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/1838575 Title: passthrough devices cause >17min boot delay Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Adding passthrough devices to a guest introduces a boot delay of > 17 minutes. During this time libvirt reports the guest to be "paused". The delay does not seem to scale with the # of hostdevs - that is, 1 hostdev causes about a 17min delay, while 16 only bumps that up to ~18min. Removing all hostdevs avoids the delay. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837621] Re: trusty/linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** 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: 1837622 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Packaging - phase-changed: Tuesday, 23. July 2019 15:24 UTC + phase: Ready for Packaging + phase-changed: Thursday, 01. August 2019 08:36 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified 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/1837621 Title: trusty/linux-azure: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-signing-to-proposed series: New 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New 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 -- kernel-stable-master-bug: 1837622 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Packaging phase-changed: Thursday, 01. August 2019 08:36 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838575] Re: passthrough devices cause >17min boot delay
You can do so even per-size via e.g. /sys/kernel/mm/hugepages/hugepages-1048576kB/nr_hugepages As discussed the later the allocation the higher the chance to fail, so re-check the sysfs file after each change if it actually got that much memory. The default size is only a boot time parameter. But you can specify explicit sizes in libvirt xml. -- 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/1838575 Title: passthrough devices cause >17min boot delay Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Adding passthrough devices to a guest introduces a boot delay of > 17 minutes. During this time libvirt reports the guest to be "paused". The delay does not seem to scale with the # of hostdevs - that is, 1 hostdev causes about a 17min delay, while 16 only bumps that up to ~18min. Removing all hostdevs avoids the delay. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837622] Re: xenial/linux-azure: 4.15.0-1053.58 -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 backports: bug 1837621 (trusty/linux-azure) derivatives: bug 1837619 (azure-kernel), bug 1837620 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1837626 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 01. August 2019 08:35 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait trackers: trusty/linux-azure: bug 1837621 xenial/linux-azure-edge: bug 1837620 xenial/linux-azure/azure-kernel: bug 1837619 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/1837622 Title: xenial/linux-azure: 4.15.0-1053.58 -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: 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837621 (trusty/linux-azure) derivatives: bug 1837619 (azure-kernel), bug 1837620 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1837626 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 01. August 2019 08:35 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait trackers: trusty/linux-azure: bug 1837621 xenial/linux-azure-edge: bug 1837620 xenial/linux-azure/azure-kernel: bug 1837619 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838613] [NEW] two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad
Public bug reported: After using the touchpad for a while, it suddenly believes that I'm doing a two-finger scroll, when I'm not. It makes the touchpad unusable : it's not possible to move the mouse anymore, vertical scrolling happens instead. I could not find an action that reliably gets me out of this mode (except reboot !). My workaround for now is to disable two-finger scrolling in "Config / Devices / Mouse & Touchpad", and enable "Edge scrolling" instead. I'm using Ubuntu 19.04 (Ubuntu 5.0.0-21.22-generic 5.0.15) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pcarbonn 1752 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 10:52:38 2019 InstallationDate: Installed on 2019-07-12 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: HP HP ZBook 15 G5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=f1861701-080f-4cd2-a32f-da146eeb4c50 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.07.01 dmi.board.name: 842A dmi.board.vendor: HP dmi.board.version: KBC Version 15.37.02 dmi.chassis.asset.tag: 5CD926C8K6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.07.01:bd06/03/2019:svnHP:pnHPZBook15G5:pvr:rvnHP:rn842A:rvrKBCVersion15.37.02:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G5 dmi.product.sku: 3AX13AV dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug disco -- 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/1838613 Title: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad Status in linux package in Ubuntu: Confirmed Bug description: After using the touchpad for a while, it suddenly believes that I'm doing a two-finger scroll, when I'm not. It makes the touchpad unusable : it's not possible to move the mouse anymore, vertical scrolling happens instead. I could not find an action that reliably gets me out of this mode (except reboot !). My workaround for now is to disable two-finger scrolling in "Config / Devices / Mouse & Touchpad", and enable "Edge scrolling" instead. I'm using Ubuntu 19.04 (Ubuntu 5.0.0-21.22-generic 5.0.15) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pcarbonn 1752 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 10:52:38 2019 InstallationDate: Installed on 2019-07-12 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: HP HP ZBook 15 G5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=f1861701-080f-4cd2-a32f-da146eeb4c50 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.07.01 dmi.board.name: 842A dmi.board.vendor: HP dmi.board.version: KBC Version 15.37.02 dmi.chassis.asset.tag: 5CD926C8K6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.07.01:bd06/03/2019:svnHP:pnHPZBook15G5:pvr:rvnHP:rn842A:rvrKBCVersion15.37.02:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G5 dmi.product.sku: 3AX13AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838613] Re: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad
Here is the output of xinput list: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Logitech Optical USB Mouseid=11 [slave pointer (2)] ⎜ ↳ ALP001F:00 044E:1222 Mouseid=14 [slave pointer (2)] ⎜ ↳ ALP001F:00 044E:1222 Touchpad id=15 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=18 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=19 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ HP HD Camera: HP HD Cameraid=12 [slave keyboard (3)] ↳ HP HD Camera: HP IR Cameraid=13 [slave keyboard (3)] ↳ ALP001F:00 044E:1222 UNKNOWN id=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=17 [slave keyboard (3)] ↳ HP Wireless hotkeys id=20 [slave keyboard (3)] ↳ HP WMI hotkeysid=21 [slave keyboard (3)] (The problem also happens without attaching the Logitech Optical USB mouse) -- 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/1838613 Title: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad Status in linux package in Ubuntu: Confirmed Bug description: After using the touchpad for a while, it suddenly believes that I'm doing a two-finger scroll, when I'm not. It makes the touchpad unusable : it's not possible to move the mouse anymore, vertical scrolling happens instead. I could not find an action that reliably gets me out of this mode (except reboot !). My workaround for now is to disable two-finger scrolling in "Config / Devices / Mouse & Touchpad", and enable "Edge scrolling" instead. I'm using Ubuntu 19.04 (Ubuntu 5.0.0-21.22-generic 5.0.15) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pcarbonn 1752 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 10:52:38 2019 InstallationDate: Installed on 2019-07-12 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: HP HP ZBook 15 G5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=f1861701-080f-4cd2-a32f-da146eeb4c50 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.07.01 dmi.board.name: 842A dmi.board.vendor: HP dmi.board.version: KBC Version 15.37.02 dmi.chassis.asset.tag: 5CD926C8K6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.07.01:bd06/03/2019:svnHP:pnHPZBook15G5:pvr:rvnHP:rn842A:rvrKBCVersion15.37.02:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G5 dmi.product.sku: 3AX13AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838613] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838613 Title: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad Status in linux package in Ubuntu: Confirmed Bug description: After using the touchpad for a while, it suddenly believes that I'm doing a two-finger scroll, when I'm not. It makes the touchpad unusable : it's not possible to move the mouse anymore, vertical scrolling happens instead. I could not find an action that reliably gets me out of this mode (except reboot !). My workaround for now is to disable two-finger scrolling in "Config / Devices / Mouse & Touchpad", and enable "Edge scrolling" instead. I'm using Ubuntu 19.04 (Ubuntu 5.0.0-21.22-generic 5.0.15) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pcarbonn 1752 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 10:52:38 2019 InstallationDate: Installed on 2019-07-12 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: HP HP ZBook 15 G5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=f1861701-080f-4cd2-a32f-da146eeb4c50 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.07.01 dmi.board.name: 842A dmi.board.vendor: HP dmi.board.version: KBC Version 15.37.02 dmi.chassis.asset.tag: 5CD926C8K6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.07.01:bd06/03/2019:svnHP:pnHPZBook15G5:pvr:rvnHP:rn842A:rvrKBCVersion15.37.02:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G5 dmi.product.sku: 3AX13AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837563] Re: disco/linux-raspi2: 5.0.0-1014.14 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1837563 Title: disco/linux-raspi2: 5.0.0-1014.14 -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-meta 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Thursday, 01. August 2019 08:25 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
I've uploaded a new test kernel based on the latest bionic kernel from
master-next:
https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-56.62~lp1796292/
In addition to that I've backported all the recent upstream bcache fixes
and applied my proposed fix for the potential deadlock in
bch_allocator_thread() (https://lkml.org/lkml/2019/7/10/241).
I've tested this kernel both on a VM and on a bare metal box, running the test
case from bug
1784665 (https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh - with
some minor adjustments to match my devices).
The tests have been running for more than 1h without triggering any
problem (and they're still going).
Ryan / Chris: it would be really nice if you could do one more test with
this new kernel... and if you're still hitting issues we can try to work
on a better reproducer. Thanks again!
--
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837563] Re: disco/linux-raspi2: 5.0.0-1014.14 -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: 1838395 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Thursday, 01. August 2019 08:25 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1837563 Title: disco/linux-raspi2: 5.0.0-1014.14 -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-meta 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Thursday, 01. August 2019 08:25 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838395] Re: disco/linux: 5.0.0-24.25 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-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 ** 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 backports: bug 1838393 (bionic/linux-hwe), bug 1838398 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837565 (linux-aws), bug 1837567 (linux-azure), bug 1837571 (linux-gcp), bug 1837572 (linux-kvm), bug 1837573 (linux-snapdragon) -- swm properties -- boot-testing-requested: true + bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Promote to Proposed - phase-changed: Thursday, 01. August 2019 06:40 UTC + phase: Testing + phase-changed: Thursday, 01. August 2019 09:51 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 + certification-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1838393 bionic/linux-oem-osp1: bug 1838398 disco/linux-aws: bug 1837565 disco/linux-azure: bug 1837567 disco/linux-gcp: bug 1837571 disco/linux-kvm: bug 1837572 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 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/1838395 Title: disco/linux: 5.0.0-24.25 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838393 (bionic/linux-hwe), bug 1838398 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837565 (linux-aws), bug 1837567 (linux-azure), bug 1837571 (linux-gcp), bug 1837572 (linux-kvm), bug 1837573 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 01. August 2019 09:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1838393 bionic/linux-oem-osp1: bug 1838398 disco/linux-aws: bug 1837565 disco/linux-azure: bug 1837567 disco/linux-gcp: bug 1837571 disco/linux-kvm: bug 1837572 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838395/+subscripti
[Kernel-packages] [Bug 1837573] Re: disco/linux-snapdragon: 5.0.0-1018.19 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** 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: 1838395 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Tuesday, 30. July 2019 22:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-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-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1837573 Title: disco/linux-snapdragon: 5.0.0-1018.19 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Tuesday, 30. July 2019 22:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-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/1837573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837622] Re: xenial/linux-azure: 4.15.0-1053.58 -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 backports: bug 1837621 (trusty/linux-azure) derivatives: bug 1837619 (azure-kernel), bug 1837620 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1837626 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 01. August 2019 08:35 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait trackers: trusty/linux-azure: bug 1837621 xenial/linux-azure-edge: bug 1837620 xenial/linux-azure/azure-kernel: bug 1837619 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/1837622 Title: xenial/linux-azure: 4.15.0-1053.58 -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: 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837621 (trusty/linux-azure) derivatives: bug 1837619 (azure-kernel), bug 1837620 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1837626 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 01. August 2019 08:35 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait trackers: trusty/linux-azure: bug 1837621 xenial/linux-azure-edge: bug 1837620 xenial/linux-azure/azure-kernel: bug 1837619 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837572] Re: disco/linux-kvm: 5.0.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** 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: 1838395 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Testing phase-changed: Wednesday, 31. July 2019 01:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1837572 Title: disco/linux-kvm: 5.0.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Testing phase-changed: Wednesday, 31. July 2019 01:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1837572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837571] Re: disco/linux-gcp: 5.0.0-1012.12 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Confirmed -- 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/1837571 Title: disco/linux-gcp: 5.0.0-1012.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837569 (bionic/linux-gke-5.0), bug 1837570 (bionic /linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Monday, 29. July 2019 12:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-edge: bug 1837570 bionic/linux-gke-5.0: bug 1837569 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837567] Re: disco/linux-azure: 5.0.0-1013.13 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1837567 Title: disco/linux-azure: 5.0.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838087 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 29. July 2019 12:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1838087 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838619] [NEW] Turn off nvme driver on raspi2
Public bug reported: We recently adjusted CONFIG_NVM to fix a build failure. The change causing this was actually a mis-merge and will be reverted. However the question came up whether it makes sense at all to build any raspberry kernel with NVME support at all. There currently is no way to attach any NVME to a raspberry pi, so lets turn off driver support for it for that kernel in total. ** Affects: linux-raspi2 (Ubuntu) Importance: Wishlist Status: Confirmed ** Affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1838619 Title: Turn off nvme driver on raspi2 Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Bionic: New Bug description: We recently adjusted CONFIG_NVM to fix a build failure. The change causing this was actually a mis-merge and will be reverted. However the question came up whether it makes sense at all to build any raspberry kernel with NVME support at all. There currently is no way to attach any NVME to a raspberry pi, so lets turn off driver support for it for that kernel in total. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1838619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838613] Re: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad
I should add that, when the mousepad has this funny behavior, the trackpoint (i.e., pointing stick) still works correctly. -- 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/1838613 Title: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad Status in linux package in Ubuntu: Confirmed Bug description: After using the touchpad for a while, it suddenly believes that I'm doing a two-finger scroll, when I'm not. It makes the touchpad unusable : it's not possible to move the mouse anymore, vertical scrolling happens instead. I could not find an action that reliably gets me out of this mode (except reboot !). My workaround for now is to disable two-finger scrolling in "Config / Devices / Mouse & Touchpad", and enable "Edge scrolling" instead. I'm using Ubuntu 19.04 (Ubuntu 5.0.0-21.22-generic 5.0.15) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pcarbonn 1752 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 10:52:38 2019 InstallationDate: Installed on 2019-07-12 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: HP HP ZBook 15 G5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=f1861701-080f-4cd2-a32f-da146eeb4c50 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.07.01 dmi.board.name: 842A dmi.board.vendor: HP dmi.board.version: KBC Version 15.37.02 dmi.chassis.asset.tag: 5CD926C8K6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.07.01:bd06/03/2019:svnHP:pnHPZBook15G5:pvr:rvnHP:rn842A:rvrKBCVersion15.37.02:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G5 dmi.product.sku: 3AX13AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832087] Re: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16
Hello You-Sheng Yang, Thank you for your work. Problem solved with the last kernel 5.0.0-23 I hope than the software "powertop" disponible on v 2.10 (https://01.org/powertop/) are soon compiled for Ubuntu... Best regards. Philippe -- 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/1832087 Title: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!?? I can not use my mouse, my keyboard and external speakers that all need bluetooth. My laptop has few usb ports, I am dependent on bluetooth with him... Unsolved problem from Kernel 5.0.0-15 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 1646 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2018-11-13 (206 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.173.6 Tags: tessa Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838613] Re: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad
Why does your laptop has both i2c and ps/2 touchpad/trackpoint? ⎜ ↳ ALP001F:00 044E:1222 Mouse id=14 [slave pointer (2)] ⎜ ↳ ALP001F:00 044E:1222 Touchpad id=15 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=18 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=19 [slave pointer (2)] So your touchpad and trackpoint are driven by ALP001F or AlpsPS/2? -- 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/1838613 Title: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad Status in linux package in Ubuntu: Confirmed Bug description: After using the touchpad for a while, it suddenly believes that I'm doing a two-finger scroll, when I'm not. It makes the touchpad unusable : it's not possible to move the mouse anymore, vertical scrolling happens instead. I could not find an action that reliably gets me out of this mode (except reboot !). My workaround for now is to disable two-finger scrolling in "Config / Devices / Mouse & Touchpad", and enable "Edge scrolling" instead. I'm using Ubuntu 19.04 (Ubuntu 5.0.0-21.22-generic 5.0.15) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pcarbonn 1752 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 10:52:38 2019 InstallationDate: Installed on 2019-07-12 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: HP HP ZBook 15 G5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=f1861701-080f-4cd2-a32f-da146eeb4c50 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.07.01 dmi.board.name: 842A dmi.board.vendor: HP dmi.board.version: KBC Version 15.37.02 dmi.chassis.asset.tag: 5CD926C8K6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.07.01:bd06/03/2019:svnHP:pnHPZBook15G5:pvr:rvnHP:rn842A:rvrKBCVersion15.37.02:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G5 dmi.product.sku: 3AX13AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838610] Re: The 3.13 kernel for Precise ESM does not provide the expected version number
Andy suggest us to use "cat /proc/version_signature" This command on this Precise node shows: Ubuntu 3.13.0-172.223~12.04.1-generic 3.13.11-ckt39 This looks more reliable than the "uname -vr" Testing a workaround on KT. He also found the bug that cause this issue. -- 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/1838610 Title: The 3.13 kernel for Precise ESM does not provide the expected version number Status in linux package in Ubuntu: Incomplete Bug description: The linux-generic-lts-trusty meta package on Precise will give you: linux-base linux-headers-3.13.0-172 linux-headers-3.13.0-172-generic linux-headers-generic-lts-trusty linux-image-3.13.0-172-generic linux-image-generic-lts-trusty linux-modules-3.13.0-172-generic And the kernel version returned from uname -a shows: Linux precise-testing 3.13.0-172-generic #1-Ubuntu SMP Sat Jul 6 10:46:56 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux This is breaking the automation as we're expecting the kernel version: 3.13.0-172.223~12.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837563] Re: disco/linux-raspi2: 5.0.0-1014.14 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** 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 ** 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: 1838395 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Promote to Proposed - phase-changed: Thursday, 01. August 2019 08:25 UTC + phase: Testing + phase-changed: Thursday, 01. August 2019 10:40 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 + certification-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-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1837563 Title: disco/linux-raspi2: 5.0.0-1014.14 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 01. August 2019 10:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-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/1837563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
This patch relies on a function that has been implemented later. I'm reopening the bug and uploading a fix for this one. vboxpci.ko: Running module version sanity check. /usr/sbin/dkms: line 784: find_module: command not found modinfo: ERROR: missing module or filename. - Original module - No original module exists within this kernel - Installation ** Changed in: dkms (Ubuntu Bionic) Status: Fix Released => New ** Changed in: dkms (Ubuntu Disco) Status: Fix Released => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: In Progress Status in dkms source package in Disco: Fix Released Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
Disco is fine, because the fund_module function is implemented already in 2.6.1 ** Changed in: dkms (Ubuntu Disco) Status: New => Fix Committed ** Changed in: dkms (Ubuntu Disco) Status: Fix Committed => Fix Released ** Changed in: dkms (Ubuntu Bionic) Status: New => In Progress ** Changed in: dkms (Ubuntu Bionic) Assignee: (unassigned) => Gianfranco Costamagna (costamagnagianfranco) ** Tags added: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: In Progress Status in dkms source package in Disco: Fix Released Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838627] [NEW] AppArmor onexec transition causes WARN kernel stack trace
Public bug reported: microk8s has reported on issue with the Xenial kernel where apparmor causes the following kernel stack trace due to an apparmor AA_BUG condition being triggered. [ 225.236085] [ cut here ] [ 225.236104] WARNING: CPU: 1 PID: 13726 at /build/linux-aUWTNP/linux-4.4.0/security/apparmor/file.c:136 aa_audit_file+0x16e/0x180() [ 225.236109] AppArmor WARN aa_audit_file: ((!(&sa)->apparmor_audit_data->request)): [ 225.236113] Modules linked in: [ 225.236118] btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs veth xt_nat xt_mark xt_comment ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs libcrc32c ctr ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep aufs overlay binfmt_misc drbg ansi_cprng dm_crypt snd_hda_codec_hdmi arc4 eeepc_wmi asus_wmi sparse_keymap nvidia_uvm(POE) mxm_wmi joydev input_leds btusb btrtl btbcm btintel bluetooth snd_usb_audio snd_usbmidi_lib snd_hda_intel snd_hda_codec intel_rapl x86_pkg_temp_thermal snd_hda_core intel_powerclamp snd_hwdep coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_ens1371 snd_ac97_codec gameport ac97_bus [ 225.236305] snd_seq_midi aesni_intel snd_pcm snd_seq_midi_event aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_rawmidi snd_seq iwlmvm snd_seq_device serio_raw snd_timer mac80211 snd soundcore iwlwifi cfg80211 mei_me mei shpchp 8250_fintek wmi acpi_pad mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_recent xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack parport_pc iptable_filter ip_tables ppdev x_tables lp parport autofs4 hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) i915_bpo psmouse e1000e intel_ips ptp i2c_algo_bit [ 225.236420] pps_core drm_kms_helper nvme syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm libahci video fjes [ 225.236446] CPU: 1 PID: 13726 Comm: runc:[2:INIT] Tainted: PW OE 4.4.0-154-generic #181-Ubuntu [ 225.236451] Hardware name: System manufacturer System Product Name/PRIME H270-PRO, BIOS 0323 01/04/2017 [ 225.236456] 0286 fa217f3573a84520 88033ade39d0 8140b481 [ 225.236464] 88033ade3a18 81d03018 88033ade3a08 81085432 [ 225.236477] 88035cb2f000 88033ade3b6c 88033bcb8b88 88033ade3d88 [ 225.236484] Call Trace: [ 225.236498] [] dump_stack+0x63/0x82 [ 225.236509] [] warn_slowpath_common+0x82/0xc0 [ 225.236518] [] warn_slowpath_fmt+0x5c/0x80 [ 225.236527] [] ? label_match.constprop.9+0x3dc/0x6c0 [ 225.236536] [] aa_audit_file+0x16e/0x180 [ 225.236544] [] profile_onexec+0x13d/0x3d0 [ 225.236554] [] handle_onexec+0x10e/0x10d0 [ 225.236562] [] ? vfs_getxattr_alloc+0x67/0x100 [ 225.236571] [] ? cap_inode_getsecurity+0x95/0x220 [ 225.236581] [] ? security_inode_getsecurity+0x5d/0x70 [ 225.236589] [] apparmor_bprm_set_creds+0x117/0xa60 [ 225.236596] [] ? vfs_getxattr+0x9e/0xb0 [ 225.236608] [] ? ovl_getxattr+0x52/0xb0 [overlay] [ 225.236617] [] ? get_vfs_caps_from_disk+0x7d/0x180 [ 225.236624] [] ? cap_bprm_set_creds+0xa3/0x5f0 [ 225.236633] [] security_bprm_set_creds+0x39/0x50 [ 225.236642] [] prepare_binprm+0x85/0x190 [ 225.236651] [] do_execveat_common.isra.31+0x4b4/0x770 [ 225.236661] [] SyS_execve+0x3a/0x50 [ 225.236671] [] stub_execve+0x5/0x5 [ 225.236678] [] ? entry_SYSCALL_64_fastpath+0x22/0xcb [ 225.236684] ---[ end trace 6b2beaa85ae31c29 ]--- This is caused when the change_onexec api is used and permitted by the profile but the task has the NO_NEW_PRIVS flag set causing the domain transition specified in the change_onexec request to fail. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: John Johansen (jjohansen) Status: Confirmed ** Tags: xenial ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => John Johansen (jjohansen) ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838627 Title: AppArmor onexec transition causes WARN kernel stack trace Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: microk8s has reported on issue with the Xenial kernel where apparmor causes the follo
[Kernel-packages] [Bug 1838627] Re: AppArmor onexec transition causes WARN kernel stack trace
The patch has been tested against a reproducer and fixes the issue. -- 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/1838627 Title: AppArmor onexec transition causes WARN kernel stack trace Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: microk8s has reported on issue with the Xenial kernel where apparmor causes the following kernel stack trace due to an apparmor AA_BUG condition being triggered. [ 225.236085] [ cut here ] [ 225.236104] WARNING: CPU: 1 PID: 13726 at /build/linux-aUWTNP/linux-4.4.0/security/apparmor/file.c:136 aa_audit_file+0x16e/0x180() [ 225.236109] AppArmor WARN aa_audit_file: ((!(&sa)->apparmor_audit_data->request)): [ 225.236113] Modules linked in: [ 225.236118] btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs veth xt_nat xt_mark xt_comment ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs libcrc32c ctr ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep aufs overlay binfmt_misc drbg ansi_cprng dm_crypt snd_hda_codec_hdmi arc4 eeepc_wmi asus_wmi sparse_keymap nvidia_uvm(POE) mxm_wmi joydev input_leds btusb btrtl btbcm btintel bluetooth snd_usb_audio snd_usbmidi_lib snd_hda_intel snd_hda_codec intel_rapl x86_pkg_temp_thermal snd_hda_core intel_powerclamp snd_hwdep coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_ens1371 snd_ac97_codec gameport ac97_bus [ 225.236305] snd_seq_midi aesni_intel snd_pcm snd_seq_midi_event aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_rawmidi snd_seq iwlmvm snd_seq_device serio_raw snd_timer mac80211 snd soundcore iwlwifi cfg80211 mei_me mei shpchp 8250_fintek wmi acpi_pad mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_recent xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack parport_pc iptable_filter ip_tables ppdev x_tables lp parport autofs4 hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) i915_bpo psmouse e1000e intel_ips ptp i2c_algo_bit [ 225.236420] pps_core drm_kms_helper nvme syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm libahci video fjes [ 225.236446] CPU: 1 PID: 13726 Comm: runc:[2:INIT] Tainted: PW OE 4.4.0-154-generic #181-Ubuntu [ 225.236451] Hardware name: System manufacturer System Product Name/PRIME H270-PRO, BIOS 0323 01/04/2017 [ 225.236456] 0286 fa217f3573a84520 88033ade39d0 8140b481 [ 225.236464] 88033ade3a18 81d03018 88033ade3a08 81085432 [ 225.236477] 88035cb2f000 88033ade3b6c 88033bcb8b88 88033ade3d88 [ 225.236484] Call Trace: [ 225.236498] [] dump_stack+0x63/0x82 [ 225.236509] [] warn_slowpath_common+0x82/0xc0 [ 225.236518] [] warn_slowpath_fmt+0x5c/0x80 [ 225.236527] [] ? label_match.constprop.9+0x3dc/0x6c0 [ 225.236536] [] aa_audit_file+0x16e/0x180 [ 225.236544] [] profile_onexec+0x13d/0x3d0 [ 225.236554] [] handle_onexec+0x10e/0x10d0 [ 225.236562] [] ? vfs_getxattr_alloc+0x67/0x100 [ 225.236571] [] ? cap_inode_getsecurity+0x95/0x220 [ 225.236581] [] ? security_inode_getsecurity+0x5d/0x70 [ 225.236589] [] apparmor_bprm_set_creds+0x117/0xa60 [ 225.236596] [] ? vfs_getxattr+0x9e/0xb0 [ 225.236608] [] ? ovl_getxattr+0x52/0xb0 [overlay] [ 225.236617] [] ? get_vfs_caps_from_disk+0x7d/0x180 [ 225.236624] [] ? cap_bprm_set_creds+0xa3/0x5f0 [ 225.236633] [] security_bprm_set_creds+0x39/0x50 [ 225.236642] [] prepare_binprm+0x85/0x190 [ 225.236651] [] do_execveat_common.isra.31+0x4b4/0x770 [ 225.236661] [] SyS_execve+0x3a/0x50 [ 225.236671] [] stub_execve+0x5/0x5 [ 225.236678] [] ? entry_SYSCALL_64_fastpath+0x22/0xcb [ 225.236684] ---[ end trace 6b2beaa85ae31c29 ]--- This is caused when the change_onexec api is used and permitted by the profile but the task has the NO_NEW_PRIVS flag set causing the domain transition specified in the change_onexec request to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837622] Re: xenial/linux-azure: 4.15.0-1053.58 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** 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 backports: bug 1837621 (trusty/linux-azure) derivatives: bug 1837619 (azure-kernel), bug 1837620 (linux-azure-edge) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Promote to Proposed - phase-changed: Thursday, 01. August 2019 08:35 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 01. August 2019 11:23 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait + promote-to-proposed: Pending -- ready for review trackers: trusty/linux-azure: bug 1837621 xenial/linux-azure-edge: bug 1837620 xenial/linux-azure/azure-kernel: bug 1837619 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/1837622 Title: xenial/linux-azure: 4.15.0-1053.58 -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: 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837621 (trusty/linux-azure) derivatives: bug 1837619 (azure-kernel), bug 1837620 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Thursday, 01. August 2019 11:23 UTC reason: promote-to-proposed: Pending -- ready for review trackers: trusty/linux-azure: bug 1837621 xenial/linux-azure-edge: bug 1837620 xenial/linux-azure/azure-kernel: bug 1837619 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838627] Re: AppArmor onexec transition causes WARN kernel stack trace
Fix selected and backported from a larger patch that originally landed in Zesty and subsequently landed in upstream. ** Patch added: "0001-UBUNTU-SAUCE-apparmor-fix-audit-failures-when-perfor.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838627/+attachment/5280320/+files/0001-UBUNTU-SAUCE-apparmor-fix-audit-failures-when-perfor.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/1838627 Title: AppArmor onexec transition causes WARN kernel stack trace Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: microk8s has reported on issue with the Xenial kernel where apparmor causes the following kernel stack trace due to an apparmor AA_BUG condition being triggered. [ 225.236085] [ cut here ] [ 225.236104] WARNING: CPU: 1 PID: 13726 at /build/linux-aUWTNP/linux-4.4.0/security/apparmor/file.c:136 aa_audit_file+0x16e/0x180() [ 225.236109] AppArmor WARN aa_audit_file: ((!(&sa)->apparmor_audit_data->request)): [ 225.236113] Modules linked in: [ 225.236118] btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs veth xt_nat xt_mark xt_comment ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs libcrc32c ctr ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep aufs overlay binfmt_misc drbg ansi_cprng dm_crypt snd_hda_codec_hdmi arc4 eeepc_wmi asus_wmi sparse_keymap nvidia_uvm(POE) mxm_wmi joydev input_leds btusb btrtl btbcm btintel bluetooth snd_usb_audio snd_usbmidi_lib snd_hda_intel snd_hda_codec intel_rapl x86_pkg_temp_thermal snd_hda_core intel_powerclamp snd_hwdep coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_ens1371 snd_ac97_codec gameport ac97_bus [ 225.236305] snd_seq_midi aesni_intel snd_pcm snd_seq_midi_event aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_rawmidi snd_seq iwlmvm snd_seq_device serio_raw snd_timer mac80211 snd soundcore iwlwifi cfg80211 mei_me mei shpchp 8250_fintek wmi acpi_pad mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_recent xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack parport_pc iptable_filter ip_tables ppdev x_tables lp parport autofs4 hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) i915_bpo psmouse e1000e intel_ips ptp i2c_algo_bit [ 225.236420] pps_core drm_kms_helper nvme syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm libahci video fjes [ 225.236446] CPU: 1 PID: 13726 Comm: runc:[2:INIT] Tainted: PW OE 4.4.0-154-generic #181-Ubuntu [ 225.236451] Hardware name: System manufacturer System Product Name/PRIME H270-PRO, BIOS 0323 01/04/2017 [ 225.236456] 0286 fa217f3573a84520 88033ade39d0 8140b481 [ 225.236464] 88033ade3a18 81d03018 88033ade3a08 81085432 [ 225.236477] 88035cb2f000 88033ade3b6c 88033bcb8b88 88033ade3d88 [ 225.236484] Call Trace: [ 225.236498] [] dump_stack+0x63/0x82 [ 225.236509] [] warn_slowpath_common+0x82/0xc0 [ 225.236518] [] warn_slowpath_fmt+0x5c/0x80 [ 225.236527] [] ? label_match.constprop.9+0x3dc/0x6c0 [ 225.236536] [] aa_audit_file+0x16e/0x180 [ 225.236544] [] profile_onexec+0x13d/0x3d0 [ 225.236554] [] handle_onexec+0x10e/0x10d0 [ 225.236562] [] ? vfs_getxattr_alloc+0x67/0x100 [ 225.236571] [] ? cap_inode_getsecurity+0x95/0x220 [ 225.236581] [] ? security_inode_getsecurity+0x5d/0x70 [ 225.236589] [] apparmor_bprm_set_creds+0x117/0xa60 [ 225.236596] [] ? vfs_getxattr+0x9e/0xb0 [ 225.236608] [] ? ovl_getxattr+0x52/0xb0 [overlay] [ 225.236617] [] ? get_vfs_caps_from_disk+0x7d/0x180 [ 225.236624] [] ? cap_bprm_set_creds+0xa3/0x5f0 [ 225.236633] [] security_bprm_set_creds+0x39/0x50 [ 225.236642] [] prepare_binprm+0x85/0x190 [ 225.236651] [] do_execveat_common.isra.31+0x4b4/0x770 [ 225.236661] [] SyS_execve+0x3a/0x50 [ 225.236671] [] stub_execve+0x5/0x5 [ 225.236678] [] ? entry_SYSCALL_64_fastpath+0x22/0xcb [ 225.236684] ---[ end trace 6b2beaa85ae31c29 ]--- This is caused when the change_onexec api is used and permitted by the profile but the task has the NO_NEW_PRIVS flag set causing the domain transition specified in the change_onexec request to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838627/+subscriptions -- Mailing list: https://l
[Kernel-packages] [Bug 1838627] 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 1838627 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 ** Tags added: xenial -- 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/1838627 Title: AppArmor onexec transition causes WARN kernel stack trace Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: microk8s has reported on issue with the Xenial kernel where apparmor causes the following kernel stack trace due to an apparmor AA_BUG condition being triggered. [ 225.236085] [ cut here ] [ 225.236104] WARNING: CPU: 1 PID: 13726 at /build/linux-aUWTNP/linux-4.4.0/security/apparmor/file.c:136 aa_audit_file+0x16e/0x180() [ 225.236109] AppArmor WARN aa_audit_file: ((!(&sa)->apparmor_audit_data->request)): [ 225.236113] Modules linked in: [ 225.236118] btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs veth xt_nat xt_mark xt_comment ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs libcrc32c ctr ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep aufs overlay binfmt_misc drbg ansi_cprng dm_crypt snd_hda_codec_hdmi arc4 eeepc_wmi asus_wmi sparse_keymap nvidia_uvm(POE) mxm_wmi joydev input_leds btusb btrtl btbcm btintel bluetooth snd_usb_audio snd_usbmidi_lib snd_hda_intel snd_hda_codec intel_rapl x86_pkg_temp_thermal snd_hda_core intel_powerclamp snd_hwdep coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_ens1371 snd_ac97_codec gameport ac97_bus [ 225.236305] snd_seq_midi aesni_intel snd_pcm snd_seq_midi_event aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_rawmidi snd_seq iwlmvm snd_seq_device serio_raw snd_timer mac80211 snd soundcore iwlwifi cfg80211 mei_me mei shpchp 8250_fintek wmi acpi_pad mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_recent xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack parport_pc iptable_filter ip_tables ppdev x_tables lp parport autofs4 hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) i915_bpo psmouse e1000e intel_ips ptp i2c_algo_bit [ 225.236420] pps_core drm_kms_helper nvme syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm libahci video fjes [ 225.236446] CPU: 1 PID: 13726 Comm: runc:[2:INIT] Tainted: PW OE 4.4.0-154-generic #181-Ubuntu [ 225.236451] Hardware name: System manufacturer System Product Name/PRIME H270-PRO, BIOS 0323 01/04/2017 [ 225.236456] 0286 fa217f3573a84520 88033ade39d0 8140b481 [ 225.236464] 88033ade3a18 81d03018 88033ade3a08 81085432 [ 225.236477] 88035cb2f000 88033ade3b6c 88033bcb8b88 88033ade3d88 [ 225.236484] Call Trace: [ 225.236498] [] dump_stack+0x63/0x82 [ 225.236509] [] warn_slowpath_common+0x82/0xc0 [ 225.236518] [] warn_slowpath_fmt+0x5c/0x80 [ 225.236527] [] ? label_match.constprop.9+0x3dc/0x6c0 [ 225.236536] [] aa_audit_file+0x16e/0x180 [ 225.236544] [] profile_onexec+0x13d/0x3d0 [ 225.236554] [] handle_onexec+0x10e/0x10d0 [ 225.236562] [] ? vfs_getxattr_alloc+0x67/0x100 [ 225.236571] [] ? cap_inode_getsecurity+0x95/0x220 [ 225.236581] [] ? security_inode_getsecurity+0x5d/0x70 [ 225.236589] [] apparmor_bprm_set_creds+0x117/0xa60 [ 225.236596] [] ? vfs_getxattr+0x9e/0xb0 [ 225.236608] [] ? ovl_getxattr+0x52/0xb0 [overlay] [ 225.236617] [] ? get_vfs_caps_from_disk+0x7d/0x180 [ 225.236624] [] ? cap_bprm_set_creds+0xa3/0x5f0 [ 225.236633] [] security_bprm_set_creds+0x39/0x50 [ 225.236642] [] prepare_binprm+0x85/0x190 [ 225.236651] [] do_execveat_common.isra.31+0x4b4/0x770 [ 225.236661] [] SyS_execve+0x3a/0x50 [ 225.236671] [] stub_execve+0x5/0x5 [ 225.236678] [] ? entry_SYSCALL_64_fastpath+0x22/0xcb [ 225.236684] ---[ end trace 6b2beaa85ae31c29 ]--- This is caused when the change_onexec api is used and permitted by the profile but
[Kernel-packages] [Bug 1838610] Re: The 3.13 kernel for Precise ESM does not provide the expected version number
** Tags added: ckct kt ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838610 Title: The 3.13 kernel for Precise ESM does not provide the expected version number Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: The linux-generic-lts-trusty meta package on Precise will give you: linux-base linux-headers-3.13.0-172 linux-headers-3.13.0-172-generic linux-headers-generic-lts-trusty linux-image-3.13.0-172-generic linux-image-generic-lts-trusty linux-modules-3.13.0-172-generic And the kernel version returned from uname -a shows: Linux precise-testing 3.13.0-172-generic #1-Ubuntu SMP Sat Jul 6 10:46:56 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux This is breaking the automation as we're expecting the kernel version: 3.13.0-172.223~12.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1838610/+subscriptions -- Mailing list: https://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 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
There is a sru request for this regression already, and land another change from upstream. Sorry for inconvenient. https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1838245 Gianfranco Costamagna 於 2019年8月1日 週四 下午7:20 寫道： > Disco is fine, because the fund_module function is implemented already > in 2.6.1 > > ** Changed in: dkms (Ubuntu Disco) >Status: New => Fix Committed > > ** Changed in: dkms (Ubuntu Disco) >Status: Fix Committed => Fix Released > > ** Changed in: dkms (Ubuntu Bionic) >Status: New => In Progress > > ** Changed in: dkms (Ubuntu Bionic) > Assignee: (unassigned) => Gianfranco Costamagna (costamagnagianfranco) > > ** Tags added: regression-update > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1828948 > > Title: > OBSOLETE_BY in DKMS.CONF does not work > > Status in DKMS: > Fix Released > Status in OEM Priority Project: > Fix Committed > Status in dkms package in Ubuntu: > Fix Released > Status in dkms source package in Bionic: > In Progress > Status in dkms source package in Disco: > Fix Released > > Bug description: > [Impact] > OBSOLETE_BY in DKMS.CONF not work > Which also be reported on upstream: > https://github.com/dell/dkms/issues/81 > > [Test case] > 1. add OBSOLETE_BY in DKMS.CONF > e.g. OBSOLETE_BY="4.15.0-1033" > 2. the kernel module should not be built with kernel greater than the > version specified by OBSOLETE_BY > e.g. >- user install kernel 4.15.0-1030 and 4.15.0-10360 >- user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] > which has OBSOLETE_BY="4.15.0-1033" >- the kernel module from dkms [1] should only built for 4.15.0-1030, > but not for 4.15.0-10360 > > [Regression potential] > None as it used to work, but somehow regression there. > > [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- > ath10k-lp1803647-4.15-dkms-daily > > To manage notifications about this bug go to: > https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: In Progress Status in dkms source package in Disco: Fix Released Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838590] Re: Update thermald to 1.9 release
Please use the latest dptfxtract tool version 1.4.2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1838590 Title: Update thermald to 1.9 release Status in dptfxtract package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: The thermald 1.9 release was just tagged, and has potential to help quite a bit with platform performance on some newer platforms when run with kernel 5.3. It would be nice to update eoan to this new release. > - The major change in this version is the active power limits adjustment. This will be useful to improve performance on some newer platform. But this will will lead to increase in CPU and other temperatures. Hence this is important to run dptfxtract version 1.4.1 tool to get performance sensitive thermal limits (https://github.com/intel/dptfxtract/commits/v1.4.1). If the default configuration picked up by thermald is not optimal, user can select other less aggressive configuration. Refer to the README here https://github.com/intel/dptfxtract/blob/master/README.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dptfxtract/+bug/1838590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835540] Re: Confusing "modinfo: ERROR: missing module or filename." during normal operation
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dkms (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1835540 Title: Confusing "modinfo: ERROR: missing module or filename." during normal operation Status in dkms package in Ubuntu: Confirmed Bug description: I just installed a new kernel, and when I did so my Nvidia kernel modules were handled through DKMS, as you would expect. However, during what I believe is normal operation, I saw the following stanza (repeated for several nvidia .ko files): nvidia.ko: Running module version sanity check. modinfo: ERROR: missing module or filename. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.0.0-20-generic/updates/dkms/ The "ERROR" in here gave me pause, but I _believe_ that's an expected message for a new kernel. It would make for a less troubling user experience if we didn't print out "ERROR" in all caps when there is no error at all. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: dkms 2.7.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Jul 5 09:52:41 2019 InstallationDate: Installed on 2019-05-07 (58 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: Upgraded to eoan on 2019-05-08 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1835540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835540] Re: Confusing "modinfo: ERROR: missing module or filename." during normal operation
I agree, I don't remember this behavior a few months ago. It was throwing me off quite a bit at first. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1835540 Title: Confusing "modinfo: ERROR: missing module or filename." during normal operation Status in dkms package in Ubuntu: Confirmed Bug description: I just installed a new kernel, and when I did so my Nvidia kernel modules were handled through DKMS, as you would expect. However, during what I believe is normal operation, I saw the following stanza (repeated for several nvidia .ko files): nvidia.ko: Running module version sanity check. modinfo: ERROR: missing module or filename. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.0.0-20-generic/updates/dkms/ The "ERROR" in here gave me pause, but I _believe_ that's an expected message for a new kernel. It would make for a less troubling user experience if we didn't print out "ERROR" in all caps when there is no error at all. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: dkms 2.7.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Jul 5 09:52:41 2019 InstallationDate: Installed on 2019-05-07 (58 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: Upgraded to eoan on 2019-05-08 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1835540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
ubuntu@ubuntu:~$ uname -r
4.15.0-56-generic
ubuntu@ubuntu:~$ cat /proc/version
Linux version 4.15.0-56-generic (arighi@kathleen) (gcc version 7.4.0 (Ubuntu
7.4.0-1ubuntu1~18.04.1)) #62~lp1796292 SMP Thu Aug 1 07:45:21 UTC 2019
This failed on the second install while running bcache-super-show /dev/vdg
Hung task.
[ 259.150347] bcache: run_cache_set() invalidating existing data
[ 259.158038] bcache: register_cache() registered cache device nvme1n1p2
[ 259.251093] bcache: register_bdev() registered backing device vdg
[ 259.379809] bcache: bch_cached_dev_attach() Caching vdg as bcache3 on set
084505ad-5f6c-4666-9e3e-4f1650e8b015
[ 259.411486] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
[ 259.537070] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
[ 259.797830] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
[ 259.900392] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
[ 271.682662] md: md0: resync done.
[ 484.525529] INFO: task python3:11257 blocked for more than 120 seconds.
[ 484.528933] Tainted: P O 4.15.0-56-generic #62~lp1796292
[ 484.532221] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 484.535936] python3 D0 11257 7974 0x
[ 484.535941] Call Trace:
[ 484.535952] __schedule+0x291/0x8a0
[ 484.535957] schedule+0x2c/0x80
[ 484.535977] bch_bucket_alloc+0x1fa/0x350 [bcache]
[ 484.535984] ? wait_woken+0x80/0x80
[ 484.535993] __bch_bucket_alloc_set+0xfe/0x150 [bcache]
[ 484.536002] bch_bucket_alloc_set+0x4e/0x70 [bcache]
[ 484.536014] __uuid_write+0x59/0x150 [bcache]
[ 484.536025] ? __write_super+0x137/0x170 [bcache]
[ 484.536035] bch_uuid_write+0x16/0x40 [bcache]
[ 484.536046] __cached_dev_store+0x1d8/0x8a0 [bcache]
[ 484.536057] bch_cached_dev_store+0x39/0xc0 [bcache]
[ 484.536061] sysfs_kf_write+0x3c/0x50
[ 484.536064] kernfs_fop_write+0x125/0x1a0
[ 484.536069] __vfs_write+0x1b/0x40
[ 484.536071] vfs_write+0xb1/0x1a0
[ 484.536075] SyS_write+0x5c/0xe0
[ 484.536081] do_syscall_64+0x73/0x130
[ 484.536085] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 484.536088] RIP: 0033:0x7f2ac7aa7154
[ 484.536090] RSP: 002b:7157b628 EFLAGS: 0246 ORIG_RAX:
0001
[ 484.536093] RAX: ffda RBX: 0008 RCX: 7f2ac7aa7154
[ 484.536095] RDX: 0008 RSI: 01c96340 RDI: 0003
[ 484.536096] RBP: 7f2ac7fa26c0 R08: R09:
[ 484.536098] R10: 0100 R11: 0246 R12: 0003
[ 484.536099] R13: R14: 01c96340 R15: 019c7db0
I'll note that, I can run bcache-super-show on the device while this was hung.
$ sudo bash
root@ubuntu:~# bcache-super-show /dev/vdg
sb.magicok
sb.first_sector 8 [match]
sb.csum C71A896B52F1C486 [match]
sb.version 1 [backing device]
dev.label osddata5
dev.uuid11df8370-fb64-4bb0-8171-dadabb47f6b1
dev.sectors_per_block 1
dev.sectors_per_bucket 1024
dev.data.first_sector 16
dev.data.cache_mode 1 [writeback]
dev.data.cache_state1 [clean]
cset.uuid 084505ad-5f6c-4666-9e3e-4f1650e8b015
--
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.n
[Kernel-packages] [Bug 1838627] Re: AppArmor onexec transition causes WARN kernel stack trace
** 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/1838627 Title: AppArmor onexec transition causes WARN kernel stack trace Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: microk8s has reported on issue with the Xenial kernel where apparmor causes the following kernel stack trace due to an apparmor AA_BUG condition being triggered. [ 225.236085] [ cut here ] [ 225.236104] WARNING: CPU: 1 PID: 13726 at /build/linux-aUWTNP/linux-4.4.0/security/apparmor/file.c:136 aa_audit_file+0x16e/0x180() [ 225.236109] AppArmor WARN aa_audit_file: ((!(&sa)->apparmor_audit_data->request)): [ 225.236113] Modules linked in: [ 225.236118] btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs veth xt_nat xt_mark xt_comment ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs libcrc32c ctr ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep aufs overlay binfmt_misc drbg ansi_cprng dm_crypt snd_hda_codec_hdmi arc4 eeepc_wmi asus_wmi sparse_keymap nvidia_uvm(POE) mxm_wmi joydev input_leds btusb btrtl btbcm btintel bluetooth snd_usb_audio snd_usbmidi_lib snd_hda_intel snd_hda_codec intel_rapl x86_pkg_temp_thermal snd_hda_core intel_powerclamp snd_hwdep coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_ens1371 snd_ac97_codec gameport ac97_bus [ 225.236305] snd_seq_midi aesni_intel snd_pcm snd_seq_midi_event aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_rawmidi snd_seq iwlmvm snd_seq_device serio_raw snd_timer mac80211 snd soundcore iwlwifi cfg80211 mei_me mei shpchp 8250_fintek wmi acpi_pad mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_recent xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack parport_pc iptable_filter ip_tables ppdev x_tables lp parport autofs4 hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) i915_bpo psmouse e1000e intel_ips ptp i2c_algo_bit [ 225.236420] pps_core drm_kms_helper nvme syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm libahci video fjes [ 225.236446] CPU: 1 PID: 13726 Comm: runc:[2:INIT] Tainted: PW OE 4.4.0-154-generic #181-Ubuntu [ 225.236451] Hardware name: System manufacturer System Product Name/PRIME H270-PRO, BIOS 0323 01/04/2017 [ 225.236456] 0286 fa217f3573a84520 88033ade39d0 8140b481 [ 225.236464] 88033ade3a18 81d03018 88033ade3a08 81085432 [ 225.236477] 88035cb2f000 88033ade3b6c 88033bcb8b88 88033ade3d88 [ 225.236484] Call Trace: [ 225.236498] [] dump_stack+0x63/0x82 [ 225.236509] [] warn_slowpath_common+0x82/0xc0 [ 225.236518] [] warn_slowpath_fmt+0x5c/0x80 [ 225.236527] [] ? label_match.constprop.9+0x3dc/0x6c0 [ 225.236536] [] aa_audit_file+0x16e/0x180 [ 225.236544] [] profile_onexec+0x13d/0x3d0 [ 225.236554] [] handle_onexec+0x10e/0x10d0 [ 225.236562] [] ? vfs_getxattr_alloc+0x67/0x100 [ 225.236571] [] ? cap_inode_getsecurity+0x95/0x220 [ 225.236581] [] ? security_inode_getsecurity+0x5d/0x70 [ 225.236589] [] apparmor_bprm_set_creds+0x117/0xa60 [ 225.236596] [] ? vfs_getxattr+0x9e/0xb0 [ 225.236608] [] ? ovl_getxattr+0x52/0xb0 [overlay] [ 225.236617] [] ? get_vfs_caps_from_disk+0x7d/0x180 [ 225.236624] [] ? cap_bprm_set_creds+0xa3/0x5f0 [ 225.236633] [] security_bprm_set_creds+0x39/0x50 [ 225.236642] [] prepare_binprm+0x85/0x190 [ 225.236651] [] do_execveat_common.isra.31+0x4b4/0x770 [ 225.236661] [] SyS_execve+0x3a/0x50 [ 225.236671] [] stub_execve+0x5/0x5 [ 225.236678] [] ? entry_SYSCALL_64_fastpath+0x22/0xcb [ 225.236684] ---[ end trace 6b2beaa85ae31c29 ]--- This is caused when the change_onexec api is used and permitted by the profile but the task has the NO_NEW_PRIVS flag set causing the domain transition specified in the change_onexec request to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834944] Re: bionic/linux-fips: 4.15.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834944 Title: bionic/linux-fips: 4.15.0-1012.13 -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: Invalid 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: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Complete phase-changed: Thursday, 01. August 2019 12:45 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834944] Re: bionic/linux-fips: 4.15.0-1012.13 -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: 1834954 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Holding before Release - phase-changed: Tuesday, 23. July 2019 12:00 UTC + phase: Complete + phase-changed: Thursday, 01. August 2019 12:45 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present 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/1834944 Title: bionic/linux-fips: 4.15.0-1012.13 -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: Invalid 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: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Complete phase-changed: Thursday, 01. August 2019 12:45 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838613] Re: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad
Does this issue happen after S3? -- 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/1838613 Title: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad Status in linux package in Ubuntu: Confirmed Bug description: After using the touchpad for a while, it suddenly believes that I'm doing a two-finger scroll, when I'm not. It makes the touchpad unusable : it's not possible to move the mouse anymore, vertical scrolling happens instead. I could not find an action that reliably gets me out of this mode (except reboot !). My workaround for now is to disable two-finger scrolling in "Config / Devices / Mouse & Touchpad", and enable "Edge scrolling" instead. I'm using Ubuntu 19.04 (Ubuntu 5.0.0-21.22-generic 5.0.15) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pcarbonn 1752 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 10:52:38 2019 InstallationDate: Installed on 2019-07-12 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: HP HP ZBook 15 G5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=f1861701-080f-4cd2-a32f-da146eeb4c50 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.07.01 dmi.board.name: 842A dmi.board.vendor: HP dmi.board.version: KBC Version 15.37.02 dmi.chassis.asset.tag: 5CD926C8K6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.07.01:bd06/03/2019:svnHP:pnHPZBook15G5:pvr:rvnHP:rn842A:rvrKBCVersion15.37.02:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G5 dmi.product.sku: 3AX13AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838613] Re: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad
I'm not sure what you are talking about ? i2c ? S3 ? Sorry. I can understand that the problem may be due to having 2 drivers for the TouchPad. I'm not sure how they got there. The only driver I have updated is the NVIDIA one. I have the same problem with the trial Ubuntu on USB. The PC is relatively new (a few weeks). -- 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/1838613 Title: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad Status in linux package in Ubuntu: Confirmed Bug description: After using the touchpad for a while, it suddenly believes that I'm doing a two-finger scroll, when I'm not. It makes the touchpad unusable : it's not possible to move the mouse anymore, vertical scrolling happens instead. I could not find an action that reliably gets me out of this mode (except reboot !). My workaround for now is to disable two-finger scrolling in "Config / Devices / Mouse & Touchpad", and enable "Edge scrolling" instead. I'm using Ubuntu 19.04 (Ubuntu 5.0.0-21.22-generic 5.0.15) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pcarbonn 1752 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 10:52:38 2019 InstallationDate: Installed on 2019-07-12 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: HP HP ZBook 15 G5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=f1861701-080f-4cd2-a32f-da146eeb4c50 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.07.01 dmi.board.name: 842A dmi.board.vendor: HP dmi.board.version: KBC Version 15.37.02 dmi.chassis.asset.tag: 5CD926C8K6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.07.01:bd06/03/2019:svnHP:pnHPZBook15G5:pvr:rvnHP:rn842A:rvrKBCVersion15.37.02:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G5 dmi.product.sku: 3AX13AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834944] Re: bionic/linux-fips: 4.15.0-1012.13 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- 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/1834944 Title: bionic/linux-fips: 4.15.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Invalid 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: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Complete phase-changed: Thursday, 01. August 2019 12:45 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837563] Re: disco/linux-raspi2: 5.0.0-1014.14 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Testing - phase-changed: Thursday, 01. August 2019 10:40 UTC + phase: Ready for Testing + phase-changed: Thursday, 01. August 2019 13:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-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-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1837563 Title: disco/linux-raspi2: 5.0.0-1014.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Ready for Testing phase-changed: Thursday, 01. August 2019 13:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-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/1837563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838613] Re: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad
S3 means system suspend. Can you also attach dmesg after the issue happens? -- 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/1838613 Title: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad Status in linux package in Ubuntu: Confirmed Bug description: After using the touchpad for a while, it suddenly believes that I'm doing a two-finger scroll, when I'm not. It makes the touchpad unusable : it's not possible to move the mouse anymore, vertical scrolling happens instead. I could not find an action that reliably gets me out of this mode (except reboot !). My workaround for now is to disable two-finger scrolling in "Config / Devices / Mouse & Touchpad", and enable "Edge scrolling" instead. I'm using Ubuntu 19.04 (Ubuntu 5.0.0-21.22-generic 5.0.15) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pcarbonn 1752 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 10:52:38 2019 InstallationDate: Installed on 2019-07-12 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: HP HP ZBook 15 G5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=f1861701-080f-4cd2-a32f-da146eeb4c50 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.07.01 dmi.board.name: 842A dmi.board.vendor: HP dmi.board.version: KBC Version 15.37.02 dmi.chassis.asset.tag: 5CD926C8K6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.07.01:bd06/03/2019:svnHP:pnHPZBook15G5:pvr:rvnHP:rn842A:rvrKBCVersion15.37.02:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G5 dmi.product.sku: 3AX13AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835279] Re: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open
That sounds awesome, Claudio, thank you! We'll start with Eoan and I will work on getting a debug kernel ready in the meantime. -- 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/1835279 Title: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc- kernel_240.snap Version signature: 4.15.0-54.58-generic 4.15.18 Issue is non-deterministic, and happens in roughly 20% of the attempts. Running on: qemu-kvm, command line: kvm \ -bios /usr/share/ovmf/OVMF.fd \ -smp 2 -m 512 -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,format=raw Commands that caused the problem: cryptsetup -q --type luks2 --key-file luksFormat /dev/sda4 LD_PRELOAD=/lib/no-udev.so cryptsetup --type luks2 --key-file open /dev/sda4 crypt-data Notes: - See https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1589083 for more information on the no-udev workaround. - The commands are scripted. Also tried to add a 200ms and 1s interval before opening the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
Thanks Ryan, this is very interesting:
[ 259.411486] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
[ 259.537070] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
[ 259.797830] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
[ 259.900392] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
It looks that we're trying to register /dev/vdg multiple times as a
backing device (make-bcache -B). I'm not getting this message during my
tests, so that might be required to reproduce that particular deadlock.
I'll modify my test case to trigger these errors and see if I can
reproduce the hung task timeout issue.
--
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837155] Re: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => 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/1837155 Title: xenial/linux-fips: 4.4.0-1015.20 -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: Confirmed 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: Fix Released 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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Release phase-changed: Thursday, 01. August 2019 14:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838613] Re: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad
I did S3 by rotating the screen down towards the keyboard (--> screen goes black), then back up, and the bug appeared after a minute. Attached is dmesg. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838613/+attachment/5280348/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838613 Title: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad Status in linux package in Ubuntu: Confirmed Bug description: After using the touchpad for a while, it suddenly believes that I'm doing a two-finger scroll, when I'm not. It makes the touchpad unusable : it's not possible to move the mouse anymore, vertical scrolling happens instead. I could not find an action that reliably gets me out of this mode (except reboot !). My workaround for now is to disable two-finger scrolling in "Config / Devices / Mouse & Touchpad", and enable "Edge scrolling" instead. I'm using Ubuntu 19.04 (Ubuntu 5.0.0-21.22-generic 5.0.15) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pcarbonn 1752 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 10:52:38 2019 InstallationDate: Installed on 2019-07-12 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: HP HP ZBook 15 G5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=f1861701-080f-4cd2-a32f-da146eeb4c50 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.07.01 dmi.board.name: 842A dmi.board.vendor: HP dmi.board.version: KBC Version 15.37.02 dmi.chassis.asset.tag: 5CD926C8K6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.07.01:bd06/03/2019:svnHP:pnHPZBook15G5:pvr:rvnHP:rn842A:rvrKBCVersion15.37.02:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G5 dmi.product.sku: 3AX13AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837155] Re: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: 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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Ready for Testing - phase-changed: Tuesday, 23. July 2019 22:41 UTC + phase: Ready for Release + phase-changed: Thursday, 01. August 2019 14:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- ready to copy 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/1837155 Title: xenial/linux-fips: 4.4.0-1015.20 -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: In Progress 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: Fix Released 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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Release phase-changed: Thursday, 01. August 2019 14:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837155] Re: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837155 Title: xenial/linux-fips: 4.4.0-1015.20 -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: In Progress 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: Fix Released 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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Release phase-changed: Thursday, 01. August 2019 14:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ongoing -- packages not yet published variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826447] Re: Azure: Backport vIOMMU driver (increase vCPU limits)
Disco: https://lists.ubuntu.com/archives/kernel- team/2019-August/102726.html -- 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/1826447 Title: Azure: Backport vIOMMU driver (increase vCPU limits) Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure source package in Disco: Confirmed Bug description: Description: To support VM instances with >255 vCPUS, we need the patch set below backported to the Azure 4.18 kernel. These patches include - - New Hyper-V IOMMU driver. This driver will be Hyper-V specific. - Minor update to the Hyper-V specific virtual PCI code. Need to expand the size of an array to allow for a larger number of vCPUs. There are very large VM instance sizes coming to Azure in 2019, and Ubuntu will require the following patches in order to function properly: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=29217a4746835fef35279abbd12c1a1efe83bfca https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=84fdfafab849036b5aefa52824b5cb42e887ef0e https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c8ccf7599ddac5fa48e06104c44b24709e21eed5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/controller /pci-hyperv.c?id=9bc1174280ddf7693e8c29a8f1743809e987ac37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1826447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837155] Re: xenial/linux-fips: 4.4.0-1015.20 -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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Ready for Release - phase-changed: Thursday, 01. August 2019 14:35 UTC + phase: Release + phase-changed: Thursday, 01. August 2019 14:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- ready to copy + promote-to-updates: Ongoing -- packages not yet published 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/1837155 Title: xenial/linux-fips: 4.4.0-1015.20 -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: Fix Released 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: Fix Released 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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Complete phase-changed: Thursday, 01. August 2019 14:50 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837155/+subscriptions -- Mailing list: https://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 1796292] Re: Tight timeout for bcache removal causes spurious failures
On Thu, Aug 1, 2019 at 10:15 AM Andrea Righi
wrote:
> Thanks Ryan, this is very interesting:
>
> [ 259.411486] bcache: register_bcache() error /dev/vdg: device already
> registered (emitting change event)
> [ 259.537070] bcache: register_bcache() error /dev/vdg: device already
> registered (emitting change event)
> [ 259.797830] bcache: register_bcache() error /dev/vdg: device already
> registered (emitting change event)
> [ 259.900392] bcache: register_bcache() error /dev/vdg: device already
> registered (emitting change event)
>
> It looks that we're trying to register /dev/vdg multiple times as a
> backing device (make-bcache -B). I'm not getting this message during my
> tests, so that might be required to reproduce that particular deadlock.
>
We carry a specific sauce patch to ensure that if the cacheset is already
online, and a backing device
shows up later, that the kernel emits the change event to trigger the udev
rules to generate the
symlink for /dev/bcache/by-uuid. I don't think the patch we carry is at
issue since we are just detecting
the re-register scenario and emitting a change uevent;
https://www.spinics.net/lists/linux-bcache/msg05833.html
We may want to resubmit that now to see if they'll take that or even want
to deal with the scenario
in a cleaner way;
>
> I'll modify my test case to trigger these errors and see if I can
> reproduce the hung task timeout issue.
>
I can provide you a setup to reproduce this. I'll put together a doc.
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1796292
>
> Title:
> Tight timeout for bcache removal causes spurious failures
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
>
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837155] Re: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates 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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Release - phase-changed: Thursday, 01. August 2019 14:45 UTC + phase: Complete + phase-changed: Thursday, 01. August 2019 14:50 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published 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/1837155 Title: xenial/linux-fips: 4.4.0-1015.20 -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: Fix Released 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: Fix Released 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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Complete phase-changed: Thursday, 01. August 2019 14:50 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
Chrony issue was solved in here: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1836929 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Released Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
Reproducer script
** Attachment added: "curtin-nvme.sh"
https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh
--
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838657] [NEW] 5.3: generic vDSO breaks seccomp-enabled userspace on i386
Public bug reported: https://lkml.org/lkml/2019/7/19/970 Detail at the above link. This is completely breaking ssh, among other things, which means autopkgtests are also completely broken. Patches to fix are available: https://lore.kernel.org/lkml/20190728131251.622415...@linutronix.de/ ** Affects: linux (Ubuntu) Importance: Critical Assignee: Seth Forshee (sforshee) Status: Fix Committed ** Changed in: linux (Ubuntu) Status: In Progress => 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/1838657 Title: 5.3: generic vDSO breaks seccomp-enabled userspace on i386 Status in linux package in Ubuntu: Fix Committed Bug description: https://lkml.org/lkml/2019/7/19/970 Detail at the above link. This is completely breaking ssh, among other things, which means autopkgtests are also completely broken. Patches to fix are available: https://lore.kernel.org/lkml/20190728131251.622415...@linutronix.de/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837155] Re: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- 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/1837155 Title: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Fix Released 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: Fix Released 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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Complete phase-changed: Thursday, 01. August 2019 14:50 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838113] Re: eoan/linux: 5.2.0-10.11 -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 backports: bug 1838112 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 31. July 2019 20:56 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:retry-needed + promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-hwe-edge: bug 1838112 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/1838113 Title: eoan/linux: 5.2.0-10.11 -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 package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838112 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 31. July 2019 20:56 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-hwe-edge: bug 1838112 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837617] Re: bionic/linux-fips: 4.15.0-1013.15 -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: 1837626 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 01. August 2019 02:15 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837617 Title: bionic/linux-fips: 4.15.0-1013.15 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1837626 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 01. August 2019 02:15 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838613] Re: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad
If it _only_ happens after S3, then it can be this bug: https://bugzilla.kernel.org/show_bug.cgi?id=203995 ** Bug watch added: Linux Kernel Bug Tracker #203995 https://bugzilla.kernel.org/show_bug.cgi?id=203995 -- 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/1838613 Title: two-finger scrolling fails with AlpsPS/2 ALPS DualPoint Touchpad Status in linux package in Ubuntu: Confirmed Bug description: After using the touchpad for a while, it suddenly believes that I'm doing a two-finger scroll, when I'm not. It makes the touchpad unusable : it's not possible to move the mouse anymore, vertical scrolling happens instead. I could not find an action that reliably gets me out of this mode (except reboot !). My workaround for now is to disable two-finger scrolling in "Config / Devices / Mouse & Touchpad", and enable "Edge scrolling" instead. I'm using Ubuntu 19.04 (Ubuntu 5.0.0-21.22-generic 5.0.15) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pcarbonn 1752 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 10:52:38 2019 InstallationDate: Installed on 2019-07-12 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: HP HP ZBook 15 G5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=f1861701-080f-4cd2-a32f-da146eeb4c50 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.07.01 dmi.board.name: 842A dmi.board.vendor: HP dmi.board.version: KBC Version 15.37.02 dmi.chassis.asset.tag: 5CD926C8K6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.07.01:bd06/03/2019:svnHP:pnHPZBook15G5:pvr:rvnHP:rn842A:rvrKBCVersion15.37.02:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G5 dmi.product.sku: 3AX13AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838113] Re: eoan/linux: 5.2.0-10.11 -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 backports: bug 1838112 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 31. July 2019 20:56 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-hwe-edge: bug 1838112 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/1838113 Title: eoan/linux: 5.2.0-10.11 -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 package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838112 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 31. July 2019 20:56 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-hwe-edge: bug 1838112 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837661] Re: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours
** Changed in: linux-azure (Ubuntu) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Also affects: linux-azure (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Disco) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Xenial) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure (Ubuntu Disco) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- 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/1837661 Title: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: New Status in linux-azure source package in Disco: In Progress Bug description: Can you please pick up the following 4 patches? They resolve this live migration that was reported by a mutual customer. PCI: hv: Add pci_destroy_slot() in pci_devices_present_work(), if necessary PCI: hv: Add hv_pci_remove_slots() when we unload the driver PCI: hv: Fix a memory leak in hv_eject_device_work() PCI: hv: Fix a use-after-free bug in hv_eject_device_work()pci/hv This is a known issue in linux pci-hyperv driver and is fixed by these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1837661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837600] Re: xenial/linux-fips: 4.4.0-1016.21 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed 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 -- kernel-stable-master-bug: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Packaging - phase-changed: Tuesday, 30. July 2019 17:35 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 01. August 2019 16:11 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:building 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/1837600 Title: xenial/linux-fips: 4.4.0-1016.21 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in 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 -- kernel-stable-master-bug: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 01. August 2019 16:11 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837661] Re: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours
I meant Bionic on the 5.0 kernel, not Xenial. -- 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/1837661 Title: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: New Status in linux-azure source package in Disco: In Progress Bug description: Can you please pick up the following 4 patches? They resolve this live migration that was reported by a mutual customer. PCI: hv: Add pci_destroy_slot() in pci_devices_present_work(), if necessary PCI: hv: Add hv_pci_remove_slots() when we unload the driver PCI: hv: Fix a memory leak in hv_eject_device_work() PCI: hv: Fix a use-after-free bug in hv_eject_device_work()pci/hv This is a known issue in linux pci-hyperv driver and is fixed by these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1837661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837661] Re: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours
Joseph, I think we also need these on Xenial, is that correct? -- 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/1837661 Title: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: New Status in linux-azure source package in Disco: In Progress Bug description: Can you please pick up the following 4 patches? They resolve this live migration that was reported by a mutual customer. PCI: hv: Add pci_destroy_slot() in pci_devices_present_work(), if necessary PCI: hv: Add hv_pci_remove_slots() when we unload the driver PCI: hv: Fix a memory leak in hv_eject_device_work() PCI: hv: Fix a use-after-free bug in hv_eject_device_work()pci/hv This is a known issue in linux pci-hyperv driver and is fixed by these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1837661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838324] Re: 4.15.0-55 Kernel Breaks Wifi
I cannot upload log files as I did not have working wifi and no access to wired Ethernet. If required, I could reinstall the kernel again then run the command and save the output after downgrading again. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838324 Title: 4.15.0-55 Kernel Breaks Wifi Status in linux package in Ubuntu: Confirmed Bug description: Network controller: Broadcom Inc. and subsidiaries BCM43228 802.11a/b/g/n Thinkpad T430U Wifi was not operational using kernel 4.15.0-55: no list of available networks and rfkill output indicated there were no hard or soft blocks. Reverted back to 4.10.0-38 to restore functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837661] Re: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours
I believe the question is indeed regarding xenial. Bionic will get the fixes via disco. But I would like to know if that should also be backported to the 4.15 azure kernel in xenial as well? -- 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/1837661 Title: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: New Status in linux-azure source package in Disco: In Progress Bug description: Can you please pick up the following 4 patches? They resolve this live migration that was reported by a mutual customer. PCI: hv: Add pci_destroy_slot() in pci_devices_present_work(), if necessary PCI: hv: Add hv_pci_remove_slots() when we unload the driver PCI: hv: Fix a memory leak in hv_eject_device_work() PCI: hv: Fix a use-after-free bug in hv_eject_device_work()pci/hv This is a known issue in linux pci-hyperv driver and is fixed by these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1837661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837600] Re: xenial/linux-fips: 4.4.0-1016.21 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 01. August 2019 16:11 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837600 Title: xenial/linux-fips: 4.4.0-1016.21 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in 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 -- kernel-stable-master-bug: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 01. August 2019 16:11 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838113] Re: eoan/linux: 5.2.0-10.11 -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/automated-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 backports: bug 1838112 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Promote to Proposed - phase-changed: Wednesday, 31. July 2019 20:56 UTC + phase: Testing + phase-changed: Thursday, 01. August 2019 17:41 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 trackers: bionic/linux-hwe-edge: bug 1838112 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/1838113 Title: eoan/linux: 5.2.0-10.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838112 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 01. August 2019 17:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1838112 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838677] [NEW] shiftfs: allow overlayfs
Public bug reported: SRU Justification Impact: Currently it is not possible to use overlayfs on top of shiftfs. This means Docker inside of LXD cannot make user of the overlay2 graph driver which is blocking users such as Travis from making use of it efficiently. Regression Potential: Limited to shiftfs and overlayfs on top of shiftfs. Overlayfs does prevent "remote" filesystems such as ceph, nfs, etc. from being used as the underlay. With this patch shiftfs however can be used as an underlay and we special case it as a suitable filesystem to be used under overlayfs. I verified that the patch does not lead to regression on overlayfs workloads that do not make use of shiftfs as underlay. Additionally, I tested Docker with the overlay2 graphdriver on top of shiftfs. This also has not lead to any regressions. Test case: Building a kernel with the patch: sudo snap install lxd sudo lxd init sudo lxc launch images:ubuntu/bionic b1 sudo lxc config set b1 security.nesting true sudo lxc restart --force b1 sudo lxc shell b1 sudo apt-get install \ apt-transport-https \ ca-certificates \ curl \ gnupg-agent \ software-properties-common curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - curl -fsSL get.docker.com | CHANNEL=test sh sudo add-apt-repository \ "deb [arch=amd64] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) \ stable" sudo apt-get update sudo apt-get install docker-ce docker-ce-cli containerd.io sudo systemctl stop docker cat < Christian Brauner (cbrauner) ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1838677 Title: shiftfs: allow overlayfs Status in linux package in Ubuntu: In Progress Bug description: SRU Justification Impact: Currently it is not possible to use overlayfs on top of shiftfs. This means Docker inside of LXD cannot make user of the overlay2 graph driver which is blocking users such as Travis from making use of it efficiently. Regression Potential: Limited to shiftfs and overlayfs on top of shiftfs. Overlayfs does prevent "remote" filesystems such as ceph, nfs, etc. from being used as the underlay. With this patch shiftfs however can be used as an underlay and we special case it as a suitable filesystem to be used under overlayfs. I verified that the patch does not lead to regression on overlayfs workloads that do not make use of shiftfs as underlay. Additionally, I tested Docker with the overlay2 graphdriver on top of shiftfs. This also has not lead to any regressions. Test case: Building a kernel with the patch: sudo snap install lxd sudo lxd init sudo lxc launch images:ubuntu/bionic b1 sudo lxc config set b1 security.nesting true sudo lxc restart --force b1 sudo lxc shell b1 sudo apt-get install \ apt-transport-https \ ca-certificates \ curl \ gnupg-agent \ software-properties-common curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - curl -fsSL get.docker.com | CHANNEL=test sh sudo add-apt-repository \ "deb [arch=amd64] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) \ stable" sudo apt-get update sudo apt-get install docker-ce docker-ce-cli containerd.io sudo systemctl stop docker cat
[Kernel-packages] [Bug 1838677] Re: shiftfs: allow overlayfs
SRU request here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838677 Patchset here: https://github.com/brauner/ubuntu-disco/tree/overlayfs_on_shiftfs Mailing list patchset posting here: https://lists.ubuntu.com/archives/kernel-team/2019-August/102741.html ** Tags added: shiftfs -- 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/1838677 Title: shiftfs: allow overlayfs Status in linux package in Ubuntu: In Progress Bug description: SRU Justification Impact: Currently it is not possible to use overlayfs on top of shiftfs. This means Docker inside of LXD cannot make user of the overlay2 graph driver which is blocking users such as Travis from making use of it efficiently. Regression Potential: Limited to shiftfs and overlayfs on top of shiftfs. Overlayfs does prevent "remote" filesystems such as ceph, nfs, etc. from being used as the underlay. With this patch shiftfs however can be used as an underlay and we special case it as a suitable filesystem to be used under overlayfs. I verified that the patch does not lead to regression on overlayfs workloads that do not make use of shiftfs as underlay. Additionally, I tested Docker with the overlay2 graphdriver on top of shiftfs. This also has not lead to any regressions. Test case: Building a kernel with the patch: sudo snap install lxd sudo lxd init sudo lxc launch images:ubuntu/bionic b1 sudo lxc config set b1 security.nesting true sudo lxc restart --force b1 sudo lxc shell b1 sudo apt-get install \ apt-transport-https \ ca-certificates \ curl \ gnupg-agent \ software-properties-common curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - curl -fsSL get.docker.com | CHANNEL=test sh sudo add-apt-repository \ "deb [arch=amd64] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) \ stable" sudo apt-get update sudo apt-get install docker-ce docker-ce-cli containerd.io sudo systemctl stop docker cat
[Kernel-packages] [Bug 1824719] Re: shiftfs: Allow stacking overlayfs on top
SRU request here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838677 Patchset here: https://github.com/brauner/ubuntu-disco/tree/overlayfs_on_shiftfs Mailing list patchset posting here: https://lists.ubuntu.com/archives/kernel-team/2019-August/102741.html ** Changed in: linux (Ubuntu) Status: Triaged => 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/1824719 Title: shiftfs: Allow stacking overlayfs on top Status in linux package in Ubuntu: In Progress Bug description: Shiftfs right now prevents stacking overlayfs on top of it which unfortunately means all users of Docker as well as some nested LXC users which aren't using btrfs are going to break when they get switched over to shiftfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837600] Re: xenial/linux-fips: 4.4.0-1016.21 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 01. August 2019 16:11 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837600 Title: xenial/linux-fips: 4.4.0-1016.21 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in 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 -- kernel-stable-master-bug: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 01. August 2019 16:11 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances
** Changed in: charm-neutron-openvswitch Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834213 Title: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances Status in OpenStack neutron-openvswitch charm: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: With an environment running Xenial-Queens, and having just upgraded the linux-image-generic kernel for MDS patching, a few of our hypervisor hosts that were rebooted (3 out of 100) ended up dropping IP (tcp/udp) ingress traffic. It turns out that nf_conntrack module was loaded, but nf_conntrack_ipv4 was not loading, and the traffic was being dropped by this rule: table=72, n_packets=214989, priority=50,ct_state=+inv+trk actions=resubmit(,93) The ct_state "inv" means invalid conntrack state, which the manpage describes as: The state is invalid, meaning that the connection tracker couldn’t identify the connection. This flag is a catch- all for problems in the connection or the connection tracker, such as: • L3/L4 protocol handler is not loaded/unavailable. With the Linux kernel datapath, this may mean that the nf_conntrack_ipv4 or nf_conntrack_ipv6 modules are not loaded. • L3/L4 protocol handler determines that the packet is malformed. • Packets are unexpected length for protocol. It appears that there may be an issue when patching the OS of a hypervisor not running instances may fail to update initrd to load nf_conntrack_ipv4 (and/or _ipv6). I couldn't find anywhere in the charm code that this would be loaded unless the charm's "harden" option is used on nova-compute charm (see charmhelpers contrib/host templates). It is unset in our environment, so we are not using any special module probing. Did nf_conntrack_ipv4 get split out from nf_conntrack in recent kernel upgrades or is it possible that the charm should define a modprobe file if we have the OVS firewall driver configured? To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832795] Re: updates to aufs
Sorry for the delay, test builds are available at https://people.canonical.com/~sforshee/lp1832795. Please confirm that the bug is fixed, 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/1832795 Title: Race in aufs leads to use-after-free Status in linux package in Ubuntu: Confirmed Bug description: I have found and reported a critical bug in aufs (as shipped with the latest Ubuntu kernels, both on Bionic and Xenial), which potentially affects anyone running Docker on Ubuntu using aufs graph driver. The fix has been developed, tested at least by me to fix the issue, and committed into upstream aufs git repos The nature of the bug is, in case of multiple parallels aufs mounts and unmounts, the kernel can screw up krefs, and once that happens, the only remedy is to reboot it (as commands like mount/umount or cat /proc/mounts are all stuck in syscalls). I would appreciate syncing aufs with the latest upstream release from git, as it was done a few times already, or at least taking the below fix (whatever suits maintainers better). The fixed versions are the ones marked with 20190610, and from what I see they are available for all kernel versions since 4.14 (for example, 4.15 tree is here: https://github.com/sfjro/aufs4-standalone/commits/aufs4.15). For 4.4, a backport might be needed, but it should be trivial. Original bug report: https://sourceforge.net/p/aufs/mailman/message/36680389/ Fix: https://github.com/sfjro/aufs4-linux/commit/b633d7b2635b9615fe294b85257d05008e3747a3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832795] Re: Race in aufs leads to use-after-free
** Summary changed: - updates to aufs + Race in aufs leads to use-after-free ** Description changed: + SRU Justification + + Impact: A race in aufs can result in use of a DYNOP object which is + being freed after its reference count reaches 0, leading to an oops. + + Fix: Upstream fix to aufs to ignore objects whose reference count is 0. + + Regression Potential: Low, limited to aufs and confirmed in testing to + fix the issue. + + --- + I have found and reported a critical bug in aufs (as shipped with the latest Ubuntu kernels, both on Bionic and Xenial), which potentially affects anyone running Docker on Ubuntu using aufs graph driver. The fix has been developed, tested at least by me to fix the issue, and committed into upstream aufs git repos The nature of the bug is, in case of multiple parallels aufs mounts and unmounts, the kernel can screw up krefs, and once that happens, the only remedy is to reboot it (as commands like mount/umount or cat /proc/mounts are all stuck in syscalls). I would appreciate syncing aufs with the latest upstream release from git, as it was done a few times already, or at least taking the below fix (whatever suits maintainers better). The fixed versions are the ones marked with 20190610, and from what I see they are available for all kernel versions since 4.14 (for example, 4.15 tree is here: https://github.com/sfjro/aufs4-standalone/commits/aufs4.15). For 4.4, a backport might be needed, but it should be trivial. Original bug report: https://sourceforge.net/p/aufs/mailman/message/36680389/ Fix: https://github.com/sfjro/aufs4-linux/commit/b633d7b2635b9615fe294b85257d05008e3747a3 -- 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/1832795 Title: Race in aufs leads to use-after-free Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification Impact: A race in aufs can result in use of a DYNOP object which is being freed after its reference count reaches 0, leading to an oops. Fix: Upstream fix to aufs to ignore objects whose reference count is 0. Regression Potential: Low, limited to aufs and confirmed in testing to fix the issue. --- I have found and reported a critical bug in aufs (as shipped with the latest Ubuntu kernels, both on Bionic and Xenial), which potentially affects anyone running Docker on Ubuntu using aufs graph driver. The fix has been developed, tested at least by me to fix the issue, and committed into upstream aufs git repos The nature of the bug is, in case of multiple parallels aufs mounts and unmounts, the kernel can screw up krefs, and once that happens, the only remedy is to reboot it (as commands like mount/umount or cat /proc/mounts are all stuck in syscalls). I would appreciate syncing aufs with the latest upstream release from git, as it was done a few times already, or at least taking the below fix (whatever suits maintainers better). The fixed versions are the ones marked with 20190610, and from what I see they are available for all kernel versions since 4.14 (for example, 4.15 tree is here: https://github.com/sfjro/aufs4-standalone/commits/aufs4.15). For 4.4, a backport might be needed, but it should be trivial. Original bug report: https://sourceforge.net/p/aufs/mailman/message/36680389/ Fix: https://github.com/sfjro/aufs4-linux/commit/b633d7b2635b9615fe294b85257d05008e3747a3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838395] Re: disco/linux: 5.0.0-24.25 -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 in Ubuntu. https://bugs.launchpad.net/bugs/1838395 Title: disco/linux: 5.0.0-24.25 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838393 (bionic/linux-hwe), bug 1838398 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837565 (linux-aws), bug 1837567 (linux-azure), bug 1837571 (linux-gcp), bug 1837572 (linux-kvm), bug 1837573 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 01. August 2019 09:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1838393 bionic/linux-oem-osp1: bug 1838398 disco/linux-aws: bug 1837565 disco/linux-azure: bug 1837567 disco/linux-gcp: bug 1837571 disco/linux-kvm: bug 1837572 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837573] Re: disco/linux-snapdragon: 5.0.0-1018.19 -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-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1837573 Title: disco/linux-snapdragon: 5.0.0-1018.19 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Tuesday, 30. July 2019 22:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-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/1837573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
