[Kernel-packages] [Bug 1811335] Re: ELAN900C:00 04F3:2844 touchscreen doesn't work
To avoid conflict, have to cherry pick one more commit
17ac526824a8 pinctrl: cannonlake: Fix community ordering for H variant
e50d95e2ad12 pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811335
Title:
ELAN900C:00 04F3:2844 touchscreen doesn't work
Status in linux package in Ubuntu:
In Progress
Bug description:
[Impact]
[ELAN900C:00 04F3:2844] doesn't work
[Fix]
It works under kernel v4.19, so after bisect the kernel and got the first bad
commit
e50d95e2ad12 pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H
variant
[Test]
Verified on the DELL machine, the touchscreen works well.
[Regression Potential]
Low, the 2 commits are all
Fixes: a663ccf0fea1 ("pinctrl: intel: Add Intel Cannon Lake PCH-H pin
controller support")
Should be safe to be included.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811335/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811335] [NEW] ELAN900C:00 04F3:2844 touchscreen doesn't work
Public bug reported: [Impact] [ELAN900C:00 04F3:2844] doesn't work [Fix] It works under kernel v4.19, so after bisect the kernel and got the first bad commit e50d95e2ad12 pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant [Test] Verified on the DELL machine, the touchscreen works well. [Regression Potential] ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: 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/1811335 Title: ELAN900C:00 04F3:2844 touchscreen doesn't work Status in linux package in Ubuntu: In Progress Bug description: [Impact] [ELAN900C:00 04F3:2844] doesn't work [Fix] It works under kernel v4.19, so after bisect the kernel and got the first bad commit e50d95e2ad12 pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant [Test] Verified on the DELL machine, the touchscreen works well. [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809870] Re: 2365dd3ca02bbb6d3412404482e1d85752549953 in ubuntu_btrfs_kernel_fixes failed on B
https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/commit/?id=0bf2e4d2ff069e3cdd7e723361c8b28ea47a6508 Test blacklisted for newer kernel. (4330e183c9537df20952d4a9ee142c536fb8ae54 added for newer kernel) ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809870 Title: 2365dd3ca02bbb6d3412404482e1d85752549953 in ubuntu_btrfs_kernel_fixes failed on B Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: Test failed on Bionic, and this patch does exist in Bionic kernel tree. Invoking test 2365dd3ca02bbb6d3412404482e1d85752549953 fix 2365dd3ca02bbb6d3412404482e1d85752549953 btrfs: undo sysfs when open_ctree() fails reproducer: mkfs.btrfs -f /dev/sdb &&mount /dev/sdb /btrfs &&btrfs dev add -f /dev/sdc /btrfs &&umount /btrfs &&wipefs -a /dev/sdc &&mount -o degraded /dev/sdb /btrfs //above mount fails so try with RO mount -o degraded,ro /dev/sdb /btrfs -- sysfs: cannot create duplicate filename '/fs/btrfs/3f48c79e-5ed0-4e87-b189-86e749e503f4' :: Performing full device TRIM /dev/loop1 (512.00MiB) ... mount -o degraded /dev/loop0 /tmp/mnt-2365dd3ca02bbb6d3412404482e1d85752549953 was expected to fail FAIL: 2365dd3ca02bbb6d3412404482e1d85752549953 (ret=1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 20 18:17 seq crw-rw 1 root audio 116, 33 Dec 20 18:17 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Thu Dec 27 07:34:54 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793901] Re: kernel oops in bcache module
We have a reproducer now: $ uname -a Linux ln-sv-infr01 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 3.7T 0 disk ├─sda18:10 512M 0 part /boot/efi └─sda28:20 3.7T 0 part ├─ln--sv--infr01--vg-root 253:00 301G 0 lvm / ├─ln--sv--infr01--vg-swap_1 │ 253:10 976M 0 lvm [SWAP] └─ln--sv--infr01--vg-var 253:20 3.4T 0 lvm └─bcache0 252:00 3.4T 0 disk /var nvme0n1 259:00 1.5T 0 disk └─bcache0 252:00 3.4T 0 disk /var $ sudo fstrim /var # at this point it will immediately fail to kernel panic ... oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793901 Title: kernel oops in bcache module Status in linux package in Ubuntu: Incomplete Bug description: This was on an 18.04.1 install running the 4.15-34 generic kernel image, running from a normal ext4 root device. I had just a short while before created a new bcache device that was mounted but to which no data had been written yet. Then without any apparent particular reason, an apport error popped up to inform of a bcache kernel oops. Crash log was uploaded but no idea how to link it, so I attach it as well. Mostly I would like to know how concerned I should be as after a previous, successful test I wanted to move the whole install to bcache. Ideally, if this is a bug or similar, it would be nice if it could get fixed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 22 18:20:22 2018 HibernationDevice: RESUME=UUID=6bcbe7fa-85b7-4baf-9b69-0558a668bcdd InstallationDate: Installed on 2014-07-29 (1515 days ago) InstallationMedia: It IwConfig: zthnhe3w6d no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=ebbab625-f14e-44ba-84d5-025ed92a5b2a ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-07 (15 days ago) dmi.bios.date: 10/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: Default string dmi.board.name: H170I-PLUS D3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0604:bd10/22/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170I-PLUSD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811200] Re: Add Cavium ThunderX2 SoC UNCORE PMU driver
** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Opinion ** Changed in: linux (Ubuntu Bionic) Status: Opinion => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: New => Incomplete ** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Disco) Status: Incomplete => 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/1811200 Title: Add Cavium ThunderX2 SoC UNCORE PMU driver Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] No driver for PMU of L3 cache controller (L3C) and the DDR4 Memory Controller (DMC) for Cavium ThunderX2 SoC [Test Case] sudo perf stat -a -e \ > uncore_dmc_0/cnt_cycles/,\ > uncore_dmc_0/data_transfers/,\ > uncore_dmc_0/read_txns/,\ > uncore_dmc_0/write_txns/ sleep 1 sudo perf stat -a -e \ > uncore_l3c_0/read_request/,\ > uncore_l3c_0/read_hit/,\ > uncore_l3c_0/inv_request/,\ > uncore_l3c_0/inv_hit/ sleep 1 sudo perf stat -a -e uncore_dmc_0/cnt_cycles/ sleep 1 [Fix] Backport patches 82975c46da perf: Export perf_event_update_userpage (only for bionic) d6310a3f33 Documentation: perf: Add documentation for ThunderX2 PMU uncore driver 69c32972d5 drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver and enable CONFIG_THUNDERX2_PMU=m [Regression Risk] This driver only loaded when CAV901C in ACPI table, lowest risk for other platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804149] Comment bridged from LTC Bugzilla
--- Comment From finne...@us.ibm.com 2019-01-10 21:11 EDT--- In response to >The error messages that belong to the Ops seem to be known and points to a >potential race discussed here: >[RFC,1/1] libiscsi: Fix race between iscsi_xmit_task and iscsi_complete_task >https://patchwork.kernel.org/patch/10501773/ Is there a target date when this race condition will have a fix available to the ubuntu distro ? as this issue has been seen on at lease two different hosts across three (3) different kernels. 4.15.0-15-generic #16-Ubuntuilzlnx4 4.15.0-23-generic #25-Ubuntuilzlnx4,ilabg3 4.15.0-36-generic #39-Ubuntuilabg3 Most recently seen again on Dec 20 17:12 (MST) root@ilabg3:/var/dump/201812201711# ls -lrt total 140732 -rw--- 1 root root 143650157 Dec 20 17:12 dump.201812201711 -rw--- 1 root root452204 Dec 20 17:12 dmesg.201812201711 Reference attached files dmesg.201812201711.txt /var/log/kern.log.3.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804149 Title: Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Michael Finnegan - 2018-11-19 14:14:40 == ---Problem Description--- Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] ---uname output--- Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) ---Debugger--- A debugger is not configured Contact Information = Michael Finnegan/finne...@us.ibm.com Stack trace output: dmesg.201811161956 [1363037.322472] Unable to handle kernel pointer dereference in virtual kernel address space [1363037.322481] Failing address: TEID: 0483 [1363037.322483] Fault in home space mode while using kernel ASCE. [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 P:013d [1363037.322524] Oops: 0004 ilc:3 [#1] SMP [1363037.322529] Modules linked in: iptable_filter binfmt_misc rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 4.15.0-36-generic #39-Ubuntu [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0) [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi] [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 (__iscsi_get_task+0x6/0x18 [libiscsi]) [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [1363037.322589] Krnl GPRS: 02923ce0 0400 [1363037.322591]03ff80277640 0008 788efc00 03ff802777cc [1363037.322592]03ff8027769c 78ce8310 [1363037.322594]f3689800 78ce83a2 03ff80272e8e 02923c90 [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6 brcl 15,3ff80272010 03ff8027262a: c0f4377b brcl 15,3ff80279520 #03ff80272630: c004 brcl 0,3ff80272630 >03ff80272636: eb012078006a asi 120(%r2),1 03ff8027263c: c0f43772 brcl 15,3ff80279520 03ff80272642: 0707 bcr 0,%r7 03ff80272644: 0707 bcr 0,%r7 03ff80272646: 0707 bcr 0,%r7 [1363037.322618] Call Trace: [1363037.322621] ([<03ff80272ec6>] iscsi_xmit_task+0x86/0x138 [libiscsi]) [1363037.322625] [<03ff8027769c>] iscsi_data_xmit+0x44c/0x548 [libiscsi] [1363037.322636] [<03ff802777cc>] iscsi_xmitworker+0x34/0x58 [libiscsi] [1363037.322642] [<001918f2>] process_one_work+0x262/0x4d8 [1363037.322644] [<00191bc0>] worker_thread+0x58/0x4e8 [1363037.322648] [<00198d24>] kthread+0x14c/0x168 [1363037.322652] [<008e3eb2>] kernel_thread_starter+0xa/0x10 [1363037.322654] [<008e3ea8>] kernel_thread_starter+0x0/0x10 [1363037.322655] Last Breaking-Event-Address: [13630
[Kernel-packages] [Bug 1804149] dmesg.201812201711.txt
--- Comment on attachment From finne...@us.ibm.com 2019-01-10 21:09 EDT--- dmesg.201812201711.txt file attached. ** Attachment added: "dmesg.201812201711.txt" https://bugs.launchpad.net/bugs/1804149/+attachment/5228411/+files/dmesg.201812201711.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804149 Title: Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Michael Finnegan - 2018-11-19 14:14:40 == ---Problem Description--- Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] ---uname output--- Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) ---Debugger--- A debugger is not configured Contact Information = Michael Finnegan/finne...@us.ibm.com Stack trace output: dmesg.201811161956 [1363037.322472] Unable to handle kernel pointer dereference in virtual kernel address space [1363037.322481] Failing address: TEID: 0483 [1363037.322483] Fault in home space mode while using kernel ASCE. [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 P:013d [1363037.322524] Oops: 0004 ilc:3 [#1] SMP [1363037.322529] Modules linked in: iptable_filter binfmt_misc rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 4.15.0-36-generic #39-Ubuntu [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0) [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi] [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 (__iscsi_get_task+0x6/0x18 [libiscsi]) [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [1363037.322589] Krnl GPRS: 02923ce0 0400 [1363037.322591]03ff80277640 0008 788efc00 03ff802777cc [1363037.322592]03ff8027769c 78ce8310 [1363037.322594]f3689800 78ce83a2 03ff80272e8e 02923c90 [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6 brcl 15,3ff80272010 03ff8027262a: c0f4377b brcl 15,3ff80279520 #03ff80272630: c004 brcl 0,3ff80272630 >03ff80272636: eb012078006a asi 120(%r2),1 03ff8027263c: c0f43772 brcl 15,3ff80279520 03ff80272642: 0707 bcr 0,%r7 03ff80272644: 0707 bcr 0,%r7 03ff80272646: 0707 bcr 0,%r7 [1363037.322618] Call Trace: [1363037.322621] ([<03ff80272ec6>] iscsi_xmit_task+0x86/0x138 [libiscsi]) [1363037.322625] [<03ff8027769c>] iscsi_data_xmit+0x44c/0x548 [libiscsi] [1363037.322636] [<03ff802777cc>] iscsi_xmitworker+0x34/0x58 [libiscsi] [1363037.322642] [<001918f2>] process_one_work+0x262/0x4d8 [1363037.322644] [<00191bc0>] worker_thread+0x58/0x4e8 [1363037.322648] [<00198d24>] kthread+0x14c/0x168 [1363037.322652] [<008e3eb2>] kernel_thread_starter+0xa/0x10 [1363037.322654] [<008e3ea8>] kernel_thread_starter+0x0/0x10 [1363037.322655] Last Breaking-Event-Address: [1363037.322657] [<03ff80272e88>] iscsi_xmit_task+0x48/0x138 [libiscsi] [1363037.322658] [1363037.322660] Kernel panic - not syncing: Fatal exception in interrupt Oops output: Oops: 0004 ilc:3 [#1] SMP *Additional Instructions for Michael Finnegan/finne...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1804149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://lau
[Kernel-packages] [Bug 1804149] kern.log.3.txt
--- Comment on attachment From finne...@us.ibm.com 2019-01-10 21:10 EDT--- kern.log.3.txt file attached ** Attachment added: "kern.log.3.txt" https://bugs.launchpad.net/bugs/1804149/+attachment/5228412/+files/kern.log.3.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804149 Title: Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Michael Finnegan - 2018-11-19 14:14:40 == ---Problem Description--- Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] ---uname output--- Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) ---Debugger--- A debugger is not configured Contact Information = Michael Finnegan/finne...@us.ibm.com Stack trace output: dmesg.201811161956 [1363037.322472] Unable to handle kernel pointer dereference in virtual kernel address space [1363037.322481] Failing address: TEID: 0483 [1363037.322483] Fault in home space mode while using kernel ASCE. [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 P:013d [1363037.322524] Oops: 0004 ilc:3 [#1] SMP [1363037.322529] Modules linked in: iptable_filter binfmt_misc rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 4.15.0-36-generic #39-Ubuntu [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0) [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi] [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 (__iscsi_get_task+0x6/0x18 [libiscsi]) [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [1363037.322589] Krnl GPRS: 02923ce0 0400 [1363037.322591]03ff80277640 0008 788efc00 03ff802777cc [1363037.322592]03ff8027769c 78ce8310 [1363037.322594]f3689800 78ce83a2 03ff80272e8e 02923c90 [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6 brcl 15,3ff80272010 03ff8027262a: c0f4377b brcl 15,3ff80279520 #03ff80272630: c004 brcl 0,3ff80272630 >03ff80272636: eb012078006a asi 120(%r2),1 03ff8027263c: c0f43772 brcl 15,3ff80279520 03ff80272642: 0707 bcr 0,%r7 03ff80272644: 0707 bcr 0,%r7 03ff80272646: 0707 bcr 0,%r7 [1363037.322618] Call Trace: [1363037.322621] ([<03ff80272ec6>] iscsi_xmit_task+0x86/0x138 [libiscsi]) [1363037.322625] [<03ff8027769c>] iscsi_data_xmit+0x44c/0x548 [libiscsi] [1363037.322636] [<03ff802777cc>] iscsi_xmitworker+0x34/0x58 [libiscsi] [1363037.322642] [<001918f2>] process_one_work+0x262/0x4d8 [1363037.322644] [<00191bc0>] worker_thread+0x58/0x4e8 [1363037.322648] [<00198d24>] kthread+0x14c/0x168 [1363037.322652] [<008e3eb2>] kernel_thread_starter+0xa/0x10 [1363037.322654] [<008e3ea8>] kernel_thread_starter+0x0/0x10 [1363037.322655] Last Breaking-Event-Address: [1363037.322657] [<03ff80272e88>] iscsi_xmit_task+0x48/0x138 [libiscsi] [1363037.322658] [1363037.322660] Kernel panic - not syncing: Fatal exception in interrupt Oops output: Oops: 0004 ilc:3 [#1] SMP *Additional Instructions for Michael Finnegan/finne...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1804149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packag
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Should it work on ubuntu 18.10? I try to install 390 driver. After this i run command sudo prime-select nvidia and restart system. But GUI no work anymore. In kernel log i see errors. My video card is geforce 750M Jan 11 02:38:17 lblack kernel: [ 121.613281] nvidia: loading out-of-tree module taints kernel. Jan 11 02:38:17 lblack kernel: [ 121.613290] nvidia: module license 'NVIDIA' taints kernel. Jan 11 02:38:17 lblack kernel: [ 121.613290] Disabling lock debugging due to kernel taint Jan 11 02:38:17 lblack kernel: [ 121.616641] nvidia: module verification failed: signature and/or required key missing - tainting kernel Jan 11 02:38:17 lblack kernel: [ 121.623093] nvidia-nvlink: Nvlink Core is being initialized, major device number 238 Jan 11 02:38:17 lblack kernel: [ 121.623677] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 (using threaded interrupts) Jan 11 02:38:17 lblack kernel: [ 121.625479] NVRM: API mismatch: the client has the version 410.66, but Jan 11 02:38:17 lblack kernel: [ 121.625479] NVRM: this kernel module has the version 390.87. Please Jan 11 02:38:17 lblack kernel: [ 121.625479] NVRM: make sure that this kernel module and all NVIDIA driver Jan 11 02:38:17 lblack kernel: [ 121.625479] NVRM: components have the same version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-
[Kernel-packages] [Bug 1690085]
So it would appear that also for me the issue is not completely resolved by setting "Typical Power idle". One of my two (identical) servers reported this morning that a bunch of processes had blocked for more than 120s: (I cut out a lot of other info like call traces, also these are just 4 examples but there's way more): > [1094614.681444] INFO: task md1_raid1:301 blocked for more than 120 seconds. > [1094614.681902] INFO: task fail2ban-server:1095 blocked for more than 120 > seconds. > [1094614.682226] INFO: task mysqld:1319 blocked for more than 120 seconds. > [1094614.682447] INFO: task ntpd:1653 blocked for more than 120 seconds. All the output occurred in the same 3 ms. Interestingly, the server had not crashed because of this. I did reboot it though, just in case. Meanwhile, still no word from AMD.. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks ---
[Kernel-packages] [Bug 1811259] Re: 4.20 kernel on s390x VM crashes
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Tags added: disco ** Also affects: linux (Ubuntu Disco) Importance: High Status: Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811259 Title: 4.20 kernel on s390x VM crashes Status in linux package in Ubuntu: Triaged Status in linux source package in Disco: Triaged Bug description: Booting with 4.20.0-2-generic on a s390x 2 CPU VM we hit a panic: [0.394835] Linux version 4.20.0-2-generic (buildd@bos02-s390x-015) (gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)) #3-Ubuntu SMP Thu Jan 3 18:43:01 UTC 2019 (Ubuntu 4.20.0-2.3-generic 4.20.0) [0.394838] setup.289988: Linux is running under KVM in 64-bit mode [0.394846] setup.b050d0: The maximum memory size is 2048MB [0.394866] numa.196305: NUMA mode: plain [0.394893] cpu.33a262: 2 configured CPUs, 0 standby CPUs [0.394999] Write protected kernel read-only data: 10464k [0.395034] Zone ranges: [0.395035] DMA [mem 0x-0x7fff] [0.395037] Normal empty [0.395038] Movable zone start for each node [0.395039] Early memory node ranges [0.395041] node 0: [mem 0x-0x7fff] [0.395042] Initmem setup node 0 [mem 0x-0x7fff] [0.413802] percpu: Embedded 25 pages/cpu @(ptrval) s62208 r8192 d32000 u102400 [0.413824] Built 1 zonelists, mobility grouping on. Total pages: 516096 [0.413825] Policy zone: DMA [0.413827] Kernel command line: root=LABEL=cloudimg-rootfs [0.450276] Memory: 2034164K/2097152K available (8116K kernel code, 1079K rwdata, 2344K rodata, 992K init, 772K bss, 62988K reserved, 0K cma-reserved) [0.450283] random: get_random_u64 called from kmem_cache_open+0x4c/0x4f0 with crng_init=0 [0.450432] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1 [0.450434] ftrace: allocating 27385 entries in 107 pages [0.473325] rcu: Hierarchical RCU implementation. [0.473327] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3. [0.473328]Tasks RCU enabled. [0.473329] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [0.473330] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3 [0.475371] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3 [0.475402] clocksource: tod: mask: 0x max_cycles: 0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns [0.475558] printk: console [ttyS1] enabled [0.475623] pid_max: default: 32768 minimum: 301 [0.475658] LSM: Security Framework initializing [0.475660] Yama: becoming mindful. [0.475677] AppArmor: AppArmor initialized [0.476134] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) [0.476352] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) [0.476370] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes) [0.476377] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes) [0.476726] rcu: Hierarchical SRCU implementation. [0.476927] smp: Bringing up secondary CPUs ... [0.477181] smp: Brought up 1 node, 2 CPUs [0.477549] devtmpfs: initialized [0.477882] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 1911260446275 ns [0.477902] futex hash table entries: 1024 (order: 6, 262144 bytes) [0.478105] NET: Registered protocol family 16 [0.478134] audit: initializing netlink subsys (disabled) [0.478183] audit: type=2000 audit(1547122707.960:1): state=initialized audit_enabled=0 res=1 [0.478222] Spectre V2 mitigation: execute trampolines [0.479205] HugeTLB registered 1.00 MiB page size, pre-allocated 0 pages [0.479623] SCSI subsystem initialized [0.479856] NetLabel: Initializing [0.479858] NetLabel: domain hash size = 128 [0.479859] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [0.479871] NetLabel: unlabeled traffic allowed by default [0.507362] VFS: Disk quotas dquot_6.6.0 [0.507378] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [0.507486] AppArmor: AppArmor Filesystem Enabled [0.507847] NET: Registered protocol family 2 [0.507976] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes) [0.507994] TCP established hash table entries: 16384 (order: 5, 131072 bytes) [0.508126] TCP bind hash table entries: 16384 (order: 6, 262144 bytes) [0.508235] TCP: Hash tables configured (established 16384 bind 16384) [0.508269] UDP hash table entries: 1024 (order: 3, 32768 bytes) [0.508287] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[Kernel-packages] [Bug 1811277] Re: GCE: RAID6_PQ module adds boot latency - can RAID6_PQ be provided as a module
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811277 Title: GCE: RAID6_PQ module adds boot latency - can RAID6_PQ be provided as a module Status in linux package in Ubuntu: Triaged Bug description: Google reports: For a n1-standard-2 with ubuntu-1604, we spend around 600 milliseconds during boot on computing the best raid6 recovery algorithm seen in the following lines of the kernel logs: ... [ 2.216022] raid6: sse2x1 gen() 8570 MB/s [ 2.264029] raid6: sse2x1 xor() 6467 MB/s [ 2.312030] raid6: sse2x2 gen() 10602 MB/s [ 2.360021] raid6: sse2x2 xor() 6999 MB/s [ 2.412028] raid6: sse2x4 gen() 12483 MB/s [ 2.464022] raid6: sse2x4 xor() 8607 MB/s [ 2.516024] raid6: avx2x1 gen() 16712 MB/s [ 2.568020] raid6: avx2x1 xor() 12050 MB/s [ 2.620019] raid6: avx2x2 gen() 19393 MB/s [ 2.672024] raid6: avx2x2 xor() 12406 MB/s [ 2.724034] raid6: avx2x4 gen() 22330 MB/s [ 2.776029] raid6: avx2x4 xor() 15196 MB/s [ 2.780440] raid6: using algorithm avx2x4 gen() 22330 MB/s [ 2.786035] raid6: xor() 15196 MB/s, rmw enabled [ 2.791196] raid6: using avx2x2 recovery algorithm ... This raid6 computation is a result of including the raid6_pq module statically. Based on the output of `lsmod`, is there any reason this couldn't just be used as a module? ryanrose@ryanrose-boottimes-ubuntu16-test:~$ lsmod Module Size Used by ... btrfs 1101824 0 raid10 49152 0 raid456 143360 0 async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_xor,async_pq,raid456,async_memcpy,async_raid6_recov xor 24576 2 async_xor,btrfs raid6_pq 118784 4 async_pq,btrfs,raid456,async_raid6_recov raid1 40960 0 raid0 20480 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798615] Re: suspend does not lock in 18.04
Confirming, issue is resolved for me (OP). Sorry can't say exactly when the behavior changed, but now it's all good. thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798615 Title: suspend does not lock in 18.04 Status in linux package in Ubuntu: Incomplete Bug description: To reproduce from the command-line (this is ubuntu 18.04): % gsettings set org.gnome.desktop.screensaver ubuntu-lock-on-suspend true % gsettings get org.gnome.desktop.screensaver ubuntu-lock-on-suspend true % systemctl suspend Now the monitors go black and report "no signal" (good), and it will stay that way for hours (good) ... but if I tap "shift" key a few times, Ubuntu 18.04 comes back without asking my password. (I expected rather that the system would be locked, i.e. I should see a dialog box that would require a password before anything else!) Same thing if I suspend by using the upper-right-of-screen "power" icon (click-and-hold, then click on the suspend icon). Same thing if I let 20 minutes go by. (A msg comes up ~~ "system will suspend soon...", and it does suspend, but doesn't lock). I have left the ubuntu-lock-on-suspend setting at "true" through several re-boots, but it still doesn't take effect. I get the same behavior whether ubuntu-lock-on-suspend is set to "true" or "false". Other info: % wmctrl -m Name: GNOME Shell Class: N/A PID: N/A Window manager's "showing the desktop" mode: N/A % lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic % uname -a Linux ucbvax 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I just upgraded from 16.04 a couple of weeks ago. I think (90%) it was locking in 16.04, but now not locking in 18.04. If I click on the upper-right-of-screen padlock icon, then the system does lock (password required). While it's locked in that way, I can click on the upper-right-of- screen "suspend" (from drop-down), and then my system is both suspended and locked. But the question is ... How can I make my system lock (automatically) every time a "suspend" happens? (Or even "every time kbd and mouse are idle for 15 minutes"?) Please advise. thanks --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 7633 F pulseaudio /dev/snd/controlC1: ubuntu 7633 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp2s0no wireless extensions. enp7s5no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-29-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/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99X EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A99XEVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798615/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810130] Re: ic2-HTIX5288
Not working. V5.0RC_1 - also not -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810130 Title: ic2-HTIX5288 Status in linux package in Ubuntu: Confirmed Bug description: touchpad not working Ubuntu Disco Dingo (development branch) WINBOOK 13 ProblemType: Bug DistroRelease: Ubuntu 19.04 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 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: docmint2172 F pulseaudio /dev/snd/controlC1: docmint2172 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 31 00:55:26 2018 InstallationDate: Installed on 2018-12-30 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181230) MachineType: AXDIA International GmbH WINBOOK 13 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=ea66942b-3d65-4c18-a99e-d02e31358a42 ro recovery nomodeset i8042.nomux=1 i8042.reset RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2017 dmi.bios.vendor: WINBOOK 13 dmi.bios.version: 1.6 dmi.board.asset.tag: Default string dmi.board.name: K132 dmi.board.vendor: AXDIA International GmbH dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnWINBOOK13:bvr1.6:bd11/27/2017:svnAXDIAInternationalGmbH:pnWINBOOK13:pvrDefaultstring:rvnAXDIAInternationalGmbH:rnK132:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: WINBOOK 13 dmi.product.sku: WINBOOK13-K132-02 dmi.product.version: Default string dmi.sys.vendor: AXDIA International GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811277] Re: GCE: RAID6_PQ module adds boot latency - can RAID6_PQ be provided as a module
** Summary changed: - GCE: RAID6_PQ module adds boot latency - can RAID6_PQ be made a DKMS + GCE: RAID6_PQ module adds boot latency - can RAID6_PQ be provided as a module -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811277 Title: GCE: RAID6_PQ module adds boot latency - can RAID6_PQ be provided as a module Status in linux package in Ubuntu: Incomplete Bug description: Google reports: For a n1-standard-2 with ubuntu-1604, we spend around 600 milliseconds during boot on computing the best raid6 recovery algorithm seen in the following lines of the kernel logs: ... [ 2.216022] raid6: sse2x1 gen() 8570 MB/s [ 2.264029] raid6: sse2x1 xor() 6467 MB/s [ 2.312030] raid6: sse2x2 gen() 10602 MB/s [ 2.360021] raid6: sse2x2 xor() 6999 MB/s [ 2.412028] raid6: sse2x4 gen() 12483 MB/s [ 2.464022] raid6: sse2x4 xor() 8607 MB/s [ 2.516024] raid6: avx2x1 gen() 16712 MB/s [ 2.568020] raid6: avx2x1 xor() 12050 MB/s [ 2.620019] raid6: avx2x2 gen() 19393 MB/s [ 2.672024] raid6: avx2x2 xor() 12406 MB/s [ 2.724034] raid6: avx2x4 gen() 22330 MB/s [ 2.776029] raid6: avx2x4 xor() 15196 MB/s [ 2.780440] raid6: using algorithm avx2x4 gen() 22330 MB/s [ 2.786035] raid6: xor() 15196 MB/s, rmw enabled [ 2.791196] raid6: using avx2x2 recovery algorithm ... This raid6 computation is a result of including the raid6_pq module statically. Based on the output of `lsmod`, is there any reason this couldn't just be used as a module? ryanrose@ryanrose-boottimes-ubuntu16-test:~$ lsmod Module Size Used by ... btrfs 1101824 0 raid10 49152 0 raid456 143360 0 async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_xor,async_pq,raid456,async_memcpy,async_raid6_recov xor 24576 2 async_xor,btrfs raid6_pq 118784 4 async_pq,btrfs,raid456,async_raid6_recov raid1 40960 0 raid0 20480 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811277] 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 1811277 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/1811277 Title: GCE: RAID6_PQ module adds boot latency - can RAID6_PQ be provided as a module Status in linux package in Ubuntu: Incomplete Bug description: Google reports: For a n1-standard-2 with ubuntu-1604, we spend around 600 milliseconds during boot on computing the best raid6 recovery algorithm seen in the following lines of the kernel logs: ... [ 2.216022] raid6: sse2x1 gen() 8570 MB/s [ 2.264029] raid6: sse2x1 xor() 6467 MB/s [ 2.312030] raid6: sse2x2 gen() 10602 MB/s [ 2.360021] raid6: sse2x2 xor() 6999 MB/s [ 2.412028] raid6: sse2x4 gen() 12483 MB/s [ 2.464022] raid6: sse2x4 xor() 8607 MB/s [ 2.516024] raid6: avx2x1 gen() 16712 MB/s [ 2.568020] raid6: avx2x1 xor() 12050 MB/s [ 2.620019] raid6: avx2x2 gen() 19393 MB/s [ 2.672024] raid6: avx2x2 xor() 12406 MB/s [ 2.724034] raid6: avx2x4 gen() 22330 MB/s [ 2.776029] raid6: avx2x4 xor() 15196 MB/s [ 2.780440] raid6: using algorithm avx2x4 gen() 22330 MB/s [ 2.786035] raid6: xor() 15196 MB/s, rmw enabled [ 2.791196] raid6: using avx2x2 recovery algorithm ... This raid6 computation is a result of including the raid6_pq module statically. Based on the output of `lsmod`, is there any reason this couldn't just be used as a module? ryanrose@ryanrose-boottimes-ubuntu16-test:~$ lsmod Module Size Used by ... btrfs 1101824 0 raid10 49152 0 raid456 143360 0 async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_xor,async_pq,raid456,async_memcpy,async_raid6_recov xor 24576 2 async_xor,btrfs raid6_pq 118784 4 async_pq,btrfs,raid456,async_raid6_recov raid1 40960 0 raid0 20480 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811277] [NEW] GCE: RAID6_PQ module adds boot latency - can RAID6_PQ be made a DKMS
Public bug reported: Google reports: For a n1-standard-2 with ubuntu-1604, we spend around 600 milliseconds during boot on computing the best raid6 recovery algorithm seen in the following lines of the kernel logs: ... [ 2.216022] raid6: sse2x1 gen() 8570 MB/s [ 2.264029] raid6: sse2x1 xor() 6467 MB/s [ 2.312030] raid6: sse2x2 gen() 10602 MB/s [ 2.360021] raid6: sse2x2 xor() 6999 MB/s [ 2.412028] raid6: sse2x4 gen() 12483 MB/s [ 2.464022] raid6: sse2x4 xor() 8607 MB/s [ 2.516024] raid6: avx2x1 gen() 16712 MB/s [ 2.568020] raid6: avx2x1 xor() 12050 MB/s [ 2.620019] raid6: avx2x2 gen() 19393 MB/s [ 2.672024] raid6: avx2x2 xor() 12406 MB/s [ 2.724034] raid6: avx2x4 gen() 22330 MB/s [ 2.776029] raid6: avx2x4 xor() 15196 MB/s [ 2.780440] raid6: using algorithm avx2x4 gen() 22330 MB/s [ 2.786035] raid6: xor() 15196 MB/s, rmw enabled [ 2.791196] raid6: using avx2x2 recovery algorithm ... This raid6 computation is a result of including the raid6_pq module statically. Based on the output of `lsmod`, is there any reason this couldn't just be used as a module? ryanrose@ryanrose-boottimes-ubuntu16-test:~$ lsmod Module Size Used by ... btrfs 1101824 0 raid10 49152 0 raid456 143360 0 async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_xor,async_pq,raid456,async_memcpy,async_raid6_recov xor 24576 2 async_xor,btrfs raid6_pq 118784 4 async_pq,btrfs,raid456,async_raid6_recov raid1 40960 0 raid0 20480 0 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Terry Rudd (terrykrudd) 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/1811277 Title: GCE: RAID6_PQ module adds boot latency - can RAID6_PQ be made a DKMS Status in linux package in Ubuntu: New Bug description: Google reports: For a n1-standard-2 with ubuntu-1604, we spend around 600 milliseconds during boot on computing the best raid6 recovery algorithm seen in the following lines of the kernel logs: ... [ 2.216022] raid6: sse2x1 gen() 8570 MB/s [ 2.264029] raid6: sse2x1 xor() 6467 MB/s [ 2.312030] raid6: sse2x2 gen() 10602 MB/s [ 2.360021] raid6: sse2x2 xor() 6999 MB/s [ 2.412028] raid6: sse2x4 gen() 12483 MB/s [ 2.464022] raid6: sse2x4 xor() 8607 MB/s [ 2.516024] raid6: avx2x1 gen() 16712 MB/s [ 2.568020] raid6: avx2x1 xor() 12050 MB/s [ 2.620019] raid6: avx2x2 gen() 19393 MB/s [ 2.672024] raid6: avx2x2 xor() 12406 MB/s [ 2.724034] raid6: avx2x4 gen() 22330 MB/s [ 2.776029] raid6: avx2x4 xor() 15196 MB/s [ 2.780440] raid6: using algorithm avx2x4 gen() 22330 MB/s [ 2.786035] raid6: xor() 15196 MB/s, rmw enabled [ 2.791196] raid6: using avx2x2 recovery algorithm ... This raid6 computation is a result of including the raid6_pq module statically. Based on the output of `lsmod`, is there any reason this couldn't just be used as a module? ryanrose@ryanrose-boottimes-ubuntu16-test:~$ lsmod Module Size Used by ... btrfs 1101824 0 raid10 49152 0 raid456 143360 0 async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_xor,async_pq,raid456,async_memcpy,async_raid6_recov xor 24576 2 async_xor,btrfs raid6_pq 118784 4 async_pq,btrfs,raid456,async_raid6_recov raid1 40960 0 raid0 20480 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750479] Re: 'perf record' does not work
** Changed in: linux (Ubuntu) Status: Expired => 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/1750479 Title: 'perf record' does not work Status in linux package in Ubuntu: Confirmed Bug description: $ perf archive perf: 'archive' is not a perf-command. See 'perf --help'. $ perf --help usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS] The most commonly used perf commands are: annotateRead perf.data (created by perf record) and display annotated code archive Create archive with object files with build-ids found in perf.data file <- bench General framework for benchmark suites buildid-cache Manage build-id cache. buildid-listList the buildids in a perf.data file c2c Shared Data C2C/HITM Analyzer. config Get and set variables in a configuration file. dataData file related processing diffRead perf.data files and display the differential profile evlist List the event names in a perf.data file ftrace simple wrapper for kernel's ftrace functionality inject Filter to augment the events stream with additional information kallsymsSearches running kernel for symbols kmemTool to trace/measure kernel memory properties kvm Tool to trace/measure kvm guest os listList all symbolic event types lockAnalyze lock events mem Profile memory accesses record Run a command and record its profile into perf.data report Read perf.data (created by perf record) and display the profile sched Tool to trace/measure scheduler properties (latencies) script Read perf.data (created by perf record) and display trace output statRun a command and gather performance counter statistics testRuns sanity tests. timechart Tool to visualize total system behavior during a workload top System profiling tool. probe Define new dynamic tracepoints trace strace inspired tool See 'perf help COMMAND' for more information on a specific command. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-tools-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sbarcomb 2227 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Feb 19 20:53:27 2018 HibernationDevice: RESUME=UUID=ac3f108f-4494-4f48-ae8c-fbab8a509ffc InstallationDate: Installed on 2017-10-19 (123 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IwConfig: lono wireless extensions. enp5s0no wireless extensions. tun0 no wireless extensions. MachineType: Alienware Aurora-R4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2013 dmi.bios.vendor: Alienware dmi.bios.version: A11 dmi.board.name: 07JNH0 dmi.board.vendor: Alienware dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: 00 dmi.modalias: dmi:bvnAlienware:bvrA11:bd11/26/2013:svnAlienware:pnAurora-R4:pvr00:rvnAlienware:rn07JNH0:rvrA02:cvnAlienware:ct3:cvr00: dmi.product.family: 0 dmi.product.name: Aurora-R4 dmi.product.version: 00 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive
** Description changed:
[Impact]
- * Users may experience cpu hard lockups when performing
- rigorous writes to NVMe drives.
+ * Users may experience cpu hard lockups when performing
+rigorous writes to NVMe drives.
- * The fix addresses an scheduling issue in the original
- implementation of wbt/writeback throttling
+ * The fix addresses an scheduling issue in the original
+implementation of wbt/writeback throttling
- * The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
- contention and thundering herd issue in wbt_wait"),
- plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
- waking of tasks").
+ * The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
+contention and thundering herd issue in wbt_wait"),
+plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
+waking of tasks").
- * There are additional commits to help with a cleaner
- backport and future maintenance:
- - Cosmic: total of 8 clean cherry picks.
- - Bionic: total of 13 commits, 9 clean cherry-picks
- and 4 backports, which are just changes to context
- lines (i.e. refresh) without any functional changes
- in the backport itself.
+ * Plus a few dependency commits for the second fix.
+
+ * Backports are trivial: mainly replace rq_wait_inc_below()
+with the equivalent atomic_inc_below(), and maintain the
+__wbt_done() signature, both due to the lack of commit
+a79050434b45 ("blk-rq-qos: refactor out common elements
+of blk-wbt"), that changes lots of other/unrelated code.
[Test Case]
- * This command has been reported to reproduce the problem:
+ * This command has been reported to reproduce the problem:
- $ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
+$ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
128
- * It generates stack traces as below in the original kernel,
- and does not generate them in the modified/patched kernel.
+ * It generates stack traces as below in the original kernel,
+and does not generate them in the modified/patched kernel.
- * The user/reporter verified the test kernel with these patches
- resolved the problem.
+ * The user/reporter verified the test kernel with these patches
+resolved the problem.
- * The developer verified in 2 systems (4-core and 24-core but
- no NVMe) for regressions, and no error messages were logged
- to dmesg.
+ * The developer verified in 2 systems (4-core and 24-core but
+no NVMe) for regressions, and no error messages were logged
+to dmesg.
[Regression Potential]
- * The commits have been verified for fixes in later commits in
- linux-next as of 2019-01-08 and all known fix commits are in.
+ * The regression potential is contained within writeback
+throttling mechanism (block/blk-wbt.*).
- * The regression potential is mostly contained in the writeback
- throttling (block/blk-wbt.*), as almost all of the 13 patches
- change exclusively that, except for 4 of them (2 of which are
- sysfs):
-
- - blk-rq-qos: refactor out common elements of blk-wbt (block/)
- - block: Protect less code with sysfs_lock in blk_{un,}register_queue()
(blk-sysfs.c)
- - block: Protect less code with sysfs_lock in blk_{un,}register_queue()
(blk-{mq-}sysfs.c)
- - block: pass struct request instead of struct blk_issue_stat to wbt
(block/, still mostly blk-wbt.*)
+ * The commits have been verified for fixes in later commits in
+linux-next as of 2019-01-08 and all known fix commits are in.
[Other Info]
- * Alternatively, it is probably possible to introduce just the
- two commits that fix this with some changes to their code in
- the backport, but since the 'blk-rq-qos: refactor ..' commit
- may become a dependency for many additional/future fixes, it
- seemed interesting to pull it in earlier in the 18.04 cycle.
-
- * The problem has been introduced with the blk-wbt mechanism,
- in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
- so only Bionic and Cosmic needs this.
+ * The problem has been introduced with the blk-wbt mechanism,
+in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
+so only Bionic and Cosmic needs this.
[Stack Traces]
[ 393.628647] NMI watchdog: Watchdog detected hard LOCKUP on cpu 30
...
[ 393.628704] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic
#21-Ubuntu
...
[ 393.628720] Call Trace:
[ 393.628721]
[ 393.628724] enqueue_task_fair+0x6c/0x7f0
[ 393.628726] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
[ 393.628728] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
[ 393.628731] activate_task+0x57/0xc0
[ 393.628735] ? sched_clock+0x9/0x10
[ 393.628736] ? sched_clock+0x9/0x10
[ 393.628738] ttwu_do_activate+0x49/0x90
[ 393.628739] try_to_wake_up+0x1df/0x490
[ 393.628741] default_wake_function+0x12/0x20
[ 393.628743] autoremove_wake_function+0x12/0
[Kernel-packages] [Bug 1729736]
Created attachment 143032 dmesg from thinkpad x1 extreme / GTX 1050 Ti on kernel 4.20 with discrete only graphics Not sure if that helps with the diagnostics, but on the same Thinkpad X1 Extreme laptop with "Discrete only" BIOS setting, lspci works fine, X starts and works, but there's a timeout logged by nouveau. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729736 Title: 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10 (Artful)' : - Linux kernel 4.13.0-16 from 'Ubuntu 17.10 (Artful)' systematically fails (1 CPU stuck). - Linux kernel 4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel- ppa/mainline seems to succeed. See attached kern.log After reboot on Linux kernel 4.13.0-16 with nouveau blacklisted : $ lspci -nn -v -s 1:0.0 01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 1050 Ti Mobile] [1462:11c8] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at de00 (32-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [disabled] [size=128] Expansion ROM at df00 [disabled] [size=512K] Capabilities: Kernel modules: nvidiafb, nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1729736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729736]
Created attachment 143031 dmesg from thinkpad x1 extreme / GTX 1050 Ti on kernel 4.20 with hybrid graphics I may be blind but I haven't seen anyone attaching full dmesg output, sorry if I missed it. The laptop in question is Thinkpad X1 Extreme with NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] (rev a1). It has a BIOS setting to switch between "Hybrid" and "Discrete only" graphics. This dmesg output is from a boot with "Hybrid" graphics, where running 'lspci' hangs and causes the system fans to spin. X server hangs on start too (using modesetting DDX) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729736 Title: 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10 (Artful)' : - Linux kernel 4.13.0-16 from 'Ubuntu 17.10 (Artful)' systematically fails (1 CPU stuck). - Linux kernel 4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel- ppa/mainline seems to succeed. See attached kern.log After reboot on Linux kernel 4.13.0-16 with nouveau blacklisted : $ lspci -nn -v -s 1:0.0 01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 1050 Ti Mobile] [1462:11c8] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at de00 (32-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [disabled] [size=128] Expansion ROM at df00 [disabled] [size=512K] Capabilities: Kernel modules: nvidiafb, nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1729736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function
** Summary changed: - LED's in Hotkey f5, f8 and f11 without function + HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 11 logs, unfortunately the upload did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt Information: This problem was previously discussed on linuxmintusers.de: https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811259] Re: 4.20 kernel on s390x VM crashes
5.0-rc1, no dice: [0.398768] Linux version 5.0.0-rc1+ (ubuntu@ckingvm1) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #1 SMP Thu Jan 10 17:45:01 UTC 2019 [0.398770] setup: Linux is running under KVM in 64-bit mode [0.398778] setup: The maximum memory size is 2048MB [0.398799] numa: NUMA mode: plain [0.398823] cpu: 2 configured CPUs, 0 standby CPUs [0.398925] Write protected kernel read-only data: 10420k [0.398958] Zone ranges: [0.398959] DMA [mem 0x-0x7fff] [0.398961] Normal empty [0.398962] Movable zone start for each node [0.398963] Early memory node ranges [0.398964] node 0: [mem 0x-0x7fff] [0.398965] Initmem setup node 0 [mem 0x-0x7fff] [0.416530] percpu: Embedded 25 pages/cpu @(ptrval) s61696 r8192 d32512 u102400 [0.416551] Built 1 zonelists, mobility grouping on. Total pages: 516096 [0.416552] Policy zone: DMA [0.416553] Kernel command line: root=LABEL=cloudimg-rootfs [0.452308] Memory: 2034240K/2097152K available (8092K kernel code, 1084K rwdata, 2324K rodata, 992K init, 776K bss, 62912K reserved, 0K cma-reserved) [0.452316] random: get_random_u64 called from __kmem_cache_create+0x4c/0x5f0 with crng_init=0 [0.452464] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1 [0.452466] ftrace: allocating 27127 entries in 106 pages [0.475936] rcu: Hierarchical RCU implementation. [0.475938] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3. [0.475939] Tasks RCU enabled. [0.475940] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [0.475941] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3 [0.478033] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3 [0.478069] clocksource: tod: mask: 0x max_cycles: 0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns [0.478241] printk: console [ttyS1] enabled [0.478311] pid_max: default: 32768 minimum: 301 [0.478345] LSM: Security Framework initializing [0.478347] Yama: becoming mindful. [0.478365] AppArmor: AppArmor initialized [0.478805] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) [0.479032] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) [0.479050] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes) [0.479057] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes) [0.479413] rcu: Hierarchical SRCU implementation. [0.479629] smp: Bringing up secondary CPUs ... [0.479884] smp: Brought up 1 node, 2 CPUs [0.480226] devtmpfs: initialized [0.480464] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 1911260446275 ns [0.480486] futex hash table entries: 1024 (order: 6, 262144 bytes) [0.480692] NET: Registered protocol family 16 [0.480721] audit: initializing netlink subsys (disabled) [0.480758] audit: type=2000 audit(1547126955.184:1): state=initialized audit_enabled=0 res=1 [0.480800] Spectre V2 mitigation: execute trampolines [0.481735] HugeTLB registered 1.00 MiB page size, pre-allocated 0 pages [0.482061] SCSI subsystem initialized [0.482269] NetLabel: Initializing [0.482270] NetLabel: domain hash size = 128 [0.482271] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [0.482283] NetLabel: unlabeled traffic allowed by default [0.511560] VFS: Disk quotas dquot_6.6.0 [0.511580] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [0.511690] AppArmor: AppArmor Filesystem Enabled [0.511972] NET: Registered protocol family 2 [0.512106] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes) [0.512127] TCP established hash table entries: 16384 (order: 5, 131072 bytes) [0.512199] TCP bind hash table entries: 16384 (order: 6, 262144 bytes) [0.512381] TCP: Hash tables configured (established 16384 bind 16384) [0.512414] UDP hash table entries: 1024 (order: 3, 32768 bytes) [0.512433] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes) [0.512477] NET: Registered protocol family 1 [0.512483] NET: Registered protocol family 44 [0.512518] Unpacking initramfs... [0.747003] Freeing initrd memory: 15780K [0.747282] kvm-s390: SIE not available [0.747301] hypfs: The hardware system does not support hypfs [0.747310] hypfs: Initialization of hypfs failed with rc=-61 [0.747678] Initialise system trusted keyrings [0.747689] Key type blacklist registered [0.747715] workingset: timestamp_bits=42 max_order=19 bucket_order=0 [0.749162] zbud: loaded [0.749614] squashfs: version 4.0 (2009/01/31) Phillip Lougher [0.749785] fuse init (API version 7.28) [0.773883] Key type asymmetric registered [0.773886] Asymmetric key parser 'x509' registered [0.773900] Block layer SCSI generic (bsg) driver versio
[Kernel-packages] [Bug 1805802] Re: [UBUNTU] qeth: fix length check in SNMP processing
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1805802
Title:
[UBUNTU] qeth: fix length check in SNMP processing
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Bug description:
== SRU Justification ==
The response for a SNMP request can consist of multiple parts,
which the cmd callback stages into a kernel buffer until all
parts have been received. If the callback detects that the
staging buffer provides insufficient space, it bails out with
error.
This processing is buggy for the first part of the response -
while it initially checks for a length of 'data_len', it later
copies an additional amount of
'offsetof(struct qeth_snmp_cmd, data)' bytes.
== Fix ==
9a764c1e5968 ("s390/qeth: fix length check in SNMP processing")
== Regression Potential ==
Low. Changes limited to s390.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Original bug description ==
Description: qeth: fix length check in SNMP processing
Symptom: Undefined behaviour.
Problem: The response for a SNMP request can consist of multiple parts,
which the cmd callback stages into a kernel buffer until all
parts have been received. If the callback detects that the
staging buffer provides insufficient space, it bails out with
error.
This processing is buggy for the first part of the response -
while it initially checks for a length of 'data_len', it later
copies an additional amount of
'offsetof(struct qeth_snmp_cmd, data)' bytes.
Solution: Fix the calculation of 'data_len' for the first part of the
response.
Upstream-ID: 9a764c1e59684c0358e16ccaafd870629f2cfe67
Should be applied to all Ubuntu Releases in Service
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805802/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811259] 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 1811259 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/1811259 Title: 4.20 kernel on s390x VM crashes Status in linux package in Ubuntu: Incomplete Bug description: Booting with 4.20.0-2-generic on a s390x 2 CPU VM we hit a panic: [0.394835] Linux version 4.20.0-2-generic (buildd@bos02-s390x-015) (gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)) #3-Ubuntu SMP Thu Jan 3 18:43:01 UTC 2019 (Ubuntu 4.20.0-2.3-generic 4.20.0) [0.394838] setup.289988: Linux is running under KVM in 64-bit mode [0.394846] setup.b050d0: The maximum memory size is 2048MB [0.394866] numa.196305: NUMA mode: plain [0.394893] cpu.33a262: 2 configured CPUs, 0 standby CPUs [0.394999] Write protected kernel read-only data: 10464k [0.395034] Zone ranges: [0.395035] DMA [mem 0x-0x7fff] [0.395037] Normal empty [0.395038] Movable zone start for each node [0.395039] Early memory node ranges [0.395041] node 0: [mem 0x-0x7fff] [0.395042] Initmem setup node 0 [mem 0x-0x7fff] [0.413802] percpu: Embedded 25 pages/cpu @(ptrval) s62208 r8192 d32000 u102400 [0.413824] Built 1 zonelists, mobility grouping on. Total pages: 516096 [0.413825] Policy zone: DMA [0.413827] Kernel command line: root=LABEL=cloudimg-rootfs [0.450276] Memory: 2034164K/2097152K available (8116K kernel code, 1079K rwdata, 2344K rodata, 992K init, 772K bss, 62988K reserved, 0K cma-reserved) [0.450283] random: get_random_u64 called from kmem_cache_open+0x4c/0x4f0 with crng_init=0 [0.450432] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1 [0.450434] ftrace: allocating 27385 entries in 107 pages [0.473325] rcu: Hierarchical RCU implementation. [0.473327] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3. [0.473328]Tasks RCU enabled. [0.473329] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [0.473330] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3 [0.475371] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3 [0.475402] clocksource: tod: mask: 0x max_cycles: 0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns [0.475558] printk: console [ttyS1] enabled [0.475623] pid_max: default: 32768 minimum: 301 [0.475658] LSM: Security Framework initializing [0.475660] Yama: becoming mindful. [0.475677] AppArmor: AppArmor initialized [0.476134] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) [0.476352] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) [0.476370] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes) [0.476377] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes) [0.476726] rcu: Hierarchical SRCU implementation. [0.476927] smp: Bringing up secondary CPUs ... [0.477181] smp: Brought up 1 node, 2 CPUs [0.477549] devtmpfs: initialized [0.477882] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 1911260446275 ns [0.477902] futex hash table entries: 1024 (order: 6, 262144 bytes) [0.478105] NET: Registered protocol family 16 [0.478134] audit: initializing netlink subsys (disabled) [0.478183] audit: type=2000 audit(1547122707.960:1): state=initialized audit_enabled=0 res=1 [0.478222] Spectre V2 mitigation: execute trampolines [0.479205] HugeTLB registered 1.00 MiB page size, pre-allocated 0 pages [0.479623] SCSI subsystem initialized [0.479856] NetLabel: Initializing [0.479858] NetLabel: domain hash size = 128 [0.479859] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [0.479871] NetLabel: unlabeled traffic allowed by default [0.507362] VFS: Disk quotas dquot_6.6.0 [0.507378] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [0.507486] AppArmor: AppArmor Filesystem Enabled [0.507847] NET: Registered protocol family 2 [0.507976] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes) [0.507994] TCP established hash table entries: 16384 (
[Kernel-packages] [Bug 1804588] Re: Power consumption during s2idle is higher than long idle (Intel SSDPEKKF)
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804588 Title: Power consumption during s2idle is higher than long idle (Intel SSDPEKKF) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: In Progress Bug description: [Impact] On new systems that facilitate s2idle, we observed the power consumption raises higher than long idle does during s2idle with Intel NVMe SSDPEKKF. Short idle: 6 Long idle: 2 S2I: 4.8 [Fix] Windows doesn't put nvme to D3 in modern standby, and uses its own APST feature to do the power management. To leverage its APST feature during s2idle, we can't disable nvme device while suspending, too. So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. prevent nvme from being disabled when suspending. [Test] Verified on the new Intel NVMe, it fixes the power consumption issue with no regression. And the power consumption decreases to 2.8W during s2idle. [Regression Potential] Low, the patches only applied to specific nvme module, and from our test, the system is still stable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1804588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811255] 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 1811255 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811255 Title: perf archive missing Status in linux package in Ubuntu: Incomplete Bug description: Running perf in 16.04 returns: `` usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS] The most commonly used perf commands are: annotateRead perf.data (created by perf record) and display annotated code archive Create archive with object files with build-ids found in perf.data file ... ``` ``` perf version 4.15.18 ``` However `perf archive` returns: ``` perf: 'archive' is not a perf-command. See 'perf --help'. ``` It appears that the archive script is somehow missing from the package. Similar reports can be seen here: * https://stackoverflow.com/questions/42150355/how-do-i-use-a-newer-perf-tool-front-end-with-a-record-from-an-older-perf-versio * https://www.spinics.net/lists/linux-perf-users/msg01294.html Description: Ubuntu 16.04.5 LTS Release: 16.04 linux-tools-4.15.0-43-generic: Installed: 4.15.0-43.46~16.04.1 Candidate: 4.15.0-43.46~16.04.1 Version table: *** 4.15.0-43.46~16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811259] [NEW] 4.20 kernel on s390x VM crashes
Public bug reported: Booting with 4.20.0-2-generic on a s390x 2 CPU VM we hit a panic: [0.394835] Linux version 4.20.0-2-generic (buildd@bos02-s390x-015) (gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)) #3-Ubuntu SMP Thu Jan 3 18:43:01 UTC 2019 (Ubuntu 4.20.0-2.3-generic 4.20.0) [0.394838] setup.289988: Linux is running under KVM in 64-bit mode [0.394846] setup.b050d0: The maximum memory size is 2048MB [0.394866] numa.196305: NUMA mode: plain [0.394893] cpu.33a262: 2 configured CPUs, 0 standby CPUs [0.394999] Write protected kernel read-only data: 10464k [0.395034] Zone ranges: [0.395035] DMA [mem 0x-0x7fff] [0.395037] Normal empty [0.395038] Movable zone start for each node [0.395039] Early memory node ranges [0.395041] node 0: [mem 0x-0x7fff] [0.395042] Initmem setup node 0 [mem 0x-0x7fff] [0.413802] percpu: Embedded 25 pages/cpu @(ptrval) s62208 r8192 d32000 u102400 [0.413824] Built 1 zonelists, mobility grouping on. Total pages: 516096 [0.413825] Policy zone: DMA [0.413827] Kernel command line: root=LABEL=cloudimg-rootfs [0.450276] Memory: 2034164K/2097152K available (8116K kernel code, 1079K rwdata, 2344K rodata, 992K init, 772K bss, 62988K reserved, 0K cma-reserved) [0.450283] random: get_random_u64 called from kmem_cache_open+0x4c/0x4f0 with crng_init=0 [0.450432] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1 [0.450434] ftrace: allocating 27385 entries in 107 pages [0.473325] rcu: Hierarchical RCU implementation. [0.473327] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3. [0.473328] Tasks RCU enabled. [0.473329] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [0.473330] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3 [0.475371] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3 [0.475402] clocksource: tod: mask: 0x max_cycles: 0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns [0.475558] printk: console [ttyS1] enabled [0.475623] pid_max: default: 32768 minimum: 301 [0.475658] LSM: Security Framework initializing [0.475660] Yama: becoming mindful. [0.475677] AppArmor: AppArmor initialized [0.476134] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) [0.476352] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) [0.476370] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes) [0.476377] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes) [0.476726] rcu: Hierarchical SRCU implementation. [0.476927] smp: Bringing up secondary CPUs ... [0.477181] smp: Brought up 1 node, 2 CPUs [0.477549] devtmpfs: initialized [0.477882] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 1911260446275 ns [0.477902] futex hash table entries: 1024 (order: 6, 262144 bytes) [0.478105] NET: Registered protocol family 16 [0.478134] audit: initializing netlink subsys (disabled) [0.478183] audit: type=2000 audit(1547122707.960:1): state=initialized audit_enabled=0 res=1 [0.478222] Spectre V2 mitigation: execute trampolines [0.479205] HugeTLB registered 1.00 MiB page size, pre-allocated 0 pages [0.479623] SCSI subsystem initialized [0.479856] NetLabel: Initializing [0.479858] NetLabel: domain hash size = 128 [0.479859] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [0.479871] NetLabel: unlabeled traffic allowed by default [0.507362] VFS: Disk quotas dquot_6.6.0 [0.507378] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [0.507486] AppArmor: AppArmor Filesystem Enabled [0.507847] NET: Registered protocol family 2 [0.507976] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes) [0.507994] TCP established hash table entries: 16384 (order: 5, 131072 bytes) [0.508126] TCP bind hash table entries: 16384 (order: 6, 262144 bytes) [0.508235] TCP: Hash tables configured (established 16384 bind 16384) [0.508269] UDP hash table entries: 1024 (order: 3, 32768 bytes) [0.508287] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes) [0.508336] NET: Registered protocol family 1 [0.508343] NET: Registered protocol family 44 [0.508374] Unpacking initramfs... [0.742412] Freeing initrd memory: 15824K [0.742685] kvm-s390: SIE not available [0.742706] hypfs.7f5705: The hardware system does not support hypfs [0.742714] hypfs.7a79f0: Initialization of hypfs failed with rc=-61 [0.743110] Initialise system trusted keyrings [0.743119] Key type blacklist registered [0.743140] workingset: timestamp_bits=42 max_order=19 bucket_order=0 [0.744539] zbud: loaded [0.745012] squashfs: version 4.0 (2009/01/31) Phillip Lougher [0.745211] fuse init (API version 7
[Kernel-packages] [Bug 1811254] Re: LED's in Hotkey f5, f8 and f11 without function
** Description changed: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS-mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. - I created 11 logs, but unfortunately it did not work at once: + I created 11 logs, unfortunately the upload did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt Information: This problem was previously discussed on linuxmintusers.de: https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: LED's in Hotkey f5, f8 and f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 11 logs, unfortunately the upload did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt Information: This problem was previously discussed on linuxmintusers.de: https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750479] Re: 'perf record' does not work
@jsalisbury? Why was this originally marked as 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/1750479 Title: 'perf record' does not work Status in linux package in Ubuntu: Expired Bug description: $ perf archive perf: 'archive' is not a perf-command. See 'perf --help'. $ perf --help usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS] The most commonly used perf commands are: annotateRead perf.data (created by perf record) and display annotated code archive Create archive with object files with build-ids found in perf.data file <- bench General framework for benchmark suites buildid-cache Manage build-id cache. buildid-listList the buildids in a perf.data file c2c Shared Data C2C/HITM Analyzer. config Get and set variables in a configuration file. dataData file related processing diffRead perf.data files and display the differential profile evlist List the event names in a perf.data file ftrace simple wrapper for kernel's ftrace functionality inject Filter to augment the events stream with additional information kallsymsSearches running kernel for symbols kmemTool to trace/measure kernel memory properties kvm Tool to trace/measure kvm guest os listList all symbolic event types lockAnalyze lock events mem Profile memory accesses record Run a command and record its profile into perf.data report Read perf.data (created by perf record) and display the profile sched Tool to trace/measure scheduler properties (latencies) script Read perf.data (created by perf record) and display trace output statRun a command and gather performance counter statistics testRuns sanity tests. timechart Tool to visualize total system behavior during a workload top System profiling tool. probe Define new dynamic tracepoints trace strace inspired tool See 'perf help COMMAND' for more information on a specific command. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-tools-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sbarcomb 2227 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Feb 19 20:53:27 2018 HibernationDevice: RESUME=UUID=ac3f108f-4494-4f48-ae8c-fbab8a509ffc InstallationDate: Installed on 2017-10-19 (123 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IwConfig: lono wireless extensions. enp5s0no wireless extensions. tun0 no wireless extensions. MachineType: Alienware Aurora-R4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2013 dmi.bios.vendor: Alienware dmi.bios.version: A11 dmi.board.name: 07JNH0 dmi.board.vendor: Alienware dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: 00 dmi.modalias: dmi:bvnAlienware:bvrA11:bd11/26/2013:svnAlienware:pnAurora-R4:pvr00:rvnAlienware:rn07JNH0:rvrA02:cvnAlienware:ct3:cvr00: dmi.product.family: 0 dmi.product.name: Aurora-R4 dmi.product.version: 00 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811255] Re: perf archive missing
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811255 Title: perf archive missing Status in linux package in Ubuntu: New Bug description: Running perf in 16.04 returns: `` usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS] The most commonly used perf commands are: annotateRead perf.data (created by perf record) and display annotated code archive Create archive with object files with build-ids found in perf.data file ... ``` ``` perf version 4.15.18 ``` However `perf archive` returns: ``` perf: 'archive' is not a perf-command. See 'perf --help'. ``` It appears that the archive script is somehow missing from the package. Similar reports can be seen here: * https://stackoverflow.com/questions/42150355/how-do-i-use-a-newer-perf-tool-front-end-with-a-record-from-an-older-perf-versio * https://www.spinics.net/lists/linux-perf-users/msg01294.html Description: Ubuntu 16.04.5 LTS Release: 16.04 linux-tools-4.15.0-43-generic: Installed: 4.15.0-43.46~16.04.1 Candidate: 4.15.0-43.46~16.04.1 Version table: *** 4.15.0-43.46~16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811255] [NEW] perf archive missing
Public bug reported: Running perf in 16.04 returns: `` usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS] The most commonly used perf commands are: annotateRead perf.data (created by perf record) and display annotated code archive Create archive with object files with build-ids found in perf.data file ... ``` ``` perf version 4.15.18 ``` However `perf archive` returns: ``` perf: 'archive' is not a perf-command. See 'perf --help'. ``` It appears that the archive script is somehow missing from the package. Similar reports can be seen here: * https://stackoverflow.com/questions/42150355/how-do-i-use-a-newer-perf-tool-front-end-with-a-record-from-an-older-perf-versio * https://www.spinics.net/lists/linux-perf-users/msg01294.html Description:Ubuntu 16.04.5 LTS Release:16.04 linux-tools-4.15.0-43-generic: Installed: 4.15.0-43.46~16.04.1 Candidate: 4.15.0-43.46~16.04.1 Version table: *** 4.15.0-43.46~16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1811255 Title: perf archive missing Status in linux-meta package in Ubuntu: New Bug description: Running perf in 16.04 returns: `` usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS] The most commonly used perf commands are: annotateRead perf.data (created by perf record) and display annotated code archive Create archive with object files with build-ids found in perf.data file ... ``` ``` perf version 4.15.18 ``` However `perf archive` returns: ``` perf: 'archive' is not a perf-command. See 'perf --help'. ``` It appears that the archive script is somehow missing from the package. Similar reports can be seen here: * https://stackoverflow.com/questions/42150355/how-do-i-use-a-newer-perf-tool-front-end-with-a-record-from-an-older-perf-versio * https://www.spinics.net/lists/linux-perf-users/msg01294.html Description: Ubuntu 16.04.5 LTS Release: 16.04 linux-tools-4.15.0-43-generic: Installed: 4.15.0-43.46~16.04.1 Candidate: 4.15.0-43.46~16.04.1 Version table: *** 4.15.0-43.46~16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1811255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: 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/1811254 Title: LED's in Hotkey f5, f8 and f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 11 logs, but unfortunately it did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679962] Re: psmouse serio1: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
I have a Lenovo W530 and I am having the same problem as others describe. I found these messages from dmesg: [ 435.029679] psmouse serio1: bad data from KBC - timeout [ 561.787068] psmouse serio1: TrackPoint at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. [ 724.389084] psmouse serio1: TrackPoint at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. [ 734.832316] psmouse serio1: TrackPoint at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. cat /etc/issue Ubuntu 18.04.1 LTS \n \l uname -a Linux w530b 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Priority: "makes computer unusable". For me turning off wifi and back on didn't 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/1679962 Title: psmouse serio1: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Status in linux package in Ubuntu: Confirmed Bug description: 353/5000 Hello, Randomly the touchpad pointer moves to one end of the screen, and we have found that when it does message appears in dmseg: psmouse serio1: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Sometimes it happens after 10 minutes of use, sometimes it happens after 3 or 4 hours. We have tested several computers with touchpad "Hantick", that use the both, the evdev library and the libinput library. It always happens randomly. Thanks, ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alejandrolopez 1678 F pulseaudio /dev/snd/controlC1: alejandrolopez 1678 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 5 09:39:01 2017 HibernationDevice: RESUME=UUID=49104028-270a-4546-b219-b38918f339ba InstallationDate: Installed on 2016-04-30 (339 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SLIMBOOK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic.efi.signed root=UUID=d9619f09-3283-4f88-a9aa-a614f1b40470 ro elevator=noop quiet i8042.noloop i8042.notimeout i8042.nomux psmouse.resolution=1200 psmouse.resetafter=1 psmouse.rate=50 mousedev.xres=1900 mousedev.yres=800 i8042.reset plymouth:debug drm.debug=0xe RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-11-10 (145 days ago) dmi.bios.date: 11/21/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: h dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: dmi.board.vendor: SLIMBOOK dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SLIMBOOK dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrh:bd11/21/2014:svnSLIMBOOK:pn:pvr1.0:rvnSLIMBOOK:rn:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion: dmi.product.name: dmi.product.version: 1.0 dmi.sys.vendor: SLIMBOOK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810457] Re: Update hisilicon SoC-specific drivers
** 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/1810457 Title: Update hisilicon SoC-specific drivers Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream. [Test Case] The Ubuntu server certification suite, which includes network and storage tests. [Fix] Backport the localized driver changes up to v5.0-rc1. [Regression Risk] These changes are restricted to the hns and hisi_sas drivers, which only impact the D05 and D06 server development board platforms. To mitigate this risk, we have explicitly tested the proposed changes on these 2 platforms - changes are staged in ppa:pearl2-team/test. Of course, there is risk that these changes introduced regressions that our testing did not catch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: LED's in Hotkey f5, f8 ans f11 without function
** Description changed: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS-mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. - This is my first bug report to launchpad and I ask for leniency and troubleshooting support. - I have created 11 logs but can only attach one? + This is my first bug report to launchpad and I ask for leniency and + troubleshooting support. - ~$ acpi_listen - button/mute MUTE 0080 K - button/f20 F20 0080 K + I created 11 logs, but unfortunately it did not work at once: - ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' - keycode 71 = (keysym 0xffc2, F5), state = 0x10 - keycode 71 = (keysym 0xffc2, F5), state = 0x10 - keycode 74 = (keysym 0xffc5, F8), state = 0x10 - keycode 74 = (keysym 0xffc5, F8), state = 0x10 - keycode 95 = (keysym 0xffc8, F11), state = 0x10 - keycode 95 = (keysym 0xffc8, F11), state = 0x10 + acpi_listen.txt + apt-cache-policy + dmesg.log + lsb_release + lsinput.log + lspci-vnvn.log + udev-db.txt + version.log + xev keypress test.txt + xkbcomp.txt + xkbmap.txt ** Summary changed: - LED's in Hotkey f5, f8 ans f11 without function + LED's in Hotkey f5, f8 and f11 without function ** Description changed: - Notebook: HP ProBook 470 G5 + Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS-mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 11 logs, but unfortunately it did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt ** Description changed: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS-mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 11 logs, but unfortunately it did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt + + Information: This problem was previously discussed on linuxmintusers.de: + https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: LED's in Hotkey f5, f8 and f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 11 logs, but unfortunately it did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt Information: This problem was previously discussed on linuxmintusers.de: https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: LED's in Hotkey f5, f8 ans f11 without function
** Attachment added: "apt-cache-policy" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+attachment/5228343/+files/apt-cache-policy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: LED's in Hotkey f5, f8 ans f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I have created 11 logs but can only attach one? ~$ acpi_listen button/mute MUTE 0080 K button/f20 F20 0080 K ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: LED's in Hotkey f5, f8 ans f11 without function
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+attachment/5228348/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: LED's in Hotkey f5, f8 ans f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I have created 11 logs but can only attach one? ~$ acpi_listen button/mute MUTE 0080 K button/f20 F20 0080 K ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: LED's in Hotkey f5, f8 ans f11 without function
** Attachment added: "udev-db.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+attachment/5228347/+files/udev-db.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: LED's in Hotkey f5, f8 ans f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I have created 11 logs but can only attach one? ~$ acpi_listen button/mute MUTE 0080 K button/f20 F20 0080 K ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: LED's in Hotkey f5, f8 ans f11 without function
** Attachment added: "acpi_listen.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+attachment/5228342/+files/acpi_listen.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: LED's in Hotkey f5, f8 ans f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I have created 11 logs but can only attach one? ~$ acpi_listen button/mute MUTE 0080 K button/f20 F20 0080 K ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: LED's in Hotkey f5, f8 ans f11 without function
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+attachment/5228349/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: LED's in Hotkey f5, f8 ans f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I have created 11 logs but can only attach one? ~$ acpi_listen button/mute MUTE 0080 K button/f20 F20 0080 K ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: LED's in Hotkey f5, f8 ans f11 without function
** Attachment added: "lsinput.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+attachment/5228346/+files/lsinput.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: LED's in Hotkey f5, f8 ans f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I have created 11 logs but can only attach one? ~$ acpi_listen button/mute MUTE 0080 K button/f20 F20 0080 K ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: LED's in Hotkey f5, f8 ans f11 without function
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+attachment/5228344/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: LED's in Hotkey f5, f8 ans f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I have created 11 logs but can only attach one? ~$ acpi_listen button/mute MUTE 0080 K button/f20 F20 0080 K ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: LED's in Hotkey f5, f8 ans f11 without function
** Attachment added: "xev keypress.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+attachment/5228350/+files/xev%20keypress.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: LED's in Hotkey f5, f8 ans f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I have created 11 logs but can only attach one? ~$ acpi_listen button/mute MUTE 0080 K button/f20 F20 0080 K ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: LED's in Hotkey f5, f8 ans f11 without function
** Attachment added: "xkbcomp.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+attachment/5228351/+files/xkbcomp.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: LED's in Hotkey f5, f8 ans f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I have created 11 logs but can only attach one? ~$ acpi_listen button/mute MUTE 0080 K button/f20 F20 0080 K ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: LED's in Hotkey f5, f8 ans f11 without function
** Attachment added: "lsb_release" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+attachment/5228345/+files/lsb_release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: LED's in Hotkey f5, f8 ans f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I have created 11 logs but can only attach one? ~$ acpi_listen button/mute MUTE 0080 K button/f20 F20 0080 K ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811094] Re: iptables connlimit allows more connections than the limit when using multiple CPUs
** Changed in: linux (Ubuntu Xenial)
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/1811094
Title:
iptables connlimit allows more connections than the limit when using
multiple CPUs
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
* The iptables connection count/limit rules can be breached
with multithreaded network driver/server/client (common)
due to a race in the conncount/connlimit code.
* For example:
# iptables -A INPUT -p tcp -m tcp --syn --dport \
-m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-j DROP
* The fix is a backport from an upstream commit that resolves
the problem (plus dependencies for a cleaner backport) that
address the race condition:
commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
collection confirm race").
[Test Case]
* Server-side: (relevant kernel side)
(limit TCP port to only 2000 connections)
# iptables -A INPUT -p tcp -m tcp --syn --dport \
-m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-j DROP
# ulimit -SHn 65000 # increase number of open files
# ruby server.rb # multi-threaded server
* Client-side:
# ulimit -SHn 65000
# ruby client.rb<# threads>
* Results with Original kernel:
(client achieves target of 6000 connections > limit of 2000 connections)
# ruby client.rb 10.230.56.100 6000 3
1
2
3
<...>
6000
Target reached. Thread finishing
6001
Target reached. Thread finishing
6002
Target reached. Thread finishing
Threads done. 6002 connections
press enter to exit
* Results with Modified kernel:
(client is limited to 2000 connections, and times out afterward)
# ruby client.rb 10.230.56.100 6000 3
1
2
3
<...>
2000
<... blocks for a few minutes ...>
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
Threads done. 2000 connections
press enter to exit
* Test cases possibly available upon request,
depending on original author's permission.
[Regression Potential]
* The patchset has been reviewed by a netfilter maintainer [1] in
stable mailing list, and was considered OK for 4.14, and that's
essentially the same backport for 4.15 and 4.4.
* The changes are limited to netfilter connlimit/conncount (names
change between older/newer kernel versions).
[Other Info]
* The backport for 4.14 [2] is applied as of 4.14.92.
[1] https://www.spinics.net/lists/stable/msg276883.html
[2] https://www.spinics.net/lists/stable/msg276910.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811094/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: LED's in Hotkey f5, f8 ans f11 without function
** Attachment added: "xkbmap.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+attachment/5228352/+files/xkbmap.txt ** Description changed: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa - Desktop: Cinnamon 4.0.8 - Kernel: 4.15.0-43-generic x86_64 bits: 64 + Desktop: Cinnamon 4.0.8 + Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS-mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I have created 11 logs but can only attach one? ~$ acpi_listen button/mute MUTE 0080 K button/f20 F20 0080 K ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: LED's in Hotkey f5, f8 ans f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I have created 11 logs but can only attach one? ~$ acpi_listen button/mute MUTE 0080 K button/f20 F20 0080 K ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] [NEW] LED's in Hotkey f5, f8 ans f11 without function
Public bug reported: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS-mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I have created 11 logs but can only attach one? ~$ acpi_listen button/mute MUTE 0080 K button/f20 F20 0080 K ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: 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/1811254 Title: LED's in Hotkey f5, f8 ans f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I have created 11 logs but can only attach one? ~$ acpi_listen button/mute MUTE 0080 K button/f20 F20 0080 K ~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 71 = (keysym 0xffc2, F5), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 74 = (keysym 0xffc5, F8), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 keycode 95 = (keysym 0xffc8, F11), state = 0x10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811252] [NEW] Xenial update: 4.4.169 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
4.4.169 upstream stable release
from git://git.kernel.org/
Linux 4.4.169
ALSA: isa/wavefront: prevent some out of bound writes
rtc: snvs: Add timeouts to avoid kernel lockups
rtc: snvs: add a missing write sync
i2c: scmi: Fix probe error on devices with an empty SMB0001 ACPI device node
i2c: axxia: properly handle master timeout
cifs: In Kconfig CONFIG_CIFS_POSIX needs depends on legacy (insecure cifs)
ARM: 8814/1: mm: improve/fix ARM v7_dma_inv_range() unaligned address handling
mv88e6060: disable hardware level MAC learning
libata: whitelist all SAMSUNG MZ7KM* solid-state disks
Input: omap-keypad - fix keyboard debounce configuration
clk: mmp: Off by one in mmp_clk_add()
ide: pmac: add of_node_put()
drivers/tty: add missing of_node_put()
drivers/sbus/char: add of_node_put()
sbus: char: add of_node_put()
SUNRPC: Fix a potential race in xprt_connect()
bonding: fix 802.3ad state sent to partner when unbinding slave
ARC: io.h: Implement reads{x}()/writes{x}()
drm/msm: Grab a vblank reference when waiting for commit_done
x86/earlyprintk/efi: Fix infinite loop on some screen widths
scsi: vmw_pscsi: Rearrange code to avoid multiple calls to free_irq during
unload
scsi: libiscsi: Fix NULL pointer dereference in iscsi_eh_session_reset
mac80211_hwsim: fix module init error paths for netlink
mac80211: Fix condition validating WMM IE
mac80211: don't WARN on bad WMM parameters from buggy APs
f2fs: fix a panic caused by NULL flush_cmd_control
Revert "drm/rockchip: Allow driver to be shutdown on reboot/kexec"
powerpc/msi: Fix NULL pointer access in teardown code
tracing: Fix memory leak of instance function hash filters
tracing: Fix memory leak in set_trigger_filter()
MMC: OMAP: fix broken MMC on OMAP15XX/OMAP5910/OMAP310
aio: fix spectre gadget in lookup_ioctx
pinctrl: sunxi: a83t: Fix IRQ offset typo for PH11
powerpc/boot: Fix random libfdt related build errors
timer/debug: Change /proc/timer_list from 0444 to 0400
lib/interval_tree_test.c: allow users to limit scope of endpoint
lib/rbtree-test: lower default params
lib/rbtree_test.c: make input module parameters
lib/interval_tree_test.c: allow full tree search
lib/interval_tree_test.c: make test options module parameters
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811252
Title:
Xenial update: 4.4.169 upstream stable release
Status in linux package in Ubuntu:
Confirmed
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.169 upstream stable release
from git://git.kernel.org/
Linux 4.4.169
ALSA: isa/wavefront: prevent some out of bound writes
rtc: snvs: Add timeouts to avoid kernel lockups
rtc: snvs: add a missing write sync
i2c: scmi: Fix probe error on devices with an empty SMB0001 ACPI device node
i2c: axxia: properly handle master timeout
cifs: In Kconfig CONFIG_CIFS_POSIX needs depends on legacy (insecure cifs)
ARM: 8814/1: mm: improve/fix ARM v7_dma_inv_range() unaligned address handling
mv88e6060: disable hardware level MAC learning
libata: whitelist all SAMSUNG MZ7KM* solid-state disks
Input: omap-keypad - fix keyboard debounce configuration
clk: mmp: Off by one in mmp_clk_add()
ide: pmac: add of_node_put()
drivers/tty: add missing of_node_put()
drivers/sbus/char: add of_node_put()
sbus: char: add of_node_put()
SUNRPC: Fix a potential race in xprt_connect()
bonding: fix 802.3ad state sent to partner when unbinding slave
ARC: io.h: Implement reads{x}()/writes{x}()
drm/msm: Grab a vblank reference when waiting for commit_done
x86/earlyprintk/efi: Fix infinite loop on some screen widths
scsi: vmw_pscsi: Rearrange code to avoid multiple calls to free_irq during
unload
scsi: libiscsi: Fix NULL pointer dereference in iscsi_
[Kernel-packages] [Bug 1806682] Re: ACPI: Invalid passive threshold
** Changed in: linux Status: Incomplete => 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/1806682 Title: ACPI: Invalid passive threshold Status in Linux: Fix Released Status in linux package in Ubuntu: New Bug description: Hello, dmesg: [1.423794] ACPI: Invalid passive threshold Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 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 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2739 F pulseaudio /dev/snd/pcmC0D0p: caravena 2739 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 09:17:14 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806682]
you can attach the out of "grep . /sys/class/thermal/thermal*/*" /sys/class/thermal/thermal*/temp shows the current temperature of each thermal zone. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806682 Title: ACPI: Invalid passive threshold Status in Linux: Fix Released Status in linux package in Ubuntu: New Bug description: Hello, dmesg: [1.423794] ACPI: Invalid passive threshold Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 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 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2739 F pulseaudio /dev/snd/pcmC0D0p: caravena 2739 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 09:17:14 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806472] Re: RTL8822BE WiFi Disabled in Kernel 4.18.0-12
So, the driver was previously unsigned, then signed and included in the original Ubuntu kernel for 18.10, then subsequently unsigned during an update somewhere along the way? That doesn't make sense to me - would have to try and find upstream to work out what has happened. Larry Finger suggests that Realtek has rewritten the driver and his GitHub repo is only for older kernels that do not already ship the r8822be driver. 4.21 is quoted as when this new driver will drop. https://github.com/lwfinger/rtlwifi_new/issues/408#issuecomment-426299298 ** Bug watch added: github.com/lwfinger/rtlwifi_new/issues #408 https://github.com/lwfinger/rtlwifi_new/issues/408 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806472 Title: RTL8822BE WiFi Disabled in Kernel 4.18.0-12 Status in linux package in Ubuntu: Confirmed Bug description: ===SRU Justification=== [Impact] Realtek 8822be doesn't work under kernel lockdown. [Fix] Add r8822be.ko to signature-inclusion, so it can be signed and be loaded when lockdown is enabled. [Test] Since I can't signed the kernel so it's not tested. [Regression Potential] Low. The driver is maintained by a Realtek guy, so bugs are actually getting fixed. ===Original Bug Report=== Received kernel patch 4.18.0-12 today on my machine. On reboot my WiFi appears to be unavailable. lspci still recognises the installed RTL8822BE card and a reboot back to the previous kernel version (4.18.0-11) seems to resolve the problem. We tried some debugging in the IRC channel and didn't get very far. The r8822be module alias is intact, trying to modprobe it or insert results in a "operation not permitted" error. Modprobing mac80211 and cfg80211 which r8822be depends on did not seem to help. KMod Lists for -12 and -11 kernels: https://paste.ubuntu.com/p/pwx5mKszVt/ `ls -latr /lib/modules/4.18.0-12-*/ ; grep -i B822 /lib/modules/4.18.0-12-*/modules.alias` : https://paste.ubuntu.com/p/5zcCbXyM5g/ 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/controlC1: callum 2989 F pulseaudio /dev/snd/controlC0: callum 2989 F pulseaudio CurrentDesktop: KDE Date: Mon Dec 3 19:27:16 2018 InstallationDate: Installed on 2018-11-10 (22 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 90H90015UK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=d5f81e09-382c-4759-8a6d-2503fe6959b4 ro quiet splash vt.handoff=1 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 StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2018 dmi.bios.vendor: LENOVO dmi.bios.version: O3FKT26A dmi.board.name: 36E1 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259620440547 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrO3FKT26A:bd06/15/2018:svnLENOVO:pn90H90015UK:pvrLegionY720T-34ASU:rvnLENOVO:rn36E1:rvrSDK0J40709WIN3259620440547:cvnLENOVO:ct3:cvrNone: dmi.product.family: Legion Y720T-34ASU dmi.product.name: 90H90015UK dmi.product.sku: LENOVO_MT_90H9_BU_LENOVO_FM_Legion Y720T-34ASU dmi.product.version: Legion Y720T-34ASU dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811094] Re: iptables connlimit allows more connections than the limit when using multiple CPUs
** Changed in: linux (Ubuntu Cosmic)
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/1811094
Title:
iptables connlimit allows more connections than the limit when using
multiple CPUs
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
* The iptables connection count/limit rules can be breached
with multithreaded network driver/server/client (common)
due to a race in the conncount/connlimit code.
* For example:
# iptables -A INPUT -p tcp -m tcp --syn --dport \
-m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-j DROP
* The fix is a backport from an upstream commit that resolves
the problem (plus dependencies for a cleaner backport) that
address the race condition:
commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
collection confirm race").
[Test Case]
* Server-side: (relevant kernel side)
(limit TCP port to only 2000 connections)
# iptables -A INPUT -p tcp -m tcp --syn --dport \
-m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-j DROP
# ulimit -SHn 65000 # increase number of open files
# ruby server.rb # multi-threaded server
* Client-side:
# ulimit -SHn 65000
# ruby client.rb<# threads>
* Results with Original kernel:
(client achieves target of 6000 connections > limit of 2000 connections)
# ruby client.rb 10.230.56.100 6000 3
1
2
3
<...>
6000
Target reached. Thread finishing
6001
Target reached. Thread finishing
6002
Target reached. Thread finishing
Threads done. 6002 connections
press enter to exit
* Results with Modified kernel:
(client is limited to 2000 connections, and times out afterward)
# ruby client.rb 10.230.56.100 6000 3
1
2
3
<...>
2000
<... blocks for a few minutes ...>
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
Threads done. 2000 connections
press enter to exit
* Test cases possibly available upon request,
depending on original author's permission.
[Regression Potential]
* The patchset has been reviewed by a netfilter maintainer [1] in
stable mailing list, and was considered OK for 4.14, and that's
essentially the same backport for 4.15 and 4.4.
* The changes are limited to netfilter connlimit/conncount (names
change between older/newer kernel versions).
[Other Info]
* The backport for 4.14 [2] is applied as of 4.14.92.
[1] https://www.spinics.net/lists/stable/msg276883.html
[2] https://www.spinics.net/lists/stable/msg276910.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811094/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811094] Re: iptables connlimit allows more connections than the limit when using multiple CPUs
** Changed in: linux (Ubuntu Bionic)
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/1811094
Title:
iptables connlimit allows more connections than the limit when using
multiple CPUs
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
New
Bug description:
[Impact]
* The iptables connection count/limit rules can be breached
with multithreaded network driver/server/client (common)
due to a race in the conncount/connlimit code.
* For example:
# iptables -A INPUT -p tcp -m tcp --syn --dport \
-m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-j DROP
* The fix is a backport from an upstream commit that resolves
the problem (plus dependencies for a cleaner backport) that
address the race condition:
commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
collection confirm race").
[Test Case]
* Server-side: (relevant kernel side)
(limit TCP port to only 2000 connections)
# iptables -A INPUT -p tcp -m tcp --syn --dport \
-m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-j DROP
# ulimit -SHn 65000 # increase number of open files
# ruby server.rb # multi-threaded server
* Client-side:
# ulimit -SHn 65000
# ruby client.rb<# threads>
* Results with Original kernel:
(client achieves target of 6000 connections > limit of 2000 connections)
# ruby client.rb 10.230.56.100 6000 3
1
2
3
<...>
6000
Target reached. Thread finishing
6001
Target reached. Thread finishing
6002
Target reached. Thread finishing
Threads done. 6002 connections
press enter to exit
* Results with Modified kernel:
(client is limited to 2000 connections, and times out afterward)
# ruby client.rb 10.230.56.100 6000 3
1
2
3
<...>
2000
<... blocks for a few minutes ...>
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
Threads done. 2000 connections
press enter to exit
* Test cases possibly available upon request,
depending on original author's permission.
[Regression Potential]
* The patchset has been reviewed by a netfilter maintainer [1] in
stable mailing list, and was considered OK for 4.14, and that's
essentially the same backport for 4.15 and 4.4.
* The changes are limited to netfilter connlimit/conncount (names
change between older/newer kernel versions).
[Other Info]
* The backport for 4.14 [2] is applied as of 4.14.92.
[1] https://www.spinics.net/lists/stable/msg276883.html
[2] https://www.spinics.net/lists/stable/msg276910.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811094/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806682]
> BTW, if you're running into a real overheating issue on this machine, How do I know if I have this temperature problem? How do I check this? -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806682 Title: ACPI: Invalid passive threshold Status in Linux: Fix Released Status in linux package in Ubuntu: New Bug description: Hello, dmesg: [1.423794] ACPI: Invalid passive threshold Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 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 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2739 F pulseaudio /dev/snd/pcmC0D0p: caravena 2739 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 09:17:14 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806682]
According to the acpidump, there is no _PSL control method, which is mandatory for a passive trip point. So, this is a BIOS bug to me, and there is no way to fix it in Linux kernel. Bug closed. BTW, if you're running into a real overheating issue on this machine, I think you can set CONFIG_INT340X_THERMAL and use the int340x thermal drivers plus userspace thermal daemon for thermal control. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806682 Title: ACPI: Invalid passive threshold Status in Linux: Fix Released Status in linux package in Ubuntu: New Bug description: Hello, dmesg: [1.423794] ACPI: Invalid passive threshold Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 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 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2739 F pulseaudio /dev/snd/pcmC0D0p: caravena 2739 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 09:17:14 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806682]
Needs more information? (: -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806682 Title: ACPI: Invalid passive threshold Status in Linux: Fix Released Status in linux package in Ubuntu: New Bug description: Hello, dmesg: [1.423794] ACPI: Invalid passive threshold Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 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 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2739 F pulseaudio /dev/snd/pcmC0D0p: caravena 2739 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 09:17:14 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810998
Title:
CPU hard lockup with rigorous writes to NVMe drive
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
New
Status in linux source package in Cosmic:
New
Bug description:
[Impact]
* Users may experience cpu hard lockups when performing
rigorous writes to NVMe drives.
* The fix addresses an scheduling issue in the original
implementation of wbt/writeback throttling
* The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
contention and thundering herd issue in wbt_wait"),
plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
waking of tasks").
* There are additional commits to help with a cleaner
backport and future maintenance:
- Cosmic: total of 8 clean cherry picks.
- Bionic: total of 13 commits, 9 clean cherry-picks
and 4 backports, which are just changes to context
lines (i.e. refresh) without any functional changes
in the backport itself.
[Test Case]
* This command has been reported to reproduce the problem:
$ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
128
* It generates stack traces as below in the original kernel,
and does not generate them in the modified/patched kernel.
* The user/reporter verified the test kernel with these patches
resolved the problem.
* The developer verified in 2 systems (4-core and 24-core but
no NVMe) for regressions, and no error messages were logged
to dmesg.
[Regression Potential]
* The commits have been verified for fixes in later commits in
linux-next as of 2019-01-08 and all known fix commits are in.
* The regression potential is mostly contained in the writeback
throttling (block/blk-wbt.*), as almost all of the 13 patches
change exclusively that, except for 4 of them (2 of which are
sysfs):
- blk-rq-qos: refactor out common elements of blk-wbt (block/)
- block: Protect less code with sysfs_lock in blk_{un,}register_queue()
(blk-sysfs.c)
- block: Protect less code with sysfs_lock in blk_{un,}register_queue()
(blk-{mq-}sysfs.c)
- block: pass struct request instead of struct blk_issue_stat to wbt
(block/, still mostly blk-wbt.*)
[Other Info]
* Alternatively, it is probably possible to introduce just the
two commits that fix this with some changes to their code in
the backport, but since the 'blk-rq-qos: refactor ..' commit
may become a dependency for many additional/future fixes, it
seemed interesting to pull it in earlier in the 18.04 cycle.
* The problem has been introduced with the blk-wbt mechanism,
in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
so only Bionic and Cosmic needs this.
[Stack Traces]
[ 393.628647] NMI watchdog: Watchdog detected hard LOCKUP on cpu 30
...
[ 393.628704] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic
#21-Ubuntu
...
[ 393.628720] Call Trace:
[ 393.628721]
[ 393.628724] enqueue_task_fair+0x6c/0x7f0
[ 393.628726] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
[ 393.628728] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
[ 393.628731] activate_task+0x57/0xc0
[ 393.628735] ? sched_clock+0x9/0x10
[ 393.628736] ? sched_clock+0x9/0x10
[ 393.628738] ttwu_do_activate+0x49/0x90
[ 393.628739] try_to_wake_up+0x1df/0x490
[ 393.628741] default_wake_function+0x12/0x20
[ 393.628743] autoremove_wake_function+0x12/0x40
[ 393.628744] __wake_up_common+0x73/0x130
[ 393.628745] __wake_up_common_lock+0x80/0xc0
[ 393.628746] __wake_up+0x13/0x20
[ 393.628749] __wbt_done.part.21+0xa4/0xb0
[ 393.628749] wbt_done+0x72/0xa0
[ 393.628753] blk_mq_free_request+0xca/0x1a0
[ 393.628755] blk_mq_end_request+0x48/0x90
[ 393.628760] nvme_complete_rq+0x23/0x120 [nvme_core]
[ 393.628763] nvme_pci_complete_rq+0x7a/0x130 [nvme]
[ 393.628764] __blk_mq_complete_request+0xd2/0x140
[ 393.628766] blk_mq_complete_request+0x18/0x20
[ 393.628767] nvme_process_cq+0xe1/0x1b0 [nvme]
[ 393.628768] nvme_irq+0x23/0x50 [nvme]
[ 393.628772] __handle_irq_event_percpu+0x44/0x1a0
[ 393.628773] handle_irq_event_percpu+0x32/0x80
[ 393.628774] handle_irq_event+0x3b/0x60
[ 393.628778] handle_edge_irq+0x7c/0x190
[ 393.628779] handle_irq+0x20/0x30
[ 393.628783] do_IRQ+0x46/0xd0
[ 393.628784] common_interrupt+0x84/0x84
[ 393.628785]
...
[ 393.628794] ? cpuidle_enter_stat
[Kernel-packages] [Bug 1811200] Re: Add Cavium ThunderX2 SoC UNCORE PMU driver
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Assignee: Ike Panhc (ikepanhc) Status: Incomplete ** Also affects: linux (Ubuntu Bionic) 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/1811200 Title: Add Cavium ThunderX2 SoC UNCORE PMU driver Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Incomplete Bug description: [Impact] No driver for PMU of L3 cache controller (L3C) and the DDR4 Memory Controller (DMC) for Cavium ThunderX2 SoC [Test Case] sudo perf stat -a -e \ > uncore_dmc_0/cnt_cycles/,\ > uncore_dmc_0/data_transfers/,\ > uncore_dmc_0/read_txns/,\ > uncore_dmc_0/write_txns/ sleep 1 sudo perf stat -a -e \ > uncore_l3c_0/read_request/,\ > uncore_l3c_0/read_hit/,\ > uncore_l3c_0/inv_request/,\ > uncore_l3c_0/inv_hit/ sleep 1 sudo perf stat -a -e uncore_dmc_0/cnt_cycles/ sleep 1 [Fix] Backport patches 82975c46da perf: Export perf_event_update_userpage (only for bionic) d6310a3f33 Documentation: perf: Add documentation for ThunderX2 PMU uncore driver 69c32972d5 drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver and enable CONFIG_THUNDERX2_PMU=m [Regression Risk] This driver only loaded when CAV901C in ACPI table, lowest risk for other platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
Also running into the same issue. It's been happening ever since I installed 18.10. I can't seem to replicate it, but I have 2 patterns 1. when I use communication software, like Skype or TeamViewer - GNOME here resets and logs me out. 2. Interacting between VMPlayer (windows) and Ubuntu - freezes completely and have to reboot I'm seeing a ton of this in SYSLOG: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 8009 Quite a bit of this: Unrecoverable failure in required component org.gnome.Shell.desktop I can't replicate. Running 18.10 with 4.18.0-13-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Triaged Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808912] Re: scsi: libsas: fix a race condition when smp task timeout
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808912 Title: scsi: libsas: fix a race condition when smp task timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] When the lldd is processing the complete sas task in interrupt and set the task stat as SAS_TASK_STATE_DONE, the smp timeout timer is able to be triggered at the same time. And smp_task_timedout() will complete the task wheter the SAS_TASK_STATE_DONE is set or not. Then the sas task may freed before lldd end the interrupt process. Thus a use-after-free will happen. [Test Case] This is hard to reproduce, so regression test only. [Fix] b90cd6f2b9 scsi: libsas: fix a race condition when smp task timeout [Regression Risk] Only 2 line moved in libsas and maintainer has reviewed/approved. I will say it's low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809046] Re: Cannot initialize ATA disk if IDENTIFY command fails
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809046 Title: Cannot initialize ATA disk if IDENTIFY command fails Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] ATA disks attached to a SAS controller may not initialize if the initial IDENTIFY command fails. [Test Case] The positive test case would require a disk that fails to respond correctly to an IDENTIFY command. I don't have one of those, so can only regression test on a system w/ SAS connected disks. [Fix] 437207d3697f5 scsi: libsas: check the ata device status by ata_dev_enabled() [Regression Risk] Clean cherry pick from upstream - any regressions will have upstream support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811236] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811236 Title: System wakes from suspend without user initialization Status in linux package in Ubuntu: Confirmed Bug description: I use `systemctl suspend` for taking my laptop to sleep. Suspend seems to work fine, but after a random amount of time, the system resumes without me pressing any buttons, moving a mouse etc. Some other methods have been attempted, but all end up with the same result, ie. system resumes unwanted. Here is a /var/log/syslog excerpt, hope I managed to grab everything valuable. The bug was filed with `ubuntu-bug linux- image-4.18.0-13-generic`, which is the linux image currently in use. Please let me know if something is missing due to incorrect package selection or otherwise. --- Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3067] manager: sleep: sleep requested (sleeping: no enabled: yes) Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3069] device (enp0s20f0u2c2): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3126] device (wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3415] device (enp0s20f0u4): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3453] manager: NetworkManager state is now ASLEEP Jan 10 13:48:35 caolila systemd[1]: Reached target Sleep. Jan 10 13:48:35 caolila systemd[1]: Starting Suspend... Jan 10 13:48:35 caolila whoopsie[1352]: [13:48:35] offline Jan 10 13:48:35 caolila systemd-sleep[32606]: Suspending system... Jan 10 13:48:35 caolila kernel: [19604.933999] PM: suspend entry (deep) Jan 10 13:48:35 caolila kernel: [19604.934001] PM: Syncing filesystems ... done. Jan 10 13:48:35 caolila wpa_supplicant[868]: nl80211: deinit ifname=wlp0s20f3 disabled_11b_rates=0 Jan 10 13:53:55 caolila kernel: [19607.067269] Freezing user space processes ... (elapsed 0.004 seconds) done. Jan 10 13:53:55 caolila kernel: [19607.071592] OOM killer disabled. Jan 10 13:53:55 caolila kernel: [19607.071593] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 10 13:53:55 caolila kernel: [19607.072971] Suspending console(s) (use no_console_suspend to debug) Jan 10 13:53:55 caolila kernel: [19607.160541] e1000e: EEE TX LPI TIMER: 0011 Jan 10 13:53:55 caolila kernel: [19607.502557] thunderbolt :07:00.0: stopping RX ring 0 Jan 10 13:53:55 caolila kernel: [19607.502575] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 12 (0x1001 -> 0x1) Jan 10 13:53:55 caolila kernel: [19607.502581] thunderbolt :07:00.0: stopping TX ring 0 Jan 10 13:53:55 caolila kernel: [19607.502605] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 0 (0x1 -> 0x0) Jan 10 13:53:55 caolila kernel: [19607.502608] thunderbolt :07:00.0: control channel stopped Jan 10 13:53:55 caolila kernel: [19607.502808] ACPI: EC: interrupt blocked Jan 10 13:53:55 caolila kernel: [19607.684603] ACPI: Preparing to enter system sleep state S3 Jan 10 13:53:55 caolila kernel: [19607.688265] ACPI: EC: event blocked Jan 10 13:53:55 caolila kernel: [19607.688267] ACPI: EC: EC stopped Jan 10 13:53:55 caolila kernel: [19607.688268] PM: Saving platform NVS memory Jan 10 13:53:55 caolila kernel: [19607.688301] Disabling non-boot CPUs ... Jan 10 13:53:55 caolila kernel: [19607.704406] IRQ 122: no longer affine to CPU1 Jan 10 13:53:55 caolila kernel: [19607.704426] IRQ 187: no longer affine to CPU1 Jan 10 13:53:55 caolila kernel: [19607.705447] smpboot: CPU 1 is now offline Jan 10 13:53:55 caolila kernel: [19607.728394] IRQ 189: no longer affine to CPU2 Jan 10 13:53:55 caolila kernel: [19607.729415] smpboot: CPU 2 is now offline Jan 10 13:53:55 caolila kernel: [19607.752349] IRQ 177: no longer affine to CPU3 Jan 10 13:53:55 caolila kernel: [19607.753377] smpboot: CPU 3 is now offline Jan 10 13:53:55 caolila kernel: [19607.780410] IRQ 179: no longer affine to CPU4 Jan 10 13:53:55 caolila kernel: [19607.781438] smpboot: CPU 4 is now offline Jan 10 13:53:55 caolila kernel: [19607.804344] IRQ 185: no longer affine to CPU5 Jan 10 13:53:55 caolila kernel: [19607.805385] smpboot: CPU 5 is now offline Jan 10 13:53:55 caolila kernel: [19607.828255] IRQ 183: no longer affine to CPU6 Jan 10 13:53:55 caolila kernel: [19607.828271] IRQ 195: no longer affine to CPU6 Jan 10 13:53:55 caolila kernel: [19607.830230] smpboot: CPU 6 is now offline Jan 10 13:53:55 caolila kernel: [19
[Kernel-packages] [Bug 1771222] Re: Using sysctl to permanently disable IPv6 doesn't have any effect
Shows up in 16.04.5 (4.15.0-43-generic) too. In the end, despite all the above ipv6.disable = 1 additions to sysctl.conf and reboots, the only sure-fire way I found to reliably disable ipv6 was to add ipv6.disable=1 to grub: $ grep ip /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 quiet splash" $ sudo update-grub $ sudo reboot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771222 Title: Using sysctl to permanently disable IPv6 doesn't have any effect Status in linux package in Ubuntu: Confirmed Bug description: Shows up in version 18.04 of Ubuntu. I added the following 2 lines in /etc/sysctl.d/99-sysctl.conf and /etc/sysctl.d/01-disable-ipv6.conf: ``` net.ipv6.conf.all.disable_ipv6=1 net.ipv6.conf.default.disable_ipv6=1 ``` Rebooting my machine sets those parameters for "all" and "default" but not for the sysctl options of my network interface: ``` net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.ens160.disable_ipv6 = 0 ``` I use disable_ipv6 above as an example. I've also verified this with the promote_secondaries option of ipv4. I can always restart systemd-sysctl.service at every boot and this will set net.ipv6.conf.ens160.disable_ipv6 to 1. Unfortunately though this won't work for devices that are hot-plugged. Other info: - version signature: Ubuntu 4.15.0-20.21-generic 4.15.17 - lspci is attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811236] [NEW] System wakes from suspend without user initialization
Public bug reported: I use `systemctl suspend` for taking my laptop to sleep. Suspend seems to work fine, but after a random amount of time, the system resumes without me pressing any buttons, moving a mouse etc. Some other methods have been attempted, but all end up with the same result, ie. system resumes unwanted. Here is a /var/log/syslog excerpt, hope I managed to grab everything valuable. The bug was filed with `ubuntu-bug linux- image-4.18.0-13-generic`, which is the linux image currently in use. Please let me know if something is missing due to incorrect package selection or otherwise. --- Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3067] manager: sleep: sleep requested (sleeping: no enabled: yes) Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3069] device (enp0s20f0u2c2): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3126] device (wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3415] device (enp0s20f0u4): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3453] manager: NetworkManager state is now ASLEEP Jan 10 13:48:35 caolila systemd[1]: Reached target Sleep. Jan 10 13:48:35 caolila systemd[1]: Starting Suspend... Jan 10 13:48:35 caolila whoopsie[1352]: [13:48:35] offline Jan 10 13:48:35 caolila systemd-sleep[32606]: Suspending system... Jan 10 13:48:35 caolila kernel: [19604.933999] PM: suspend entry (deep) Jan 10 13:48:35 caolila kernel: [19604.934001] PM: Syncing filesystems ... done. Jan 10 13:48:35 caolila wpa_supplicant[868]: nl80211: deinit ifname=wlp0s20f3 disabled_11b_rates=0 Jan 10 13:53:55 caolila kernel: [19607.067269] Freezing user space processes ... (elapsed 0.004 seconds) done. Jan 10 13:53:55 caolila kernel: [19607.071592] OOM killer disabled. Jan 10 13:53:55 caolila kernel: [19607.071593] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 10 13:53:55 caolila kernel: [19607.072971] Suspending console(s) (use no_console_suspend to debug) Jan 10 13:53:55 caolila kernel: [19607.160541] e1000e: EEE TX LPI TIMER: 0011 Jan 10 13:53:55 caolila kernel: [19607.502557] thunderbolt :07:00.0: stopping RX ring 0 Jan 10 13:53:55 caolila kernel: [19607.502575] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 12 (0x1001 -> 0x1) Jan 10 13:53:55 caolila kernel: [19607.502581] thunderbolt :07:00.0: stopping TX ring 0 Jan 10 13:53:55 caolila kernel: [19607.502605] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 0 (0x1 -> 0x0) Jan 10 13:53:55 caolila kernel: [19607.502608] thunderbolt :07:00.0: control channel stopped Jan 10 13:53:55 caolila kernel: [19607.502808] ACPI: EC: interrupt blocked Jan 10 13:53:55 caolila kernel: [19607.684603] ACPI: Preparing to enter system sleep state S3 Jan 10 13:53:55 caolila kernel: [19607.688265] ACPI: EC: event blocked Jan 10 13:53:55 caolila kernel: [19607.688267] ACPI: EC: EC stopped Jan 10 13:53:55 caolila kernel: [19607.688268] PM: Saving platform NVS memory Jan 10 13:53:55 caolila kernel: [19607.688301] Disabling non-boot CPUs ... Jan 10 13:53:55 caolila kernel: [19607.704406] IRQ 122: no longer affine to CPU1 Jan 10 13:53:55 caolila kernel: [19607.704426] IRQ 187: no longer affine to CPU1 Jan 10 13:53:55 caolila kernel: [19607.705447] smpboot: CPU 1 is now offline Jan 10 13:53:55 caolila kernel: [19607.728394] IRQ 189: no longer affine to CPU2 Jan 10 13:53:55 caolila kernel: [19607.729415] smpboot: CPU 2 is now offline Jan 10 13:53:55 caolila kernel: [19607.752349] IRQ 177: no longer affine to CPU3 Jan 10 13:53:55 caolila kernel: [19607.753377] smpboot: CPU 3 is now offline Jan 10 13:53:55 caolila kernel: [19607.780410] IRQ 179: no longer affine to CPU4 Jan 10 13:53:55 caolila kernel: [19607.781438] smpboot: CPU 4 is now offline Jan 10 13:53:55 caolila kernel: [19607.804344] IRQ 185: no longer affine to CPU5 Jan 10 13:53:55 caolila kernel: [19607.805385] smpboot: CPU 5 is now offline Jan 10 13:53:55 caolila kernel: [19607.828255] IRQ 183: no longer affine to CPU6 Jan 10 13:53:55 caolila kernel: [19607.828271] IRQ 195: no longer affine to CPU6 Jan 10 13:53:55 caolila kernel: [19607.830230] smpboot: CPU 6 is now offline Jan 10 13:53:55 caolila kernel: [19607.864142] IRQ 143: no longer affine to CPU7 Jan 10 13:53:55 caolila kernel: [19607.864152] IRQ 178: no longer affine to CPU7 Jan 10 13:53:55 caolila kernel: [19607.865177] smpboot: CPU 7 is now offline Jan 10 13:53:55 caolila kernel: [19607.889142] smpboot: CPU 8 is now offline Jan 10 13:53:55 caolila kernel: [19607.913119] smpboot: CPU 9 is now offline Jan 10 13:53:55 caolila kernel: [19607.937091] smpboot: CPU 10 is now offline Jan 10 13:53:55 caolila kernel: [19607.965065] s
[Kernel-packages] [Bug 1805085] Re: Fix and issue that LG I2C touchscreen stops working after reboot
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Cosmic) 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/1805085 Title: Fix and issue that LG I2C touchscreen stops working after reboot Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] LG I2C touchscreen stops working after reboot. [Fix] Disable runtime PM for the touchscreen, which doesn't work well with consecutive ON/SLEEP commands. [Test] The touchscreen works well after reboot, when runtime PM is disabled. [Regression Potential] None. This is a new device and the fix is limited to this particular device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1805085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => Fix Released ** Description changed: This bug is for tracking the 4.15.0-1007.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 - phase: Release -- release to Updates ready - phase-changed: Thursday, 10. January 2019 11:08 UTC + phase: Release -- complete + phase-changed: Thursday, 10. January 2019 11:30 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Pending -- ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807702 Title: linux-oracle: 4.15.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1007.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Release -- complete phase-changed: Thursday, 10. January 2019 11:30 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/1807702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => Fix Released ** Description changed: This bug is for tracking the 4.15.0-1007.7~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 - phase: Release -- release to Updates ready - phase-changed: Thursday, 10. January 2019 11:09 UTC + phase: Release -- complete + phase-changed: Thursday, 10. January 2019 11:30 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Pending -- ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Release -- complete phase-changed: Thursday, 10. January 2019 11:30 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/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807702 Title: linux-oracle: 4.15.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1007.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Release -- complete phase-changed: Thursday, 10. January 2019 11:30 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/1807702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Release -- complete phase-changed: Thursday, 10. January 2019 11:30 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/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805245] Re: powerpc/powernv/pci: Work around races in PCI bridge enabling
** 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/1805245 Title: powerpc/powernv/pci: Work around races in PCI bridge enabling Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification = [Impact] An IBM OpenPower partner reports their system with a bunch of NVMe drives fails the NVMe init due to some drives taking PCIe EEH errors. [Fix] Pick patch db2173198b9513f7add8009f225afa1f1c79bcc6 upstream. [Testing] IBM reports that this patch fixes the user's issue. [Regression Potential] The patch is already in Cosmic (db33bbe77b9594133fecf0dc290322437170627f) and in some stable trees (1eb08e7b192d2c412175f607cf51449c916abd57 in 4.14.y). It only affects PowerPC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807757] Re: Drivers: hv: vmbus: Offload the handling of channels to two workqueues
** 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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1807757
Title:
Drivers: hv: vmbus: Offload the handling of channels to two workqueues
Status in linux package in Ubuntu:
Fix Committed
Status in linux-azure package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Bug description:
== SRU Justification ==
Microsoft has identified a multiple-NIC-deadlock issue on Hyper-V VMs. This
bug is fixed by the following commit, which is in mainline as of v4.20-rc6:
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two
workqueues")
A second commit is also needed to prevent a deadlock with single NIC VMs.
This commit is in mainline as of 4.19-rc3:
e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier in
netvsc_probe()")
The Disco development release has been rebased to upstream 4.19, and
it already has commit eceb0596548. Disco only needs 37c2578c0c40.
Cosmic does not require any dependent commits, just the two
above(37c2578c0c40, e04e7a7bbd4b).
linux-azure and Bionic(4.15+ kernels) require the following five dependent
commits:
4.18-rc1 - 7bf7bb37f16a ("hv_netvsc: fix network namespace issues with VF
support")
4.18-rc4 - 3ffe64f1a641 ("hv_netvsc: split sub-channel setup into async and
sync")
4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in
vmbus_process_offer()")
4.19-rc3 - e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock
earlier in netvsc_probe()")
4.19-rc4 - 6712cc9c2211 ("vmbus: don't return values for uninitalized
channels")
== Fixes ==
("Dependent commits mentioned above, based on Ubuntu release")
e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier
in netvsc_probe()")
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to
two workqueues")
== Regression Potential ==
Low. Limited to hyperv.
== Test Case ==
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807757/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed ** Description changed: This bug is for tracking the 4.15.0-1007.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 - phase: Testing -- passed - phase-changed: Wednesday, 09. January 2019 11:18 UTC + phase: Release -- release to Updates ready + phase-changed: Thursday, 10. January 2019 11:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present + promote-to-updates: Pending -- ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807702 Title: linux-oracle: 4.15.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1007.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Release -- release to Updates ready phase-changed: Thursday, 10. January 2019 11:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed ** Description changed: This bug is for tracking the 4.15.0-1007.7~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 - phase: Testing -- passed - phase-changed: Wednesday, 09. January 2019 11:18 UTC + phase: Release -- release to Updates ready + phase-changed: Thursday, 10. January 2019 11:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present + promote-to-updates: Pending -- ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Release -- release to Updates ready phase-changed: Thursday, 10. January 2019 11:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker
** Tags removed: kernel-block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Release -- release to Updates ready phase-changed: Thursday, 10. January 2019 11:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker
** Tags removed: kernel-block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807702 Title: linux-oracle: 4.15.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1007.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Release -- release to Updates ready phase-changed: Thursday, 10. January 2019 11:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807757] Re: Drivers: hv: vmbus: Offload the handling of channels to two workqueues
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1807757
Title:
Drivers: hv: vmbus: Offload the handling of channels to two workqueues
Status in linux package in Ubuntu:
Fix Committed
Status in linux-azure package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Bug description:
== SRU Justification ==
Microsoft has identified a multiple-NIC-deadlock issue on Hyper-V VMs. This
bug is fixed by the following commit, which is in mainline as of v4.20-rc6:
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two
workqueues")
A second commit is also needed to prevent a deadlock with single NIC VMs.
This commit is in mainline as of 4.19-rc3:
e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier in
netvsc_probe()")
The Disco development release has been rebased to upstream 4.19, and
it already has commit eceb0596548. Disco only needs 37c2578c0c40.
Cosmic does not require any dependent commits, just the two
above(37c2578c0c40, e04e7a7bbd4b).
linux-azure and Bionic(4.15+ kernels) require the following five dependent
commits:
4.18-rc1 - 7bf7bb37f16a ("hv_netvsc: fix network namespace issues with VF
support")
4.18-rc4 - 3ffe64f1a641 ("hv_netvsc: split sub-channel setup into async and
sync")
4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in
vmbus_process_offer()")
4.19-rc3 - e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock
earlier in netvsc_probe()")
4.19-rc4 - 6712cc9c2211 ("vmbus: don't return values for uninitalized
channels")
== Fixes ==
("Dependent commits mentioned above, based on Ubuntu release")
e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier
in netvsc_probe()")
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to
two workqueues")
== Regression Potential ==
Low. Limited to hyperv.
== Test Case ==
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807757/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Description changed: This bug is for tracking the 4.15.0-1007.7~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Testing -- passed phase-changed: Wednesday, 09. January 2019 11:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- kernel-block/kernel-block-proposed tag present promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Testing -- passed phase-changed: Wednesday, 09. January 2019 11:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802248] Re: Disable LPM for Raydium Touchscreens
** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802248 Title: Disable LPM for Raydium Touchscreens Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] Raydium touchscreens don't work on LPM capable platforms. [Test] Raydium touchscreens start to work with the patch. [Fix] Disable LPM for Raydium touchscreens. [Regression Potential] Low. Limits to specific Raydium touchscreens. Also, USB runtime PM (SeletiveSuspend) still works, so disabling LPM doesn't really increase power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1802248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802248] Re: Disable LPM for Raydium Touchscreens
** 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/1802248 Title: Disable LPM for Raydium Touchscreens Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] Raydium touchscreens don't work on LPM capable platforms. [Test] Raydium touchscreens start to work with the patch. [Fix] Disable LPM for Raydium touchscreens. [Regression Potential] Low. Limits to specific Raydium touchscreens. Also, USB runtime PM (SeletiveSuspend) still works, so disabling LPM doesn't really increase power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1802248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802813] Re: Fix "incomplete report" noise after S3
This fix has already been applied to Bionic as part of bug 1808399. ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1802813 Title: Fix "incomplete report" noise after S3 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Bug description: [Impact] I2C HID devices may keep spewing out error "i2c_hid_get_input: incomplete report (30/2)" after system S3. [Fix] It a regression caused by commit ac75a041048b, backport commmit ef6eaf27274c to fix it. Input report length 2 is a valid length. [Test] With the fix the issue can no longer be observed on Alps touchpads. [Regression Potential] None. Input report lenght 2 is valid per spec. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1802813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807702 Title: linux-oracle: 4.15.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow 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: Invalid 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: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1007.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Testing -- passed phase-changed: Wednesday, 09. January 2019 11:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Description changed: This bug is for tracking the 4.15.0-1007.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Testing -- passed phase-changed: Wednesday, 09. January 2019 11:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- kernel-block/kernel-block-proposed tag present promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807702 Title: linux-oracle: 4.15.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow 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: Invalid 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: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1007.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Testing -- passed phase-changed: Wednesday, 09. January 2019 11:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811226] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228267/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811226] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228266/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811226] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228265/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Testing -- passed phase-changed: Wednesday, 09. January 2019 11:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811226] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228260/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811226] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228261/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811226] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228262/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811226] Re: ipvsadm --ops causes CPU soft lockup on traffic
apport information ** Tags added: apport-collected bionic ** Description changed: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel- ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jan 10 11:37 seq + crw-rw 1 root audio 116, 33 Jan 10 11:37 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro + ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-43-generic N/A + linux-backports-modules-4.15.0-43-generic N/A + linux-firmware 1.173.2 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic + Uname: Linux 4.15.0-43-generic x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: False + dmi.bios.date: 04/01/2014 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-i440fx-2.12 + dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: + dmi.product.name: Standard PC (i440FX + PIIX, 1996) + dmi.product.version: pc-i440fx-2.12 + dmi.sys.vendor: QEMU ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228259/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 De
[Kernel-packages] [Bug 1811226] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228264/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811226] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228263/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811226] 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 1811226 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/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Incomplete Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809870] Re: 2365dd3ca02bbb6d3412404482e1d85752549953 in ubuntu_btrfs_kernel_fixes failed on B
According to the btrfs document[1], adding another disk to the existing btrfs file system is equivalent to create a raid with Raid 1 on Meta, Raid 0 on Data group (mkfs.btrfs -m raid1 -d raid0). So when wiping one of the disks out, it will corrupt the data but the meta should be OK: # btrfs fi show Label: none uuid: 3e7e0fb5-5fec-4938-bc20-0e5dfdf466ff Total devices 2 FS bytes used 128.00KiB devid1 size 512.00MiB used 88.00MiB path /dev/loop0 *** Some devices missing This behaviour in this test case has been changed in the kernel with commit 4330e183c9537df20952d4a9ee142c536fb8ae54, we should be able to mount the drive with 'rw' in degraded mode, unless the data chunk was destroyed. [1] https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => 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/1809870 Title: 2365dd3ca02bbb6d3412404482e1d85752549953 in ubuntu_btrfs_kernel_fixes failed on B Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Bug description: Test failed on Bionic, and this patch does exist in Bionic kernel tree. Invoking test 2365dd3ca02bbb6d3412404482e1d85752549953 fix 2365dd3ca02bbb6d3412404482e1d85752549953 btrfs: undo sysfs when open_ctree() fails reproducer: mkfs.btrfs -f /dev/sdb &&mount /dev/sdb /btrfs &&btrfs dev add -f /dev/sdc /btrfs &&umount /btrfs &&wipefs -a /dev/sdc &&mount -o degraded /dev/sdb /btrfs //above mount fails so try with RO mount -o degraded,ro /dev/sdb /btrfs -- sysfs: cannot create duplicate filename '/fs/btrfs/3f48c79e-5ed0-4e87-b189-86e749e503f4' :: Performing full device TRIM /dev/loop1 (512.00MiB) ... mount -o degraded /dev/loop0 /tmp/mnt-2365dd3ca02bbb6d3412404482e1d85752549953 was expected to fail FAIL: 2365dd3ca02bbb6d3412404482e1d85752549953 (ret=1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 20 18:17 seq crw-rw 1 root audio 116, 33 Dec 20 18:17 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Thu Dec 27 07:34:54 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811226] [NEW] ipvsadm --ops causes CPU soft lockup on traffic
Public bug reported: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel- ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1811226/+attachment/5228243/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: New Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811077] Re: Xenial update: 4.4.167 upstream stable release
** Changed in: linux (Ubuntu Xenial) 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/1811077 Title: Xenial update: 4.4.167 upstream stable release Status in linux package in Ubuntu: Invalid 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.167 upstream stable release from git://git.kernel.org/ Linux 4.4.167 mac80211: ignore NullFunc frames in the duplicate detection mac80211: fix reordering of buffered broadcast packets mac80211: ignore tx status for PS stations in ieee80211_tx_status_ext mac80211: Clear beacon_int in ieee80211_do_stop mac80211_hwsim: Timer should be initialized before device registered kgdboc: fix KASAN global-out-of-bounds bug in param_set_kgdboc_var() tty: serial: 8250_mtk: always resume the device in probe. cifs: Fix separator when building path from dentry Staging: lustre: remove two build warnings xhci: Prevent U1/U2 link pm states if exit latency is too long SUNRPC: Fix leak of krb5p encode pages virtio/s390: fix race in ccw_io_helper() virtio/s390: avoid race on vcdev->config ALSA: pcm: Fix interval evaluation with openmin/max ALSA: pcm: Call snd_pcm_unlink() conditionally at closing ALSA: pcm: Fix starvation on down_write_nonblock() ALSA: hda: Add support for AMD Stoney Ridge ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in card.c USB: check usb_get_extra_descriptor for proper size usb: appledisplay: Add 27" Apple Cinema Display usb: quirk: add no-LPM quirk on SanDisk Ultra Flair device net: amd: add missing of_node_put() iommu/vt-d: Use memunmap to free memremap net: faraday: ftmac100: remove netif_running(netdev) check before disabling interrupts net/mlx4: Fix UBSAN warning of signed integer overflow net/mlx4_core: Fix uninitialized variable compilation warning net/mlx4_core: Zero out lkey field in SW2HW_MPT fw command qed: Fix reading wrong value in loop condition qed: Fix PTT leak in qed_drain() bnx2x: Assign unique DMAE channel number for FW DMAE transactions. batman-adv: Expand merged fragment buffer for full packet can: rcar_can: Fix erroneous registration iommu/ipmmu-vmsa: Fix crash on early domain free iommu/vt-d: Fix NULL pointer dereference in prq_event_thread() usb: gadget: dummy: fix nonsensical comparisons mm: mlock: avoid increase mm->locked_vm on mlock() when already mlock2(,MLOCK_ONFAULT) mm: cleancache: fix corruption on missed inode invalidation arc: [devboards] Add support of NFSv3 ACL ARC: change defconfig defaults to ARCv2 Btrfs: fix use-after-free when dumping free space btrfs: Always try all copies when reading extent buffers Input: elan_i2c - add support for ELAN0621 touchpad Input: elan_i2c - add ACPI ID for Lenovo IdeaPad 330-15ARR Input: elan_i2c - add ELAN0620 to the ACPI table Input: matrix_keypad - check for errors from of_get_named_gpio() Input: xpad - quirk all PDP Xbox One gamepads leds: leds-gpio: Fix return value check in create_gpio_led() leds: turn off the LED and wait for completion on unregistering LED class device leds: call led_pwm_set() in leds-pwm to enforce default LED_OFF kgdboc: Fix warning with module build kgdboc: Fix restrict error scsi: csiostor: Avoid content leaks and casts ALSA: trident: Suppress gcc string warning scsi: scsi_devinfo: cleanly zero-pad devinfo strings drm/ast: Fix incorrect free on ioregs mips: fix mips_get_syscall_arg o32 check MIPS: ralink: Fix mt7620 nd_sd pinmux uprobes: Fix handle_swbp() vs. unregister() + register() race once more iser: set sector for ambiguous mr status errors kdb: use memmove instead of overlapping memcpy staging: rts5208: fix gcc-8 logic error warning scsi: bfa: convert to strlcpy/strlcat drm: gma500: fix logic error ip_tunnel: Fix name string concatenate in __ip_tunnel_create() kernfs: Replace strncpy with memcpy unifdef: use memcpy instead of strncpy kobject: Replace strncpy with memcpy disable stringop truncation warnings for now exec: avoid gcc-8 warning for get_task_comm Kbuild: suppress packed-not-aligned warning for default setting only misc: mic/scif: fix copy-paste error in scif_create_remote_lookup usb: core: quirks: add RESET_RESUME quirk for Cherry G230 Stream series USB: usb-storage: Add new IDs to ums-realtek btrfs: release metadat
[Kernel-packages] [Bug 1811077] Re: Xenial update: 4.4.167 upstream stable release
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811077 Title: Xenial update: 4.4.167 upstream stable release Status in linux package in Ubuntu: Invalid 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.167 upstream stable release from git://git.kernel.org/ Linux 4.4.167 mac80211: ignore NullFunc frames in the duplicate detection mac80211: fix reordering of buffered broadcast packets mac80211: ignore tx status for PS stations in ieee80211_tx_status_ext mac80211: Clear beacon_int in ieee80211_do_stop mac80211_hwsim: Timer should be initialized before device registered kgdboc: fix KASAN global-out-of-bounds bug in param_set_kgdboc_var() tty: serial: 8250_mtk: always resume the device in probe. cifs: Fix separator when building path from dentry Staging: lustre: remove two build warnings xhci: Prevent U1/U2 link pm states if exit latency is too long SUNRPC: Fix leak of krb5p encode pages virtio/s390: fix race in ccw_io_helper() virtio/s390: avoid race on vcdev->config ALSA: pcm: Fix interval evaluation with openmin/max ALSA: pcm: Call snd_pcm_unlink() conditionally at closing ALSA: pcm: Fix starvation on down_write_nonblock() ALSA: hda: Add support for AMD Stoney Ridge ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in card.c USB: check usb_get_extra_descriptor for proper size usb: appledisplay: Add 27" Apple Cinema Display usb: quirk: add no-LPM quirk on SanDisk Ultra Flair device net: amd: add missing of_node_put() iommu/vt-d: Use memunmap to free memremap net: faraday: ftmac100: remove netif_running(netdev) check before disabling interrupts net/mlx4: Fix UBSAN warning of signed integer overflow net/mlx4_core: Fix uninitialized variable compilation warning net/mlx4_core: Zero out lkey field in SW2HW_MPT fw command qed: Fix reading wrong value in loop condition qed: Fix PTT leak in qed_drain() bnx2x: Assign unique DMAE channel number for FW DMAE transactions. batman-adv: Expand merged fragment buffer for full packet can: rcar_can: Fix erroneous registration iommu/ipmmu-vmsa: Fix crash on early domain free iommu/vt-d: Fix NULL pointer dereference in prq_event_thread() usb: gadget: dummy: fix nonsensical comparisons mm: mlock: avoid increase mm->locked_vm on mlock() when already mlock2(,MLOCK_ONFAULT) mm: cleancache: fix corruption on missed inode invalidation arc: [devboards] Add support of NFSv3 ACL ARC: change defconfig defaults to ARCv2 Btrfs: fix use-after-free when dumping free space btrfs: Always try all copies when reading extent buffers Input: elan_i2c - add support for ELAN0621 touchpad Input: elan_i2c - add ACPI ID for Lenovo IdeaPad 330-15ARR Input: elan_i2c - add ELAN0620 to the ACPI table Input: matrix_keypad - check for errors from of_get_named_gpio() Input: xpad - quirk all PDP Xbox One gamepads leds: leds-gpio: Fix return value check in create_gpio_led() leds: turn off the LED and wait for completion on unregistering LED class device leds: call led_pwm_set() in leds-pwm to enforce default LED_OFF kgdboc: Fix warning with module build kgdboc: Fix restrict error scsi: csiostor: Avoid content leaks and casts ALSA: trident: Suppress gcc string warning scsi: scsi_devinfo: cleanly zero-pad devinfo strings drm/ast: Fix incorrect free on ioregs mips: fix mips_get_syscall_arg o32 check MIPS: ralink: Fix mt7620 nd_sd pinmux uprobes: Fix handle_swbp() vs. unregister() + register() race once more iser: set sector for ambiguous mr status errors kdb: use memmove instead of overlapping memcpy staging: rts5208: fix gcc-8 logic error warning scsi: bfa: convert to strlcpy/strlcat drm: gma500: fix logic error ip_tunnel: Fix name string concatenate in __ip_tunnel_create() kernfs: Replace strncpy with memcpy unifdef: use memcpy instead of strncpy kobject: Replace strncpy with memcpy disable stringop truncation warnings for now exec: avoid gcc-8 warning for get_task_comm Kbuild: suppress packed-not-aligned warning for default setting only misc: mic/scif: fix copy-paste error in scif_create_remote_lookup usb: core: quirks: add RESET_RESUME quirk for Cherry G230 Stream series USB: usb-storage: Add new IDs to ums-realtek btrfs: release metadat
[Kernel-packages] [Bug 1811094] Re: iptables connlimit allows more connections than the limit when using multiple CPUs
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Cosmic)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811094
Title:
iptables connlimit allows more connections than the limit when using
multiple CPUs
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
New
Status in linux source package in Cosmic:
New
Bug description:
[Impact]
* The iptables connection count/limit rules can be breached
with multithreaded network driver/server/client (common)
due to a race in the conncount/connlimit code.
* For example:
# iptables -A INPUT -p tcp -m tcp --syn --dport \
-m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-j DROP
* The fix is a backport from an upstream commit that resolves
the problem (plus dependencies for a cleaner backport) that
address the race condition:
commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
collection confirm race").
[Test Case]
* Server-side: (relevant kernel side)
(limit TCP port to only 2000 connections)
# iptables -A INPUT -p tcp -m tcp --syn --dport \
-m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-j DROP
# ulimit -SHn 65000 # increase number of open files
# ruby server.rb # multi-threaded server
* Client-side:
# ulimit -SHn 65000
# ruby client.rb<# threads>
* Results with Original kernel:
(client achieves target of 6000 connections > limit of 2000 connections)
# ruby client.rb 10.230.56.100 6000 3
1
2
3
<...>
6000
Target reached. Thread finishing
6001
Target reached. Thread finishing
6002
Target reached. Thread finishing
Threads done. 6002 connections
press enter to exit
* Results with Modified kernel:
(client is limited to 2000 connections, and times out afterward)
# ruby client.rb 10.230.56.100 6000 3
1
2
3
<...>
2000
<... blocks for a few minutes ...>
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
Threads done. 2000 connections
press enter to exit
* Test cases possibly available upon request,
depending on original author's permission.
[Regression Potential]
* The patchset has been reviewed by a netfilter maintainer [1] in
stable mailing list, and was considered OK for 4.14, and that's
essentially the same backport for 4.15 and 4.4.
* The changes are limited to netfilter connlimit/conncount (names
change between older/newer kernel versions).
[Other Info]
* The backport for 4.14 [2] is applied as of 4.14.92.
[1] https://www.spinics.net/lists/stable/msg276883.html
[2] https://www.spinics.net/lists/stable/msg276910.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811094/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
