[Kernel-packages] [Bug 1798052] Re: request_key03 in ubuntu_ltp_syscalls failed with T
Still failing with generic Trusty kernel <<>> tag=request_key03 stime=1541576525 cmdline="request_key03" contacts="" analysis=exit <<>> tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s request_key03.c:154: PASS: didn't crash while updating key of type 'encrypted' request_key03.c:168: PASS: didn't crash while requesting key of type 'encrypted' request_key03.c:115: BROK: unexpected error adding key of type 'trusted': ENOMEM request_key03.c:160: BROK: add_key child exited with 2 Summary: passed 2 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=2 <<>> <<>> tag=cve-2017-15299 stime=1541576525 cmdline="request_key03 -b cve-2017-15299" contacts="" analysis=exit <<>> tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s request_key03.c:154: PASS: didn't crash while updating key of type 'encrypted' request_key03.c:168: INFO: didn't crash while requesting key of type 'encrypted' request_key03.c:154: PASS: didn't crash while updating key of type 'trusted' request_key03.c:168: INFO: didn't crash while requesting key of type 'trusted' request_key03.c:154: PASS: didn't crash while updating key of type 'user' request_key03.c:168: INFO: didn't crash while requesting key of type 'user' Summary: passed 3 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=0 corefile=no cutime=1 cstime=24 <<>> <<>> tag=cve-2017-15951 stime=1541576526 cmdline="request_key03 -b cve-2017-15951" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s request_key03.c:154: INFO: didn't crash while updating key of type 'encrypted' request_key03.c:168: PASS: didn't crash while requesting key of type 'encrypted' request_key03.c:115: BROK: unexpected error adding key of type 'trusted': ENOMEM request_key03.c:160: BROK: add_key child exited with 2 Summary: passed 1 failed 0 skipped 0 warnings 0 ** Changed in: ubuntu-kernel-tests 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/1798052 Title: request_key03 in ubuntu_ltp_syscalls failed with T Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After bug 1775370, this test is now failing with another error message, to me it looks like there is something to do with the test case. $ sudo ./request_key03 tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s request_key03.c:154: PASS: didn't crash while updating key of type 'encrypted' request_key03.c:168: PASS: didn't crash while requesting key of type 'encrypted' request_key03.c:115: BROK: unexpected error adding key of type 'trusted': ENOMEM request_key03.c:160: BROK: add_key child exited with 2 Summary: passed 2 failed 0 skipped 0 warnings 0 ubuntu@amaura:/opt/ltp/testcases/bin$ uname -a Linux amaura 3.13.0-161-generic #211-Ubuntu SMP Wed Oct 3 14:52:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-161-generic 3.13.0-161.211 ProcVersionSignature: User Name 3.13.0-161.211-generic 3.13.11-ckt39 Uname: Linux 3.13.0-161-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 16 07:01 seq crw-rw 1 root audio 116, 33 Oct 16 07:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Oct 16 09:02:48 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-161-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-3.13.0-161-generic N/A linux-backports-modules-3.13.0-161-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS
[Kernel-packages] [Bug 1802056] Re: Unable to start KVM, timed out waiting for dnsmasq lease
Similar issue bug 1765668 This is not a regression. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802056 Title: Unable to start KVM, timed out waiting for dnsmasq lease Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Bug description: On node gonzo with Trusty + uvtool (0~bzr92-0ubuntu1.1) and 0~bzr99~ubuntu14.04.1 from ppa, the kvm smoke test failed with dnsmasq lease time out. ubuntu@gonzo:~$ uvt-kvm create trusty release=trusty arch=amd64 ubuntu@gonzo:~$ uvt-kvm wait trusty --insecure --ssh-private-key-file /home/ubuntu/.ssh/id_rsa uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:c9:fe:f5. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-161-generic 3.13.0-161.211 ProcVersionSignature: User Name 3.13.0-161.211-generic 3.13.11-ckt39 Uname: Linux 3.13.0-161-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 7 03:48 seq crw-rw 1 root audio 116, 33 Nov 7 03:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Nov 7 07:03:48 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R415 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-161-generic root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-3.13.0-161-generic N/A linux-backports-modules-3.13.0-161-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 08WNM9 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd04/26/2012:svnDellInc.:pnPowerEdgeR415:pvr:rvnDellInc.:rn08WNM9:rvrA02:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R415 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802056] 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/1802056 Title: Unable to start KVM, timed out waiting for dnsmasq lease Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: On node gonzo with Trusty + uvtool (0~bzr92-0ubuntu1.1) and 0~bzr99~ubuntu14.04.1 from ppa, the kvm smoke test failed with dnsmasq lease time out. ubuntu@gonzo:~$ uvt-kvm create trusty release=trusty arch=amd64 ubuntu@gonzo:~$ uvt-kvm wait trusty --insecure --ssh-private-key-file /home/ubuntu/.ssh/id_rsa uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:c9:fe:f5. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-161-generic 3.13.0-161.211 ProcVersionSignature: User Name 3.13.0-161.211-generic 3.13.11-ckt39 Uname: Linux 3.13.0-161-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 7 03:48 seq crw-rw 1 root audio 116, 33 Nov 7 03:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Nov 7 07:03:48 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R415 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-161-generic root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-3.13.0-161-generic N/A linux-backports-modules-3.13.0-161-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 08WNM9 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd04/26/2012:svnDellInc.:pnPowerEdgeR415:pvr:rvnDellInc.:rn08WNM9:rvrA02:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R415 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800641] Re: [Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1800641
Title:
[Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
== SRU Justification ==
IBM is requesting these commits in s390 for X, B and C. The bug
description the commits fix is as follows:
Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom:
Infinite loop when processing a received cmd.
Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build
human-readable messages for received cmd data.
== Fixes ==
065a2cdcbdf8 ("s390: qeth_core_mpc: Use ARRAY_SIZE instead of reimplementing
its function")
048a7f8b4ec0 ("s390: qeth: Fix potential array overrun in cmd/rc lookup")
== Regression Potential ==
Low. Limited to s390.
== Test Case ==
A test kernel was built with these two patches and tested by IBM.
The bug reporter states the test kernel resolved the bug.
Description: qeth: Fix potential array overrun in cmd/rc lookup
Symptom: Infinite loop when processing a received cmd.
Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used
to build human-readable messages for received cmd data.
They store the to-be translated value in the last entry of a
global array, and then iterate over each entry until they found
the queried value (and the corresponding message string).
If there is no prior match, the lookup is intended to stop at
the final entry (which was previously prepared).
If two qeth devices are concurrently processing a received cmd,
one lookup can over-write the last entry of the global array
while a second lookup is in process. This second lookup will
then
never hit its stop-condition, and loop.
Solution: Remove the modification of the global array, and limit the
number
of iterations to the size of the array.
Upstream-ID: kernel 4.19
- 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b
- 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9
Should also be applied, to all other Ubuntu Releases in the field !
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800641/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802056] [NEW] Unable to start KVM, timed out waiting for dnsmasq lease
Public bug reported: On node gonzo with Trusty + uvtool (0~bzr92-0ubuntu1.1) and 0~bzr99~ubuntu14.04.1 from ppa, the kvm smoke test failed with dnsmasq lease time out. ubuntu@gonzo:~$ uvt-kvm create trusty release=trusty arch=amd64 ubuntu@gonzo:~$ uvt-kvm wait trusty --insecure --ssh-private-key-file /home/ubuntu/.ssh/id_rsa uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:c9:fe:f5. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-161-generic 3.13.0-161.211 ProcVersionSignature: User Name 3.13.0-161.211-generic 3.13.11-ckt39 Uname: Linux 3.13.0-161-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 7 03:48 seq crw-rw 1 root audio 116, 33 Nov 7 03:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Nov 7 07:03:48 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R415 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-161-generic root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-3.13.0-161-generic N/A linux-backports-modules-3.13.0-161-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 08WNM9 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd04/26/2012:svnDellInc.:pnPowerEdgeR415:pvr:rvnDellInc.:rn08WNM9:rvrA02:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R415 dmi.sys.vendor: Dell Inc. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty uec-images ** Description changed: - On node gonzo with Trusty + uvtool (and 0~bzr99~ubuntu14.04.1 from ppa, - the kvm smoke test failed with dnsmasq lease time out. + On node gonzo with Trusty + uvtool (0~bzr92-0ubuntu1.1) and + 0~bzr99~ubuntu14.04.1 from ppa, the kvm smoke test failed with dnsmasq + lease time out. ubuntu@gonzo:~$ uvt-kvm create trusty release=trusty arch=amd64 ubuntu@gonzo:~$ uvt-kvm wait trusty --insecure --ssh-private-key-file /home/ubuntu/.ssh/id_rsa uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:c9:fe:f5. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-161-generic 3.13.0-161.211 ProcVersionSignature: User Name 3.13.0-161.211-generic 3.13.11-ckt39 Uname: Linux 3.13.0-161-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Nov 7 03:48 seq - crw-rw 1 root audio 116, 33 Nov 7 03:48 timer + total 0 + crw-rw 1 root audio 116, 1 Nov 7 03:48 seq + crw-rw 1 root audio 116, 33 Nov 7 03:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Nov 7 07:03:48 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R415 PciMultimedia: - + ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-161-generic root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro console=ttyS0,115200n8 RelatedPackageVersions: - linux-restricted-modules-3.13.0-161-generic N/A - linux-backports-modules-3.13.0-161-generic N/A - linux-firmware 1.127.24 + linux-restricted-modules-3.13.0-161-generic N/A + linux-backports-modules-3.13.0-161-generic N/A + linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 08WNM9 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd04/26/2012:svnDellInc.:pnPowerEdgeR415:pvr:rvnDellInc.:rn08WNM9:rvrA02:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R415 dmi.sys.vendor: Dell Inc. ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, whi
[Kernel-packages] [Bug 1802052] Re: WMI Error - ACPI Exception AE_NOT_FOUND
Removing "acpi_osi=! "acpi_osi=Windows 2009" " from boot does not fix the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802052 Title: WMI Error - ACPI Exception AE_NOT_FOUND Status in linux package in Ubuntu: Confirmed Bug description: Backstory: The discrete touchpad enable/disable switch does not work on Ubuntu but works perfectly on windows. This is probably an issue of the msi_wmi drivers, so I tried to find a solution. Followed the instructions here - https://wiki.ubuntu.com/Kernel/Reference/WMI ACPI dump error - AE_NOT_EXIST Logs - https://pastebin.com/BKCHpie4 WMI dump error - AE_NOT_FOUND Logs - https://pastebin.com/aY6ngxzh ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pratyush 4060 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 7 12:02:12 2018 InstallationDate: Installed on 2018-09-17 (50 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1038:1122 SteelSeries ApS Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=dba04826-1b60-412d-b2f4-06f876af3f8f ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash acpi_backlight=vendor nouveau.runpm=0 vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16Q2IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-16Q2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16Q2IMS.10E:bd08/27/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS65StealthThin8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16Q2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GS dmi.product.name: GS65 Stealth Thin 8RF dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575334] Re: Docking thinkpad laptop causes a complete system freeze
I upgraded to 18.10 about two weeks ago and since then it happens to me on 90% of the times, and only after hard shutdown it recovers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575334 Title: Docking thinkpad laptop causes a complete system freeze Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to Xenial, about 80% of the time when I dock my thinkpad laptop I get a complete system freeze. The symptoms of the freeze are: * The two external monitors connected to the dock seem to be in a half-configured state - they're powered on, and display some graphics from my desktop, but do not yet show the correct contents. * I can't get to a console with Ctrl+Alt+F1. * I can't kill X with Ctrl+Alt+Backspace * I can't get the mouse cursor to appear or move, either with the trackpad or the external mouse. * Undocking the laptop doesn't help. The only thing I *can* do at this point is to hold down the power button. I seem to recall similar issues in the past (perhaps in Vivid?), where the fix ended up being in the graphics driver. The laptop is a T540p. The docking station is an "ultra dock pro" - not a USB dock, but rather one of those ones where the laoptop clicks into a base. This bug makes the docking station rather useless, and makes me sad :( ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomi 3196 F pulseaudio /dev/snd/controlC0: thomi 3196 F pulseaudio /dev/snd/controlC1: thomi 3196 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 27 07:35:58 2016 HibernationDevice: RESUME=UUID=d27c9b15-955a-4bff-b4a7-e6116a8b30bb InstallationDate: Installed on 2015-10-12 (197 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 20BECTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (5 days ago) dmi.bios.date: 09/01/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GMET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BECTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 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:bvrGMET72WW(2.20):bd09/01/2015:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20BECTO1WW dmi.product.version: ThinkPad T540p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802052] Re: WMI Error - ACPI Exception AE_NOT_FOUND
Issue persists in upstream kernel v4.19. ** Description changed: Backstory: The discrete touchpad enable/disable switch does not work on Ubuntu but works perfectly on windows. This is probably an issue of the msi_wmi drivers, so I tried to find a solution. Followed the instructions here - https://wiki.ubuntu.com/Kernel/Reference/WMI ACPI dump error - AE_NOT_EXIST Logs - https://pastebin.com/BKCHpie4 WMI dump error - AE_NOT_FOUND Logs - https://pastebin.com/aY6ngxzh - - The problem persists in 4.19 kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pratyush 4060 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 7 12:02:12 2018 InstallationDate: Installed on 2018-09-17 (50 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1038:1122 SteelSeries ApS Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=dba04826-1b60-412d-b2f4-06f876af3f8f ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash acpi_backlight=vendor nouveau.runpm=0 vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16Q2IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-16Q2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16Q2IMS.10E:bd08/27/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS65StealthThin8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16Q2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GS dmi.product.name: GS65 Stealth Thin 8RF dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802052 Title: WMI Error - ACPI Exception AE_NOT_FOUND Status in linux package in Ubuntu: Confirmed Bug description: Backstory: The discrete touchpad enable/disable switch does not work on Ubuntu but works perfectly on windows. This is probably an issue of the msi_wmi drivers, so I tried to find a solution. Followed the instructions here - https://wiki.ubuntu.com/Kernel/Reference/WMI ACPI dump error - AE_NOT_EXIST Logs - https://pastebin.com/BKCHpie4 WMI dump error - AE_NOT_FOUND Logs - https://pastebin.com/aY6ngxzh ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pratyush 4060 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 7 12:02:12 2018 InstallationDate: Installed on 2018-09-17 (50 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1038:1122 SteelSeries ApS Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=dba04826-1b60-412d-b2f4-06f876af3f8f ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash acpi_backlight=vendor nouveau.runpm=0 vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.vendor: American Megatrends
[Kernel-packages] [Bug 1800641] Re: [Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1800641
Title:
[Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
== SRU Justification ==
IBM is requesting these commits in s390 for X, B and C. The bug
description the commits fix is as follows:
Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom:
Infinite loop when processing a received cmd.
Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build
human-readable messages for received cmd data.
== Fixes ==
065a2cdcbdf8 ("s390: qeth_core_mpc: Use ARRAY_SIZE instead of reimplementing
its function")
048a7f8b4ec0 ("s390: qeth: Fix potential array overrun in cmd/rc lookup")
== Regression Potential ==
Low. Limited to s390.
== Test Case ==
A test kernel was built with these two patches and tested by IBM.
The bug reporter states the test kernel resolved the bug.
Description: qeth: Fix potential array overrun in cmd/rc lookup
Symptom: Infinite loop when processing a received cmd.
Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used
to build human-readable messages for received cmd data.
They store the to-be translated value in the last entry of a
global array, and then iterate over each entry until they found
the queried value (and the corresponding message string).
If there is no prior match, the lookup is intended to stop at
the final entry (which was previously prepared).
If two qeth devices are concurrently processing a received cmd,
one lookup can over-write the last entry of the global array
while a second lookup is in process. This second lookup will
then
never hit its stop-condition, and loop.
Solution: Remove the modification of the global array, and limit the
number
of iterations to the size of the array.
Upstream-ID: kernel 4.19
- 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b
- 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9
Should also be applied, to all other Ubuntu Releases in the field !
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800641/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802052] 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/1802052 Title: WMI Error - ACPI Exception AE_NOT_FOUND Status in linux package in Ubuntu: Confirmed Bug description: Backstory: The discrete touchpad enable/disable switch does not work on Ubuntu but works perfectly on windows. This is probably an issue of the msi_wmi drivers, so I tried to find a solution. Followed the instructions here - https://wiki.ubuntu.com/Kernel/Reference/WMI ACPI dump error - AE_NOT_EXIST Logs - https://pastebin.com/BKCHpie4 WMI dump error - AE_NOT_FOUND Logs - https://pastebin.com/aY6ngxzh ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pratyush 4060 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 7 12:02:12 2018 InstallationDate: Installed on 2018-09-17 (50 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1038:1122 SteelSeries ApS Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=dba04826-1b60-412d-b2f4-06f876af3f8f ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash acpi_backlight=vendor nouveau.runpm=0 vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16Q2IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-16Q2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16Q2IMS.10E:bd08/27/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS65StealthThin8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16Q2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GS dmi.product.name: GS65 Stealth Thin 8RF dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1798165
Title:
Vulkan applications cause permanent memory leak with Intel GPU
Status in Linux:
Unknown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
== SRU Justification ==
Vulkan applications, as Dota 2 and DXVK games cause a memory leak where
memory is never freed and can cause a system crash if the applications are
used for long enough. Certain applications can make the leak be as high as
10 MB/minute.
This commit has been cc'd to upstream stable, but it has not landed in
Bionic or Cosmic as of yet.
Details about the upstream bug can be seen at:
https://github.com/doitsujin/dxvk/issues/632
https://bugs.freedesktop.org/show_bug.cgi?id=107899
== Fix ==
337fe9f5c1e7 ("drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set")
== Regression Potential ==
Low. This commit has been cc'd to stable, so it has had additional
upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Vulkan applications, as Dota 2 and DXVK games cause a memory leak
where memory is never freed and can cause a system crash if the
applications are used for long enough. Certain applications can make
the leak be as high as 10 MB/minute.
Details about this bug can be seen at
https://github.com/doitsujin/dxvk/issues/632 and
https://bugs.freedesktop.org/show_bug.cgi?id=107899
This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
The particular commit is:
commit a2cef7d049f07995406b403605119a54881daf15
Author: Jason Ekstrand
Date: Wed Sep 26 02:17:03 2018 -0500
drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.
We attempt to get fences earlier in the hopes that everything will
already have fences and no callbacks will be needed. If we do succeed
in getting a fence, getting one a second time will result in a duplicate
ref with no unref. This is causing memory leaks in Vulkan applications
that create a lot of fences; playing for a few hours can, apparently,
bring down the system.
Cc: sta...@vger.kernel.org
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
Reviewed-by: Chris Wilson
Signed-off-by: Jason Ekstrand
Signed-off-by: Sean Paul
Link:
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
Signed-off-by: Greg Kroah-Hartman
On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as:
https://i.imgur.com/qMAvuwl.png
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-36-generic 4.15.0-36.39
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: usuario4655 F pulseaudio
/dev/snd/seq:usuario4640 F timidity
CurrentDesktop: XFCE
Date: Tue Oct 16 14:16:54 2018
HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
InstallationDate: Installed on 2017-06-13 (489 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 80UG
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt
i915.enable_gvt=1 i915.fastboot=1
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
dmi.bios.date: 08/09/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.modalias:
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad31
[Kernel-packages] [Bug 1799393] Re: Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core)
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799393
Title:
Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core)
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Cosmic:
Fix Committed
Bug description:
== SRU Justification ==
The requested commit fixes a regression introduce by mainline commit
3a2f70331226, in v4.18-rc1. The commit is only needed in Cosmic. Do to
the regression, A Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core)
== Fix ==
37fdffb217a4 ("net/mlx5: WQ, fixes for fragmented WQ buffers API")
== Regression Potential ==
Low. This commit has been cc'd to stable, so it has had additional
upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Michael Ranweiler - 2018-10-18 11:34:40 ==
---Problem Description---
At the system if u do
ethtool -S enP48p1s0f0 | grep wqe_err
rx_wqe_err: 1
rx0_wqe_err: 0
rx1_wqe_err: 0
rx2_wqe_err: 0
rx3_wqe_err: 1
rx4_wqe_err: 0
rx5_wqe_err: 0
rx6_wqe_err: 0
rx7_wqe_err: 0
rx8_wqe_err: 0
rx9_wqe_err: 0
rx10_wqe_err: 0
rx11_wqe_err: 0
rx12_wqe_err: 0
rx13_wqe_err: 0
rx14_wqe_err: 0
rx15_wqe_err: 0
Will see that rx side is hitting issue.
---Additional Hardware Info---
Mellanox CX5 Ethernet 100G
lspci
0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family
[ConnectX-5 Ex]
0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family
[ConnectX-5 Ex]
Machine Type = P9
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Using a CX5 Ethernet 100G card
lspci
0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family
[ConnectX-5 Ex]
0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family
[ConnectX-5 Ex]
just configure IP
ifconfig enP48p1s0f0 33.33.33.33 netmask 255.255.255.0 up
then partner system configure IP and then try ping -f
ping -f 33.33.33.33
PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data.
^C
--- 33.33.33.33 ping statistics ---
5413 packets transmitted, 5373 received, 0% packet loss, time 934ms
rtt min/avg/max/mdev = 0.015/0.019/0.669/0.010 ms, ipg/ewma 0.172/0.020 ms
# ping 33.33.33.33
PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data.
^C
--- 33.33.33.33 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1071ms
then at the recv system then do
ethtool -S enP48p1s0f0 | grep wqe_err
rx_wqe_err: 1
rx0_wqe_err: 0
rx1_wqe_err: 0
rx2_wqe_err: 0
rx3_wqe_err: 1
rx4_wqe_err: 0
rx5_wqe_err: 0
rx6_wqe_err: 0
rx7_wqe_err: 0
rx8_wqe_err: 0
rx9_wqe_err: 0
rx10_wqe_err: 0
rx11_wqe_err: 0
rx12_wqe_err: 0
rx13_wqe_err: 0
rx14_wqe_err: 0
rx15_wqe_err: 0
you will see rx_wqe_err with a counter non-zero.
This is fixed by this patch:
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=37fdffb217a45609edccbb8b407d031143f551c0
== Comment: #1 - Carol L. Soto - 2018-10-18 11:46:00 ==
I did a git clone to the cosmic tree and loaded the kernel in a system.
kernel 4.18.12 and I can recreate it.
lspci | grep Mell | grep ConnectX-5
:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family
[ConnectX-5 Ex]
:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family
[ConnectX-5 Ex]
0030:01:00.0 Infiniband controller: Mellanox Technologies MT28800 Family
[ConnectX-5 Ex]
0030:01:00.1 Infiniband controller: Mellanox Technologies MT28800 Family
[ConnectX-5 Ex]
:~# ethtool -S enp1s0f0 | grep wqe_err
rx_wqe_err: 2
rx0_wqe_err: 1
rx1_wqe_err: 1
rx2_wqe_err: 0
rx3_wqe_err: 0
rx4_wqe_err: 0
rx5_wqe_err: 0
rx6_wqe_err: 0
rx7_wqe_err: 0
rx8_wqe_err: 0
rx9_wqe_err: 0
rx10_wqe_err: 0
...
Let me check if the proposed patch needs backport or not.
== Comment: #3 - Carol L. Soto - 2018-10-18 13:34:46 ==
I was able to apply the proposed patch as it to the cosmic git tree and no
issue. (no need to backport)
using a kernel 4.18.12+.
With the proposed patch I do not see wqe err and ping does not stop.
ethtool -S enp1s0f0 | grep wqe_err
rx_wqe_err: 0
rx0_wqe_err: 0
rx1_wqe_err: 0
rx2_wqe_err: 0
rx3_wqe_err: 0
rx4_wqe_err: 0
rx5_wqe_err: 0
rx6_wqe_err: 0
rx7_wqe_err: 0
[Kernel-packages] [Bug 1792580] Re: Mounting SOFS SMB shares fails
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792580
Title:
Mounting SOFS SMB shares fails
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
Commit 395a2076b406 is needed to fix a bug in Bionic which causes mounting
SOFS SMB shares to fail. It was found that this commit fixes the bug
after a reverse bisect.
This fix has already landed in Cosmic.
== Fix ==
395a2076b406 ("cifs: connect to servername instead of IP for IPC$ share)"
== Regression Potential ==
Low. This is a one liner limited to cifs. It was also cc'd to upstream
stable, so it has had additional upstrem review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Ubuntu 18.04.1 LTS 4.15.0-33.36-generic
cifs-utils 2:6.8-1
Mounting scale-out SMB shares is failing.
mount -t cifs -o
credentials=/tmp/creds,domain=cbs.com,uid=114,gid=119,vers=3.0,_netdev,nodfs
//s2dscaleout.cbs.com/glance-images /tmp/test_mount
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
What works:
* mounting the share from a 16.04 host
* mounting standalone smb3 shares
Relevant error from the log (full logs attached separately):
Sep 14 11:12:05 r07-u13 kernel: Status code returned 0xc0c9
STATUS_NETWORK_NAME_DELETED
Sep 14 11:12:05 r07-u13 kernel:
/build/linux-81MBYC/linux-4.15.0/fs/cifs/smb2maperror.c: Mapping SMB2 status
code 0xc0c9 to POSIX err -5
Share server os: Windows Server 2016 10.0.14393
PS C:\Users\jujuadmin> get-smbshare glance-images | fl *
ShareState: Online
AvailabilityType : ScaleOut
ShareType : FileSystemDirectory
FolderEnumerationMode : Unrestricted
CachingMode : Manual
SmbInstance : Default
CATimeout : 0
ConcurrentUserLimit : 0
ContinuouslyAvailable : True
CurrentUsers : 2
Description :
EncryptData : False
Name : glance-images
Path : C:\ClusterStorage\Volume1\GLANCE-IMAGES
Scoped: True
ScopeName : S2DSCALEOUT
ShadowCopy: False
Special : False
Temporary : False
Volume: \\?\Volume{5faf880d-d308-4058-9ec2-d19d48089495}\
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 7 16:51 seq
crw-rw 1 root audio 116, 33 Sep 7 16:51 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Dell Inc. PowerEdge R710
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic
root=UUID=ba74e4cf-9634-4049-abd8-0ed721836a41 ro
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
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
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-33-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/23/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 6.4.0
dmi.board.name: 0YDJK3
dmi.board.vendor: Dell Inc.
dmi.board.version: A14
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR710:pvr:rvnDellInc.:rn0YDJK3:rvrA14:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R710
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792580/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802052] Re: WMI Error - ACPI Exception AE_NOT_FOUND
** Description changed: Backstory: The discrete touchpad enable/disable switch does not work on Ubuntu but works perfectly on windows. This is probably an issue of the msi_wmi drivers, so I tried to find a solution. Followed the instructions here - https://wiki.ubuntu.com/Kernel/Reference/WMI ACPI dump error - AE_NOT_EXIST Logs - https://pastebin.com/BKCHpie4 WMI dump error - AE_NOT_FOUND Logs - https://pastebin.com/aY6ngxzh + The problem persists in 4.19 kernel. + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: pratyush 4060 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: pratyush 4060 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 7 12:02:12 2018 InstallationDate: Installed on 2018-09-17 (50 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 002: ID 1038:1122 SteelSeries ApS - Bus 001 Device 004: ID 8087:0aaa Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 1038:1122 SteelSeries ApS + Bus 001 Device 004: ID 8087:0aaa Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=dba04826-1b60-412d-b2f4-06f876af3f8f ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash acpi_backlight=vendor nouveau.runpm=0 vt.handoff=1 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 + 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16Q2IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-16Q2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16Q2IMS.10E:bd08/27/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS65StealthThin8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16Q2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GS dmi.product.name: GS65 Stealth Thin 8RF dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802052 Title: WMI Error - ACPI Exception AE_NOT_FOUND Status in linux package in Ubuntu: New Bug description: Backstory: The discrete touchpad enable/disable switch does not work on Ubuntu but works perfectly on windows. This is probably an issue of the msi_wmi drivers, so I tried to find a solution. Followed the instructions here - https://wiki.ubuntu.com/Kernel/Reference/WMI ACPI dump error - AE_NOT_EXIST Logs - https://pastebin.com/BKCHpie4 WMI dump error - AE_NOT_FOUND Logs - https://pastebin.com/aY6ngxzh The problem persists in 4.19 kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pratyush 4060 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 7 12:02:12 2018 InstallationDate: Installed on 2018-09-17 (50 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1038:1122 SteelSeries ApS Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=dba0
[Kernel-packages] [Bug 1802052] [NEW] WMI Error - ACPI Exception AE_NOT_FOUND
Public bug reported: Backstory: The discrete touchpad enable/disable switch does not work on Ubuntu but works perfectly on windows. This is probably an issue of the msi_wmi drivers, so I tried to find a solution. Followed the instructions here - https://wiki.ubuntu.com/Kernel/Reference/WMI ACPI dump error - AE_NOT_EXIST Logs - https://pastebin.com/BKCHpie4 WMI dump error - AE_NOT_FOUND Logs - https://pastebin.com/aY6ngxzh The problem persists in 4.19 kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pratyush 4060 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 7 12:02:12 2018 InstallationDate: Installed on 2018-09-17 (50 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1038:1122 SteelSeries ApS Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=dba04826-1b60-412d-b2f4-06f876af3f8f ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash acpi_backlight=vendor nouveau.runpm=0 vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16Q2IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-16Q2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16Q2IMS.10E:bd08/27/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS65StealthThin8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16Q2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GS dmi.product.name: GS65 Stealth Thin 8RF dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1802052 Title: WMI Error - ACPI Exception AE_NOT_FOUND Status in linux package in Ubuntu: New Bug description: Backstory: The discrete touchpad enable/disable switch does not work on Ubuntu but works perfectly on windows. This is probably an issue of the msi_wmi drivers, so I tried to find a solution. Followed the instructions here - https://wiki.ubuntu.com/Kernel/Reference/WMI ACPI dump error - AE_NOT_EXIST Logs - https://pastebin.com/BKCHpie4 WMI dump error - AE_NOT_FOUND Logs - https://pastebin.com/aY6ngxzh The problem persists in 4.19 kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pratyush 4060 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 7 12:02:12 2018 InstallationDate: Installed on 2018-09-17 (50 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1038:1122 SteelSeries ApS Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=dba04826-1b60-412d-b2f4-06f876af3f8f ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash acpi_backlight=vendor nouveau.runpm=0 vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.versi
[Kernel-packages] [Bug 1800649] Re: Add support to NVIDIA GPU passthrough
The file passthrough-patches.tar.gz contains the following patches: 0001-kvm-no-need-to-check-return-value-of-debugfs_create-.patch 0002-powerpc-powernv-idoa-Remove-unnecessary-pcidev-from-.patch 0003-powerpc-Use-sizeof-foo-rather-than-sizeof-struct-foo.patch 0004-powerpc-powernv-npu-Do-not-try-invalidating-32bit-ta.patch 0005-powerpc-ioda-Use-ibm-supported-tce-sizes-for-IOMMU-p.patch 0006-powerpc-io-Add-__raw_writeq_be-__raw_rm_writeq_be.patch 0007-powerpc-powernv-Use-__raw_-rm_-writeq_be-in-pci-ioda.patch 0008-powerpc-powernv-ioda2-Remove-redundant-free-of-TCE-p.patch 0009-powerpc-powernv-ioda2-Reduce-upper-limit-for-DMA-win.patch 0010-Revert-cxl-Add-kernel-API-to-allow-a-context-to-oper.patch 0011-Revert-cxl-Add-support-for-interrupts-on-the-Mellano.patch 0012-Revert-cxl-Add-cxl_check_and_switch_mode-API-to-swit.patch 0013-Revert-cxl-Add-support-for-using-the-kernel-API-with.patch 0014-Revert-powerpc-powernv-Add-support-for-the-cxl-kerne.patch 0015-Revert-cxl-Add-cxl_slot_is_supported-API.patch 0016-cxl-Remove-abandonned-capi-support-for-the-Mellanox-.patch 0017-powerpc-powernv-ioda2-Add-256M-IOMMU-page-size-to-th.patch 0018-powerpc-powernv-Remove-useless-wrapper.patch 0019-powerpc-powernv-Move-TCE-manupulation-code-to-its-ow.patch 0020-KVM-PPC-Make-iommu_table-it_userspace-big-endian.patch 0021-powerpc-powernv-Add-indirect-levels-to-it_userspace.patch 0022-powerpc-powernv-Rework-TCE-level-allocation.patch 0023-powerpc-powernv-ioda-Allocate-indirect-TCE-levels-on.patch 0024-KVM-PPC-Validate-all-tces-before-updating-tables.patch 0025-KVM-PPC-Inform-the-userspace-about-TCE-update-failur.patch 0026-KVM-PPC-Validate-TCEs-against-preregistered-memory-p.patch 0027-KVM-PPC-Avoid-marking-DMA-mapped-pages-dirty-in-real.patch 0028-KVM-PPC-Propagate-errors-to-the-guest-when-failed-in.patch 0029-KVM-PPC-Remove-redundand-permission-bits-removal.patch 0030-vfio-pci-Quiet-broken-INTx-whining-when-INTx-is-unsu.patch 0031-KVM-PPC-Book3S-HV-Add-a-debugfs-file-to-dump-radix-m.patch 0032-cxl-Remove-unused-include.patch 0033-powerpc-powernv-ioda2-Reduce-upper-limit-for-DMA-win.patch 0034-powerpc-powernv-ioda-Allocate-indirect-TCE-levels-of.patch 0035-powerpc-pseries-iommu-Allow-dynamic-window-to-start-.patch 0036-KVM-PPC-Optimize-clearing-TCEs-for-sparse-tables.patch 0037-powerpc-powernv-npu-Add-a-debugfs-setting-to-change-.patch 0038-powerpc-powernv-npu-Remove-unused-headers-and-a-macr.patch 0039-KVM-PPC-Expose-userspace-mm-context-id-via-debugfs.patch 0040-powerpc-ioda-npu2-Call-hot-reset-skiboot-hook-when-d.patch 0041-vfio-spapr_tce-Get-rid-of-possible-infinite-loop.patch 0042-vfio-spapr_tce-Simplify-page-contained-test.patch 0043-powerpc-iommu_context-Change-referencing-in-API.patch 0044-powerpc-iommu-Do-not-pin-memory-of-a-memory-device.patch 0045-vfio_pci-Allow-mapping-extra-regions.patch 0046-vfio_pci-Allow-regions-to-add-own-capabilities.patch 0047-powerpc-powernv-npu-Simplify-nestMMU-flush-flag-copy.patch 0048-powerpc-npu-dma-Add-helper-to-access-struct-npu-for-.patch 0049-powerpc-powernv-npu-Collect-all-static-symbols-under.patch 0050-FIXME-powerpc-powernv-Detach-npu-struct-from-pnv_phb.patch 0051-powerpc-pseries-iommu-Force-default-DMA-window-remov.patch 0052-powerpc-pseries-iommu-Use-memory-nodes-in-max-RAM-ad.patch 0053-FIXME-powerpc-pseries-npu2-Enable-platform-support.patch 0054-vfio_pci-Add-NVIDIA-GV100GL-Tesla-V100-SXM2-10de-1db.patch They were generated based on master-next@git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git These are related to Linux KVM only. ** Patch removed: "0001-kvm-no-need-to-check-return-value-of-debugfs_create-.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800649/+attachment/5209841/+files/0001-kvm-no-need-to-check-return-value-of-debugfs_create-.patch ** Attachment added: "patches" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800649/+attachment/5209842/+files/passthrough-patches.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800649 Title: Add support to NVIDIA GPU passthrough Status in linux package in Ubuntu: Incomplete Bug description: This bug will keep track of an important feature that is being developed upstream and need to be backported to Ubuntu 18.04 PPC64. The feature allows QEMU/KVM guests to have NVIDIA GPUs passed-through. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780654] Re: Realtek Ethernet driver lost after update to kernel 4.15.0-24
I am getting the same exact bug on Ubuntu 18.04.1 with linux kernel 4.15.0-38 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780654 Title: Realtek Ethernet driver lost after update to kernel 4.15.0-24 Status in linux package in Ubuntu: Confirmed Bug description: After automatic update to kernel 4.15.0-24 from 4.13 in my Ubuntu 16.04 desktop installation, the ethernet driver r8168 dissapears and the device is not recognized by the system. This issue appears every time my kernel is updated. I assume this is because I installed the latest version from the vendor manually. (8.45) It is usually solved rebuilding the driver. But with this kernel update, now the driver update procedure fails in the compilation phase. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-45-generic 4.13.0-45.50~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: i3 Date: Sun Jul 8 17:39:03 2018 InstallationDate: Installed on 2017-06-04 (399 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800649] Re: Add support to NVIDIA GPU passthrough
The patch attached here contains the necessary to build QEMU with support to nvlink2 passthrough: 0001-qdev-Use-string-for-QOM-string-properties.patch 0002-ppc-spapr-Receive-and-store-device-tree-blob-from-SL.patch 0003-DBG-store-fdt.patch 0004-vfio-spapr-Fix-indirect-levels-calculation.patch 0005-headers-update.patch 0006-pci-Move-NVIDIA-vendor-id-to-the-rest-of-ids.patch 0007-RFC-vfio-nvidia-v100-Disable-VBIOS-update.patch 0008-spapr-iommu-Always-advertise-the-maximum-possible-DM.patch 0009-FIXME-vfio-Do-not-replay-IOMMU-mappings.patch 0010-vfio-Make-vfio_get_region_info_cap-public.patch 0011-vfio-spapr-Try-allocating-less-levels-if-failed-with.patch 0012-spapr-Add-NVLink2-memory-to-PHB-placement.patch 0013-spapr-Create-ibm-gpu-and-ibm-npu-cross-links-in-the-.patch 0014-spapr-vfio-Map-GPU-RAM-and-advertise-to-the-guest.patch 0015-debug-Disables-KVM-TCE-acceleration-and-direct-ATSD-.patch https://github.com/aik/qemu/tree/nv2 ** Attachment added: "qemu-patches.tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800649/+attachment/5209845/+files/qemu-patches.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800649 Title: Add support to NVIDIA GPU passthrough Status in linux package in Ubuntu: Incomplete Bug description: This bug will keep track of an important feature that is being developed upstream and need to be backported to Ubuntu 18.04 PPC64. The feature allows QEMU/KVM guests to have NVIDIA GPUs passed-through. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working
I tried the 4.15.0-39 kernel. It still doesn't work but there's a difference in the dmesg output, which I attached. This message is new / different: [2.908167] i2c_hid i2c-ELAN469D:00: hid_descr_cmd failed This kernel did, as before with other 4.15 kernels, fix the microphone input problem I reported here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796582 Kinda disappointed that no progress was made yet on that bug, since 4.15 provides a working reference. Any of the other people here with the same laptop have the non-working microphone as well in 4.18 and 4.19? If so, please add your voice to that bug. ** Attachment added: "dmesg-4.15.0-39.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795292/+attachment/5209844/+files/dmesg-4.15.0-39.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/1795292 Title: ELAN469D touch pad not working Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800649] Re: Add support to NVIDIA GPU passthrough
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800649 Title: Add support to NVIDIA GPU passthrough Status in linux package in Ubuntu: Incomplete Bug description: This bug will keep track of an important feature that is being developed upstream and need to be backported to Ubuntu 18.04 PPC64. The feature allows QEMU/KVM guests to have NVIDIA GPUs passed-through. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791030] Re: package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to install/upgrade: package linux-image-extra-4.4.0-131-generic is not ready for configuration cann
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791030 Title: package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to install/upgrade: package linux-image-extra-4.4.0-131-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: Expired Bug description: bug during update (???) Cordially ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-131-generic 4.4.0-131.157 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eric 6073 F pulseaudio /dev/snd/seq:timidity 1500 F timidity Date: Thu Sep 6 09:48:42 2018 ErrorMessage: package linux-image-extra-4.4.0-131-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=2fd83354-6537-4d4a-9080-0fd25e636274 InstallationDate: Installed on 2012-07-21 (2237 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120425-15:28 MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-134-generic root=UUID=e2cf79c0-5225-4f68-9c25-bde3c11e9747 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.18 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to install/upgrade: package linux-image-extra-4.4.0-131-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO GEN3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd09/16/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPROGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800649] Re: Add support to NVIDIA GPU passthrough
** Patch added: "0001-kvm-no-need-to-check-return-value-of-debugfs_create-.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800649/+attachment/5209841/+files/0001-kvm-no-need-to-check-return-value-of-debugfs_create-.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800649 Title: Add support to NVIDIA GPU passthrough Status in linux package in Ubuntu: Incomplete Bug description: This bug will keep track of an important feature that is being developed upstream and need to be backported to Ubuntu 18.04 PPC64. The feature allows QEMU/KVM guests to have NVIDIA GPUs passed-through. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801716] Re: Xorg freeze (black screen after ubuntu logo during boot)
I am so so so sorry for I made a mistake of selecting the wrong kernel with the wrong architecture to install, which lead to all those error messages during boot in v4.19. (My laptop should install the kernel with architecture amd64 but I installed i386, I am so sorry for making things more complicated, SORRY!!!) Anyway, I "apt purge" the wrong kernel (4.19 with architecture i386) and just installed the proper one(architecture amd64). However! The issue in the v4.17 remain in the 4.19! I don't see anything improve in my situation, I still can't get in the system, getting stuck in the black screen after the Ubuntu logo during the boot, I can only access the system in recovery mode; the brightness of my display can't be adjusted; the setting for my display still says "Unknown Display", and the laptop can't get back if I put the whole system into sleep mode(by turn off the display) Any idea? Please help Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801716 Title: Xorg freeze (black screen after ubuntu logo during boot) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I experienced this bug ever since I have upgraded my laptop from 16.04. But it got resolved in my last update after I reported the bug. However, I forgot to go back to Launchpad to mark it as resolved and now the problem comes again after I just updated the system. So, as the title stated, I can't get in the system due to the infinite black screen I am facing. I am only able to report this bug under the recovery mode. Besides, there's something wrong with the lock screen too. I can't get back to the system if I just put the system into "sleep mode". Black screen again! What's worst, the brightness of my display can't be adjusted as well! I feel like being blind at night! Please help!!! Thank you! And I think there might be the compatibility problem between my laptop and the new desktop -- Gnome, which is the default in 18.04. What should do? I really love using Ubuntu, as I really learned a lot in these days I used it as my study os for CS. Any help is appreciated, thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.17.0-041700rc3-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 19:49:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 08) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:15fd] InstallationDate: Installed on 2018-04-04 (215 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK COMPUTER INC. T300FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic root=UUID=63fcbd04-ec8b-462c-ba66-4f45c229353c ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300FA.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300FA.214:bd09/01/2015:svnASUSTeKCOMPUTERINC.:pnT300FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T300FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Nov 6 03:47:33 2018 xserver.configfile: default xserver.err
[Kernel-packages] [Bug 1801856] Re: seccomp in ubuntu_stress_smoke_test failed on ARM64/Power8 Trusty
** Changed in: ubuntu-kernel-tests 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/1801856 Title: seccomp in ubuntu_stress_smoke_test failed on ARM64/Power8 Trusty Status in Stress-ng: New Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Didn't see this on amd64 / i386, but it can be reproduced on power8 and ARM64 seccomp STARTING seccomp RETURNED 2 seccomp FAILED stress-ng: debug: [7528] 8 processors online, 8 processors configured stress-ng: info: [7528] dispatching hogs: 4 seccomp stress-ng: debug: [7528] /sys/devices/system/cpu/cpu0/cache does not exist stress-ng: info: [7528] cache allocate: using built-in defaults as unable to determine cache details stress-ng: debug: [7528] cache allocate: default cache size: 2048K stress-ng: debug: [7528] starting stressors stress-ng: debug: [7529] stress-ng-seccomp: started [7529] (instance 0) stress-ng: debug: [7528] 4 stressors spawned stress-ng: debug: [7530] stress-ng-seccomp: started [7530] (instance 1) stress-ng: fail: [7533] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, errno=22 (Invalid argument) stress-ng: fail: [7534] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, errno=22 (Invalid argument) stress-ng: debug: [7531] stress-ng-seccomp: started [7531] (instance 2) stress-ng: fail: [7530] stress-ng-seccomp: aborting because of unexpected failure in child process stress-ng: debug: [7530] stress-ng-seccomp: exited [7530] (instance 1) stress-ng: fail: [7529] stress-ng-seccomp: aborting because of unexpected failure in child process stress-ng: debug: [7529] stress-ng-seccomp: exited [7529] (instance 0) stress-ng: debug: [7532] stress-ng-seccomp: started [7532] (instance 3) stress-ng: error: [7528] process 7529 (stress-ng-seccomp) terminated with an error, exit status=1 (stress-ng core failure) stress-ng: debug: [7528] process [7529] terminated stress-ng: error: [7528] process 7530 (stress-ng-seccomp) terminated with an error, exit status=1 (stress-ng core failure) stress-ng: debug: [7528] process [7530] terminated stress-ng: fail: [7535] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, errno=22 (Invalid argument) stress-ng: fail: [7536] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, errno=22 (Invalid argument) stress-ng: fail: [7532] stress-ng-seccomp: aborting because of unexpected failure in child process stress-ng: debug: [7531] stress-ng-seccomp: exited [7531] (instance 2) stress-ng: error: [7528] process 7531 (stress-ng-seccomp) terminated with an error, exit status=1 (stress-ng core failure) stress-ng: debug: [7528] process [7531] terminated stress-ng: error: [7528] process 7532 (stress-ng-seccomp) terminated with an error, exit status=1 (stress-ng core failure) stress-ng: debug: [7528] process [7532] terminated stress-ng: info: [7528] unsuccessful run completed in 0.00s ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-161-generic 3.13.0-161.211 ProcVersionSignature: User Name 3.13.0-161.211-generic 3.13.11-ckt39 Uname: Linux 3.13.0-161-generic aarch64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: Date: Tue Nov 6 06:23:27 2018 IwConfig: lono wireless extensions. enp1s0no wireless extensions. enp1s0d1 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-3.13.0-161-generic N/A linux-backports-modules-3.13.0-161-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1801856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801875] Re: Power consumption during s2idle is higher than long idle(sk hynix)
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801875 Title: Power consumption during s2idle is higher than long idle(sk hynix) Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: [Impact] On some Dell XPS models, we observed the power consumption raises higher than long idle does during s2idle with sk hynix nvme. C2: Short idle: 4 Long idle: 1 S2I: 3.7 S5: 0.19 C3: Short idle: 7.2 Long idle: 4.5 S2I: 6.22 S5: 0.18 C5: Short idle: 6.5 Long idle: 1 S2I: 2.88 S5: 0.18 [Fix] From SK hynix FE, MS Windows doesn't put nvme to D3, and uses its own APST feature to do the power management. To leverage its APST feature during s2idle, we can't disable nvme device while suspending, too. So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. prevent nvme from being disabled when suspending. [Test] Verified on different XPS machines with different sk hynix nvme disks, it fixes the power consumption issue with no regression. And the power consumption drops to 0.77W during s2idle. [Regression Potential] Low, the patches only applied to specific nvme module, and from our test, the system is still stable. [Misc] This issue should be fixed by the firmware, and we're pushing sk hynix to fix it. But before sk hynix find out how to solve it, we have to preserve these commits in our kernel for a while. BTW, the patches use pm_suspend_via_s2idle() function from below commit which is still under reviewing. https://lists.ubuntu.com/archives/kernel-team/2018-October/096141.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1229662] Re: [AMD Radeon HD 6450][1002:6779] No DisplayPort audio output with radeon driver
*** This bug is a duplicate of bug 1186879 *** https://bugs.launchpad.net/bugs/1186879 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-lts-vivid (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1229662 Title: [AMD Radeon HD 6450][1002:6779] No DisplayPort audio output with radeon driver Status in linux-lts-vivid package in Ubuntu: Confirmed Status in xserver-xorg-video-ati-lts-raring package in Ubuntu: Confirmed Bug description: CID: 201201-10383 Dell Optiplex 7010 DT No DisplayPort audio output with the open source radeon driver. The output source does not appear in the Sound settings when the DisplayPort was connected. This problem could be solved by installing the AMD proprietary driver. And according to comment #5 in bug 1186879, it seems that this audio feature was disabled intentionally. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-radeon-lts-raring 1:7.1.0-0ubuntu2~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Tue Sep 24 06:32:44 2013 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-ati-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1229662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801976] Re: Display does not work correctly
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1801976 Title: Display does not work correctly Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Initially everything was fine. Then came an update and now the display is milky and too large. I dont know what to do. What would be the proper BIOS Setting or how can the issue be settled? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Tue Nov 6 18:07:43 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c0d1] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 620M/630M/635M/640M LE] [144d:c0d1] InstallationDate: Installed on 2018-11-06 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: SAMSUNG ELECTRONICS CO., LTD. 550P5C/550P7C ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=e703b236-f073-42b6-bcef-3f6eca97246c ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P09ABI.026.141024.dg dmi.board.asset.tag: No Asset Tag dmi.board.name: NP550P7C-T0ADE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP09ABI.026.141024.dg:bd10/24/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn550P5C/550P7C:pvrP09ABI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550P7C-T0ADE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: SAMSUNG SENS dmi.product.name: 550P5C/550P7C dmi.product.version: P09ABI dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801747] 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/1801747 Title: External display not recognized, internal one goes to black Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: Hi, I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu 18.04.1 I face a problem on ALL of them, as soon as I connect an external screen, doesn't matter VGA or HDMI, the internal screen goes black, only mouse icon is their, blinking from time to time but reacting. External screen does show nothing but there is no "no signal" info what means that source is recognized. As soon as I release the video cable from external display, the internal one come back to live after few seconds. The BIOS was updated to latest available. Daniel tootai@hirondelle:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Mon Nov 5 16:30:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2018-10-19 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU0012B8R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black
** Changed in: gdm3 (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => 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/1801747 Title: External display not recognized, internal one goes to black Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi, I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu 18.04.1 I face a problem on ALL of them, as soon as I connect an external screen, doesn't matter VGA or HDMI, the internal screen goes black, only mouse icon is their, blinking from time to time but reacting. External screen does show nothing but there is no "no signal" info what means that source is recognized. As soon as I release the video cable from external display, the internal one come back to live after few seconds. The BIOS was updated to latest available. Daniel tootai@hirondelle:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Mon Nov 5 16:30:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2018-10-19 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU0012B8R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800752] Re: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance
apport information ** Tags added: apport-collected ** Description changed: I run a BOINC project which uses opencl_intel on my Kubunut system On bioinc the tasks ran in 12,000 +/- 200 seconds. They've been doing that for ~6 months. I've now updated the system to cosmic, and the task are not taking 19,000 +/- 200s. I have another system (which is still running Mint18.3 - and hasn't changed) which also runs these tasks and the timings there have not changed, so the tasks themselves are still equivalent. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: beignet-opencl-icd 1.3.2-4 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 CurrentDesktop: KDE Date: Wed Oct 31 01:17:08 2018 InstallationDate: Installed on 2018-05-09 (174 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: beignet UpgradeStatus: Upgraded to cosmic on 2018-10-26 (4 days ago) + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13 + Architecture: amd64 + DistroRelease: Ubuntu 18.10 + InstallationDate: Installed on 2018-03-23 (228 days ago) + InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) + Package: linux + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 + Tags: cosmic + Uname: Linux 4.18.0-10-generic x86_64 + UpgradeStatus: Upgraded to cosmic on 2018-10-28 (9 days ago) + UserGroups: + + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1800752/+attachment/5209799/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800752 Title: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance Status in beignet package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Bug description: I run a BOINC project which uses opencl_intel on my Kubunut system On bioinc the tasks ran in 12,000 +/- 200 seconds. They've been doing that for ~6 months. I've now updated the system to cosmic, and the task are not taking 19,000 +/- 200s. I have another system (which is still running Mint18.3 - and hasn't changed) which also runs these tasks and the timings there have not changed, so the tasks themselves are still equivalent. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: beignet-opencl-icd 1.3.2-4 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 CurrentDesktop: KDE Date: Wed Oct 31 01:17:08 2018 InstallationDate: Installed on 2018-05-09 (174 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: beignet UpgradeStatus: Upgraded to cosmic on 2018-10-26 (4 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-03-23 (228 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-28 (9 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800752] Re: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance
Only affect Cosmic. Bionic is 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/1800752 Title: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance Status in beignet package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Bug description: I run a BOINC project which uses opencl_intel on my Kubunut system On bioinc the tasks ran in 12,000 +/- 200 seconds. They've been doing that for ~6 months. I've now updated the system to cosmic, and the task are not taking 19,000 +/- 200s. I have another system (which is still running Mint18.3 - and hasn't changed) which also runs these tasks and the timings there have not changed, so the tasks themselves are still equivalent. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: beignet-opencl-icd 1.3.2-4 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 CurrentDesktop: KDE Date: Wed Oct 31 01:17:08 2018 InstallationDate: Installed on 2018-05-09 (174 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: beignet UpgradeStatus: Upgraded to cosmic on 2018-10-26 (4 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-03-23 (228 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-28 (9 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800752] Re: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance
OK. So I have to run as root *while logged in to desktop of the system*. Just being logged in as root (on a system where I "never" user the console...) over the network isn't good enough. Now done. It claims to have submitted data. I'll change the state to Confirmed. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800752 Title: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance Status in beignet package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Bug description: I run a BOINC project which uses opencl_intel on my Kubunut system On bioinc the tasks ran in 12,000 +/- 200 seconds. They've been doing that for ~6 months. I've now updated the system to cosmic, and the task are not taking 19,000 +/- 200s. I have another system (which is still running Mint18.3 - and hasn't changed) which also runs these tasks and the timings there have not changed, so the tasks themselves are still equivalent. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: beignet-opencl-icd 1.3.2-4 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 CurrentDesktop: KDE Date: Wed Oct 31 01:17:08 2018 InstallationDate: Installed on 2018-05-09 (174 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: beignet UpgradeStatus: Upgraded to cosmic on 2018-10-26 (4 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-03-23 (228 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-28 (9 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800752] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1800752/+attachment/5209800/+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/1800752 Title: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance Status in beignet package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Bug description: I run a BOINC project which uses opencl_intel on my Kubunut system On bioinc the tasks ran in 12,000 +/- 200 seconds. They've been doing that for ~6 months. I've now updated the system to cosmic, and the task are not taking 19,000 +/- 200s. I have another system (which is still running Mint18.3 - and hasn't changed) which also runs these tasks and the timings there have not changed, so the tasks themselves are still equivalent. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: beignet-opencl-icd 1.3.2-4 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 CurrentDesktop: KDE Date: Wed Oct 31 01:17:08 2018 InstallationDate: Installed on 2018-05-09 (174 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: beignet UpgradeStatus: Upgraded to cosmic on 2018-10-26 (4 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-03-23 (228 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-28 (9 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800164] Re: Keyboard backlight control doesn't work on Asus N550JV
*** This bug is a duplicate of bug 1796550 *** https://bugs.launchpad.net/bugs/1796550 ** Package changed: linux (Ubuntu) => upower (Ubuntu) ** Changed in: upower (Ubuntu) Status: Fix Released => Confirmed ** This bug has been marked a duplicate of bug 1796550 [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800164 Title: Keyboard backlight control doesn't work on Asus N550JV Status in upower package in Ubuntu: Confirmed Bug description: Pressing Fn+F3 or Fn+F4 keys (which are the combinations to increase or decrease keyboard backlight brightness, respectively) doesn't do anything, the keyboard backlight stays off. Other key combinations, like adjusting display brightness or audio volume, do work. Keyboard backlight control worked in Kubuntu 18.04 on the same machine. 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 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 2820 F pulseaudio /dev/snd/controlC1: lastique 2820 F pulseaudio CurrentDesktop: KDE Date: Fri Oct 26 17:40:24 2018 InstallationDate: Installed on 2013-10-11 (1840 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. N550JV ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=bafa6509-dea3-48a1-a308-129b1514ab28 ro quiet splash nmi_watchdog=0 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-20 (6 days ago) WifiSyslog: dmi.bios.date: 11/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JV dmi.product.sku: ASUS-NotebookSKU 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/upower/+bug/1800164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800752] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1800752/+attachment/5209801/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800752 Title: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance Status in beignet package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Bug description: I run a BOINC project which uses opencl_intel on my Kubunut system On bioinc the tasks ran in 12,000 +/- 200 seconds. They've been doing that for ~6 months. I've now updated the system to cosmic, and the task are not taking 19,000 +/- 200s. I have another system (which is still running Mint18.3 - and hasn't changed) which also runs these tasks and the timings there have not changed, so the tasks themselves are still equivalent. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: beignet-opencl-icd 1.3.2-4 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 CurrentDesktop: KDE Date: Wed Oct 31 01:17:08 2018 InstallationDate: Installed on 2018-05-09 (174 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: beignet UpgradeStatus: Upgraded to cosmic on 2018-10-26 (4 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-03-23 (228 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-28 (9 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799994] Re: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1
OK. Next we probably want to get an idea of what gdm is doing. Please reproduce the problem, then reboot and collect the system log of the previous boot where the problem occured: journalctl -b-1 > prev_boot.txt and attach prev_boot.txt. ** No longer affects: nvidia-graphics-drivers-390 (Ubuntu) ** No longer affects: linux (Ubuntu) -- 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/174 Title: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 Status in gdm3 package in Ubuntu: Incomplete Bug description: Lenovo ThinkPad W540 docked with an ultradock. 3 external displays running on VGA, DVI and display port all connected to the dock. BIOS mode set to run external displays ONLY with nvidia chipset. prime- select nvidia run. When running under 4.15.0-36-generic with nvidia 390.77-0ubuntu0.18.04.1 I boot and all three external displays run fine. Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timr 3768 F pulseaudio /dev/snd/controlC1: timr 3768 F pulseaudio /dev/snd/controlC0: timr 3768 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-image-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" 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: Upgraded to bionic on 2018-08-17 (69 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS0240
[Kernel-packages] [Bug 1800752] Re: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance
>> I've installed it - it might now be collecting data... No, it's not. It fired up the OAuth authorization page, which I authorized (and got the mail confirmation). Now it just sits there -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800752 Title: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance Status in beignet package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Bug description: I run a BOINC project which uses opencl_intel on my Kubunut system On bioinc the tasks ran in 12,000 +/- 200 seconds. They've been doing that for ~6 months. I've now updated the system to cosmic, and the task are not taking 19,000 +/- 200s. I have another system (which is still running Mint18.3 - and hasn't changed) which also runs these tasks and the timings there have not changed, so the tasks themselves are still equivalent. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: beignet-opencl-icd 1.3.2-4 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 CurrentDesktop: KDE Date: Wed Oct 31 01:17:08 2018 InstallationDate: Installed on 2018-05-09 (174 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: beignet UpgradeStatus: Upgraded to cosmic on 2018-10-26 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802026] 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/1802026 Title: Kernel bug - possible race or inode issue - 4.15.0-38 Status in linux package in Ubuntu: Confirmed Bug description: Release: Ubuntu 18.04 /proc/version_signature: Ubuntu 4.15.0-38.41-generic 4.15.18 Issue was triggered when running the following: . IO intensive application (steamos) . Virtualization application (VMware workstation) . Heavy IO between various FS/LVs atop of MD devices . Out of Space situation - an FS/LV resize was executed to alleviate Attached is kern.log which captures the sequence of the Kernel WARNINGS/BUGS . Notable items in kern.log (attached) - Nov 6 10:05:30 FrankWorkstation0 kernel: [588291.771562] WARNING: CPU: 4 PID: 15553 at /build/linux-CuEUJv/linux-4.15.0/fs/ext4/inode.c:3892 ext4_set_page_dirty+0x44/0x60 Nov 6 15:02:15 FrankWorkstation0 kernel: [606096.787691] WARNING: CPU: 5 PID: 15552 at /build/linux-CuEUJv/linux-4.15.0/fs/ext4/inode.c:3893 ext4_set_page_dirty+0x4e/0x60 Nov 6 15:02:16 FrankWorkstation0 kernel: [606097.800925] kernel BUG at /build/linux-CuEUJv/linux-4.15.0/fs/ext4/inode.c:2680! Nov 6 15:02:16 FrankWorkstation0 kernel: [606097.853375] WARNING: CPU: 9 PID: 20503 at /build/linux-CuEUJv/linux-4.15.0/kernel/exit.c:771 do_exit+0x51/0xb40 This led to an application crash/halt situation - steamos hung, vmware-vmx hung, and during shutdown an unclean power off due to vmware-vmx not allowing a clean umount. Slight FS corruption occurred. Please advise if BUG confirmed, or if other items to check. unable to attempt to recreat bug - not able to risk data loss on working system ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: frank 2689 F pulseaudio /dev/snd/controlC2: frank 2689 F pulseaudio /dev/snd/controlC1: frank 2689 F pulseaudio /dev/snd/controlC0: frank 2689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 6 18:14:59 2018 HibernationDevice: RESUME=/dev/mapper/FrankWorkstation0--vg-swap_1 InstallationDate: Installed on 2018-10-26 (11 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Precision 5820 Tower ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=/dev/mapper/hostname--vg-root ro ipv6.disable=1 ipv6.disable=1 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 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0X8DXD dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd09/04/2018:svnDellInc.:pnPrecision5820Tower:pvr:rvnDellInc.:rn0X8DXD:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision 5820 Tower dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802026] [NEW] Kernel bug - possible race or inode issue - 4.15.0-38
Public bug reported: Release: Ubuntu 18.04 /proc/version_signature: Ubuntu 4.15.0-38.41-generic 4.15.18 Issue was triggered when running the following: . IO intensive application (steamos) . Virtualization application (VMware workstation) . Heavy IO between various FS/LVs atop of MD devices . Out of Space situation - an FS/LV resize was executed to alleviate Attached is kern.log which captures the sequence of the Kernel WARNINGS/BUGS . Notable items in kern.log (attached) - Nov 6 10:05:30 FrankWorkstation0 kernel: [588291.771562] WARNING: CPU: 4 PID: 15553 at /build/linux-CuEUJv/linux-4.15.0/fs/ext4/inode.c:3892 ext4_set_page_dirty+0x44/0x60 Nov 6 15:02:15 FrankWorkstation0 kernel: [606096.787691] WARNING: CPU: 5 PID: 15552 at /build/linux-CuEUJv/linux-4.15.0/fs/ext4/inode.c:3893 ext4_set_page_dirty+0x4e/0x60 Nov 6 15:02:16 FrankWorkstation0 kernel: [606097.800925] kernel BUG at /build/linux-CuEUJv/linux-4.15.0/fs/ext4/inode.c:2680! Nov 6 15:02:16 FrankWorkstation0 kernel: [606097.853375] WARNING: CPU: 9 PID: 20503 at /build/linux-CuEUJv/linux-4.15.0/kernel/exit.c:771 do_exit+0x51/0xb40 This led to an application crash/halt situation - steamos hung, vmware-vmx hung, and during shutdown an unclean power off due to vmware-vmx not allowing a clean umount. Slight FS corruption occurred. Please advise if BUG confirmed, or if other items to check. unable to attempt to recreat bug - not able to risk data loss on working system ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: frank 2689 F pulseaudio /dev/snd/controlC2: frank 2689 F pulseaudio /dev/snd/controlC1: frank 2689 F pulseaudio /dev/snd/controlC0: frank 2689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 6 18:14:59 2018 HibernationDevice: RESUME=/dev/mapper/FrankWorkstation0--vg-swap_1 InstallationDate: Installed on 2018-10-26 (11 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Precision 5820 Tower ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=/dev/mapper/hostname--vg-root ro ipv6.disable=1 ipv6.disable=1 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 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0X8DXD dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd09/04/2018:svnDellInc.:pnPrecision5820Tower:pvr:rvnDellInc.:rn0X8DXD:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision 5820 Tower dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic ** Attachment added: "Kern.Log files capturing from power up to BUG event" https://bugs.launchpad.net/bugs/1802026/+attachment/5209782/+files/kernlogs.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802026 Title: Kernel bug - possible race or inode issue - 4.15.0-38 Status in linux package in Ubuntu: Confirmed Bug description: Release: Ubuntu 18.04 /proc/version_signature: Ubuntu 4.15.0-38.41-generic 4.15.18 Issue was triggered when running the following: . IO intensive application (steamos) . Virtualization application (VMware workstation) . Heavy IO between various FS/LVs atop of MD devices . Out of Space situation - an FS/LV resize was executed to alleviate Attached is kern.log which captures the sequence of the Kernel WARNINGS/BUGS . Notable items in kern.log (attached) - Nov 6 10:05:30 FrankWorkstation0 kernel: [588291.771562] WARNING: CPU: 4 PID: 15553 at /build/linux-CuEUJv/linux-4.15.0/fs/ext4/inode.c:3892 ext4_set_page_dirty+0x44/0x60 Nov 6 15:02:15 FrankWorkstation0 kernel: [606096.787691] WARNING: CPU: 5 PID: 15552 at /build/linux-CuEUJv/linux-4.15.0/fs/ext4/inode.c:3893 ext4_set_page_dirty+0x4e/0x60 Nov 6 15:02:16 FrankWorkstation0 kernel: [606097.800925] kernel BUG at /build/linux-CuEUJv/linux-4.15.0/fs/ext4/inode.c:2680! Nov 6 15:02:16 FrankWorkstation0 kernel: [606097.853375] WARNING: CPU: 9 PID: 20503 at /build/linux-CuEUJv/linux-4.15.0/kernel/exit.c:771 do_exit+0x51/0xb40 This led to an application crash/halt situation - steamos hung, vmware-vmx hung, and during shu
[Kernel-packages] [Bug 1802023] [NEW] hns3: map tx ring to tc
Public bug reported: [Impact] hns3 supports hardware-based traffic classes. However, this requires that the driver map the classes to hardware rings during initialization. [Test Case] I don't have a way to verify that the hardware is behaving as programmed, so this is regression-tested only. [Fix] 1c77215480bcf net: hns3: Set tx ring' tc info when netdev is up [Regression Risk] Restricted to a single driver, which has been tested on the target SoC. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802023 Title: hns3: map tx ring to tc Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] hns3 supports hardware-based traffic classes. However, this requires that the driver map the classes to hardware rings during initialization. [Test Case] I don't have a way to verify that the hardware is behaving as programmed, so this is regression-tested only. [Fix] 1c77215480bcf net: hns3: Set tx ring' tc info when netdev is up [Regression Risk] Restricted to a single driver, which has been tested on the target SoC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802021] [NEW] [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
Public bug reported: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev&id=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: linux-azure (Ubuntu) Status: New => 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux-azure package in Ubuntu: Confirmed Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kerne
[Kernel-packages] [Bug 1800752] Re: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance
>> Further information may be available in the files (readable only by root, >> the 0 may be different if you have more than one graphics device): Info attached (only 0 has those files) for both Cosmic (4.18.0-10-generic) and Bionic (4.15.0-38-generic) kernels. (The change mentioned in #14 seems to have gone into 4.17.) ** Attachment added: "4.18.0-10-generic (Cosmic) dri info" https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+attachment/5209780/+files/dri-info.4.18.0-10-generic.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/1800752 Title: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance Status in beignet package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Bug description: I run a BOINC project which uses opencl_intel on my Kubunut system On bioinc the tasks ran in 12,000 +/- 200 seconds. They've been doing that for ~6 months. I've now updated the system to cosmic, and the task are not taking 19,000 +/- 200s. I have another system (which is still running Mint18.3 - and hasn't changed) which also runs these tasks and the timings there have not changed, so the tasks themselves are still equivalent. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: beignet-opencl-icd 1.3.2-4 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 CurrentDesktop: KDE Date: Wed Oct 31 01:17:08 2018 InstallationDate: Installed on 2018-05-09 (174 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: beignet UpgradeStatus: Upgraded to cosmic on 2018-10-26 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800752] Re: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance
Here's the Bionic kernel info (couldn't seem to be able to attach two files to one comment?). ** Attachment added: "4.15.0-38-generic (Bionic) dri info" https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+attachment/5209781/+files/dri-info.4.15.0-38-generic.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/1800752 Title: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance Status in beignet package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Bug description: I run a BOINC project which uses opencl_intel on my Kubunut system On bioinc the tasks ran in 12,000 +/- 200 seconds. They've been doing that for ~6 months. I've now updated the system to cosmic, and the task are not taking 19,000 +/- 200s. I have another system (which is still running Mint18.3 - and hasn't changed) which also runs these tasks and the timings there have not changed, so the tasks themselves are still equivalent. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: beignet-opencl-icd 1.3.2-4 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 CurrentDesktop: KDE Date: Wed Oct 31 01:17:08 2018 InstallationDate: Installed on 2018-05-09 (174 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: beignet UpgradeStatus: Upgraded to cosmic on 2018-10-26 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772675] Re: Intel i40e PF reset due to incorrect MDD detection (continues...again...)
We are getting this error on all of our new systems (Dell 14G C6420) running Xenial. I've tried 4.4.0-139-generic. I'm now trying 4.13.0-45-generic and see if it still shows up there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772675 Title: Intel i40e PF reset due to incorrect MDD detection (continues...again...) Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: [impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the nic, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [fix] The fix for this is currently unknown. As the "MDD event" is generated by the i40e firmware, and is completely undocumented, there is no way to tell what the i40e driver did to cause the MDD event. [test case] the bug is unfortunately very difficult to reproduce, but as shown in this (and previous) bug comments, some users of the i40e have traffic that can consistently reproduce the problem (although usually on the order of days, or longer, to reproduce). Reproducing is easily detected, as the nw traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued [regression potential] unknown since the specific fix is unknown. [original description] This is a continuation from bug 1713553 and then bug 1723127; a patch was added in the first bug and then the second bug, to attempt to fix this, and it may have helped reduce the issue but appears not to have fixed it, based on more reports. See bug 1713553 and bug 1723127 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800752] Re: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance
apport-collect 1800752 produced: >> ERROR: The python3-launchpadlib package is not installed. This functionality >> is not available. which might explain why the info wasn't there... I've installed it - it might now be collecting data... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800752 Title: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance Status in beignet package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Bug description: I run a BOINC project which uses opencl_intel on my Kubunut system On bioinc the tasks ran in 12,000 +/- 200 seconds. They've been doing that for ~6 months. I've now updated the system to cosmic, and the task are not taking 19,000 +/- 200s. I have another system (which is still running Mint18.3 - and hasn't changed) which also runs these tasks and the timings there have not changed, so the tasks themselves are still equivalent. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: beignet-opencl-icd 1.3.2-4 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 CurrentDesktop: KDE Date: Wed Oct 31 01:17:08 2018 InstallationDate: Installed on 2018-05-09 (174 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: beignet UpgradeStatus: Upgraded to cosmic on 2018-10-26 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801975] Re: update to build for 4.19
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801975 Title: update to build for 4.19 Status in dm-writeboost package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Status in dm-writeboost source package in Disco: In Progress Status in linux source package in Disco: Invalid Bug description: dm-writeboost-dkms fails to build on linux 4.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1801975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799305] Re: No desktop after reboot when using nvidia graphics on 18.10
Yes, looks like it and editing /etc/gdm3/custom.conf to set "WaylandEnable=false" fixed the issue for me too. Thanks! -- 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/1799305 Title: No desktop after reboot when using nvidia graphics on 18.10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I upgraded from 18.04 to 18.10 and now the desktop does not start after a reboot. The console output ends with "Starting GNOME Display Manager". I cannot switch VTs, my keyboard and mouse are unresponsive though RESUIB sequence works to reboot. If I remote login using ssh, I can run "systemctrl restart gdm3" and I get a working login screen and can continue as expected. If I remove my nvidia drivers the desktop starts as expected after reboot. Examining /var/log/syslog appears to show the nvidia driver failing to load correctly; see below. In the failed state "systemctl status gdm3" shows: ● gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled) Active: active (running) since Mon 2018-10-22 22:06:38 BST; 16min ago Process: 1877 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, status=0/SUCCESS) Process: 1723 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1880 (gdm3) Tasks: 3 (limit: 4915) Memory: 5.7M CGroup: /system.slice/gdm.service └─1880 /usr/sbin/gdm3 Oct 22 22:06:35 hagrid systemd[1]: Starting GNOME Display Manager... Oct 22 22:06:38 hagrid systemd[1]: Started GNOME Display Manager. Oct 22 22:06:44 hagrid gdm-launch-environment][2108]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. root@hagrid:/var/log# grep 2634 syslog Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. . . . This is a section from syslog: Oct 22 22:06:53 hagrid systemd[1]: Starting NVIDIA Persistence Daemon... Oct 22 22:06:53 hagrid nvidia-persistenced: Verbose syslog connection opened Oct 22 22:06:53 hagrid systemd[1]: Started NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Now running with user ID 123 and group ID 129 Oct 22 22:06:54 hagrid [2750]: meta_kms_resources_init failed: Calling drmModeGetResources() failed, assuming we have no outputs Oct 22 22:06:54 hagrid gnome-session[2664]: gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid nvidia-persistenced: Started (2865) Oct 22 22:06:54 hagrid [2750]: Failed to create backend: No GPUs with outputs found Oct 22 22:06:54 hagrid nvidia-persistenced: device :01:00.0 - registered Oct 22 22:06:54 hagrid gnome-session-binary[2664]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 22 22:06:54 hagrid nvidia-persistenced: Local RPC service initialized Oct 22 22:06:54 hagrid systemd[1]: Stopping NVIDIA Persistence Daemon... Oct 22 22:06:54 hagrid kernel: [ 86.847749] virbr0: port 1(virbr0-nic) entered blocking state Oct 22 22:06:54 hagrid kernel: [ 86.847753] virbr0: port 1(virbr0-nic) entered listening state Oct 22 22:06:54 hagrid gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid systemd[1]: Stopped NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Received signal 15 Oct 22 22:06:54 hagrid nvidia-persistenced: Socket closed. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file unlocked. Oct 22 22:06:54 hagrid systemd[1]: user-runtime-dir@121.service: Unit not needed anymore. Stopping. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file closed. Oct 22 22:06:54 hagrid systemd[1]: Stopping User Manager for UID 121... Oct 22 22:06:54 hagrid nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Oct 22 22:06:54 hagrid systemd[2507]: Stopping D-Bus User Message Bus... Oct 22 22:06:54 hagrid nvidia-persistenced: Shutdown (2865) Oct 22 22:06:54 hagrid systemd[2507]: Stopped target Default. Oct 22 22:06:54 hagrid systemd[2507]: Stopped D-Bus User Message Bus. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Description: Ubuntu 18.10 Release: 18.10 nvidia-driver-390: Installed: 390.87-0ubuntu1 Candidate: 390.87-0ubuntu1 Version table: *** 390.87-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu cosmic/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroR
[Kernel-packages] [Bug 1800752] 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 1800752 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/1800752 Title: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance Status in beignet package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Bug description: I run a BOINC project which uses opencl_intel on my Kubunut system On bioinc the tasks ran in 12,000 +/- 200 seconds. They've been doing that for ~6 months. I've now updated the system to cosmic, and the task are not taking 19,000 +/- 200s. I have another system (which is still running Mint18.3 - and hasn't changed) which also runs these tasks and the timings there have not changed, so the tasks themselves are still equivalent. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: beignet-opencl-icd 1.3.2-4 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 CurrentDesktop: KDE Date: Wed Oct 31 01:17:08 2018 InstallationDate: Installed on 2018-05-09 (174 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: beignet UpgradeStatus: Upgraded to cosmic on 2018-10-26 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802009] Re: package linux-azure-tools-4.18.0-1004 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package
** Tags removed: need-duplicate-check -- 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/1802009 Title: package linux-azure-tools-4.18.0-1004 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package linux- aws-tools-4.18.0-1004 4.18.0-1004.5 Status in linux-azure package in Ubuntu: New Bug description: E: /tmp/apt-dpkg-install-6DWtCe/41-linux-azure-tools-4.18.0-1004_4.18.0-1004.4_amd64.deb: trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package linux-aws-tools-4.18.0-1004 4.18.0-1004.5 E:Repository 'http://dl.google.com/linux/chrome/deb stable Release' changed its 'Origin' value from 'Google, Inc.' to 'Google LLC' ProblemType: Package DistroRelease: Ubuntu 18.10 Package: linux-azure-tools-4.18.0-1004 (not installed) 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.1 Architecture: amd64 Date: Tue Nov 6 14:13:56 2018 DuplicateSignature: package:linux-azure-tools-4.18.0-1004:(not installed) Unpacking linux-azure-tools-4.18.0-1004 (4.18.0-1004.4) ... dpkg: error processing archive /tmp/apt-dpkg-install-6DWtCe/41-linux-azure-tools-4.18.0-1004_4.18.0-1004.4_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package linux-aws-tools-4.18.0-1004 4.18.0-1004.5 ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package linux-aws-tools-4.18.0-1004 4.18.0-1004.5 InstallationDate: Installed on 2018-08-14 (84 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: linux-azure Title: package linux-azure-tools-4.18.0-1004 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package linux-aws-tools-4.18.0-1004 4.18.0-1004.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802009/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802009] [NEW] package linux-azure-tools-4.18.0-1004 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in packa
Public bug reported: E: /tmp/apt-dpkg-install-6DWtCe/41-linux-azure-tools-4.18.0-1004_4.18.0-1004.4_amd64.deb: trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package linux-aws-tools-4.18.0-1004 4.18.0-1004.5 E:Repository 'http://dl.google.com/linux/chrome/deb stable Release' changed its 'Origin' value from 'Google, Inc.' to 'Google LLC' ProblemType: Package DistroRelease: Ubuntu 18.10 Package: linux-azure-tools-4.18.0-1004 (not installed) 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.1 Architecture: amd64 Date: Tue Nov 6 14:13:56 2018 DuplicateSignature: package:linux-azure-tools-4.18.0-1004:(not installed) Unpacking linux-azure-tools-4.18.0-1004 (4.18.0-1004.4) ... dpkg: error processing archive /tmp/apt-dpkg-install-6DWtCe/41-linux-azure-tools-4.18.0-1004_4.18.0-1004.4_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package linux-aws-tools-4.18.0-1004 4.18.0-1004.5 ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package linux-aws-tools-4.18.0-1004 4.18.0-1004.5 InstallationDate: Installed on 2018-08-14 (84 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: linux-azure Title: package linux-azure-tools-4.18.0-1004 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package linux-aws-tools-4.18.0-1004 4.18.0-1004.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic package-conflict -- 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/1802009 Title: package linux-azure-tools-4.18.0-1004 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package linux- aws-tools-4.18.0-1004 4.18.0-1004.5 Status in linux-azure package in Ubuntu: New Bug description: E: /tmp/apt-dpkg-install-6DWtCe/41-linux-azure-tools-4.18.0-1004_4.18.0-1004.4_amd64.deb: trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package linux-aws-tools-4.18.0-1004 4.18.0-1004.5 E:Repository 'http://dl.google.com/linux/chrome/deb stable Release' changed its 'Origin' value from 'Google, Inc.' to 'Google LLC' ProblemType: Package DistroRelease: Ubuntu 18.10 Package: linux-azure-tools-4.18.0-1004 (not installed) 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.1 Architecture: amd64 Date: Tue Nov 6 14:13:56 2018 DuplicateSignature: package:linux-azure-tools-4.18.0-1004:(not installed) Unpacking linux-azure-tools-4.18.0-1004 (4.18.0-1004.4) ... dpkg: error processing archive /tmp/apt-dpkg-install-6DWtCe/41-linux-azure-tools-4.18.0-1004_4.18.0-1004.4_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package linux-aws-tools-4.18.0-1004 4.18.0-1004.5 ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package linux-aws-tools-4.18.0-1004 4.18.0-1004.5 InstallationDate: Installed on 2018-08-14 (84 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: linux-azure Title: package linux-azure-tools-4.18.0-1004 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.18.0-1004', which is also in package linux-aws-tools-4.18.0-1004 4.18.0-1004.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802009/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800752] Re: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance
Further information may be available in the files (readable only by root, the 0 may be different if you have more than one graphics device): /sys/kernel/debug/dri/0/i915_capabilities /sys/kernel/debug/dri/0/i915_sseu_status ** Summary changed: - Performance degraded in Cosmic + [regression] Wrong EU count for i5-5250U, reducing OpenCL performance ** 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/1800752 Title: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance Status in beignet package in Ubuntu: In Progress Status in linux package in Ubuntu: New Bug description: I run a BOINC project which uses opencl_intel on my Kubunut system On bioinc the tasks ran in 12,000 +/- 200 seconds. They've been doing that for ~6 months. I've now updated the system to cosmic, and the task are not taking 19,000 +/- 200s. I have another system (which is still running Mint18.3 - and hasn't changed) which also runs these tasks and the timings there have not changed, so the tasks themselves are still equivalent. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: beignet-opencl-icd 1.3.2-4 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 CurrentDesktop: KDE Date: Wed Oct 31 01:17:08 2018 InstallationDate: Installed on 2018-05-09 (174 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: beignet UpgradeStatus: Upgraded to cosmic on 2018-10-26 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800803] Re: linux-azure: 4.15.0-1031.32 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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: 1799411 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED regression-testing: Testing in progress 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/1800803 Title: linux-azure: 4.15.0-1031.32 -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: Fix Released 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: 1799411 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress 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/1800803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801124] Re: linux-aws: 4.4.0-1072.82 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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: 1799401 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED regression-testing: Testing in progress 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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1801124 Title: linux-aws: 4.4.0-1072.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released 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-aws package in Ubuntu: Invalid Status in linux-aws 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: 1799401 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress 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/1801124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789227] Re: nvme devices namespace assigned to the wrong controller
Hello Kleber, or anyone else affected, Accepted debian-installer into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu543.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: debian-installer (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed verification-needed-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/1789227 Title: nvme devices namespace assigned to the wrong controller Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: == Impact == During device discovery, when multipath is disabled, nvme multipath module will very likely think that the name space on one nvme controller belongs to the other controller. == Fix == Commit a785dbccd95c37606c720580714f5a7a8b3255f1 upstream From: Keith Busch When CONFIG_NVME_MULTIPATH is set, but we're not using nvme to multipath, namespaces with multiple paths were not creating unique names due to reusing the same instance number from the namespace's head. This patch fixes this by falling back to the non-multipath naming method when the parameter disabled using multipath. Reported-by: Mike Snitzer Signed-off-by: Keith Busch Reviewed-by: Christoph Hellwig Signed-off-by: Jens Axboe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1789227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
** Changed in: linux (Ubuntu Xenial) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in unattended-upgrades source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in unattended-upgrades source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in unattended-upgrades source package in Cosmic: Fix Released Status in linux source package in Disco: Invalid Status in unattended-upgrades source package in Disco: Fix Released Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
UPDATE: I found the packages in bionic-updates. After setting prime-select nvidia and logging out, I got the attached /var/log/gpu-manager.log. It says that nvidia is not loaded, and my laptop still runs hot. When I set prime-select intel, log out, and back in, nvidia is still not loaded (according to the log) and my laptop still runs hot. Any suggestings? ** Attachment added: "/var/log/gpu-manager.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5209748/+files/gpu-manager.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801986] Re: Cosmic update: 4.18.14 upstream stable release
Skipped "KVM: x86: fix L1TF's MMIO GFN calculation" as it is already applied for bug #1798427. Skipped "xen-netback: fix input validation in xenvif_set_hash_mapping()" because is was already applied for XSA-270 / CVE-2018-15471. Reverted and replaced UBUNTU SAUCE patch with upstream version (PCI: Reprogram bridge prefetch registers on resume). ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15471 ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + 4.18.14 upstream stable release + from git://git.kernel.org/ -4.18.14 upstream stable release -from git://git.kernel.org/ + The following patches will be applied: + * perf/core: Add sanity check to deal with pinned event failure + * mm: migration: fix migration of huge PMD shared pages + * mm, thp: fix mlocking THP page with migration enabled + * mm/vmstat.c: skip NR_TLB_REMOTE_FLUSH* properly + * KVM: VMX: check for existence of secondary exec controls before accessing + * blk-mq: I/O and timer unplugs are inverted in blktrace + * pstore/ram: Fix failure-path memory leak in ramoops_init + * clocksource/drivers/timer-atmel-pit: Properly handle error cases + * fbdev/omapfb: fix omapfb_memory_read infoleak + * mmc: core: Fix debounce time to use microseconds + * mmc: slot-gpio: Fix debounce time to use miliseconds again + * mac80211: allocate TXQs for active monitor interfaces + * drm/amdgpu: Fix vce work queue was not cancelled when suspend + * drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set + * drm: fix use-after-free read in drm_mode_create_lease_ioctl() + * x86/vdso: Fix asm constraints on vDSO syscall fallbacks + * selftests/x86: Add clock_gettime() tests to test_vdso + * x86/vdso: Only enable vDSO retpolines when enabled and supported + * x86/vdso: Fix vDSO syscall fallback asm constraint regression + * Revert "UBUNTU: SAUCE: PCI: Reprogram bridge prefetch registers on resume" + * PCI: Reprogram bridge prefetch registers on resume + * mac80211: fix setting IEEE80211_KEY_FLAG_RX_MGMT for AP mode keys + * PM / core: Clear the direct_complete flag on errors + * dm mpath: fix attached_handler_name leak and dangling hw_handler_name pointer + * dm cache metadata: ignore hints array being too small during resize + * dm cache: fix resize crash if user doesn't reload cache table + * xhci: Add missing CAS workaround for Intel Sunrise Point xHCI + * usb: xhci-mtk: resume USB3 roothub first + * USB: serial: simple: add Motorola Tetra MTP6550 id + * USB: serial: option: improve Quectel EP06 detection + * USB: serial: option: add two-endpoints device-id flag + * usb: cdc_acm: Do not leak URB buffers + * tty: Drop tty->count on tty_reopen() failure + * of: unittest: Disable interrupt node tests for old world MAC systems + * powerpc: Avoid code patching freed init sections + * powerpc/lib: fix book3s/32 boot failure due to code patching + * ARC: clone syscall to setp r25 as thread pointer + * f2fs: fix invalid memory access + * tipc: call start and done ops directly in __tipc_nl_compat_dumpit() + * ucma: fix a use-after-free in ucma_resolve_ip() + * ubifs: Check for name being NULL while mounting + * rds: rds_ib_recv_alloc_cache() should call alloc_percpu_gfp() instead + * ath10k: fix scan crash due to incorrect length calculation + * Linux 4.18.14 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801986 Title: Cosmic update: 4.18.14 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in t
[Kernel-packages] [Bug 1800877] Re: iproute2/xenial: Add support for the VF Trust setting (fix IPv6 multicast under SR-IOV on Mellanox adapters)
Hello Mauricio, or anyone else affected,
Accepted iproute2 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/4.3.0-1ubuntu3.16.04.4 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: iproute2 (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1800877
Title:
iproute2/xenial: Add support for the VF Trust setting (fix IPv6
multicast under SR-IOV on Mellanox adapters)
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Fix Committed
Bug description:
[Impact]
* An VM's VF cannot receive IPv6 multicast traffic
from other VMs' VFs in the same Mellanox adapter
_if_ its VF trust setting is not enabled, and on
Xenial currently iproute2 _cannot_ enable it.
* This breaks IPv6 NDP (Neighbor Discovery Protocol)
in that scenario.
* This upload adds three iproute2 upstream commits
to enable/disable the VF setting, which resolves
that problem/limitation.
[Test Case]
* Check 'ip link help' for the 'trust' option:
Before:
# ip link help 2>&1 | grep trust
After:
# ip link help 2>&1 | grep trust
[ trust { on | off} ] ]
* Check 'ip link show dev PF' for 'trust on|off' field in VFs.
Before: (trust field _is not_ present)
# ip link show dev ens1f0
...
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
After: (trust field _is_ present)
# ip link show dev ens1f0
...
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
* Set the VF trust on/off and check it:
Set VF 0 trust on:
# ip link set ens1f0 vf 0 trust on
# ip link show dev ens1f0 | grep trust
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust on
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
Set VF 0 trust off:
# ip link set ens1f0 vf 0 trust off
# ip link show dev ens1f0 | grep trust
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
[Regression Potential]
* Regression potential is low because the commits just add the
netlink attribute for the userspace-kernel interface and the
ways to set/clear it, and show the current value to the user.
* Regressions could happen _if_ the user turns the setting on
(it's disabled by default) and there's a problem/bug likely
in _other_ component that depends on that setting (which is
something to fix on such component).
[Other Info]
* The users that reported this problem have verified
the test package with these changes, and confirmed
that it now works correctly for IPv6 NDP/multicast.
* Upstream commits:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=dddf1b44126e
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=fe9322781e63
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=b6d77d9ee312
* Only affect Xenial release :
# rmadison iproute2
iproute2 | 4.3.0-1ubuntu3.16.04.3 | xenial-updates
iproute2 | 4.15.0-2ubuntu1| bionic
iproute2 | 4.18.0-1ubuntu2| cosmic
iproute2 | 4.18.0-1ubuntu2| disco
# iproute2 upstream vcs
$ git describe --contains dddf1b44126e
v4.4.0~67
$ git describe --contains b6d77d9ee312
v4.5.0~47
$ git describe --c
[Kernel-packages] [Bug 1801931] Re: Cosmic update: 4.18.13 upstream stable release
Regression for Bug #1796720. * "Driver: Video(DRI - non Intel): fix Power consumption RX560 idle raised from 7 W to 13 W" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801931 Title: Cosmic update: 4.18.13 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.18.13 upstream stable release from git://git.kernel.org/ The following patches will be applied: * rseq/selftests: fix parametrized test with -fpie * mac80211: Run TXQ teardown code before de-registering interfaces * mac80211_hwsim: require at least one channel * Btrfs: fix unexpected failure of nocow buffered writes after snapshotting when low on space * KVM: PPC: Book3S HV: Don't truncate HPTE index in xlate function * cfg80211: remove division by size of sizeof(struct ieee80211_wmm_rule) * btrfs: btrfs_shrink_device should call commit transaction at the end * scsi: csiostor: add a check for NULL pointer after kmalloc() * scsi: csiostor: fix incorrect port capabilities * scsi: libata: Add missing newline at end of file * scsi: aacraid: fix a signedness bug * bpf, sockmap: fix potential use after free in bpf_tcp_close * bpf, sockmap: fix psock refcount leak in bpf_tcp_recvmsg * bpf: sockmap, decrement copied count correctly in redirect error case * mac80211: correct use of IEEE80211_VHT_CAP_RXSTBC_X * mac80211_hwsim: correct use of IEEE80211_VHT_CAP_RXSTBC_X * cfg80211: make wmm_rule part of the reg_rule structure * mac80211_hwsim: Fix possible Spectre-v1 for hwsim_world_regdom_custom * nl80211: Fix nla_put_u8 to u16 for NL80211_WMMR_TXOP * nl80211: Pass center frequency in kHz instead of MHz * bpf: fix several offset tests in bpf_msg_pull_data * gpio: adp5588: Fix sleep-in-atomic-context bug * mac80211: mesh: fix HWMP sequence numbering to follow standard * mac80211: avoid kernel panic when building AMSDU from non-linear SKB * gpiolib: acpi: Switch to cansleep version of GPIO library call * gpiolib-acpi: Register GpioInt ACPI event handlers from a late_initcall * gpio: dwapb: Fix error handling in dwapb_gpio_probe() * bpf: fix msg->data/data_end after sg shift repair in bpf_msg_pull_data * bpf: fix shift upon scatterlist ring wrap-around in bpf_msg_pull_data * bpf: fix sg shift repair start offset in bpf_msg_pull_data * tipc: switch to rhashtable iterator * sh_eth: Add R7S9210 support * net: mvpp2: initialize port of_node pointer * tc-testing: add test-cases for numeric and invalid control action * cfg80211: nl80211_update_ft_ies() to validate NL80211_ATTR_IE * mac80211: do not convert to A-MSDU if frag/subframe limited * mac80211: always account for A-MSDU header changes * tools/kvm_stat: fix python3 issues * tools/kvm_stat: fix handling of invalid paths in debugfs provider * tools/kvm_stat: fix updates for dead guests * gpio: Fix crash due to registration race * ARC: atomics: unbork atomic_fetch_##op() * Revert "blk-throttle: fix race between blkcg_bio_issue_check() and cgroup_rmdir()" * md/raid5-cache: disable reshape completely * RAID10 BUG_ON in raise_barrier when force is true and conf->barrier is 0 * selftests: pmtu: maximum MTU for vti4 is 2^16-1-20 * selftests: pmtu: detect correct binary to ping ipv6 addresses * ibmvnic: Include missing return code checks in reset function * bpf: Fix bpf_msg_pull_data() * bpf: avoid misuse of psock when TCP_ULP_BPF collides with another ULP * i2c: uniphier: issue STOP only for last message or I2C_M_STOP * i2c: uniphier-f: issue STOP only for last message or I2C_M_STOP * net: cadence: Fix a sleep-in-atomic-context bug in macb_halt_tx() * fs/cifs: don't translate SFM_SLASH (U+F026) to backslash * mac80211: fix an off-by-one issue in A-MSDU max_subframe computation * cfg80211: fix a type issue in ieee80211_chandef_to_operating_class() * mac80211: fix WMM TXOP calculation * mac80211: fix a race between restart and CSA flows * mac80211: Fix station bandwidth setting after channel switch * mac80211: don't Tx a deauth frame if the AP forbade Tx * mac80211: shorten the IBSS debug messages * fsnotify: fix ignore mask logic in fsnotify() * net/ibm/emac: wrong emac_calc_base call was used by typo * nds32: fix logic for module * nds32: add NULL entry to the end of_device_id array * nds32: Fix empty call
[Kernel-packages] [Bug 1801986] [NEW] Cosmic update: 4.18.14 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.18.14 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Cosmic) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801986 Title: Cosmic update: 4.18.14 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.18.14 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1624540] Re: please have lxd recommend zfs
Marking the LXD side of this fixed as we're now shipping as a snap by default and the snap contains zfs. ** Changed in: lxd (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1624540 Title: please have lxd recommend zfs Status in lxd package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: In Progress Bug description: Since ZFS is now in Main (Bug #1532198), LXD should recommend the ZFS userspace package, such that 'sudo lxd init' just works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1624540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460
Hi Cristian, thank you for the heads up... Regards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796720 Title: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hello, Today I have received an update for Linux kernel which upgraded the kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately after restart I noticed that the GPU temperature is abnormally High... Before Update: - GPU fan set to off on idle - GPU idle temperature: 29-32 C After Update: - GPU fan set to off on idle - GPU idle temperature: 47-50 C (which I have to put the fans on 50% to keep it on 33 C) I have also tried to boot from the older kernel (4.18.0.8) and everything is normal there! System spec: - MB: ASUS Prime x299-deluxe - CPU: Intel Corei7 7820x skylake-x - GPU: AMD RX460 glxinfo | grep OpenGL: OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.26.0, 4.18.0-9-generic, LLVM 7.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.1 OpenGL shading language version string: 4.40 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: sudo cat /sys/kernel/debug/dri/0/amdgpu_pm_info: Clock Gating Flags Mask: 0x37bcf Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: On Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: On Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: On Graphics Run List Controller Light Sleep: On Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: Off System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: Off Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: On Video Compression Engine Medium Grain Clock Gating: On Host Data Path Light Sleep: Off Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: On Data Fabric Medium Grain Clock Gating: Off GFX Clocks and Power: 1750 MHz (MCLK) 1212 MHz (SCLK) 214 MHz (PSTATE_SCLK) 300 MHz (PSTATE_MCLK) 1081 mV (VDDGFX) 18.65 W (average GPU) GPU Temperature: 39 C GPU Load: 0 % UVD: Disabled VCE: Disabled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadowfax 3078 F pulseaudio /dev/snd/controlC0: shadowfax 3078 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 20:27:13 2018 InstallationDate: Installed on 2018-09-26 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180925.1) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=a58662c7-39e2-4f05-9da6-d63173c94d53 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd08/03/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstr
[Kernel-packages] [Bug 1799718] Re: Ubuntu 18.10 fr FAN always ON 5 400 rpm
For info, I charged Linuxmint 17 and all things ok (except drivers of wifi and sound) But videos, others functions ok I join you attachement of screen capture then crash ** Attachment added: "screen ca" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799718/+attachment/5209739/+files/IMG_20181106_114422_DRO.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799718 Title: Ubuntu 18.10 fr FAN always ON 5 400 rpm Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.10 fr since 20181022. By update from 18.04 My PC ASUS ROG GL 753V Notebook PC Fan always on At 5 400 rpm. Air cold ! GPU temp 31 °C PC 33 °C Ubuntu version : 4.18.0.11-generic On startup, says "Failed start load kernel Modules" On picture on attachment : Value of fan is incorrect I don't know where is fan sensor to put on my conky --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rg 4260 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862 InstallationDate: Installed on 2018-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 004: ID 13d3:5666 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL753VD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VD 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/1799718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801878] Re: NULL pointer dereference at 0000000000000020 when access dst_orig->ops->family in function xfrm_lookup_with_ifid()
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
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/1801878
Title:
NULL pointer dereference at 0020 when access
dst_orig->ops->family in function xfrm_lookup_with_ifid()
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
New
Status in linux source package in Cosmic:
New
Bug description:
[Impact]
NULL pointer access happens when trying to access dst_orig->ops.
The function xfrm_lookup() calls xfrm_lookup_with_ifid() and there is
a line inside trying to access dst_orig->ops and it's exactly where the
panicing happens:
u16 family = dst_orig->ops->family;
As you can see that the symbol offset of ops is about 32(0x20) which
definitely is the error message shows in the kern.log:
[267265.140511] BUG: unable to handle kernel NULL pointer dereference
at 0020
struct dst_entry {
struct callback_head callback_head; /* 0 16 */
struct dst_entry * child; /* 16 8 */
struct net_device * dev; /* 24 8 */
struct dst_ops * ops; <-- /* 32 8 */
The oops:
BUG: unable to handle kernel NULL pointer dereference at 0020
IP: xfrm_lookup+0x31/0x870
PGD 0 P4D 0
Oops: [#1] SMP PTI
CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.15.0-36-generic
#39~16.04.1-Ubuntu
Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
RIP: 0010:xfrm_lookup+0x31/0x870
RSP: 0018:98b542343a48 EFLAGS: 00010246
RAX: RBX: 98b542343ac8 RCX:
RDX: 98b542343ac8 RSI: RDI: b39e4380
RBP: 98b542343ab8 R08: 0002 R09:
R10: 0020 R11: 7fb56465 R12:
R13: b39e4380 R14: 0002 R15: b39e4380
FS: () GS:98b54234() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 0020 CR3: 0004ed40a001 CR4: 001606e0
DR0: DR1: DR2:
DR3: DR6: fffe0ff0 DR7: 0400
Call Trace:
? __xfrm_policy_check+0x41d/0x630
__xfrm_route_forward+0xa3/0x110
ip_forward+0x38c/0x470
? ip_route_input_noref+0x28/0x40
ip_rcv_finish+0x124/0x410
ip_rcv+0x28e/0x3b0
? inet_del_offload+0x40/0x40
__netif_receive_skb_core+0x879/0xba0
? __skb_checksum+0x188/0x2c0
__netif_receive_skb+0x18/0x60
? __netif_receive_skb+0x18/0x60
netif_receive_skb_internal+0x37/0xe0
? tcp4_gro_complete+0x86/0x90
napi_gro_complete+0x73/0x90
dev_gro_receive+0x2ee/0x5c0
napi_gro_frags+0xa3/0x230
ena_clean_rx_irq+0x486/0x7c0 [ena]
ena_io_poll+0x41d/0x770 [ena]
net_rx_action+0x265/0x3b0
__do_softirq+0xf5/0x28f
irq_exit+0xb8/0xc0
xen_evtchn_do_upcall+0x30/0x40
xen_hvm_callback_vector+0x84/0x90
[Fix]
The patch tries to avoid the NULL pointer access before the line
mentioned "dst_orig->ops->family" in function __xfrm_route_forward.
And the function calling sequence is:
__xfrm_route_forward -> xfrm_lookup -> xfrm_lookup_with_ifid
It definitely avoids the NULL pointer access in the
xfrm_lookup_with_ifid.
commit c5e39ef174ad34cd4d26af3a83bdbccddd2ad9d6
Author: Steffen Klassert
Date: Tue Sep 11 10:31:15 2018 +0200
xfrm: Fix NULL pointer dereference when skb_dst_force clears the
dst_entry.
Since commit 222d7dbd258d ("net: prevent dst uses after free")
skb_dst_force() might clear the dst_entry attached to the skb.
The xfrm code don't expect this to happen, so we crash with
a NULL pointer dereference in this case. Fix it by checking
skb_dst(skb) for NULL after skb_dst_force() and drop the packet
in cast the dst_entry was cleared.
[Test]
The fix has been tested in the production system with the IPSec enabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801878/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801975] Re: update to build for 4.19
Tested to build against 4.18 and 4.19. ** Patch added: "dm-writeboost_2.2.9-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1801975/+attachment/5209738/+files/dm-writeboost_2.2.9-1ubuntu1.debdiff ** Changed in: linux (Ubuntu Disco) Status: Incomplete => Invalid ** Changed in: dm-writeboost (Ubuntu Disco) Status: New => In Progress ** Changed in: dm-writeboost (Ubuntu Disco) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801975 Title: update to build for 4.19 Status in dm-writeboost package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Status in dm-writeboost source package in Disco: In Progress Status in linux source package in Disco: Invalid Bug description: dm-writeboost-dkms fails to build on linux 4.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1801975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769937] Re: Error reported when creating ZFS pool with "-t" option, despite successful pool creation
This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu26
---
zfs-linux (0.6.5.6-0ubuntu26) xenial; urgency=medium
* Fix error exit when using -t option (LP: #1769937)
- Upstream ZFS fix 4ceb8dd6fdfd ("Fix 'zpool create -t '")
fixes error message and error exit when using the -t option
when creating a pool.
-- Colin Ian King Wed, 10 Oct 2018 12:16:47
+0100
** Changed in: zfs-linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1769937
Title:
Error reported when creating ZFS pool with "-t" option, despite
successful pool creation
Status in linux package in Ubuntu:
Fix Released
Status in zfs-linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in zfs-linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in zfs-linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in zfs-linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification, Xenial, Bionic ==
Bug:
When creating a pool with the -t option on Ubuntu 18.04 LTS, it will
report an error and return a non-zero exit code, but the pool appears
to be successfully created.
For example:
# zpool create -O canmount=off -O mountpoint=none -R /mnt/rpool-25582 -t
rpool-25582 rpool /dev/mapper/loop2p1
cannot create 'rpool': no such pool or dataset
# zpool list
NAME SIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH
ALTROOT
rpool-25582 69.5G 92.5K 69.5G - 0% 0% 1.00x ONLINE
/mnt/rpool-25582
# zpool export rpool-25582
# zpool import rpool
# zpool list
NAMESIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT
rpool 69.5G 134K 69.5G - 0% 0% 1.00x ONLINE -
I opened an upstream bug against ZFS on Linux, here:
https://github.com/zfsonlinux/zfs/issues/7502
And it has been recently fixed, here:
https://github.com/zfsonlinux/zfs/pull/7509
Can this upstream fix be pulled into the Ubuntu 18.04 LTS packages?
Thanks,
Prakash
== Fix ==
Upstream zfs commit 4ceb8dd6fdfd ("Fix 'zpool create -t '")
== Test ==
Without the fix, creating a pool with -t will show an error message
such as:
"cannot create 'rpool': no such pool or dataset" and will return an
error number even though it successfully created the pool. With the
fix, the error is not shown and it exits with 0.
E.g.
pool create -O canmount=off -O mountpoint=none -R /mnt/rpool-25582 -t
rpool-25582 rpool /dev/mapper/loop2p1
cannot create 'rpool': no such pool or dataset
== Regression Potential ==
Small. This is an upstream fix that is know to fix the error. There
are no known subsequent changes to the fix hence suggesting it is a
good fix. The change is very limited and testing shows it does not
break any of the kernel team's ZFS regression testing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769937/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801975] 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 1801975 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/1801975 Title: update to build for 4.19 Status in dm-writeboost package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in dm-writeboost source package in Disco: New Status in linux source package in Disco: Incomplete Bug description: dm-writeboost-dkms fails to build on linux 4.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1801975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black
Ubuntu 18.10 does have the same problem, Ubuntu 16.04.2 has *NO* problem. From where could I get an 4.4 kernel for 18.04 for testing purpose ? Other infos: when I check in systems, it show me 3 display despite the fact that only 2 are connected: 1. internal display 2. unknown display with resolution 1024 x 768 (4:3) 800 x 600 (4:3) 848 x 480 (16:9) ! 3. external display with correct informations (Brand, model, ) I also discover that starting the laptop with the display connected, shows me the splash image on both displays as it should. Problem arise on greeting image. From here I see "No input signal" and the external display goes black. Daniel PS: perhaps bug 1723025? could be identical but from my side, I can start with or without external display, it's only when I use the fn switch key that problem arise. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801747 Title: External display not recognized, internal one goes to black Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi, I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu 18.04.1 I face a problem on ALL of them, as soon as I connect an external screen, doesn't matter VGA or HDMI, the internal screen goes black, only mouse icon is their, blinking from time to time but reacting. External screen does show nothing but there is no "no signal" info what means that source is recognized. As soon as I release the video cable from external display, the internal one come back to live after few seconds. The BIOS was updated to latest available. Daniel tootai@hirondelle:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Mon Nov 5 16:30:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2018-10-19 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU0012B8R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801975] [NEW] update to build for 4.19
Public bug reported: dm-writeboost-dkms fails to build on linux 4.19. ** Affects: dm-writeboost (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: dm-writeboost (Ubuntu Disco) Importance: Undecided Status: New ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: Incomplete ** Also affects: dm-writeboost (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: dm-writeboost (Ubuntu Disco) 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/1801975 Title: update to build for 4.19 Status in dm-writeboost package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in dm-writeboost source package in Disco: New Status in linux source package in Disco: Incomplete Bug description: dm-writeboost-dkms fails to build on linux 4.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1801975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799994] Re: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1
I'm already not running Wayland. When I was running Wayland, it started up on the internal display using the Intel driver. When docked, I don't use the internal display, so I disabled Wayland. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => Confirmed -- 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/174 Title: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Lenovo ThinkPad W540 docked with an ultradock. 3 external displays running on VGA, DVI and display port all connected to the dock. BIOS mode set to run external displays ONLY with nvidia chipset. prime- select nvidia run. When running under 4.15.0-36-generic with nvidia 390.77-0ubuntu0.18.04.1 I boot and all three external displays run fine. Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timr 3768 F pulseaudio /dev/snd/controlC1: timr 3768 F pulseaudio /dev/snd/controlC0: timr 3768 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-image-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" 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: Upgraded to bionic on 2018-08-17 (69 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dm
[Kernel-packages] [Bug 1801574] Re: [cosmic] ipoib ping with large message size failed
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Tyler Hicks (tyhicks) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801574 Title: [cosmic] ipoib ping with large message size failed Status in linux package in Ubuntu: Incomplete Bug description: We see that ping over ipoib interface stuck with large packets, this is a new degradation, this test pass on Ubuntu 18.04. After investigating the issue, we see that commit [1] introduce the issue, and it is not an upstream commit, it is canonical commit. Could you please check with the canonical kernel team why they revert that commit? To reproduce the bug, please use ConnectX-3 devices with ipoib connection with 2044 MTU (default) and run command [2]. Is there open Launchpad on it? [1] commit 77a24c313d21e3765b04d90521e9228a9bb6e332 Author: Tyler Hicks Date: Fri Aug 3 21:53:15 2018 + Revert "net: increase fragment memory usage limits" This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It made denial of service attacks on the IP fragment handling easier to carry out. CVE-2018-5391 Signed-off-by: Tyler Hicks Signed-off-by: Stefan Bader [2] ping 13.194.22.1 -I 13.194.23.1 -s 65507 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460
Daniel, See Bug #1801931 :) -- Cristian -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796720 Title: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hello, Today I have received an update for Linux kernel which upgraded the kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately after restart I noticed that the GPU temperature is abnormally High... Before Update: - GPU fan set to off on idle - GPU idle temperature: 29-32 C After Update: - GPU fan set to off on idle - GPU idle temperature: 47-50 C (which I have to put the fans on 50% to keep it on 33 C) I have also tried to boot from the older kernel (4.18.0.8) and everything is normal there! System spec: - MB: ASUS Prime x299-deluxe - CPU: Intel Corei7 7820x skylake-x - GPU: AMD RX460 glxinfo | grep OpenGL: OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.26.0, 4.18.0-9-generic, LLVM 7.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.1 OpenGL shading language version string: 4.40 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: sudo cat /sys/kernel/debug/dri/0/amdgpu_pm_info: Clock Gating Flags Mask: 0x37bcf Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: On Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: On Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: On Graphics Run List Controller Light Sleep: On Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: Off System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: Off Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: On Video Compression Engine Medium Grain Clock Gating: On Host Data Path Light Sleep: Off Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: On Data Fabric Medium Grain Clock Gating: Off GFX Clocks and Power: 1750 MHz (MCLK) 1212 MHz (SCLK) 214 MHz (PSTATE_SCLK) 300 MHz (PSTATE_MCLK) 1081 mV (VDDGFX) 18.65 W (average GPU) GPU Temperature: 39 C GPU Load: 0 % UVD: Disabled VCE: Disabled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadowfax 3078 F pulseaudio /dev/snd/controlC0: shadowfax 3078 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 20:27:13 2018 InstallationDate: Installed on 2018-09-26 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180925.1) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=a58662c7-39e2-4f05-9da6-d63173c94d53 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd08/03/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.p
[Kernel-packages] [Bug 1801686] Re: [Ubuntu] qdio: reset old sbal_state flags
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Status: New => Triaged
--
You 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:
Triaged
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
New
Status in linux source package in Cosmic:
New
Status in linux source package in Disco:
New
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 1798921] Re: sky2 ethernet card don't work after returning from suspension
my dmesg saved on pastebinit https://paste.ubuntu.com/p/nbFhQwWVVP/ however, the error ends on the line [ 380.567633] do_IRQ: 3.34 No irq handler for vector further entries after the option: rmmod sky2 modprobe sky2 to get internet access and pastebinit services :-) regards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Incomplete Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: 00:23:ae:ea:23:3e size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801875] Re: Power consumption during s2idle is higher than long idle(sk hynix)
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) 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/1801875 Title: Power consumption during s2idle is higher than long idle(sk hynix) Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: [Impact] On some Dell XPS models, we observed the power consumption raises higher than long idle does during s2idle with sk hynix nvme. C2: Short idle: 4 Long idle: 1 S2I: 3.7 S5: 0.19 C3: Short idle: 7.2 Long idle: 4.5 S2I: 6.22 S5: 0.18 C5: Short idle: 6.5 Long idle: 1 S2I: 2.88 S5: 0.18 [Fix] From SK hynix FE, MS Windows doesn't put nvme to D3, and uses its own APST feature to do the power management. To leverage its APST feature during s2idle, we can't disable nvme device while suspending, too. So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. prevent nvme from being disabled when suspending. [Test] Verified on different XPS machines with different sk hynix nvme disks, it fixes the power consumption issue with no regression. And the power consumption drops to 0.77W during s2idle. [Regression Potential] Low, the patches only applied to specific nvme module, and from our test, the system is still stable. [Misc] This issue should be fixed by the firmware, and we're pushing sk hynix to fix it. But before sk hynix find out how to solve it, we have to preserve these commits in our kernel for a while. BTW, the patches use pm_suspend_via_s2idle() function from below commit which is still under reviewing. https://lists.ubuntu.com/archives/kernel-team/2018-October/096141.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Comment bridged from LTC Bugzilla
--- Comment From peter.mor...@de.ibm.com 2018-11-06 11:01 EDT---
Thanks for providing the kernel image so quickly.
I successfully tested the AP passthrough function using the following
components:
Distribution:
Ubuntu 18.04 LTS
Host kernel:
Linux KVMCrypto 4.15.0-38-generic #42~lp1787405 SMP Mon Nov 5 21:13:01 UTC 2018
s390x s390x s390x GNU/Linux
KVM guest kernel:
Linux f6c59abfb01a 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:57:21 UTC
2018 s390x Linux
Qemu:
QEMU emulator version 3.0.50 (v3.0.0-1732-gef30274865-dirty)
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/1787405
Title:
[19.04 FEAT] Guest-dedicated Crypto Adapters
Status in Ubuntu on IBM z Systems:
Triaged
Status in libvirt package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Triaged
Status in qemu package in Ubuntu:
Incomplete
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/ap
[Kernel-packages] [Bug 1799305] Re: No desktop after reboot when using nvidia graphics on 18.10
Possibly duplicate of https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790 -- 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/1799305 Title: No desktop after reboot when using nvidia graphics on 18.10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I upgraded from 18.04 to 18.10 and now the desktop does not start after a reboot. The console output ends with "Starting GNOME Display Manager". I cannot switch VTs, my keyboard and mouse are unresponsive though RESUIB sequence works to reboot. If I remote login using ssh, I can run "systemctrl restart gdm3" and I get a working login screen and can continue as expected. If I remove my nvidia drivers the desktop starts as expected after reboot. Examining /var/log/syslog appears to show the nvidia driver failing to load correctly; see below. In the failed state "systemctl status gdm3" shows: ● gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled) Active: active (running) since Mon 2018-10-22 22:06:38 BST; 16min ago Process: 1877 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, status=0/SUCCESS) Process: 1723 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1880 (gdm3) Tasks: 3 (limit: 4915) Memory: 5.7M CGroup: /system.slice/gdm.service └─1880 /usr/sbin/gdm3 Oct 22 22:06:35 hagrid systemd[1]: Starting GNOME Display Manager... Oct 22 22:06:38 hagrid systemd[1]: Started GNOME Display Manager. Oct 22 22:06:44 hagrid gdm-launch-environment][2108]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. root@hagrid:/var/log# grep 2634 syslog Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. . . . This is a section from syslog: Oct 22 22:06:53 hagrid systemd[1]: Starting NVIDIA Persistence Daemon... Oct 22 22:06:53 hagrid nvidia-persistenced: Verbose syslog connection opened Oct 22 22:06:53 hagrid systemd[1]: Started NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Now running with user ID 123 and group ID 129 Oct 22 22:06:54 hagrid [2750]: meta_kms_resources_init failed: Calling drmModeGetResources() failed, assuming we have no outputs Oct 22 22:06:54 hagrid gnome-session[2664]: gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid nvidia-persistenced: Started (2865) Oct 22 22:06:54 hagrid [2750]: Failed to create backend: No GPUs with outputs found Oct 22 22:06:54 hagrid nvidia-persistenced: device :01:00.0 - registered Oct 22 22:06:54 hagrid gnome-session-binary[2664]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 22 22:06:54 hagrid nvidia-persistenced: Local RPC service initialized Oct 22 22:06:54 hagrid systemd[1]: Stopping NVIDIA Persistence Daemon... Oct 22 22:06:54 hagrid kernel: [ 86.847749] virbr0: port 1(virbr0-nic) entered blocking state Oct 22 22:06:54 hagrid kernel: [ 86.847753] virbr0: port 1(virbr0-nic) entered listening state Oct 22 22:06:54 hagrid gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid systemd[1]: Stopped NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Received signal 15 Oct 22 22:06:54 hagrid nvidia-persistenced: Socket closed. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file unlocked. Oct 22 22:06:54 hagrid systemd[1]: user-runtime-dir@121.service: Unit not needed anymore. Stopping. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file closed. Oct 22 22:06:54 hagrid systemd[1]: Stopping User Manager for UID 121... Oct 22 22:06:54 hagrid nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Oct 22 22:06:54 hagrid systemd[2507]: Stopping D-Bus User Message Bus... Oct 22 22:06:54 hagrid nvidia-persistenced: Shutdown (2865) Oct 22 22:06:54 hagrid systemd[2507]: Stopped target Default. Oct 22 22:06:54 hagrid systemd[2507]: Stopped D-Bus User Message Bus. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Description: Ubuntu 18.10 Release: 18.10 nvidia-driver-390: Installed: 390.87-0ubuntu1 Candidate: 390.87-0ubuntu1 Version table: *** 390.87-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu cosmic/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidi
[Kernel-packages] [Bug 1801686] Re: [Ubuntu] qdio: reset old sbal_state flags
SRU submitted:
[SRU][Cosmic][Bionic][Xenial][PATCH 0/1] Fixes for LP1801686 [v2]
https://lists.ubuntu.com/archives/kernel-team/2018-November/096507.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801686
Title:
[Ubuntu] qdio: reset old sbal_state flags
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
New
Status in linux source package in Cosmic:
New
Status in linux source package in Disco:
New
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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Alberto This is my first time on launchpad, so please forgive any noob errors. I followed the instructions to the letter: I enabled bionic-proposed with: sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -sc)-proposed restricted main universe" I created /etc/apt/preferences.d/proposed-updates with the specified content I updated. Then when I tried to install the packages I saw: Reading package lists... Done Building dependency tree Reading state information... Done E: Release 'bionic-proposed' for 'nvidia-driver-390' was not found E: Release 'bionic-proposed' for 'gdm3' was not found E: Release 'bionic-proposed' for 'nvidia-settings' was not found E: Release 'bionic-proposed' for 'libnvidia-gl-390' was not found E: Release 'bionic-proposed' for 'libnvidia-compute-390' was not found E: Release 'bionic-proposed' for 'libnvidia-decode-390' was not found E: Release 'bionic-proposed' for 'libnvidia-encode-390' was not found E: Release 'bionic-proposed' for 'libnvidia-ifr1-390' was not found E: Release 'bionic-proposed' for 'libnvidia-fbc1-390' was not found Am I missing something? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions
[Kernel-packages] [Bug 1799184] Re: [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding
SRU request:
Subject: [SRU][Bionic][PATCH 0/3] Fixes for LP1799184
https://lists.ubuntu.com/archives/kernel-team/2018-November/096438.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799184
Title:
[18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic
driver binding
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
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
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is ex
[Kernel-packages] [Bug 1799276] Re: [Bionic] ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver
** Changed in: linux (Ubuntu Bionic)
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/1799276
Title:
[Bionic] ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
In Progress
Bug description:
[Impact]
The IPMI spec states:
The purpose of the SPMI Table is to provide a mechanism that can be
used by the OSPM (an ACPI term for “OS Operating System-directed
configuration and Power Management” essentially meaning an ACPI-aware
OS or OS loader) very early in the boot process, e.g., before the
ability to execute ACPI control methods in the OS is available.
When we are probing IPMI in Linux, ACPI control methods are available,
so we shouldn't be probing using SPMI. It could cause some confusion
during the probing process.
[Fix]
Fixed upstream in 4.17:
commit 4866b1dce0389013a268f0ab63f7229b30c6e5fe
Author: Corey Minyard
Date: Thu Mar 8 15:00:28 2018 -0600
ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver
[Test]
-- Test case --
for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; sudo modprobe
ipmi_ssif || exit; done
--
-- Before Applying the patch --
Jun 19 18:53:04 starbuck kernel: [ 126.351580] ipmi_ssif 0-000e: Found new
BMC (man_id: 0x00, prod_id: 0x0202, dev_id: 0x20)
Jun 19 18:53:06 starbuck kernel: [ 128.725391] ipmi_ssif: probe of
dmi-ipmi-ssif.1 failed with error -17
-- With patch applied --
Oct 19 19:59:49 starbuck kernel: [ 1501.699109] IPMI SSIF Interface driver
Oct 19 19:59:49 starbuck kernel: [ 1501.730439] ipmi_ssif: Trying
SMBIOS-specified SSIF interface at i2c address 0xe, adapter xlp9xx-i2c, slave
address 0x20
Oct 19 19:59:49 starbuck kernel: [ 1501.862509] ipmi_ssif 0-000e: Found new
BMC (man_id: 0x00, prod_id: 0x0202, dev_id: 0x20)
[Regression Potential]
This patch applies to ipmi_ssif driver and was tested on ARM64 Cavium
ThunderX2 platform and no regressions were found.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799276/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799281] Re: [Bionic][Cosmic] ipmi: Fix timer race with module unload
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Cosmic)
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/1799281
Title:
[Bionic][Cosmic] ipmi: Fix timer race with module unload
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
[Impact]
If you attempt to remove and insert the ipmi_ssif module a number of times,
it would result in a kernel panic. This is due to mod_timer from arming a timer
that was already removed by del_timer during module unload.
[Fix]
In linux-next:
0711e8c1b457 ipmi: Fix timer race with module unload
[Test]
-- Test Case --
for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; sudo modprobe
ipmi_ssif || exit; done
After the patch was applied, no kernel panics were obsereved. Tested on
Cavium ThunderX2.
[Regression Risk]
The patch was applied to bionic and tested tested on a Cavium ThunderX2 and
no regressions were found. Risk of regression none.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799281/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799049] Re: [bionic]mlx5: reading SW stats through ifstat cause kernel crash
** Changed in: linux (Ubuntu Bionic) 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/1799049 Title: [bionic]mlx5: reading SW stats through ifstat cause kernel crash Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: Description of problem: Attempting to read SW stats (ifstat -x cpu_hit) on a system with probed VFs will crash the system. How reproducible: Always Steps to Reproduce: 1. Create a VF echo 1 > /sys/bus/pci/devices/\:82\:00.0/sriov_numvfs 2. read SW stats: ifstat -x cpu_hit Actual results: System will crash Expected results: No system crash Additional info: The reason for the crash is insufficient check on the helper that determines if a netdev is vf rep. will crash: $ ifstat -x cpu_hit will not crash: $ ifstat -x cpu_hit $VF_REP $ ifstat -x cpu_hit $UPLINK_REP We already have a fix for this issue, and it is accepted upstream. https://patchwork.ozlabs.org/patch/935193/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799049/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730924] Re: Wifi does down "crash" in Surface Pro 4
Yes, just tried it and unfortunately no help, same coredump (let me know if you want one attached again) after playing a bit of video from youtube :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730924 Title: Wifi does down "crash" in Surface Pro 4 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I have a Surface Pro 4. The wifi works well in principle, but unfortunately it drops every x minutes. The only way to fix it I've found is to reboot the computer. lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: predatux 1537 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 8 10:41:26 2017 HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b Lsusb: Bus 002 Device 002: ID 045e:090c Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago) dmi.bios.date: 02/24/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1624.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1730924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801878] Re: NULL pointer dereference at 0000000000000020 when access dst_orig->ops->family in function xfrm_lookup_with_ifid()
** Description changed:
- [267265.140511] BUG: unable to handle kernel NULL pointer dereference at
0020
- [267265.144406] IP: xfrm_lookup+0x31/0x870
- [267265.146224] PGD 0 P4D 0
- [267265.147469] Oops: [#1] SMP PTI
- [267265.149141] Modules linked in: xt_iprange xt_nat ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_mangle xt_limit nf_log_ipv4 nf_log_common xt_LOG
xt_mark ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_conntrack veth overlay vxlan
ip6_udp_tunnel udp_tunnel xfs binfmt_misc xfrm4_mode_transport xfrm_user
xfrm4_tunnel tunnel4 iptable_nat nf_conntrack_ipv4 ipcomp nf_defrag_ipv4
xfrm_ipcomp nf_nat_ipv4 nf_nat esp4 nf_conntrack ah4 libcrc32c af_key xfrm_algo
iptable_filter ip_tables x_tables intel_rapl sb_edac crct10dif_pclmul
crc32_pclmul ghash_clmulni_intel pcbc aesni_intel input_leds aes_x86_64
i2c_piix4 crypto_simd glue_helper cryptd mac_hid serio_raw intel_rapl_perf
autofs4 cirrus ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops
psmouse pata_acpi ena drm floppy
- [267265.180439] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.15.0-36-generic
#39~16.04.1-Ubuntu
- [267265.184285] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
- [267265.187224] RIP: 0010:xfrm_lookup+0x31/0x870
- [267265.189246] RSP: 0018:98b542343a48 EFLAGS: 00010246
- [267265.191743] RAX: RBX: 98b542343ac8 RCX:
- [267265.195048] RDX: 98b542343ac8 RSI: RDI:
b39e4380
- [267265.198524] RBP: 98b542343ab8 R08: 0002 R09:
- [267265.201930] R10: 0020 R11: 7fb56465 R12:
- [267265.205235] R13: b39e4380 R14: 0002 R15:
b39e4380
- [267265.208567] FS: () GS:98b54234()
knlGS:
- [267265.212404] CS: 0010 DS: ES: CR0: 80050033
- [267265.215084] CR2: 0020 CR3: 0004ed40a001 CR4:
001606e0
- [267265.218442] DR0: DR1: DR2:
- [267265.221769] DR3: DR6: fffe0ff0 DR7:
0400
- [267265.225063] Call Trace:
- [267265.226280]
- [267265.227291] ? __xfrm_policy_check+0x41d/0x630
- [267265.229412] __xfrm_route_forward+0xa3/0x110
- [267265.231475] ip_forward+0x38c/0x470
- [267265.233140] ? ip_route_input_noref+0x28/0x40
- [267265.235214] ip_rcv_finish+0x124/0x410
- [267265.237041] ip_rcv+0x28e/0x3b0
- [267265.238572] ? inet_del_offload+0x40/0x40
- [267265.240487] __netif_receive_skb_core+0x879/0xba0
- [267265.242734] ? __skb_checksum+0x188/0x2c0
- [267265.244631] __netif_receive_skb+0x18/0x60
- [267265.246591] ? __netif_receive_skb+0x18/0x60
- [267265.248625] netif_receive_skb_internal+0x37/0xe0
- [267265.252142] ? tcp4_gro_complete+0x86/0x90
- [267265.255313] napi_gro_complete+0x73/0x90
- [267265.258432] dev_gro_receive+0x2ee/0x5c0
- [267265.261560] napi_gro_frags+0xa3/0x230
- [267265.264583] ena_clean_rx_irq+0x486/0x7c0 [ena]
- [267265.267981] ena_io_poll+0x41d/0x770 [ena]
- [267265.271189] net_rx_action+0x265/0x3b0
- [267265.274134] __do_softirq+0xf5/0x28f
- [267265.276933] irq_exit+0xb8/0xc0
- [267265.279648] xen_evtchn_do_upcall+0x30/0x40
- [267265.282691] xen_hvm_callback_vector+0x84/0x90
+ [Impact]
+
+ NULL pointer access happens when trying to access dst_orig->ops.
+
+ The function xfrm_lookup() calls xfrm_lookup_with_ifid() and there is
+ a line inside trying to access dst_orig->ops and it's exactly where the
+ panicing happens:
+
+ u16 family = dst_orig->ops->family;
+
+ As you can see that the symbol offset of ops is about 32(0x20) which
+ definitely is the error message shows in the kern.log:
+
+ [267265.140511] BUG: unable to handle kernel NULL pointer dereference
+ at 0020
+
+ struct dst_entry {
+ struct callback_head callback_head; /* 0 16 */
+ struct dst_entry * child; /* 16 8 */
+ struct net_device * dev; /* 24 8 */
+ struct dst_ops * ops; <-- /* 32 8 */
+
+ The oops:
+ BUG: unable to handle kernel NULL pointer dereference at 0020
+ IP: xfrm_lookup+0x31/0x870
+ PGD 0 P4D 0
+ Oops: [#1] SMP PTI
+ CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.15.0-36-generic
#39~16.04.1-Ubuntu
+ Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
+ RIP: 0010:xfrm_lookup+0x31/0x870
+ RSP: 0018:98b542343a48 EFLAGS: 00010246
+ RAX: RBX: 98b542343ac8 RCX:
+ RDX: 98b542343ac8 RSI: RDI: b39e4380
+ RBP: 98b542343ab8 R08: 0002 R09:
+ R10: 0020 R11: 7fb56465 R12:
+ R13: b39e4380 R14: 0002 R15: b39e4380
+ FS: () GS:98b54234() knlGS:
+ CS: 0010 DS: ES: CR0: 80050033
+ CR2: 0020 CR3: 0004ed40a001 CR4: 001606e0
+ DR0: 00
[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Would it be possible for you to do a kernel bisection? First, find the last good kernel and the first bad kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/ The range is from v4.5-rc1 to v4.8. Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the good version you found) $ git bisect bad $(the bad version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If the issue still happens, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HPE ProLiant DL360 gen9 Ubuntu Version: 18.04 Problem: When rebooting the server, everything goes well (shutting down services, unmounting etc) until the last step where it reads "Starting Reboot". At this point the system is getting stuck and nothing else can can be done than holding the power button in for a long enough time to turn it off. At the same time as the system get stuck, a red error light is lightening up on the server. This light is green until it reaches this "Starting Reboot" stage. The same happens if the server is shutdown, with the difference that the last message is "Starting Power-Off" instead of "Starting Reboot". The server is installed with a new clean 18.04 installation. This server was rebooting/shutting down without a problem with all releases between 16.04 and 17.10. This problem is serious as it prevents remote reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 11:16 seq crw-rw 1 root audio 116, 33 Jun 13 11:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro 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 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/21/2018 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
The problem is, it could take days before the system freezes. I don't know how to reproduce, it simply happens. I don't even know where to start. Maybe 4.17-rc1 and so on. But that's a huge task and one needs a lot of patience to do it. I'm not sure I'll be able to. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Triaged Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. 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: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: [Ubuntu] qdio: reset old sbal_state flags
SRU submitted:
[SRU][Bionic][PATCH 0/1] Fixes for LP1801686
https://lists.ubuntu.com/archives/kernel-team/2018-November/096462.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801686
Title:
[Ubuntu] qdio: reset old sbal_state flags
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
New
Status in linux source package in Cosmic:
New
Status in linux source package in Disco:
New
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 1800639] Re: [Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
updated SRU link:
https://lists.ubuntu.com/archives/kernel-team/2018-November/096436.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1800639
Title:
[Ubuntu] net/af_iucv: fix skb leaks for HiperTransport
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
Fix socket buffer (skb) leaks for HiperTransport
Description: net/af_iucv: fix skb leaks for HiperTransport
Symptom: Memory leaks and/or double-freed network packets.
Problem: Inbound packets may have any combination of flag bits set in
their iucv header. Current code only handles certain
combinations, and ignores (ie. leaks) all packets with other flags.
On Transmit, current code is inconsistent about whether the error
paths need to free the skb. Depending on which error path is
taken, it may either get freed twice, or leak.
Solution: On receive, drop any skb with an unexpected combination of iucv
Header flags.
On transmit, be consistent in all error paths about free'ing the skb.
== Fix ==
222440996d6daf635bed6cb35041be22ede3e8a0 ("net/af_iucv: drop inbound packets
with invalid flags")
b2f543949acd1ba64313fdad9e672ef47550d773 ("net/af_iucv: fix skb handling on
HiperTransport xmit error")
== Patch ==
commit 222440996d6daf635bed6cb35041be22ede3e8a0
Author: Julian Wiedmann
Date: Wed Sep 5 16:55:10 2018 +0200
net/af_iucv: drop inbound packets with invalid flags
Inbound packets may have any combination of flag bits set in their iucv
header. If we don't know how to handle a specific combination, drop the
skb instead of leaking it.
To clarify what error is returned in this case, replace the hard-coded
0 with the corresponding macro.
Signed-off-by: Julian Wiedmann
Signed-off-by: David S. Miller
==
commit b2f543949acd1ba64313fdad9e672ef47550d773
Author: Julian Wiedmann
Date: Wed Sep 5 16:55:11 2018 +0200
net/af_iucv: fix skb handling on HiperTransport xmit error
When sending an skb, afiucv_hs_send() bails out on various error
conditions. But currently the caller has no way of telling whether the
skb was freed or not - resulting in potentially either
a) leaked skbs from iucv_send_ctrl(), or
b) double-free's from iucv_sock_sendmsg().
As dev_queue_xmit() will always consume the skb (even on error), be
consistent and also free the skb from all other error paths. This way
callers no longer need to care about managing the skb.
Signed-off-by: Julian Wiedmann
Reviewed-by: Ursula Braun
Signed-off-by: David S. Miller
== Regression Potential ==
Low, because:
- IUCV functionality is very special to s390x and is only supported in z/VM
environments
(z/VM hypervisor to guest or guest to guest communications)
- So everything is s390x specific.
- Patch is limited to this single file: /net/iucv/af_iucv.c
- Patch was tested by IBM, and fixes an identified problem situation.
== Test Case ==
Set IUCV communication on an Ubuntu s390x system that runs as z/VM guest:
https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.linux.z.ludd/ludd_r_afiucv_setup.html
Provoke an error situation.
This is btw. hard to do, because the 'Inter-User Communication Vehicle"
(IUCV) is a virtual z/VM internal
network that does not use any real media.
To check for regressions one can use a shell over an ssh connection using an
IUCV interface
or use an application that utilises AF_IUCV sockets (like ICC).
__
Description: net/af_iucv: fix skb leaks for HiperTransport
Symptom: Memory leaks and/or double-freed network packets.
Problem: Inbound packets may have any combination of flag bits set in
their iucv header. Current code only handles certain
combinations, and ignores (ie. leaks) all packets with other
flags.
On Transmit, current code is inconsistent about whether the error
paths need to free the skb. Depending on which error path is
taken, it may either get freed twice, or leak.
Solution: On receive, drop any skb with an unexpected combination of iucv
Header flags.
On transmit, be consistent in all error paths about free'ing the
skb.
kerne 4.19
Upstream-ID: 222440996d6daf635bed6cb35041be22ede3e8a0
b2f543949acd1ba64313fdad9e672ef47550d773
Should also be applied, to all other Ubuntu Releases in the field !
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800639/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@list
[Kernel-packages] [Bug 1801686] Re: [Ubuntu] qdio: reset old sbal_state flags
SRU submitted:
[SRU][Bionic][PATCH 0/1] Fixes for LP1801686
https://lists.ubuntu.com/archives/kernel-team/2018-November/096433.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801686
Title:
[Ubuntu] qdio: reset old sbal_state flags
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
New
Status in linux source package in Cosmic:
New
Status in linux source package in Disco:
New
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 1801931] Re: Cosmic update: 4.18.13 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + 4.18.13 upstream stable release + from git://git.kernel.org/ -4.18.13 upstream stable release -from git://git.kernel.org/ + The following patches will be applied: + * rseq/selftests: fix parametrized test with -fpie + * mac80211: Run TXQ teardown code before de-registering interfaces + * mac80211_hwsim: require at least one channel + * Btrfs: fix unexpected failure of nocow buffered writes after snapshotting when + low on space + * KVM: PPC: Book3S HV: Don't truncate HPTE index in xlate function + * cfg80211: remove division by size of sizeof(struct ieee80211_wmm_rule) + * btrfs: btrfs_shrink_device should call commit transaction at the end + * scsi: csiostor: add a check for NULL pointer after kmalloc() + * scsi: csiostor: fix incorrect port capabilities + * scsi: libata: Add missing newline at end of file + * scsi: aacraid: fix a signedness bug + * bpf, sockmap: fix potential use after free in bpf_tcp_close + * bpf, sockmap: fix psock refcount leak in bpf_tcp_recvmsg + * bpf: sockmap, decrement copied count correctly in redirect error case + * mac80211: correct use of IEEE80211_VHT_CAP_RXSTBC_X + * mac80211_hwsim: correct use of IEEE80211_VHT_CAP_RXSTBC_X + * cfg80211: make wmm_rule part of the reg_rule structure + * mac80211_hwsim: Fix possible Spectre-v1 for hwsim_world_regdom_custom + * nl80211: Fix nla_put_u8 to u16 for NL80211_WMMR_TXOP + * nl80211: Pass center frequency in kHz instead of MHz + * bpf: fix several offset tests in bpf_msg_pull_data + * gpio: adp5588: Fix sleep-in-atomic-context bug + * mac80211: mesh: fix HWMP sequence numbering to follow standard + * mac80211: avoid kernel panic when building AMSDU from non-linear SKB + * gpiolib: acpi: Switch to cansleep version of GPIO library call + * gpiolib-acpi: Register GpioInt ACPI event handlers from a late_initcall + * gpio: dwapb: Fix error handling in dwapb_gpio_probe() + * bpf: fix msg->data/data_end after sg shift repair in bpf_msg_pull_data + * bpf: fix shift upon scatterlist ring wrap-around in bpf_msg_pull_data + * bpf: fix sg shift repair start offset in bpf_msg_pull_data + * tipc: switch to rhashtable iterator + * sh_eth: Add R7S9210 support + * net: mvpp2: initialize port of_node pointer + * tc-testing: add test-cases for numeric and invalid control action + * cfg80211: nl80211_update_ft_ies() to validate NL80211_ATTR_IE + * mac80211: do not convert to A-MSDU if frag/subframe limited + * mac80211: always account for A-MSDU header changes + * tools/kvm_stat: fix python3 issues + * tools/kvm_stat: fix handling of invalid paths in debugfs provider + * tools/kvm_stat: fix updates for dead guests + * gpio: Fix crash due to registration race + * ARC: atomics: unbork atomic_fetch_##op() + * Revert "blk-throttle: fix race between blkcg_bio_issue_check() and + cgroup_rmdir()" + * md/raid5-cache: disable reshape completely + * RAID10 BUG_ON in raise_barrier when force is true and conf->barrier is 0 + * selftests: pmtu: maximum MTU for vti4 is 2^16-1-20 + * selftests: pmtu: detect correct binary to ping ipv6 addresses + * ibmvnic: Include missing return code checks in reset function + * bpf: Fix bpf_msg_pull_data() + * bpf: avoid misuse of psock when TCP_ULP_BPF collides with another ULP + * i2c: uniphier: issue STOP only for last message or I2C_M_STOP + * i2c: uniphier-f: issue STOP only for last message or I2C_M_STOP + * net: cadence: Fix a sleep-in-atomic-context bug in macb_halt_tx() + * fs/cifs: don't translate SFM_SLASH (U+F026) to backslash + * mac80211: fix an off-by-one issue in A-MSDU max_subframe computation + * cfg80211: fix a type issue in ieee80211_chandef_to_operating_class() + * mac80211: fix WMM TXOP calculation + * mac80211: fix a race between restart and CSA flows + * mac80211: Fix station bandwidth setting after channel switch + * mac80211: don't Tx a deauth frame if the AP forbade Tx + * mac80211: shorten the IBSS debug messages + * fsnotify: fix ignore mask logic in fsnotify() + * net/ibm/emac: wrong emac_calc_base call was used by typo + * n
[Kernel-packages] [Bug 1801931] Re: Cosmic update: 4.18.13 upstream stable release
Skipping because those were already applied for bug #1792209. * "net: hns: add the code for cleaning pkt in chip" * "net: hns: add netif_carrier_off before change speed and duplex" Skip "HID: i2c-hid: Don't reset device upon system resume" because it was already applied for bug #1792309. Skipping because those were already applied for bug #1792044 * "net: ena: fix surprise unplug NULL dereference kernel crash" * "net: ena: fix driver when PAGE_SIZE == 64kB" * "net: ena: fix device destruction to gracefully free resources" * "net: ena: fix potential double ena_destroy_device()" * "net: ena: fix missing lock during device destruction" * "net: ena: fix missing calls to READ_ONCE" Skip "s390/qeth: use vzalloc for QUERY OAT buffer" because it was already applied for bug #1793086. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801931 Title: Cosmic update: 4.18.13 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.18.13 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
To answer my own question: that update removed a blacklisting in blacklist.conf. The result of that removal, on my system, was that the touchpad stopped working after suspend, even when S3 was not enabled. A few hacks get the touchpad working again, but not properly - edge- scrolling, and I suspect some other functions, are lost. -- You 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
[Kernel-packages] [Bug 1801931] [NEW] Cosmic update: 4.18.13 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.18.13 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Cosmic) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => 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/1801931 Title: Cosmic update: 4.18.13 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.18.13 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
** Also affects: unattended-upgrades (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: unattended-upgrades (Ubuntu Xenial) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => In Progress ** Changed in: unattended-upgrades (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in unattended-upgrades source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in unattended-upgrades source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in unattended-upgrades source package in Cosmic: Fix Released Status in linux source package in Disco: Invalid Status in unattended-upgrades source package in Disco: Fix Released Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801116] Re: linux-aws: 4.15.0-1027.27 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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: 1799411 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED regression-testing: Testing in progress snap-release-to-candidate: Snap not in 18/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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1801116 Title: linux-aws: 4.15.0-1027.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released 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-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: 1799411 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress snap-release-to-candidate: Snap not in 18/candidate channel verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801922] 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/1801922 Title: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to install/upgrade: installed linux-image-4.15.0-36-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: I've tried to install nvidia-304 and the system told me that was impossible, and I couldn't remove the kernel 4.15.0.36. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: snd_hda_codec_via snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm edac_mce_amd kvm_amd snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device k8temp kvm irqbypass input_leds serio_raw snd_timer snd soundcore shpchp mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid nouveau mxm_wmi wmi video i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse pata_acpi forcedeth pata_amd sata_nv i2c_nforce2 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jota 1271 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Nov 6 11:44:00 2018 ErrorMessage: installed linux-image-4.15.0-36-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2018-11-04 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. enp0s7no wireless extensions. Lsusb: Bus 001 Device 025: ID 04e8:6865 Samsung Electronics Co., Ltd GT-I9300 Phone [Galaxy S III] (PTP mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 192f:0416 Avago Technologies, Pte. ADNS-5700 Optical Mouse Controller (3-button) Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a0615c99-82b5-44b1-8410-4861f5b6b168 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.7 RfKill: SourcePackage: linux Title: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to install/upgrade: installed linux-image-4.15.0-36-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: N68-S dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801123] Re: linux-aws: 4.4.0-1034.37 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing 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: 1799401 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing in progress regression-testing: Testing in progress 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/1801123 Title: linux-aws: 4.4.0-1034.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released 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 Trusty: 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: 1799401 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801124] Re: linux-aws: 4.4.0-1072.82 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** 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: 1799401 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing in progress + automated-testing: Testing FAILED regression-testing: Testing in progress 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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1801124 Title: linux-aws: 4.4.0-1072.82 -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: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released 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-aws package in Ubuntu: Invalid Status in linux-aws 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: 1799401 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress 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/1801124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
** Changed in: unattended-upgrades (Ubuntu Bionic) Assignee: Eric Desrochers (slashd) => (unassigned) ** Changed in: unattended-upgrades (Ubuntu Bionic) Assignee: (unassigned) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in unattended-upgrades source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in unattended-upgrades source package in Cosmic: Fix Released Status in linux source package in Disco: Invalid Status in unattended-upgrades source package in Disco: Fix Released Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
