[Kernel-packages] [Bug 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot
Hi Adam: Could you try 4.19 kernel with i2c_i801 loaded? http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19/ to see if it 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/1802689 Title: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in kmod source package in Xenial: Fix Committed Status in linux source package in Xenial: Incomplete Status in kmod source package in Bionic: Fix Committed Status in linux source package in Bionic: Incomplete Status in kmod source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Incomplete Bug description: After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it hangs on boot. After blacklisting i2c_i801 everything works great again. I realize that this was a fix for bug 1786574, and that helps some other folks out. I'm not sure what the right fix is but there's got to be something that works for everyone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802558] Re: linux-aws: 4.15.0-1028.29 -proposed tracker
4.15.0-1028.29 - aws Regression test CMPL, RTB. Issue to note in x86_64 (aws): monotonic_time - failed on m5a.large ubuntu_kvm_unit_tests - test skipped due to no KVM support ubuntu_ltp - test disabled ubuntu_ltp_syscalls - fanotify09 case 2 (bug 1804594) fanotify10 (bug 1802454) quotactl01 (quota not working on AWS) inotify08 (bug 1775784) msgstress03 (bug 1783881) Skipped / blacklisted: * libhugetlbfs * ubuntu_quota_smoke_test * ubuntu_seccomp * ubuntu_zram_smoke_test -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1802558 Title: linux-aws: 4.15.0-1028.29 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802636] Re: REGRESSION: only one displayport fron docking station is used at a time
** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802636 Title: REGRESSION: only one displayport fron docking station is used at a time Status in linux package in Ubuntu: Incomplete Bug description: When my HP 840 G3 is connected to its docking station only one DisplayPort is used at a time. If I disconnect the one in use, the other is enabled. Only one display is detected. I'm using a fresh installation of Ubuntu 18.10. Before, on 18.04, it worked. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 10 12:49:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] InstallationDate: Installed on 2018-11-01 (9 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7054 Lite-On Technology Corp. Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 03f0:521d Hewlett-Packard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 840 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=1203967d-3709-4fd4-966f-4c08b53203ce ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2017 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.16 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.76 dmi.chassis.asset.tag: 5CG7320Q91 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.16:bd06/08/2017:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.76:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G3 dmi.product.sku: L3C65AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802749] Re: linux-aws: 4.18.0-1005.6 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED - regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1802749 Title: linux-aws: 4.18.0-1005.6 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802749/+subscriptions -- Mailing list: https://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 1787405] Comment bridged from LTC Bugzilla
On Thu, Nov 22, 2018 at 6:35 PM bugproxy wrote:
> --- Comment From boris_fiuczyn...@de.ibm.com 2018-11-22 12:21
> EDT---
> @Christian E.:
> You listed two libvirt commit IDs
>
> https://libvirt.org/git/?p=libvirt.git;a=commit;h=faab373b53e1a4eacf0d6f524eb47df243f21fac
>
> https://libvirt.org/git/?p=libvirt.git;a=commit;h=f865d58028ccd568b6e7909608678584b12d3c90
> that I cannot find in libvirt. Maybe it's just a copy&paste error.
>
Hmm, yeah that was copy-pasta :-/
The files in my branch are actually good already for completeness here on
the bug the patches that work unmodified on 4.6 are:
https://libvirt.org/git/?p=libvirt.git;a=commit;h=11708641983e9107a129c62fd343d0fec228342f
https://libvirt.org/git/?p=libvirt.git;a=commit;h=208d6e6f5aafa102d04ce300c6338b0736bb52df
https://libvirt.org/git/?p=libvirt.git;a=commit;h=25dde373730545894f60ce5b1497f19d61714c69
I just looked at patch 6 again and it is correct that I have included
> code from another commit (most likely
> d54e45b6edd7623e488a19e30bc4148a21fa8b03) to make the refactoring work
> and compile without noting it down as origin in the commit message.
> Sorry about that.
>
No problem at all.
d54e45b6 is qemuDomainMdevDefValidate which is in patch #5 actually already.
But #6 is is qemuDomainMdevDefVFIOAPValidate from 25dde373 and the
extension for AP in 208d6e6f fused into one.
But that is ok, an SRU wants to only pick what is needed and not rework all
the rest - I just wanted to make sure references are ok.
It is mostly for housekeeping and to make it "traceable" for the upcoming
SRU review.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1787405
Title:
[FEAT] Guest-dedicated Crypto Adapters
Status in Ubuntu on IBM z Systems:
In Progress
Status in libvirt package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in qemu package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Bug description:
== SRU Justification ==
(Kernel SRU)
Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to
a KVM guest such that the hypervisor cannot observe the communication of the
guest with the device.
(Since all kernel patches/commits are from kernel 4.19, they will
automagically land in 'Disco'.)
== Fix ==
9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
e585b24 ("KVM: s390: refactor crypto initialization")
1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
4210459 ("KVM: s390: interface to clear CRYCB masks")
258287c ("s390: vfio-ap: implement mediated device open callback")
e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
46a7263 ("s390: vfio-ap: zeroize the AP queues")
cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
112c24d ("KVM: s390: CPU model support for AP virtualization")
492a6be ("s390: doc: detailed specifications for AP virtualization")
<-- till here in 'kvm/next'
(https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->
8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
0e237e4 ("KVM: s390: Tracing APCB changes")
76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")
<-- till here in 'kvms390/next'
(https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
-->
<-- In addition to that some prereqs for the 'ap/crypto' driver are
necessary -->
ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
df80c03 ("s390/zcrypt: Review inline assembler constraints.")
f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
7e0bdbe ("s390/zcrypt: AP bus supp
[Kernel-packages] [Bug 1802749] Re: linux-aws: 4.18.0-1005.6 -proposed tracker
4.18.0-1005.6 - aws Regression test CMPL, RTB. Issue to note in x86_64 (aws): ubuntu_kvm_unit_tests - test skipped due to no KVM support ubuntu_ltp - test disabled ubuntu_ltp_syscalls - quotactl01 failed (not supported on AWS) fanotify case 2 (bug 1804594) msgstress03 (bug 1783881) inotify09 timeouted on slow machine (bug 1782758) ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack (bug 1803921) Skipped / blacklisted: * libhugetlbfs * ubuntu_quota_smoke_test * ubuntu_seccomp * ubuntu_zram_smoke_test ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1802749 Title: linux-aws: 4.18.0-1005.6 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803275] Re: nvidia-kernel-source-390 390.87-0ubuntu2: nvidia kernel module failed to build [error: implicit declaration of function ‘drm_connector_attach_encoder’]
Try and push this along. Is this a packaging error ? As the Xorg file indicates: 4.976] (==) ModulePath set to "/usr/lib/xorg/modules" However, the nvidia directive does not exist there: sysop@x1904:~$ ls -al /usr/lib/xorg/modules total 864 drwxr-xr-x 5 root root 4096 Nov 14 23:26 . drwxr-xr-x 3 root root 4096 Nov 14 23:26 .. drwxr-xr-x 2 root root 4096 Nov 22 17:40 drivers drwxr-xr-x 2 root root 4096 Nov 14 23:26 extensions drwxr-xr-x 2 root root 4096 Oct 16 23:44 input -rw-r--r-- 1 root root 101040 Oct 25 09:53 libexa.so -rw-r--r-- 1 root root 22792 Oct 25 09:53 libfbdevhw.so -rw-r--r-- 1 root root 109360 Oct 25 09:53 libfb.so -rw-r--r-- 1 root root 217048 Oct 25 09:53 libglamoregl.so -rw-r--r-- 1 root root 146088 Oct 25 09:53 libint10.so -rw-r--r-- 1 root root 14472 Oct 25 09:53 libshadowfb.so -rw-r--r-- 1 root root 39112 Oct 25 09:53 libshadow.so -rw-r--r-- 1 root root 31120 Oct 25 09:53 libvbe.so -rw-r--r-- 1 root root 35880 Oct 25 09:53 libvgahw.so -rw-r--r-- 1 root root 133904 Oct 25 09:53 libwfb.so sysop@x1904:~$ Looking in /drivers and no nvidia file there either: sysop@x1904:~$ ls -al /usr/lib/xorg/modules/drivers/ total 3064 drwxr-xr-x 2 root root4096 Nov 22 17:40 . drwxr-xr-x 5 root root4096 Nov 14 23:26 .. -rw-r--r-- 1 root root 160864 Sep 18 02:23 amdgpu_drv.so -rw-r--r-- 1 root root 14504 Sep 18 03:54 ati_drv.so -rw-r--r-- 1 root root 27648 Oct 4 02:11 fbdev_drv.so -rw-r--r-- 1 root root 1686056 Oct 11 03:39 intel_drv.so -rw-r--r-- 1 root root 68 Oct 25 09:53 modesetting_drv.so -rw-r--r-- 1 root root 212968 Jun 25 11:39 nouveau_drv.so -rw-r--r-- 1 root root 180840 May 23 2018 qxl_drv.so -rw-r--r-- 1 root root 514336 Sep 18 03:54 radeon_drv.so -rw-r--r-- 1 root root 31784 Aug 18 06:42 vesa_drv.so -rw-r--r-- 1 root root 170168 May 28 00:57 vmware_drv.so sysop@x1904:~$ Mind you, I do not know, but seems logical the nvidia_drv.so should be pointed to. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1803275 Title: nvidia-kernel-source-390 390.87-0ubuntu2: nvidia kernel module failed to build [error: implicit declaration of function ‘drm_connector_attach_encoder’] Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Loading new nvidia-390.87 DKMS files... Building for 4.18.0-10-generic Building for architecture x86_64 Building initial module for 4.18.0-10-generic Error! Bad return status for module build on kernel: 4.18.0-10-generic (x86_64) Consult /var/lib/dkms/nvidia/390.87/build/make.log for more information. dpkg: error processing package nvidia-dkms-390 (--configure): installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Setting up libnvidia-gl-390:i386 (390.87-0ubuntu2) ... Setting up libnvidia-gl-390:amd64 (390.87-0ubuntu2) ... Setting up hplip (3.18.10+dfsg0-3) ... Creating/updating hplip user account... dpkg: dependency problems prevent configuration of nvidia-driver-390: nvidia-driver-390 depends on nvidia-dkms-390 (= 390.87-0ubuntu2); however: Package nvidia-dkms-390 is not configured yet. dpkg: error processing package nvidia-driver-390 (--configure): dependency problems - leaving unconfigured Setting up printer-driver-postscript-hp (3.18.10+dfsg0-3) ... No apport report written because the error message indicates its a followup error from a previous failure. Setting up libnvidia-ifr1-390:amd64 (390.87-0ubuntu2) ... Setting up libnvidia-ifr1-390:i386 (390.87-0ubuntu2) ... Processing triggers for initramfs-tools (0.131ubuntu15) ... update-initramfs: Generating /boot/initrd.img-4.18.0-10-generic Processing triggers for libc-bin (2.28-0ubuntu1) ... Errors were encountered while processing: nvidia-dkms-390 nvidia-driver-390 E: Sub-process /usr/bin/dpkg returned an error code (1) sysop@x1904:~$ ProblemType: Package DistroRelease: Ubuntu 19.04 Package: nvidia-kernel-source-390 390.87-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 DKMSKernelVersion: 4.18.0-10-generic Date: Tue Nov 13 22:56:33 2018 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-390:390.87-0ubuntu2:/var/lib/dkms/nvidia/390.87/build/nvidia-drm/nvidia-drm-encoder.c:223:11: error: implicit declaration of function ‘drm_connector_attach_encoder’; did you mean ‘drm_mode_connector_attach_encoder’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2018-05-20 (177 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180520) PackageVersion: 390.87-0ubuntu2 Python3Details: /usr/bin/python3.7, Python 3.7.1, python
[Kernel-packages] [Bug 1804748] 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 1804748 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804748 Title: s390x qemu vt220 terminal, tput cols and lines is wrong Status in linux package in Ubuntu: Incomplete Status in ncurses package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: s390x qemu vt220 terminal, tput cols and lines is reported as 80x24, whilst that's not true. The number of columns is semi-true, as the shell wraps them, however, one can print things beyond 80 cols. Ideally resizing qemu window, should manage to report the actual number of lines and columns to the underlying terminal. Similarly, one should be able to resize ASCII terminal window in HMC beyond 80x24. These days everyone has HD widescreen monitors, there is no reason to limit to 80x24. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804748] Re: s390x qemu vt220 terminal, tput cols and lines is wrong
tput reset -> breaks the terminal resizing the qemu window -> fixes things Thus e.g. SIGWINCH is probably handled correctly. However it seems like there is terminal definitions missing or something. ** Tags added: s390x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804748 Title: s390x qemu vt220 terminal, tput cols and lines is wrong Status in linux package in Ubuntu: New Status in ncurses package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: s390x qemu vt220 terminal, tput cols and lines is reported as 80x24, whilst that's not true. The number of columns is semi-true, as the shell wraps them, however, one can print things beyond 80 cols. Ideally resizing qemu window, should manage to report the actual number of lines and columns to the underlying terminal. Similarly, one should be able to resize ASCII terminal window in HMC beyond 80x24. These days everyone has HD widescreen monitors, there is no reason to limit to 80x24. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804748] [NEW] s390x qemu vt220 terminal, tput cols and lines is wrong
Public bug reported: s390x qemu vt220 terminal, tput cols and lines is reported as 80x24, whilst that's not true. The number of columns is semi-true, as the shell wraps them, however, one can print things beyond 80 cols. Ideally resizing qemu window, should manage to report the actual number of lines and columns to the underlying terminal. Similarly, one should be able to resize ASCII terminal window in HMC beyond 80x24. These days everyone has HD widescreen monitors, there is no reason to limit to 80x24. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: ncurses (Ubuntu) Importance: Undecided Status: New ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2018-11-23 03-31-40.png" https://bugs.launchpad.net/bugs/1804748/+attachment/5215498/+files/Screenshot%20from%202018-11-23%2003-31-40.png ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804748 Title: s390x qemu vt220 terminal, tput cols and lines is wrong Status in linux package in Ubuntu: New Status in ncurses package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: s390x qemu vt220 terminal, tput cols and lines is reported as 80x24, whilst that's not true. The number of columns is semi-true, as the shell wraps them, however, one can print things beyond 80 cols. Ideally resizing qemu window, should manage to report the actual number of lines and columns to the underlying terminal. Similarly, one should be able to resize ASCII terminal window in HMC beyond 80x24. These days everyone has HD widescreen monitors, there is no reason to limit to 80x24. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
corentin barbu, please file a new bug as Precision 7530 uses a different touchpad. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804706] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1804706/+attachment/5215390/+files/ProcEnviron.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804706 Title: CONFIG_HSA_AMD has moved and is therefore no longer being set at kernel build for kernels >= 4.20 Status in linux package in Ubuntu: Confirmed Bug description: Hello. Due to recent changes that amount to merging the amdkfd kernel module into amdgpu (for context, see https://lists.freedesktop.org/archives/amd-gfx/2018-August/025719.html), the CONFIG_HSA_AMD option moved from the Display Interface Bridges kernel build option group to the Display Engine group. It appears that as a consequence of this the option is no longer being set when building the kernel (see for example http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc3/). This breaks client software such as https://github.com/RadeonOpenCompute/ROCm. It would be extremely helpful if this behaviour was corrected to match existing practice i.e. CONFIG_HSA_AMD is set. Thank you. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-15 (280 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: linux (not installed) Tags: wayland-session cosmic Uname: Linux 4.20.0-042000rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804706] Re: CONFIG_HSA_AMD has moved and is therefore no longer being set at kernel build for kernels >= 4.20
apport information ** Tags added: apport-collected cosmic wayland-session ** Description changed: Hello. - Due to recent changes that amount to merging the amdkfd kernel module - into amdgpu (for context, see https://lists.freedesktop.org/archives - /amd-gfx/2018-August/025719.html), the CONFIG_HSA_AMD option moved from - the Display Interface Bridges kernel build option group to the Display - Engine group. It appears that as a consequence of this the option is no - longer being set when building the kernel (see for example - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc3/). This breaks - client software such as https://github.com/RadeonOpenCompute/ROCm. It - would be extremely helpful if this behaviour was corrected to match - existing practice i.e. CONFIG_HSA_AMD is set. Thank you. + Due to recent changes that amount to merging the amdkfd kernel module into amdgpu (for context, see https://lists.freedesktop.org/archives/amd-gfx/2018-August/025719.html), the CONFIG_HSA_AMD option moved from the Display Interface Bridges kernel build option group to the Display Engine group. It appears that as a consequence of this the option is no longer being set when building the kernel (see for example http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc3/). This breaks client software such as https://github.com/RadeonOpenCompute/ROCm. It would be extremely helpful if this behaviour was corrected to match existing practice i.e. CONFIG_HSA_AMD is set. Thank you. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13.1 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.10 + InstallationDate: Installed on 2018-02-15 (280 days ago) + InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + Package: linux (not installed) + Tags: wayland-session cosmic + Uname: Linux 4.20.0-042000rc3-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1804706/+attachment/5215389/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804706 Title: CONFIG_HSA_AMD has moved and is therefore no longer being set at kernel build for kernels >= 4.20 Status in linux package in Ubuntu: Confirmed Bug description: Hello. Due to recent changes that amount to merging the amdkfd kernel module into amdgpu (for context, see https://lists.freedesktop.org/archives/amd-gfx/2018-August/025719.html), the CONFIG_HSA_AMD option moved from the Display Interface Bridges kernel build option group to the Display Engine group. It appears that as a consequence of this the option is no longer being set when building the kernel (see for example http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc3/). This breaks client software such as https://github.com/RadeonOpenCompute/ROCm. It would be extremely helpful if this behaviour was corrected to match existing practice i.e. CONFIG_HSA_AMD is set. Thank you. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-15 (280 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: linux (not installed) Tags: wayland-session cosmic Uname: Linux 4.20.0-042000rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
Similar problem here on brand new Dell precision 7530 sold with Ubuntu 16.04... uname -a: Linux atlas 4.15.0-39-generic #42~16.04.1-Ubuntu SMP Wed Oct 24 17:09:54 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux The two finger scrolling -and tap to click- stops working after suspend but none of the temporary or supposedly permanent fixes listed in #86 work, no "blacklist i2c_*" in /etc/modprobe.d/blacklist.conf either. t -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804706] 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 1804706 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804706 Title: CONFIG_HSA_AMD has moved and is therefore no longer being set at kernel build for kernels >= 4.20 Status in linux package in Ubuntu: Incomplete Bug description: Hello. Due to recent changes that amount to merging the amdkfd kernel module into amdgpu (for context, see https://lists.freedesktop.org/archives /amd-gfx/2018-August/025719.html), the CONFIG_HSA_AMD option moved from the Display Interface Bridges kernel build option group to the Display Engine group. It appears that as a consequence of this the option is no longer being set when building the kernel (see for example http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc3/). This breaks client software such as https://github.com/RadeonOpenCompute/ROCm. It would be extremely helpful if this behaviour was corrected to match existing practice i.e. CONFIG_HSA_AMD is set. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804706] [NEW] CONFIG_HSA_AMD has moved and is therefore no longer being set at kernel build for kernels >= 4.20
Public bug reported: Hello. Due to recent changes that amount to merging the amdkfd kernel module into amdgpu (for context, see https://lists.freedesktop.org/archives /amd-gfx/2018-August/025719.html), the CONFIG_HSA_AMD option moved from the Display Interface Bridges kernel build option group to the Display Engine group. It appears that as a consequence of this the option is no longer being set when building the kernel (see for example http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc3/). This breaks client software such as https://github.com/RadeonOpenCompute/ROCm. It would be extremely helpful if this behaviour was corrected to match existing practice i.e. CONFIG_HSA_AMD is set. Thank you. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug ** Attachment added: "version_and_lspci.tar.xz" https://bugs.launchpad.net/bugs/1804706/+attachment/5215388/+files/version_and_lspci.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804706 Title: CONFIG_HSA_AMD has moved and is therefore no longer being set at kernel build for kernels >= 4.20 Status in linux package in Ubuntu: New Bug description: Hello. Due to recent changes that amount to merging the amdkfd kernel module into amdgpu (for context, see https://lists.freedesktop.org/archives /amd-gfx/2018-August/025719.html), the CONFIG_HSA_AMD option moved from the Display Interface Bridges kernel build option group to the Display Engine group. It appears that as a consequence of this the option is no longer being set when building the kernel (see for example http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc3/). This breaks client software such as https://github.com/RadeonOpenCompute/ROCm. It would be extremely helpful if this behaviour was corrected to match existing practice i.e. CONFIG_HSA_AMD is set. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Ubuntu 18.10 with 4.18.0-11-generic #12-Ubuntu SMP Tue Oct 23 19:22:37
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux has the same problems
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
C'mon guys, this stuff is hopeless. As I said, I'm using Linux Mint. It lacks the /etc/gdm3 folder - perhaps because (I don't know) it uses a different 'greeter'. Nor does Mint use Wayland. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No As
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Try this: 1. Edit /etc/gdm3/custom.conf as root/with sudo 2. Uncomment the line WaylandEnable=false so it looks like below: [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false 3. Reboot and see if the issue still occurs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: L
[Kernel-packages] [Bug 1787405] Comment bridged from LTC Bugzilla
--- Comment From boris_fiuczyn...@de.ibm.com 2018-11-22 12:21 EDT---
@Christian E.:
You listed two libvirt commit IDs
https://libvirt.org/git/?p=libvirt.git;a=commit;h=faab373b53e1a4eacf0d6f524eb47df243f21fac
https://libvirt.org/git/?p=libvirt.git;a=commit;h=f865d58028ccd568b6e7909608678584b12d3c90
that I cannot find in libvirt. Maybe it's just a copy&paste error.
I just looked at patch 6 again and it is correct that I have included
code from another commit (most likely
d54e45b6edd7623e488a19e30bc4148a21fa8b03) to make the refactoring work
and compile without noting it down as origin in the commit message.
Sorry about that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1787405
Title:
[FEAT] Guest-dedicated Crypto Adapters
Status in Ubuntu on IBM z Systems:
In Progress
Status in libvirt package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in qemu package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Bug description:
== SRU Justification ==
(Kernel SRU)
Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to
a KVM guest such that the hypervisor cannot observe the communication of the
guest with the device.
(Since all kernel patches/commits are from kernel 4.19, they will
automagically land in 'Disco'.)
== Fix ==
9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
e585b24 ("KVM: s390: refactor crypto initialization")
1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
4210459 ("KVM: s390: interface to clear CRYCB masks")
258287c ("s390: vfio-ap: implement mediated device open callback")
e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
46a7263 ("s390: vfio-ap: zeroize the AP queues")
cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
112c24d ("KVM: s390: CPU model support for AP virtualization")
492a6be ("s390: doc: detailed specifications for AP virtualization")
<-- till here in 'kvm/next'
(https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->
8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
0e237e4 ("KVM: s390: Tracing APCB changes")
76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")
<-- till here in 'kvms390/next'
(https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
-->
<-- In addition to that some prereqs for the 'ap/crypto' driver are
necessary -->
ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
df80c03 ("s390/zcrypt: Review inline assembler constraints.")
f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")
<--
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
-->
== PATCH ==
Above git commits are all from 4.19.
The git commands for 4.18 would be:
$ git cherry-pick
(112c24d "KVM: s390: CPU model support for AP virtualization" may have
a trivial merge conflict with the etoken patch)
$ git cherry-pick
$ git cherry-pick
== Regression Potential ==
Low to mid:
- mid because in summary there are a lot of changes, but low
- they are all limited to the s390x architecture
- and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
- Test kernel was built for testting.
== Test Case ==
Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka
crypto-) adapters installed.
V
[Kernel-packages] [Bug 1802787] Re: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker
** 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 ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802750 phase: Uploaded reason: prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Thursday, 22. November 2018 17:02 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802750 phase: Uploaded reason: - prepare-package-meta: Package not yet uploaded - prepare-package-signed: Package not yet uploaded - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 22. November 2018 17:02 UTC + promote-to-proposed: Ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802787 Title: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802750 phase: Uploaded reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787405] Re: [FEAT] Guest-dedicated Crypto Adapters
In preparation I did prepare the series for Disco/Cosmic:
For libvirt 4.6 compared to our series to 4.0:
- drop three being upstream in 4.4 and 4.6
2b9690b62d01bb0b8555764e2365976b98fe4d47 v4.4.0
21442874cf61ce61c7e0f8bcd616641f35adda2b v4.4.0
d54e45b6edd7623e488a19e30bc4148a21fa8b03 v4.6.0
- old lp1787405-0006-conf-Move-VFIO-AP-validation-from-post-parse-to-QEMU.patch
backport can now use the upstream versions of
208d6e6f5aafa102d04ce300c6338b0736bb52df and
faab373b53e1a4eacf0d6f524eb47df243f21fac instead
- we can now use the upstram patch for f865d58028ccd568b6e7909608678584b12d3c90
as-is
- context updates for
debian/patches/ubuntu/lp1787405-0003-qemu-add-vfio-ap-capability.patch
- also updated the Bionic branch as I realized patch 6 had actually two
upstream patches as source (only meta data).
For qemu:
- patch debian/patches/ubuntu/lp1787405-0001-linux-headers-update.patch had
some minor context updates
- patch
ubuntu/lp1787405-0002-s390x-cpumodel-Set-up-CPU-model-for-AP-device-suppor.patch
and
ubuntu/lp1787405-0004-s390x-ap-base-Adjunct-Processor-AP-object-model.patch can
now use the upstream version as-is
- some minor header updates for the Bionic branch
Both branches are built for Disco in the PPA we already used [1].
I'll wait another day for the libvirt upstreaming - there were a few
reviews, but no formal ack's yet. I'll ping via IRC if nothing more is
happening until tomorrow.
FYI: To add more fun to all the code-porting I just happened to realize that
there is also a bunch of CVE fixes incoming (I don't know the content yet). But
that might force us to bump these branches once more.
[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3520
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1787405
Title:
[FEAT] Guest-dedicated Crypto Adapters
Status in Ubuntu on IBM z Systems:
In Progress
Status in libvirt package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in qemu package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Bug description:
== SRU Justification ==
(Kernel SRU)
Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to
a KVM guest such that the hypervisor cannot observe the communication of the
guest with the device.
(Since all kernel patches/commits are from kernel 4.19, they will
automagically land in 'Disco'.)
== Fix ==
9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
e585b24 ("KVM: s390: refactor crypto initialization")
1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
4210459 ("KVM: s390: interface to clear CRYCB masks")
258287c ("s390: vfio-ap: implement mediated device open callback")
e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
46a7263 ("s390: vfio-ap: zeroize the AP queues")
cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
112c24d ("KVM: s390: CPU model support for AP virtualization")
492a6be ("s390: doc: detailed specifications for AP virtualization")
<-- till here in 'kvm/next'
(https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->
8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
0e237e4 ("KVM: s390: Tracing APCB changes")
76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")
<-- till here in 'kvms390/next'
(https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
-->
<-- In addition to that some prereqs for the 'ap/crypto' driver are
necessary -->
ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
df80c03 ("s390/zcrypt: Review inline assembler constraints.")
f1b0a43 ("s390/zcrypt: Integrate ap_asm.
[Kernel-packages] [Bug 1804677] Re: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804677 Title: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: Confirmed Bug description: There was a fault a few days ago and the system updates have not worked properly since then. I received a screen massage " package linux-image- extra-4.40-89-generic is not ready for for configuration cannot configure (current status 'half-installed' " ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-89-generic 4.4.0-89.112 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stewart1606 F pulseaudio Date: Thu Nov 22 14:17:40 2018 ErrorMessage: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=2359cbc7-0ac6-4d11-a02f-df73f23283fe InstallationDate: Installed on 2017-02-14 (646 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: OEM OEM ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic root=UUID=868abb4a-f10f-42b4-8c2c-ec7686786f70 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.19 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: G31MX Series dmi.board.vendor: Foxconn dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/05/2009:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MXSeries:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787405] Re: [FEAT] Guest-dedicated Crypto Adapters
Actually Eric beat me, so while I rebased here the patch for lbivirt
vfio MDEV for virt-aa-helper was merged.
That said I can finalize the branches for Disco tomorrow and run a round
of regression tests before an upload to Disco.
In the meantime I got a few cards to my lpar, maybe I can also verify
the feature on my own now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1787405
Title:
[FEAT] Guest-dedicated Crypto Adapters
Status in Ubuntu on IBM z Systems:
In Progress
Status in libvirt package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in qemu package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Bug description:
== SRU Justification ==
(Kernel SRU)
Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to
a KVM guest such that the hypervisor cannot observe the communication of the
guest with the device.
(Since all kernel patches/commits are from kernel 4.19, they will
automagically land in 'Disco'.)
== Fix ==
9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
e585b24 ("KVM: s390: refactor crypto initialization")
1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
4210459 ("KVM: s390: interface to clear CRYCB masks")
258287c ("s390: vfio-ap: implement mediated device open callback")
e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
46a7263 ("s390: vfio-ap: zeroize the AP queues")
cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
112c24d ("KVM: s390: CPU model support for AP virtualization")
492a6be ("s390: doc: detailed specifications for AP virtualization")
<-- till here in 'kvm/next'
(https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->
8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
0e237e4 ("KVM: s390: Tracing APCB changes")
76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")
<-- till here in 'kvms390/next'
(https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
-->
<-- In addition to that some prereqs for the 'ap/crypto' driver are
necessary -->
ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
df80c03 ("s390/zcrypt: Review inline assembler constraints.")
f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")
<--
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
-->
== PATCH ==
Above git commits are all from 4.19.
The git commands for 4.18 would be:
$ git cherry-pick
(112c24d "KVM: s390: CPU model support for AP virtualization" may have
a trivial merge conflict with the etoken patch)
$ git cherry-pick
$ git cherry-pick
== Regression Potential ==
Low to mid:
- mid because in summary there are a lot of changes, but low
- they are all limited to the s390x architecture
- and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
- Test kernel was built for testting.
== Test Case ==
Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka
crypto-) adapters installed.
Verify that the AP bus created a sysfs device for each APQN, like:
/sys/devices/ap/card04/04.0006
/sys/devices/ap/card04/04.0047
/sys/devices/ap/card0a/0a.0006
/sys/devices/ap/card0a/0a.0047
Verify the APQN range via the following two sysfs files:
/sys/bus/ap/apmask
/sys/bus/ap/aqmask
Configure a
[Kernel-packages] [Bug 1804677] 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/1804677 Title: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: Confirmed Bug description: There was a fault a few days ago and the system updates have not worked properly since then. I received a screen massage " package linux-image- extra-4.40-89-generic is not ready for for configuration cannot configure (current status 'half-installed' " ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-89-generic 4.4.0-89.112 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stewart1606 F pulseaudio Date: Thu Nov 22 14:17:40 2018 ErrorMessage: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=2359cbc7-0ac6-4d11-a02f-df73f23283fe InstallationDate: Installed on 2017-02-14 (646 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: OEM OEM ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic root=UUID=868abb4a-f10f-42b4-8c2c-ec7686786f70 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.19 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: G31MX Series dmi.board.vendor: Foxconn dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/05/2009:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MXSeries:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804677] [NEW] package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration canno
Public bug reported: There was a fault a few days ago and the system updates have not worked properly since then. I received a screen massage " package linux-image-extra-4.40-89-generic is not ready for for configuration cannot configure (current status 'half-installed' " ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-89-generic 4.4.0-89.112 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stewart1606 F pulseaudio Date: Thu Nov 22 14:17:40 2018 ErrorMessage: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=2359cbc7-0ac6-4d11-a02f-df73f23283fe InstallationDate: Installed on 2017-02-14 (646 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: OEM OEM ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic root=UUID=868abb4a-f10f-42b4-8c2c-ec7686786f70 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.19 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: G31MX Series dmi.board.vendor: Foxconn dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/05/2009:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MXSeries:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-package i386 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/1804677 Title: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: Confirmed Bug description: There was a fault a few days ago and the system updates have not worked properly since then. I received a screen massage " package linux-image- extra-4.40-89-generic is not ready for for configuration cannot configure (current status 'half-installed' " ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-89-generic 4.4.0-89.112 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stewart1606 F pulseaudio Date: Thu Nov 22 14:17:40 2018 ErrorMessage: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=2359cbc7-0ac6-4d11-a02f-df73f23283fe InstallationDate: Installed on 2017-02-14 (646 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: OEM OEM ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic root=UUID=868abb4a-f10f-42b4-8c2c-ec7686786f70 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.19 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: G31MX Series dmi.board.vendor: Foxconn dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/05/2009:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MXSeries:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.
[Kernel-packages] [Bug 1764956] Re: Guests using IBRS incur a large performance penalty
Vincent, I'll update the description to match the SRU requirements, but
your original description will still be available.
** Description changed:
- Hello!
+ [Impact]
+ the IBRS would be mistakenly enabled in the host when the switching
+ from an IBRS-enabled VM and that causes the performance overhead in
+ the host. The other condition could also mistakenly disables the IBRS
+ in VM when context-switching from the host. And this could be
+ considered a CVE host.
- As of Linux 4.4.0-119, when a KVM guest is using IBRS, this incurs a
- very large performance penalty on the hosts and other guests.
+ [Fix]
+ The patch fixes the logic inside the x86_virt_spec_ctrl that it checks
+ the ibrs_enabled and _or_ the hostval with the SPEC_CTRL_IBRS as the
+ x86_spec_ctrl_base by default is zero. Because the upstream
+ implementation is not equal to the Xenial's implementation. Upstream
+ doesn't use the IBRS as the formal fix. So, by default, it's zero.
- From my understanding, the patch
- f676aa34b4027d1a7a4bbcc58b81b20c68c7ce0c is incomplete. If host doesn't
- handle IBRS itself (which is now the case by default since 4.4.0-116: it
- relies on retpoline instead) but the guest does (eg running an earlier
- kernel), the guest will set IBRS for the CPU it is running on from time
- to time but if it gets preempted at some point, the IBRS bit will stay,
- incurring a major performance penalty for all other users of the CPU
- (host userland, host kernel and other guests not caring about IBRS). The
- equivalent patch in mainline (d28b387fb74da95d69d2615732f50cceb38e9a4d)
- ensure the appropriate MSR is correctly restored when switching from one
- guest to another or from one guest to host.
+ On the other hand, after the VM exit, the SPEC_CTRL register also
+ needs to be saved manually by reading the SPEC_CTRL MSR as the MSR
+ intercept is disabled by default in the hardware_setup(v4.4) and
+ vmx_init(v3.13). The access to SPEC_CTRL MSR in VM is direct and
+ doesn't trigger a trap. So, the vmx_set_msr() function isn't called.
- The issue is easy to reproduce: host running 4.4.0-119, exposing
- "spec_ctrl" to a guest running CentOS 7.4 with its January kernel. Wait
- a few minutes and the host will become pretty slow. A simple shell loop
- will take 10 more times to execute. Executing "sysctl -w
- kernel.ibrs_dump=1" will show that most real cores have now their IBRS
- bit set to 1.
+ The v3.13 kernel hasn't been tested. However, the patch can be viewed
+ at:
+
http://kernel.ubuntu.com/git/gavinguo/ubuntu-trusty-amd64.git/log/?h=sf00191076-sru
- A workaround is to reeanble IBRS on the host (sysctl -w
- kernel.ibrs_enabled=1). This way, IBRS will be correctly disabled when
- changing context.
+ The v4.4 patch:
+
http://kernel.ubuntu.com/git/gavinguo/ubuntu-xenial.git/log/?h=sf00191076-spectre-v2-regres-backport-juerg
- A long term solution would be to properly backport the patch from
- mainline. It is not part of the 4.4 stable branch and it seems not
- trivial to port.
+ [Test]
- A mid term solution could be to remove the faulty patch (not exposing
- IBRS), since most VM don't need it anymore. This also salvage the
- ability to use IBPB (which doesn't seem to alter performance that much)
- but it isn't believed to be essential.
+ The patch has been tested on the 4.4.0-140.166 and works fine.
+
+ The reproducing environment:
+ Guest kernel version: 4.4.0-138.164
+ Host kernel version: 4.4.0-140.166
+
+ (host IBRS, guest IBRS)
+
+ - 1). (0, 1).
+ The case can be reproduced by the following instructions:
+ guest$ echo 1 | sudo tee /proc/sys/kernel/ibrs_enabled
+ 1
+
+
+
+ host$ cat /proc/sys/kernel/ibrs_enabled
+ 0
+ host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
+ 110001001010
+
+ Some of the IBRS bit inside the SPEC_CTRL MSR are mistakenly
+ enabled.
+
+ host$ taskset -c 5 stress-ng -c 1 --cpu-ops 2500
+ stress-ng: info: [11264] defaulting to a 86400 second run per stressor
+ stress-ng: info: [11264] dispatching hogs: 1 cpu
+ stress-ng: info: [11264] cache allocate: default cache size: 35840K
+ stress-ng: info: [11264] successful run completed in 33.48s
+
+ The host kernel didn't notice the IBRS bit is enabled. So, the situation
+ is the same as "echo 2 > /proc/sys/kernel/ibrs_enabled" in the host.
+ And running the stress-ng is a pure userspace CPU capability
+ calculation. So, the performance downgrades to about 1/3. Without the
+ IBRS enabled, it needs about 10s.
+
+ - 2). (1, 1) disables IBRS in host -> (0, 1) actually it becomes (0, 0).
+ The guest IBRS has been mistakenly disabled.
+
+ guest$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
+ guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
+
+
+ host$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
+ host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
+
+ hos
[Kernel-packages] [Bug 1764956] Re: Guests using IBRS incur a large performance penalty
Gavin Guo had provided a patch to fix this issue, it's a SRU candidate:
https://lists.ubuntu.com/archives/kernel-team/2018-November/096844.html
I'll update this issue accordingly, thanks Gavin!
Cheers,
Guilherme
** Changed in: linux (Ubuntu)
Importance: Medium => High
** Changed in: linux (Ubuntu Xenial)
Importance: Medium => High
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Xenial)
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/1764956
Title:
Guests using IBRS incur a large performance penalty
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
[Impact]
the IBRS would be mistakenly enabled in the host when the switching
from an IBRS-enabled VM and that causes the performance overhead in
the host. The other condition could also mistakenly disables the IBRS
in VM when context-switching from the host. And this could be
considered a CVE host.
[Fix]
The patch fixes the logic inside the x86_virt_spec_ctrl that it checks
the ibrs_enabled and _or_ the hostval with the SPEC_CTRL_IBRS as the
x86_spec_ctrl_base by default is zero. Because the upstream
implementation is not equal to the Xenial's implementation. Upstream
doesn't use the IBRS as the formal fix. So, by default, it's zero.
On the other hand, after the VM exit, the SPEC_CTRL register also
needs to be saved manually by reading the SPEC_CTRL MSR as the MSR
intercept is disabled by default in the hardware_setup(v4.4) and
vmx_init(v3.13). The access to SPEC_CTRL MSR in VM is direct and
doesn't trigger a trap. So, the vmx_set_msr() function isn't called.
The v3.13 kernel hasn't been tested. However, the patch can be viewed
at:
http://kernel.ubuntu.com/git/gavinguo/ubuntu-trusty-amd64.git/log/?h=sf00191076-sru
The v4.4 patch:
http://kernel.ubuntu.com/git/gavinguo/ubuntu-xenial.git/log/?h=sf00191076-spectre-v2-regres-backport-juerg
[Test]
The patch has been tested on the 4.4.0-140.166 and works fine.
The reproducing environment:
Guest kernel version: 4.4.0-138.164
Host kernel version: 4.4.0-140.166
(host IBRS, guest IBRS)
- 1). (0, 1).
The case can be reproduced by the following instructions:
guest$ echo 1 | sudo tee /proc/sys/kernel/ibrs_enabled
1
host$ cat /proc/sys/kernel/ibrs_enabled
0
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
110001001010
Some of the IBRS bit inside the SPEC_CTRL MSR are mistakenly
enabled.
host$ taskset -c 5 stress-ng -c 1 --cpu-ops 2500
stress-ng: info: [11264] defaulting to a 86400 second run per stressor
stress-ng: info: [11264] dispatching hogs: 1 cpu
stress-ng: info: [11264] cache allocate: default cache size: 35840K
stress-ng: info: [11264] successful run completed in 33.48s
The host kernel didn't notice the IBRS bit is enabled. So, the situation
is the same as "echo 2 > /proc/sys/kernel/ibrs_enabled" in the host.
And running the stress-ng is a pure userspace CPU capability
calculation. So, the performance downgrades to about 1/3. Without the
IBRS enabled, it needs about 10s.
- 2). (1, 1) disables IBRS in host -> (0, 1) actually it becomes (0, 0).
The guest IBRS has been mistakenly disabled.
guest$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
host$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
host$ echo 0 | sudo tee /proc/sys/kernel/ibrs_enabled
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764956/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily
There's a second issue that also affects cosmic/linux-azure: In 4.18, the module pci-hyperv moved from "drivers/pci/host/pci- hyperv.ko" to "./drivers/pci/controller/pci-hyperv.c". That caused the module to be included to the linux-modules-extra instead of the linux- modules package. I'm preparing a fix for it and adding some additional checks to prevent modules to move silently to the linux-modules-extra when its based location has changed. -- 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/1794477 Title: Accelerated networking (SR-IOV VF) broken in 18.10 daily Status in linux package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we discovered that accelerated networking wasn’t working inside the VM. No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in use. We tested the daily build on Hyper-V also, but there the Mellanox VF is functional, with the same mlx4 drivers. To give more details about this: • No mellanox logs are showing up in dmesg or syslog. • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as loaded, although Accelerated Networking is enabled for the Azure VM, so this should happen transparently. • Modprobe -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but nothing really happens. And no Mellanox messages are logged in dmesg/syslog. - There are no entries in the logs to show anything about the drivers or netvsc/pci-hyperv that might relate to this issue. Kernel: 4.18.0-7-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily
** Changed in: linux (Ubuntu Cosmic) Status: Fix Committed => Confirmed ** Changed in: linux-azure (Ubuntu) Status: Fix Committed => 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/1794477 Title: Accelerated networking (SR-IOV VF) broken in 18.10 daily Status in linux package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we discovered that accelerated networking wasn’t working inside the VM. No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in use. We tested the daily build on Hyper-V also, but there the Mellanox VF is functional, with the same mlx4 drivers. To give more details about this: • No mellanox logs are showing up in dmesg or syslog. • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as loaded, although Accelerated Networking is enabled for the Azure VM, so this should happen transparently. • Modprobe -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but nothing really happens. And no Mellanox messages are logged in dmesg/syslog. - There are no entries in the logs to show anything about the drivers or netvsc/pci-hyperv that might relate to this issue. Kernel: 4.18.0-7-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802559] Re: linux-azure: 4.15.0-1033.34 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff - snap-release-to-candidate: Snap not in 18/candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress -- 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/1802559 Title: linux-azure: 4.15.0-1033.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802787] Re: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802750 phase: Packaging reason: - prepare-package: Version not specified + prepare-package: Package not yet uploaded + prepare-package-meta: Package not yet uploaded + prepare-package-signed: Package not yet uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802787 Title: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802750 phase: Packaging reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802565] Re: linux-azure: 4.15.0-1033.34~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff - snap-release-to-candidate: Snap not in candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress -- 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/1802565 Title: linux-azure: 4.15.0-1033.34~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802568] Re: linux-gcp: 4.15.0-1025.26~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Nvidia GCP object not found -- 4.15.0-1025 regression-testing: Testing in progress security-signoff: Waiting for signoff - snap-release-to-candidate: Snap not in candidate channel verification-testing: Testing in progress -- 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/1802568 Title: linux-gcp: 4.15.0-1025.26~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Nvidia GCP object not found -- 4.15.0-1025 regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily
Small correction: 4.18.0-1005 is already built on the CKT PPA: https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/ppa/+packages?field.name_filter=azure- edge&field.status_filter=published&field.series_filter=bionic -- 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/1794477 Title: Accelerated networking (SR-IOV VF) broken in 18.10 daily Status in linux package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we discovered that accelerated networking wasn’t working inside the VM. No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in use. We tested the daily build on Hyper-V also, but there the Mellanox VF is functional, with the same mlx4 drivers. To give more details about this: • No mellanox logs are showing up in dmesg or syslog. • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as loaded, although Accelerated Networking is enabled for the Azure VM, so this should happen transparently. • Modprobe -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but nothing really happens. And no Mellanox messages are logged in dmesg/syslog. - There are no entries in the logs to show anything about the drivers or netvsc/pci-hyperv that might relate to this issue. Kernel: 4.18.0-7-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily
4.15.0-1005 is already built on the CKT PPA: https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/ppa/+packages?field.name_filter=azure- edge&field.status_filter=published&field.series_filter=bionic -- 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/1794477 Title: Accelerated networking (SR-IOV VF) broken in 18.10 daily Status in linux package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we discovered that accelerated networking wasn’t working inside the VM. No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in use. We tested the daily build on Hyper-V also, but there the Mellanox VF is functional, with the same mlx4 drivers. To give more details about this: • No mellanox logs are showing up in dmesg or syslog. • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as loaded, although Accelerated Networking is enabled for the Azure VM, so this should happen transparently. • Modprobe -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but nothing really happens. And no Mellanox messages are logged in dmesg/syslog. - There are no entries in the logs to show anything about the drivers or netvsc/pci-hyperv that might relate to this issue. Kernel: 4.18.0-7-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily
Hi Marcelo, Maybe I'm doing something wrong but I still don't see the Mellanox devices with this 4.18.0-1005 kernel from the CKT PPA: ubuntu@lp1794477:~$ sudo add-apt-repository ppa:canonical-kernel-team/ppa ubuntu@lp1794477:~$ sudo apt install linux-azure-edge ubuntu@lp1794477:~$ sudo update-grub ubuntu@lp1794477:~$ sudo reboot ubuntu@lp1794477:~$ uname -a Linux lp1794477 4.18.0-1005-azure #5~18.04.1-Ubuntu SMP Thu Nov 22 00:01:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ubuntu@lp1794477:~$ dmesg | grep -i mella ubuntu@lp1794477:~$ lspci | grep -i mell ubuntu@lp1794477:~$ lsmod | grep -i mlx ubuntu@lp1794477:~$ apt-cache policy linux-image-4.18.0-1005-azure linux-image-4.18.0-1005-azure: Installed: 4.18.0-1005.5~18.04.1 Candidate: 4.18.0-1005.5~18.04.1 Version table: *** 4.18.0-1005.5~18.04.1 500 500 http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status -- 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/1794477 Title: Accelerated networking (SR-IOV VF) broken in 18.10 daily Status in linux package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we discovered that accelerated networking wasn’t working inside the VM. No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in use. We tested the daily build on Hyper-V also, but there the Mellanox VF is functional, with the same mlx4 drivers. To give more details about this: • No mellanox logs are showing up in dmesg or syslog. • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as loaded, although Accelerated Networking is enabled for the Azure VM, so this should happen transparently. • Modprobe -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but nothing really happens. And no Mellanox messages are logged in dmesg/syslog. - There are no entries in the logs to show anything about the drivers or netvsc/pci-hyperv that might relate to this issue. Kernel: 4.18.0-7-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."
Those kernels are OK. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792100 Title: Boot hangs at "loading initial ramdisk..." Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I cannot load a kernel beyond 4.15.0-32-generic on my machine. Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial ramdisk...". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kms2233 F pulseaudio /dev/snd/controlC1: kms2233 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 10:52:00 2018 HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef InstallationDate: Installed on 2018-01-05 (249 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Precision Tower 7810 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago) dmi.bios.date: 06/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A27 dmi.board.name: 0KJCC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802777] Re: linux: 3.2.0-138.184 -proposed tracker
3.2.0-138.184 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_cts_kernel - perf with redirection issue (bug 1801877) Issue to note in i386: ubuntu_cts_kernel - perf with redirection issue (bug 1801877) ubuntu_qrt_kernel_security - test_022_aslr_hardy_vdso failed on P-i386 (bug 1747630) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802777 Title: linux: 3.2.0-138.184 -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-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803169] Re: linux-aws-edge: 4.15.0-1027.28~16.04.1 -proposed tracker
*** This bug is a duplicate of bug 1804071 *** https://bugs.launchpad.net/bugs/1804071 ** This bug is no longer a duplicate of bug 1803170 linux-aws-edge: 4.15.0-1027.28~16.04.1 -proposed tracker ** This bug has been marked a duplicate of bug 1804071 linux-aws-edge: 4.15.0-1028.29~16.04.1 -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/1803169 Title: linux-aws-edge: 4.15.0-1027.28~16.04.1 -proposed tracker Status in Kernel SRU Workflow: New 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: 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1027.28~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- reason: overall: Source not found in kernel-series To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1803169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803166] Re: linux-aws-edge: 4.15.0-1027.28~16.04.1 -proposed tracker
*** This bug is a duplicate of bug 1804071 *** https://bugs.launchpad.net/bugs/1804071 ** This bug is no longer a duplicate of bug 1803170 linux-aws-edge: 4.15.0-1027.28~16.04.1 -proposed tracker ** This bug has been marked a duplicate of bug 1804071 linux-aws-edge: 4.15.0-1028.29~16.04.1 -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/1803166 Title: linux-aws-edge: 4.15.0-1027.28~16.04.1 -proposed tracker Status in Kernel SRU Workflow: New 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: Confirmed 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 linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1027.28~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Packaging reason: prepare-package: Version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1803166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802787] Re: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802750 phase: Packaging reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Thursday, 22. November 2018 13:13 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802750 - phase: Packaging + phase: Uploaded reason: - prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 22. November 2018 13:13 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802787 Title: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802750 phase: Uploaded reason: prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803170] Re: linux-aws-edge: 4.15.0-1027.28~16.04.1 -proposed tracker
*** This bug is a duplicate of bug 1804071 *** https://bugs.launchpad.net/bugs/1804071 ** This bug has been marked a duplicate of bug 1804071 linux-aws-edge: 4.15.0-1028.29~16.04.1 -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/1803170 Title: linux-aws-edge: 4.15.0-1027.28~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux-aws-edge package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-aws-edge source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.15.0-1027.28~16.04.1 upload package. This bug will contain status and testing results related to that upload. 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 phase: Uploaded reason: promote-to-proposed: 'FAILED: Packages no longer available' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1803170/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1564463] Re: Joystick Dragonrise Axes confused in Ubuntu 14.04
Hello there, I'm using Ubuntu 18.10 (Linux 4.18.0) and I don't know why but the issue still exists. I use a GameCube USB gamepad recognized as a Dragonrise Generic USB controller (2 analog sticks, 1 digital D-pad and 8 buttons). In jstest the stick/axis assignments is as follows: * axis-0: horizontal axis of left stick * axis-1: vertical axis of left stick * axis-2: horizontal axis of right stick * axis-3: vertical axis of right stick * axis-4: unused * axis-5: unused In my case axis-0 conflicts with axis-2, i.e. moving horizontally the left stick affects both axis-0 and axis-2, while moving horizontally the right stick causes mostly undefined reads in axis-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/1564463 Title: Joystick Dragonrise Axes confused in Ubuntu 14.04 Status in linux package in Ubuntu: Incomplete Status in linux package in Debian: Confirmed Bug description: In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly working. Its conflicting and superimposed by axis 0 (left-right of the left joystick) Axis 2 was allready behaving bad in eralier versions now its completly broken. Also jscal complains when applying stored settings from earlier ubuntu versions as the joystick now has 6 axes [0-5] and used to have 7, but this seems correct. The Dragonrise chip seems to be very widespread among different speedlink and LinQ models There is a related bugreport in Debian Bug-Tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606 that makes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802076] Re: Trackpad not detected
*** This bug is a duplicate of bug 1781879 *** https://bugs.launchpad.net/bugs/1781879 also duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879 ** This bug has been marked a duplicate of bug 1781879 Latest ASUS trackpad doesn't work in Ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802076 Title: Trackpad not detected Status in linux package in Ubuntu: Incomplete Bug description: My Laptop is an ASUS TUF FX504 Series model. I installed ubuntu 18.04.1 on it but my trackpad is not detected. Attaching an external mouse works fine. Trackpad is easily identified by Windows 10. `cat /proc/bus/input/devices | grep Name` shows the output: ``` N: Name="Sleep Button" N: Name="Power Button" N: Name="Lid Switch" N: Name="Power Button" N: Name="AT Translated Set 2 keyboard" N: Name="Video Bus" N: Name="Video Bus" N: Name="Asus Wireless Radio Control" N: Name="Asus WMI hotkeys" N: Name="USB2.0 HD UVC WebCam: USB2.0 HD" N: Name="HDA Intel PCH Front Headphone" N: Name="HDA Intel PCH HDMI/DP,pcm=3" N: Name="HDA Intel PCH HDMI/DP,pcm=7" N: Name="HDA Intel PCH HDMI/DP,pcm=8" N: Name="HDA Intel PCH HDMI/DP,pcm=9" N: Name="HDA Intel PCH HDMI/DP,pcm=10" N: Name="E-Signal USB Gaming Mouse" N: Name="E-Signal USB Gaming Mouse" ``` I have also attached the output of `cat /proc/bus/input/devices > ~/devices` to this post. `uname -a` outputs: > Linux ayush-TUF-GAMING-FX504GM-FX80GM 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Regards Ayush To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802076] Re: Trackpad not detected
*** This bug is a duplicate of bug 1781879 *** https://bugs.launchpad.net/bugs/1781879 Linux kernel v4.19+ supports touchpad, add tag kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802076 Title: Trackpad not detected Status in linux package in Ubuntu: Incomplete Bug description: My Laptop is an ASUS TUF FX504 Series model. I installed ubuntu 18.04.1 on it but my trackpad is not detected. Attaching an external mouse works fine. Trackpad is easily identified by Windows 10. `cat /proc/bus/input/devices | grep Name` shows the output: ``` N: Name="Sleep Button" N: Name="Power Button" N: Name="Lid Switch" N: Name="Power Button" N: Name="AT Translated Set 2 keyboard" N: Name="Video Bus" N: Name="Video Bus" N: Name="Asus Wireless Radio Control" N: Name="Asus WMI hotkeys" N: Name="USB2.0 HD UVC WebCam: USB2.0 HD" N: Name="HDA Intel PCH Front Headphone" N: Name="HDA Intel PCH HDMI/DP,pcm=3" N: Name="HDA Intel PCH HDMI/DP,pcm=7" N: Name="HDA Intel PCH HDMI/DP,pcm=8" N: Name="HDA Intel PCH HDMI/DP,pcm=9" N: Name="HDA Intel PCH HDMI/DP,pcm=10" N: Name="E-Signal USB Gaming Mouse" N: Name="E-Signal USB Gaming Mouse" ``` I have also attached the output of `cat /proc/bus/input/devices > ~/devices` to this post. `uname -a` outputs: > Linux ayush-TUF-GAMING-FX504GM-FX80GM 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Regards Ayush To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769792] Re: Keyboard and Touchpad do not work after suspend/resume
I have the same or very similar problem, with Fujitsu Lifebook E557, Ubuntu 16.04,18.04 and 18.10. After resume from suspend, touchpad doesn't work at all. Keyboard works somewhat, but some keys are randomly "repete". Reboot doesn't help, but need to to turn the machine off and on 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/1769792 Title: Keyboard and Touchpad do not work after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: My laptop is a Toshiba Satellite C850D with updated 18.04 installed. When resuming from suspend, I have no keyboard and touchpad. dmesg shows "i8042: Can't reactivate KBD port" This looks like a recurring problem, and is just like these: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014240 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1142118 Here's the dmesg output from before and after suspending. https://paste.ubuntu.com/p/rsFX9Yw7Xh/ This post also talks about this bit failing for a lot of people! http://lightrush.ndoytchev.com/random-1/i8042quirkoptions Some of the function keys work, such as changing the screen brightness, but the key (fn+F5) does not turn the touchpad back on. I have not yet tried any of the suggested options, as results have been mixed, but I will. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 7 22:01:26 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804647] [NEW] Installed Nvidia drivers have unmet dependencies
Public bug reported: I had some error while installing the drivers for Nvidia, so when i gave the command to remove fully and reinstall as `sudo apt remove nvidia-*` I get the error as: `. . . Package 'nvidia-libopencl1-331-updates' is not installed, so not removed Package 'nvidia-libopencl1-340' is not installed, so not removed Package 'nvidia-libopencl1-340-updates' is not installed, so not removed Package 'nvidia-libopencl1-384' is not installed, so not removed Package 'nvidia-opencl-icd-331' is not installed, so not removed Package 'nvidia-opencl-icd-331-updates' is not installed, so not removed Package 'nvidia-opencl-icd-340-updates' is not installed, so not removed Package 'nvidia-opencl-icd-384' is not installed, so not removed You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libnvidia-ifr1-390 : Depends: libnvidia-gl-390 but it is not going to be installed libnvidia-ifr1-390:i386 : Depends: libnvidia-gl-390:i386 but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).` Even when i typed `sudo apt --fix-broken install` I get the error as: `diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.77-0ubuntu0.18.04.1_i386.deb (--unpack): new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 Preparing to unpack .../libnvidia-gl-390_390.77-0ubuntu0.18.04.1_amd64.deb ... diversion of /usr/lib/x86_64-linux-gnu/libGL.so to /usr/lib/x86_64-linux-gnu/libGL.so.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so by libnvidia-gl-390' found 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so to /usr/lib/x86_64-linux-gnu/libGL.so.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.77-0ubuntu0.18.04.1_amd64.deb (--unpack): new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libnvidia-gl-390_390.77-0ubuntu0.18.04.1_i386.deb /var/cache/apt/archives/libnvidia-gl-390_390.77-0ubuntu0.18.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)` How do i solve this issue..?? Any suggestions are highly appreciated. Thank you. ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1804647 Title: Installed Nvidia drivers have unmet dependencies Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I had some error while installing the drivers for Nvidia, so when i gave the command to remove fully and reinstall as `sudo apt remove nvidia-*` I get the error as: `. . . Package 'nvidia-libopencl1-331-updates' is not installed, so not removed Package 'nvidia-libopencl1-340' is not installed, so not removed Package 'nvidia-libopencl1-340-updates' is not installed, so not removed Package 'nvidia-libopencl1-384' is not installed, so not removed Package 'nvidia-opencl-icd-331' is not installed, so not removed Package 'nvidia-opencl-icd-331-updates' is not installed, so not removed Package 'nvidia-opencl-icd-340-updates' is not installed, so not removed Package 'nvidia-opencl-icd-384' is not installed, so not removed You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libnvidia-ifr1-390 : Depends: libnvidia-gl-390 but it is not going to be installed libnvidia-ifr1-390:i386 : Depends: libnvidia-gl-390:i386 but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).` Even when i typed `sudo apt --fix-broken install` I get the error as: `diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.77-0ubuntu0.18.04.1_i386.deb (--unpack): new libnvidia-gl-390:i386 package pre-installation script subprocess return
[Kernel-packages] [Bug 1801686] Re: [Ubuntu] qdio: reset old sbal_state flags
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1810
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801686
Title:
[Ubuntu] qdio: reset old sbal_state flags
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Released
Status in linux source package in Disco:
Fix Released
Bug description:
== SRU Justification ==
Description: qdio: reset old sbal_state flags
Symptom:
af_iucv socket using HiperSockets may stall.
Problem:
When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution:
Unconditionally clear the buffer's flags field.
== Fix ==
64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old
sbal_state flags")
== Regression Potential ==
Low, because:
- s390x only
- further limited to qeth driver (OSA Express networking)
- changes are limited to two files and 6 lines
- arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
- drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
- error was identified at IBM/customer, fix was created there and tested
upfront
- (changes are upstream in 4.20 (according to bug description,
but in 4.19 according to 'git tag'),
hence will make it automatically into 'disco')
== Test Case ==
Test case / reproduction:
Error inject and then simulate out-of-memory situation.
__
Description: qdio: reset old sbal_state flags
Symptom: af_iucv socket using HiperSockets may stall.
Problem: When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution: Unconditionally clear the buffer's flags field.
Reproduction: Error inject, simulating out-of-memory.
kernel 4.20
Upstream-ID: 64e03ff72623b8c2ea89ca3cb660094e019ed4ae
Canonical , please provide this fix for all Releases in Service
Ubuntu 18.10, 18.04 and 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1801686/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802787] Re: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker
** Summary changed: - linux-gcp-edge: -proposed tracker + linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802787 Title: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802750 phase: Packaging reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802559] Re: linux-azure: 4.15.0-1033.34 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff - snap-release-to-beta: Snap not in 18/beta channel - snap-release-to-edge: Snap not in 18/edge channel + snap-release-to-candidate: Snap not in 18/candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress -- 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/1802559 Title: linux-azure: 4.15.0-1033.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff snap-release-to-candidate: Snap not in 18/candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Description changed:
== Justification ==
Commit 92183a42898d ("fsnotify: fix ignore mask logic in
send_to_group()") acknowledges the use case of ignoring an event on
an inode mark, because of an ignore mask on a mount mark of the same
group (i.e. I want to get all events on this file, except for the events
that came from that mount).
This change depends on correctly merging the inode marks and mount marks
group lists, so that the mount mark ignore mask would be tested in
send_to_group(). Alas, the merging of the lists did not take into
account the case where event in question is not in the mask of any of
the mount marks.
To fix this, completely remove the tests for inode and mount event masks
from the lists merging code.
== Fix ==
9bdda4e9 (fsnotify: fix ignore mask logic in fsnotify())
Test kernels for Bionic can be found here:
http://people.canonical.com/~phlin/kernel/lp-1802454-fanotify10/bionic/
- It seems that T/X poses with the same issue and the patch can be backported
- with the same logic, but I think we should target Bionic as it's a fix for
+ It seems that T/X poses with the same issue and we might be able to backport
+ it with the same logic, but I think we should target Bionic as it's a fix for
for 92183a42898d which was only applied to Bionic.
== Regression Potential ==
Low.
The backport work is required as it's missing commit 47d9c7cc457 in Bionic,
which generalizes the iteration of marks for inode_mark and vfsmount_mark,
from:
- iter_info.inode_mark
+ iter_info.inode_mark
to:
- iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE]
+ iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE]
But the patch can still be backported with the same logic without this
commit.
The test with the syscalls test in LTP test suite shows no sign of
regression.
== Test Case ==
Run the fanotify10 test in ubuntu_ltp_syscalls test suite. And it will pass
with the patched kernel.
Full LTP syscalls test with 4.15.0-42 in -proposed:
http://paste.ubuntu.com/p/Wm8nQ932g6/
Full LTP syscalls test with patched 4.15.0-42:
http://paste.ubuntu.com/p/nv4jW6shpJ/
-
This is a new test case that landed 7 days ago.
<<>>
tag=fanotify10 stime=1541744937
cmdline="fanotify10"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
mke2fs 1.44.1 (24-Mar-2018)
tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 1 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 2 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 0 (prio 2) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 1 (prio 2) with FAN_MARK_IN
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Thanks for that. The ls reveals 1f.*4* on my system, but using that in the file does *not* work for my system, at least not after a long sleep. *Is any kernel switch (aka grub boot string) required for this*? *WHERE on the Arch forum did you get this workaround? And was it really a forum rather than the ArchWiki?* -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Avai
[Kernel-packages] [Bug 1802568] Re: linux-gcp: 4.15.0-1025.26~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Nvidia GCP object not found -- 4.15.0-1025 regression-testing: Testing in progress security-signoff: Waiting for signoff - snap-release-to-beta: Snap not in beta channel - snap-release-to-edge: Snap not in edge channel + snap-release-to-candidate: Snap not in candidate channel verification-testing: Testing in progress -- 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/1802568 Title: linux-gcp: 4.15.0-1025.26~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Nvidia GCP object not found -- 4.15.0-1025 regression-testing: Testing in progress security-signoff: Waiting for signoff snap-release-to-candidate: Snap not in candidate channel verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
I have just verified both: bionic (15.04.1+18.04.20180413-0ubuntu1.2) and cosmic (15.04.1+18.04.20180413-0ubuntu3) u-s-d packages. In both cases it calculates the diagonal correctly or puts the model name if the real dimensions are not available. However, there is a problem I didn't see coming: hwdata is not installed by default on bionic & cosmic, so the PNP codes are not resolved to vendor names, e.g. u-s-d returned DEL for Dell and GSM for LG Electronics. What are your thoughts on this Seb? Is it worth pulling in hwdata as dependency of u-s-d? It's clearly safer than changing the implementation to use systemd's hwdb. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center Status in hwdata package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon source package in Bionic: Fix Committed Status in unity-settings-daemon source package in Cosmic: Fix Committed Bug description: [Impact] * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). 2. Open the Displays section of Unity settings. 3. Look for the name of the newly connected display in the settings window. Expected result: Display name should contain its real diagonal or model name (if dimensions are not availabe). Actual result: Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802283] Re: system freezes
Today it already crashed twice in a very short period: I resumed my laptop from suspend this morning and suspened it a few times more. Then I noticed Firefox starting to crash a lot again. It got so bad that I switched to using Chrome for work because Firefox just closed a few seconds after opening it again. After a while Chrome also began crashing. By that time I already suspected that the system might freeze any minute and I unplugged the external monitor and the AC connection. Then it happened and the system froze again after some more Chrome crashes. The BIOS is configured to run the system in "performance" mode when connected to the power outlet and spare resources when on battery. Initially I thought that the system might get too hot so I started s-tui to monitor thermal output and CPU usage before the crash happened but the window wasn't in focus when it eventually froze :-/ I was able to use the Magic SysRq keys to reboot this time. Shortly after logging in to gnome-shell the system crashed a second time. I attached the relevant output from kern.log since this morning. Unfortunately, I wasn't able to install the Thunderbolt firmware update from #18 because I don't have access to Windows. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+attachment/5215271/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802283 Title: system freezes Status in linux package in Ubuntu: Incomplete Bug description: My system freezes once every second day or so. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jnns 2519 F pulseaudio /dev/snd/controlC0: jnns 2519 F pulseaudio CurrentDesktop: GNOME Date: Thu Nov 8 12:07:32 2018 HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327 InstallationDate: Installed on 2018-08-05 (95 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KGS5DU00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago) dmi.bios.date: 09/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS5DU00 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: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS5DU00 dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802283] Re: system freezes
I just ran `sudo fwupdmgr` to see if there have been firmware updates and – in deed – they released update 0.1.34 today: > Lenovo ThinkPad X1 Carbon 6th System Firmware Version 1.34 > * Updated the CPU microcode. > * Updated the Diagnostics module to version 04.04.001. > * Improved Thermal FAN behavior. Let's see if it helps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802283 Title: system freezes Status in linux package in Ubuntu: Incomplete Bug description: My system freezes once every second day or so. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jnns 2519 F pulseaudio /dev/snd/controlC0: jnns 2519 F pulseaudio CurrentDesktop: GNOME Date: Thu Nov 8 12:07:32 2018 HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327 InstallationDate: Installed on 2018-08-05 (95 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KGS5DU00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago) dmi.bios.date: 09/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS5DU00 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: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS5DU00 dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802565] Re: linux-azure: 4.15.0-1033.34~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff - snap-release-to-beta: Snap not in beta channel - snap-release-to-edge: Snap not in edge channel + snap-release-to-candidate: Snap not in candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress -- 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/1802565 Title: linux-azure: 4.15.0-1033.34~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff snap-release-to-candidate: Snap not in candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787405] Re: [FEAT] Guest-dedicated Crypto Adapters
FYI: https://www.redhat.com/archives/libvir-list/2018-November/msg00827.html
for the MDEV-vfio apparmor fix upstreaming.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1787405
Title:
[FEAT] Guest-dedicated Crypto Adapters
Status in Ubuntu on IBM z Systems:
In Progress
Status in libvirt package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in qemu package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Bug description:
== SRU Justification ==
(Kernel SRU)
Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to
a KVM guest such that the hypervisor cannot observe the communication of the
guest with the device.
(Since all kernel patches/commits are from kernel 4.19, they will
automagically land in 'Disco'.)
== Fix ==
9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
e585b24 ("KVM: s390: refactor crypto initialization")
1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
4210459 ("KVM: s390: interface to clear CRYCB masks")
258287c ("s390: vfio-ap: implement mediated device open callback")
e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
46a7263 ("s390: vfio-ap: zeroize the AP queues")
cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
112c24d ("KVM: s390: CPU model support for AP virtualization")
492a6be ("s390: doc: detailed specifications for AP virtualization")
<-- till here in 'kvm/next'
(https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->
8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
0e237e4 ("KVM: s390: Tracing APCB changes")
76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")
<-- till here in 'kvms390/next'
(https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
-->
<-- In addition to that some prereqs for the 'ap/crypto' driver are
necessary -->
ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
df80c03 ("s390/zcrypt: Review inline assembler constraints.")
f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")
<--
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
-->
== PATCH ==
Above git commits are all from 4.19.
The git commands for 4.18 would be:
$ git cherry-pick
(112c24d "KVM: s390: CPU model support for AP virtualization" may have
a trivial merge conflict with the etoken patch)
$ git cherry-pick
$ git cherry-pick
== Regression Potential ==
Low to mid:
- mid because in summary there are a lot of changes, but low
- they are all limited to the s390x architecture
- and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
- Test kernel was built for testting.
== Test Case ==
Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka
crypto-) adapters installed.
Verify that the AP bus created a sysfs device for each APQN, like:
/sys/devices/ap/card04/04.0006
/sys/devices/ap/card04/04.0047
/sys/devices/ap/card0a/0a.0006
/sys/devices/ap/card0a/0a.0047
Verify the APQN range via the following two sysfs files:
/sys/bus/ap/apmask
/sys/bus/ap/aqmask
Configure and start a guest.
More details see: 492a6be ("s390: doc: detailed specifications for AP
virtualization")
But for that an updated qemu and libvirt should be in place - that's
addressed in LP1787405, too.
[Kernel-packages] [Bug 1798373] Re: linux-gcp-edge: 4.18.0-1002.3~18.04.1 -proposed tracker
*** This bug is a duplicate of bug 1802787 *** https://bugs.launchpad.net/bugs/1802787 ** This bug is no longer a duplicate of bug 1802618 linux-gcp-edge: 4.18.0-1003.4~18.04.1 -proposed tracker ** This bug has been marked a duplicate of bug 1802787 linux-gcp-edge: -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/1798373 Title: linux-gcp-edge: 4.18.0-1002.3~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.18.0-1002.3~18.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1798373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801877] 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 1801877 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801877 Title: lp1153769 in ubuntu_cts_kernel failed on P with logfd error Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: If you run it on jenkins remotely: ~/kernel-testing/remote --kernel-test-list=ubuntu_cts_kernel ubuntu@rizzo It will fail with: *** lp1153769 *** Running '/home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1' [stderr] Failed opening logfd: Invalid argument Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/ubuntu_cts_kernel.py", line 37, in run_once self.results = utils.system_output(cmd, retain_output=True) File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in system_output verbose=verbose, args=args).stdout File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=234, Command returned non-zero exit status * Command: /home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1 Exit status: 234 Duration: 0.056932926178 This can be reproduced with just ssh on the host to SUT: $ myssh rizzo "/home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1" Warning: Permanently added 'rizzo,10.246.72.30' (ECDSA) to the list of known hosts. Failed opening logfd: Invalid argument But if you run this test locally on the SUT, it will pass without any issue: sudo apt-get install git python-minimal gdb -y git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_cts_kernel/control Or just run the test directly on the SUT: $ /home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1 autotest kernel-test-results kernel-testing Performance counter stats for 'ls': 256 cycles#0.000 GHz 0.002389283 seconds time elapsed I think this has something to do with the perf command and the shell redirection: https://lore.kernel.org/patchwork/patch/309039/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1801877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801877] Re: lp1153769 in ubuntu_cts_kernel failed on P with logfd error
Targeting linux-tools-common Precise package as it's where the perf tool came from. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801877 Title: lp1153769 in ubuntu_cts_kernel failed on P with logfd error Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: If you run it on jenkins remotely: ~/kernel-testing/remote --kernel-test-list=ubuntu_cts_kernel ubuntu@rizzo It will fail with: *** lp1153769 *** Running '/home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1' [stderr] Failed opening logfd: Invalid argument Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/ubuntu_cts_kernel.py", line 37, in run_once self.results = utils.system_output(cmd, retain_output=True) File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in system_output verbose=verbose, args=args).stdout File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=234, Command returned non-zero exit status * Command: /home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1 Exit status: 234 Duration: 0.056932926178 This can be reproduced with just ssh on the host to SUT: $ myssh rizzo "/home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1" Warning: Permanently added 'rizzo,10.246.72.30' (ECDSA) to the list of known hosts. Failed opening logfd: Invalid argument But if you run this test locally on the SUT, it will pass without any issue: sudo apt-get install git python-minimal gdb -y git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_cts_kernel/control Or just run the test directly on the SUT: $ /home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1 autotest kernel-test-results kernel-testing Performance counter stats for 'ls': 256 cycles#0.000 GHz 0.002389283 seconds time elapsed I think this has something to do with the perf command and the shell redirection: https://lore.kernel.org/patchwork/patch/309039/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1801877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802618] Re: linux-gcp-edge: 4.18.0-1003.4~18.04.1 -proposed tracker
*** This bug is a duplicate of bug 1802787 *** https://bugs.launchpad.net/bugs/1802787 ** This bug has been marked a duplicate of bug 1802787 linux-gcp-edge: -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/1802618 Title: linux-gcp-edge: 4.18.0-1003.4~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.18.0-1003.4~18.04.1 upload package. This bug will contain status and testing results related to that upload. 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: 1799445 phase: Uploaded reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802777] Re: linux: 3.2.0-138.184 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing 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/1802777 Title: linux: 3.2.0-138.184 -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-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799184] Re: [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding
I was able to successfully verify the patches and can now see the apmask and
aqmask in /sys/bus/ap using the kernel from bionic-proposed (4.15.0-42-generic).
$ cat /sys/bus/ap/aqmask
0x
$ cat /sys/bus/ap/apmask
0x
Adjusting tags accordingly.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799184
Title:
[18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic
driver binding
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
APQN tags in the zcrypt device driver are required to support
deterministic driver binding
With the introduction of KVM hw crypto virtualization (on s390x) the driver
bound to an AP queue device is no longer unique determined.
Therefore a deterministic hot plugging semantics of AP queues that may be
bound to multiple drivers is needed.
With the three listed commits here it will be possible to configure an AP
queue (APQN) as being bound to a particular driver even if the associate hw
gets intermittently lost and reconnected.
== Fixes ==
ac2b96f351d7d222 ("s390/zcrypt: code beautify")
7e0bdbe5c21cb831 ("s390/zcrypt: AP bus support for alternate driver(s)")
3d8f60d38e249f98 ("s390/zcrypt: hex string mask improvements for apmask and
aqmask")
== Patches ==
Git-commit: ac2b96f351d7d222
https://github.com/torvalds/linux/commit/ac2b96f351d7d222c46e524feca03005f3fa8d75
Author: Harald Freudenberger
Date: Fri Aug 17 12:36:01 2018 +0200
s390/zcrypt: code beautify
Code beautify by following most of the checkpatch suggestions:
- SPDX license identifier line complains by checkpatch
- missing space or newline complains by checkpatch
- octal numbers for permssions complains by checkpatch
- renaming of static sysfs functions complains by checkpatch
- fix of block comment complains by checkpatch
- fix printf like calls where function name instead of %s __func__
was used
- __packed instead of __attribute__((packed))
- init to zero for static variables removed
- use of DEVICE_ATTR_RO and DEVICE_ATTR_RW macros
No functional code changes or API changes!
Signed-off-by: Harald Freudenberger
Signed-off-by: Martin Schwidefsky
===
Git-commit 7e0bdbe5c21cb831
https://github.com/torvalds/linux/commit/7e0bdbe5c21cb8316a694e46ad5aad339f6894a6
Author: Harald Freudenberger
Date: Fri Jul 20 08:36:53 2018 +0200
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
ALinuxUser I got this script on archlinux forum. I changed their value :00:1f.4 to my :00:1f.3. # ls /sys/bus/pci/drivers/i801_smbus/ :00:1f.3 bind module new_id remove_id uevent unbind Also i have nfc, but i don`t is it realy work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO
[Kernel-packages] [Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Description changed:
== Justification ==
Commit 92183a42898d ("fsnotify: fix ignore mask logic in
send_to_group()") acknowledges the use case of ignoring an event on
an inode mark, because of an ignore mask on a mount mark of the same
group (i.e. I want to get all events on this file, except for the events
that came from that mount).
This change depends on correctly merging the inode marks and mount marks
group lists, so that the mount mark ignore mask would be tested in
send_to_group(). Alas, the merging of the lists did not take into
account the case where event in question is not in the mask of any of
the mount marks.
To fix this, completely remove the tests for inode and mount event masks
from the lists merging code.
== Fix ==
9bdda4e9 (fsnotify: fix ignore mask logic in fsnotify())
Test kernels for Bionic can be found here:
http://people.canonical.com/~phlin/kernel/lp-1802454-fanotify10/bionic/
- It seems that T/X poses with the same issue and the patch can be
- backported with the same logic, but we should target Bionic only as it's
- a fix for 92183a42898d which was only applied to Bionic.
+ It seems that T/X poses with the same issue and the patch can be backported
+ with the same logic, but I think we should target Bionic as it's a fix for
+ for 92183a42898d which was only applied to Bionic.
== Regression Potential ==
Low.
- The backport work is required because it's missing another patch 47d9c7cc457
in Bionic, which generalizes the iteration of marks for inode_mark and
vfsmount_mark, from:
+ The backport work is required as it's missing commit 47d9c7cc457 in Bionic,
+ which generalizes the iteration of marks for inode_mark and vfsmount_mark,
from:
iter_info.inode_mark
to:
iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE]
- But the patch can still be backported with the same logic.
+ But the patch can still be backported with the same logic without this
+ commit.
+
+ The test with the syscalls test in LTP test suite shows no sign of
+ regression.
== Test Case ==
- Run the fanotify10 test in ubuntu_ltp_syscalls test suite. And it will pass
with the patched kernel.
+ Run the fanotify10 test in ubuntu_ltp_syscalls test suite. And it will pass
+ with the patched kernel.
- Full LTP syscalls test with 4.15.0-42 in -proposed:
+ Full LTP syscalls test with 4.15.0-42 in -proposed:
http://paste.ubuntu.com/p/Wm8nQ932g6/
Full LTP syscalls test with patched 4.15.0-42:
http://paste.ubuntu.com/p/nv4jW6shpJ/
-
-
-
This is a new test case that landed 7 days ago.
<<>>
tag=fanotify10 stime=1541744937
cmdline="fanotify10"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
mke2fs 1.44.1 (24-Mar-2018)
tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanot
[Kernel-packages] [Bug 1801686] Re: [Ubuntu] qdio: reset old sbal_state flags
Adjusting tags according to comment #9.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801686
Title:
[Ubuntu] qdio: reset old sbal_state flags
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Released
Status in linux source package in Disco:
Fix Released
Bug description:
== SRU Justification ==
Description: qdio: reset old sbal_state flags
Symptom:
af_iucv socket using HiperSockets may stall.
Problem:
When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution:
Unconditionally clear the buffer's flags field.
== Fix ==
64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old
sbal_state flags")
== Regression Potential ==
Low, because:
- s390x only
- further limited to qeth driver (OSA Express networking)
- changes are limited to two files and 6 lines
- arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
- drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
- error was identified at IBM/customer, fix was created there and tested
upfront
- (changes are upstream in 4.20 (according to bug description,
but in 4.19 according to 'git tag'),
hence will make it automatically into 'disco')
== Test Case ==
Test case / reproduction:
Error inject and then simulate out-of-memory situation.
__
Description: qdio: reset old sbal_state flags
Symptom: af_iucv socket using HiperSockets may stall.
Problem: When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution: Unconditionally clear the buffer's flags field.
Reproduction: Error inject, simulating out-of-memory.
kernel 4.20
Upstream-ID: 64e03ff72623b8c2ea89ca3cb660094e019ed4ae
Canonical , please provide this fix for all Releases in Service
Ubuntu 18.10, 18.04 and 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1801686/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801686] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2018-11-22 03:57 EDT---
Fix verified upfront on upstream by IBM
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801686
Title:
[Ubuntu] qdio: reset old sbal_state flags
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Released
Status in linux source package in Disco:
Fix Released
Bug description:
== SRU Justification ==
Description: qdio: reset old sbal_state flags
Symptom:
af_iucv socket using HiperSockets may stall.
Problem:
When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution:
Unconditionally clear the buffer's flags field.
== Fix ==
64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old
sbal_state flags")
== Regression Potential ==
Low, because:
- s390x only
- further limited to qeth driver (OSA Express networking)
- changes are limited to two files and 6 lines
- arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
- drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
- error was identified at IBM/customer, fix was created there and tested
upfront
- (changes are upstream in 4.20 (according to bug description,
but in 4.19 according to 'git tag'),
hence will make it automatically into 'disco')
== Test Case ==
Test case / reproduction:
Error inject and then simulate out-of-memory situation.
__
Description: qdio: reset old sbal_state flags
Symptom: af_iucv socket using HiperSockets may stall.
Problem: When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution: Unconditionally clear the buffer's flags field.
Reproduction: Error inject, simulating out-of-memory.
kernel 4.20
Upstream-ID: 64e03ff72623b8c2ea89ca3cb660094e019ed4ae
Canonical , please provide this fix for all Releases in Service
Ubuntu 18.10, 18.04 and 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1801686/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802752] Re: linux-azure: 4.18.0-1005.5 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Uploaded reason: - promote-to-proposed: Builds not complete + promote-to-proposed: Another kernel is currently pending in proposed -- 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/1802752 Title: linux-azure: 4.18.0-1005.5 -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 upload-to-ppa 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 Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Uploaded reason: promote-to-proposed: Another kernel is currently pending in proposed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Description changed:
+ == Justification ==
+ Commit 92183a42898d ("fsnotify: fix ignore mask logic in
+ send_to_group()") acknowledges the use case of ignoring an event on
+ an inode mark, because of an ignore mask on a mount mark of the same
+ group (i.e. I want to get all events on this file, except for the events
+ that came from that mount).
+
+ This change depends on correctly merging the inode marks and mount marks
+ group lists, so that the mount mark ignore mask would be tested in
+ send_to_group(). Alas, the merging of the lists did not take into
+ account the case where event in question is not in the mask of any of
+ the mount marks.
+
+ To fix this, completely remove the tests for inode and mount event masks
+ from the lists merging code.
+
+ == Fix ==
+ 9bdda4e9 (fsnotify: fix ignore mask logic in fsnotify())
+
+ Test kernels for Bionic can be found here:
+ http://people.canonical.com/~phlin/kernel/lp-1802454-fanotify10/bionic/
+
+ It seems that T/X poses with the same issue and the patch can be
+ backported with the same logic, but we should target Bionic only as it's
+ a fix for 92183a42898d which was only applied to Bionic.
+
+ == Regression Potential ==
+ Low.
+
+ The backport work is required because it's missing another patch 47d9c7cc457
in Bionic, which generalizes the iteration of marks for inode_mark and
vfsmount_mark, from:
+ iter_info.inode_mark
+ to:
+ iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE]
+
+ But the patch can still be backported with the same logic.
+
+ == Test Case ==
+ Run the fanotify10 test in ubuntu_ltp_syscalls test suite. And it will pass
with the patched kernel.
+
+ Full LTP syscalls test with 4.15.0-42 in -proposed:
+ http://paste.ubuntu.com/p/Wm8nQ932g6/
+
+ Full LTP syscalls test with patched 4.15.0-42:
+ http://paste.ubuntu.com/p/nv4jW6shpJ/
+
+
+ -
+
+
This is a new test case that landed 7 days ago.
<<>>
tag=fanotify10 stime=1541744937
cmdline="fanotify10"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
mke2fs 1.44.1 (24-Mar-2018)
tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 1 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 2 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 0 (prio 2) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 1 (prio 2) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 2 (prio 2) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:199: INFO: Test #3: don't ignore inode events created on another
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187:
[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs
Kai-Heng - just tried out that kernel and that looks like it stops the issue for me here - thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784152 Title: i2c_hid_get_input floods system logs Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.15.0-29.31-generic 4.15.18 After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system logs are flooded whenever I move the cursor with my touchpad. It looks like this: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) etc... This problem did not occur on the previous kernel version so there must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file. This seems to be fixed in a recent commit here: https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c I am currently running the older kernel version but would still like to be up to date without this flooding happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793953] Re: resume from suspend fails after upgrade from 16.04 LTS to 18.04 LTS
Can you try kernel v4.4? It's a regression if it works under old kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793953 Title: resume from suspend fails after upgrade from 16.04 LTS to 18.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Problems: 1) on resume from suspend the keyboard is not working. I can log in using virtual keyboard, but then the keyboard is disalbled yet. 2) the function key to disable the touch pad doesn't work. Note: during upgrade from 16.04 LTS to 18.04 LTS something fails, it was: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1773859 $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ uname -a Linux ferz-SVF1521G1EW 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lspci 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04) 07:00.0 Network controller: Broadcom Limited BCM43142 802.11b/g/n (rev 01) 08:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01) 0e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ferz 2096 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-01-13 (1761 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Sony Corporation SVF1521G1EW NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=af1ed5d3-2a4f-4bea-ae66-c7c0f32056f1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0200DA dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0200DA:bd03/26/2013:svnSonyCorporation:pnSVF1521G1EW:pvrC10H2Q08:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVF1521G1EW dmi.product.version: C10H2Q08 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
I have same problem in Lenovo laptop with intel CPU, SSD. With 16.04 it worked. In 18.04 it worked few days ago, now it doesn't work and using other kernel versions doesn't help, so I suspect it is not fault of newer kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: ===SRU Justification=== [Impact] Systems with acpi-lpss can't do S3/S4 on Bionic. [Test] Users confirmed these patches work for them. [Fix] Commit a192aa923b66a (ACPI / LPSS: Consolidate runtime PM and system sleep handling) applies quirks for both runtime and system suspend. This causes problems for some systems, so avoid using quirks on S3 and S4. [Regression Potential] Low. These patches are in upstream stable, and it brings back driver's old behavior. ===Original Bug Report=== I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
