[Kernel-packages] [Bug 1826410] Re: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10]
Debian: root@d10-sid:~# apt-cache show libbpf-dev libbpf4.19 Package: libbpf-dev Source: linux Version: 4.19.37-5 Installed-Size: 378 Maintainer: Debian Kernel Team Architecture: amd64 Depends: libbpf4.19 (= 4.19.37-5) Description-en: eBPF helper library (development files) libbpf is a library for loading eBPF programs and reading and manipulating eBPF objects from user-space. Description-md5: b8834dcec31d23cd9577fbae4ac6a867 Multi-Arch: same Homepage: https://www.kernel.org/ Tag: devel::library, role::devel-lib Section: libdevel Priority: optional Filename: pool/main/l/linux/libbpf-dev_4.19.37-5_amd64.deb Size: 289844 MD5sum: 52493b768caf815e814b60a4a4b9ee0e SHA256: bcd283261336ae8ac5eefde91b4d43b8923c6eb48da9466b3485f95f86ca3506 Package: libbpf4.19 Source: linux Version: 4.19.37-5 Installed-Size: 344 Maintainer: Debian Kernel Team Architecture: amd64 Depends: libc6 (>= 2.26), libelf1 (>= 0.131) Description-en: eBPF helper library (shared library) libbpf is a library for loading eBPF programs and reading and manipulating eBPF objects from user-space. Description-md5: 320aac663a5bd3caf223c7aa27857113 Multi-Arch: same Homepage: https://www.kernel.org/ Tag: role::shared-lib Section: libs Priority: optional Filename: pool/main/l/linux/libbpf4.19_4.19.37-5_amd64.deb Size: 287356 MD5sum: 592e499e9b22192d08e8a7e621036bd7 SHA256: ef5e355ae43dfddc9d83c161bb78c8fe6ea465ed8ad3885d894caf7b4e5cafbc Eoan: root@d:~# apt-cache search libbpf libbpfcc - shared library for BPF Compiler Collection (BCC) libbpfcc-dev - shared library for BPF Compiler Collection (BCC) This might (again?) be a stray bug update. This isn't fixed in Eoan, re-opening the bug. ** Changed in: linux (Ubuntu) Status: Fix Released => 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/1826410 Title: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10] Status in linux package in Ubuntu: Triaged Bug description: Hi, Debian packages libbpf and so far does so out of the kernel source [1]. There is some movement to separate that from the kernel source [2] but this isn't ready yet. So far it is just a sync of the subtree out of the kernel sources. Since we do not share our kernel packaging we will not get this for-free without doing anything. If there will be an ITP about it in Debian I'll let you know and we can abort this, but unless that really happens I wanted to ask if you could as well build the libbpf* packages for 19.10 and onward? Note: this is not the same bpf lib as [3] despite the similarity in names. Reasoning: BPF becomes more and more important in general and is used in the kernel for many things. In the case that brought it to my attention it will be a PMD of DPDK that will need it to control XDP [4]. And XDP in general is an interesting and rising feature for network acceleration - I'd think it would be helpful to have this package around in Ubuntu. [1]: https://packages.debian.org/sid/libbpf-dev [2]: https://github.com/libbpf/libbpf [3]: https://github.com/iovisor/bcc [4]: https://www.iovisor.org/technology/xdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836585] Re: Xenial kernel 4.4.0-155.182 fails to build perf with libnuma
** Changed in: linux (Ubuntu Xenial) 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/1836585 Title: Xenial kernel 4.4.0-155.182 fails to build perf with libnuma Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: [Impact] When libnuma-dev is installed on the build environment, tools/perf tries to build bench/numa.c, but in the current Xenial kernel in -proposed it fails: CC bench/numa.o bench/numa.c: In function 'lfsr_32': bench/numa.c:729:24: error: implicit declaration of function 'BIT' [-Werror=implicit-function-declaration] const uint32_t taps = BIT(1) | BIT(5) | BIT(6) | BIT(31); ^ bench/numa.c:729:2: error: nested extern declaration of 'BIT' [-Werror=nested-externs] const uint32_t taps = BIT(1) | BIT(5) | BIT(6) | BIT(31); ^ [Fix] Commit "UBUNTU: SAUCE: perf/bench: Drop definition of BIT in numa.c", applied for "Xenial update: 4.4.180 upstream stable release (LP: #1830176)" is causing build failures on tools/perf/bench after stable upstream commit "perf tools: No need to include bitops.h in util.h" removed the inclusion of the header file where the BIT() macro is defined. The fix is to revert the SAUCE patch and keep the definition of BIT() in loco in numa.c as done in 4.4 stable upstream. [Test Case] 1. Install libnuma-dev package on the build environment. 2. cd xenial/linux source directory. 3. fakeroot debian/rules clean 4. cd tools/perf 5. make [Regression Potential] Low. The fix is to revert a SAUCE patch that was applied to fix a build failure that has been fixed upstream and it's not needed anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836694] 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/1836694 Title: memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic Status in linux package in Ubuntu: Confirmed Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836694] [NEW] memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic
Public bug reported: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 bionic uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836694 Title: memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic Status in linux package in Ubuntu: New Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each *
[Kernel-packages] [Bug 1827452] Re: null pointer dereference in uvcvideo
[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/1827452 Title: null pointer dereference in uvcvideo Status in linux package in Ubuntu: Expired Bug description: I have a logitech c920 webcam. When using this camera in obs-studio v23.x, all of my USB devices stop working and I see the following in my kernel log: [ 590.282211] usb 3-3: new high-speed USB device number 5 using xhci_hcd [ 592.660916] usb 3-3: New USB device found, idVendor=046d, idProduct=082d, bcdDevice= 0.11 [ 592.660922] usb 3-3: New USB device strings: Mfr=0, Product=2, SerialNumber=1 [ 592.660925] usb 3-3: Product: HD Pro Webcam C920 [ 592.660928] usb 3-3: SerialNumber: 2EAD866F [ 592.664600] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d) [ 592.666416] uvcvideo 3-3:1.0: Entity type for entity Processing 3 was not initialized! [ 592.666421] uvcvideo 3-3:1.0: Entity type for entity Extension 6 was not initialized! [ 592.666425] uvcvideo 3-3:1.0: Entity type for entity Extension 12 was not initialized! [ 592.666428] uvcvideo 3-3:1.0: Entity type for entity Camera 1 was not initialized! [ 592.666430] uvcvideo 3-3:1.0: Entity type for entity Extension 8 was not initialized! [ 592.666433] uvcvideo 3-3:1.0: Entity type for entity Extension 9 was not initialized! [ 592.666436] uvcvideo 3-3:1.0: Entity type for entity Extension 10 was not initialized! [ 592.666439] uvcvideo 3-3:1.0: Entity type for entity Extension 11 was not initialized! [ 592.22] input: HD Pro Webcam C920 as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input23 [ 748.490453] usb 3-3: reset high-speed USB device number 5 using xhci_hcd [ 938.125745] usb 3-3: USB disconnect, device number 5 [ 943.298530] BUG: unable to handle kernel NULL pointer dereference at [ 943.298533] #PF error: [normal kernel read fault] [ 943.298534] PGD 8007ca5f3067 P4D 8007ca5f3067 PUD 0 [ 943.298536] Oops: [#1] SMP PTI [ 943.298538] CPU: 0 PID: 9442 Comm: libobs: graphic Tainted: P OE 5.0.0-13-generic #14-Ubuntu [ 943.298539] Hardware name: Gigabyte Technology Co., Ltd. Z87-HD3/Z87-HD3, BIOS F7 01/20/2014 [ 943.298543] RIP: 0010:usb_ifnum_to_if+0x24/0x60 [ 943.298544] Code: ff c3 0f 1f 40 00 0f 1f 44 00 00 55 48 8b 87 c0 03 00 00 48 89 e5 48 85 c0 74 43 0f b6 48 04 84 c9 74 39 48 8b 90 98 00 00 00 <48> 8b 3a 0f b6 7f 02 39 fe 74 2b 48 8d 90 a0 00 00 00 8d 41 ff 48 [ 943.298545] RSP: 0018:bdae493dbab0 EFLAGS: 00010202 [ 943.298547] RAX: a106ae527000 RBX: a1070ad0a800 RCX: 0004 [ 943.298547] RDX: RSI: 0001 RDI: a1070ad0a800 [ 943.298548] RBP: bdae493dbab0 R08: 00027040 R09: b57825b8 [ 943.298549] R10: fba45fce4bc0 R11: 0001 R12: [ 943.298550] R13: a10644187b98 R14: ff92 R15: a1075131a000 [ 943.298551] FS: 7f93c40d7700() GS:a1075ea0() knlGS: [ 943.298552] CS: 0010 DS: ES: CR0: 80050033 [ 943.298553] CR2: CR3: 0006f8a94004 CR4: 001606f0 [ 943.298553] Call Trace: [ 943.298557] usb_hcd_alloc_bandwidth+0x241/0x370 [ 943.298559] usb_set_interface+0xfc/0x380 [ 943.298565] uvc_video_start_transfer+0x155/0x4b0 [uvcvideo] [ 943.298568] uvc_video_start_streaming+0x7f/0xd0 [uvcvideo] [ 943.298570] uvc_start_streaming+0x28/0x70 [uvcvideo] [ 943.298573] vb2_start_streaming+0x6d/0x110 [videobuf2_common] [ 943.298575] vb2_core_streamon+0x59/0xc0 [videobuf2_common] [ 943.298578] vb2_streamon+0x18/0x30 [videobuf2_v4l2] [ 943.298580] uvc_queue_streamon+0x2e/0x50 [uvcvideo] [ 943.298582] uvc_ioctl_streamon+0x3f/0x60 [uvcvideo] [ 943.298588] v4l_streamon+0x20/0x30 [videodev] [ 943.298592] __video_do_ioctl+0x19a/0x3f0 [videodev] [ 943.298596] video_usercopy+0x1a6/0x660 [videodev] [ 943.298599] ? v4l_s_fmt+0x630/0x630 [videodev] [ 943.298603] video_ioctl2+0x15/0x20 [videodev] [ 943.298606] v4l2_ioctl+0x49/0x50 [videodev] [ 943.298608] do_vfs_ioctl+0xa9/0x640 [ 943.298610] ? __switch_to_asm+0x34/0x70 [ 943.298611] ? __switch_to_asm+0x40/0x70 [ 943.298612] ? __switch_to_asm+0x34/0x70 [ 943.298612] ? __switch_to_asm+0x40/0x70 [ 943.298613] ? __switch_to_asm+0x34/0x70 [ 943.298614] ? __switch_to_asm+0x40/0x70 [ 943.298615] ? __switch_to_asm+0x34/0x70 [ 943.298616] ? __switch_to_asm+0x40/0x70 [ 943.298617] ksys_ioctl+0x67/0x90 [ 943.298619] __x64_sys_ioctl+0x1a/0x20 [ 943.298621] do_syscall_64+0x5a/0x110 [ 943.298622]
[Kernel-packages] [Bug 1830682] Re: cve-2017-5754 from cve test suite in LTP failed with KVM kernel
Didn't see this anymore, mark it as fix-released. ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1830682 Title: cve-2017-5754 from cve test suite in LTP failed with KVM kernel Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: Invalid Bug description: It looks like this is cause by the absence of kallsyms: safe_file_ops.c:202: BROK: Failed to open FILE '/proc/kallsyms' for reading at meltdown.c:272: ENOENT <<>> tag=cve-2017-5754 stime=1559026443 cmdline="meltdown" contacts="" analysis=exit <<>> tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s meltdown.c:259: INFO: access time: cached = 49, uncached = 290, threshold = 119 safe_file_ops.c:202: BROK: Failed to open FILE '/proc/kallsyms' for reading at meltdown.c:272: ENOENT Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=2 corefile=no cutime=21 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1013-kvm 4.18.0-1013.13 ProcVersionSignature: User Name 4.18.0-1013.13-kvm 4.18.20 Uname: Linux 4.18.0-1013-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 Date: Tue May 28 06:54:14 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up
Oh - and now it looks like bluetooth is working! Is it possible that turning it off for 45s just wasn't enough? I thought that should be plenty...? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836467 Title: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up Status in linux-firmware package in Ubuntu: Incomplete Bug description: This is similar to https://bugs.launchpad.net/bugs/1829737 - however the issue was not fixed by linux-firmware 1.173.8 so I was advised to log a new bug. I have an ASUS ZenBook 14 - UX433FA - which based on this - https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html - I believe has an Intel 9560 chipset (I am not sure how to independently verify this). With kernels older than 4.20 I can successfully pair my bluetooth mouse (Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request failed to create LE connection: status 0x0c" messages. I'm running Linux Mint 19.1 I tried installing linux-firmware 1.173.8, and it didn't seem to help - I also downloaded 1.173.9 proposed from here: https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and that also didn't seem to help. Both after a cold reboot and a warm reboot I see [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 in my dmesg output. Bluetooth works just fine with earlier kernels (however other aspects of the laptop like suspend don't work as well, which is why I'm trying the newer kernel. Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3 12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux dmesg | egrep -i 'blue|firm' [ [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 14.641146] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2 [ 14.642377] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2 [ 14.642392] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2 [ 14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [ 14.675356] Bluetooth: Core ver 2.22 [ 14.675374] Bluetooth: HCI device and connection manager initialized [ 14.675377] Bluetooth: HCI socket layer initialized [ 14.675379] Bluetooth: L2CAP socket layer initialized [ 14.675382] Bluetooth: SCO socket layer initialized [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [ 15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.207801] Bluetooth: BNEP filters: protocol multicast [ 15.207804] Bluetooth: BNEP socket layer initialized [ 22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 22.040232] Bluetooth: HIDP socket layer initialized [ 22.042238] input: Logitech K810 Keyboard as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27 [ 22.042996] input: Logitech K810 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28 [ 22.043235] input: Logitech K810 System Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input29 [ 22.043426] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID v12.02 Keyboard [Logitech K810] on 00:bb:60:09:27:1a [ 29.296700] Bluetooth: RFCOMM TTY layer initialized [ 29.296705] Bluetooth: RFCOMM socket layer initialized [ 29.296711] Bluetooth: RFCOMM ver 1.11 [ 217.675736] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 217.709807] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.537827] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.767709] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 220.244821] Bluetooth: hci0: request failed to create LE connection: status 0x0c If there are any other debugging things to try, or info you need, let me know... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up
** Attachment added: "dmesg2.out" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836467/+attachment/5277252/+files/dmesg2.out -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836467 Title: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up Status in linux-firmware package in Ubuntu: Incomplete Bug description: This is similar to https://bugs.launchpad.net/bugs/1829737 - however the issue was not fixed by linux-firmware 1.173.8 so I was advised to log a new bug. I have an ASUS ZenBook 14 - UX433FA - which based on this - https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html - I believe has an Intel 9560 chipset (I am not sure how to independently verify this). With kernels older than 4.20 I can successfully pair my bluetooth mouse (Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request failed to create LE connection: status 0x0c" messages. I'm running Linux Mint 19.1 I tried installing linux-firmware 1.173.8, and it didn't seem to help - I also downloaded 1.173.9 proposed from here: https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and that also didn't seem to help. Both after a cold reboot and a warm reboot I see [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 in my dmesg output. Bluetooth works just fine with earlier kernels (however other aspects of the laptop like suspend don't work as well, which is why I'm trying the newer kernel. Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3 12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux dmesg | egrep -i 'blue|firm' [ [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 14.641146] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2 [ 14.642377] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2 [ 14.642392] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2 [ 14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [ 14.675356] Bluetooth: Core ver 2.22 [ 14.675374] Bluetooth: HCI device and connection manager initialized [ 14.675377] Bluetooth: HCI socket layer initialized [ 14.675379] Bluetooth: L2CAP socket layer initialized [ 14.675382] Bluetooth: SCO socket layer initialized [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [ 15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.207801] Bluetooth: BNEP filters: protocol multicast [ 15.207804] Bluetooth: BNEP socket layer initialized [ 22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 22.040232] Bluetooth: HIDP socket layer initialized [ 22.042238] input: Logitech K810 Keyboard as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27 [ 22.042996] input: Logitech K810 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28 [ 22.043235] input: Logitech K810 System Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input29 [ 22.043426] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID v12.02 Keyboard [Logitech K810] on 00:bb:60:09:27:1a [ 29.296700] Bluetooth: RFCOMM TTY layer initialized [ 29.296705] Bluetooth: RFCOMM socket layer initialized [ 29.296711] Bluetooth: RFCOMM ver 1.11 [ 217.675736] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 217.709807] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.537827] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.767709] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 220.244821] Bluetooth: hci0: request failed to create LE connection: status 0x0c If there are any other debugging things to try, or info you need, let me know... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up
I tried it for about 3 minutes this time, and I think I see the line you are looking for: [ 11.182302] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi I'll attache the entire log... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836467 Title: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up Status in linux-firmware package in Ubuntu: Incomplete Bug description: This is similar to https://bugs.launchpad.net/bugs/1829737 - however the issue was not fixed by linux-firmware 1.173.8 so I was advised to log a new bug. I have an ASUS ZenBook 14 - UX433FA - which based on this - https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html - I believe has an Intel 9560 chipset (I am not sure how to independently verify this). With kernels older than 4.20 I can successfully pair my bluetooth mouse (Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request failed to create LE connection: status 0x0c" messages. I'm running Linux Mint 19.1 I tried installing linux-firmware 1.173.8, and it didn't seem to help - I also downloaded 1.173.9 proposed from here: https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and that also didn't seem to help. Both after a cold reboot and a warm reboot I see [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 in my dmesg output. Bluetooth works just fine with earlier kernels (however other aspects of the laptop like suspend don't work as well, which is why I'm trying the newer kernel. Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3 12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux dmesg | egrep -i 'blue|firm' [ [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 14.641146] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2 [ 14.642377] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2 [ 14.642392] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2 [ 14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [ 14.675356] Bluetooth: Core ver 2.22 [ 14.675374] Bluetooth: HCI device and connection manager initialized [ 14.675377] Bluetooth: HCI socket layer initialized [ 14.675379] Bluetooth: L2CAP socket layer initialized [ 14.675382] Bluetooth: SCO socket layer initialized [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [ 15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.207801] Bluetooth: BNEP filters: protocol multicast [ 15.207804] Bluetooth: BNEP socket layer initialized [ 22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 22.040232] Bluetooth: HIDP socket layer initialized [ 22.042238] input: Logitech K810 Keyboard as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27 [ 22.042996] input: Logitech K810 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28 [ 22.043235] input: Logitech K810 System Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input29 [ 22.043426] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID v12.02 Keyboard [Logitech K810] on 00:bb:60:09:27:1a [ 29.296700] Bluetooth: RFCOMM TTY layer initialized [ 29.296705] Bluetooth: RFCOMM socket layer initialized [ 29.296711] Bluetooth: RFCOMM ver 1.11 [ 217.675736] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 217.709807] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.537827] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.767709] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 220.244821] Bluetooth: hci0: request failed to create LE connection: status 0x0c If there are any other debugging things to try, or info you need, let me know... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774636] Re: Lenovo V330 needs patch in ideapad_laptop module for rfkill
It also affects my brand new Legion Y540. rmmod idea-laptop works, but when I blacklisted it and rebooted, I had no wifi ifaces at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774636 Title: Lenovo V330 needs patch in ideapad_laptop module for rfkill Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: == SRU Justification == The quite new Lenovo V330 is not yet completely supported by the ideapad_laptop module. Without an explicit rule, this module assumes that a hardware kill switch for wireless devices exists and thus sometimes boots up with all devices hard blocked and no way to reenable them at runtime. This requested patch has been sent upstream, but it is not in mainline as of yet. Since this laptop is available now and the bug is a real blocker for unexperienced users, this patch is being request as SAUCE. == Fix == UBUNTU: SAUCE: Add Lenovo V330 to the ideapad_laptop rfkill blacklist == Regression Potential == Low. This patch just adds an additon DMI entry. == 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. The quite new Lenovo V330 is not yet completely supported by the ideapad_laptop module. Without an explicit rule, this module assumes that a hardware kill switch for wireless devices exists and thus sometimes boots up with all devices hard blocked and no way to reenable them at runtime. I have provided a patch to the kernel developers upstream: https://bugzilla.kernel.org/show_bug.cgi?id=199855 However, there is not much activity at the moment. Since this laptop is available now and the bug is a real blocker for unexperienced users, would it be possible to add the (quite simple) fix to the ubuntu kernel until it is accepted upstream? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up
Thanks @vicamo. I powered off and let it sit for about 45s before the log I sent you... I'll try again and leave it off for a longer period and see if I see the line... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836467 Title: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up Status in linux-firmware package in Ubuntu: Incomplete Bug description: This is similar to https://bugs.launchpad.net/bugs/1829737 - however the issue was not fixed by linux-firmware 1.173.8 so I was advised to log a new bug. I have an ASUS ZenBook 14 - UX433FA - which based on this - https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html - I believe has an Intel 9560 chipset (I am not sure how to independently verify this). With kernels older than 4.20 I can successfully pair my bluetooth mouse (Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request failed to create LE connection: status 0x0c" messages. I'm running Linux Mint 19.1 I tried installing linux-firmware 1.173.8, and it didn't seem to help - I also downloaded 1.173.9 proposed from here: https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and that also didn't seem to help. Both after a cold reboot and a warm reboot I see [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 in my dmesg output. Bluetooth works just fine with earlier kernels (however other aspects of the laptop like suspend don't work as well, which is why I'm trying the newer kernel. Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3 12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux dmesg | egrep -i 'blue|firm' [ [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 14.641146] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2 [ 14.642377] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2 [ 14.642392] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2 [ 14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [ 14.675356] Bluetooth: Core ver 2.22 [ 14.675374] Bluetooth: HCI device and connection manager initialized [ 14.675377] Bluetooth: HCI socket layer initialized [ 14.675379] Bluetooth: L2CAP socket layer initialized [ 14.675382] Bluetooth: SCO socket layer initialized [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [ 15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.207801] Bluetooth: BNEP filters: protocol multicast [ 15.207804] Bluetooth: BNEP socket layer initialized [ 22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 22.040232] Bluetooth: HIDP socket layer initialized [ 22.042238] input: Logitech K810 Keyboard as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27 [ 22.042996] input: Logitech K810 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28 [ 22.043235] input: Logitech K810 System Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input29 [ 22.043426] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID v12.02 Keyboard [Logitech K810] on 00:bb:60:09:27:1a [ 29.296700] Bluetooth: RFCOMM TTY layer initialized [ 29.296705] Bluetooth: RFCOMM socket layer initialized [ 29.296711] Bluetooth: RFCOMM ver 1.11 [ 217.675736] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 217.709807] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.537827] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.767709] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 220.244821] Bluetooth: hci0: request failed to create LE connection: status 0x0c If there are any other debugging things to try, or info you need, let me know... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up
Hi @wjbaird, thank you for the logs. From your lspci output, we should be able to confirm it's a "Intel(R) Dual Band Wireless AC 9560"[1], and we should have the support in linux-oem-osp1 kernel since bug 1833065. For -generic kernel flavors, the backport-iwlwifi-dkms in ppa:canonical- hwe-team/pc-oem-dkms[2] is required, and we're working on publish it to ubuntu archive. For bluetooth, unfortunately we still have no luck to retrieve the firmware name from dmesg. I met this before. All I know is that it takes a complete power off, wait for a period, power on and you may find the line that gives firmware name in this first boot. With the blob firmware name, we may begin to find out which revision of that given blob works for you. If the latest one from linux-firmware git repository[3] still doesn't work well, then we'll probably need to file a bug to Intel instead. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/tree/drivers/net/wireless/intel/iwlwifi/cfg/9000.c#n218 [2]: https://code.launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem-dkms [3]: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836467 Title: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up Status in linux-firmware package in Ubuntu: Incomplete Bug description: This is similar to https://bugs.launchpad.net/bugs/1829737 - however the issue was not fixed by linux-firmware 1.173.8 so I was advised to log a new bug. I have an ASUS ZenBook 14 - UX433FA - which based on this - https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html - I believe has an Intel 9560 chipset (I am not sure how to independently verify this). With kernels older than 4.20 I can successfully pair my bluetooth mouse (Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request failed to create LE connection: status 0x0c" messages. I'm running Linux Mint 19.1 I tried installing linux-firmware 1.173.8, and it didn't seem to help - I also downloaded 1.173.9 proposed from here: https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and that also didn't seem to help. Both after a cold reboot and a warm reboot I see [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 in my dmesg output. Bluetooth works just fine with earlier kernels (however other aspects of the laptop like suspend don't work as well, which is why I'm trying the newer kernel. Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3 12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux dmesg | egrep -i 'blue|firm' [ [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 14.641146] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2 [ 14.642377] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2 [ 14.642392] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2 [ 14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [ 14.675356] Bluetooth: Core ver 2.22 [ 14.675374] Bluetooth: HCI device and connection manager initialized [ 14.675377] Bluetooth: HCI socket layer initialized [ 14.675379] Bluetooth: L2CAP socket layer initialized [ 14.675382] Bluetooth: SCO socket layer initialized [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [ 15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.207801] Bluetooth: BNEP filters: protocol multicast [ 15.207804] Bluetooth: BNEP socket layer initialized [ 22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 22.040232] Bluetooth: HIDP socket layer initialized [ 22.042238] input: Logitech K810 Keyboard as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27 [ 22.042996] input: Logitech K810 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28 [ 22.043235] input: Logitech K810 System Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input29 [ 22.043426] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID v12.02 Keyboard [Logitech K810] on 00:bb:60:09:27:1a [ 29.296700] Bluetooth: RFCOMM TTY layer
[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up
Thanks @vicamo - I followed the process you described and attached the output. Let me know if there's anything else I can do. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836467 Title: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up Status in linux-firmware package in Ubuntu: Incomplete Bug description: This is similar to https://bugs.launchpad.net/bugs/1829737 - however the issue was not fixed by linux-firmware 1.173.8 so I was advised to log a new bug. I have an ASUS ZenBook 14 - UX433FA - which based on this - https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html - I believe has an Intel 9560 chipset (I am not sure how to independently verify this). With kernels older than 4.20 I can successfully pair my bluetooth mouse (Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request failed to create LE connection: status 0x0c" messages. I'm running Linux Mint 19.1 I tried installing linux-firmware 1.173.8, and it didn't seem to help - I also downloaded 1.173.9 proposed from here: https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and that also didn't seem to help. Both after a cold reboot and a warm reboot I see [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 in my dmesg output. Bluetooth works just fine with earlier kernels (however other aspects of the laptop like suspend don't work as well, which is why I'm trying the newer kernel. Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3 12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux dmesg | egrep -i 'blue|firm' [ [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 14.641146] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2 [ 14.642377] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2 [ 14.642392] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2 [ 14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [ 14.675356] Bluetooth: Core ver 2.22 [ 14.675374] Bluetooth: HCI device and connection manager initialized [ 14.675377] Bluetooth: HCI socket layer initialized [ 14.675379] Bluetooth: L2CAP socket layer initialized [ 14.675382] Bluetooth: SCO socket layer initialized [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [ 15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.207801] Bluetooth: BNEP filters: protocol multicast [ 15.207804] Bluetooth: BNEP socket layer initialized [ 22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 22.040232] Bluetooth: HIDP socket layer initialized [ 22.042238] input: Logitech K810 Keyboard as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27 [ 22.042996] input: Logitech K810 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28 [ 22.043235] input: Logitech K810 System Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input29 [ 22.043426] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID v12.02 Keyboard [Logitech K810] on 00:bb:60:09:27:1a [ 29.296700] Bluetooth: RFCOMM TTY layer initialized [ 29.296705] Bluetooth: RFCOMM socket layer initialized [ 29.296711] Bluetooth: RFCOMM ver 1.11 [ 217.675736] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 217.709807] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.537827] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.767709] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 220.244821] Bluetooth: hci0: request failed to create LE connection: status 0x0c If there are any other debugging things to try, or info you need, let me know... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up
** Attachment added: "lspci output" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836467/+attachment/5277248/+files/lspci_out.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836467 Title: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up Status in linux-firmware package in Ubuntu: Incomplete Bug description: This is similar to https://bugs.launchpad.net/bugs/1829737 - however the issue was not fixed by linux-firmware 1.173.8 so I was advised to log a new bug. I have an ASUS ZenBook 14 - UX433FA - which based on this - https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html - I believe has an Intel 9560 chipset (I am not sure how to independently verify this). With kernels older than 4.20 I can successfully pair my bluetooth mouse (Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request failed to create LE connection: status 0x0c" messages. I'm running Linux Mint 19.1 I tried installing linux-firmware 1.173.8, and it didn't seem to help - I also downloaded 1.173.9 proposed from here: https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and that also didn't seem to help. Both after a cold reboot and a warm reboot I see [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 in my dmesg output. Bluetooth works just fine with earlier kernels (however other aspects of the laptop like suspend don't work as well, which is why I'm trying the newer kernel. Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3 12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux dmesg | egrep -i 'blue|firm' [ [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 14.641146] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2 [ 14.642377] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2 [ 14.642392] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2 [ 14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [ 14.675356] Bluetooth: Core ver 2.22 [ 14.675374] Bluetooth: HCI device and connection manager initialized [ 14.675377] Bluetooth: HCI socket layer initialized [ 14.675379] Bluetooth: L2CAP socket layer initialized [ 14.675382] Bluetooth: SCO socket layer initialized [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [ 15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.207801] Bluetooth: BNEP filters: protocol multicast [ 15.207804] Bluetooth: BNEP socket layer initialized [ 22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 22.040232] Bluetooth: HIDP socket layer initialized [ 22.042238] input: Logitech K810 Keyboard as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27 [ 22.042996] input: Logitech K810 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28 [ 22.043235] input: Logitech K810 System Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input29 [ 22.043426] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID v12.02 Keyboard [Logitech K810] on 00:bb:60:09:27:1a [ 29.296700] Bluetooth: RFCOMM TTY layer initialized [ 29.296705] Bluetooth: RFCOMM socket layer initialized [ 29.296711] Bluetooth: RFCOMM ver 1.11 [ 217.675736] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 217.709807] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.537827] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.767709] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 220.244821] Bluetooth: hci0: request failed to create LE connection: status 0x0c If there are any other debugging things to try, or info you need, let me know... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up
** Attachment added: "dmesg output" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836467/+attachment/5277247/+files/dmesg.out -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836467 Title: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up Status in linux-firmware package in Ubuntu: Incomplete Bug description: This is similar to https://bugs.launchpad.net/bugs/1829737 - however the issue was not fixed by linux-firmware 1.173.8 so I was advised to log a new bug. I have an ASUS ZenBook 14 - UX433FA - which based on this - https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html - I believe has an Intel 9560 chipset (I am not sure how to independently verify this). With kernels older than 4.20 I can successfully pair my bluetooth mouse (Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request failed to create LE connection: status 0x0c" messages. I'm running Linux Mint 19.1 I tried installing linux-firmware 1.173.8, and it didn't seem to help - I also downloaded 1.173.9 proposed from here: https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and that also didn't seem to help. Both after a cold reboot and a warm reboot I see [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 in my dmesg output. Bluetooth works just fine with earlier kernels (however other aspects of the laptop like suspend don't work as well, which is why I'm trying the newer kernel. Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3 12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux dmesg | egrep -i 'blue|firm' [ [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 14.641146] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2 [ 14.642377] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2 [ 14.642392] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2 [ 14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [ 14.675356] Bluetooth: Core ver 2.22 [ 14.675374] Bluetooth: HCI device and connection manager initialized [ 14.675377] Bluetooth: HCI socket layer initialized [ 14.675379] Bluetooth: L2CAP socket layer initialized [ 14.675382] Bluetooth: SCO socket layer initialized [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [ 15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.207801] Bluetooth: BNEP filters: protocol multicast [ 15.207804] Bluetooth: BNEP socket layer initialized [ 22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 22.040232] Bluetooth: HIDP socket layer initialized [ 22.042238] input: Logitech K810 Keyboard as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27 [ 22.042996] input: Logitech K810 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28 [ 22.043235] input: Logitech K810 System Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input29 [ 22.043426] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID v12.02 Keyboard [Logitech K810] on 00:bb:60:09:27:1a [ 29.296700] Bluetooth: RFCOMM TTY layer initialized [ 29.296705] Bluetooth: RFCOMM socket layer initialized [ 29.296711] Bluetooth: RFCOMM ver 1.11 [ 217.675736] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 217.709807] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.537827] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.767709] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 220.244821] Bluetooth: hci0: request failed to create LE connection: status 0x0c If there are any other debugging things to try, or info you need, let me know... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834085] 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/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: Applying InputClass "libinput touchpad catchall" de juny 13 21:37:50 TM1703
[Kernel-packages] [Bug 1733168] Re: resume from hibernate is slow and not reliable (nvidia)
I got another computer, same type, slightly different equipment. The problem no linger occurs. So I think it was strongly hardware related. ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1733168 Title: resume from hibernate is slow and not reliable (nvidia) Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Bug description: My system: ubuntu 17.04 gnome desktop 4GB RAM 2x3GHz core duo Nvidia GT 630 TWO MONITORS, attached to the video card with DVI / HDMI (I think this is important...) When resuming from suspend to RAM, my system very often will first show the unlocked screen I saw before suspend, and then switch both screens dark again. Again pressing a keyboard key whill then switch on monitors again and I get the password prompt. The whole process goes for more than 20s, which is annoying. Often (several times a week) it completely fails and the system will freeze in various status. I'v been experiencing this bug since something like 3 years now with various (clean) installation, graphics drivers and kernel versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1733168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836211] Re: bcmwl fails to install with recent Eoan (Bad return status for module build on kernel: 5.0.0-20-generic)
Please search your /var/lib/dkms and find the relevant build log for bcmwl containing the error, then attach it here. ** Changed in: bcmwl (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1836211 Title: bcmwl fails to install with recent Eoan (Bad return status for module build on kernel: 5.0.0-20-generic) Status in bcmwl package in Ubuntu: Incomplete Bug description: With recent Eoan builds, bcmwl fails to install completely, . It had worked when I installed Eoan a couple weeks ago, but not when I first tried to clean install on 9 July until today. (I've unfortunately erased the old, working installation so I don't have more details.) $ sudo apt install bcmwl-kernel-source Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: dkms Suggested packages: menu The following NEW packages will be installed: bcmwl-kernel-source dkms 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 1,610 kB of archives. After this operation, 8,359 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 dkms all 2.7.1-1ubuntu1 [66.5 kB] Get:2 http://us.archive.ubuntu.com/ubuntu eoan/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu5 [1,544 kB] Fetched 1,610 kB in 0s (4,097 kB/s) Selecting previously unselected package dkms. (Reading database ... 122315 files and directories currently installed.) Preparing to unpack .../dkms_2.7.1-1ubuntu1_all.deb ... Unpacking dkms (2.7.1-1ubuntu1) ... Selecting previously unselected package bcmwl-kernel-source. Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu5_amd64.deb ... Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Setting up dkms (2.7.1-1ubuntu1) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.0.0-20-generic Building for architecture x86_64 Building initial module for 5.0.0-20-generic Error! Bad return status for module build on kernel: 5.0.0-20-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Processing triggers for man-db (2.8.5-2) ... Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 11 09:02:53 2019 InstallationDate: Installed on 2019-07-11 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1836211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up
** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836467 Title: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up Status in linux-firmware package in Ubuntu: Incomplete Bug description: This is similar to https://bugs.launchpad.net/bugs/1829737 - however the issue was not fixed by linux-firmware 1.173.8 so I was advised to log a new bug. I have an ASUS ZenBook 14 - UX433FA - which based on this - https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html - I believe has an Intel 9560 chipset (I am not sure how to independently verify this). With kernels older than 4.20 I can successfully pair my bluetooth mouse (Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request failed to create LE connection: status 0x0c" messages. I'm running Linux Mint 19.1 I tried installing linux-firmware 1.173.8, and it didn't seem to help - I also downloaded 1.173.9 proposed from here: https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and that also didn't seem to help. Both after a cold reboot and a warm reboot I see [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 in my dmesg output. Bluetooth works just fine with earlier kernels (however other aspects of the laptop like suspend don't work as well, which is why I'm trying the newer kernel. Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3 12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux dmesg | egrep -i 'blue|firm' [ [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 14.641146] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2 [ 14.642377] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2 [ 14.642392] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2 [ 14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [ 14.675356] Bluetooth: Core ver 2.22 [ 14.675374] Bluetooth: HCI device and connection manager initialized [ 14.675377] Bluetooth: HCI socket layer initialized [ 14.675379] Bluetooth: L2CAP socket layer initialized [ 14.675382] Bluetooth: SCO socket layer initialized [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [ 15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.207801] Bluetooth: BNEP filters: protocol multicast [ 15.207804] Bluetooth: BNEP socket layer initialized [ 22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 22.040232] Bluetooth: HIDP socket layer initialized [ 22.042238] input: Logitech K810 Keyboard as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27 [ 22.042996] input: Logitech K810 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28 [ 22.043235] input: Logitech K810 System Control as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input29 [ 22.043426] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID v12.02 Keyboard [Logitech K810] on 00:bb:60:09:27:1a [ 29.296700] Bluetooth: RFCOMM TTY layer initialized [ 29.296705] Bluetooth: RFCOMM socket layer initialized [ 29.296711] Bluetooth: RFCOMM ver 1.11 [ 217.675736] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 217.709807] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.537827] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 218.767709] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 220.244821] Bluetooth: hci0: request failed to create LE connection: status 0x0c If there are any other debugging things to try, or info you need, let me know... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836521] Re: Mainline kernel build failure for i386 and amd64 - v5.2.1, v5.1.18 [error: '-mindirect-branch' and '-fcf-protection' are not compatible]
*** This bug is a duplicate of bug 1830961 *** https://bugs.launchpad.net/bugs/1830961 Sounds like bug 1830961, which was closed just today. I guess the problem here is that this bug is reported against the wrong component... The 'linux' source package is not the mainline kernel, it's the Ubuntu kernel :) ** Summary changed: - Mainline kernel build failure for i386 and amd64 - v5.2.1, v5.1.18 + Mainline kernel build failure for i386 and amd64 - v5.2.1, v5.1.18 [error: '-mindirect-branch' and '-fcf-protection' are not compatible] ** Package changed: linux (Ubuntu) => ubuntu ** This bug has been marked a duplicate of bug 1830961 Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836521 Title: Mainline kernel build failure for i386 and amd64 - v5.2.1, v5.1.18 [error: '-mindirect-branch' and '-fcf-protection' are not compatible] Status in Ubuntu: Confirmed Bug description: The mainline kernel builds on kernels.ubuntu.com are in failed state for the latest kernel versions. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.17/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.18/ Build seems to have failed for i386 and amd64 but succeeded for other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1836521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
If the new kernel works per comment #25 then no specific DKMS packages need fixing. ** Changed in: xtables-addons (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in gcc-9 package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Won't Fix Status in xtables-addons package in Ubuntu: Won't Fix Bug description: Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
** No longer affects: tlp (Ubuntu) ** Changed in: linux (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/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in linux package in Ubuntu: New Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: Applying InputClass "libinput touchpad catchall" de juny 13 21:37:50 TM1703
[Kernel-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in gcc-9 package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Won't Fix Status in xtables-addons package in Ubuntu: Confirmed Bug description: Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836476] Re: Binarypplication/x-rpm: bcmwl
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** 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/1836476 Title: Binarypplication/x-rpm: bcmwl Status in linux package in Ubuntu: Invalid Bug description: Binarypplication/x-rpm: bcmwl-kernel-source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: hibmc-drm Causes Unreadable Display for Huawei amd64 Servers
** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Disco) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Eoan) 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/1762940 Title: hibmc-drm Causes Unreadable Display for Huawei amd64 Servers Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1762940 [Impact] amd64 based Huawei servers have problems where the display output of their iBMC chips is broken, resulting in a "blurry" screen when viewed from their in house remote kvm-like console. Example: https://launchpadlibrarian.net/365907668/creen_picture_for_blur.png The issue is caused by the hibmc_drm kernel module being loaded. The PCI ID for the iBMC chips on amd64 hardware is the same as arm64 hardware, but the hibmc_drm driver was developed only for use on arm64 hardware, most notably for the Huawei D05 development board. The impact to Huawei is that their customers cannot use Ubuntu server install media as the screen goes "blurry" when the d-i install media or subuqity installer loads the hibmc_drm kernel module after language selection. The only workaround for their customers is to press the "E" key during the very first installer menu and adding "modprobe.blacklist=hibmc_drm" to the kernel command line in the grub menu. This is not good for customer experience with their servers. Other problems exist for the hibmc_drm driver on amd64, such as working on bios, but not uefi, and not being wayland compatible, making the screen blurry whenever a desktop session is started and gdm loaded. Huawei have asked us to remove hibmc_drm from all architectures except arm64, and this aligns with advice from Hisilicon. [Fix] I modified the config/annotations file to remove all architectures except arm64, and created a patch for Kconfig to set a firm requirement on ARM64 for hibmc_drm. I will send the Kconfig patch upstream in the coming days for a more permanent fix. [Testcase] Apply the patches and run: ubuntu-bionic/CONFIGS$ fakeroot debian/rules genconfigs ubuntu-bionic/CONFIGS$ grep -Rin "hibmc" . ./arm64-config.flavour.generic:5739:CONFIG_DRM_HISI_HIBMC=m You should see that only arm64 has the config option enabled. A test kernel has been built, and is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf232667-test Huawei requested a test d-i install iso to test server install with, which can be found here and uses the kernel from the ppa above: https://people.canonical.com/~mruffell/sf232667_ubuntu_server_d-i_20190711b1.iso Both the test kernel and the custom d-i install iso have been tested on amd64 Huawei server hardware successfully and video output is functional. [Regression Potential] Regressions will be limited to hardware containing the iBMC chips from Hisilicon, which I believe are exclusive to Huawei servers. I have taken care to ensure that hibmc_drm is enabled for ARM64 so it should not impact kernels built for the Huawei D05 arm64 development board, and d-i will still load the hibmc_drm driver during startup for arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836665] [NEW] Xenial update: 4.4.182 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.182 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836665 Title: Xenial update: 4.4.182 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.182 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836668] [NEW] Xenial update: 4.4.185 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.185 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836668 Title: Xenial update: 4.4.185 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.185 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836666] [NEW] Xenial update: 4.4.183 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.183 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: Xenial update: 4.4.183 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.183 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836667] [NEW] Xenial update: 4.4.184 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.184 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836667 Title: Xenial update: 4.4.184 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.184 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835939] Re: The 18.04 linux kernel hangs and crashes when shutting down a Windows 10 instance running under vmware
Thanks Scott, I've made the bug public. There's a surprising number of crashes reported to the error tracker -- I wonder if your hardware is entirely stable? Have you run memtest86 or memtest86+ recently? Is there anything in your smartctl output that would indicate drive problems? Thanks ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835939 Title: The 18.04 linux kernel hangs and crashes when shutting down a Windows 10 instance running under vmware Status in linux package in Ubuntu: Incomplete Bug description: This is the second crash and the second time that I have reported this problem. I apologize but I forgot to make a note of the bug number and can't seem to find it. My whoopsie number is 02aff7e0e154c826180cb958966df0a740c15d05305d3d9b6520f8fae51f25680fa7831afada8c542654d752a069fc813fcb29567e21d3c0f9b84d2a0147fdf3b I ran the "ubuntu-bug linux" command to send configuration information. If I need to do something else, please let me know. VMware Workstation 15.1.0 build-13591040 I have had the system hand once using Oracle's Virtual Box (i.e. exiting from Windows) but there was no crash. Let me know what other information I need to give you. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: butler 3213 F pulseaudio /dev/snd/controlC1: butler 3213 F pulseaudio /dev/snd/controlC0: butler 3213 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Jul 9 14:05:40 2019 HibernationDevice: RESUME=UUID=81a753c1-bc6b-4040-8aff-c2495d989ba3 InstallationDate: Installed on 2018-06-16 (387 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. CM6870 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=512M-:192M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM6870 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0708:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnCM6870:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6870:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: CM6870 dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829749] Re: [MIR] Please add support for SIPL
https://lists.ubuntu.com/archives/kernel-team/2019-July/102204.html
https://lists.ubuntu.com/archives/kernel-team/2019-July/102205.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/1829749
Title:
[MIR] Please add support for SIPL
Status in Launchpad itself:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in linux-signed package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
Fix Released
Status in s390-tools-signed package in Ubuntu:
Fix Released
Bug description:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1829749/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836211] Re: bcmwl fails to install with recent Eoan (Bad return status for module build on kernel: 5.0.0-20-generic)
Please mark the bug as affecting you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1836211 Title: bcmwl fails to install with recent Eoan (Bad return status for module build on kernel: 5.0.0-20-generic) Status in bcmwl package in Ubuntu: New Bug description: With recent Eoan builds, bcmwl fails to install completely, . It had worked when I installed Eoan a couple weeks ago, but not when I first tried to clean install on 9 July until today. (I've unfortunately erased the old, working installation so I don't have more details.) $ sudo apt install bcmwl-kernel-source Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: dkms Suggested packages: menu The following NEW packages will be installed: bcmwl-kernel-source dkms 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 1,610 kB of archives. After this operation, 8,359 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 dkms all 2.7.1-1ubuntu1 [66.5 kB] Get:2 http://us.archive.ubuntu.com/ubuntu eoan/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu5 [1,544 kB] Fetched 1,610 kB in 0s (4,097 kB/s) Selecting previously unselected package dkms. (Reading database ... 122315 files and directories currently installed.) Preparing to unpack .../dkms_2.7.1-1ubuntu1_all.deb ... Unpacking dkms (2.7.1-1ubuntu1) ... Selecting previously unselected package bcmwl-kernel-source. Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu5_amd64.deb ... Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Setting up dkms (2.7.1-1ubuntu1) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.0.0-20-generic Building for architecture x86_64 Building initial module for 5.0.0-20-generic Error! Bad return status for module build on kernel: 5.0.0-20-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Processing triggers for man-db (2.8.5-2) ... Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 11 09:02:53 2019 InstallationDate: Installed on 2019-07-11 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1836211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767992] Re: Linux md raid-10 freezes during resync
Thank you for testing that and providing a test case, Damir! I've gone ahead and submitted that patch to the mailing list: https://lists.ubuntu.com/archives/kernel-team/2019-July/102199.html ** Description changed: + [Impact] + + * If regular and resync IO happen at the same time during a regular IO + split, the split bio will wait until resync IO finishes while at the + same time the resync IO is waiting for regular IO to finish. This + results in deadlock. + + * I believe this only impacts Bionic as Disco+ already contains this + commit. Xenial doesn't contain the commit that this one fixes. + + [Test Case] + + The test kernel containing this commit received positive feedback in the + launchpad bug. + + From the launchpad bug comment #10: + + "For reproduce on 4.15.0-50-generic: Make new raid-10, add some io fio/dd, + unpack anaconda archives, after minute or two deadlocked" + + [Regression Potential] + + * This fix has been in mainline since December 2018 and I don't see any + fixup commits upstream referencing this one. The small number of + changes in this commit seem reasonable for managing the `nr_pending` + adjustments which preclude either regular or resync IO. + + + Original bug description follows: + - + I'm trying to setup a few nodes with software raid-10. When array is created and resync is running i'm trying to install a few packages and frequently system stops responding, resync process stops, and I'm getting following errors in the kernel log. This looks like a deadlock for me. I had this problem in both 18.04 and 16.04. Reboot is the only way to fix the node. [ 2659.317256] INFO: task kworker/u24:13:343 blocked for more than 120 seconds. [ 2659.317313] Not tainted 4.15.0-20-generic #21-Ubuntu [ 2659.317350] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2659.317401] kworker/u24:13 D0 343 2 0x8000 [ 2659.317414] Workqueue: writeback wb_workfn (flush-9:1) [ 2659.317417] Call Trace: [ 2659.317430] __schedule+0x297/0x8b0 [ 2659.317435] schedule+0x2c/0x80 [ 2659.317443] wait_barrier+0x146/0x1a0 [raid10] [ 2659.317449] ? wait_woken+0x80/0x80 [ 2659.317454] raid10_write_request+0x77/0x950 [raid10] [ 2659.317459] ? r10bio_pool_alloc+0x24/0x30 [raid10] [ 2659.317465] ? mempool_alloc+0x71/0x190 [ 2659.317469] ? ___slab_alloc+0x20a/0x4b0 [ 2659.317475] ? md_write_start+0xc8/0x200 [ 2659.317480] ? mempool_alloc_slab+0x15/0x20 [ 2659.317484] raid10_make_request+0xcc/0x140 [raid10] [ 2659.317489] md_handle_request+0x126/0x1a0 [ 2659.317494] md_make_request+0x6b/0x150 [ 2659.317501] generic_make_request+0x124/0x300 [ 2659.317506] submit_bio+0x73/0x150 [ 2659.317510] ? submit_bio+0x73/0x150 [ 2659.317579] xfs_submit_ioend+0x87/0x1c0 [xfs] [ 2659.317626] xfs_do_writepage+0x377/0x6a0 [xfs] [ 2659.317632] write_cache_pages+0x20c/0x4e0 [ 2659.317674] ? xfs_vm_writepages+0xf0/0xf0 [xfs] [ 2659.317682] ? intel_pstate_update_pstate+0x40/0x40 [ 2659.317687] ? update_load_avg+0x5c5/0x6e0 [ 2659.317727] xfs_vm_writepages+0xbe/0xf0 [xfs] [ 2659.317732] do_writepages+0x4b/0xe0 [ 2659.317738] ? check_preempt_curr+0x83/0x90 [ 2659.317742] ? ttwu_do_wakeup+0x1e/0x150 [ 2659.317746] __writeback_single_inode+0x45/0x340 [ 2659.317749] ? __writeback_single_inode+0x45/0x340 [ 2659.317752] writeback_sb_inodes+0x1e1/0x510 [ 2659.317756] __writeback_inodes_wb+0x67/0xb0 [ 2659.317759] wb_writeback+0x271/0x300 [ 2659.317764] wb_workfn+0x180/0x410 [ 2659.317766] ? wb_workfn+0x180/0x410 [ 2659.317773] process_one_work+0x1de/0x410 [ 2659.317776] worker_thread+0x32/0x410 [ 2659.317781] kthread+0x121/0x140 [ 2659.317784] ? process_one_work+0x410/0x410 [ 2659.317788] ? kthread_create_worker_on_cpu+0x70/0x70 [ 2659.317793] ? do_syscall_64+0x73/0x130 [ 2659.317797] ? SyS_exit_group+0x14/0x20 [ 2659.317801] ret_from_fork+0x35/0x40 [ 2659.317806] INFO: task md1_resync:429 blocked for more than 120 seconds. [ 2659.317853] Not tainted 4.15.0-20-generic #21-Ubuntu [ 2659.317889] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2659.317940] md1_resync D0 429 2 0x8000 [ 2659.317943] Call Trace: [ 2659.317949] __schedule+0x297/0x8b0 [ 2659.317954] schedule+0x2c/0x80 [ 2659.317959] raise_barrier+0xa1/0x1a0 [raid10] [ 2659.317963] ? wait_woken+0x80/0x80 [ 2659.317968] raid10_sync_request+0x205/0x1f10 [raid10] [ 2659.317975] ? find_next_bit+0xb/0x10 [ 2659.317980] ? cpumask_next+0x1b/0x20 [ 2659.317985] ? is_mddev_idle+0x92/0xf4 [ 2659.317990] md_do_sync+0x8ca/0xf10 [ 2659.317994] ? wait_woken+0x80/0x80 [ 2659.318000] md_thread+0x129/0x170 [ 2659.318004] ? mddev_put+0x140/0x140 [ 2659.318007] ? md_thread+0x129/0x170 [ 2659.318012] kthread+0x121/0x140 [ 2659.318015] ?
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Ready for Release phase-changed: Monday, 15. July 2019 22:07 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-release: Pending -- ready to copy variant: debs ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Ready for Release phase-changed: Monday, 15. July 2019 22:07 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836654] Re: Bionic update: upstream stable patchset 2019-07-15
** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836654 Title: Bionic update: upstream stable patchset 2019-07-15 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: 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: upstream stable patchset 2019-07-15 Ported from the following upstream stable releases: v4.14.78, v4.18.16, v4.14.79, v4.18.17, v4.14.80, v4.18.18 from git://git.kernel.org/ media: af9035: prevent buffer overflow on write batman-adv: Avoid probe ELP information leak batman-adv: Fix segfault when writing to throughput_override batman-adv: Fix segfault when writing to sysfs elp_interval batman-adv: Prevent duplicated gateway_node entry batman-adv: Prevent duplicated nc_node entry batman-adv: Prevent duplicated softif_vlan entry batman-adv: Prevent duplicated global TT entry batman-adv: Prevent duplicated tvlv handler batman-adv: fix backbone_gw refcount on queue_work() failure batman-adv: fix hardif_neigh refcount on queue_work() failure clocksource/drivers/ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for non-am43 SoCs scsi: ibmvscsis: Fix a stringop-overflow warning scsi: ibmvscsis: Ensure partition name is properly NUL terminated intel_th: pci: Add Ice Lake PCH support Input: atakbd - fix Atari keymap Input: atakbd - fix Atari CapsLock behaviour net: emac: fix fixed-link setup for the RTL8363SB switch ravb: do not write 1 to reserved bits PCI: dwc: Fix scheduling while atomic issues drm: mali-dp: Call drm_crtc_vblank_reset on device init scsi: ipr: System hung while dlpar adding primary ipr adapter back scsi: sd: don't crash the host on invalid commands net/mlx4: Use cpumask_available for eq->affinity_mask clocksource/drivers/fttmr010: Fix set_next_event handler powerpc/tm: Fix userspace r13 corruption powerpc/tm: Avoid possible userspace r1 corruption on reclaim iommu/amd: Return devid as alias for ACPI HID devices ARC: build: Get rid of toolchain check ARC: build: Don't set CROSS_COMPILE in arch's Makefile HID: quirks: fix support for Apple Magic Keyboards staging: ccree: check DMA pool buf !NULL before free net/smc: fix sizeof to int comparison qed: Fix populating the invalid stag value in multi function mode. RDMA/uverbs: Fix validity check for modify QP bpf: test_maps, only support ESTABLISHED socks RDMA/bnxt_re: Fix system crash during RDMA resource initialization RISC-V: include linux/ftrace.h in asm-prototypes.h powerpc/numa: Use associativity if VPHN hcall is successful x86/boot: Fix kexec booting failure in the SEV bit detection code xfrm: Validate address prefix lengths in the xfrm selector. xfrm6: call kfree_skb when skb is toobig xfrm: reset transport header back to network header after all input transforms ahave been applied xfrm: reset crypto_done when iterating over multiple input xfrms mac80211: Always report TX status cfg80211: reg: Init wiphy_idx in regulatory_hint_core() mac80211: fix pending queue hang due to TX_DROP cfg80211: Address some corner cases in scan result channel updating mac80211: TDLS: fix skb queue/priority assignment mac80211: fix TX status reporting for ieee80211s ARM: 8799/1: mm: fix pci_ioremap_io() offset check xfrm: validate template mode netfilter: bridge: Don't sabotage nf_hook calls from an l3mdev arm64: hugetlb: Fix handling of young ptes ARM: dts: BCM63xx: Fix incorrect interrupt specifiers net: macb: Clean 64b dma addresses if they are not detected soc: fsl: qbman: qman: avoid allocating from non existing gen_pool soc: fsl: qe: Fix copy/paste bug in ucc_get_tdm_sync_shift() mac80211_hwsim: do not omit multicast announce of first added radio Bluetooth: SMP: fix crash in unpairing pxa168fb: prepare the clock qed: Avoid implicit enum conversion in qed_set_tunn_cls_info qed: Fix mask parameter in qed_vf_prep_tunn_req_tlv qed: Avoid implicit enum conversion in qed_roce_mode_to_flavor qed: Avoid constant logical operation warning in qed_vf_pf_acquire qed: Avoid implicit enum conversion in qed_iwarp_parse_rx_pkt asix: Check for supported Wake-on-LAN modes ax88179_178a: Check for supported
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
** Also affects: linux (Ubuntu Eoan) Importance: High Status: Triaged ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => Triaged ** Changed in: linux (Ubuntu Disco) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Description changed: - For all(as I know) Huawei servers, the vga adapter are embed in the iBMC - chips. Those server can install from ISO manually for 16.04.4 and screen - display normally. But for 18.04 ( tested both for daily and final - beta)version, the install screen is blur. One of tested server is Huawei - 2855 v5, the certification link for 16.04 are - https://certification.ubuntu.com/hardware/201707-25596/. + BugLink: https://bugs.launchpad.net/bugs/1762940 - Below are key difference of dmesg. It seems might related with DRM. + [Impact] - 18.04 install screen is blur - dmesg - ... - [2.039009] fb0: EFI VGA frame buffer device - ... - [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). - [4.191435] [drm] No driver support for vblank timestamp query. - [4.209338] checking generic (9000 30) vs hw (0 0) - [4.209384] fbcon: hibmcdrmfb (fb1) is primary device - [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 - ... - [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device - [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 - ... - [5.636624] vga16fb: initializing - [5.636627] vga16fb: mapped to 0x48a7a1d2 - [5.636630] checking generic (9000 30) vs hw (a 1) - [5.636676] fb2: VGA16 VGA frame buffer device - ... + amd64 based Huawei servers have problems where the display output of + their iBMC chips is broken, resulting in a "blurry" screen when viewed + from their in house remote kvm-like console. - 16.04.4 install screen is fine (no screen blur) - dmesg - ... - [2.000419] fb0: EFI VGA frame buffer device - - [8.795065] vga16fb: initializing - [8.795068] vga16fb: mapped to 0x880a - [8.795071] checking generic (9800 30) vs hw (a 1) - [8.795121] fb1: VGA16 VGA frame buffer device - ... + Example: + + https://launchpadlibrarian.net/365907668/creen_picture_for_blur.png + + The issue is caused by the hibmc_drm kernel module being loaded. The PCI ID for the iBMC chips on amd64 hardware is the same as arm64 hardware, but the + hibmc_drm driver was developed only for use on arm64 hardware, most notably for the Huawei D05 development board. + + The impact to Huawei is that their customers cannot use Ubuntu server install + media as the screen goes "blurry" when the d-i install media or subuqity + installer loads the hibmc_drm kernel module after language selection. + + The only workaround for their customers is to press the "E" key during + the very first installer menu and adding "modprobe.blacklist=hibmc_drm" + to the kernel command line in the grub menu. This is not good for + customer experience with their servers. + + Other problems exist for the hibmc_drm driver on amd64, such as working on + bios, but not uefi, and not being wayland compatible, making the screen blurry whenever a desktop session is started and gdm loaded. + + Huawei have asked us to remove hibmc_drm from all architectures except arm64, + and this aligns with advice from Hisilicon. + + [Fix] + + I modified the config/annotations file to remove all architectures + except arm64, and created a patch for Kconfig to set a firm requirement + on ARM64 for hibmc_drm. + + I will send the Kconfig patch upstream in the coming days for a more + permanent fix. + + [Testcase] + + Apply the patches and run: + + ubuntu-bionic/CONFIGS$ fakeroot debian/rules genconfigs + ubuntu-bionic/CONFIGS$ grep -Rin "hibmc" . + ./arm64-config.flavour.generic:5739:CONFIG_DRM_HISI_HIBMC=m + + You should see that only arm64 has the config option enabled. + + A test kernel has been built, and is available here: + https://launchpad.net/~mruffell/+archive/ubuntu/sf232667-test + + Huawei requested a test d-i install iso to test server install with, which can be found here and uses the kernel from the ppa above: + https://people.canonical.com/~mruffell/sf232667_ubuntu_server_d-i_20190711b1.iso + + Both the test kernel and the custom d-i install iso have been tested on amd64 + Huawei server hardware successfully and video output is functional. + + [Regression Potential] + + Regressions will be limited to hardware containing the iBMC chips from + Hisilicon, which I believe are exclusive to Huawei servers. + + I have taken care to ensure that hibmc_drm is
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
Yes, I have turned it off an on several times during the day. But give me a couple of days and I will check (and attach) the corresponding logs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in linux package in Ubuntu: Incomplete Status in tlp package in Ubuntu: Incomplete Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
Did you reboot your machine after uninstalling TLP ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in linux package in Ubuntu: Incomplete Status in tlp package in Ubuntu: Incomplete Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: Applying InputClass "libinput touchpad catchall" de juny 13 21:37:50 TM1703
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Released Bug description: === SRU Justification === [Impact] Qualcomm WiFi/Bluetooth may disappear after boot. [Fix] Disable USB2 LPM at shutdown phase, to prevent it from lingering in LPM L1. Pull back the device to full power before shutdown imitates the behavior on Windows. [Test] The affected user confimed it fixes the issue. I can also confirm that a) The power drain in S5 is much lower, b) Both WiFi and Bluetooth are always present during reboot stress test. [Regression Potential] Low. Only a limited number of USB2 devices that support LPM. === Original Bug Report === Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package:
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods. [Test case] $ sudo perf record -k 1 -e instructions:u ./java -agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32 $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted $ sudo perf report -f -i ./perf.data.jitted [Fix] Include java build dependencies and install the library into linux-tools package. [Regression potential] Small regression potential, an extra file is distributed and is not automatically linked to anything. It could impact the build, which was tested. ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- linux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826410] Re: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10]
This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826410 Title: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10] Status in linux package in Ubuntu: Fix Released Bug description: Hi, Debian packages libbpf and so far does so out of the kernel source [1]. There is some movement to separate that from the kernel source [2] but this isn't ready yet. So far it is just a sync of the subtree out of the kernel sources. Since we do not share our kernel packaging we will not get this for-free without doing anything. If there will be an ITP about it in Debian I'll let you know and we can abort this, but unless that really happens I wanted to ask if you could as well build the libbpf* packages for 19.10 and onward? Note: this is not the same bpf lib as [3] despite the similarity in names. Reasoning: BPF becomes more and more important in general and is used in the kernel for many things. In the case that brought it to my attention it will be a PMD of DPDK that will need it to control XDP [4]. And XDP in general is an interesting and rising feature for network acceleration - I'd think it would be helpful to have this package around in Ubuntu. [1]: https://packages.debian.org/sid/libbpf-dev [2]: https://github.com/libbpf/libbpf [3]: https://github.com/iovisor/bcc [4]: https://www.iovisor.org/technology/xdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: [Impact] We enabled CONFIG_DMA_CMA to fix bug 1803206, but that led to a regression on other arm64 systems that began spewing these messages on boot - sometimes > 10K of them: [ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 In a previous SRU (bug 1828092), we worked around this by just rate- limiting these messages. These are "err" priority messages though, so even a lower number of them is still disconcerting. [Fix] 1) Bump up the amount of available CMA on arm64 to 32M (same as upstream defconfig) 2) A patch-set from linux-next that redirects dma-direct contiguous allocations to alloc_pages() for single page allocations (single pages are by definition contiguous), avoiding CMA usage/fragmentation. [Test Case] dmesg | grep "cma_alloc: alloc failed" Some system configs will still have some of these errors even after this fix - but this should reduce them significantly. Per-driver optimizations can be used to make further improvements, but we should track those in other bugs. [Regression Risk] Tested on a HiSilicon D06 and HP m400 (Hi1620 & X-Gene arm64). Regression tested on: - Raspberry Pi 3B (see Comment #22) - Power9 system (ppc64el) - z/VM instance (s390x) - Intel Centerton system (amd64) Test builds are staged at http://ppa.launchpad.net/~dannf/ubuntu/cma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829050] Re: Eoan update: v5.1.2 upstream stable release
This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829050 Title: Eoan update: v5.1.2 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released 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: v5.1.2 upstream stable release from git://git.kernel.org/ Linux 5.1.2 x86/speculation/mds: Fix documentation typo Documentation: Correct the possible MDS sysfs values x86/mds: Add MDSUM variant to the MDS documentation x86/speculation/mds: Add 'mitigations=' support for MDS s390/speculation: Support 'mitigations=' cmdline option powerpc/speculation: Support 'mitigations=' cmdline option x86/speculation: Support 'mitigations=' cmdline option cpu/speculation: Add 'mitigations=' cmdline option x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off x86/speculation/mds: Fix comment x86/speculation/mds: Add SMT warning message x86/speculation: Move arch_smt_update() call to after mitigation decisions x86/speculation/mds: Add mds=full,nosmt cmdline option Documentation: Add MDS vulnerability documentation Documentation: Move L1TF to separate directory x86/speculation/mds: Add mitigation mode VMWERV x86/speculation/mds: Add sysfs reporting for MDS x86/speculation/mds: Add mitigation control for MDS x86/speculation/mds: Conditionally clear CPU buffers on idle entry x86/kvm/vmx: Add MDS protection when L1D Flush is not active x86/speculation/mds: Clear CPU buffers on exit to user x86/speculation/mds: Add mds_clear_cpu_buffers() x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests x86/speculation/mds: Add BUG_MSBDS_ONLY x86/speculation/mds: Add basic bug infrastructure for MDS x86/speculation: Consolidate CPU whitelists x86/msr-index: Cleanup bit defines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829652] Re: Kernel panic upon resetting ixgbe SR-IOV VFIO virtual function using 5.0 kernel
This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829652 Title: Kernel panic upon resetting ixgbe SR-IOV VFIO virtual function using 5.0 kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: [Impact] If you pass a vf of an intel 10G nic - such as the X550T - into a VM, and that nic does not support IPsec, the system will oops. [Test Case] Enable virtual functions (e.g. (class/net/em1/device/sriov_numvfs = 4). Use an XML snippet to delegate virtual function to VM, e.g.: Start VM. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue.git/commit/?h=dev-queue=a2243a4faae5a3c210995ade2cbca369b20daa0f [Regression Risk] Restricted to the ixgbe driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830815] Re: Hi1620 driver updates from upstream 5.2 merge window
This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830815 Title: Hi1620 driver updates from upstream 5.2 merge window Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: [Impact] Sync up the hns drivers with the 5.2 merge window. (Cut & paste from bug 1819535) Drivers for the HiSilicon Hi1620 SoC continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream. [Test Case] Validated by testing on the Hi1620-based D06 systems. These changes were staged in a PPA kernel that underwent testing w/ the Ubuntu certification test suite (Ubuntu certification is targeted for 18.04.3 HWE kernel). In addition, perftest was used to verify RDMA functionality and iperf was used to verify networking performance. [Regression Risk] Changes are restricted to drivers specific to the Hi1620 SoC, and tested on the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829046] Re: Eoan update: v5.1.1 upstream stable release
This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829046 Title: Eoan update: v5.1.1 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released 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: v5.1.1 upstream stable release from git://git.kernel.org/ Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings staging: greybus: power_supply: fix prop-descriptor request size staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. staging: most: cdev: fix chrdev_region leak in mod_exit staging: most: sound: pass correct device when creating a sound card usb: dwc3: Allow building USB_DWC3_QCOM without EXTCON usb: dwc3: Fix default lpm_nyet_threshold value USB: serial: f81232: fix interrupt worker not stop USB: cdc-acm: fix unthrottle races usb-storage: Set virt_boundary_mask to avoid SG overflows genirq: Prevent use-after-free and work list corruption intel_th: pci: Add Comet Lake support iio: adc: qcom-spmi-adc5: Fix of-based module autoloading cpufreq: armada-37xx: fix frequency calculation for opp ACPI / LPSS: Use acpi_lpss_* instead of acpi_subsys_* functions for hibernate soc: sunxi: Fix missing dependency on REGMAP_MMIO scsi: lpfc: change snprintf to scnprintf for possible overflow scsi: qla2xxx: Fix incorrect region-size setting in optrom SYSFS routines scsi: qla2xxx: Set remote port devloss timeout to 0 scsi: qla2xxx: Fix device staying in blocked state Bluetooth: hidp: fix buffer overflow Bluetooth: Align minimum encryption key size for LE and BR/EDR connections Bluetooth: Fix not initializing L2CAP tx_credits Bluetooth: hci_bcm: Fix empty regulator supplies for Intel Macs UAS: fix alignment of scatter/gather segments ASoC: Intel: avoid Oops if DMA setup fails i3c: Fix a shift wrap bug in i3c_bus_set_addr_slot_status() locking/futex: Allow low-level atomic operations to return -EAGAIN arm64: futex: Bound number of LDXR/STXR loops in FUTEX_WAKE_OP Linux 5.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832048] Re: hinic: fix oops due to race in set_rx_mode
This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832048 Title: hinic: fix oops due to race in set_rx_mode 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 Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: [Impact] It is possible for the hinic driver to oops after the module is removed and reinserted. [Test Case] while :; do sudo modprobe -r hinic; modprobe hinic; done [Fix] From linux-next: 66350023d5756 hinic: fix a bug in set rx mode [Regression Risk] Patch is local to the hinic driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833484] Re: Sometimes touchpad automatically trigger double click
This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833484 Title: Sometimes touchpad automatically trigger double click Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: New Bug description: [Impact] Dell machines which uses goodix touchpad IC emit double click event while touching the touchpad if designware i2c adapter is in runtime suspend. Goodix re-assert the interrupt if host doesn't read the data within 100ms and designware takes a longer time to wake up from runtime suspend. In the case, it got a second interrupt during resuming, so it thinks it's a double click. [Fix] There is no simple way to fix this, it's a firmware issue and goodix agrees to fix this in their firmware on next release, but this issue is still affects the machines that don't come with an updated firmware. So, add a quirk to mark those machines and avoid the designware from entering runtime suspend. [Regression Potential] Low, it only affects the listed machines, and prevent designware from entering runtime suspend impacts the power consumption little or none during short or long idle. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1833484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu Eoan) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Ready for Release phase-changed: Monday, 15. July 2019 22:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832316] Re: shiftfs: allow changing ro/rw for subvolumes
This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832316 Title: shiftfs: allow changing ro/rw for subvolumes Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: Stéphane reported regression for btrfs workloads employing shiftfs. Unprivileged users can already toggle whether a subvolume will be ro or rw. This is broken on current shiftfs as we haven't whitelisted these ioctls(). Fix: To enable this with shiftfs we need to whitelist BTRFS_IOC_FS_INFO, BTRFS_IOC_SUBVOL_GETFLAGS, BTRFS_IOC_SUBVOL_SETFLAGS. All of them should be safe for unprivileged users. Regression Potential: Limited to shiftfs. Test Case: Tested with LXD running shiftfs on top of btrfs and verified btrfs subvolumes can be made ro or rw. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833387] Re: Add pointstick support on HP ZBook 17 G5
This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1833387 Title: Add pointstick support on HP ZBook 17 G5 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Won't Fix Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Won't Fix Bug description: [Impact] Pointstick on HP ZBook 17 G5 doesn't work. [Fix] Let hid-multitouch know it has a pointstick, and exposes it as a mouse. [Test] With the fix applied the pointstick starts to work. [Regression Potential] Low. It's limited to one driver and limited to one specific device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1833387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834479] Re: depmod may prefer unsigned l-r-m nvidia modules to signed modules
This bug was fixed in the package linux - 5.2.0-8.9 --- linux (5.2.0-8.9) eoan; urgency=medium * linux: 5.2.0-8.9 -proposed tracker (LP: #1835700) * Miscellaneous Ubuntu changes - [Packaging] replace zfs and spl build with zfs 0.8.1-1ubuntu1 - SAUCE: test_bpf: remove expected fail for Ctx heavy transformations test on s390 - SAUCE: add -fcf-protection=none to retpoline flags - SAUCE: usbip: ensure strings copied using strncpy are null-terminated - SAUCE: usbip: add -Wno-address-of-packed-member to EXTRA_CFLAGS - SAUCE: perf jvmti: ensure strncpy result is null-terminated - update dkms package versions - add removed zfs modules to modules.ignore [ Upstream Kernel Changes ] * Rebase to v5.2 -- Seth Forshee Mon, 08 Jul 2019 07:13:41 -0500 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834479 Title: depmod may prefer unsigned l-r-m nvidia modules to signed modules Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Bug description: Impact: When testing patches for bug 1834476, a bug was observed whereby modprobe was someties attempting to load the unsigned nvidia modules in /lib/modules/$(uname -r)/kernel/nvidia-N/bits rather than the signed modules from /lib/modules/$(uname -r)/kernel/nvidia-N. This appears to be because depmod is not deterministic in which module will be preferred when duplicate modules of the same name exist. Fix: The unsigned modules are no longer needed after the signed modules have been generated, so update the build script to remove the unsigned modules. Test Case: Confirm that the ko files are found in /lib/modules/$(uname -r)/kernel/nvidia-N but not in /lib/modules/$(uname -r)/kernel/nvidia-N/bits. Confirm that the modules are signed and loadable by the kernel under lockdown (or when booted with modules.sig_enforce=y), and that modprobe consistently loads the modules from the expected path after depmod. Regression Potential: The modules being removed are an intermediate build artifact and not meant to be loaded, so no regressions are expected. However, if for some reason linking the intermediate unsigned module was successful but generation of the signed module was not, the user would have been left with a module that could potentially be loaded (if not booted under UEFI secure boot) and would now be left with no modules. This is not the intended behavior and never occurred in my testing, so it's not a case we should be concerned about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
I completely uninatalled tlp this morning and I am still experiencing this issue. I don't think it has anything to do with it. (As I mentioned previously, other bluetooth devices work alright, even with tlp). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in linux package in Ubuntu: Incomplete Status in tlp package in Ubuntu: Incomplete Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
THIS IS NOT A BUG. This is in TLP's FAQ : https://linrunner.de/en/tlp/docs/tlp-faq.html#btusb Please read the documentation, do what it says, confirm that your problem is fixed, and close the bug as 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/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in linux package in Ubuntu: Incomplete Status in tlp package in Ubuntu: Incomplete Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13
[Kernel-packages] [Bug 1836654] [NEW] Bionic update: upstream stable patchset 2019-07-15
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-07-15 Ported from the following upstream stable releases: v4.14.78, v4.18.16, v4.14.79, v4.18.17, v4.14.80, v4.18.18 from git://git.kernel.org/ media: af9035: prevent buffer overflow on write batman-adv: Avoid probe ELP information leak batman-adv: Fix segfault when writing to throughput_override batman-adv: Fix segfault when writing to sysfs elp_interval batman-adv: Prevent duplicated gateway_node entry batman-adv: Prevent duplicated nc_node entry batman-adv: Prevent duplicated softif_vlan entry batman-adv: Prevent duplicated global TT entry batman-adv: Prevent duplicated tvlv handler batman-adv: fix backbone_gw refcount on queue_work() failure batman-adv: fix hardif_neigh refcount on queue_work() failure clocksource/drivers/ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for non-am43 SoCs scsi: ibmvscsis: Fix a stringop-overflow warning scsi: ibmvscsis: Ensure partition name is properly NUL terminated intel_th: pci: Add Ice Lake PCH support Input: atakbd - fix Atari keymap Input: atakbd - fix Atari CapsLock behaviour net: emac: fix fixed-link setup for the RTL8363SB switch ravb: do not write 1 to reserved bits PCI: dwc: Fix scheduling while atomic issues drm: mali-dp: Call drm_crtc_vblank_reset on device init scsi: ipr: System hung while dlpar adding primary ipr adapter back scsi: sd: don't crash the host on invalid commands net/mlx4: Use cpumask_available for eq->affinity_mask clocksource/drivers/fttmr010: Fix set_next_event handler powerpc/tm: Fix userspace r13 corruption powerpc/tm: Avoid possible userspace r1 corruption on reclaim iommu/amd: Return devid as alias for ACPI HID devices ARC: build: Get rid of toolchain check ARC: build: Don't set CROSS_COMPILE in arch's Makefile HID: quirks: fix support for Apple Magic Keyboards staging: ccree: check DMA pool buf !NULL before free net/smc: fix sizeof to int comparison qed: Fix populating the invalid stag value in multi function mode. RDMA/uverbs: Fix validity check for modify QP bpf: test_maps, only support ESTABLISHED socks RDMA/bnxt_re: Fix system crash during RDMA resource initialization RISC-V: include linux/ftrace.h in asm-prototypes.h powerpc/numa: Use associativity if VPHN hcall is successful x86/boot: Fix kexec booting failure in the SEV bit detection code xfrm: Validate address prefix lengths in the xfrm selector. xfrm6: call kfree_skb when skb is toobig xfrm: reset transport header back to network header after all input transforms ahave been applied xfrm: reset crypto_done when iterating over multiple input xfrms mac80211: Always report TX status cfg80211: reg: Init wiphy_idx in regulatory_hint_core() mac80211: fix pending queue hang due to TX_DROP cfg80211: Address some corner cases in scan result channel updating mac80211: TDLS: fix skb queue/priority assignment mac80211: fix TX status reporting for ieee80211s ARM: 8799/1: mm: fix pci_ioremap_io() offset check xfrm: validate template mode netfilter: bridge: Don't sabotage nf_hook calls from an l3mdev arm64: hugetlb: Fix handling of young ptes ARM: dts: BCM63xx: Fix incorrect interrupt specifiers net: macb: Clean 64b dma addresses if they are not detected soc: fsl: qbman: qman: avoid allocating from non existing gen_pool soc: fsl: qe: Fix copy/paste bug in ucc_get_tdm_sync_shift() mac80211_hwsim: do not omit multicast announce of first added radio Bluetooth: SMP: fix crash in unpairing pxa168fb: prepare the clock qed: Avoid implicit enum conversion in qed_set_tunn_cls_info qed: Fix mask parameter in qed_vf_prep_tunn_req_tlv qed: Avoid implicit enum conversion in qed_roce_mode_to_flavor qed: Avoid constant logical operation warning in qed_vf_pf_acquire qed: Avoid implicit enum conversion in qed_iwarp_parse_rx_pkt asix: Check for supported Wake-on-LAN modes ax88179_178a: Check for supported Wake-on-LAN modes lan78xx: Check for supported Wake-on-LAN modes sr9800: Check for supported Wake-on-LAN modes r8152: Check for supported Wake-on-LAN Modes smsc75xx: Check for Wake-on-LAN modes smsc95xx: Check for Wake-on-LAN modes cfg80211: fix use-after-free in reg_process_hint() perf/core: Fix perf_pmu_unregister() locking perf/ring_buffer: Prevent concurent ring buffer access perf/x86/intel/uncore: Fix PCI BDF address of M3UPI on SKX perf/x86/amd/uncore: Set ThreadMask and SliceMask for L3 Cache perf events net: fec: fix rare tx timeout declance: Fix continuation with the adapter identification message locking/ww_mutex: Fix runtime warning in the WW
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-eoan ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - phase: Testing - phase-changed: Tuesday, 09. July 2019 22:34 UTC + phase: Ready for Release + phase-changed: Monday, 15. July 2019 22:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + promote-to-release: Pending -- ready to copy variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Ready for Release phase-changed: Monday, 15. July 2019 22:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828868] Re: crashdump fails on HiSilicon D06
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828868 Title: crashdump fails on HiSilicon D06 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 Status in linux source package in Disco: Fix Committed Bug description: [Impact] The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3 ARM systems. [Test Case] sudo apt install linux-crashdump Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as appropriate (for D06, crashkernel=512M) Add "arm_smmu_v3.disable_bypass=1" to the kernel command line sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger (Note to self - the following is needed on our systems w/ Mellanox adapters: ubuntu@d06-3:~$ grep blacklist /etc/default/kdump-tools KDUMP_CMDLINE_APPEND="nr_cpus=1 systemd.unit=kdump-tools-dump.service module_blacklist=mlx5_core") [Fix] 3f54c447df34f iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel [Regression Risk] Restricted to SMMUv3 arm64-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833140] Re: hns: fix ICMP6 neighbor solicitation messages discard problem
Smoke test successful on each release. ** Tags removed: verification-needed-bionic verification-needed-cosmic verification-needed-disco ** Tags added: verification-done-bionic verification-done-cosmic verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833140 Title: hns: fix ICMP6 neighbor solicitation messages discard problem 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 Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: In Progress Bug description: [Impact] ICMP6 neighbor solicitation messages are discarded. [Test Case] Regression tested only [Fix] ea401685a20b5 net: hns: fix unsigned comparison to less than zero f058e46855dcb net: hns: fix ICMP6 neighbor solicitation messages discard problem [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Testing phase-changed: Tuesday, 09. July 2019 22:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Testing phase-changed: Tuesday, 09. July 2019 22:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Testing phase-changed: Tuesday, 09. July 2019 22:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828868] Re: crashdump fails on HiSilicon D06
** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828868 Title: crashdump fails on HiSilicon D06 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 Status in linux source package in Disco: Fix Committed Bug description: [Impact] The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3 ARM systems. [Test Case] sudo apt install linux-crashdump Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as appropriate (for D06, crashkernel=512M) Add "arm_smmu_v3.disable_bypass=1" to the kernel command line sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger (Note to self - the following is needed on our systems w/ Mellanox adapters: ubuntu@d06-3:~$ grep blacklist /etc/default/kdump-tools KDUMP_CMDLINE_APPEND="nr_cpus=1 systemd.unit=kdump-tools-dump.service module_blacklist=mlx5_core") [Fix] 3f54c447df34f iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel [Regression Risk] Restricted to SMMUv3 arm64-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836635] Re: Bionic: support for Solarflare X2542 network adapter (sfc driver)
Regression test results/log/script,
for documentation purposes.
** Attachment added: "lp1836635-test-regression.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836635/+attachment/5277232/+files/lp1836635-test-regression.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836635
Title:
Bionic: support for Solarflare X2542 network adapter (sfc driver)
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
Invalid
Status in linux source package in Disco:
Invalid
Status in linux source package in Eoan:
Invalid
Bug description:
[Impact]
* Support for Solarflare X2542 network adapter
(Medford2 / SFC9250) in the Bionic sfc driver.
* This network adapter is present on recent hardware,
at least HP 2019 and Dell PowerEdge R740xd systems.
* On recent-hardware deployments that would rather use
the Bionic LTS / GA supported kernel and cannot move
to HWE kernels this adapter is non functional at all.
[Test Case]
* The X2542 adapter has been exercised with iperf3 and nc
across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000
on both directions, for 1 week.
Its performance is on par with the Cosmic 4.18 kernel
(which contains all these patches) and the out-of-tree
driver from the vendor.
* The 7000 series adapter (for regression testing an old model,
supported previously) has been exercised with iperf and netperf
(TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one
host (client/server in different adapter ports isolated with
network namespaces, so traffic goes through the network switch),
on 10G link speed on MTUs 1500/9000, for 1 weekend.
No regressions observed between the original and test kernels.
[Regression Potential]
* The patchset touches a lot of the sfc driver, so the potential
for regression definitely exists. Thus, a lot of consideration
and testing happened:
* It has been tested on other adapter which uses the old code,
and no regressions were found so far (see 7000 series above).
* The patchset is exclusively cherry-picks, no single backport.
* The patchset essentially moves the Bionic driver up in the
upstream 'git log --oneline -- drivers/net/ethernet/sfc/':
- since commit d4a7a8893d4c ("sfc: pass valid pointers from
efx_enqueue_unwind")
- until commit 7f61e6c6279b ("sfc: support FEC configuration through
ethtool")
- except for 2 commits (not needed / unrelated)
- commit 42356d9a137b ("sfc: support RSS spreading of ethtool ntuple
filters")
- commit 9baeb5eb1f83 ("sfc: falcon: remove duplicated bit-wise or of
LOOPBACK_SGMII")
- plus 2 more recent commits (fixes)
- commit 458bd99e4974 ("sfc: remove ctpio_dmabuf_start from stats")
- commit 0c235113b3c4 ("sfc: stop the TX queue before pushing new
buffers")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836635/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833147] Re: hns: attempt to restart autoneg when disabled should report error
verification = cosmic = ubuntu@d05-3:~$ cat /proc/version Linux version 4.18.0-26-generic (buildd@bos02-arm64-042) (gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1~18.10.1)) #27-Ubuntu SMP Tue Jul 2 15:36:34 UTC 2019 ubuntu@d05-3:~$ sudo ethtool -s enahisic2i1 autoneg off ubuntu@d05-3:~$ sudo ethtool -r enahisic2i1 Cannot restart autonegotiation: Invalid argument = bionic = ubuntu@d05-3:~$ cat /proc/version Linux version 4.15.0-55-generic (buildd@bos02-arm64-065) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #60-Ubuntu SMP Tue Jul 2 18:23:38 UTC 2019 ubuntu@d05-3:~$ sudo ethtool -s enahisic2i1 autoneg off ubuntu@d05-3:~$ sudo ethtool -r enahisic2i1 Cannot restart autonegotiation: Invalid argument ** Tags removed: verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833147 Title: hns: attempt to restart autoneg when disabled should report error 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 Committed Bug description: [Impact] Asking the driver to restart autonegotiation silently fails when autonegotation has been disabled. It should report an error. [Test Case] sudo ethtool -s ethX autoneg off sudo ethtool -r ethX [Fix] ed29ca8b95925 net: hns: Restart autoneg need return failed when autoneg off [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835279] Re: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open
** Attachment added: "4.15.0-54-generic #58+lp1835279 kernel log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+attachment/5277230/+files/kernel-arighi.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/1835279 Title: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc- kernel_240.snap Version signature: 4.15.0-54.58-generic 4.15.18 Issue is non-deterministic, and happens in roughly 20% of the attempts. Running on: qemu-kvm, command line: kvm \ -bios /usr/share/ovmf/OVMF.fd \ -smp 2 -m 512 -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,format=raw Commands that caused the problem: cryptsetup -q --type luks2 --key-file luksFormat /dev/sda4 LD_PRELOAD=/lib/no-udev.so cryptsetup --type luks2 --key-file open /dev/sda4 crypt-data Notes: - See https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1589083 for more information on the no-udev workaround. - The commands are scripted. Also tried to add a 200ms and 1s interval before opening the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835279] Re: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open
We're now opening the LUKS device using the master key directly and the crash is happening again in both the original 4.15.0-54-generic (buildd@lgw01-amd64-014) kernel or the patched 4.15.0-54-generic (arighi@kathleen) kernel. The backtrace is very similar but unlike the previous scenario it happens even if delays as large as 5000 ms are placed between partition table re-reading and commands. The LUKS device is created and accessed using the following commands: # cryptsetup -q luksFormat --type luks2 --pbkdf-memory 1 --master- key-file # LD_PRELOAD=/lib/no-udev.so cryptsetup open --master-key-file -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835279 Title: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc- kernel_240.snap Version signature: 4.15.0-54.58-generic 4.15.18 Issue is non-deterministic, and happens in roughly 20% of the attempts. Running on: qemu-kvm, command line: kvm \ -bios /usr/share/ovmf/OVMF.fd \ -smp 2 -m 512 -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,format=raw Commands that caused the problem: cryptsetup -q --type luks2 --key-file luksFormat /dev/sda4 LD_PRELOAD=/lib/no-udev.so cryptsetup --type luks2 --key-file open /dev/sda4 crypt-data Notes: - See https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1589083 for more information on the no-udev workaround. - The commands are scripted. Also tried to add a 200ms and 1s interval before opening the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836614] Re: Disco update: 5.0.18 upstream stable release
Commit "s390/mm: convert to the generic get_user_pages_fast code" implements a gup_fast_permitted() function which expects 2 arguments. However at that point the general mm code is using 3 arguments. This gets changed in 5.0.19 by "mm/gup: Remove the 'write' parameter from gup_fast_permitted()". To avoid breaking the build on s390x this one patch from 5.0.19 got moved into 5.0.18. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836614 Title: Disco update: 5.0.18 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.18 upstream stable release from git://git.kernel.org/ The following patches were applied: * locking/rwsem: Prevent decrement of reader count before increment * x86/speculation/mds: Revert CPU buffer clear on double fault exit * x86/speculation/mds: Improve CPU buffer clear documentation * objtool: Fix function fallthrough detection * arm64: dts: rockchip: fix IO domain voltage setting of APIO5 on rockpro64 * arm64: dts: rockchip: Disable DCMDs on RK3399's eMMC controller. * ARM: dts: qcom: ipq4019: enlarge PCIe BAR range * ARM: dts: exynos: Fix interrupt for shared EINTs on Exynos5260 * ARM: dts: exynos: Fix audio (microphone) routing on Odroid XU3 * mmc: sdhci-of-arasan: Add DTS property to disable DCMDs. * ARM: exynos: Fix a leaked reference by adding missing of_node_put * power: supply: axp288_charger: Fix unchecked return value * power: supply: axp288_fuel_gauge: Add ACEPC T8 and T11 mini PCs to the blacklist * arm64: mmap: Ensure file offset is treated as unsigned * arm64: arch_timer: Ensure counter register reads occur with seqlock held * arm64: compat: Reduce address limit * arm64: Clear OSDLR_EL1 on CPU boot * arm64: Save and restore OSDLR_EL1 across suspend/resume * sched/x86: Save [ER]FLAGS on context switch * x86/MCE: Add an MCE-record filtering function * x86/MCE/AMD: Turn off MC4_MISC thresholding on all family 0x15 models * x86/MCE/AMD: Carve out the MC4_MISC thresholding quirk * x86/MCE: Group AMD function prototypes in * x86/MCE/AMD: Don't report L1 BTB MCA errors on some family 17h models * crypto: crypto4xx - fix ctr-aes missing output IV * crypto: crypto4xx - fix cfb and ofb "overran dst buffer" issues * crypto: salsa20 - don't access already-freed walk.iv * crypto: lrw - don't access already-freed walk.iv * crypto: chacha-generic - fix use as arm64 no-NEON fallback * crypto: chacha20poly1305 - set cra_name correctly * crypto: ccp - Do not free psp_master when PLATFORM_INIT fails * crypto: vmx - fix copy-paste error in CTR mode * crypto: skcipher - don't WARN on unprocessed data after slow walk step * crypto: crct10dif-generic - fix use via crypto_shash_digest() * crypto: x86/crct10dif-pcl - fix use via crypto_shash_digest() * crypto: arm64/gcm-aes-ce - fix no-NEON fallback code * crypto: gcm - fix incompatibility between "gcm" and "gcm_base" * crypto: rockchip - update IV buffer to contain the next IV * crypto: caam/qi2 - fix zero-length buffer DMA mapping * crypto: caam/qi2 - fix DMA mapping of stack memory * crypto: caam/qi2 - generate hash keys in-place * crypto: arm/aes-neonbs - don't access already-freed walk.iv * crypto: arm64/aes-neonbs - don't access already-freed walk.iv * mmc: tegra: fix ddr signaling for non-ddr modes * mmc: core: Fix tag set memory leak * mmc: sdhci-pci: Fix BYT OCP setting * ALSA: line6: toneport: Fix broken usage of timer for delayed execution * ALSA: usb-audio: Fix a memory leak bug * ALSA: hda/realtek - EAPD turn on later * ASoC: max98090: Fix restore of DAPM Muxes * ASoC: RT5677-SPI: Disable 16Bit SPI Transfers * ASoC: fsl_esai: Fix missing break in switch statement * ASoC: codec: hdac_hdmi add device_link to card device * bpf, arm64: remove prefetch insn in xadd mapping * crypto: ccree - remove special handling of chained sg * crypto: ccree - fix mem leak on error path * crypto: ccree - don't map MAC key on stack * crypto: ccree - use correct internal state sizes for export * crypto: ccree - don't map AEAD key and IV on stack * crypto: ccree - pm resume first enable the source clk * crypto: ccree - HOST_POWER_DOWN_EN should be the last CC access during suspend * crypto: ccree - add function to handle cryptocell tee fips error * crypto:
[Kernel-packages] [Bug 1836635] Re: Bionic: support for Solarflare X2542 network adapter (sfc driver)
[Bionic][PULL] sfc: patches for LP#1836635
https://lists.ubuntu.com/archives/kernel-team/2019-July/102196.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/1836635
Title:
Bionic: support for Solarflare X2542 network adapter (sfc driver)
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
Invalid
Status in linux source package in Disco:
Invalid
Status in linux source package in Eoan:
Invalid
Bug description:
[Impact]
* Support for Solarflare X2542 network adapter
(Medford2 / SFC9250) in the Bionic sfc driver.
* This network adapter is present on recent hardware,
at least HP 2019 and Dell PowerEdge R740xd systems.
* On recent-hardware deployments that would rather use
the Bionic LTS / GA supported kernel and cannot move
to HWE kernels this adapter is non functional at all.
[Test Case]
* The X2542 adapter has been exercised with iperf3 and nc
across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000
on both directions, for 1 week.
Its performance is on par with the Cosmic 4.18 kernel
(which contains all these patches) and the out-of-tree
driver from the vendor.
* The 7000 series adapter (for regression testing an old model,
supported previously) has been exercised with iperf and netperf
(TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one
host (client/server in different adapter ports isolated with
network namespaces, so traffic goes through the network switch),
on 10G link speed on MTUs 1500/9000, for 1 weekend.
No regressions observed between the original and test kernels.
[Regression Potential]
* The patchset touches a lot of the sfc driver, so the potential
for regression definitely exists. Thus, a lot of consideration
and testing happened:
* It has been tested on other adapter which uses the old code,
and no regressions were found so far (see 7000 series above).
* The patchset is exclusively cherry-picks, no single backport.
* The patchset essentially moves the Bionic driver up in the
upstream 'git log --oneline -- drivers/net/ethernet/sfc/':
- since commit d4a7a8893d4c ("sfc: pass valid pointers from
efx_enqueue_unwind")
- until commit 7f61e6c6279b ("sfc: support FEC configuration through
ethtool")
- except for 2 commits (not needed / unrelated)
- commit 42356d9a137b ("sfc: support RSS spreading of ethtool ntuple
filters")
- commit 9baeb5eb1f83 ("sfc: falcon: remove duplicated bit-wise or of
LOOPBACK_SGMII")
- plus 2 more recent commits (fixes)
- commit 458bd99e4974 ("sfc: remove ctpio_dmabuf_start from stats")
- commit 0c235113b3c4 ("sfc: stop the TX queue before pushing new
buffers")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836635/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836635] Re: Bionic: support for Solarflare X2542 network adapter (sfc driver)
** Description changed:
[Impact]
- * Support for Solarflare X2542 network adapter
-(Medford2 / SFC9250) in the sfc driver.
+ * Support for Solarflare X2542 network adapter
+ (Medford2 / SFC9250) in the sfc driver.
- * This network adapter is present on recent hardware,
-at least HP 2019 and Dell PowerEdge R740xd systems.
+ * This network adapter is present on recent hardware,
+ at least HP 2019 and Dell PowerEdge R740xd systems.
- * On recent-hardware deployments that would rather use
-the Bionic LTS / GA supported kernel and cannot move
-to HWE kernels this adapter is non functional at all.
+ * On recent-hardware deployments that would rather use
+ the Bionic LTS / GA supported kernel and cannot move
+ to HWE kernels this adapter is non functional at all.
[Test Case]
- * The X2542 adapter has been exercised with iperf3 and nc
-across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000
-on both directions, for 1 week.
+ * The X2542 adapter has been exercised with iperf3 and nc
+ across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000
+ on both directions, for 1 week.
-Its performance is on par with the Cosmic 4.18 kernel
-(which contains all these patches) and the out-of-tree
-driver from the vendor.
+ Its performance is on par with the Cosmic 4.18 kernel
+ (which contains all these patches) and the out-of-tree
+ driver from the vendor.
- * The 7000 series adapter (for regression testing an old model,
-supported previously) has been exercised with iperf and netperf
-(TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one
-host (client/server in different adapter ports isolated with
-network namespaces, so traffic goes through the network switch),
-on 10G link speed on MTUs 1500/9000, for 1 weekend.
+ * The 7000 series adapter (for regression testing an old model,
+ supported previously) has been exercised with iperf and netperf
+ (TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one
+ host (client/server in different adapter ports isolated with
+ network namespaces, so traffic goes through the network switch),
+ on 10G link speed on MTUs 1500/9000, for 1 weekend.
-No regressions observed between the original and test kernels.
+ No regressions observed between the original and test kernels.
[Regression Potential]
* The patchset touches a lot of the sfc driver, so the potential
-for regression definitely exists. It has been tested on other
-adapter which uses the old code, and no regressions were found.
+for regression definitely exists. Thus, a lot of consideration
+and testing happened:
+
+ * It has been tested on other adapter which uses the old code,
+and no regressions were found so far (see 7000 series above).
+
+ * The patchset essentially moves the driver in Bionic up in the
+upstream 'git log':
+- since commit d4a7a8893d4c ("sfc: pass valid pointers from
efx_enqueue_unwind")
+- until commit 7f61e6c6279b ("sfc: support FEC configuration through
ethtool")
+- except for 2 commits (not needed / unrelated)
+ - commit 42356d9a137b ("sfc: support RSS spreading of ethtool ntuple
filters")
+ - commit 9baeb5eb1f83 ("sfc: falcon: remove duplicated bit-wise or of
LOOPBACK_SGMII")
+- plus 2 more recent commits (fixes)
+ - commit 458bd99e4974 ("sfc: remove ctpio_dmabuf_start from stats")
+ - commit 0c235113b3c4 ("sfc: stop the TX queue before pushing new
buffers")
+
+ * The patchset is exclusively cherry-picks, no single backport.
** Description changed:
[Impact]
* Support for Solarflare X2542 network adapter
(Medford2 / SFC9250) in the sfc driver.
* This network adapter is present on recent hardware,
at least HP 2019 and Dell PowerEdge R740xd systems.
* On recent-hardware deployments that would rather use
the Bionic LTS / GA supported kernel and cannot move
to HWE kernels this adapter is non functional at all.
[Test Case]
* The X2542 adapter has been exercised with iperf3 and nc
across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000
on both directions, for 1 week.
Its performance is on par with the Cosmic 4.18 kernel
(which contains all these patches) and the out-of-tree
driver from the vendor.
* The 7000 series adapter (for regression testing an old model,
supported previously) has been exercised with iperf and netperf
(TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one
host (client/server in different adapter ports isolated with
network namespaces, so traffic goes through the network switch),
on 10G link speed on MTUs 1500/9000, for 1 weekend.
No regressions observed between the original and test kernels.
[Regression Potential]
- * The patchset touches a lot of the sfc driver, so the potential
-for regression definitely exists. Thus, a
[Kernel-packages] [Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10
** Changed in: linux (Ubuntu Disco) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => Triaged ** Also affects: linux via https://bugs.freedesktop.org/show_bug.cgi?id=110604 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826691 Title: fwupd hangs after 19.04 upgrade from 18.10 Status in Linux: Unknown Status in fwupd package in Ubuntu: Triaged Status in linux package in Ubuntu: Triaged Status in fwupd source package in Disco: Triaged Status in linux source package in Disco: Triaged Status in fwupd source package in Eoan: Triaged Status in linux source package in Eoan: Triaged Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 Being a firmware updater, the machine is probably relevant - Dell 7730. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt policy fwupd fwupd: Installed: (none) Candidate: 1.2.5-1ubuntu1 Version table: 1.2.5-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected few/no issues after 19.04 upgrade. The fwupd process worked perfectly in 18.10. It's upgraded the firmware on my laptop twice since I installed 18.10. 4) What happened instead After upgrading from 18.10 to 19.04 I had an issues that when I tried to suspend my laptop using the same button press as previous, the laptop would be hot and screen flickering when I returned to reopen it. I thought there were power management issues in the upgrade, but I've traced it to fwupd not letting the PM suspend process complete (see dmesg below). I tried shutting down the fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr commands timeout. Thinking something might have broken in the upgrade, I tried uninstalling (purge) the fwupd package and reinstalling. Starting the process with systemctl hangs forever like stopping it. Trying to kill -9 the process does not work - in uninterruptible sleep (D). This crash is probably related. It happened a couple of ours before I tried to put it to sleep the last time before uninstalling fwupd. Apr 23 19:29:14 texas kernel: [ 133.673290] [drm] REG_WAIT timeout 10us * 160 tries - submit_channel_request line:246 Apr 23 19:29:14 texas kernel: [ 133.673348] WARNING: CPU: 6 PID: 2467 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 generic_reg_wait.cold.3+0x25/0x2c [amdgpu] Apr 23 19:29:14 texas kernel: [ 133.673349] Modules linked in: thunderbolt rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common Apr 23 19:29:14 texas kernel: [ 133.673362] ledtrig_audio vfio_iommu_type1 videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone dell_smo8800 acpi_pad intel_hid int3400_thermal mac_hid acpi_thermal_rel sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic rtsx_pci_sdmmc nvme e1000e i2c_i801 intel_lpss_pci rtsx_pci nvme_core intel_lpss i2c_hid wmi hid video pinctrl_cannonlake pinctrl_intel Apr 23 19:29:14 texas kernel: [
[Kernel-packages] [Bug 1836630] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277212/+files/WifiSyslog.txt ** Changed in: linux-hwe-edge (Ubuntu) Status: New => 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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277201/+files/IwConfig.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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277210/+files/RfKill.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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277206/+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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277211/+files/UdevDb.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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277199/+files/CRDA.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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277205/+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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277203/+files/Lsusb.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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277200/+files/CurrentDmesg.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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277209/+files/PulseList.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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277202/+files/Lspci.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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277207/+files/ProcInterrupts.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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277204/+files/ProcCpuinfo.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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277208/+files/ProcModules.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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
apport information ** Also affects: linux-hwe-edge (Ubuntu) Importance: Undecided Status: New ** Tags added: apport-collected bionic ** Description changed: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: system76 1721 F pulseaudio + /dev/snd/controlC0: system76 1721 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + MachineType: System76 Oryx Pro + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux-hwe-edge + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro + ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-21-generic N/A + linux-backports-modules-5.0.0-21-generic N/A + linux-firmware1.173.9 + Tags: bionic + Uname: Linux 5.0.0-21-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm sudo + _MarkForUpload: True + dmi.bios.date: 05/07/2019 + dmi.bios.vendor: INSYDE Corp. + dmi.bios.version: 1.07.08 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: Oryx Pro + dmi.board.vendor: System76 + dmi.board.version: oryp5 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: System76 + dmi.chassis.version: oryp5 + dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: + dmi.product.family: Not Applicable + dmi.product.name: Oryx Pro + dmi.product.sku: Not Applicable + dmi.product.version: oryp5 + dmi.sys.vendor: System76 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1836630/+attachment/5277198/+files/AlsaInfo.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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias:
[Kernel-packages] [Bug 1836635] [NEW] Bionic: support for Solarflare X2542 network adapter (sfc driver)
Public bug reported: [Impact] * Support for Solarflare X2542 network adapter (Medford2 / SFC9250) in the sfc driver. * This network adapter is present on recent hardware, at least HP 2019 and Dell PowerEdge R740xd systems. * On recent-hardware deployments that would rather use the Bionic LTS / GA supported kernel and cannot move to HWE kernels this adapter is non functional at all. [Test Case] * The X2542 adapter has been exercised with iperf3 and nc across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000 on both directions, for 1 week. Its performance is on par with the Cosmic 4.18 kernel (which contains all these patches) and the out-of-tree driver from the vendor. * The 7000 series adapter (for regression testing an old model, supported previously) has been exercised with iperf and netperf (TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one host (client/server in different adapter ports isolated with network namespaces, so traffic goes through the network switch), on 10G link speed on MTUs 1500/9000, for 1 weekend. No regressions observed between the original and test kernels. [Regression Potential] * The patchset touches a lot of the sfc driver, so the potential for regression definitely exists. It has been tested on other adapter which uses the old code, and no regressions were found. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Mauricio Faria de Oliveira (mfo) Status: In Progress ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: linux (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux (Ubuntu Disco) Status: New => Invalid ** Changed in: linux (Ubuntu Eoan) 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/1836635 Title: Bionic: support for Solarflare X2542 network adapter (sfc driver) Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: Invalid Status in linux source package in Eoan: Invalid Bug description: [Impact] * Support for Solarflare X2542 network adapter (Medford2 / SFC9250) in the sfc driver. * This network adapter is present on recent hardware, at least HP 2019 and Dell PowerEdge R740xd systems. * On recent-hardware deployments that would rather use the Bionic LTS / GA supported kernel and cannot move to HWE kernels this adapter is non functional at all. [Test Case] * The X2542 adapter has been exercised with iperf3 and nc across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000 on both directions, for 1 week. Its performance is on par with the Cosmic 4.18 kernel (which contains all these patches) and the out-of-tree driver from the vendor. * The 7000 series adapter (for regression testing an old model, supported previously) has been exercised with iperf and netperf (TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one host (client/server in different adapter ports isolated with network namespaces, so traffic goes through the network switch), on 10G link speed on MTUs 1500/9000, for 1 weekend. No regressions observed between the original and test kernels. [Regression Potential] * The patchset touches a lot of the sfc driver, so the potential for regression definitely exists. It has been tested on other adapter which uses the old code, and no regressions were found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] 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 1836630 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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] [NEW] System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
Public bug reported: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. ** 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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in linux package in Ubuntu: New Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835891] Re: [wishlist] CONFIG_XFRM_MIGRATE=y
** 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/1835891 Title: [wishlist] CONFIG_XFRM_MIGRATE=y Status in libreswan package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This is a new feature request, Ubuntu linux, kernel, package. Description: Ubuntu 18.04.1 LTS Release: 18.04 Ubuntu 4.15.0-36.39-generic 4.15.18 I am adding version information from bionic, it would be nice to be fixed in the next possible version. Please enable CONFIG_XFRM_MIGRATE=y in kernel config to supoort IKE (IPsec mobike). Libreswan use this kernel feature to support MOBIKE RFC 4555. conn iphone-psk mobike=yes Error meesage: ipsec auto --add iphone-psk 036 MOBIKE kernel support missing for netkey interface: CONFIG_XFRM_MIGRATE && CONFIG_NET_KEY_MIGRATE FYI: CONFIG_XFRM_MIGRATE=y in Debian Buster and RHEL, Fedora. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreswan/+bug/1835891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836211] Re: bcmwl fails to install with recent Eoan (Bad return status for module build on kernel: 5.0.0-20-generic)
I am facing this same issue. Wifi not found and the driver wont compile. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1836211 Title: bcmwl fails to install with recent Eoan (Bad return status for module build on kernel: 5.0.0-20-generic) Status in bcmwl package in Ubuntu: New Bug description: With recent Eoan builds, bcmwl fails to install completely, . It had worked when I installed Eoan a couple weeks ago, but not when I first tried to clean install on 9 July until today. (I've unfortunately erased the old, working installation so I don't have more details.) $ sudo apt install bcmwl-kernel-source Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: dkms Suggested packages: menu The following NEW packages will be installed: bcmwl-kernel-source dkms 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 1,610 kB of archives. After this operation, 8,359 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 dkms all 2.7.1-1ubuntu1 [66.5 kB] Get:2 http://us.archive.ubuntu.com/ubuntu eoan/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu5 [1,544 kB] Fetched 1,610 kB in 0s (4,097 kB/s) Selecting previously unselected package dkms. (Reading database ... 122315 files and directories currently installed.) Preparing to unpack .../dkms_2.7.1-1ubuntu1_all.deb ... Unpacking dkms (2.7.1-1ubuntu1) ... Selecting previously unselected package bcmwl-kernel-source. Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu5_amd64.deb ... Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Setting up dkms (2.7.1-1ubuntu1) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.0.0-20-generic Building for architecture x86_64 Building initial module for 5.0.0-20-generic Error! Bad return status for module build on kernel: 5.0.0-20-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Processing triggers for man-db (2.8.5-2) ... Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 11 09:02:53 2019 InstallationDate: Installed on 2019-07-11 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1836211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836622] Re: Eoan update: v5.2.1 upstream stable release
** Changed in: linux (Ubuntu Eoan) 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/1836622 Title: Eoan update: v5.2.1 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Committed 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: v5.2.1 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836622] [NEW] Eoan update: v5.2.1 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: v5.2.1 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836622 Title: Eoan update: v5.2.1 upstream stable release Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.2.1 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836153] Re: [18.04 FEAT] zKVM: Add hardware CPU Model - kernel part
** Description changed: + SRU Justification: + == + + [Impact] + + * New hardware is not supported by qemu and won't run run, due to + missing hardware CPU model + + [Fix] + + * 11ba5961a2156a4f210627ed8421387e2531b100 11ba596 "KVM: s390: add debug + logging for cpu model subfunctions" + + * 346fa2f891c71a9b98014f8f62c15f4c7dd95ec1 346fa2f "KVM: s390: implement + subfunction processor calls" + + * 7832e91cd33f21f3cf82b003478c292915a1ec14 7832e91 "KVM: s390: add + vector enhancements facility 2 to cpumodel" + + * d5cb6ab1e3d4d7e0648a167f6290e89f6e86964e d5cb6ab "KVM: s390: add + vector BCD enhancements facility to cpumodel" + + * 13209ad0395c4de7fa48108b1dac72e341d5c089 13209ad "KVM: s390: add MSA9 + to cpumodel" + + * d668139718a9e2260702777bd8d86d71c30b6539 d668139 "KVM: s390: provide + query function for instructions returning 32 byte" + + * 173aec2d5a9fa5f40e462661a8283fcafe04764f 173aec2 "KVM: s390: add + enhanced sort facilty to cpu model" + + * 4f45b90e1c03466202fca7f62eaf32243f220830 4f45b90 "KVM: s390: add + deflate conversion facilty to cpu model" + + * 8ec2fa52eac53bff7ef1cedbc4ad8af650ec937c 8ec2fa5 "KVM: s390: enable + MSA9 keywrapping functions depending on cpu model" + + [Test Case] + + * need to be tested by IBM on pre-rel. hardware or simulator + + [Regression Potential] + + * The regression potential can be considered as low since these changes + are limited to arch/s390 + + * changes are in support for new and upcoming hardware and shouldn't + affect existing s390x systems + + [Other Info] + + * the first 2 commits are the key ones, the other 7 are needed to make + them applly cleanly + + * these patches are already all included in upstream kernel 5.2, hence + they are in eoan's kernel 5.2 + + * qemu package SRU in LP 1836154 complements this SRU - for testing both + need to be in place + + * I could apply the commit IDs cleanly with 'cherry-picks --strategy=recursive -X theirs' and checked that no patches on top were pulled in + _ + Feature request to be applied to Ubuntu 18.04 - kernel. - The git commit information is already provided within + The git commit information is already provided within https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830239 Once this feature is accepted all information for integration will be provided by IBM kernel 5.2 down to 4.15. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836153 Title: [18.04 FEAT] zKVM: Add hardware CPU Model - kernel part Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: SRU Justification: == [Impact] * New hardware is not supported by qemu and won't run run, due to missing hardware CPU model [Fix] * 11ba5961a2156a4f210627ed8421387e2531b100 11ba596 "KVM: s390: add debug logging for cpu model subfunctions" * 346fa2f891c71a9b98014f8f62c15f4c7dd95ec1 346fa2f "KVM: s390: implement subfunction processor calls" * 7832e91cd33f21f3cf82b003478c292915a1ec14 7832e91 "KVM: s390: add vector enhancements facility 2 to cpumodel" * d5cb6ab1e3d4d7e0648a167f6290e89f6e86964e d5cb6ab "KVM: s390: add vector BCD enhancements facility to cpumodel" * 13209ad0395c4de7fa48108b1dac72e341d5c089 13209ad "KVM: s390: add MSA9 to cpumodel" * d668139718a9e2260702777bd8d86d71c30b6539 d668139 "KVM: s390: provide query function for instructions returning 32 byte" * 173aec2d5a9fa5f40e462661a8283fcafe04764f 173aec2 "KVM: s390: add enhanced sort facilty to cpu model" * 4f45b90e1c03466202fca7f62eaf32243f220830 4f45b90 "KVM: s390: add deflate conversion facilty to cpu model" * 8ec2fa52eac53bff7ef1cedbc4ad8af650ec937c 8ec2fa5 "KVM: s390: enable MSA9 keywrapping functions depending on cpu model" [Test Case] * need to be tested by IBM on pre-rel. hardware or simulator [Regression Potential] * The regression potential can be considered as low since these changes are limited to arch/s390 * changes are in support for new and upcoming hardware and shouldn't affect existing s390x systems [Other Info] * the first 2 commits are the key ones, the other 7 are needed to make them applly cleanly * these patches are already all included in upstream kernel 5.2, hence they are in eoan's kernel 5.2 * qemu package SRU in LP 1836154 complements this SRU - for testing both need to be in place * I could apply the commit IDs cleanly with 'cherry-picks --strategy=recursive -X theirs' and checked that no patches on top were pulled in _ Feature request to be applied to Ubuntu 18.04 - kernel. The git commit information is already provided within https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830239 Once this feature is accepted all information for integration will be provided by IBM
[Kernel-packages] [Bug 1767992] Re: Linux md raid-10 freezes during resync
Kernel from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767992/comments/8 solved my issues. For reproduce on 4.15.0-50-generic Make new raid-10, add some io fio/dd, unpack anaconda archives(lol), after minute or two deadlocked [Mon Jul 15 19:31:11 2019] Workqueue: md md_submit_flush_data [Mon Jul 15 19:31:11 2019] Call Trace: [Mon Jul 15 19:31:11 2019] __schedule+0x291/0x8a0 [Mon Jul 15 19:31:11 2019] ? __switch_to_asm+0x34/0x70 [Mon Jul 15 19:31:11 2019] ? __switch_to_asm+0x40/0x70 [Mon Jul 15 19:31:11 2019] schedule+0x2c/0x80 [Mon Jul 15 19:31:11 2019] wait_barrier+0x146/0x1a0 [raid10] [Mon Jul 15 19:31:11 2019] ? wait_woken+0x80/0x80 [Mon Jul 15 19:31:11 2019] raid10_write_request+0x77/0x950 [raid10] [Mon Jul 15 19:31:11 2019] ? r10bio_pool_alloc+0x24/0x30 [raid10] [Mon Jul 15 19:31:11 2019] ? mempool_alloc+0x71/0x190 [Mon Jul 15 19:31:11 2019] ? md_write_start+0xf4/0x210 [Mon Jul 15 19:31:11 2019] ? default_wake_function+0x12/0x20 [Mon Jul 15 19:31:11 2019] ? autoremove_wake_function+0x12/0x40 [Mon Jul 15 19:31:11 2019] raid10_make_request+0xcc/0x140 [raid10] [Mon Jul 15 19:31:11 2019] md_handle_request+0x126/0x1a0 [Mon Jul 15 19:31:11 2019] md_submit_flush_data+0x54/0x70 [Mon Jul 15 19:31:11 2019] process_one_work+0x1de/0x410 [Mon Jul 15 19:31:11 2019] worker_thread+0x32/0x410 [Mon Jul 15 19:31:11 2019] kthread+0x121/0x140 [Mon Jul 15 19:31:11 2019] ? process_one_work+0x410/0x410 [Mon Jul 15 19:31:11 2019] ? kthread_create_worker_on_cpu+0x70/0x70 [Mon Jul 15 19:31:11 2019] ret_from_fork+0x35/0x40 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767992 Title: Linux md raid-10 freezes during resync Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: I'm trying to setup a few nodes with software raid-10. When array is created and resync is running i'm trying to install a few packages and frequently system stops responding, resync process stops, and I'm getting following errors in the kernel log. This looks like a deadlock for me. I had this problem in both 18.04 and 16.04. Reboot is the only way to fix the node. [ 2659.317256] INFO: task kworker/u24:13:343 blocked for more than 120 seconds. [ 2659.317313] Not tainted 4.15.0-20-generic #21-Ubuntu [ 2659.317350] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2659.317401] kworker/u24:13 D0 343 2 0x8000 [ 2659.317414] Workqueue: writeback wb_workfn (flush-9:1) [ 2659.317417] Call Trace: [ 2659.317430] __schedule+0x297/0x8b0 [ 2659.317435] schedule+0x2c/0x80 [ 2659.317443] wait_barrier+0x146/0x1a0 [raid10] [ 2659.317449] ? wait_woken+0x80/0x80 [ 2659.317454] raid10_write_request+0x77/0x950 [raid10] [ 2659.317459] ? r10bio_pool_alloc+0x24/0x30 [raid10] [ 2659.317465] ? mempool_alloc+0x71/0x190 [ 2659.317469] ? ___slab_alloc+0x20a/0x4b0 [ 2659.317475] ? md_write_start+0xc8/0x200 [ 2659.317480] ? mempool_alloc_slab+0x15/0x20 [ 2659.317484] raid10_make_request+0xcc/0x140 [raid10] [ 2659.317489] md_handle_request+0x126/0x1a0 [ 2659.317494] md_make_request+0x6b/0x150 [ 2659.317501] generic_make_request+0x124/0x300 [ 2659.317506] submit_bio+0x73/0x150 [ 2659.317510] ? submit_bio+0x73/0x150 [ 2659.317579] xfs_submit_ioend+0x87/0x1c0 [xfs] [ 2659.317626] xfs_do_writepage+0x377/0x6a0 [xfs] [ 2659.317632] write_cache_pages+0x20c/0x4e0 [ 2659.317674] ? xfs_vm_writepages+0xf0/0xf0 [xfs] [ 2659.317682] ? intel_pstate_update_pstate+0x40/0x40 [ 2659.317687] ? update_load_avg+0x5c5/0x6e0 [ 2659.317727] xfs_vm_writepages+0xbe/0xf0 [xfs] [ 2659.317732] do_writepages+0x4b/0xe0 [ 2659.317738] ? check_preempt_curr+0x83/0x90 [ 2659.317742] ? ttwu_do_wakeup+0x1e/0x150 [ 2659.317746] __writeback_single_inode+0x45/0x340 [ 2659.317749] ? __writeback_single_inode+0x45/0x340 [ 2659.317752] writeback_sb_inodes+0x1e1/0x510 [ 2659.317756] __writeback_inodes_wb+0x67/0xb0 [ 2659.317759] wb_writeback+0x271/0x300 [ 2659.317764] wb_workfn+0x180/0x410 [ 2659.317766] ? wb_workfn+0x180/0x410 [ 2659.317773] process_one_work+0x1de/0x410 [ 2659.317776] worker_thread+0x32/0x410 [ 2659.317781] kthread+0x121/0x140 [ 2659.317784] ? process_one_work+0x410/0x410 [ 2659.317788] ? kthread_create_worker_on_cpu+0x70/0x70 [ 2659.317793] ? do_syscall_64+0x73/0x130 [ 2659.317797] ? SyS_exit_group+0x14/0x20 [ 2659.317801] ret_from_fork+0x35/0x40 [ 2659.317806] INFO: task md1_resync:429 blocked for more than 120 seconds. [ 2659.317853] Not tainted 4.15.0-20-generic #21-Ubuntu [ 2659.317889] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2659.317940] md1_resync D0 429 2 0x8000 [ 2659.317943] Call Trace: [ 2659.317949]
[Kernel-packages] [Bug 1836614] Re: Disco update: 5.0.18 upstream stable release
Already applied for bug #1827967: - "ALSA: hda/hdmi - Read the pin sense from register when repolling" - "ALSA: hda/hdmi - Consider eld_valid when reporting jack event" Already applied for bug #1827555: - "ALSA: hda/realtek - Headset fixup for System76 Gazelle (gaze14)" - "ALSA: hda/realtek - Corrected fixup for System76 Gazelle (gaze14)" Already applied for CVE-2019-11833: - "ext4: zero out the unused memory region in the extent tree block" Already applied for bug #1828798: - "ALSA: hda/realtek - Fixup headphone noise via runtime suspend" ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11833 ** 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: + 5.0.18 upstream stable release + from git://git.kernel.org/ -5.0.18 upstream stable release -from git://git.kernel.org/ + The following patches were applied: + * locking/rwsem: Prevent decrement of reader count before increment + * x86/speculation/mds: Revert CPU buffer clear on double fault exit + * x86/speculation/mds: Improve CPU buffer clear documentation + * objtool: Fix function fallthrough detection + * arm64: dts: rockchip: fix IO domain voltage setting of APIO5 on rockpro64 + * arm64: dts: rockchip: Disable DCMDs on RK3399's eMMC controller. + * ARM: dts: qcom: ipq4019: enlarge PCIe BAR range + * ARM: dts: exynos: Fix interrupt for shared EINTs on Exynos5260 + * ARM: dts: exynos: Fix audio (microphone) routing on Odroid XU3 + * mmc: sdhci-of-arasan: Add DTS property to disable DCMDs. + * ARM: exynos: Fix a leaked reference by adding missing of_node_put + * power: supply: axp288_charger: Fix unchecked return value + * power: supply: axp288_fuel_gauge: Add ACEPC T8 and T11 mini PCs to the blacklist + * arm64: mmap: Ensure file offset is treated as unsigned + * arm64: arch_timer: Ensure counter register reads occur with seqlock held + * arm64: compat: Reduce address limit + * arm64: Clear OSDLR_EL1 on CPU boot + * arm64: Save and restore OSDLR_EL1 across suspend/resume + * sched/x86: Save [ER]FLAGS on context switch + * x86/MCE: Add an MCE-record filtering function + * x86/MCE/AMD: Turn off MC4_MISC thresholding on all family 0x15 models + * x86/MCE/AMD: Carve out the MC4_MISC thresholding quirk + * x86/MCE: Group AMD function prototypes in + * x86/MCE/AMD: Don't report L1 BTB MCA errors on some family 17h models + * crypto: crypto4xx - fix ctr-aes missing output IV + * crypto: crypto4xx - fix cfb and ofb "overran dst buffer" issues + * crypto: salsa20 - don't access already-freed walk.iv + * crypto: lrw - don't access already-freed walk.iv + * crypto: chacha-generic - fix use as arm64 no-NEON fallback + * crypto: chacha20poly1305 - set cra_name correctly + * crypto: ccp - Do not free psp_master when PLATFORM_INIT fails + * crypto: vmx - fix copy-paste error in CTR mode + * crypto: skcipher - don't WARN on unprocessed data after slow walk step + * crypto: crct10dif-generic - fix use via crypto_shash_digest() + * crypto: x86/crct10dif-pcl - fix use via crypto_shash_digest() + * crypto: arm64/gcm-aes-ce - fix no-NEON fallback code + * crypto: gcm - fix incompatibility between "gcm" and "gcm_base" + * crypto: rockchip - update IV buffer to contain the next IV + * crypto: caam/qi2 - fix zero-length buffer DMA mapping + * crypto: caam/qi2 - fix DMA mapping of stack memory + * crypto: caam/qi2 - generate hash keys in-place + * crypto: arm/aes-neonbs - don't access already-freed walk.iv + * crypto: arm64/aes-neonbs - don't access already-freed walk.iv + * mmc: tegra: fix ddr signaling for non-ddr modes + * mmc: core: Fix tag set memory leak + * mmc: sdhci-pci: Fix BYT OCP setting + * ALSA: line6: toneport: Fix broken usage of timer for delayed execution + * ALSA: usb-audio: Fix a memory leak bug + * ALSA: hda/realtek - EAPD turn on later + * ASoC: max98090: Fix restore of DAPM Muxes + * ASoC: RT5677-SPI: Disable 16Bit SPI Transfers + * ASoC: fsl_esai: Fix missing break in switch statement + * ASoC: codec: hdac_hdmi add device_link to card device + * bpf, arm64: remove prefetch insn in xadd mapping + * crypto: ccree -
[Kernel-packages] [Bug 1836614] [NEW] Disco update: 5.0.18 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: 5.0.18 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Disco) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Stefan Bader (smb) ** 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/1836614 Title: Disco update: 5.0.18 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.18 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
Subscribing kernel team. Also, posting the difference between the kernel configurations for reference so that you can see exactly why I believe it's a hardware issue. This issue you're reporting has been reported very few times, which is why I believe there is hardware commonality and might be related to the video driver. For instance, I have issues with stuttering on my AMD video unless I add the following kernel options: radeon.cik_support=0 radeon.si_support=0 amdgpu.dc=1 amdgpu.cik_support=1 amdgpu.si_support=1 amdgpu.dpm=0 amdgpu.gpu_recovery=1 Here's the configuration file differences, which you'll find are VERY minimal: --- /home/erich/Desktop/config-5.0.0-20-generic +++ /home/erich/Desktop/config-5.0.0-20-lowlatency @@ -1,6 +1,6 @@ # # Automatically generated file; DO NOT EDIT. -# Linux/x86 5.0.0-20-generic Kernel Configuration +# Linux/x86 5.0.0-20-lowlatency Kernel Configuration # # @@ -35,7 +35,7 @@ # CONFIG_KERNEL_LZO is not set # CONFIG_KERNEL_LZ4 is not set CONFIG_DEFAULT_HOSTNAME="(none)" -CONFIG_VERSION_SIGNATURE="Ubuntu 5.0.0-20.21-generic 5.0.8" +CONFIG_VERSION_SIGNATURE="Ubuntu 5.0.0-20.21-lowlatency 5.0.8" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y @@ -63,7 +63,7 @@ CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=y CONFIG_GENERIC_IRQ_RESERVATION_MODE=y CONFIG_IRQ_FORCED_THREADING=y -# CONFIG_IRQ_FORCED_THREADING_DEFAULT is not set +CONFIG_IRQ_FORCED_THREADING_DEFAULT=y CONFIG_SPARSE_IRQ=y # CONFIG_GENERIC_IRQ_DEBUGFS is not set CONFIG_CLOCKSOURCE_WATCHDOG=y @@ -87,8 +87,9 @@ CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y # CONFIG_PREEMPT_NONE is not set -CONFIG_PREEMPT_VOLUNTARY=y -# CONFIG_PREEMPT is not set +# CONFIG_PREEMPT_VOLUNTARY is not set +CONFIG_PREEMPT=y +CONFIG_PREEMPT_COUNT=y # # CPU/Task time and stats accounting @@ -109,7 +110,7 @@ # # RCU Subsystem # -CONFIG_TREE_RCU=y +CONFIG_PREEMPT_RCU=y # CONFIG_RCU_EXPERT is not set CONFIG_SRCU=y CONFIG_TREE_SRCU=y @@ -421,10 +422,10 @@ CONFIG_EFI_MIXED=y CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set -CONFIG_HZ_250=y +# CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set -# CONFIG_HZ_1000 is not set -CONFIG_HZ=250 +CONFIG_HZ_1000=y +CONFIG_HZ=1000 CONFIG_SCHED_HRTICK=y CONFIG_KEXEC=y CONFIG_KEXEC_FILE=y @@ -864,11 +865,7 @@ CONFIG_PREEMPT_NOTIFIERS=y CONFIG_PADATA=y CONFIG_ASN1=y -CONFIG_INLINE_SPIN_UNLOCK_IRQ=y -CONFIG_INLINE_READ_UNLOCK=y -CONFIG_INLINE_READ_UNLOCK_IRQ=y -CONFIG_INLINE_WRITE_UNLOCK=y -CONFIG_INLINE_WRITE_UNLOCK_IRQ=y +CONFIG_UNINLINE_SPIN_UNLOCK=y CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y CONFIG_MUTEX_SPIN_ON_OWNER=y CONFIG_RWSEM_SPIN_ON_OWNER=y @@ -5160,6 +5157,7 @@ CONFIG_REGULATOR_WM8994=m CONFIG_CEC_CORE=y CONFIG_CEC_NOTIFIER=y +CONFIG_CEC_PIN=y CONFIG_RC_CORE=m CONFIG_RC_MAP=m CONFIG_LIRC=y @@ -5205,6 +5203,7 @@ CONFIG_MEDIA_RADIO_SUPPORT=y CONFIG_MEDIA_SDR_SUPPORT=y CONFIG_MEDIA_CEC_SUPPORT=y +# CONFIG_CEC_PIN_ERROR_INJ is not set CONFIG_MEDIA_CONTROLLER=y # CONFIG_MEDIA_CONTROLLER_DVB is not set # CONFIG_MEDIA_CONTROLLER_REQUEST_API is not set @@ -5498,6 +5497,7 @@ CONFIG_DVB_PLATFORM_DRIVERS=y CONFIG_CEC_PLATFORM_DRIVERS=y CONFIG_VIDEO_CROS_EC_CEC=m +CONFIG_CEC_GPIO=m CONFIG_VIDEO_SECO_CEC=m CONFIG_VIDEO_SECO_RC=y CONFIG_SDR_PLATFORM_DRIVERS=y @@ -9709,6 +9709,7 @@ CONFIG_SCHEDSTATS=y CONFIG_SCHED_STACK_END_CHECK=y # CONFIG_DEBUG_TIMEKEEPING is not set +# CONFIG_DEBUG_PREEMPT is not set # # Lock Debugging (spinlocks, mutexes, etc...) @@ -9753,7 +9754,7 @@ # CONFIG_NETDEV_NOTIFIER_ERROR_INJECT is not set CONFIG_FUNCTION_ERROR_INJECTION=y # CONFIG_FAULT_INJECTION is not set -# CONFIG_LATENCYTOP is not set +CONFIG_LATENCYTOP=y CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_NOP_TRACER=y CONFIG_HAVE_FUNCTION_TRACER=y @@ -9778,6 +9779,7 @@ CONFIG_FUNCTION_GRAPH_TRACER=y # CONFIG_PREEMPTIRQ_EVENTS is not set # CONFIG_IRQSOFF_TRACER is not set +# CONFIG_PREEMPT_TRACER is not set CONFIG_SCHED_TRACER=y CONFIG_HWLAT_TRACER=y CONFIG_FTRACE_SYSCALLS=y -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Confirmed Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and
[Kernel-packages] [Bug 1831775] Autopkgtest regression report (iproute2/4.18.0-1ubuntu2.1)
All autopkgtests for the newly accepted iproute2 (4.18.0-1ubuntu2.1) for disco have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
** 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/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Confirmed Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834944] Re: linux-fips: 4.15.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Promote to Proposed - phase-changed: Monday, 15. July 2019 12:41 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 15. July 2019 15:22 UTC reason: - promote-signing-to-proposed: Ongoing -- builds not complete in Signing signed:building - promote-to-proposed: Pending -- packages copied to Signing signed:building + promote-signing-to-proposed: Holding -- another kernel is currently pending in Proposed variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834944 Title: linux-fips: 4.15.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Holding before Promote to Proposed phase-changed: Monday, 15. July 2019 15:22 UTC reason: promote-signing-to-proposed: Holding -- another kernel is currently pending in Proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834915] Re: linux-fips: 4.4.0-1014.19 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1834918 - phase: Holding before Promote to Proposed - phase-changed: Monday, 15. July 2019 11:08 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 15. July 2019 15:08 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,signed:building + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834915 Title: linux-fips: 4.4.0-1014.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834918 phase: Ready for Promote to Proposed phase-changed: Monday, 15. July 2019 15:08 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
