[Kernel-packages] [Bug 1836031] Re: [SRU][B/B-OEM]Fix resume failure on some TPM chips
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836031 Title: [SRU][B/B-OEM]Fix resume failure on some TPM chips Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Bug description: SRU justification: [Impact] System will reboot when resume from S3 with some TPM chips installed. [Fix] stable patch is merged in 4.15 kernel: 888d867df441 (tpm: cmd_ready command can be issued only after granting locality) it needs a fix: tpm: separate cmd_ready/go_idle from runtime_pm these 2 patches fix the issue and enable tpm resume after seprating cmd_ready/go_idle. [Test] Verified on hardware. resume from S3 about 30 times with positive result. [Regression Potential] Medium, stable patches backported. Verified on hardware. backported with minor adjustion. These 2 patches are included in 4.18 and 5.0 kernel, only 4.15 needs them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836839] Re: prctl04 in LTP syscall test failed with T kernel on P8 node
The test result on AMD64: startup='Tue Jul 9 14:23:18 2019' tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s prctl04.c:213: INFO: kernel support PR_GET/SET_SECCOMP prctl04.c:125: PASS: prctl(PR_SET_SECCOMP) sets SECCOMP_MODE_STRICT succeed prctl04.c:197: PASS: SECCOMP_MODE_STRICT doesn't permit GET_SECCOMP call prctl04.c:133: PASS: SECCOMP_MODE_STRICT permits read(2) write(2) and _exit(2) prctl04.c:197: PASS: SECCOMP_MODE_STRICT doesn't permit close(2) prctl04.c:165: PASS: prctl(PR_SET_SECCOMP) sets SECCOMP_MODE_FILTER succeed prctl04.c:197: PASS: SECCOMP_MODE_FILTER doestn't permit GET_SECCOMP call prctl04.c:171: PASS: SECCOMP_MODE_FILTER permits close(2) prctl04.c:197: PASS: SECCOMP_MODE_FILTER doesn't permit exit() prctl04.c:95: PASS: SECCOMP_MODE_FILTER permits fork(2) prctl04.c:102: PASS: SECCOMP_MODE_FILTER has been inherited by child Summary: passed 10 failed 0 skipped 0 warnings 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836839 Title: prctl04 in LTP syscall test failed with T kernel on P8 node Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Trusty: New Bug description: This failure was only spotted on PowerPC (node "modoc"), it has passed with AMD64 / i386, entirely skipped on ARM64. startup='Mon Jul 15 22:48:25 2019' tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s prctl04.c:213: INFO: kernel support PR_GET/SET_SECCOMP prctl04.c:125: PASS: prctl(PR_SET_SECCOMP) sets SECCOMP_MODE_STRICT succeed prctl04.c:197: PASS: SECCOMP_MODE_STRICT doesn't permit GET_SECCOMP call prctl04.c:133: PASS: SECCOMP_MODE_STRICT permits read(2) write(2) and _exit(2) prctl04.c:197: PASS: SECCOMP_MODE_STRICT doesn't permit close(2) prctl04.c:155: CONF: kernel doesn't support SECCOMP_MODE_FILTER prctl04.c:155: CONF: kernel doesn't support SECCOMP_MODE_FILTER prctl04.c:155: CONF: kernel doesn't support SECCOMP_MODE_FILTER prctl04.c:205: FAIL: SECCOMP_MODE_FILTER permits exit() unexpectedly prctl04.c:155: CONF: kernel doesn't support SECCOMP_MODE_FILTER Summary: passed 4 failed 1 skipped 4 warnings 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836755] Re: hda/realtek: can't detect external mic on a Dell machine
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836755 Title: hda/realtek: can't detect external mic on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] The external can't be detected when plugging headset in the front audio jack. [Fix] apply the alc891 fixup to set headset-mic and headpphone-mic pins. [Test Case] apply this patch and boot with the kernel, plug the headset-mic and choose headset-mic from popup dialogue, the headset-mic can record sound very well. [Regression Risk] Low. this patch is specific to a dell machine by pin configuration definition. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767992 Title: Linux md raid-10 freezes during resync Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [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.31800
[Kernel-packages] [Bug 1836839] [NEW] prctl04 in LTP syscall test failed with T kernel on P8 node
Public bug reported: This failure was only spotted on PowerPC (node "modoc"), it has passed with AMD64 / i386, entirely skipped on ARM64. startup='Mon Jul 15 22:48:25 2019' tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s prctl04.c:213: INFO: kernel support PR_GET/SET_SECCOMP prctl04.c:125: PASS: prctl(PR_SET_SECCOMP) sets SECCOMP_MODE_STRICT succeed prctl04.c:197: PASS: SECCOMP_MODE_STRICT doesn't permit GET_SECCOMP call prctl04.c:133: PASS: SECCOMP_MODE_STRICT permits read(2) write(2) and _exit(2) prctl04.c:197: PASS: SECCOMP_MODE_STRICT doesn't permit close(2) prctl04.c:155: CONF: kernel doesn't support SECCOMP_MODE_FILTER prctl04.c:155: CONF: kernel doesn't support SECCOMP_MODE_FILTER prctl04.c:155: CONF: kernel doesn't support SECCOMP_MODE_FILTER prctl04.c:205: FAIL: SECCOMP_MODE_FILTER permits exit() unexpectedly prctl04.c:155: CONF: kernel doesn't support SECCOMP_MODE_FILTER Summary: passed 4 failed 1 skipped 4 warnings 0 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Tags: 3.13 ppc64el sru-20190701 trusty ubuntu-ltp-syscalls ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: 3.13 ppc64el sru-20190701 trusty ubuntu-ltp-syscalls -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836839 Title: prctl04 in LTP syscall test failed with T kernel on P8 node Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Trusty: New Bug description: This failure was only spotted on PowerPC (node "modoc"), it has passed with AMD64 / i386, entirely skipped on ARM64. startup='Mon Jul 15 22:48:25 2019' tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s prctl04.c:213: INFO: kernel support PR_GET/SET_SECCOMP prctl04.c:125: PASS: prctl(PR_SET_SECCOMP) sets SECCOMP_MODE_STRICT succeed prctl04.c:197: PASS: SECCOMP_MODE_STRICT doesn't permit GET_SECCOMP call prctl04.c:133: PASS: SECCOMP_MODE_STRICT permits read(2) write(2) and _exit(2) prctl04.c:197: PASS: SECCOMP_MODE_STRICT doesn't permit close(2) prctl04.c:155: CONF: kernel doesn't support SECCOMP_MODE_FILTER prctl04.c:155: CONF: kernel doesn't support SECCOMP_MODE_FILTER prctl04.c:155: CONF: kernel doesn't support SECCOMP_MODE_FILTER prctl04.c:205: FAIL: SECCOMP_MODE_FILTER permits exit() unexpectedly prctl04.c:155: CONF: kernel doesn't support SECCOMP_MODE_FILTER Summary: passed 4 failed 1 skipped 4 warnings 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836474] Re: dell touchpad not working
Does kernel parameter "i8042.nomux=1" help? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836474 Title: dell touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: i installed ubuntu today on my dell lattitude 3540 and touchpad was working fine while installing ubuntu os but after its installation and rebooting touchpad is not working at all. it is not even detecting it . in device list. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-20-generic 5.0.0-20.21 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: motican1678 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 14 14:10:35 2019 InstallationDate: Installed on 2019-07-14 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Latitude 3540 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=b6ff2f80-7175-4690-8484-add63299c36e ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 043T50 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A13 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/18/2018:svnDellInc.:pnLatitude3540:pvrA13:rvnDellInc.:rn043T50:rvrA00:cvnDellInc.:ct8:cvrA13: dmi.product.name: Latitude 3540 dmi.product.sku: Latitude 3540 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775378] Re: fanotify06 in LTP syscall test failed with T kernel
I could see this failing on Trusty ARM64 Moonshot node, but not the ppc64le node "modoc": startup='Tue Jul 9 07:45:17 2019' tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop0' tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' mke2fs 1.42.9 (4-Feb-2014) tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s tst_fs_setup.c:43: INFO: fanotify06.c:239: overlayfs is not configured in this kernel fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=6308 fd=30 fanotify06.c:147: PASS: group 1 got event: mask 2 pid=6308 fd=30 fanotify06.c:147: PASS: group 2 got event: mask 2 pid=6308 fd=30 fanotify06.c:220: FAIL: group 3 got event fanotify06.c:230: PASS: group 4 got no event fanotify06.c:220: FAIL: group 5 got event fanotify06.c:230: PASS: group 6 got no event fanotify06.c:230: PASS: group 7 got no event fanotify06.c:230: PASS: group 8 got no event fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:173: CONF: overlayfs is not configured in this kernel. Summary: passed 7 failed 2 skipped 1 warnings 0 ** Tags added: arm64 sru-20190701 ubuntu-ltp-syscalls ** Tags added: 3.13 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775378 Title: fanotify06 in LTP syscall test failed with T kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Bug description: The "fanotify06" from the LTP syscall tests has failed on a testing node with T kernel installed. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. /opt/ltp/testcases/bin/fanotify06 <<>> tag=fanotify06 stime=1528269991 cmdline="fanotify06" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fanotify06.c:147: PASS: group 0 get event: mask 2 pid=22619 fd=29 fanotify06.c:147: PASS: group 1 get event: mask 2 pid=22619 fd=29 fanotify06.c:147: PASS: group 2 get event: mask 2 pid=22619 fd=29 fanotify06.c:197: FAIL: group 3 got event fanotify06.c:197: FAIL: group 4 got event fanotify06.c:197: FAIL: group 5 got event fanotify06.c:208: PASS: group 6 got no event fanotify06.c:208: PASS: group 7 got no event fanotify06.c:197: FAIL: group 8 got event Summary: passed 5 failed 4 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-generic 3.13.0-149.199 ProcVersionSignature: User Name 3.13.0-149.199-generic 3.13.11-ckt39 Uname: Linux 3.13.0-149-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 6 10:09 seq crw-rw 1 root audio 116, 33 Jun 6 10:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [3.472391] init: plymouth-upstart-bridge main process ended, respawning Date: Wed Jun 6 10:12:15 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.name: S1200RP dmi.product.ver
[Kernel-packages] [Bug 1836801] Re: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba
Upstream stable 4.4.181 had many brcmfmac updates. From the trace
suspicious seems:
brcmfmac: revise handling events in receive path
commit 9c349892ccc90c6de2baaa69cc78449f58082273 upstream.
which has a fixup upstream that sounds like the issue:
commit 31143e2933d1675c4c1ba6ce125cdd95870edd85
Author: Franky Lin
Date: Thu Jun 2 02:00:27 2016 -0700
brcmfmac: add eth_type_trans back for PCIe full dongle
A regression was introduced in commit 9c349892ccc9 ("brcmfmac: revise
handling events in receive path") which moves eth_type_trans() call
to brcmf_rx_frame(). Msgbuf layer doesn't use brcmf_rx_frame() but invokes
brcmf_netif_rx() directly. In such case the Ethernet header was not
stripped out resulting in null pointer dereference in the networking
stack.
BUG: unable to handle kernel NULL pointer dereference at 0048
IP: [] enqueue_to_backlog+0x56/0x260
...
Fixes: 9c349892ccc9 ("brcmfmac: revise handling events in receive path")
Reported-by: Rafal Milecki
Reported-by: Grey Christoforo
Reviewed-by: Pieter-Paul Giesberts
Reviewed-by: Arend Van Spriel
Reviewed-by: Hante Meuleman
Signed-off-by: Franky Lin
[ar...@broadcom.com: rephrased the commit message]
Signed-off-by: Arend van Spriel
Signed-off-by: Kalle Valo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1836801
Title:
BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba
Status in linux package in Ubuntu:
Confirmed
Status in linux-signed package in Ubuntu:
New
Bug description:
[Description]
The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running
with the proposed kernel 4.4.0-155.182-generic will cause kernel
trace[1]. However the wifi function works properly with the kernel
4.4.0-154.181
[Steps to Reproduce]
1. Install ubuntu xenial, enable the proposed repository, and update the
system with "sudo apt-get dist-upgrade"
2. nmcli d wifi rescan
3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi
interface is wlp2s0), you will see the available SSIDs in your environment.
4. nmcli d wifi connect ifname wlp2s0 name TEST_CON
[Expected Result]
The AP is connected
[Actual Result]
You will get the message: "Error: Connection activation failed: (5) IP
configuration could not be reserved (no available address, timeout, etc.)." and
the kernel trace from /var/log/syslog[1]
Sometime the system hangs when connecting to a wifi AP.
[More Information]
[1] The kernel trace log
hecking kernel ring buffer for brcmfmac messages:
kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface
driver brcmfmac
kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct
firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2
kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0:
renamed from wlan0
kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep
snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic
snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core
snd_hda_core snd_hwd
ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp
kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul
dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device
aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd
snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms
brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc
btintel
videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma
videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss
kern :warn : [Tue Jul 16 10:08:01 2019] []
brcmf_netif_rx+0x73/0xa0 [brcmfmac]
kern :warn : [Tue Jul 16 10:08:01 2019] []
brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac]
kern :warn : [Tue Jul 16 10:08:01 2019] []
brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac]
kern :warn : [Tue Jul 16 10:08:01 2019] []
brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac]
kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep
snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic
snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core
snd_hda_core snd_hwd
ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp
kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul
dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device
aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd
snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms
brcmutil usbnet memstick btusb btrtl uvcvideo btbcm c
[Kernel-packages] [Bug 1828166] Re: perf top problem on z with Ubuntu 18.04
I can also confirm that the issue still exists, but only if I run perf top as root or with sudo. Running perf top it as regular user is fine - even w/o the patches packages! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as low since this happens only while using the perf top tool * and it is known that the commit (above) fixes the problem * and the fix is upstream since 4.19 [Other Info] * current disco and eoan kernels don't show that problem * bisecting result points to above commit * applies cleanly on cosmic, but has a little conflict on bionic (both master-next) _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836836] [NEW] First click on Goodix touchpad doesn't be recognized after runtime suspended
Public bug reported: [Impact] Wake up from runtime suspend, Goodix doesn't report correct Tap event by tapping it the first time, so if you double tap the touchpad, the system only got one tap. [Fix] Adding one missing platform which uses Goodix touchpad IC to the i2c designware quirk list. [Test] Verified on the buggy machines. [Regression Potential] Low, this quirk doesn't hurt anything and do little or none to power consumption. ** Affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836836 Title: First click on Goodix touchpad doesn't be recognized after runtime suspended Status in linux-oem-osp1 package in Ubuntu: New Status in linux-oem-osp1 source package in Bionic: In Progress Bug description: [Impact] Wake up from runtime suspend, Goodix doesn't report correct Tap event by tapping it the first time, so if you double tap the touchpad, the system only got one tap. [Fix] Adding one missing platform which uses Goodix touchpad IC to the i2c designware quirk list. [Test] Verified on the buggy machines. [Regression Potential] Low, this quirk doesn't hurt anything and do little or none to power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1836836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 [9df0:0034]
https://lists.ubuntu.com/archives/kernel-team/2019-July/102298.html https://lists.ubuntu.com/archives/kernel-team/2019-July/102299.html ** Description changed: + SRU Justification: + + [Impact] + Bluetooth for Intel Wireless-AC 9560 variant 9df0:0034 still fails to + pair BT LE HID devices on recent (>= 4.19) kernel. + + [Fix] + Bluetooth firmware REL0450 or newer is required to fix this issue. + + [Test Case] + Install new firmware blob to /lib/firmware/intel, shutdown the machine + completely and wait for a couple minutes to trigger firmware reloading + at the next boot. Then perform Bluetooth LE HID devices pairing to + verify if the proposed fw fixes this issue. + + [Regression Risk] + Low. This affects only sub models of Intel JeffersonPeak Bluetooth chip + series using these firmware blobs. + + == Original 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... -- You received this bug notification because you
[Kernel-packages] [Bug 1836668] Re: Xenial update: 4.4.185 upstream stable release
2 patches were skipped because they were already applied: 0002-mm-page_idle.c-fix-oops-because-end_pfn-is-larger-th.patch 0036-KVM-X86-Fix-scan-ioapic-use-before-initialization.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1836668] Re: Xenial update: 4.4.185 upstream stable release
Applied patches:
* fs/binfmt_flat.c: make load_flat_shared_library() work
* scsi: vmw_pscsi: Fix use-after-free in pvscsi_queue_lck()
* tracing: Silence GCC 9 array bounds warning
* gcc-9: silence 'address-of-packed-member' warning
* usb: chipidea: udc: workaround for endpoint conflict issue
* Input: uinput - add compat ioctl number translation for UI_*_FF_UPLOAD
* apparmor: enforce nullbyte at end of tag string
* parport: Fix mem leak in parport_register_dev_model
* parisc: Fix compiler warnings in float emulation code
* IB/hfi1: Insure freeze_work work_struct is canceled on shutdown
* MIPS: uprobes: remove set but not used variable 'epc'
* net: hns: Fix loopback test failed at copper ports
* sparc: perf: fix updated event period in response to PERF_EVENT_IOC_PERIOD
* scripts/checkstack.pl: Fix arm64 wrong or unknown architecture
* scsi: ufs: Check that space was properly alloced in copy_query_response
* s390/qeth: fix VLAN attribute in bridge_hostnotify udev event
* hwmon: (pmbus/core) Treat parameters as paged if on multiple pages
* Btrfs: fix race between readahead and device replace/removal
* btrfs: start readahead also in seed devices
* can: flexcan: fix timeout when set small bitrate
* can: purge socket error queue on sock destruct
* ARM: imx: cpuidle-imx6sx: Restrict the SW2ISO increase to i.MX6SX
* Bluetooth: Align minimum encryption key size for LE and BR/EDR connections
* Bluetooth: Fix regression with minimum encryption key size alignment
* SMB3: retry on STATUS_INSUFFICIENT_RESOURCES instead of failing write
* cfg80211: fix memory leak of wiphy device name
* mac80211: drop robust management frames from unknown TA
* perf ui helpline: Use strlcpy() as a shorter form of strncpy() + explicit set
nul
* perf help: Remove needless use of strncpy()
* 9p/rdma: do not disconnect on down_interruptible EAGAIN
* 9p: acl: fix uninitialized iattr access
* 9p/rdma: remove useless check in cm_event_handler
* 9p: p9dirent_read: check network-provided name length
* net/9p: include trans_common.h to fix missing prototype warning.
* ovl: modify ovl_permission() to do checks on two inodes
* x86/speculation: Allow guests to use SSBD even if host does not
* cpu/speculation: Warn on unsupported mitigations= parameter
* sctp: change to hold sk after auth shkey is created successfully
* tipc: change to use register_pernet_device
* tipc: check msg->req data len in tipc_nl_compat_bearer_disable
* team: Always enable vlan tx offload
* ipv4: Use return value of inet_iif() for __raw_v4_lookup in the while loop
* bonding: Always enable vlan tx offload
* net: check before dereferencing netdev_ops during busy poll
* Bluetooth: Fix faulty expression for minimum encryption key size check
* um: Compile with modern headers
* ASoC : cs4265 : readable register too low
* spi: bitbang: Fix NULL pointer dereference in spi_unregister_master
* ASoC: max98090: remove 24-bit format support if RJ is 0
* usb: gadget: fusb300_udc: Fix memory leak of fusb300->ep[i]
* usb: gadget: udc: lpc32xx: allocate descriptor with GFP_ATOMIC
* scsi: hpsa: correct ioaccel2 chaining
* ARC: Assume multiplier is always present
* ARC: fix build warning in elf.h
* MIPS: math-emu: do not use bools for arithmetic
* mfd: omap-usb-tll: Fix register offsets
* swiotlb: Make linux/swiotlb.h standalone includible
* bug.h: work around GCC PR82365 in BUG()
* MIPS: Workaround GCC __builtin_unreachable reordering bug
* ptrace: Fix ->ptracer_cred handling for PTRACE_TRACEME
* crypto: user - prevent operating on larval algorithms
* ALSA: seq: fix incorrect order of dest_client/dest_ports arguments
* ALSA: firewire-lib/fireworks: fix miss detection of received MIDI messages
* ALSA: usb-audio: fix sign unintended sign extension on left shifts
* lib/mpi: Fix karactx leak in mpi_powm
* btrfs: Ensure replaced device doesn't have pending chunk allocation
* tty: rocket: fix incorrect forward declaration of 'rp_init()'
* ARC: handle gcc generated __builtin_trap for older compiler
* arm64, vdso: Define vdso_{start,end} as array
* KVM: x86: degrade WARN to pr_warn_ratelimited
* dmaengine: imx-sdma: remove BD_INTR for channel0
* Linux 4.4.185
--
You 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
fro
[Kernel-packages] [Bug 1836667] Re: Xenial update: 4.4.184 upstream stable release
All patches from this updated were already applied. -- You 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 1836666] Re: Xenial update: 4.4.183 upstream stable release
One patch was skipped as it was already present: 0039-Revert-Bluetooth-Align-minimum-encryption-key-size-f.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1836665] Re: Xenial update: 4.4.182 upstream stable release
All patches from this updated were already applied. -- You 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: 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: 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 1836665] Re: Xenial update: 4.4.182 upstream stable release
Applied patches: * Linux 4.4.182 -- You 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: 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: 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 1836666] Re: Xenial update: 4.4.183 upstream stable release
Applied patches: * fs/fat/file.c: issue flush after the writeback of FAT * sysctl: return -EINVAL if val violates minmax * ipc: prevent lockup on alloc_msg and free_msg * hugetlbfs: on restore reserve error path retain subpool reservation * mm/cma.c: fix crash on CMA allocation if bitmap allocation fails * mm/cma_debug.c: fix the break condition in cma_maxchunk_get() * kernel/sys.c: prctl: fix false positive in validate_prctl_map() * mfd: intel-lpss: Set the device in reset state when init * mfd: twl6040: Fix device init errors for ACCCTL register * perf/x86/intel: Allow PEBS multi-entry in watermark mode * drm/bridge: adv7511: Fix low refresh rate selection * ntp: Allow TAI-UTC offset to be set to zero * f2fs: fix to avoid panic in do_recover_data() * f2fs: fix to do sanity check on valid block count of segment * iommu/vt-d: Set intel_iommu_gfx_mapped correctly * ALSA: hda - Register irq handler after the chip initialization * nvmem: core: fix read buffer in place * fuse: retrieve: cap requested size to negotiated max_write * nfsd: allow fh_want_write to be called twice * x86/PCI: Fix PCI IRQ routing table memory leak * platform/chrome: cros_ec_proto: check for NULL transfer function * soc: mediatek: pwrap: Zero initialize rdata in pwrap_init_cipher * clk: rockchip: Turn on "aclk_dmac1" for suspend on rk3288 * ARM: dts: imx6sx: Specify IMX6SX_CLK_IPG as "ahb" clock to SDMA * ARM: dts: imx6sx: Specify IMX6SX_CLK_IPG as "ipg" clock to SDMA * ARM: dts: imx6qdl: Specify IMX6QDL_CLK_IPG as "ipg" clock to SDMA * PCI: rpadlpar: Fix leaked device_node references in add/remove paths * PCI: rcar: Fix a potential NULL pointer dereference * video: hgafb: fix potential NULL pointer dereference * video: imsttfb: fix potential NULL pointer dereferences * PCI: xilinx: Check for __get_free_pages() failure * gpio: gpio-omap: add check for off wake capable gpios * dmaengine: idma64: Use actual device for DMA transfers * pwm: tiehrpwm: Update shadow register for disabling PWMs * ARM: dts: exynos: Always enable necessary APIO_1V8 and ABB_1V8 regulators on Arndale Octa * pwm: Fix deadlock warning when removing PWM device * ARM: exynos: Fix undefined instruction during Exynos5422 resume * futex: Fix futex lock the wrong page * ALSA: seq: Cover unsubscribe_port() in list_mutex * libata: Extend quirks for the ST1000LM024 drives with NOLPM quirk * mm/list_lru.c: fix memory leak in __memcg_init_list_lru_node * fs/ocfs2: fix race in ocfs2_dentry_attach_lock() * signal/ptrace: Don't leak unitialized kernel memory with PTRACE_PEEK_SIGINFO * ptrace: restore smp_rmb() in __ptrace_may_access() * i2c: acorn: fix i2c warning * bcache: fix stack corruption by PRECEDING_KEY() * cgroup: Use css_tryget() instead of css_tryget_online() in task_get_css() * ASoC: cs42xx8: Add regcache mask dirty * Drivers: misc: fix out-of-bounds access in function param_set_kgdbts_var * scsi: lpfc: add check for loss of ndlp when sending RRQ * scsi: bnx2fc: fix incorrect cast to u64 on shift operation * usbnet: ipheth: fix racing condition * KVM: x86/pmu: do not mask the value that is written to fixed PMUs * KVM: s390: fix memory slot handling for KVM_SET_USER_MEMORY_REGION * drm/vmwgfx: integer underflow in vmw_cmd_dx_set_shader() leading to an invalid read * drm/vmwgfx: NULL pointer dereference from vmw_cmd_dx_view_define() * USB: Fix chipmunk-like voice when using Logitech C270 for recording audio. * USB: usb-storage: Add new ID to ums-realtek * USB: serial: pl2303: add Allied Telesis VT-Kit3 * USB: serial: option: add support for Simcom SIM7500/SIM7600 RNDIS mode * USB: serial: option: add Telit 0x1260 and 0x1261 compositions * ax25: fix inconsistent lock state in ax25_destroy_timer * be2net: Fix number of Rx queues used for flow hashing * ipv6: flowlabel: fl6_sock_lookup() must use atomic_inc_not_zero * lapb: fixed leak of control-blocks. * neigh: fix use-after-free read in pneigh_get_next * sunhv: Fix device naming inconsistency between sunhv_console and sunhv_reg * mISDN: make sure device name is NUL terminated * x86/CPU/AMD: Don't force the CPB cap when running under a hypervisor * perf/ring_buffer: Fix exposing a temporarily decreased data_head * perf/ring_buffer: Add ordering to rb->nest increment * gpio: fix gpio-adp5588 build errors * net: tulip: de4x5: Drop redundant MODULE_DEVICE_TABLE() * i2c: dev: fix potential memory leak in i2cdev_ioctl_rdwr * configfs: Fix use-after-free when accessing sd->s_dentry * ia64: fix build errors by exporting paddr_to_nid() * KVM: PPC: Book3S: Use new mutex to synchronize access to rtas token list * net: sh_eth: fix mdio access in sh_eth_close() for R-Car Gen2 and RZ/A1 SoCs * scsi: libcxgbi: add a check for NULL pointer in cxgbi_check_route() * scsi: libsas: delete sas port if expander discover failed * Revert "crypto: crypto4xx - properly set IV after de- and encrypt" * coredump: fix race condition between mmget_not_zero()/get_task_mm() and core dumping * Abort file_remove_privs() for non-reg. files * Linux 4.4
[Kernel-packages] [Bug 1836667] Re: Xenial update: 4.4.184 upstream stable release
Applied patches: * Linux 4.4.184 -- You 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 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash
Yes, please test hwe-edge kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818974 Title: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE. Since kernel 4.18 sometimes while waking up from standby my user session crash. I assume that my attached external USB to SATA HDD could be cause this kernel bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin27966 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (228 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: LENOVO 20FXS05500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs noibpb l1tf=off vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 09/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET87W (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774394] Re: fcntl35 / fcntl35_64 in LTP syscall test failed with T/X/X-LTS kernel
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-xenial (Ubuntu Trusty) 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/1774394 Title: fcntl35 / fcntl35_64 in LTP syscall test failed with T/X/X-LTS kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-lts-xenial package in Ubuntu: New Status in linux source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Bug description: The "fcntl35" and "fcntl35_64" from the LTP syscall tests have failed on a testing node with X-LTS i386 kernel installed (they were not tested on amd64/arm64 because the test was not ready when the SRU starts). <>> tag=fcntl35 stime=1527764565 cmdline="fcntl35" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> <<>> tag=fcntl35_64 stime=1527764565 cmdline="fcntl35_64" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154~14.04.1 ProcVersionSignature: User Name 4.4.0-128.154~14.04.1-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: i386 Date: Thu May 31 11:05:58 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Thank you, Warren. So I think I can begin to send a patch to the series don't have REL0450 ibt-17-16-1.sfi, so that owners of the same devices don't have to manually download again. For polluted /lib/firmware, I think I would restore what it was and copy only ibt-17-16-1.sfi to keep Bluetooth working. Because I myself run apt updates everyday, and I don't want to break any installation script as possible. Besides, yes, keep things simple would also be nice. ** Also affects: linux-firmware (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux-firmware (Ubuntu Cosmic) Status: New => Won't Fix ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Disco) Status: New => In Progress ** Summary changed: - Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up + Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up [9df0:0034] -- 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 [9df0:0034] Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: In Progress Status in linux-firmware source package in Cosmic: Won't Fix Status in linux-firmware source package in Disco: In Progress 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 Contro
[Kernel-packages] [Bug 1830084] Re: ubuntu_kernel_tests ftrace fails
On GCP trace_printk module can't be found which triggers exit_unresolved /home/jenkins/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace/test.d/event/trace_printk.tc + rmmod trace-printk rmmod: ERROR: Module trace_printk is not currently loaded + : + modprobe trace-printk modprobe: FATAL: Module trace-printk not found in directory /lib/modules/5.0.0-1011-gcp + echo No trace-printk sample module - please make CONFIG_SAMPLE_TRACE_PRINTK=m ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Tags added: aws gcp sru-20190701 ** Tags removed: aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1830084 Title: ubuntu_kernel_tests ftrace fails Status in ubuntu-kernel-tests: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-gcp package in Ubuntu: New Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: Confirmed Status in linux-gcp source package in Disco: New Bug description: Cloud: Azure Series: Disco Kernel: 5.0.0-1007.7 linux-azure Instance: Standard_D2_v3 and others. 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > /proc/sys/net/ipv4/conf/all/accept_local'' 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done for 'all'. 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13 05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest 05/20 14:24:27 DEBUG| utils:0153| [stdout] 05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal number: 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests === 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file check 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for tracers 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock test 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing check 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the ringbuffer size 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing setting 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and trace_marker 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic event - add/remove kprobe events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic event - add/remove synthetic events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic event - selective clear (compatibility) 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic event - generic clear event 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - enable/disable with event level files 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - restricts events based on pid 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - enable/disable with subsystem level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20
[Kernel-packages] [Bug 1830084] Re: ubuntu_kernel_tests ftrace fails
On Google, GCP this appears to fail across all of our tested instances. Looks like that the cause is from the following due to the following 07/16 06:52:00 DEBUG| utils:0153| [stdout] [16] Test trace_printk from module [UNRESOLVED] 07/16 06:52:05 DEBUG| utils:0153| [stdout] [21] ftrace - function trace with cpumask[UNRESOLVED] 07/16 06:52:08 DEBUG| utils:0153| [stdout] [23] ftrace - function trace on module [UNRESOLVED] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1830084 Title: ubuntu_kernel_tests ftrace fails Status in ubuntu-kernel-tests: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-gcp package in Ubuntu: New Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: Confirmed Status in linux-gcp source package in Disco: New Bug description: Cloud: Azure Series: Disco Kernel: 5.0.0-1007.7 linux-azure Instance: Standard_D2_v3 and others. 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > /proc/sys/net/ipv4/conf/all/accept_local'' 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done for 'all'. 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13 05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest 05/20 14:24:27 DEBUG| utils:0153| [stdout] 05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal number: 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests === 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file check 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for tracers 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock test 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing check 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the ringbuffer size 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing setting 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and trace_marker 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic event - add/remove kprobe events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic event - add/remove synthetic events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic event - selective clear (compatibility) 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic event - generic clear event 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - enable/disable with event level files 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - restricts events based on pid 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - enable/disable with subsystem level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - enable/disable with top level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 1
[Kernel-packages] [Bug 1821906] Re: debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4
Failure on Trusty: timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.4VEzBBYPcp -smp 1 # -initrd /tmp/tmp.Ef5R8Mt7p5 enabling apic PASS: #BP FAIL: hw breakpoint (test that dr6.BS is not set) FAIL: hw breakpoint (test that dr6.BS is not cleared) FAIL: single step FAIL: single step emulated instructions FAIL: hw watchpoint (test that dr6.BS is not cleared) FAIL: hw watchpoint (test that dr6.BS is not set) PASS: icebp PASS: MOV SS + watchpoint + ICEBP PASS: MOV SS + watchpoint + int $1 PASS: MOV SS + watchpoint + INT3 SUMMARY: 11 tests, 6 unexpected failures FAIL debug (11 tests, 6 unexpected failures) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Trusty) Status: Incomplete => Confirmed ** Tags added: 3.13 4.4 ubuntu-kvm-unit-tests ** Tags added: sru-20190701 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821906 Title: debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Status in linux source package in Xenial: Confirmed Bug description: This test has failed on: * T-3.13: - FAIL debug (11 tests, 6 unexpected failures) * T-4.4 / X-4.4: - FAIL debug (11 tests, 1 unexpected failures) root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=debug TIMEOUT=90s ACCEL= ./x86/run x86/debug.flat -smp 1 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/debug.flat -smp 1 # -initrd /tmp/tmp.WOQmQkB7bo enabling apic PASS: #BP PASS: hw breakpoint (test that dr6.BS is not set) PASS: hw breakpoint (test that dr6.BS is not cleared) PASS: single step FAIL: single step emulated instructions PASS: hw watchpoint (test that dr6.BS is not cleared) PASS: hw watchpoint (test that dr6.BS is not set) PASS: icebp PASS: MOV SS + watchpoint + ICEBP PASS: MOV SS + watchpoint + int $1 PASS: MOV SS + watchpoint + INT3 SUMMARY: 11 tests, 1 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2 ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Wed Mar 27 11:15:05 2019 SourcePackage: linux-signed-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836809] Re: segfault when CCD are present in two different HOG services
Thanks for the bug report. Please tell us what version of Ubuntu you are using. Then please report the problem to the BlueZ developers at: https://bugzilla.kernel.org (Product: Drivers, Component: Bluetooth) and then tell us the new bug ID. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1836809 Title: segfault when CCD are present in two different HOG services Status in bluez package in Ubuntu: Incomplete Bug description: Hello everyone, We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1836809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 after reverting to rel0450 of ibt-17-16-1.sfi" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836467/+attachment/5277544/+files/dmesg3.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
OK - after installing the rel0450 version, shutting down for 5 minutes and rebooting, Bluetooth is still working for me. Here's the new md5sum b24eceb411cf63695aac8e0b6d9f1743 /lib/firmware/intel/ibt-17-16-1.sfi I'll upload the latest output of dmesg | egrep -i "blue|firm", in case that helps. is there a downside to leaving the firmware content that I got off the git site in my /lib/firmware folder for now, or should I reset it? Thanks for your help!!! -- 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/
[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
The md5sum of what is current installed and working is: 5740378bfc048108341a204b83ca97c7 /lib/firmware/intel/ibt-17-16-1.sfi Which is the same md5sum as the rel0472 version you link to above, so yes, that does seem to be working. I've downloaded the rel0450 version now, I'll install it, and leave my computer off for at least 5 minutes this time, and see what happens... -- 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/~ker
[Kernel-packages] [Bug 1685794] Re: Boot delayed for about 90 seconds until 'random: crng init done'
** Also affects: plymouth (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572 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/1685794 Title: Boot delayed for about 90 seconds until 'random: crng init done' Status in linux package in Ubuntu: Confirmed Status in broadcom-sta package in Debian: New Status in plymouth package in Debian: Unknown Bug description: Shortened dmesg output, notice the unnaturally long delay before crng init finishes: [8.533630] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [8.542239] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card1/input18 [8.542313] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card1/input19 [8.542382] input: HDA Intel PCH Dock Line Out as /devices/pci:00/:00:1b.0/sound/card1/input20 [8.542449] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card1/input21 [8.544240] cdc_ether 2-6:2.0 usb0: register 'cdc_ether' at usb-:00:14.0-6, CDC Ethernet Device, 02:1e:10:1f:00:00 [8.544271] usbcore: registered new interface driver cdc_ether [8.637660] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [8.654022] input: HP WMI hotkeys as /devices/virtual/input/input22 [8.688226] cdc_ether 2-6:2.0 enp0s20u6c2: renamed from usb0 [8.713288] iwlwifi :02:00.0 wlo1: renamed from wlan0 [9.804308] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input23 [ 98.327857] random: crng init done [ 98.330072] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 98.330073] Bluetooth: BNEP filters: protocol multicast [ 98.330077] Bluetooth: BNEP socket layer initialized [ 98.443281] kauditd_printk_skb: 90 callbacks suppressed [ 98.492927] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [ 98.681030] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [ 98.685672] IPv6: ADDRCONF(NETDEV_UP): enp0s20u6c2: link is not ready [ 98.685789] cdc_ether 2-6:2.0 enp0s20u6c2: kevent 12 may have been dropped [ 98.688384] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready [ 98.690915] iwlwifi :02:00.0: L1 Enabled - LTR Enabled ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: boot/vmlinuz-4.10.0-19-generic] ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7 Date: Mon Apr 24 14:58:33 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-18 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=9fb9fc1d-15a4-4e98-a2ae-bf572e0900d5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: USH452L0B1 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL
** Changed in: linux-firmware (Ubuntu) Status: In Progress => Fix Committed -- 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/1835879 Title: Intel Wireless-AC 9462/9560 not supported on ICL Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux-firmware source package in Cosmic: Won't Fix Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux-firmware source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Won't Fix Bug description: [Impact] Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake platforms. [Fix] Two changes from Intel maintained backport-iwlwifi repository are necessary to add device ID/configs to iwlwifi driver. [Test] Verified on hardware 9462/9560 on IceLake/CometLake platforms. [Regression Potential] Low. These changes are part of the series to enable 9462/9560 on CometLake/IceLake platforms that don't have the support originally. = Original Bug Description = Intel Wireless-AC 9462/9560 on CML was previously enabled via bug 1833065, bug 1834415 and bug 1834464. However on ICL, it fails to startup with following error messages with kernel v5.2-rc7: iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338 iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3 iwlwifi :00:14.3: Failed to start RT ucode: -5 iwlwifi :00:14.3: Collecting data: trigger 16 fired. iwlwifi :00:14.3: Firmware not running - cannot dump error iwlwifi :00:14.3: Failed to run INIT ucode: -5 Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at the moment) with no luck. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830084] Re: ubuntu_kernel_tests ftrace fails
** Summary changed: - ubuntu_kernel_tests ftrace fails on disco, linux-azure + ubuntu_kernel_tests ftrace fails ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1830084 Title: ubuntu_kernel_tests ftrace fails Status in ubuntu-kernel-tests: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: Confirmed Bug description: Cloud: Azure Series: Disco Kernel: 5.0.0-1007.7 linux-azure Instance: Standard_D2_v3 and others. 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > /proc/sys/net/ipv4/conf/all/accept_local'' 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done for 'all'. 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13 05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest 05/20 14:24:27 DEBUG| utils:0153| [stdout] 05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal number: 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests === 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file check 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for tracers 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock test 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing check 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the ringbuffer size 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing setting 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and trace_marker 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic event - add/remove kprobe events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic event - add/remove synthetic events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic event - selective clear (compatibility) 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic event - generic clear event 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - enable/disable with event level files 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - restricts events based on pid 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - enable/disable with subsystem level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - enable/disable with top level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [16] Test trace_printk from module 05/20 14:24:36 DEBUG| utils:0153| [stdout] -e [UNRESOLVED] 05/20 14:24:36 DEBUG| utils:0153| [stdout] -e -n [17] ftrace - function graph filters with stack tracer 05/20 14:24:38 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:38 D
[Kernel-packages] [Bug 1834930] Re: linux-aws: 4.15.0-1044.46 -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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834930 Title: linux-aws: 4.15.0-1044.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: 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 backports: bug 1834929 (xenial/linux-aws-hwe) derivatives: bug 1834927 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Testing phase-changed: Thursday, 11. July 2019 00:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834930] Re: linux-aws: 4.15.0-1044.46 -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 backports: bug 1834929 (xenial/linux-aws-hwe) derivatives: bug 1834927 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Testing phase-changed: Thursday, 11. July 2019 00:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834930 Title: linux-aws: 4.15.0-1044.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: 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 backports: bug 1834929 (xenial/linux-aws-hwe) derivatives: bug 1834927 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Testing phase-changed: Thursday, 11. July 2019 00:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834886] Re: linux-aws: 5.0.0-1011.12 -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 backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Testing phase-changed: Monday, 15. July 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834886 Title: linux-aws: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: 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 backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Testing phase-changed: Monday, 15. July 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834886] Re: linux-aws: 5.0.0-1011.12 -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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834886 Title: linux-aws: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: 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 backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Testing phase-changed: Monday, 15. July 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
** Changed in: dkms (Ubuntu Disco) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Committed Status in dkms source package in Disco: Fix Committed Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836211] Re: bcmwl fails to install with recent Eoan (Bad return status for module build on kernel: 5.0.0-20-generic)
I went to try again and get the log ... and with today's build it is working. Let me try on the other machine that I was seeing this with and then I will close the bug. (The one thing I noticed is that I needed to restart the computer before it worked, while I could swear it used to work as soon as the driver was installed, and so also in a live session. But I have no proof, and maybe it was a different proprietary wi-fi driver I'm thinking of.) -- 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 1836816] 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 1836816 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/1836816 Title: Fix nf_conntrack races when dealing with same origin requests in NAT environments Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Won't Fix Bug description: BugLink: https://bugs.launchpad.net/bugs/1836816 [Impact] There are a number of races in nf_conntrack when multiple packets are sent from the same origin to the same destination at the same time, where there is no pre-existing confirmed conntrack entry, in a NAT environment. This is most frequently seen in users with kubernetes workloads, where dns requests are sent from the same socket at the same time, from different threads. One request is for a A record, the other . A conntrack race happens, which leads to one request being dropped, which leads to 5 second dns timeouts. This problem is not specific to kubernetes, as any multi-threaded process which sends UDP packets from the same socket at the same time from different threads is affected. Note that since UDP is connectionless, no packet is sent when connect() is called, so no conntrack entries are created until a packet is first sent. In the scenario where two UDP packets are sent at the same time from the same socket on different threads, there are the following possible races: 1.) Neither of the packets find a confirmed conntrack entry. This leads to two conntrack entries being created with the same tuples. 2.) Same as 1), but a conntrack entry is confirmed for one of the packets before the other calls get_unique_tuple(). The other packet gets a different reply tuple with the source port changed. The outcomes of the races are the same, one of the packets is dropped when it comes time to confirm conntrack entries with __nf_conntrack_confirm(). For more information, read the technical blog post: https://www.weave.works/blog/racy-conntrack-and-dns-lookup-timeouts [Fix] The fix to race 1) was included in 4.19 upstream by this commit: netfilter: nf_conntrack: resolve clash for matching conntracks commit ed07d9a021df6da53456663a76999189badc432a Author: Martynas Pumputis Date: Mon Jul 2 16:52:14 2018 +0200 This commit adds an extra check to see if the two entries are the same and to merge the entries if they are. The fix to race 2) was included in 5.0 upstream by this commit: netfilter: nf_nat: skip nat clash resolution for same-origin entries commit 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 Author: Martynas Pumputis Date: Tue Jan 29 15:51:42 2019 +0100 This commit ensures that a new source port is not allocated to a duplicated entry, and forwards the duplicated entries to be resolved later on. Note that 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 was also backported to stable releases 4.9.163, 4.14.106, 4.19.29, 4.20.16. Both commits cherry-pick to 4.15 bionic cleanly. Please cherry-pick both commits to all bionic kernels. [Testcase] The reproducer has been provided by the author of the fixes, and is best viewed here: https://github.com/brb/conntrack-race The dmesg logs and packet traces in the above github repo are best viewed while reading upstream discussion: https://patchwork.ozlabs.org/patch/937963/ I have built a test kernel for xenial HWE, which can be found here: https://launchpad.net/~mruffell/+archive/ubuntu/sf00227747-test-kernel The test kernel has been tested with a kubernetes workload and aided with resolution of kubernetes problems. [Regression Potential] As noted previously, 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 has been backported to stable releases 4.9.163, 4.14.106, 4.19.29, 4.20.16 and has no changes to the primary commit. This commit is well tested and considered stable by the community. Both commits have also been present in the -azure kernels since 4.15.0-1030.31 and 4.18.0-1004.4, as per LP #1795493, http://bugs.launchpad.net/bugs/1795493 They have received wide testing, and no problems have been reported. The changes are specifically limited to resolving clashes between duplicate conntrack entries, and any regressions will be limited to that s
[Kernel-packages] [Bug 1836816] [NEW] Fix nf_conntrack races when dealing with same origin requests in NAT environments
Public bug reported: BugLink: https://bugs.launchpad.net/bugs/1836816 [Impact] There are a number of races in nf_conntrack when multiple packets are sent from the same origin to the same destination at the same time, where there is no pre-existing confirmed conntrack entry, in a NAT environment. This is most frequently seen in users with kubernetes workloads, where dns requests are sent from the same socket at the same time, from different threads. One request is for a A record, the other . A conntrack race happens, which leads to one request being dropped, which leads to 5 second dns timeouts. This problem is not specific to kubernetes, as any multi-threaded process which sends UDP packets from the same socket at the same time from different threads is affected. Note that since UDP is connectionless, no packet is sent when connect() is called, so no conntrack entries are created until a packet is first sent. In the scenario where two UDP packets are sent at the same time from the same socket on different threads, there are the following possible races: 1.) Neither of the packets find a confirmed conntrack entry. This leads to two conntrack entries being created with the same tuples. 2.) Same as 1), but a conntrack entry is confirmed for one of the packets before the other calls get_unique_tuple(). The other packet gets a different reply tuple with the source port changed. The outcomes of the races are the same, one of the packets is dropped when it comes time to confirm conntrack entries with __nf_conntrack_confirm(). For more information, read the technical blog post: https://www.weave.works/blog/racy-conntrack-and-dns-lookup-timeouts [Fix] The fix to race 1) was included in 4.19 upstream by this commit: netfilter: nf_conntrack: resolve clash for matching conntracks commit ed07d9a021df6da53456663a76999189badc432a Author: Martynas Pumputis Date: Mon Jul 2 16:52:14 2018 +0200 This commit adds an extra check to see if the two entries are the same and to merge the entries if they are. The fix to race 2) was included in 5.0 upstream by this commit: netfilter: nf_nat: skip nat clash resolution for same-origin entries commit 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 Author: Martynas Pumputis Date: Tue Jan 29 15:51:42 2019 +0100 This commit ensures that a new source port is not allocated to a duplicated entry, and forwards the duplicated entries to be resolved later on. Note that 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 was also backported to stable releases 4.9.163, 4.14.106, 4.19.29, 4.20.16. Both commits cherry-pick to 4.15 bionic cleanly. Please cherry-pick both commits to all bionic kernels. [Testcase] The reproducer has been provided by the author of the fixes, and is best viewed here: https://github.com/brb/conntrack-race The dmesg logs and packet traces in the above github repo are best viewed while reading upstream discussion: https://patchwork.ozlabs.org/patch/937963/ I have built a test kernel for xenial HWE, which can be found here: https://launchpad.net/~mruffell/+archive/ubuntu/sf00227747-test-kernel The test kernel has been tested with a kubernetes workload and aided with resolution of kubernetes problems. [Regression Potential] As noted previously, 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 has been backported to stable releases 4.9.163, 4.14.106, 4.19.29, 4.20.16 and has no changes to the primary commit. This commit is well tested and considered stable by the community. Both commits have also been present in the -azure kernels since 4.15.0-1030.31 and 4.18.0-1004.4, as per LP #1795493, http://bugs.launchpad.net/bugs/1795493 They have received wide testing, and no problems have been reported. The changes are specifically limited to resolving clashes between duplicate conntrack entries, and any regressions will be limited to that scenario. The overall risk of regression is very low. [Notes] The commits in the -azure kernels will need to be reverted before importing the generic bionic updates, since they are the pre-upstream commits, and have had several revisions since they were imported. Replacing them with the actual upstream commits will make things easier in the future to maintain. http://bugs.launchpad.net/bugs/1795493 For race 1): Azure: https://patchwork.ozlabs.org/patch/937963/ Upstream: ed07d9a021df6da53456663a76999189badc432a Commits are the same. For race 2): Azure: https://patchwork.ozlabs.org/patch/952939/ Upstream: 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 Note the difference, old commit must be reverted first. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Affects: linux (Ubuntu Cosmic) Importance: Medium Status: Won't Fix ** Tags: sts ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ub
[Kernel-packages] [Bug 1836742] Re: Please enable CONFIG_PMIC_OPREGION and it's components to resolve issues with enabling integrated display on some BayTrail/CherryTrail-based devices
** 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/1836742 Title: Please enable CONFIG_PMIC_OPREGION and it's components to resolve issues with enabling integrated display on some BayTrail/CherryTrail- based devices Status in linux package in Ubuntu: Confirmed Bug description: Please enable CONFIG_PMIC_OPREGION and it's components (CONFIG_CRC_PMIC_OPREGION, CONFIG_XPOWER_PMIC_OPREGION, CONFIG_BXT_WC_PMIC_OPREGION, CONFIG_CHT_WC_PMIC_OPREGION, CONFIG_CHT_DC_TI_PMIC_OPREGION). On GPD Win 1 and GPD Pocket 1 this should allow to use integrated display when external display is connected. More details is here: https://github.com/torvalds/linux/commit/7b5618f4b834330a052958db934c3dffad4a15c2 https://github.com/torvalds/linux/commit/4e8052af858a6ea2cf656bdb6dbcf16dd87a39c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812159] Re: q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM kernels
I can confirm that the SCHED_STACK_END_CHECK config option has been
enabled in the linux-kvm kernel 4.4.0-1052.59 for xenial, 4.15.0-1039.39
for bionic, and 5.0.0-1011.12 for disco. Thanks!
** Tags added: verification-done-bionic verification-done-disco
verification-failed-xenial
** Tags removed: verification-failed-xenial
** Tags added: verification-done-xenial
--
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/1812159
Title:
q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM
kernels
Status in ubuntu-kernel-tests:
In Progress
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-kvm source package in Xenial:
Fix Committed
Status in linux-kvm source package in Bionic:
Fix Committed
Status in linux-kvm source package in Cosmic:
Fix Committed
Status in linux-kvm source package in Disco:
Fix Committed
Bug description:
== SRU Justification ==
Security team requires the SCHED_STACK_END_CHECK config to be enabled
on all of our kernel.
The test_380_config_sched_stack_end_check test from q-r-t will fail on
all the KVM kernels.
Copied from the config help text:
This option checks for a stack overrun on calls to schedule(). If the
stack end location is found to be over written always panic as the
content of the corrupted region can no longer be trusted. This is to
ensure no erroneous behaviour occurs which could result in data
corruption or a sporadic crash at a later stage once the region is
examined. The runtime overhead introduced is minimal.
== Test ==
Test kernels could be found here:
https://people.canonical.com/~phlin/kernel/lp-1812159-kvm-sched-check/
This issue case be verified with the test_380_config_sched_stack_end_check
test from q-r-t, the test will pass with the patched kernel.
== Regression Potential ==
Low, the introduced runtime overhead is minimal, and it's already enabled in
the generic kernel.
== Original Bug report ==
The test_380_config_sched_stack_end_check test failed on the Bionic
KVM kernel
FAIL: test_380_config_sched_stack_end_check
(__main__.KernelSecurityConfigTest)
Ensure SCHED_STACK_END_CHECK is set
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2628, in
test_380_config_sched_stack_end_check
self.assertKernelConfig('SCHED_STACK_END_CHECK', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: SCHED_STACK_END_CHECK option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
Uname: Linux 4.15.0-1028-kvm x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Jan 17 06:44:41 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/1812159/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836806] Re: Two crashes on raid0 error path (during a member device removal)
This issue affects only kernels after 4.17 and before 5.2, hence it's
fixed on Bionic and Eoan, and won't be fixed in Cosmic (4.18) since it
is EOL.
Patches submitted to kernel-team ML: https://lists.ubuntu.com/archives
/kernel-team/2019-July/102287.html
Cheers,
Guilherme
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836806
Title:
Two crashes on raid0 error path (during a member device removal)
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
* During raid0 error path testing, by removing one member of the
array, we've noticed after kernel 4.18 we can trigger a crash
depending if there's I/O in-flight during the array removal. When
debugging the issue, a second problem was found, that could cause a
different crash.
* For the first and more relevant problem, commit cd4a4ae4683d
("block: don't use blocking queue entered for recursive bio submits")
introduced the flag BIO_QUEUE_ENTERED in order BIOs that were split do bypass
the blocking queue entering routine and use the live non-blocking version. What
happens with md/raid0 though is that their BIOs have their underlying device
changed to the physical disk (array member). If we remove this physical disk
(or if it fails), we could have one BIO that had the flag changed to
BIO_QUEUE_ENTERED and had the device changed to the removed array member
(before its removal); this bio then skips a lot of checks in
generic_make_request_checks(), triggering the following crash:
BUG: unable to handle kernel NULL pointer dereference at 0155
PGD 0 P4D 0
Oops: [#1] SMP PTI
RIP: 0010:blk_throtl_bio+0x45/0x970
[...]
Call Trace:
generic_make_request_checks+0x1bf/0x690
generic_make_request+0x64/0x3f0
raid0_make_request+0x184/0x620 [raid0]
? raid0_make_request+0x184/0x620 [raid0]
md_handle_request+0x126/0x1a0
md_make_request+0x7b/0x180
generic_make_request+0x19e/0x3f0
submit_bio+0x73/0x140
[...]
* When debugging the above issue, by rebuilding the kernel with
CONFIG_BLK_CGROUP=n we've noticed a different crash. Commit
37f9579f4c31 ("blk-mq: Avoid that submitting a bio concurrently with
device removal triggers a crash") introduced a NULL pointer
dereference in generic_make_request(), that manifests as:
BUG: unable to handle kernel NULL pointer dereference at 0078
PGD 0 P4D 0
Oops: [#1] SMP PTI
RIP: 0010:generic_make_request+0x32b/0x400
Call Trace:
submit_bio+0x73/0x140
ext4_io_submit+0x4d/0x60
ext4_writepages+0x626/0xe90
do_writepages+0x4b/0xe0
[...]
* For both the issues, we have simple patches that are present in
linux-stable but not in Linus tree.
## For issue 1 (md removal crash):
869eec894663 ("md/raid0: Do not bypass blocking queue entered for raid0 bios")
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=869eec894663
## For issue 2 (generic_make_request() NULL dereference):
c9d8d3e9d7a0 ("block: Fix a NULL pointer dereference in
generic_make_request()")
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c9d8d3e9d7a0
The reasoning for both patches not being present in Linus tree is
explained in the commit messages, but in summary Ming Lei submitted a
major clean-up series at the same time I've submitted both patches, it
wouldn't make sense to accept my patches to soon after remove the code
paths with his clean-up. But Ming's series rely on legacy I/O path
removal, and so it's very hard to backport. Hence maintainers
suggested me to submit my small fixes to stable tree only.
[Test case]
For both cases, the test is the same, the only change being a kernel
config option. To reproduce issue 1 (md removal crash), a regular
Ubuntu kernel config is enough. For the issue 2, a kernel rebuild with
CONFIG_BLK_CGROUP=n is necessary.
Steps to reproduce:
a) Create a raid0 md array with 2 NVMe devices as members, and mount it with
an ext4 filesystem.
b) Run the following oneliner (supposing the raid0 is mounted in /mnt):
(dd of=/mnt/tmp if=/dev/zero bs=1M count=999 &); sleep 0.3;\
echo 1 > /sys/block/nvme1n1/device/device/remove
(whereas nvme1n1 is the 2nd array member)
[Regression potential]
The fixes are self-contained and small, both validated by a great
number of subsystem maintainers (including block, raid and stable).
Commit c9d8d3e9d7a0 was also validated by the author of the offender
patch it fixes, and has no functional change. Commit 869eec894663 has
only raid0 driver as scope, and fall-backs raid0 to a previous
behavior before the introduction of BIO_QU
[Kernel-packages] [Bug 1836806] Re: Two crashes on raid0 error path (during a member device removal)
** Description changed:
- TBD
+ [Impact]
+
+ * During raid0 error path testing, by removing one member of the array,
+ we've noticed after kernel 4.18 we can trigger a crash depending if
+ there's I/O in-flight during the array removal. When debugging the
+ issue, a second problem was found, that could cause a different crash.
+
+ * For the first and more relevant problem, commit cd4a4ae4683d
+ ("block: don't use blocking queue entered for recursive bio submits")
introduced the flag BIO_QUEUE_ENTERED in order BIOs that were split do bypass
the blocking queue entering routine and use the live non-blocking version. What
happens with md/raid0 though is that their BIOs have their underlying device
changed to the physical disk (array member). If we remove this physical disk
(or if it fails), we could have one BIO that had the flag changed to
BIO_QUEUE_ENTERED and had the device changed to the removed array member
(before its removal); this bio then skips a lot of checks in
generic_make_request_checks(), triggering the following crash:
+
+ BUG: unable to handle kernel NULL pointer dereference at 0155
+ PGD 0 P4D 0
+ Oops: [#1] SMP PTI
+ RIP: 0010:blk_throtl_bio+0x45/0x970
+ [...]
+ Call Trace:
+ generic_make_request_checks+0x1bf/0x690
+ generic_make_request+0x64/0x3f0
+ raid0_make_request+0x184/0x620 [raid0]
+ ? raid0_make_request+0x184/0x620 [raid0]
+ md_handle_request+0x126/0x1a0
+ md_make_request+0x7b/0x180
+ generic_make_request+0x19e/0x3f0
+ submit_bio+0x73/0x140
+ [...]
+
+ * When debugging the above issue, by rebuilding the kernel with
+ CONFIG_BLK_CGROUP=n we've noticed a different crash. Commit 37f9579f4c31
+ ("blk-mq: Avoid that submitting a bio concurrently with device removal
+ triggers a crash") introduced a NULL pointer dereference in
+ generic_make_request(), that manifests as:
+
+ BUG: unable to handle kernel NULL pointer dereference at 0078
+ PGD 0 P4D 0
+ Oops: [#1] SMP PTI
+ RIP: 0010:generic_make_request+0x32b/0x400
+ Call Trace:
+ submit_bio+0x73/0x140
+ ext4_io_submit+0x4d/0x60
+ ext4_writepages+0x626/0xe90
+ do_writepages+0x4b/0xe0
+ [...]
+
+ * For both the issues, we have simple patches that are present in
linux-stable but not in Linus tree.
+ ## For issue 1 (md removal crash):
+ 869eec894663 ("md/raid0: Do not bypass blocking queue entered for raid0 bios")
+
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=869eec894663
+
+ ## For issue 2 (generic_make_request() NULL dereference):
+ c9d8d3e9d7a0 ("block: Fix a NULL pointer dereference in
generic_make_request()")
+
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c9d8d3e9d7a0
+
+ The reasoning for both patches not being present in Linus tree is
+ explained in the commit messages, but in summary Ming Lei submitted a
+ major clean-up series at the same time I've submitted both patches, it
+ wouldn't make sense to accept my patches to soon after remove the code
+ paths with his clean-up. But Ming's series rely on legacy I/O path
+ removal, and so it's very hard to backport. Hence maintainers suggested
+ me to submit my small fixes to stable tree only.
+
+ [Test case]
+
+ For both cases, the test is the same, the only change being a kernel
+ config option. To reproduce issue 1 (md removal crash), a regular Ubuntu
+ kernel config is enough. For the issue 2, a kernel rebuild with
+ CONFIG_BLK_CGROUP=n is necessary.
+
+ Steps to reproduce:
+
+ a) Create a raid0 md array with 2 NVMe devices as members, and mount it with
an ext4 filesystem.
+
+ b) Run the following oneliner (supposing the raid0 is mounted in /mnt):
+ (dd of=/mnt/tmp if=/dev/zero bs=1M count=999 &); sleep 0.3;\
+ echo 1 > /sys/block/nvme1n1/device/device/remove
+ (whereas nvme1n1 is the 2nd array member)
+
+ [Regression potential]
+
+ The fixes are self-contained and small, both validated by a great number
+ of subsystem maintainers (including block, raid and stable). Commit
+ c9d8d3e9d7a0 was also validated by the author of the offender patch it
+ fixes, and has no functional change. Commit 869eec894663 has only raid0
+ driver as scope, and fall-backs raid0 to a previous behavior before the
+ introduction of BIO_QUEUE_ENTERED flag (which indeed increases the
+ amount of checks performed in BIOs), so the regression potential is low
+ and restricted to raid0.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836806
Title:
Two crashes on raid0 error path (during a member device removal)
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
* During raid0 error path testing, by removing one member of
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
I can confirm that the PAGE_POISONING, PAGE_POISONING_NO_SANITY, and
PAGE_POISONING_ZERO config options are set in the linux-kvm
5.0.0-1011.12 kernel in disco proposed. Thanks!
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
In Progress
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-aws source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-kvm source package in Cosmic:
Fix Released
Status in linux-aws source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-kvm source package in Disco:
Fix Committed
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 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/1812624/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820311] Re: linux-kvm: 5.0.0-1001.1 -proposed tracker
linux-kvm is currently 5.0.0-1010.11 in disco, looks like this bug got left behind. Closing. ** Changed in: linux-kvm (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-kvm (Ubuntu Disco) Status: Confirmed => 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/1820311 Title: linux-kvm: 5.0.0-1001.1 -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 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-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Disco: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1819759 phase: Ready for Release phase-changed: Friday, 22. March 2019 13:07 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM
I can confirm that the CONFIG_LOCK_DOWN_KERNEL config is enabled in the
5.0.0-1011.12 linux-kvm kernel in disco-proposed. Thanks!
** Tags added: verifiction-done-disco
--
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/1811981
Title:
test_410_config_lock_down_kernel in ubuntu_kernel_security test failed
on B/C/D KVM
Status in QA Regression Testing:
Fix Released
Status in ubuntu-kernel-tests:
In Progress
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-kvm source package in Bionic:
Fix Committed
Status in linux-kvm source package in Cosmic:
Fix Committed
Status in linux-kvm source package in Disco:
Fix Committed
Bug description:
== SRU Justification ==
Security team requires the CONFIG_LOCK_DOWN_KERNEL to be enabled in all of
our kernels.
== Test ==
Test kernels could be found here:
https://people.canonical.com/~phlin/kernel/lp-1811981-kvm-lockdown/
This issue can be verified with test_410_config_lock_down_kernel
test from q-r-t, the test will pass with the patched kernel.
== Regression Potential ==
Low, we already have this config enabled in the generic kernel.
== Original bug report ==
Kernel Version: 4.15.0-44.47
This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
Power8 and Power9
FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
Ensure kernel efi lockdown is enabled
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2668, in
test_410_config_lock_down_kernel
self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel
config
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1811981/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795659] Re: kernel panic using CIFS share smb2_push_mandatory_locks
** Changed in: linux (Ubuntu Disco) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795659 Title: kernel panic using CIFS share smb2_push_mandatory_locks Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Bug description: Description:Ubuntu 16.04.5 LTS Release:16.04 Kernel: 4.15.0-36-generic #39~16.04.1-Ubuntu SMP Tue Sep 25 08:59:23 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Under load, getting a system crash when accessing files on an SMB3 share. dmesg from crash attached. I can upload the crash dump if needed. Share is mounted with the following options: "ro,_netdev,username=*,password=*,domain=*,vers=3.02,sec=ntlmsspi,nounix,noserverino,nobrl,cache=none" Dmesg points to the cifs module [ 2192.662345] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 2192.662407] IP: smb2_push_mandatory_locks+0x10e/0x3b0 [cifs] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat
** Changed in: linux (Ubuntu Cosmic) Status: In Progress => 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/1824981 Title: cifs set_oplock buffer overflow in strcat Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Fix Committed Bug description: Ubuntu 18.04.2 LTS Linux SRV013 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux DELL R740, 2 CPU (40 Cores, 80 Threads), 384 GiB RAM top - 12:39:53 up 3:41, 4 users, load average: 66.19, 64.06, 76.90 Tasks: 1076 total, 1 running, 675 sleeping, 12 stopped, 1 zombie %Cpu(s): 28.2 us, 0.3 sy, 0.0 ni, 71.5 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 39483801+total, 24077185+free, 57428284 used, 96637872 buff/cache KiB Swap: 999420 total, 999420 free,0 used. 33477683+avail Mem We've seen the following bug many times since we introduced new machines running Ubuntu 18. Wasn't an issue older machines running Ubuntu 16. Three different machines are affected, so it's rather not a hardware issue. | detected buffer overflow in strcat | [ cut here ] | kernel BUG at /build/linux-6ZmFRN/linux-4.15.0/lib/string.c:1052! | invalid opcode: [#1] SMP PTI | Modules linked in: [...] | Hardware name: Dell Inc. PowerEdge R740/0923K0, BIOS 1.6.11 11/20/2018 | RIP: 0010:fortify_panic+0x13/0x22 | [...] | Call Trace: | smb21_set_oplock_level+0x147/0x1a0 [cifs] | smb3_set_oplock_level+0x22/0x90 [cifs] | smb2_set_fid+0x76/0xb0 [cifs] | cifs_new_fileinfo+0x259/0x390 [cifs] | ? smb2_get_lease_key+0x40/0x40 [cifs] | ? cifs_new_fileinfo+0x259/0x390 [cifs] | cifs_open+0x3db/0x8d0 [cifs] | [...] (Full dmesg output attached) After hitting this bug there are many cifs related dmesg entries, processes lock up and eventually the systems freezes. The share is mounted using: //server/share /mnt/server/ cifs defaults,auto,iocharset=utf8,noperm,file_mode=0777,dir_mode=0777,credentials=/root/passwords/share,domain=myDomain,uid=myUser,gid=10513,mfsymlinks Currently we're testing the cifs mount options "cache=none" as the bug seems to be oplock related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828495] Autopkgtest regression report (qemu/1:3.1+dfsg-2ubuntu3.3)
All autopkgtests for the newly accepted qemu (1:3.1+dfsg-2ubuntu3.3) 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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Committed Status in libvirt source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Won't Fix Status in qemu source package in Cosmic: Won't Fix Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Committed Status in libvirt source package in Eoan: Fix Released Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM
I can confirm that the CONFIG_LOCK_DOWN_KERNEL config is enabled in the
4.15.0-1039.39 linux-kvm kernel in bionic-proposed. Thanks!
** Tags added: verification-done-bionic
--
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/1811981
Title:
test_410_config_lock_down_kernel in ubuntu_kernel_security test failed
on B/C/D KVM
Status in QA Regression Testing:
Fix Released
Status in ubuntu-kernel-tests:
In Progress
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-kvm source package in Bionic:
Fix Committed
Status in linux-kvm source package in Cosmic:
Fix Committed
Status in linux-kvm source package in Disco:
Fix Committed
Bug description:
== SRU Justification ==
Security team requires the CONFIG_LOCK_DOWN_KERNEL to be enabled in all of
our kernels.
== Test ==
Test kernels could be found here:
https://people.canonical.com/~phlin/kernel/lp-1811981-kvm-lockdown/
This issue can be verified with test_410_config_lock_down_kernel
test from q-r-t, the test will pass with the patched kernel.
== Regression Potential ==
Low, we already have this config enabled in the generic kernel.
== Original bug report ==
Kernel Version: 4.15.0-44.47
This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
Power8 and Power9
FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
Ensure kernel efi lockdown is enabled
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2668, in
test_410_config_lock_down_kernel
self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel
config
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1811981/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836809] [NEW] segfault when CCD are present in two different HOG services
Public bug reported: Hello everyone, We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Attachment added: "callstacks.txt" https://bugs.launchpad.net/bugs/1836809/+attachment/5277531/+files/callstacks.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1836809 Title: segfault when CCD are present in two different HOG services Status in bluez package in Ubuntu: New Bug description: Hello everyone, We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1836809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836760] Re: ixgbe{vf} - Physical Function gets IRQ when VF checks link state
** Changed in: linux (Ubuntu Ff-series)
Status: Fix Released => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836760
Title:
ixgbe{vf} - Physical Function gets IRQ when VF checks link state
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Status in linux source package in FF-Series:
Fix Committed
Bug description:
[Impact]
* Intel NICs that are SR-IOV capable and are managed by ixgbe driver presents
a potentially harmful behavior when the ixgbevf-managed VFs (Virtual Functions)
perform an ethtool link check. The ixgbevf driver issues a mailbox command in
the ethtool link state handler, which induces one IRQ in the PF (Physical
Function) per link check.
* This was reported as a sort of "denial-of-service" from a guest; due to
some link check loop running inside a guest with PCI-PT of a ixgbevf-managed
VF, the host received a huge amount of IRQs causing soft-lockups.
* The patch proposed in this SRU request fix this behavior by relying in the
saved link state (obtained in the ixgbevf's watchdog routine) instead of
issuing a mailbox command to the PF in every link state check request. The
commit is available on Linus tree: 1e1b0c658d9b ("ixgbevf: Use cached link
state instead of re-reading the value for ethtool")
http://git.kernel.org/linus/1e1b0c658d9b
[Test case]
Reproducing the behavior is pretty simple; having a machine with an
Intel NIC managed by ixgbe, proceed with the following steps:
a) Create one or more VFs
(echo 1 > /sys/class/net//device/sriov_numvfs)
b) In a different terminal, monitor the non-TxRx PF IRQs:
(watch -n1 "cat /proc/interrupts | grep | grep -v Tx")
c) Run "ethtool " in a loop
Without the hereby proposed patch, the PF IRQs will increase.
[Regression potential]
The patch scope is restricted to ixgbevf ethtool link-check procedure,
and was developed by the vendor itself. Being a self-contained patch
affecting only this driver's ethtool handler, the worst potential
regression would be a wrong link state report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836760/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL
** Changed in: linux-firmware (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Cosmic) Status: In Progress => Won't Fix ** Changed in: linux-firmware (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1835879 Title: Intel Wireless-AC 9462/9560 not supported on ICL Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-osp1 package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux-firmware source package in Cosmic: Won't Fix Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux-firmware source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Won't Fix Bug description: [Impact] Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake platforms. [Fix] Two changes from Intel maintained backport-iwlwifi repository are necessary to add device ID/configs to iwlwifi driver. [Test] Verified on hardware 9462/9560 on IceLake/CometLake platforms. [Regression Potential] Low. These changes are part of the series to enable 9462/9560 on CometLake/IceLake platforms that don't have the support originally. = Original Bug Description = Intel Wireless-AC 9462/9560 on CML was previously enabled via bug 1833065, bug 1834415 and bug 1834464. However on ICL, it fails to startup with following error messages with kernel v5.2-rc7: iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338 iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3 iwlwifi :00:14.3: Failed to start RT ucode: -5 iwlwifi :00:14.3: Collecting data: trigger 16 fired. iwlwifi :00:14.3: Firmware not running - cannot dump error iwlwifi :00:14.3: Failed to run INIT ucode: -5 Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at the moment) with no luck. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836806] Re: Two crashes on raid0 error path (during a member device removal)
** Also affects: linux (Ubuntu Eoan) Importance: Medium Assignee: Guilherme G. Piccoli (gpiccoli) Status: Confirmed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Released ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => Won't Fix ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836806 Title: Two crashes on raid0 error path (during a member device removal) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Fix Released Bug description: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813721] Re: SECURITY_SELINUX_DISABLE should be enable on X s390x
Turning this option off is only significant in 4.12 kernels and newer,
where the LSM hooks make use of __ro_after_init if
CONFIG_SECURITY_SELINUX_DISABLE is disabled.
Per the discussion on the kernel-team list
(https://lists.ubuntu.com/archives/kernel-team/2019-July/102026.html),
I've made sure the test won't fail for kernels older than 4.12
regardless of whether CONFIG_SECURITY_SELINUX_DISABLE is set or unset:
https://git.launchpad.net/qa-regression-
testing/commit/?id=3a1752a5f5743fb330336b4d01f0a6a4200fe31f
Thanks.
** Changed in: qa-regression-testing
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/1813721
Title:
SECURITY_SELINUX_DISABLE should be enable on X s390x
Status in QA Regression Testing:
Fix Released
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description:
== SRU Justification ==
Security team requires the CONFIG_SECURITY_SELINUX_DISABLE should be
enabled in all of our kernels.
Currently it's not enabled for s390x in Xenial. And causing the
test_081_config_security_selinux_disable test in ubuntu_kernel_security
test suite complaining about this:
==
FAIL: test_081_config_security_selinux_disable
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2158, in
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: SECURITY_SELINUX_DISABLE option was expected to be set in
the kernel config
== Test ==
A test kernel could be found here:
https://people.canonical.com/~phlin/kernel/lp-1813721-s390x-selinux/
This issue can be verified with a q-r-t test:
test_081_config_security_selinux_disable, the test will pass with the
patched kernel.
test_081_config_security_selinux_disable (__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315) ...
(skipped: l) ok
== Regression Potential ==
Low, we already have this config enabled in all kernels except this
specific Xenial s390x.
--
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-142-generic 4.4.0-142.168
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDmesg:
Date: Tue Jan 29 02:30:42 2019
HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3
crashkernel=196M
RelatedPackageVersions:
linux-restricted-modules-4.4.0-142-generic N/A
linux-backports-modules-4.4.0-142-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1813721/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836806] [NEW] Two crashes on raid0 error path (during a member device removal)
Public bug reported: TBD ** Affects: linux (Ubuntu) Importance: Medium Assignee: Guilherme G. Piccoli (gpiccoli) Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Affects: linux (Ubuntu Eoan) Importance: Medium Assignee: Guilherme G. Piccoli (gpiccoli) Status: Confirmed ** Tags: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836806 Title: Two crashes on raid0 error path (during a member device removal) Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Disco: New Status in linux source package in Eoan: Confirmed Bug description: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836801] 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-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: Confirmed Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID A
[Kernel-packages] [Bug 1685794] Re: Boot delayed for about 90 seconds until 'random: crng init done'
Just to add more ubuntu/debian specific details because this includes a kernel config options that was changed from vanilla kernel and that not everyone may agree with and I had missed myself. This seem to have started when crg_init was changed in the kernel to 1 to fix a CVE. This caused a change in behavior and after that fix when calls to getrandom in the early boot were done it was now properly blocking until it was securely initialized. As described in this systemd discussion https://github.com/systemd/systemd/issues/4167 This caused software that were calling getrandom without GRND_NONBLOCK to now properly block. The problem is if any of those software did not require this, e.g. they could use urandom instead or did not even need a random number in the first place, and were called during the early boot process they would cause the system to hang unnecessarily. This was what happened with "plymouth/fontconfig/libuuid (generating uuids requires randomness). That specific UUID generation can be prevented, and util-linux 2.32 makes the getrandom call non-blocking." which was fixed in util-linux 2.32 and was causing my long boot delay before the login screen appeared. Now I was using 18.04 LTS which still has util-linux 2.31 so the reason kernel 5.1.x was working when kernel 4.19 did not, was not because the source of the problem was really in the kernel, it was because of this change in the ubuntu/debian kernel that is not in the vanilla kernel https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1823754 which sets CONFIG_RANDOM_TRUST_CPU=y instead of N on the vanilla kernel. This kernel option was added in 4.19 by Theodore Ts'o and must have landed somewhere in the ubuntu/debian kernel between 4.19 and 5.1 https://lwn.net/Articles/760121/ This is why a kernel who has CONFIG_RANDOM_TRUST_CPU=y and software that wrongly call a blocking getrandom during boot time where crg_init is still 1, i.e. random number generator is not fully initialized, does not block if they have a CPU that support random number generation like many modern CPU. Note that there is an associated boot option to change this manually random.trust_cpu=on/off It seems like there might have been a time where the crg_init patch landed and the CONFIG_RANDOM_TRUST_CPU=y was not there yet that may have caused issues, but at least the state of the packages in 18.04 does not have this problem for me. Nevertheless, while I will probably keep CONFIG_RANDOM_TRUST_CPU=y I can see some hardware where this might not be an appropriate default. Therefore if someone wants to run with CONFIG_RANDOM_TRUST_CPU=N, and util-linux < 2.32 or any other software that calls a blocking getrandom at boot when it is not required, the only options left are software that were suggested here like rng-tools and haveged to attempt to speed up the kernel entropy generation. In addition, to libuuid I also saw that the Bluetooth library may have also at one point using wrongly a blocking getrandom call which seems to be the problem of the original poster. However, I do not have this library on this machine so I cannot verify but assume at some point that library must have also been fixed down the line. Otherwise, any of the fixes above would also work. ** Bug watch added: github.com/systemd/systemd/issues #4167 https://github.com/systemd/systemd/issues/4167 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685794 Title: Boot delayed for about 90 seconds until 'random: crng init done' Status in linux package in Ubuntu: Confirmed Status in broadcom-sta package in Debian: New Bug description: Shortened dmesg output, notice the unnaturally long delay before crng init finishes: [8.533630] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [8.542239] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card1/input18 [8.542313] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card1/input19 [8.542382] input: HDA Intel PCH Dock Line Out as /devices/pci:00/:00:1b.0/sound/card1/input20 [8.542449] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card1/input21 [8.544240] cdc_ether 2-6:2.0 usb0: register 'cdc_ether' at usb-:00:14.0-6, CDC Ethernet Device, 02:1e:10:1f:00:00 [8.544271] usbcore: registered new interface driver cdc_ether [8.637660] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [8.654022] input: HP WMI hotkeys as /devices/virtual/input/input22 [8.688226] cdc_ether 2-6:2.0 enp0s20u6c2: renamed from usb0 [8.713288] iwlwifi :02:00.0 wlo1: renamed from wlan0 [9.804308] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input23 [ 98.327857] random: crng init done [ 98.330072] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [
[Kernel-packages] [Bug 1836801] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277507/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Audi
[Kernel-packages] [Bug 1836801] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277508/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Audi
[Kernel-packages] [Bug 1836801] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277509/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd
[Kernel-packages] [Bug 1836760] Re: ixgbe{vf} - Physical Function gets IRQ when VF checks link state
SRU request was sent to kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2019-July/102282.html
Cheers,
Guilherme
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Cosmic)
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/1836760
Title:
ixgbe{vf} - Physical Function gets IRQ when VF checks link state
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in FF-Series:
Fix Released
Bug description:
[Impact]
* Intel NICs that are SR-IOV capable and are managed by ixgbe driver presents
a potentially harmful behavior when the ixgbevf-managed VFs (Virtual Functions)
perform an ethtool link check. The ixgbevf driver issues a mailbox command in
the ethtool link state handler, which induces one IRQ in the PF (Physical
Function) per link check.
* This was reported as a sort of "denial-of-service" from a guest; due to
some link check loop running inside a guest with PCI-PT of a ixgbevf-managed
VF, the host received a huge amount of IRQs causing soft-lockups.
* The patch proposed in this SRU request fix this behavior by relying in the
saved link state (obtained in the ixgbevf's watchdog routine) instead of
issuing a mailbox command to the PF in every link state check request. The
commit is available on Linus tree: 1e1b0c658d9b ("ixgbevf: Use cached link
state instead of re-reading the value for ethtool")
http://git.kernel.org/linus/1e1b0c658d9b
[Test case]
Reproducing the behavior is pretty simple; having a machine with an
Intel NIC managed by ixgbe, proceed with the following steps:
a) Create one or more VFs
(echo 1 > /sys/class/net//device/sriov_numvfs)
b) In a different terminal, monitor the non-TxRx PF IRQs:
(watch -n1 "cat /proc/interrupts | grep | grep -v Tx")
c) Run "ethtool " in a loop
Without the hereby proposed patch, the PF IRQs will increase.
[Regression potential]
The patch scope is restricted to ixgbevf ethtool link-check procedure,
and was developed by the vendor itself. Being a self-contained patch
affecting only this driver's ethtool handler, the worst potential
regression would be a wrong link state report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836760/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836802] Re: Bionic update: upstream stable patchset 2019-07-16
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ upstream stable patchset 2019-07-16
-upstream stable patchset 2019-07-16
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v4.14.81, v4.18.19,
+ v4.14.82, v4.18.20
+
+ from git://git.kernel.org/
+
+ mtd: spi-nor: fsl-quadspi: fix read error for flash size larger than 16MB
+ spi: bcm-qspi: switch back to reading flash using smaller chunks
+ bcache: trace missed reading by cache_missed
+ bcache: fix miss key refill->end in writeback
+ hwmon: (pmbus) Fix page count auto-detection.
+ jffs2: free jffs2_sb_info through jffs2_kill_sb()
+ cpufreq: conservative: Take limits changes into account properly
+ pcmcia: Implement CLKRUN protocol disabling for Ricoh bridges
+ parisc: Fix address in HPMC IVA
+ parisc: Fix map_pages() to not overwrite existing pte entries
+ parisc: Fix exported address of os_hpmc handler
+ ALSA: hda - Add quirk for ASUS G751 laptop
+ ALSA: hda - Fix headphone pin config for ASUS G751
+ ALSA: hda - Add mic quirk for the Lenovo G50-30 (17aa:3905)
+ ALSA: ca0106: Disable IZD on SB0570 DAC to fix audio pops
+ x86/xen: Fix boot loader version reported for PVH guests
+ x86/corruption-check: Fix panic in memory_corruption_check() when boot option
without value is provided
+ ARM: dts: exynos: Disable pull control for MAX8997 interrupts on Origen
+ bpf: do not blindly change rlimit in reuseport net selftest
+ Revert "perf tools: Fix PMU term format max value calculation"
+ xfrm: policy: use hlist rcu variants on insert
+ perf vendor events intel: Fix wrong filter_band* values for uncore events
+ sched/fair: Fix the min_vruntime update logic in dequeue_entity()
+ perf tools: Fix use of alternatives to find JDIR
+ perf cpu_map: Align cpu map synthesized events properly.
+ x86/fpu: Remove second definition of fpu in __fpu__restore_sig()
+ net: qla3xxx: Remove overflowing shift statement
+ selftests: ftrace: Add synthetic event syntax testcase
+ i2c: rcar: cleanup DMA for all kinds of failure
+ locking/lockdep: Fix debug_locks off performance problem
+ ataflop: fix error handling during setup
+ swim: fix cleanup on setup error
+ nfp: devlink port split support for 1x100G CXP NIC
+ tun: Consistently configure generic netdev params via rtnetlink
+ s390/sthyi: Fix machine name validity indication
+ hwmon: (pwm-fan) Set fan speed to 0 on suspend
+ lightnvm: pblk: fix two sleep-in-atomic-context bugs
+ spi: spi-ep93xx: Use dma_data_direction for ep93xx_spi_dma_{finish,prepare}
+ perf tools: Free temporary 'sys' string in read_event_files()
+ perf tools: Cleanup trace-event-info 'tdata' leak
+ perf strbuf: Match va_{add,copy} with va_end
+ cpupower: Fix coredump on VMWare
+ mmc: sdhci-pci-o2micro: Add quirk for O2 Micro dev 0x8620 rev 0x01
+ iwlwifi: pcie: avoid empty free RB queue
+ iwlwifi: mvm: clear HW_RESTART_REQUESTED when stopping the interface
+ x86/olpc: Indicate that legacy PC XO-1 platform should not register RTC
+ ACPI / processor: Fix the return value of acpi_processor_ids_walk()
+ cpufreq: dt: Try freeing static OPPs only if we have added them
+ mtd: rawnand: atmel: Fix potential NULL pointer dereference
+ signal: Introduce COMPAT_SIGMINSTKSZ for use in compat_sys_sigaltstack
+ Bluetooth: btbcm: Add entry for BCM4335C0 UART bluetooth
+ x86: boot: Fix EFI stub alignment
+ pinctrl: qcom: spmi-mpp: Fix err handling of pmic_mpp_set_mux
+ brcmfmac: fix for proper support of 160MHz bandwidth
+ net: phy: phylink: ensure the carrier is off when starting phylink
+ block, bfq: correctly charge and reset entity service in all cases
+ kprobes: Return error if we fail to reuse kprobe instead of BUG_ON()
+ ACPI / LPSS: Add alternative ACPI HIDs for Cherry Trail DMA controllers
+ pinctrl: qcom: spmi-mpp: Fix drive strength setting
+ pinctrl: spmi-mpp: Fix pmic_mpp_config_get() to be compliant
+ pinctrl: ssbi-gpio: Fix pm8xxx_pin_config_get() to be compliant
+ net: dsa: mv88e6xxx: Fix writing to a PHY page.
+ iwlwifi: mvm: fix BAR seq ctrl reporting
+ ixgbevf:
[Kernel-packages] [Bug 1836801] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277500/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioD
[Kernel-packages] [Bug 1836801] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277497/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture:
[Kernel-packages] [Bug 1836801] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277505/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: a
[Kernel-packages] [Bug 1836801] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277502/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 A
[Kernel-packages] [Bug 1836801] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277501/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: a
[Kernel-packages] [Bug 1836801] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277498/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64
[Kernel-packages] [Bug 1836801] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277503/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: a
[Kernel-packages] [Bug 1836801] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277496/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDev
[Kernel-packages] [Bug 1836801] [NEW] BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba
Public bug reported: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1756 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d93551ad-a8f2-44f5-93ad-2ff3a972a488 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. XPS 15 9550 Package: linux-signed ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-155-generic root=UUID=97caa0b1-7590-4cb2-8da8-d6a8af773f58 ro ProcVersionSignature: Ubuntu 4.4.0-155.182-ge
[Kernel-packages] [Bug 1836801] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277495/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64
[Kernel-packages] [Bug 1836801] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277504/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architect
[Kernel-packages] [Bug 1836801] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277499/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioD
[Kernel-packages] [Bug 1836801] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1836801/+attachment/5277506/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1836801 Title: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: [Description] The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running with the proposed kernel 4.4.0-155.182-generic will cause kernel trace[1]. However the wifi function works properly with the kernel 4.4.0-154.181 [Steps to Reproduce] 1. Install ubuntu xenial, enable the proposed repository, and update the system with "sudo apt-get dist-upgrade" 2. nmcli d wifi rescan 3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi interface is wlp2s0), you will see the available SSIDs in your environment. 4. nmcli d wifi connect ifname wlp2s0 name TEST_CON [Expected Result] The AP is connected [Actual Result] You will get the message: "Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.)." and the kernel trace from /var/log/syslog[1] Sometime the system hangs when connecting to a wifi AP. [More Information] [1] The kernel trace log hecking kernel ring buffer for brcmfmac messages: kern :info : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface driver brcmfmac kern :warn : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 kern :info : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core snd_hda_core snd_hwd ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc btintel videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_netif_rx+0x73/0xa0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac] kern :warn : [Tue Jul 16 10:08:01 2019] [] brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac] [Known Affected Platforms] Dell XPS 15 9550 (CID 201606-22346) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 16 15:57:36 2019 InstallationDate: Installed on 2018-01-11 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64
[Kernel-packages] [Bug 1836802] [NEW] Bionic update: upstream stable patchset 2019-07-16
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-16
Ported from the following upstream stable releases:
v4.14.81, v4.18.19,
v4.14.82, v4.18.20
from git://git.kernel.org/
mtd: spi-nor: fsl-quadspi: fix read error for flash size larger than 16MB
spi: bcm-qspi: switch back to reading flash using smaller chunks
bcache: trace missed reading by cache_missed
bcache: fix miss key refill->end in writeback
hwmon: (pmbus) Fix page count auto-detection.
jffs2: free jffs2_sb_info through jffs2_kill_sb()
cpufreq: conservative: Take limits changes into account properly
pcmcia: Implement CLKRUN protocol disabling for Ricoh bridges
parisc: Fix address in HPMC IVA
parisc: Fix map_pages() to not overwrite existing pte entries
parisc: Fix exported address of os_hpmc handler
ALSA: hda - Add quirk for ASUS G751 laptop
ALSA: hda - Fix headphone pin config for ASUS G751
ALSA: hda - Add mic quirk for the Lenovo G50-30 (17aa:3905)
ALSA: ca0106: Disable IZD on SB0570 DAC to fix audio pops
x86/xen: Fix boot loader version reported for PVH guests
x86/corruption-check: Fix panic in memory_corruption_check() when boot option
without value is provided
ARM: dts: exynos: Disable pull control for MAX8997 interrupts on Origen
bpf: do not blindly change rlimit in reuseport net selftest
Revert "perf tools: Fix PMU term format max value calculation"
xfrm: policy: use hlist rcu variants on insert
perf vendor events intel: Fix wrong filter_band* values for uncore events
sched/fair: Fix the min_vruntime update logic in dequeue_entity()
perf tools: Fix use of alternatives to find JDIR
perf cpu_map: Align cpu map synthesized events properly.
x86/fpu: Remove second definition of fpu in __fpu__restore_sig()
net: qla3xxx: Remove overflowing shift statement
selftests: ftrace: Add synthetic event syntax testcase
i2c: rcar: cleanup DMA for all kinds of failure
locking/lockdep: Fix debug_locks off performance problem
ataflop: fix error handling during setup
swim: fix cleanup on setup error
nfp: devlink port split support for 1x100G CXP NIC
tun: Consistently configure generic netdev params via rtnetlink
s390/sthyi: Fix machine name validity indication
hwmon: (pwm-fan) Set fan speed to 0 on suspend
lightnvm: pblk: fix two sleep-in-atomic-context bugs
spi: spi-ep93xx: Use dma_data_direction for ep93xx_spi_dma_{finish,prepare}
perf tools: Free temporary 'sys' string in read_event_files()
perf tools: Cleanup trace-event-info 'tdata' leak
perf strbuf: Match va_{add,copy} with va_end
cpupower: Fix coredump on VMWare
mmc: sdhci-pci-o2micro: Add quirk for O2 Micro dev 0x8620 rev 0x01
iwlwifi: pcie: avoid empty free RB queue
iwlwifi: mvm: clear HW_RESTART_REQUESTED when stopping the interface
x86/olpc: Indicate that legacy PC XO-1 platform should not register RTC
ACPI / processor: Fix the return value of acpi_processor_ids_walk()
cpufreq: dt: Try freeing static OPPs only if we have added them
mtd: rawnand: atmel: Fix potential NULL pointer dereference
signal: Introduce COMPAT_SIGMINSTKSZ for use in compat_sys_sigaltstack
Bluetooth: btbcm: Add entry for BCM4335C0 UART bluetooth
x86: boot: Fix EFI stub alignment
pinctrl: qcom: spmi-mpp: Fix err handling of pmic_mpp_set_mux
brcmfmac: fix for proper support of 160MHz bandwidth
net: phy: phylink: ensure the carrier is off when starting phylink
block, bfq: correctly charge and reset entity service in all cases
kprobes: Return error if we fail to reuse kprobe instead of BUG_ON()
ACPI / LPSS: Add alternative ACPI HIDs for Cherry Trail DMA controllers
pinctrl: qcom: spmi-mpp: Fix drive strength setting
pinctrl: spmi-mpp: Fix pmic_mpp_config_get() to be compliant
pinctrl: ssbi-gpio: Fix pm8xxx_pin_config_get() to be compliant
net: dsa: mv88e6xxx: Fix writing to a PHY page.
iwlwifi: mvm: fix BAR seq ctrl reporting
ixgbevf: VF2VF TCP RSS
ath10k: schedule hardware restart if WMI command times out
thermal: da9062/61: Prevent hardware access during system suspend
cgroup, netclassid: add a preemption point to write_classid
scsi: esp_scsi: Track residual for PIO transfers
UAPI: ndctl: Fix g++-unsupported initialisation in headers
KVM: nVMX: Clear reserved bits of #DB exit qualification
scsi: megaraid_sas: fix a missing-check bug
RDMA/core: Do not expose unsupported counters
IB/ipoib: Clear IPCB before icmp_send
RDMA/bnxt_re: Fix recursive lock warning in debug kernel
usb: host: ohci-at91: fix request of irq for optional gpio
PCI: mediatek: Fix mtk_pcie_find_port() endpoint/port matching logic
tpm: suppress transmit cmd error lo
[Kernel-packages] [Bug 1828495] Autopkgtest regression report (qemu/1:2.11+dfsg-1ubuntu7.16)
All autopkgtests for the newly accepted qemu (1:2.11+dfsg-1ubuntu7.16) for bionic 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#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/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Committed Status in libvirt source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Won't Fix Status in qemu source package in Cosmic: Won't Fix Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Committed Status in libvirt source package in Eoan: Fix Released Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
I have tested a kernel with _only_ 6c6bc1aee6a61fe7a98196794735849286761a4a "PCI: PM: Skip devices in D0 for suspend-to-idle" reverted. That appears to fix all issues with suspend on this system. I am now attempting to find a minimal patch for restoring functionality. ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=204187 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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in Linux: Unknown 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/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 1836760] Re: ixgbe{vf} - Physical Function gets IRQ when VF checks link state
** Description changed:
- TBA
+ [Impact]
+
+ * Intel NICs that are SR-IOV capable and are managed by ixgbe driver presents
a potentially harmful behavior when the ixgbevf-managed VFs (Virtual Functions)
perform an ethtool link check. The ixgbevf driver issues a mailbox command in
the ethtool link state handler, which induces one IRQ in the PF (Physical
Function) per link check.
+
+ * This was reported as a sort of "denial-of-service" from a guest; due to
some link check loop running inside a guest with PCI-PT of a ixgbevf-managed
VF, the host received a huge amount of IRQs causing soft-lockups.
+
+ * The patch proposed in this SRU request fix this behavior by relying in the
saved link state (obtained in the ixgbevf's watchdog routine) instead of
issuing a mailbox command to the PF in every link state check request. The
commit is available on Linus tree: 1e1b0c658d9b ("ixgbevf: Use cached link
state instead of re-reading the value for ethtool")
+ http://git.kernel.org/linus/1e1b0c658d9b
+
+ [Test case]
+
+ Reproducing the behavior is pretty simple; having a machine with an
+ Intel NIC managed by ixgbe, proceed with the following steps:
+
+ a) Create one or more VFs
+ (echo 1 > /sys/class/net//device/sriov_numvfs)
+
+ b) In a different terminal, monitor the non-TxRx PF IRQs:
+ (watch -n1 "cat /proc/interrupts | grep | grep -v Tx")
+
+ c) Run "ethtool " in a loop
+
+ Without the hereby proposed patch, the PF IRQs will increase.
+
+ [Regression potential]
+
+ The patch scope is restricted to ixgbevf ethtool link-check procedure,
+ and was developed by the vendor itself. Being a self-contained patch
+ affecting only this driver's ethtool handler, the worst potential
+ regression would be a wrong link state report.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836760
Title:
ixgbe{vf} - Physical Function gets IRQ when VF checks link state
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in FF-Series:
Fix Released
Bug description:
[Impact]
* Intel NICs that are SR-IOV capable and are managed by ixgbe driver presents
a potentially harmful behavior when the ixgbevf-managed VFs (Virtual Functions)
perform an ethtool link check. The ixgbevf driver issues a mailbox command in
the ethtool link state handler, which induces one IRQ in the PF (Physical
Function) per link check.
* This was reported as a sort of "denial-of-service" from a guest; due to
some link check loop running inside a guest with PCI-PT of a ixgbevf-managed
VF, the host received a huge amount of IRQs causing soft-lockups.
* The patch proposed in this SRU request fix this behavior by relying in the
saved link state (obtained in the ixgbevf's watchdog routine) instead of
issuing a mailbox command to the PF in every link state check request. The
commit is available on Linus tree: 1e1b0c658d9b ("ixgbevf: Use cached link
state instead of re-reading the value for ethtool")
http://git.kernel.org/linus/1e1b0c658d9b
[Test case]
Reproducing the behavior is pretty simple; having a machine with an
Intel NIC managed by ixgbe, proceed with the following steps:
a) Create one or more VFs
(echo 1 > /sys/class/net//device/sriov_numvfs)
b) In a different terminal, monitor the non-TxRx PF IRQs:
(watch -n1 "cat /proc/interrupts | grep | grep -v Tx")
c) Run "ethtool " in a loop
Without the hereby proposed patch, the PF IRQs will increase.
[Regression potential]
The patch scope is restricted to ixgbevf ethtool link-check procedure,
and was developed by the vendor itself. Being a self-contained patch
affecting only this driver's ethtool handler, the worst potential
regression would be a wrong link state report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836760/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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
It looks like reverting 1bde9ecf018ee646b68258921bf0fa364afda38a fixes
suspend issues when writing devices to /sys/power/pm_test, but also
reverting 6c6bc1aee6a61fe7a98196794735849286761a4a fixes suspend issues
when using standard suspend/resume:
commit 6c6bc1aee6a61fe7a98196794735849286761a4a
Author: Rafael J. Wysocki
Date: Thu Jun 13 23:59:45 2019 +0200
PCI: PM: Skip devices in D0 for suspend-to-idle
BugLink: https://bugs.launchpad.net/bugs/1808957
Patchwork: https://patchwork.kernel.org/patch/10993697/
Commit d491f2b75237 ("PCI: PM: Avoid possible suspend-to-idle issue")
attempted to avoid a problem with devices whose drivers want them to
stay in D0 over suspend-to-idle and resume, but it did not go as far
as it should with that.
Namely, first of all, the power state of a PCI bridge with a
downstream device in D0 must be D0 (based on the PCI PM spec r1.2,
sec 6, table 6-1, if the bridge is not in D0, there can be no PCI
transactions on its secondary bus), but that is not actively enforced
during system-wide PM transitions, so use the skip_bus_pm flag
introduced by commit d491f2b75237 for that.
Second, the configuration of devices left in D0 (whatever the reason)
during suspend-to-idle need not be changed and attempting to put them
into D0 again by force is pointless, so explicitly avoid doing that.
Fixes: d491f2b75237 ("PCI: PM: Avoid possible suspend-to-idle issue")
Reported-by: Kai-Heng Feng
Signed-off-by: Rafael J. Wysocki
Reviewed-by: Mika Westerberg
Tested-by: Kai-Heng Feng
(cherry picked from commit 3e26c5feed2add218046ecf91bab3cfa9bf762a6)
Signed-off-by: Kai-Heng Feng
Acked-by: Timo Aaltonen
Acked-by: Stefan Bader
Signed-off-by: Kleber Sacilotto de Souza
--
You 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 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
Hello quanxian, or anyone else affected, Accepted qemu into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qemu/1:2.11+dfsg- 1ubuntu7.16 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: qemu (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Committed Status in libvirt source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Won't Fix Status in qemu source package in Cosmic: Won't Fix Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Committed Status in libvirt source package in Eoan: Fix Released Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
** Changed in: libvirt (Ubuntu Bionic) Importance: Undecided => Wishlist ** Changed in: libvirt (Ubuntu Cosmic) Importance: Undecided => Wishlist ** Changed in: libvirt (Ubuntu Disco) Importance: Undecided => Wishlist ** Changed in: libvirt (Ubuntu Eoan) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Committed Status in libvirt source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Won't Fix Status in qemu source package in Cosmic: Won't Fix Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Committed Status in libvirt source package in Eoan: Fix Released Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed
also occurs on AWS-disco 5.0.0-1011.12 : amd64 ** Summary changed: - fib related test in net from ubuntu_kernel_selftests failed on C-KVM + fib related test in net from ubuntu_kernel_selftests failed ** Tags added: aws disco sru-20190701 ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-aws (Ubuntu Cosmic) ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Disco) Importance: Undecided Status: New -- 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/1812622 Title: fib related test in net from ubuntu_kernel_selftests failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: New Status in linux source package in Disco: New Status in linux-aws source package in Disco: New Status in linux-kvm source package in Disco: New Bug description: These tests: * fib_tests.sh * fib-onlink-tests.sh * fib_rule_tests.sh All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not supported: selftests: net: fib_tests.sh Single path route test RTNETLINK answers: Operation not supported not ok 1..11 selftests: net: fib_tests.sh [FAIL] selftests: net: fib-onlink-tests.sh Configuring interfaces RTNETLINK answers: Operation not supported not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL] selftests: net: fib_rule_tests.sh RTNETLINK answers: Operation not supported not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL] (works on generic Cosmic kernel) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6 ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17 Uname: Linux 4.18.0-1006-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Mon Jan 21 08:00:22 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/1812622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
Hello quanxian, or anyone else affected, Accepted qemu into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qemu/1:3.1+dfsg- 2ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: qemu (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-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/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Committed Status in libvirt source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Won't Fix Status in qemu source package in Cosmic: Won't Fix Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Committed Status in libvirt source package in Eoan: Fix Released Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
The application of 1bde9ecf018ee646b68258921bf0fa364afda38a appears to have caused https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630 -- 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/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Confirmed 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: New 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: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836202] Re: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1836201 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834891 - phase: Promote to Proposed - phase-changed: Monday, 15. July 2019 13:10 UTC + phase: Testing + phase-changed: Tuesday, 16. July 2019 16:53 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- Nvidia objects not found -- current-driver-5.0.0-1011-gke-d1809-0-amd64 + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836202 Title: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed 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 derivatives: bug 1836201 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834891 phase: Testing phase-changed: Tuesday, 16. July 2019 16:53 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- Nvidia objects not found -- current-driver-5.0.0-1011-gke-d1809-0-amd64 regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
Also reported here: https://bugzilla.kernel.org/show_bug.cgi?id=204187 ** Bug watch added: Linux Kernel Bug Tracker #204187 https://bugzilla.kernel.org/show_bug.cgi?id=204187 -- You 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 1836202] Re: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836202 Title: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in 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 derivatives: bug 1836201 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834891 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 13:10 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync promote-to-updates: Pending -- Nvidia objects not found -- current-driver-5.0.0-1011-gke-d1809-0-amd64 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836202] Re: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing 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/1836202 Title: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in 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 derivatives: bug 1836201 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834891 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 13:10 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync promote-to-updates: Pending -- Nvidia objects not found -- current-driver-5.0.0-1011-gke-d1809-0-amd64 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
I was able to narrow this down to this commit: commit 1bde9ecf018ee646b68258921bf0fa364afda38a Author: Keith Busch Date: Thu May 23 09:27:35 2019 -0600 nvme-pci: Use host managed power state for suspend BugLink: https://bugs.launchpad.net/bugs/1808957 The nvme pci driver prepares its devices for power loss during suspend by shutting down the controllers. The power setting is deferred to pci driver's power management before the platform removes power. The suspend-to-idle mode, however, does not remove power. NVMe devices that implement host managed power settings can achieve lower power and better transition latencies than using generic PCI power settings. Try to use this feature if the platform is not involved with the suspend. If successful, restore the previous power state on resume. Cc: Mario Limonciello Cc: Kai Heng Feng Tested-by: Kai-Heng Feng Tested-by: Mario Limonciello Reviewed-by: Rafael J. Wysocki Reviewed-by: Christoph Hellwig Signed-off-by: Keith Busch Signed-off-by: Sagi Grimberg (cherry picked from commit a0805317252ad9cf09d4a32b0435e165580adf8a) Signed-off-by: Kai-Heng Feng Acked-by: Timo Aaltonen Acked-by: Stefan Bader Signed-off-by: Kleber Sacilotto de Souza -- You 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 1828166] Re: perf top problem on z with Ubuntu 18.04
Hi Klaus, The same version of perf is expected. I was able to reproduce the issue and I can confirm that I see the same behavior as you described even with the patched test kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as low since this happens only while using the perf top tool * and it is known that the commit (above) fixes the problem * and the fix is upstream since 4.19 [Other Info] * current disco and eoan kernels don't show that problem * bisecting result points to above commit * applies cleanly on cosmic, but has a little conflict on bionic (both master-next) _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831268] Re: Ubuntu 19.04: Random SR-IOV issues
This issues is due to a test case bug. Please close. ** Changed in: linux-azure (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1831268 Title: Ubuntu 19.04: Random SR-IOV issues Status in linux-azure package in Ubuntu: Invalid Bug description: No VFs inside the VM. Unfortunately this issue doesn’t have a 100% repro. Sometimes all the VFs are missing, other times a few are available and the rest are missing. The best test case to catch this issue is VERIFY-ENABLE-DISABLE-SRIOV- ON-EXISTING-VM. Comparing the logs between working/not working VMs, the only difference was that these 2 messages were missing from the broken VMs: mlx4_en: rename9: Steering Mode 2 mlx4_en: rename9: Link Up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1831268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836202] Re: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker
** 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 derivatives: bug 1836201 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834891 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 13:10 UTC reason: - promote-to-proposed: Pending -- packages copied to Proposed signed:retry-needed + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync promote-to-updates: Pending -- Nvidia objects not found -- current-driver-5.0.0-1011-gke-d1809-0-amd64 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/1836202 Title: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux 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 derivatives: bug 1836201 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834891 phase: Promote to Proposed phase-changed: Monday, 15. July 2019 13:10 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync promote-to-updates: Pending -- Nvidia objects not found -- current-driver-5.0.0-1011-gke-d1809-0-amd64 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836760] [NEW] ixgbe{vf} - Physical Function gets IRQ when VF checks link state
Public bug reported:
TBA
** Affects: linux (Ubuntu)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: linux (Ubuntu Xenial)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: linux (Ubuntu Bionic)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: linux (Ubuntu Cosmic)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: linux (Ubuntu Disco)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: linux (Ubuntu Eoan)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: linux (Ubuntu Ff-series)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Fix Released
** Tags: sts
** Summary changed:
- ixgbe - Physical Function gets IRQ when VF checks link state
+ ixgbe{vf} - Physical Function gets IRQ when VF checks link state
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Also affects: linux (Ubuntu Ff-series)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Ff-series)
Importance: Undecided => High
** Changed in: linux (Ubuntu Disco)
Importance: Undecided => High
** Changed in: linux (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Ff-series)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Disco)
Status: New => Confirmed
** Changed in: linux (Ubuntu Cosmic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: linux (Ubuntu Ff-series)
Status: New => Confirmed
** Changed in: linux (Ubuntu Ff-series)
Status: Confirmed => 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/1836760
Title:
ixgbe{vf} - Physical Function gets IRQ when VF checks link state
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in FF-Series:
Fix Released
Bug description:
TBA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836760/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
** Tags added: ath10k -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818881] Re: ath10k_pci crashing
** Tags added: ath10k -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818881 Title: ath10k_pci crashing Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias: pci:v168Cd0040sv*sd*bc*sc*i* alias: pci:v168Cd0
[Kernel-packages] [Bug 1836755] 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 1836755 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/1836755 Title: hda/realtek: can't detect external mic on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The external can't be detected when plugging headset in the front audio jack. [Fix] apply the alc891 fixup to set headset-mic and headpphone-mic pins. [Test Case] apply this patch and boot with the kernel, plug the headset-mic and choose headset-mic from popup dialogue, the headset-mic can record sound very well. [Regression Risk] Low. this patch is specific to a dell machine by pin configuration definition. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836755] Re: hda/realtek: can't detect external mic on a Dell machine
** Description changed: - [Expected result] - External microphone can work well + [Impact] + The external can't be detected when plugging headset in the + front audio jack. - [Actual result] - Can not detect external microphone + [Fix] + apply the alc891 fixup to set headset-mic and headpphone-mic pins. + + [Test Case] + apply this patch and boot with the kernel, plug the headset-mic + and choose headset-mic from popup dialogue, the headset-mic can + record sound very well. + + [Regression Risk] + Low. this patch is specific to a dell machine by pin configuration + definition. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836755 Title: hda/realtek: can't detect external mic on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The external can't be detected when plugging headset in the front audio jack. [Fix] apply the alc891 fixup to set headset-mic and headpphone-mic pins. [Test Case] apply this patch and boot with the kernel, plug the headset-mic and choose headset-mic from popup dialogue, the headset-mic can record sound very well. [Regression Risk] Low. this patch is specific to a dell machine by pin configuration definition. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
