[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
Hi all got the issue on Thinkpad X1 Carbon 6th. dmesg: input: Synaptics TM3288-011 as /devices/rmi4-00/input/input20 cheers Andy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263): "/dev/input/event5" # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation 8 Series USB
[Kernel-packages] [Bug 1830361] Re: cpuset_sched_domains from controller test suite in LTP failed
Found on Eoan Azure 5.3.0-1009.10 Standard_D48_v3 ** Tags added: sru-20191202 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830361 Title: cpuset_sched_domains from controller test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Disco: New Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:24:26 2019' cpuset_sched_domains 1 TINFO: root group load balance test cpuset_sched_domains 1 TINFO: sched load balance: 0 cpuset_sched_domains 1 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 1 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 1 TFAIL: partition sched domains failed. cpuset_sched_domains 3 TINFO: root group load balance test cpuset_sched_domains 3 TINFO: sched load balance: 1 cpuset_sched_domains 3 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 3 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 3 TFAIL: partition sched domains failed. cpuset_sched_domains 5 TINFO: root group load balance test cpuset_sched_domains 5 TINFO: sched load balance: 0 cpuset_sched_domains 5 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 5 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 5 TFAIL: partition sched domains failed. cpuset_sched_domains 7 TINFO: root group load balance test cpuset_sched_domains 7 TINFO: sched load balance: 0 cpuset_sched_domains 7 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 7 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 7 TFAIL: partition sched domains failed. cpuset_sched_domains 9 TINFO: root group load balance test cpuset_sched_domains 9 TINFO: sched load balance: 1 cpuset_sched_domains 9 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 9 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 9 TFAIL: partition sched domains failed. cpuset_sched_domains 11 TINFO: root group load balance test cpuset_sched_domains 11 TINFO: sched load balance: 1 cpuset_sched_domains 11 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 11 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 11 TFAIL: partition sched domains failed. cpuset_sched_domains 13 TINFO: general group load balance test cpuset_sched_domains 13 TINFO: root group info: cpuset_sched_domains 13 TINFO: sched load balance: 0 cpuset_sched_domains 13 TINFO: general group info: cpuset_sched_domains 13 TINFO: cpus: - cpuset_sched_domains 13 TINFO: sched load balance: 1 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 13 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 13 TFAIL: partition sched domains failed. cpuset_sched_domains 15 TINFO: general group load balance test cpuset_sched_domains 15 TINFO: root group info: cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_sched_domains 15 TINFO: general group info: cpuset_sched_domains 15 TINFO: cpus: 1 cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 15 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 15 TFAIL: partition sched domains failed. cpuset_sched_domains 17 TINFO: general group load balance test cpuset_sched_domains 17 TINFO: root group info: cpuset_sched_domains 17 TINFO: sched load balance: 1 cpuset_sched_domains 17 TINFO: general group info: cpuset_sched_domains 17 TINFO: cpus: - cpuset_sched_domains 17 TINFO: sched load balance: 1 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 17 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 17 TFAIL: partition sched domains failed. cpuset_sched_domains 19 TINFO: general group load balance test
[Kernel-packages] [Bug 1830359] Re: cpuset_base_ops from controller test suite in LTP failed
Found on Eoan Azure 5.3.0-1009.10 Standard_D48_v3 ** Tags added: sru-20191202 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830359 Title: cpuset_base_ops from controller test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Disco: New Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:23:44 2019' cpuset_base_ops 1 TPASS: cpuset.cpus(READONLY): Get the expected string cpuset_base_ops 3 TPASS: cpuset.mems(READONLY): Get the expected string cpuset_base_ops 5 TPASS: cpuset.memory_pressure(READONLY): Get the expected string cpuset_base_ops 7 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 9 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 11 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 13 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 15 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 17 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 19 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 21 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 23 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 25 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 27 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 29 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 31 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 33 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 35 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 37 TFAIL: cpuset.cpus: Test result - Expected string - "0" cpuset_base_ops 39 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 41 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 43 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 45 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 47 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 49 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 51 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 53 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 55 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 57 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 59 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 61 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 63 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 65 TFAIL: cpuset.mems: Test result - Expected string - "0" cpuset_base_ops 67 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 69 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 71 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 73 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 75 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 77 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 79 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 81 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 83 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 85 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 87 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 89 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 91 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 93 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 95 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 97 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 99 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 101 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 103 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 105 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 107 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 109 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 111 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 113 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 115 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 117 TPASS: cpuset.memory_spread_slab: Get the expected string cpuset_base_ops 119 TPASS: cpuset.memory_spread_slab: Get the expected string cpuset_base_ops 121 TPASS: cpuset.memory_spread_slab: Get the expected string
[Kernel-packages] [Bug 1830360] Re: cpuset_load_balance from controller test suite in LTP failed
Found on Eoan Azure 5.3.0-1009.10 Standard_D48_v3 ** Tags added: sru-20191202 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830360 Title: cpuset_load_balance from controller test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Disco: New Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:24:55 2019' cpuset_load_balance 1 TINFO: general group load balance test cpuset_load_balance 1 TINFO: root group info: cpuset_load_balance 1 TINFO: sched load balance: 0 cpuset_load_balance 1 TINFO: general group info: cpuset_load_balance 1 TINFO: cpus: - cpuset_load_balance 1 TINFO: sched load balance: 1 cpuset_load_balance 1 TFAIL: load balance test failed. cpuset_load_balance 3 TINFO: general group load balance test cpuset_load_balance 3 TINFO: root group info: cpuset_load_balance 3 TINFO: sched load balance: 0 cpuset_load_balance 3 TINFO: general group info: cpuset_load_balance 3 TINFO: cpus: 1 cpuset_load_balance 3 TINFO: sched load balance: 0 cpuset_load_balance 3 TFAIL: load balance test failed. cpuset_load_balance 5 TINFO: general group load balance test cpuset_load_balance 5 TINFO: root group info: cpuset_load_balance 5 TINFO: sched load balance: 1 cpuset_load_balance 5 TINFO: general group info: cpuset_load_balance 5 TINFO: cpus: - cpuset_load_balance 5 TINFO: sched load balance: 1 cpuset_load_balance 5 TFAIL: load balance test failed. cpuset_load_balance 7 TINFO: general group load balance test cpuset_load_balance 7 TINFO: root group info: cpuset_load_balance 7 TINFO: sched load balance: 1 cpuset_load_balance 7 TINFO: general group info: cpuset_load_balance 7 TINFO: cpus: 1 cpuset_load_balance 7 TINFO: sched load balance: 1 cpuset_load_balance 7 TFAIL: load balance test failed. cpuset_load_balance 9 TINFO: general group load balance test cpuset_load_balance 9 TINFO: root group info: cpuset_load_balance 9 TINFO: sched load balance: 0 cpuset_load_balance 9 TINFO: general group info: cpuset_load_balance 9 TINFO: cpus: 1,2 cpuset_load_balance 9 TINFO: sched load balance: 0 cpuset_load_balance 9 TFAIL: load balance test failed. cpuset_load_balance 11 TINFO: general group load balance test cpuset_load_balance 11 TINFO: root group info: cpuset_load_balance 11 TINFO: sched load balance: 0 cpuset_load_balance 11 TINFO: general group info: cpuset_load_balance 11 TINFO: cpus: 1,2 cpuset_load_balance 11 TINFO: sched load balance: 1 cpuset_load_balance 11 TFAIL: load balance test failed. cpuset_load_balance 13 TINFO: general group load balance test cpuset_load_balance 13 TINFO: root group info: cpuset_load_balance 13 TINFO: sched load balance: 0 cpuset_load_balance 13 TINFO: general group info: cpuset_load_balance 13 TINFO: cpus: 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39 cpuset_load_balance 13 TINFO: sched load balance: 1 cpuset_load_balance 13 TFAIL: load balance test failed. cpuset_load_balance 15 TINFO: general group load balance test cpuset_load_balance 15 TINFO: root group info: cpuset_load_balance 15 TINFO: sched load balance: 0 cpuset_load_balance 15 TINFO: general group1 info: cpuset_load_balance 15 TINFO: cpus: 1 cpuset_load_balance 15 TINFO: sched load balance: 1 cpuset_load_balance 15 TINFO: general group2 info: cpuset_load_balance 15 TINFO: cpus: 0 cpuset_load_balance 15 TINFO: sched load balance: 1 cpuset_load_balance 15 TINFO: CPU hotplug: none cpuset_load_balance 15 TFAIL: load balance test failed. cpuset_load_balance 17 TINFO: general group load balance test cpuset_load_balance 17 TINFO: root group info: cpuset_load_balance 17 TINFO: sched load balance: 0 cpuset_load_balance 17 TINFO: general group1 info: cpuset_load_balance 17 TINFO: cpus: 1,2 cpuset_load_balance 17 TINFO: sched load balance: 1 cpuset_load_balance 17 TINFO: general group2 info: cpuset_load_balance 17 TINFO: cpus: 0-3 cpuset_load_balance 17 TINFO: sched load balance: 0 cpuset_load_balance 17 TINFO: CPU hotplug: none cpuset_load_balance 17 TFAIL: load balance test failed. cpuset_load_balance 19 TINFO: general group load balance test cpuset_load_balance 19 TINFO: root group info: cpuset_load_balance 19 TINFO: sched load balance: 0 cpuset_load_balance 19 TINFO: general group1 info: cpuset_load_balance 19 TINFO: cpus: 1,2 cpuset_load_balance 19 TINFO: sched load balance: 1 cpuset_load_balance
[Kernel-packages] [Bug 1854751] Re: eoan/linux-gcp: 5.3.0-1010.11 -proposed tracker
5.3.0-1010.11 - gcp Regression test CMPL, RTB. Issue to note in gcp: ubuntu_fan_smoke_test - failed with unknown underlay network format (bug 1840904) ubuntu_k8s_unit_tests - cmd (bug 1855808) vclib (bug 1855809) podautoscaler (bug 1855810) container (bug 1855811) kuberuntime (bug 1855812) ipset (bug 1855813) label (bug 1855814) flag (bug 1855815) naming (bug 1855816) ubuntu_kernel_selftests - test_bpf in net (bug 1812189) test_blackhole_dev in net (bug 1851619) msg_zerocopy in net (bug 1812620) ubuntu_ltp - test timeouted with 4 hours threshold on jenkins (bug 1837206) ubuntu_ltp_syscalls - msgstress03 (bug 1797341) signal06 (bug 1855817) ubuntu_sysdig_smoke_test - test failed with 0 read / write event from dd (bug 1844493) Skipped / blacklisted: * libhugetlbfs ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1854751 Title: eoan/linux-gcp: 5.3.0-1010.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 05. December 2019 12:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-5.3: bug 1854750 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854751] Re: eoan/linux-gcp: 5.3.0-1010.11 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 05. December 2019 12:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-5.3: bug 1854750 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1854751 Title: eoan/linux-gcp: 5.3.0-1010.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 05. December 2019 12:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-5.3: bug 1854750 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855811] Re: container from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
** Description changed: Issue found on 5.3.0-1010 Eoan GCP # k8s.io/kubernetes/pkg/kubelet/container pkg/kubelet/container/sync_result_test.go:48:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:56:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:66:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult []*k8s.io/kubernetes/pkg/kubelet/container.Pod FAIL k8s.io/kubernetes/pkg/kubelet/container [build failed] + + This is not a regression as this failure can be found in + 5.3.0-1009.10-gcp as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855811 Title: container from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP # k8s.io/kubernetes/pkg/kubelet/container pkg/kubelet/container/sync_result_test.go:48:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:56:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:66:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult []*k8s.io/kubernetes/pkg/kubelet/container.Pod FAIL k8s.io/kubernetes/pkg/kubelet/container [build failed] This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855812] Re: kuberuntime from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
** Description changed: Issue found on 5.3.0-1010 Eoan GCP # k8s.io/kubernetes/pkg/kubelet/kuberuntime - pkg/kubelet/kuberuntime/kuberuntime_manager_test.go:388:3: Errorf format %q has arg expected of wrong type + pkg/kubelet/kuberuntime/kuberuntime_manager_test.go:388:3: Errorf format %q has arg expected of wrong type FAIL k8s.io/kubernetes/pkg/kubelet/kuberuntime [build failed] + + This is not a regression as this failure can be found in + 5.3.0-1009.10-gcp as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855812 Title: kuberuntime from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP # k8s.io/kubernetes/pkg/kubelet/kuberuntime pkg/kubelet/kuberuntime/kuberuntime_manager_test.go:388:3: Errorf format %q has arg expected of wrong type FAIL k8s.io/kubernetes/pkg/kubelet/kuberuntime [build failed] This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855793] 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 1855793 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/1855793 Title: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Oftentimes, when I am using my PC, the Wi-Fi will drop all of a sudden and I will then be forced to turn the Wi-Fi off and then back on again, which is annoying. And even then, the Wi-Fi becomes unusually slow afterwards. Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 20:35:53 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575941718 Mon 09 Dec 2019 08:35:18 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575939877 Mon 09 Dec 2019 08:04:37 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/2 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853197] Re: Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853197 Title: Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [SRU Justification] == Impact == An upstream change in v4.11 made xfrm loose memory (8 pages per ipsec connection). This was fixed in v5.4 by: commit 86c6739eda7d "xfrm: Fix memleak on xfrm state destroy" == Fix == Pick the upstream fix into all affected series. == Testcase == see below == Risk of Regression == Low, the change adds a single memory release case in one driver. The effect can be verified. --- Ubuntu linux distro, 4.15.0-62 kernel, server platform. This OS is used as an IPSec VPN gateway. It serves up to several hundred concurrent connections In an attempt to upgrade from the 4.4 kernel to 4.15, the team noticed that VPN gateway VMs were running out of physical memory after 12-48 hours, depending on load. Attachments from a server machine in this state in attached leakinfo.txt output of free -t output of /proc/meminfo in out of memory condition output of /slabtop -o -sc /sys/kernel/debug/page_owner sorted and aggregated after server ran for 12 hrs and ran out of memory Patches for 4.15 and 5.4 Highlight from page_owner, we can see the leak is a buffer associated with the ipsec impelementation. Each connection leaks 32k of memory via alloc_page with order=3 100960 times: Page allocated via order 3, mask 0x1085220(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP) get_page_from_freelist+0xd64/0x1250 __alloc_pages_nodemask+0x11c/0x2e0 alloc_pages_current+0x6a/0xe0 skb_page_frag_refill+0x71/0x100 esp_output_head+0x265/0x3e0 [esp4] esp_output+0xbc/0x180 [esp4] xfrm_output_resume+0x179/0x530 xfrm_output+0x8e/0x230 xfrm4_output_finish+0x2b/0x30 __xfrm4_output+0x3a/0x50 xfrm4_output+0x43/0xc0 ip_forward_finish+0x51/0x80 ip_forward+0x38a/0x480 ip_rcv_finish+0x122/0x410 ip_rcv+0x292/0x360 __netif_receive_skb_core+0x815/0xbd0 Patch to fix this issue in 4.15 (tested and verified on same server exhibiting above leak): diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c index 728272f..7842f83 100644 --- a/net/xfrm/xfrm_state.c +++ b/net/xfrm/xfrm_state.c @@ -451,6 +451,10 @@ static void xfrm_state_gc_destroy(struct xfrm_state *x) } xfrm_dev_state_free(x); security_xfrm_state_free(x); + + if(x->xfrag.page) + put_page(x->xfrag.page); + kfree(x); } Patch for master branch (5.4 I believe) from Paul Wouters (p...@nohats.ca) diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c index c6f3c4a1bd99..f3423562d933 100644 --- a/net/xfrm/xfrm_state.c +++ b/net/xfrm/xfrm_state.c @@ -495,6 +495,8 @@ static void ___xfrm_state_destroy(struct xfrm_state *x) x->type->destructor(x); xfrm_put_type(x->type); } + if (x->xfrag.page) + put_page(x->xfrag.page); xfrm_dev_state_free(x); security_xfrm_state_free(x); xfrm_state_free(x); Severity: Critical - we are unable to use any kernel later than 4.11, and are sticking with 4.4 in production. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855809] Re: vclib from ubuntu_k8s_unit_tests fail on Eoan 5.3 GCP
** Description changed:
Issue found on 5.3.0-1010 Eoan GCP
- E1207 09:14:34.779687 29118 datacenter.go:45] Failed to find the datacenter:
enoent. err: datacenter 'enoent' not found
- E1207 09:14:34.783331 29118 datacenter.go:78] Unable to find VM by UUID. VM
UUID: enoent
- E1207 09:14:34.785587 29118 datacenter.go:106] Failed to find VM by Path. VM
Path: enoent, err: vm 'enoent' not found
- E1207 09:14:34.787217 29118 datacenter.go:153] Failed to parse vmDiskPath:
enoent
- E1207 09:14:34.788754 29118 datacenter.go:165] Failed while searching for
datastore: enoent. err: datastore 'enoent' not found
- E1207 09:14:34.792557 29118 datacenter.go:165] Failed while searching for
datastore: enoent. err: datastore 'enoent' not found
- E1207 09:14:34.801865 29118 datacenter.go:191] Failed to get the folder
reference for enoent. err: folder 'enoent' not found
- E1207 09:14:34.804569 29118 datacenter.go:203] VirtualMachine Object list is
empty
- E1207 09:14:34.805548 29118 datacenter.go:213] Failed to get VM managed
objects from VM objects. vmObjList: [VirtualMachine:vm-54 @
/DC0/vm/DC0_H0_VM1], properties: [enoent], err: InvalidProperty
- E1207 09:14:34.806781 29118 datacenter.go:241] Datastore Object list is empty
- E1207 09:14:34.807159 29118 datacenter.go:251] Failed to get Datastore
managed objects from datastore objects. dsObjList:
[Datastore:/tmp/govcsim-DC0-LocalDS_0-314024335@folder-5 @
/DC0/datastore/LocalDS_0], properties: [enoent], err: InvalidProperty
- E1207 09:14:34.968117 29118 connection.go:180] Failed to create new client.
err: EOF
- 2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:58028: remote
error: tls: bad certificate
- E1207 09:14:35.039988 29118 connection.go:180] Failed to create new client.
err: Post https://127.0.0.1:35147/sdk: Host "127.0.0.1:35147" thumbprint does
not match "obviously wrong"
- E1207 09:14:35.052610 29118 connection.go:180] Failed to create new client.
err: Post https://127.0.0.1:40591/sdk: x509: certificate signed by unknown
authority
- 2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:37506: remote
error: tls: bad certificate
- 2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:33050: remote
error: tls: bad certificate
- E1207 09:14:35.081393 29118 connection.go:180] Failed to create new client.
err: EOF
- E1207 09:14:35.081489 29118 connection.go:163] Failed to parse URL: . err:
parse https://should-not-matter:should-not-matter: invalid port
":should-not-matter" after host
- --- FAIL: TestWithInvalidCaCertPath (0.00s)
- connection_test.go:168: Expected an os.PathError, got: 'parse
https://should-not-matter:should-not-matter: invalid port ":should-not-matter"
after host' ({Op:"parse",
URL:"https://should-not-matter:should-not-matter;,
Err:(*errors.errorString)(0xc0004fcd70)})
- E1207 09:14:35.081626 29118 connection.go:163] Failed to parse URL: . err:
parse https://should-not-matter:should-not-matter: invalid port
":should-not-matter" after host
- --- FAIL: TestInvalidCaCert (0.00s)
- connection_test.go:182: Expected invalid certificate error, got 'parse
https://should-not-matter:should-not-matter: invalid port ":should-not-matter"
after host'
- FAIL
- FAIL k8s.io/kubernetes/pkg/cloudprovider/providers/vsphere/vclib 0.319s
+ E1207 09:14:34.779687 29118 datacenter.go:45] Failed to find the datacenter:
enoent. err: datacenter 'enoent' not found
+ E1207 09:14:34.783331 29118 datacenter.go:78] Unable to find VM by UUID. VM
UUID: enoent
+ E1207 09:14:34.785587 29118 datacenter.go:106] Failed to find VM by Path. VM
Path: enoent, err: vm 'enoent' not found
+ E1207 09:14:34.787217 29118 datacenter.go:153] Failed to parse vmDiskPath:
enoent
+ E1207 09:14:34.788754 29118 datacenter.go:165] Failed while searching for
datastore: enoent. err: datastore 'enoent' not found
+ E1207 09:14:34.792557 29118 datacenter.go:165] Failed while searching for
datastore: enoent. err: datastore 'enoent' not found
+ E1207 09:14:34.801865 29118 datacenter.go:191] Failed to get the folder
reference for enoent. err: folder 'enoent' not found
+ E1207 09:14:34.804569 29118 datacenter.go:203] VirtualMachine Object list is
empty
+ E1207 09:14:34.805548 29118 datacenter.go:213] Failed to get VM managed
objects from VM objects. vmObjList: [VirtualMachine:vm-54 @
/DC0/vm/DC0_H0_VM1], properties: [enoent], err: InvalidProperty
+ E1207 09:14:34.806781 29118 datacenter.go:241] Datastore Object list is empty
+ E1207 09:14:34.807159 29118 datacenter.go:251] Failed to get Datastore
managed objects from datastore objects. dsObjList:
[Datastore:/tmp/govcsim-DC0-LocalDS_0-314024335@folder-5 @
/DC0/datastore/LocalDS_0], properties: [enoent], err: InvalidProperty
+ E1207 09:14:34.968117 29118 connection.go:180] Failed to create new client.
err: EOF
+ 2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:58028: remote
error: tls: bad certificate
+ E1207 09:14:35.039988 29118
[Kernel-packages] [Bug 1855808] Re: cmd from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
** Description changed: Issue found on 5.3.0-1010 Eoan GCP + [preflight] running pre-flight checks + [preflight] running pre-flight checks + [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test690031695/manifests /tmp/kubeadm-reset-test690031695/pki] + [reset] deleting files: [/tmp/kubeadm-reset-test690031695/admin.conf /tmp/kubeadm-reset-test690031695/kubelet.conf /tmp/kubeadm-reset-test690031695/bootstrap-kubelet.conf /tmp/kubeadm-reset-test690031695/controller-manager.conf /tmp/kubeadm-reset-test690031695/scheduler.conf] + [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test190360418/manifests /tmp/kubeadm-reset-test190360418/pki] + [reset] deleting files: [/tmp/kubeadm-reset-test190360418/admin.conf /tmp/kubeadm-reset-test190360418/kubelet.conf /tmp/kubeadm-reset-test190360418/bootstrap-kubelet.conf /tmp/kubeadm-reset-test190360418/controller-manager.conf /tmp/kubeadm-reset-test190360418/scheduler.conf] + [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test519448409/manifests /tmp/kubeadm-reset-test519448409/pki] + [reset] deleting files: [/tmp/kubeadm-reset-test519448409/admin.conf /tmp/kubeadm-reset-test519448409/kubelet.conf /tmp/kubeadm-reset-test519448409/bootstrap-kubelet.conf /tmp/kubeadm-reset-test519448409/controller-manager.conf /tmp/kubeadm-reset-test519448409/scheduler.conf] + [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test499669220/manifests /tmp/kubeadm-reset-test499669220/pki] + [reset] deleting files: [/tmp/kubeadm-reset-test499669220/admin.conf /tmp/kubeadm-reset-test499669220/kubelet.conf /tmp/kubeadm-reset-test499669220/bootstrap-kubelet.conf /tmp/kubeadm-reset-test499669220/controller-manager.conf /tmp/kubeadm-reset-test499669220/scheduler.conf] + [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test469422835/manifests /tmp/kubeadm-reset-test469422835/test-path] + E1207 09:05:16.966842 26490 reset.go:227] [reset] failed to remove directory: "/tmp/kubeadm-reset-test469422835/test-path" [readdirent: not a directory] + [reset] deleting files: [/tmp/kubeadm-reset-test469422835/admin.conf /tmp/kubeadm-reset-test469422835/kubelet.conf /tmp/kubeadm-reset-test469422835/bootstrap-kubelet.conf /tmp/kubeadm-reset-test469422835/controller-manager.conf /tmp/kubeadm-reset-test469422835/scheduler.conf] + [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test838040502/manifests /tmp/kubeadm-reset-test838040502/pki] + [reset] deleting files: [/tmp/kubeadm-reset-test838040502/admin.conf /tmp/kubeadm-reset-test838040502/kubelet.conf /tmp/kubeadm-reset-test838040502/bootstrap-kubelet.conf /tmp/kubeadm-reset-test838040502/controller-manager.conf /tmp/kubeadm-reset-test838040502/scheduler.conf] + [dryrun] Would perform action DELETE on resource "secrets" in API group "core/v1" + [dryrun] Resource name: "bootstrap-token-abcdef" + [dryrun] Would perform action DELETE on resource "secrets" in API group "core/v1" + [dryrun] Resource name: "bootstrap-token-abcdef" + [dryrun] Would perform action DELETE on resource "secrets" in API group "core/v1" + [dryrun] Resource name: "bootstrap-token-abcdef" + [dryrun] Would perform action LIST on resource "secrets" in API group "core/v1" + dummy API server listening on localhost:9008 + Running HTTP test case (0) "token-id not defined" + [dryrun] Would perform action LIST on resource "secrets" in API group "core/v1" + panic: test timed out after 2m0s - [preflight] running pre-flight checks - [preflight] running pre-flight checks - [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test690031695/manifests /tmp/kubeadm-reset-test690031695/pki] - [reset] deleting files: [/tmp/kubeadm-reset-test690031695/admin.conf /tmp/kubeadm-reset-test690031695/kubelet.conf /tmp/kubeadm-reset-test690031695/bootstrap-kubelet.conf /tmp/kubeadm-reset-test690031695/controller-manager.conf /tmp/kubeadm-reset-test690031695/scheduler.conf] - [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test190360418/manifests /tmp/kubeadm-reset-test190360418/pki] - [reset] deleting files: [/tmp/kubeadm-reset-test190360418/admin.conf /tmp/kubeadm-reset-test190360418/kubelet.conf /tmp/kubeadm-reset-test190360418/bootstrap-kubelet.conf /tmp/kubeadm-reset-test190360418/controller-manager.conf /tmp/kubeadm-reset-test190360418/scheduler.conf] - [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test519448409/manifests /tmp/kubeadm-reset-test519448409/pki] - [reset] deleting files: [/tmp/kubeadm-reset-test519448409/admin.conf /tmp/kubeadm-reset-test519448409/kubelet.conf /tmp/kubeadm-reset-test519448409/bootstrap-kubelet.conf /tmp/kubeadm-reset-test519448409/controller-manager.conf /tmp/kubeadm-reset-test519448409/scheduler.conf] - [reset] deleting contents of config directories:
[Kernel-packages] [Bug 1855813] Re: ipset from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
** Description changed: Issue found on 5.3.0-1010 Eoan GCP FAILk8s.io/kubernetes/pkg/util/ipset [build failed] No other information from the test report, might need to run this manually to collect more details. + + This is not a regression as this failure can be found in + 5.3.0-1009.10-gcp as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855813 Title: ipset from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP FAILk8s.io/kubernetes/pkg/util/ipset [build failed] No other information from the test report, might need to run this manually to collect more details. This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855810] Re: podautoscaler from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
** Description changed: Issue found on 5.3.0-1010 Eoan GCP Test failed with: - panic: test timed out after 2m0s + panic: test timed out after 2m0s (error message too long, please refer to the attachment) - /tmp/kubernetes.git/_output/local/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:69 +0x62 - FAIL k8s.io/kubernetes/pkg/controller/podautoscaler 120.039s + /tmp/kubernetes.git/_output/local/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:69 +0x62 + FAIL k8s.io/kubernetes/pkg/controller/podautoscaler 120.039s + + This is not a regression as this failure can be found in + 5.3.0-1009.10-gcp as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855810 Title: podautoscaler from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP Test failed with: panic: test timed out after 2m0s (error message too long, please refer to the attachment) /tmp/kubernetes.git/_output/local/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:69 +0x62 FAIL k8s.io/kubernetes/pkg/controller/podautoscaler 120.039s This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855814] Re: label from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
** Description changed: Issue found on 5.3.0-1010 Eoan GCP FAIL k8s.io/kubernetes/plugin/pkg/admission/storage/persistentvolume/label [build failed] No other information from the test report, might need to run this manually to collect more details. + + This is not a regression as this failure can be found in + 5.3.0-1009.10-gcp as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855814 Title: label from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP FAIL k8s.io/kubernetes/plugin/pkg/admission/storage/persistentvolume/label [build failed] No other information from the test report, might need to run this manually to collect more details. This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855816] Re: naming from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
** Description changed: Issue found on 5.3.0-1010 Eoan GCP - --- FAIL: TestGetNameFromCallsite (0.00s) - --- FAIL: TestGetNameFromCallsite/ignore-package (0.00s) - from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" - --- FAIL: TestGetNameFromCallsite/ignore-file (0.00s) - from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" - FAIL - FAIL k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/naming0.002s + --- FAIL: TestGetNameFromCallsite (0.00s) + --- FAIL: TestGetNameFromCallsite/ignore-package (0.00s) + from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" + --- FAIL: TestGetNameFromCallsite/ignore-file (0.00s) + from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" + FAIL + FAIL k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/naming0.002s + + This is not a regression as this failure can be found in + 5.3.0-1009.10-gcp as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855816 Title: naming from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP --- FAIL: TestGetNameFromCallsite (0.00s) --- FAIL: TestGetNameFromCallsite/ignore-package (0.00s) from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" --- FAIL: TestGetNameFromCallsite/ignore-file (0.00s) from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" FAIL FAIL k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/naming0.002s This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855815] Re: flag from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
** Description changed: Issue found on 5.3.0-1010 Eoan GCP - --- FAIL: TestConstantMaps (0.07s) - ciphersuites_flag_test.go:106: discovered version tls.VersionTLS13 not in version map - FAIL - FAIL k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/util/flag 0.072s + --- FAIL: TestConstantMaps (0.07s) + ciphersuites_flag_test.go:106: discovered version tls.VersionTLS13 not in version map + FAIL + FAIL k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/util/flag 0.072s + + This is not a regression as this failure can be found in + 5.3.0-1009.10-gcp as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855815 Title: flag from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP --- FAIL: TestConstantMaps (0.07s) ciphersuites_flag_test.go:106: discovered version tls.VersionTLS13 not in version map FAIL FAIL k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/util/flag 0.072s This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855817] Re: signal06 from ubuntu_ltp_syscalls failed on Eoan 5.3 GCP
** Description changed: Issue found on 5.3.0-1010 Eoan GCP - startup='Sat Dec 7 10:43:06 2019' - signal06 0 TINFO : loop = 10771 - signal06 1 TFAIL : signal06.c:87: Bug Reproduced! - tag=signal06 stime=1575715386 dur=1 exit=exited stat=1 core=no cu=1 cs=3 + startup='Sat Dec 7 10:43:06 2019' + signal06 0 TINFO : loop = 10771 + signal06 1 TFAIL : signal06.c:87: Bug Reproduced! + tag=signal06 stime=1575715386 dur=1 exit=exited stat=1 core=no cu=1 cs=3 + + This is not a regression as this failure can be found in + 5.3.0-1009.10-gcp as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855817 Title: signal06 from ubuntu_ltp_syscalls failed on Eoan 5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP startup='Sat Dec 7 10:43:06 2019' signal06 0 TINFO : loop = 10771 signal06 1 TFAIL : signal06.c:87: Bug Reproduced! tag=signal06 stime=1575715386 dur=1 exit=exited stat=1 core=no cu=1 cs=3 This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855825] Re: When connecting to wifi with the proposed linux-oem kernel , the system hangs
** Attachment added: "var.log.201906-27119-191210tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem/+bug/1855825/+attachment/5311303/+files/var.log.201906-27119-191210tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1855825 Title: When connecting to wifi with the proposed linux-oem kernel , the system hangs Status in linux-meta-oem package in Ubuntu: New Bug description: Dell XPS 13 7390 (CID 201906-27119) Pre-load Ubuntu kernel: linux-oem 4.15.0-1066.76-oem [Description] The system hangs when connecting to wifi [Steps to Reproduce] Connect to bg-wifi over the wifi applet of your desktop. Select the SSID and then being prompted for a password. The system hangs immediately after entering the password. Reproducing Rate: 100% [Expected Result] Wifi works and the system keeps running. [Actual Result] System hangs. [Additional Information] 4.15.0-1066 oem kernel looks good for this test case. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1066.70 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Tue Dec 10 13:47:54 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-10-08 (63 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem/+bug/1855825/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855793] Re: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855793 Title: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Oftentimes, when I am using my PC, the Wi-Fi will drop all of a sudden and I will then be forced to turn the Wi-Fi off and then back on again, which is annoying. And even then, the Wi-Fi becomes unusually slow afterwards. Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 20:35:53 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575941718 Mon 09 Dec 2019 08:35:18 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575939877 Mon 09 Dec 2019 08:04:37 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/2 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855825] [NEW] When connecting to wifi with the proposed linux-oem kernel , the system hangs
Public bug reported: Dell XPS 13 7390 (CID 201906-27119) Pre-load Ubuntu kernel: linux-oem 4.15.0-1066.76-oem [Description] The system hangs when connecting to wifi [Steps to Reproduce] Connect to bg-wifi over the wifi applet of your desktop. Select the SSID and then being prompted for a password. The system hangs immediately after entering the password. Reproducing Rate: 100% [Expected Result] Wifi works and the system keeps running. [Actual Result] System hangs. [Additional Information] 4.15.0-1066 oem kernel looks good for this test case. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1066.70 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Tue Dec 10 13:47:54 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-10-08 (63 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-oem (Ubuntu) Importance: Undecided Status: New ** Tags: 201906-27119 amd64 apport-bug bionic package-from-proposed taipei-lab uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1855825 Title: When connecting to wifi with the proposed linux-oem kernel , the system hangs Status in linux-meta-oem package in Ubuntu: New Bug description: Dell XPS 13 7390 (CID 201906-27119) Pre-load Ubuntu kernel: linux-oem 4.15.0-1066.76-oem [Description] The system hangs when connecting to wifi [Steps to Reproduce] Connect to bg-wifi over the wifi applet of your desktop. Select the SSID and then being prompted for a password. The system hangs immediately after entering the password. Reproducing Rate: 100% [Expected Result] Wifi works and the system keeps running. [Actual Result] System hangs. [Additional Information] 4.15.0-1066 oem kernel looks good for this test case. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1066.70 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Tue Dec 10 13:47:54 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-10-08 (63 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem/+bug/1855825/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
I did it from the proposed channel and the touchpad works perfectly, but when will the kernel be available from the official channels? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263): "/dev/input/event5" # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation 8
[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
I tried the commands written by AaronMa, but it did not work. So, I just boot with 4.15.0-70-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/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263): "/dev/input/event5" # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0
[Kernel-packages] [Bug 1844493] Re: ubuntu_sysdig_smoke_test failed on Eoan
** Tags added: sru-20191202 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1844493 Title: ubuntu_sysdig_smoke_test failed on Eoan Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux source package in Eoan: Incomplete Status in linux-aws source package in Eoan: New Status in linux-azure source package in Eoan: New Status in linux-gcp source package in Eoan: New Bug description: Test failed with: FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Steps: sudo apt-get install git python-minimal python-yaml gdb -y git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_sysdig_smoke_test/control Test output: == sysdig smoke test to trace dd, cat, read and writes == Limiting raw capture file to 16384 blocks Try 1 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 18 Mbytes Try 2 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 22 Mbytes Try 3 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 4 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 5 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 6 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 7 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 8 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 9 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 10 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Found: 279845 sysdig events 29882 context switches 0 reads from /dev/zero by dd 0 writes to /dev/null by dd PASSED (trace at least 25 context switches) FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Summary: 1 passed, 2 failed ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: User Name 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 18 08:10 seq crw-rw 1 root audio 116, 33 Sep 18 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu7 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: Wed Sep 18 08:18:54 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias:
[Kernel-packages] [Bug 1855817] [NEW] signal06 from ubuntu_ltp_syscalls failed on Eoan 5.3 GCP
Public bug reported: Issue found on 5.3.0-1010 Eoan GCP startup='Sat Dec 7 10:43:06 2019' signal06 0 TINFO : loop = 10771 signal06 1 TFAIL : signal06.c:87: Bug Reproduced! tag=signal06 stime=1575715386 dur=1 exit=exited stat=1 core=no cu=1 cs=3 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Tags: 5.3 amd64 eoan gcp sru-20191202 ubuntu-ltp-syscalls ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855817 Title: signal06 from ubuntu_ltp_syscalls failed on Eoan 5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP startup='Sat Dec 7 10:43:06 2019' signal06 0 TINFO : loop = 10771 signal06 1 TFAIL : signal06.c:87: Bug Reproduced! tag=signal06 stime=1575715386 dur=1 exit=exited stat=1 core=no cu=1 cs=3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824136] Re: ubuntu_k8s_unit_tests failed with GCP
scheduler and spdy passed on Eoan 5.3 GCP (5.3.0-1010) ok k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler 48.528s ok k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/httpstream/spdy 0.197s -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1824136 Title: ubuntu_k8s_unit_tests failed with GCP Status in ubuntu-kernel-tests: Confirmed Status in linux-signed-gcp package in Ubuntu: New Bug description: There are 3 failures found on Cosmic GCP (n1-highcpu-16) * k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler * k8s.io/kubernetes/pkg/master * k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/httpstream/spdy [build failed] Steps to reproduce: sudo apt-get install git python-minimal python-yaml gdb -y git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_k8s_unit_tests/control Error messages: * k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler --- FAIL: TestUpdateNodeWithMultiplePods (2.56s) taint_manager_test.go:486: Starting testcase "Pods with different toleration times are evicted appropriately" taint_manager_test.go:512: Sleeping for 499.999448ms taint_manager_test.go:521: Found not-delete action with verb list. Ignoring. taint_manager_test.go:538: Found not-delete action with verb list. Ignoring. taint_manager_test.go:512: Sleeping for 594.563805ms taint_manager_test.go:532: Failed to deleted pod pod2 after 0 taint_manager_test.go:486: Starting testcase "Evict all pods not matching all taints instantly" taint_manager_test.go:512: Sleeping for 499.999844ms taint_manager_test.go:521: Found not-delete action with verb list. Ignoring. taint_manager_test.go:521: Found not-delete action with verb list. Ignoring. taint_manager_test.go:521: Found not-delete action with verb list. Ignoring. taint_manager_test.go:538: Found not-delete action with verb list. Ignoring. FAIL FAIL k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler 35.544s * k8s.io/kubernetes/pkg/master 2019-03-21 16:02:16.793715 I | integration: launching 2444030890339279063 (unix://localhost:24440308903392790630) 2019-03-21 16:02:16.798460 I | etcdserver: name = 2444030890339279063 2019-03-21 16:02:16.798550 I | etcdserver: data dir = /tmp/etcd396328703 2019-03-21 16:02:16.798566 I | etcdserver: member dir = /tmp/etcd396328703/member 2019-03-21 16:02:16.798576 I | etcdserver: heartbeat = 10ms 2019-03-21 16:02:16.798585 I | etcdserver: election = 100ms 2019-03-21 16:02:16.798594 I | etcdserver: snapshot count = 0 2019-03-21 16:02:16.798635 I | etcdserver: advertise client URLs = unix://127.0.0.1:2100211086 2019-03-21 16:02:16.798657 I | etcdserver: initial advertise peer URLs = unix://127.0.0.1:2100111086 2019-03-21 16:02:16.798676 I | etcdserver: initial cluster = 2444030890339279063=unix://127.0.0.1:2100111086 2019-03-21 16:02:16.804030 I | etcdserver: starting member d951fd13cdcf6e11 in cluster b8d26aa038f828d 2019-03-21 16:02:16.804137 I | raft: d951fd13cdcf6e11 became follower at term 0 2019-03-21 16:02:16.804164 I | raft: newRaft d951fd13cdcf6e11 [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0] 2019-03-21 16:02:16.804206 I | raft: d951fd13cdcf6e11 became follower at term 1 2019-03-21 16:02:16.818807 W | auth: simple token is not cryptographically signed 2019-03-21 16:02:16.822703 I | etcdserver: set snapshot count to default 10 2019-03-21 16:02:16.822805 I | etcdserver: starting server... [version: 3.2.13, cluster version: to_be_decided] 2019-03-21 16:02:16.823182 I | integration: launched 2444030890339279063 (unix://localhost:24440308903392790630) 2019-03-21 16:02:16.825229 I | etcdserver/membership: added member d951fd13cdcf6e11 [unix://127.0.0.1:2100111086] to cluster b8d26aa038f828d 2019-03-21 16:02:16.885057 I | raft: d951fd13cdcf6e11 is starting a new election at term 1 2019-03-21 16:02:16.885151 I | raft: d951fd13cdcf6e11 became candidate at term 2 2019-03-21 16:02:16.885168 I | raft: d951fd13cdcf6e11 received MsgVoteResp from d951fd13cdcf6e11 at term 2 2019-03-21 16:02:16.885180 I | raft: d951fd13cdcf6e11 became leader at term 2 2019-03-21 16:02:16.885187 I | raft: raft.node: d951fd13cdcf6e11 elected leader d951fd13cdcf6e11 at term 2 2019-03-21 16:02:16.885759 I | etcdserver: setting up the initial cluster version to 3.2 2019-03-21 16:02:16.886707 N | etcdserver/membership: set the initial cluster version to 3.2 2019-03-21 16:02:16.886797 I | etcdserver/api: enabled capabilities for
[Kernel-packages] [Bug 1855812] Re: kuberuntime from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
** Description changed: Issue found on 5.3.0-1010 Eoan GCP - FAILk8s.io/kubernetes/pkg/kubelet/kuberuntime [build failed] - - No other information from the test report, might need to run this - manually to collect more details. + # k8s.io/kubernetes/pkg/kubelet/kuberuntime + pkg/kubelet/kuberuntime/kuberuntime_manager_test.go:388:3: Errorf format %q has arg expected of wrong type + FAIL k8s.io/kubernetes/pkg/kubelet/kuberuntime [build failed] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855812 Title: kuberuntime from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP # k8s.io/kubernetes/pkg/kubelet/kuberuntime pkg/kubelet/kuberuntime/kuberuntime_manager_test.go:388:3: Errorf format %q has arg expected of wrong type FAIL k8s.io/kubernetes/pkg/kubelet/kuberuntime [build failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855815] [NEW] flag from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
Public bug reported: Issue found on 5.3.0-1010 Eoan GCP --- FAIL: TestConstantMaps (0.07s) ciphersuites_flag_test.go:106: discovered version tls.VersionTLS13 not in version map FAIL FAIL k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/util/flag 0.072s ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Tags: 5.3 amd64 eoan gcp sru-20191202 ubuntu-k8s-unit-tests ** Tags added: 5.3 amd64 eoan gcp sru-20191202 ubuntu-k8s-unit-tests ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855815 Title: flag from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP --- FAIL: TestConstantMaps (0.07s) ciphersuites_flag_test.go:106: discovered version tls.VersionTLS13 not in version map FAIL FAIL k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/util/flag 0.072s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855811] Re: container from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
** Description changed: Issue found on 5.3.0-1010 Eoan GCP - # k8s.io/kubernetes/pkg/kubelet/container - pkg/kubelet/container/sync_result_test.go:48:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult - pkg/kubelet/container/sync_result_test.go:56:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult - pkg/kubelet/container/sync_result_test.go:66:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult - # k8s.io/kubernetes/pkg/kubelet/kuberuntime - pkg/kubelet/kuberuntime/kuberuntime_manager_test.go:388:3: Errorf format %q has arg expected of wrong type []*k8s.io/kubernetes/pkg/kubelet/container.Pod - FAIL k8s.io/kubernetes/pkg/kubelet/container [build failed] + # k8s.io/kubernetes/pkg/kubelet/container + pkg/kubelet/container/sync_result_test.go:48:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult + pkg/kubelet/container/sync_result_test.go:56:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult + pkg/kubelet/container/sync_result_test.go:66:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult + []*k8s.io/kubernetes/pkg/kubelet/container.Pod + FAIL k8s.io/kubernetes/pkg/kubelet/container [build failed] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855811 Title: container from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP # k8s.io/kubernetes/pkg/kubelet/container pkg/kubelet/container/sync_result_test.go:48:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:56:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:66:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult []*k8s.io/kubernetes/pkg/kubelet/container.Pod FAIL k8s.io/kubernetes/pkg/kubelet/container [build failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855816] [NEW] naming from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
Public bug reported: Issue found on 5.3.0-1010 Eoan GCP --- FAIL: TestGetNameFromCallsite (0.00s) --- FAIL: TestGetNameFromCallsite/ignore-package (0.00s) from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" --- FAIL: TestGetNameFromCallsite/ignore-file (0.00s) from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" FAIL FAIL k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/naming0.002s ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Tags: 5.3 amd64 eoan gcp sru-20191202 ubuntu-k8s-unit-tests ** Tags added: 5.3 amd64 eoan gcp sru-20191202 ubuntu-k8s-unit-tests ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855816 Title: naming from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP --- FAIL: TestGetNameFromCallsite (0.00s) --- FAIL: TestGetNameFromCallsite/ignore-package (0.00s) from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" --- FAIL: TestGetNameFromCallsite/ignore-file (0.00s) from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" FAIL FAIL k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/naming0.002s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855814] [NEW] label from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
Public bug reported: Issue found on 5.3.0-1010 Eoan GCP FAIL k8s.io/kubernetes/plugin/pkg/admission/storage/persistentvolume/label [build failed] No other information from the test report, might need to run this manually to collect more details. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Tags: 5.3 amd64 eoan gcp sru-20191202 ubuntu-k8s-unit-tests ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855814 Title: label from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP FAIL k8s.io/kubernetes/plugin/pkg/admission/storage/persistentvolume/label [build failed] No other information from the test report, might need to run this manually to collect more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855813] [NEW] ipset from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
Public bug reported: Issue found on 5.3.0-1010 Eoan GCP FAILk8s.io/kubernetes/pkg/util/ipset [build failed] No other information from the test report, might need to run this manually to collect more details. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Tags: 5.3 amd64 eoan gcp sru-20191202 ubuntu-k8s-unit-tests ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855813 Title: ipset from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP FAILk8s.io/kubernetes/pkg/util/ipset [build failed] No other information from the test report, might need to run this manually to collect more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855811] [NEW] container from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
Public bug reported: Issue found on 5.3.0-1010 Eoan GCP # k8s.io/kubernetes/pkg/kubelet/container pkg/kubelet/container/sync_result_test.go:48:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:56:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:66:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult # k8s.io/kubernetes/pkg/kubelet/kuberuntime pkg/kubelet/kuberuntime/kuberuntime_manager_test.go:388:3: Errorf format %q has arg expected of wrong type []*k8s.io/kubernetes/pkg/kubelet/container.Pod FAIL k8s.io/kubernetes/pkg/kubelet/container [build failed] ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Tags: 5.3 amd64 eoan gcp sru-20191202 ubuntu-k8s-unit-tests ** Tags added: 5.3 amd64 eoan gcp sru-20191202 ubuntu-k8s-unit-tests ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855811 Title: container from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP # k8s.io/kubernetes/pkg/kubelet/container pkg/kubelet/container/sync_result_test.go:48:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:56:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:66:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult # k8s.io/kubernetes/pkg/kubelet/kuberuntime pkg/kubelet/kuberuntime/kuberuntime_manager_test.go:388:3: Errorf format %q has arg expected of wrong type []*k8s.io/kubernetes/pkg/kubelet/container.Pod FAIL k8s.io/kubernetes/pkg/kubelet/container [build failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855812] [NEW] kuberuntime from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
Public bug reported: Issue found on 5.3.0-1010 Eoan GCP FAILk8s.io/kubernetes/pkg/kubelet/kuberuntime [build failed] No other information from the test report, might need to run this manually to collect more details. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Tags: 5.3 amd64 eoan gcp sru-20191202 ubuntu-k8s-unit-tests ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855812 Title: kuberuntime from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP FAILk8s.io/kubernetes/pkg/kubelet/kuberuntime [build failed] No other information from the test report, might need to run this manually to collect more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797753] Re: I have lenevo ideapad 130-131KB and in that there is not support for wifi-adapter and touchpad (RTL8821CE chip and no detection of mousepad doing xinput)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797753 Title: I have lenevo ideapad 130-131KB and in that there is not support for wifi-adapter and touchpad (RTL8821CE chip and no detection of mousepad doing xinput) Status in linux package in Ubuntu: Expired Bug description: I installed a fresh ubuntu 18.04 in lenevo ideapad 130-131 and after installation there is no wifi adapter and also touchpad not working firstly id lspci and in that the output i found of chip : 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter secondly id did xinput but there was not device dected as touchpad after that i dual boot centos 7 along side ubunt in that touchpad is working but again wifi adapter not found please solve this issue for both ubuntu (wifi adapter not found and touchpad not detected) and centos (wifi adapter not found) i searched and read regarding this issue and tried all of the but didn't find any solution so at last i have hopes only on u all Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855810] [NEW] podautoscaler from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
Public bug reported: Issue found on 5.3.0-1010 Eoan GCP Test failed with: panic: test timed out after 2m0s (error message too long, please refer to the attachment) /tmp/kubernetes.git/_output/local/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:69 +0x62 FAIL k8s.io/kubernetes/pkg/controller/podautoscaler 120.039s ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Tags: 5.3 amd64 eoan gcp sru-20191202 ubuntu-k8s-unit-tests ** Attachment added: "podautoscaler.log" https://bugs.launchpad.net/bugs/1855810/+attachment/5311275/+files/podautoscaler.log ** Tags added: 5.3 amd64 eoan gcp sru-20191202 ubuntu-k8s-unit-tests ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855810 Title: podautoscaler from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP Test failed with: panic: test timed out after 2m0s (error message too long, please refer to the attachment) /tmp/kubernetes.git/_output/local/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:69 +0x62 FAIL k8s.io/kubernetes/pkg/controller/podautoscaler 120.039s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838839] Re: Install of custom kernel fails after recent dkms update
New to the Ubuntu community & issue tracker so apologies if this comment should go elsewhere. I am seeing the same behavior on Ubuntu 18.04.3 LTS (bionic) after following the procedure for compiling a new kernel at https://help.ubuntu.com/lts/installation-guide/amd64/ch08s06.html. The compile completes successfully but installation fails when running sudo dpkg -i ../linux-image...deb. After adding "set -x" to /etc/kernel/postinst.d/x-grub-legacy-ec2 and /usr/sbin/update-grub-legacy-ec2, it looks like the /usr/sbin/update- grub-legacy-ec2 script is failing in the ucf_update_kernels function. RET='20 Unsupported command "*" (full line was " * dkms: running auto installation service for kernel 4.15.18custom") received from confmodule.' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1838839 Title: Install of custom kernel fails after recent dkms update Status in dkms package in Ubuntu: Confirmed Bug description: Release: Ubuntu 16.04.6 LTS (xenial) Upgrading dkms from 2.2.0.3-2ubuntu11.6 to 2.2.0.3-2ubuntu11.7 (the "fix" for https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827697) breaks installation of custom kernels again, as it undoes the fixes done for bug https://bugs.launchpad.net/ubuntu/+source/nvidia- common/+bug/292606 . To be specific, during package install (either via dpkg or apt-get) I'm now getting the following error from /usr/sbin/update-grub-legacy- ec2 which is run from /etc/kernel/postinst.d/x-grub-legacy-ec2 (after running /etc/kernel/postinst.d/dkms): 20 Unsupported command "*" (full line was " * dkms: running auto installation service for kernel ...") received from confmodule. The only solution I've found so far is to downgrade dkms to 2.2.0.3-2ubuntu11.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1838839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855808] Re: cmd from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855808 Title: cmd from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP [preflight] running pre-flight checks [preflight] running pre-flight checks [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test690031695/manifests /tmp/kubeadm-reset-test690031695/pki] [reset] deleting files: [/tmp/kubeadm-reset-test690031695/admin.conf /tmp/kubeadm-reset-test690031695/kubelet.conf /tmp/kubeadm-reset-test690031695/bootstrap-kubelet.conf /tmp/kubeadm-reset-test690031695/controller-manager.conf /tmp/kubeadm-reset-test690031695/scheduler.conf] [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test190360418/manifests /tmp/kubeadm-reset-test190360418/pki] [reset] deleting files: [/tmp/kubeadm-reset-test190360418/admin.conf /tmp/kubeadm-reset-test190360418/kubelet.conf /tmp/kubeadm-reset-test190360418/bootstrap-kubelet.conf /tmp/kubeadm-reset-test190360418/controller-manager.conf /tmp/kubeadm-reset-test190360418/scheduler.conf] [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test519448409/manifests /tmp/kubeadm-reset-test519448409/pki] [reset] deleting files: [/tmp/kubeadm-reset-test519448409/admin.conf /tmp/kubeadm-reset-test519448409/kubelet.conf /tmp/kubeadm-reset-test519448409/bootstrap-kubelet.conf /tmp/kubeadm-reset-test519448409/controller-manager.conf /tmp/kubeadm-reset-test519448409/scheduler.conf] [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test499669220/manifests /tmp/kubeadm-reset-test499669220/pki] [reset] deleting files: [/tmp/kubeadm-reset-test499669220/admin.conf /tmp/kubeadm-reset-test499669220/kubelet.conf /tmp/kubeadm-reset-test499669220/bootstrap-kubelet.conf /tmp/kubeadm-reset-test499669220/controller-manager.conf /tmp/kubeadm-reset-test499669220/scheduler.conf] [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test469422835/manifests /tmp/kubeadm-reset-test469422835/test-path] E1207 09:05:16.966842 26490 reset.go:227] [reset] failed to remove directory: "/tmp/kubeadm-reset-test469422835/test-path" [readdirent: not a directory] [reset] deleting files: [/tmp/kubeadm-reset-test469422835/admin.conf /tmp/kubeadm-reset-test469422835/kubelet.conf /tmp/kubeadm-reset-test469422835/bootstrap-kubelet.conf /tmp/kubeadm-reset-test469422835/controller-manager.conf /tmp/kubeadm-reset-test469422835/scheduler.conf] [reset] deleting contents of config directories: [/tmp/kubeadm-reset-test838040502/manifests /tmp/kubeadm-reset-test838040502/pki] [reset] deleting files: [/tmp/kubeadm-reset-test838040502/admin.conf /tmp/kubeadm-reset-test838040502/kubelet.conf /tmp/kubeadm-reset-test838040502/bootstrap-kubelet.conf /tmp/kubeadm-reset-test838040502/controller-manager.conf /tmp/kubeadm-reset-test838040502/scheduler.conf] [dryrun] Would perform action DELETE on resource "secrets" in API group "core/v1" [dryrun] Resource name: "bootstrap-token-abcdef" [dryrun] Would perform action DELETE on resource "secrets" in API group "core/v1" [dryrun] Resource name: "bootstrap-token-abcdef" [dryrun] Would perform action DELETE on resource "secrets" in API group "core/v1" [dryrun] Resource name: "bootstrap-token-abcdef" [dryrun] Would perform action LIST on resource "secrets" in API group "core/v1" dummy API server listening on localhost:9008 Running HTTP test case (0) "token-id not defined" [dryrun] Would perform action LIST on resource "secrets" in API group "core/v1" panic: test timed out after 2m0s goroutine 41 [running]: testing.(*M).startAlarm.func1() /usr/lib/go-1.12/src/testing/testing.go:1334 +0xdf created by time.goFunc /usr/lib/go-1.12/src/time/sleep.go:169 +0x44 goroutine 1 [chan receive, 1 minutes]: testing.(*T).Run(0xc00043c400, 0x1711494, 0x11, 0x17ab5f8, 0x481e01) /usr/lib/go-1.12/src/testing/testing.go:917 +0x381 testing.runTests.func1(0xcd9d00) /usr/lib/go-1.12/src/testing/testing.go:1157 +0x78 testing.tRunner(0xcd9d00, 0xc0005f7e30) /usr/lib/go-1.12/src/testing/testing.go:865 +0xc0 testing.runTests(0xc0001ea320, 0x2781c20, 0x14, 0x14, 0x0) /usr/lib/go-1.12/src/testing/testing.go:1155 +0x2a9 testing.(*M).Run(0xc000324e00, 0x0) /usr/lib/go-1.12/src/testing/testing.go:1072 +0x162 main.main() _testmain.go:82 +0x13e
[Kernel-packages] [Bug 1855809] [NEW] vclib from ubuntu_k8s_unit_tests fail on Eoan 5.3 GCP
Public bug reported:
Issue found on 5.3.0-1010 Eoan GCP
E1207 09:14:34.779687 29118 datacenter.go:45] Failed to find the datacenter:
enoent. err: datacenter 'enoent' not found
E1207 09:14:34.783331 29118 datacenter.go:78] Unable to find VM by UUID. VM
UUID: enoent
E1207 09:14:34.785587 29118 datacenter.go:106] Failed to find VM by Path. VM
Path: enoent, err: vm 'enoent' not found
E1207 09:14:34.787217 29118 datacenter.go:153] Failed to parse vmDiskPath:
enoent
E1207 09:14:34.788754 29118 datacenter.go:165] Failed while searching for
datastore: enoent. err: datastore 'enoent' not found
E1207 09:14:34.792557 29118 datacenter.go:165] Failed while searching for
datastore: enoent. err: datastore 'enoent' not found
E1207 09:14:34.801865 29118 datacenter.go:191] Failed to get the folder
reference for enoent. err: folder 'enoent' not found
E1207 09:14:34.804569 29118 datacenter.go:203] VirtualMachine Object list is
empty
E1207 09:14:34.805548 29118 datacenter.go:213] Failed to get VM managed
objects from VM objects. vmObjList: [VirtualMachine:vm-54 @
/DC0/vm/DC0_H0_VM1], properties: [enoent], err: InvalidProperty
E1207 09:14:34.806781 29118 datacenter.go:241] Datastore Object list is empty
E1207 09:14:34.807159 29118 datacenter.go:251] Failed to get Datastore managed
objects from datastore objects. dsObjList:
[Datastore:/tmp/govcsim-DC0-LocalDS_0-314024335@folder-5 @
/DC0/datastore/LocalDS_0], properties: [enoent], err: InvalidProperty
E1207 09:14:34.968117 29118 connection.go:180] Failed to create new client.
err: EOF
2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:58028: remote
error: tls: bad certificate
E1207 09:14:35.039988 29118 connection.go:180] Failed to create new client.
err: Post https://127.0.0.1:35147/sdk: Host "127.0.0.1:35147" thumbprint does
not match "obviously wrong"
E1207 09:14:35.052610 29118 connection.go:180] Failed to create new client.
err: Post https://127.0.0.1:40591/sdk: x509: certificate signed by unknown
authority
2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:37506: remote
error: tls: bad certificate
2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:33050: remote
error: tls: bad certificate
E1207 09:14:35.081393 29118 connection.go:180] Failed to create new client.
err: EOF
E1207 09:14:35.081489 29118 connection.go:163] Failed to parse URL: . err:
parse https://should-not-matter:should-not-matter: invalid port
":should-not-matter" after host
--- FAIL: TestWithInvalidCaCertPath (0.00s)
connection_test.go:168: Expected an os.PathError, got: 'parse
https://should-not-matter:should-not-matter: invalid port ":should-not-matter"
after host' ({Op:"parse",
URL:"https://should-not-matter:should-not-matter;,
Err:(*errors.errorString)(0xc0004fcd70)})
E1207 09:14:35.081626 29118 connection.go:163] Failed to parse URL: . err:
parse https://should-not-matter:should-not-matter: invalid port
":should-not-matter" after host
--- FAIL: TestInvalidCaCert (0.00s)
connection_test.go:182: Expected invalid certificate error, got 'parse
https://should-not-matter:should-not-matter: invalid port ":should-not-matter"
after host'
FAIL
FAIL k8s.io/kubernetes/pkg/cloudprovider/providers/vsphere/vclib 0.319s
** Affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Tags: 5.3 amd64 eoan gcp sru-20191202 ubuntu-k8s-unit-tests
** Tags added: 5.3 amd64 eoan gcp ubuntu-k8s-unit-tests
** Tags added: sru-20191202
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1855809
Title:
vclib from ubuntu_k8s_unit_tests fail on Eoan 5.3 GCP
Status in ubuntu-kernel-tests:
New
Status in linux-gcp package in Ubuntu:
New
Bug description:
Issue found on 5.3.0-1010 Eoan GCP
E1207 09:14:34.779687 29118 datacenter.go:45] Failed to find the datacenter:
enoent. err: datacenter 'enoent' not found
E1207 09:14:34.783331 29118 datacenter.go:78] Unable to find VM by UUID. VM
UUID: enoent
E1207 09:14:34.785587 29118 datacenter.go:106] Failed to find VM by Path. VM
Path: enoent, err: vm 'enoent' not found
E1207 09:14:34.787217 29118 datacenter.go:153] Failed to parse vmDiskPath:
enoent
E1207 09:14:34.788754 29118 datacenter.go:165] Failed while searching for
datastore: enoent. err: datastore 'enoent' not found
E1207 09:14:34.792557 29118 datacenter.go:165] Failed while searching for
datastore: enoent. err: datastore 'enoent' not found
E1207 09:14:34.801865 29118 datacenter.go:191] Failed to get the folder
reference for enoent. err: folder 'enoent' not found
E1207 09:14:34.804569 29118 datacenter.go:203] VirtualMachine Object list is
empty
E1207 09:14:34.805548 29118 datacenter.go:213] Failed to get VM
[Kernel-packages] [Bug 1838839] Re: Install of custom kernel fails after recent dkms update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dkms (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1838839 Title: Install of custom kernel fails after recent dkms update Status in dkms package in Ubuntu: Confirmed Bug description: Release: Ubuntu 16.04.6 LTS (xenial) Upgrading dkms from 2.2.0.3-2ubuntu11.6 to 2.2.0.3-2ubuntu11.7 (the "fix" for https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827697) breaks installation of custom kernels again, as it undoes the fixes done for bug https://bugs.launchpad.net/ubuntu/+source/nvidia- common/+bug/292606 . To be specific, during package install (either via dpkg or apt-get) I'm now getting the following error from /usr/sbin/update-grub-legacy- ec2 which is run from /etc/kernel/postinst.d/x-grub-legacy-ec2 (after running /etc/kernel/postinst.d/dkms): 20 Unsupported command "*" (full line was " * dkms: running auto installation service for kernel ...") received from confmodule. The only solution I've found so far is to downgrade dkms to 2.2.0.3-2ubuntu11.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1838839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855645] Re: Touchpad not working completely.
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 Hi GShyam, This issue looks like a duplicate of bug 1854798, you can try the suggestions there, or just boot with an older kernel before the kernel update (e.g. 4.15.0-70). If you think this is not the same issue, please feel free to change the bug status. Thank you. ** This bug has been marked a duplicate of bug 1854798 Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-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/1855645 Title: Touchpad not working completely. Status in linux package in Ubuntu: Confirmed Bug description: The touchpad stopped working suddenly. At night of yesterday, it was working, but in the morning it was not worked. Before its stop working there were some packages showing there update and asking for the restart of the system. And did not restart that time. After some time I shutdown my system. But after starting the system the came in the touchpad. My system working in dual boot mode with windows 10 also. Touchpad working in the windows 10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: ghanshyam 1675 F...m pulseaudio /dev/snd/controlC1: ghanshyam 1675 F pulseaudio /dev/snd/controlC0: ghanshyam 1675 F pulseaudio CRDA: global country IN: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5350 @ 160), (N/A, 23), (N/A) (5725 - 5875 @ 80), (N/A, 23), (N/A) CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 09:57:19 2019 InstallationDate: Installed on 2019-01-28 (314 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Vostro 3558 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=c754d81b-93d5-449d-aa12-40e76d829be9 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PPH4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/01/2016:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn0PPH4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3558 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/1855645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849269] Re: The system cannot resume from S3 if user unplugs the TB16 during suspend state
** No longer affects: linux (Ubuntu Disco) -- 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/1849269 Title: The system cannot resume from S3 if user unplugs the TB16 during suspend state Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] Unplug TBT dock during S3 and then wakes up the system leads to system hangs. This not only happens on Dell TB16, but also Dell WD19TB. It's more like a BIOS or TBT firmware issue that TBT firmware doesn't re-create the PCIe tunnels. [Fix] Mika provides 4 patches to fix this issue, but only 2 are accepted and are included in linus' tree. We need especially the 4th commit to fix the issue, so we keep the 3rd and 4th commits as sauce patches. [Test] Verified on Dell Precision 5530 + WD19TB [Regression Potential] Low, those patches doesn't change the code path much. The 4th commit adds some checks to return failure state, and it should be safe for those machines which is working well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1849269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853683] Re: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
*** This bug is a duplicate of bug 1573508 *** https://bugs.launchpad.net/bugs/1573508 This bug is already fixed in updates: nvidia-graphics-drivers-384 (384.130-0ubuntu0.16.04.2) xenial; urgency=medium See bug 1573508 ** Summary changed: - nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build + nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build [error: too many arguments to function ‘get_user_pages’] ** This bug has been marked a duplicate of bug 1573508 SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1853683 Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: NVIDIA-SMI couldn't find libnvidia-ml.so library in your system. Please make sure that the NVIDIA Display Driver is properly installed and present in your system. Please also try adding directory that contains libnvidia-ml.so to your system PATH. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.130-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 DKMSKernelVersion: 4.4.0-169-generic Date: Sat Nov 23 16:02:50 2019 DuplicateSignature: dkms:nvidia-384:384.130-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-384/384.130/build/common/inc/nv-mm.h:44:9: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2017-06-02 (903 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 384.130-0ubuntu0.16.04.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1853683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855710] Re: Losing my printer
** No longer affects: xorg (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855710 Title: Losing my printer Status in linux package in Ubuntu: Incomplete Bug description: Hello, After the last update of the system lost access to the printer and could not connect to it. Thanks Ferran Lindström ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-170.199-generic 4.4.200 Uname: Linux 4.4.0-170-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Dec 9 13:14:04 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1495] InstallationDate: Installed on 2016-10-25 (1139 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC ProcEnviron: LANGUAGE=ca PATH=(custom, no user) LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-170-generic root=UUID=55d2d15a-85c8-4ae0-bd45-dc47177bc25b ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.09 dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.09:bd07/01/2011:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Dec 8 17:56:16 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816429] Re: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
Actually that still counts as Fix Released for 18.10, but incomplete for 18.04. Please answer comment #7. ** 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/1816429 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Bug description: I'm having a sound problem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erkan 2121 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 18 16:48:58 2019 InstallationDate: Installed on 2019-02-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: bytcr-rt5651 - bytcr-rt5651 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816429] Re: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
Reopened due to bionic bug 1853439 ** Changed in: linux (Ubuntu) Status: Fix Released => 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/1816429 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Bug description: I'm having a sound problem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erkan 2121 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 18 16:48:58 2019 InstallationDate: Installed on 2019-02-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: bytcr-rt5651 - bytcr-rt5651 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816429] 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 1816429 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/1816429 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Bug description: I'm having a sound problem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erkan 2121 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 18 16:48:58 2019 InstallationDate: Installed on 2019-02-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: bytcr-rt5651 - bytcr-rt5651 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853439] Re: Cherry Trail xubuntu 18.04.3 rt5651 sound problem
*** This bug is a duplicate of bug 1816429 *** https://bugs.launchpad.net/bugs/1816429 I think we closed bug 1816429 too soon so let's use that... ** This bug has been marked a duplicate of bug 1816429 [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853439 Title: Cherry Trail xubuntu 18.04.3 rt5651 sound problem Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: no sound ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Thu Nov 21 13:27:58 2019 InstallationDate: Installed on 2019-11-20 (0 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=tr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853439] Re: xubuntu 18.04.3 rt5651 sound problem
*** This bug is a duplicate of bug 1816429 *** https://bugs.launchpad.net/bugs/1816429 Thanks. It looks like pulseaudio is being limited by a recurring kernel error: Ara 09 14:05:29 unluturk kernel: Audio Port: ASoC: no backend DAIs enabled for Audio Port Ara 09 14:05:29 unluturk kernel: Audio Port: ASoC: no backend DAIs enabled for Audio Port Ara 09 14:05:29 unluturk kernel: Audio Port: ASoC: no backend DAIs enabled for Audio Port Ara 09 14:05:29 unluturk kernel: Audio Port: ASoC: no backend DAIs enabled for Audio Port Ara 09 14:05:29 unluturk kernel: Audio Port: ASoC: no backend DAIs enabled for Audio Port Ara 09 14:05:29 unluturk kernel: Audio Port: ASoC: no backend DAIs enabled for Audio Port Ara 09 14:05:29 unluturk pulseaudio[2075]: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Ara 09 14:05:29 unluturk kernel: Audio Port: ASoC: no backend DAIs enabled for Audio Port Ara 09 14:05:29 unluturk pulseaudio[2075]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-bytcr_rt5651" card_name="alsa_card.platform-bytcr_rt5651" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. ** Summary changed: - xubuntu 18.04.3 rt5651 sound problem + Cherry Trail xubuntu 18.04.3 rt5651 sound problem ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853439 Title: Cherry Trail xubuntu 18.04.3 rt5651 sound problem Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: no sound ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Thu Nov 21 13:27:58 2019 InstallationDate: Installed on 2019-11-20 (0 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=tr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854755] Re: eoan/linux-oracle: 5.3.0-1008.9 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Ready for Promote to Proposed phase-changed: Monday, 09. December 2019 13:34 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-oracle-5.3: bug 1854754 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1854755 Title: eoan/linux-oracle: 5.3.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Ready for Promote to Proposed phase-changed: Monday, 09. December 2019 13:34 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-oracle-5.3: bug 1854754 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848127 Title: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: [IMPACT] MCE test renders the system unresponsive on P9 open power hardware (Withersoon) [TEST] A test kernel is available in ppa:ubuntu-power-triage/lp1848127. Please see the [OTHER] section for test details and comment #7 for results with the PPA kernel. [FIX] IBM has identified the following patch that fixes this issue: commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee Author: Balbir Singh Date: Tue Aug 20 13:43:47 2019 +0530 powerpc/mce: Fix MCE handling for huge pages [REGRESSION POTENTIAL] The patch is applicable the powerpc architecture and limited in scope to MCE handling for huge pages. Patch does not touch any generic code. Regression if any is limited to powerpc MCE handling. [OTHER] == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v2.3-rc2-58-g59fd0743 buildroot-2019.02.2-17-g93b841d204 skiboot-v6.3-rc2 hostboot-19a436e occ-58e422d linux-5.0.9-openpower1-p3a4d5a4 petitboot-v1.10.3 machine-xml-a6f4df3 hostboot-binaries-hw043019a.940 capp-ucode-p9-dd2-v4 sbe-249671d hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs: 100 101 102 103 CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs: 104 105 106 107 CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs: 108 109 110 111 CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs: 112 113 114 115 CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs: 116 117 118 119 CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs: 120 121 122 123 CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs: 124 125 126 127 CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs: 128 129 130 131 CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs: 132 133 134 135 CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs: 136 137 138 139 CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs: 140 141 142 143 - p[0] eq[0,1,2,3,4,5] ex[0,1,3,4,5,6,8,9,10]
[Kernel-packages] [Bug 1855521] Re: [Dell Inspiron 5490] Internal microphone not detected
This machine probably has the internal dmic connected to the PCH, we need to use sof driver on this machine. Please wait for some time (maybe 1 month), we are adding sof support in the 19.10 kernel, not finished yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1357 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1854762] Re: eoan/linux: 5.3.0-25.27 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 05. December 2019 11:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1855309 bionic/linux-hwe-edge: bug 1854761 eoan/linux-aws: bug 1854746 eoan/linux-azure: bug 1854749 eoan/linux-gcp: bug 1854751 eoan/linux-kvm: bug 1854752 eoan/linux-oracle: bug 1854755 eoan/linux-raspi2: bug 1854744 eoan/linux/pc-kernel: bug 1854741 eoan/linux/pc-lowlatency-kernel: bug 1854742 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854762 Title: eoan/linux: 5.3.0-25.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 05. December 2019 11:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1855309 bionic/linux-hwe-edge: bug 1854761 eoan/linux-aws: bug 1854746 eoan/linux-azure: bug 1854749 eoan/linux-gcp: bug 1854751 eoan/linux-kvm: bug 1854752 eoan/linux-oracle: bug 1854755 eoan/linux-raspi2: bug 1854744 eoan/linux/pc-kernel: bug 1854741 eoan/linux/pc-lowlatency-kernel: bug 1854742 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855645] Re: Touchpad not working completely.
I suggest looking at the aforementioned link (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854798), and trying what has been suggested there (eg. comment 13 OR 15). If you try it, and it works PLEASE report back here or on other 1854798 bug report. (this report can be marked a duplicate of the other one; ie. same problem with same fix) The 'fix' (a reversion) has been found to work on the other s3203/TM2714-002 as noted in the other bug report I linked. Bots are not people, it's a program running on a machine that looked through your provided files & 'confirmed' at least one other user has the same issue (recorded in their logs). It adds 'heat' to your bug (you'll note the 'heat' for the other report is much higher, it'll thus get more attention). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855645 Title: Touchpad not working completely. Status in linux package in Ubuntu: Confirmed Bug description: The touchpad stopped working suddenly. At night of yesterday, it was working, but in the morning it was not worked. Before its stop working there were some packages showing there update and asking for the restart of the system. And did not restart that time. After some time I shutdown my system. But after starting the system the came in the touchpad. My system working in dual boot mode with windows 10 also. Touchpad working in the windows 10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: ghanshyam 1675 F...m pulseaudio /dev/snd/controlC1: ghanshyam 1675 F pulseaudio /dev/snd/controlC0: ghanshyam 1675 F pulseaudio CRDA: global country IN: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5350 @ 160), (N/A, 23), (N/A) (5725 - 5875 @ 80), (N/A, 23), (N/A) CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 09:57:19 2019 InstallationDate: Installed on 2019-01-28 (314 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Vostro 3558 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=c754d81b-93d5-449d-aa12-40e76d829be9 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PPH4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/01/2016:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn0PPH4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3558 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/1855645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855787] [NEW] Bionic update: upstream stable patchset 2019-12-09
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-12-09 Ported from the following upstream stable releases: v4.14.158, v4.19.88 from git://git.kernel.org/ Revert "KVM: nVMX: reset cache/shadows when switching loaded VMCS" clk: meson: gxbb: let sar_adc_clk_div set the parent clock rate ASoC: msm8916-wcd-analog: Fix RX1 selection in RDAC2 MUX ASoC: compress: fix unsigned integer overflow check reset: Fix memory leak in reset_control_array_put() ASoC: kirkwood: fix external clock probe defer clk: samsung: exynos5420: Preserve PLL configuration during suspend/resume reset: fix reset_control_ops kerneldoc comment clk: at91: avoid sleeping early clk: sunxi-ng: a80: fix the zero'ing of bits 16 and 18 idr: Fix idr_alloc_u32 on 32-bit systems x86/resctrl: Prevent NULL pointer dereference when reading mondata clk: ti: dra7-atl-clock: Remove ti_clk_add_alias call net: fec: add missed clk_disable_unprepare in remove bridge: ebtables: don't crash when using dnat target in output chains can: peak_usb: report bus recovery as well can: c_can: D_CAN: c_can_chip_config(): perform a sofware reset on open can: rx-offload: can_rx_offload_queue_tail(): fix error handling, avoid skb mem leak can: rx-offload: can_rx_offload_offload_one(): do not increase the skb_queue beyond skb_queue_len_max can: rx-offload: can_rx_offload_offload_one(): increment rx_fifo_errors on queue overflow or OOM can: rx-offload: can_rx_offload_offload_one(): use ERR_PTR() to propagate error value in case of errors can: rx-offload: can_rx_offload_irq_offload_timestamp(): continue on error can: rx-offload: can_rx_offload_irq_offload_fifo(): continue on error watchdog: meson: Fix the wrong value of left time scripts/gdb: fix debugging modules compiled with hot/cold partitioning net: bcmgenet: reapply manual settings to the PHY ceph: return -EINVAL if given fsc mount option on kernel w/o support mac80211: fix station inactive_time shortly after boot block: drbd: remove a stray unlock in __drbd_send_protocol() pwm: bcm-iproc: Prevent unloading the driver module while in use scsi: lpfc: Fix kernel Oops due to null pring pointers scsi: lpfc: Fix dif and first burst use in write commands ARM: dts: Fix up SQ201 flash access ARM: debug-imx: only define DEBUG_IMX_UART_PORT if needed UBUNTU: [Config] updateconfigs for DEBUG_IMX_UART_PORT ARM: dts: imx53-voipac-dmm-668: Fix memory node duplication parisc: Fix serio address output parisc: Fix HP SDC hpa address output arm64: mm: Prevent mismatched 52-bit VA support arm64: smp: Handle errors reported by the firmware ARM: OMAP1: fix USB configuration for device-only setups RDMA/vmw_pvrdma: Use atomic memory allocation in create AH PM / AVS: SmartReflex: NULL check before some freeing functions is not needed ARM: ks8695: fix section mismatch warning ACPI / LPSS: Ignore acpi_device_fix_up_power() return value scsi: lpfc: Enable Management features for IF_TYPE=6 crypto: user - support incremental algorithm dumps mwifiex: fix potential NULL dereference and use after free mwifiex: debugfs: correct histogram spacing, formatting rtl818x: fix potential use after free xfs: require both realtime inodes to mount ubi: Put MTD device after it is not used ubi: Do not drop UBI device reference before using microblaze: adjust the help to the real behavior microblaze: move "... is ready" messages to arch/microblaze/Makefile iwlwifi: move iwl_nvm_check_version() into dvm gpiolib: Fix return value of gpio_to_desc() stub if !GPIOLIB kvm: vmx: Set IA32_TSC_AUX for legacy mode guests VSOCK: bind to random port for VMADDR_PORT_ANY mmc: meson-gx: make sure the descriptor is stopped on errors mtd: rawnand: sunxi: Write pageprog related opcodes to WCMD_SET btrfs: only track ref_heads in delayed_ref_updates HID: intel-ish-hid: fixes incorrect error handling serial: 8250: Rate limit serial port rx interrupts during input overruns kprobes/x86/xen: blacklist non-attachable xen interrupt functions xen/pciback: Check dev_data before using it vfio-mdev/samples: Use u8 instead of char for handle functions pinctrl: xway: fix gpio-hog related boot issues net/mlx5: Continue driver initialization despite debugfs failure exofs_mount(): fix leaks on failure exits bnxt_en: Return linux standard errors in bnxt_ethtool.c bnxt_en: query force speeds before disabling autoneg mode. KVM: s390: unregister debug feature on failing arch init pinctrl: sh-pfc: sh7264: Fix PFCR3 and PFCR0 register configuration pinctrl: sh-pfc: sh7734: Fix shifted values in IPSR10 HID:
[Kernel-packages] [Bug 1854811] Re: trusty/linux-azure: 4.15.0-1065.70~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854813 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 09. December 2019 10:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1854811 Title: trusty/linux-azure: 4.15.0-1065.70~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: 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: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854813 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 09. December 2019 10:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840498] Re: WARNING: CPU: 4 PID: 0 at net/mac80211/rx.c:4568 ieee80211_rx_napi+0x2e6/0x580 [mac80211]
This was merged at Linux 5.5-rc1. Patch 1/2 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e01fddc19d215f6ad397894ec2a851d99bf154e2 Patch 2/2 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=cd486e627e67ee9ab66914d36d3127ef057cc010 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840498 Title: WARNING: CPU: 4 PID: 0 at net/mac80211/rx.c:4568 ieee80211_rx_napi+0x2e6/0x580 [mac80211] Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [ 4249.706469] [ cut here ] [ 4249.706474] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 127 (0x7f) [ 4249.706596] WARNING: CPU: 4 PID: 0 at net/mac80211/rx.c:4568 ieee80211_rx_napi+0x2e6/0x580 [mac80211] [ 4249.706597] Modules linked in: snd_seq_dummy ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs rfcomm hidp pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm cmac bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio arc4 nls_iso8859_1 mei_hdcp snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl snd_soc_skl_ipc x86_pkg_temp_thermal intel_powerclamp snd_soc_sst_ipc coretemp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi kvm_intel snd_soc_core kvm snd_compress irqbypass ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul snd_pcm crc32_pclmul ghash_clmulni_intel uvcvideo videobuf2_vmalloc videobuf2_memops ath9k_htc videobuf2_v4l2 ath9k_common videobuf2_common ath9k_hw videodev ath media snd_seq_midi mac80211 aesni_intel snd_seq_midi_event snd_rawmidi joydev cfg80211 aes_x86_64 btusb crypto_simd btrtl cryptd glue_helper btbcm snd_seq btintel intel_cstate input_leds i915 bluetooth snd_seq_device [ 4249.706657] intel_rapl_perf snd_timer ecdh_generic ecc hp_wmi drm_kms_helper snd serio_raw hid_sensor_accel_3d drm hid_sensor_magn_3d hid_sensor_gyro_3d hid_sensor_incl_3d hid_sensor_rotation spi_pxa2xx_platform hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common mei_me dw_dmac i2c_algo_bit idma64 intel_xhci_usb_role_switch soundcore dw_dmac_core 8250_dw wmi_bmof mei hid_multitouch virt_dma processor_thermal_device fb_sys_fops intel_wmi_thunderbolt industrialio intel_pch_thermal roles intel_soc_dts_iosf syscopyarea sysfillrect sysimgblt int3403_thermal int340x_thermal_zone soc_button_array intel_vbtn sparse_keymap hp_accel int3400_thermal acpi_thermal_rel hp_wireless lis3lv02d input_polldev acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid hid_generic psmouse intel_ish_ipc ahci intel_ishtp i2c_i801 sdhci_pci [ 4249.706714] libahci cqhci intel_lpss_pci sdhci i2c_hid intel_lpss wmi hid video pinctrl_sunrisepoint pinctrl_intel [ 4249.706730] CPU: 4 PID: 0 Comm: swapper/4 Tainted: G OE 5.2.0-10-generic #11-Ubuntu [ 4249.706732] Hardware name: HP HP Pavilion x360 Convertible 14-cd0xxx/8486, BIOS F.34 04/29/2019 [ 4249.706785] RIP: 0010:ieee80211_rx_napi+0x2e6/0x580 [mac80211] [ 4249.706792] Code: 42 18 0f 8d 76 cc 04 00 48 8b 42 08 48 8d 0c 49 48 8d 14 88 e9 fb fd ff ff 0f b6 f1 48 c7 c7 c8 4f 11 c1 89 f2 e8 16 de 3d ee <0f> 0b 4c 89 e7 e8 a0 98 c1 ee eb a4 80 f9 0b 0f 86 5e 01 00 00 80 [ 4249.706794] RSP: 0018:b16b01aa0dd8 EFLAGS: 00010286 [ 4249.706798] RAX: RBX: 89061a9b47a0 RCX: 0006 [ 4249.706800] RDX: 0007 RSI: 0086 RDI: 890625d17440 [ 4249.706802] RBP: b16b01aa0e68 R08: 03fb R09: 0004 [ 4249.706804] R10: R11: 0001 R12: 89060ba6ef00 [ 4249.706805] R13: R14: R15: 0292 [ 4249.706808] FS: () GS:890625d0() knlGS: [ 4249.706811] CS: 0010 DS: ES: CR0: 80050033 [ 4249.706813] CR2: 152dba73 CR3: 000316c0a001 CR4: 003606e0 [ 4249.706815] Call Trace: [ 4249.706819] [ 4249.706831] ? ath9k_rx_prepare.isra.0+0x242/0x290 [ath9k_htc] [ 4249.706841] ath9k_rx_tasklet+0x106/0x1c0 [ath9k_htc] [ 4249.706852] tasklet_action_common.isra.0+0x60/0x110 [ 4249.706858] tasklet_action+0x22/0x30 [ 4249.706866] __do_softirq+0xe1/0x2f4 [ 4249.706872] irq_exit+0xb6/0xc0 [ 4249.706878] do_IRQ+0x86/0xe0 [ 4249.706883] common_interrupt+0xf/0xf [ 4249.706885] [ 4249.706893] RIP: 0010:cpuidle_enter_state+0xc5/0x420 [ 4249.706897] Code: ff e8 0f 3c 84 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 3d 03 00 00 31 ff e8 c2 90 8a ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 89 d1 01 00 00 41 c7 44 24 10 00 00
[Kernel-packages] [Bug 1843598] Re: WARNING: CPU: 4 PID: 0 at net/mac80211/rx.c:4568 ieee80211_rx_napi+0x2e6/0x580 [mac80211]
This was merged at Linux 5.5-rc1. Patch 1/2 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e01fddc19d215f6ad397894ec2a851d99bf154e2 Patch 2/2 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=cd486e627e67ee9ab66914d36d3127ef057cc010 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1843598 Title: WARNING: CPU: 4 PID: 0 at net/mac80211/rx.c:4568 ieee80211_rx_napi+0x2e6/0x580 [mac80211] Status in linux package in Ubuntu: Confirmed Bug description: I lose internet when this error happens. Sometimes I have to disconnect the USB-WiFI peripheral and connect again. dmesg: [ 147.026240] [ cut here ] [ 147.026241] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 127 (0x7f) [ 147.026281] WARNING: CPU: 4 PID: 0 at net/mac80211/rx.c:4568 ieee80211_rx_napi+0x2e6/0x580 [mac80211] [ 147.026281] Modules linked in: rfcomm hidp pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm cmac bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc x86_pkg_temp_thermal snd_soc_sst_ipc intel_powerclamp snd_soc_sst_dsp coretemp snd_soc_acpi_intel_match snd_soc_acpi nls_iso8859_1 kvm_intel snd_soc_core snd_compress kvm ac97_bus irqbypass snd_pcm_dmaengine snd_hda_intel ath9k_htc snd_hda_codec ath9k_common snd_hda_core mei_hdcp crct10dif_pclmul snd_hwdep crc32_pclmul uvcvideo intel_rapl_msr ghash_clmulni_intel videobuf2_vmalloc snd_pcm ath9k_hw videobuf2_memops snd_seq_midi videobuf2_v4l2 ath videobuf2_common snd_seq_midi_event mac80211 aesni_intel snd_rawmidi btusb videodev aes_x86_64 btrtl crypto_simd btbcm btintel cryptd mc snd_seq glue_helper bluetooth intel_cstate i915 cfg80211 snd_seq_device snd_timer ecdh_generic ecc joydev input_leds libarc4 intel_rapl_perf serio_raw hp_wmi [ 147.026300] wmi_bmof intel_wmi_thunderbolt snd hid_sensor_magn_3d soundcore drm_kms_helper hid_sensor_incl_3d hid_sensor_rotation hid_sensor_accel_3d hid_sensor_gyro_3d hid_sensor_trigger spi_pxa2xx_platform industrialio_triggered_buffer kfifo_buf 8250_dw dw_dmac hid_sensor_iio_common dw_dmac_core industrialio mei_me drm mei processor_thermal_device hid_multitouch intel_rapl_common i2c_algo_bit fb_sys_fops cros_ec_ishtp idma64 syscopyarea intel_xhci_usb_role_switch cros_ec_core sysfillrect roles virt_dma intel_pch_thermal sysimgblt intel_soc_dts_iosf int3403_thermal int340x_thermal_zone soc_button_array intel_vbtn sparse_keymap hp_accel lis3lv02d hp_wireless input_polldev int3400_thermal acpi_thermal_rel acpi_pad mac_hid sch_fq_codel parport_pc ppdev sunrpc lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid hid_generic psmouse sdhci_pci cqhci i2c_i801 sdhci i2c_hid ahci intel_lpss_pci [ 147.026319] intel_ish_ipc libahci intel_lpss intel_ishtp wmi hid pinctrl_sunrisepoint video pinctrl_intel [ 147.026323] CPU: 4 PID: 0 Comm: swapper/4 Tainted: G OE 5.3.0-10-generic #11-Ubuntu [ 147.026324] Hardware name: HP HP Pavilion x360 Convertible 14-cd0xxx/8486, BIOS F.34 04/29/2019 [ 147.026337] RIP: 0010:ieee80211_rx_napi+0x2e6/0x580 [mac80211] [ 147.026338] Code: 42 18 0f 8d b5 cb 04 00 48 8b 42 08 48 8d 0c 49 48 8d 14 88 e9 fb fd ff ff 0f b6 f1 48 c7 c7 e0 2f d9 c0 89 f2 e8 35 14 96 de <0f> 0b 4c 89 e7 e8 b0 f0 1a df eb a4 80 f9 0b 0f 86 5e 01 00 00 80 [ 147.026339] RSP: 0018:b4f94020cdd8 EFLAGS: 00010286 [ 147.026340] RAX: RBX: 8e7e9ab907a0 RCX: 0006 [ 147.026340] RDX: 0007 RSI: 0086 RDI: 8e7ea5d17440 [ 147.026341] RBP: b4f94020ce68 R08: 03cc R09: 0004 [ 147.026342] R10: R11: 0001 R12: 8e7cea8da300 [ 147.026342] R13: R14: R15: 0292 [ 147.026343] FS: () GS:8e7ea5d0() knlGS: [ 147.026344] CS: 0010 DS: ES: CR0: 80050033 [ 147.026344] CR2: 0f61bc614000 CR3: 0001e820a003 CR4: 003606e0 [ 147.026345] Call Trace: [ 147.026346] [ 147.026350] ? ath9k_rx_prepare.isra.0+0x242/0x290 [ath9k_htc] [ 147.026352] ath9k_rx_tasklet+0x106/0x1c0 [ath9k_htc] [ 147.026355] tasklet_action_common.isra.0+0x60/0x110 [ 147.026356] tasklet_action+0x22/0x30 [ 147.026358] __do_softirq+0xe1/0x2d6 [ 147.026359] irq_exit+0xae/0xb0 [ 147.026360] do_IRQ+0x86/0xe0 [ 147.026362] common_interrupt+0xf/0xf [ 147.026363] [ 147.026365] RIP: 0010:cpuidle_enter_state+0xc5/0x420 [ 147.026366] Code: ff e8 8f 91 83 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f
[Kernel-packages] [Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
Please note that I went ahead and reinstalled on another drive and completely updated, so there is a system ready to go with this issue--I just have to boot into it. It's a slow USB external drive, so, gross, but it works. Also, I'm a former c developer with some kernel dev experience in the past. I'm a bit (lot) rusty, but just so you're aware, I can probably deliver some value in troubleshooting this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854896] Re: Synaptics TM3336-004 Touchpad Stopped working after update to the latest kernel 4.15.0-72 generic
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 Same issue with - Touchpad: Synaptics s3203 - kernel : 4.15.0-72-generic - Distro : Kubuntu 18.04 Back to kernel 4.15.0-70 works just fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854896 Title: Synaptics TM3336-004 Touchpad Stopped working after update to the latest kernel 4.15.0-72 generic Status in linux package in Ubuntu: Incomplete Bug description: Please see to it, my touchpad all of a sudden stopped working after reboot. it happened after updating to the latest kernel 4.15.0-72, i am using linux mint 19.2. Pointer version: Synaptics TM3336-004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311222/+files/WifiSyslog.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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311210/+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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311215/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311213/+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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311214/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311218/+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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311220/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311217/+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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311219/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311216/+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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311212/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311209/+files/AudioDevicesInUse.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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311221/+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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311211/+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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
apport information ** Tags added: apport-collected eoan ** Description changed: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-12-09 (0 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 + 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 nouveaudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-24-generic N/A + linux-backports-modules-5.3.0-24-generic N/A + linux-firmware1.183.2 + Tags: eoan + Uname: Linux 5.3.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/31/2015 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F9 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: Z97-HD3 + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: Z97-HD3 + dmi.product.sku: To be filled by O.E.M. + dmi.product.version: To be filled by O.E.M. + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311208/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user)
[Kernel-packages] [Bug 1855729] Re: ARM CPU erratum Neoverse-N1 #1542419
** Changed in: linux-aws (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1855729 Title: ARM CPU erratum Neoverse-N1 #1542419 Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Bionic: In Progress Bug description: linux-aws-bionic needs the mainline patch set for ARM CPU erratum Neoverse-N1 #1542419 and its prerequisites: arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419 arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1 #1542419 arm64: cpufeature: Trap CTR_EL0 access only where it is necessary arm64: Add part number for Neoverse N1 arm64: Add support for new control bits CTR_EL0.DIC and CTR_EL0.IDC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1855729/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854071] Re: Backport In-Memory Collection Counters (IMC) trace-mode patches
IBM, Please test the Disco kernel available in https://launchpad.net/~ubuntu- power-triage/+archive/ubuntu/lp1854071/ Also, please share following details 1. What impact does it have without these patches? 2. The testcase used, and how to run the tests. Thanks ** Changed in: linux (Ubuntu Disco) Status: In Progress => Incomplete ** 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/1854071 Title: Backport In-Memory Collection Counters (IMC) trace-mode patches Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Incomplete Bug description: == Comment: #0 - Murilo Opsfelder Araujo - 2019-11-08 06:30:06 == ---Problem Description--- The following patches may be wanted in >= Bionic kernels: 1. powerpc/include: Add data structures and macros for IMC trace mode https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=d1720adff3783a2ba7c128e304a385d18962835b 2. powerpc/perf: Rearrange setting of ldbar for thread-imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=dd50cf7cbc7bdd86483b797ac3d27b37d5aeeaa4 3. powerpc/perf: Add privileged access check for thread_imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=216c3087a346db8d7c8a064d2b8f0f49e4694934 4. powerpc/perf: Trace imc events detection and cpuhotplug https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=72c69dcddce103338de558c5c6e9ef9e4f607ce1 5. powerpc/perf: Trace imc PMU functions https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=012ae244845f19d5f6ca2a90426851bc5044a0dc Patch #3 addresses a security issue. ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. == Comment: #12 - Murilo Opsfelder Araujo - 2019-11-22 07:41:20 == Please mirror to Canonical to backporting this single patch for >= Bionic kernels (or for which kernels they find appropriate): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=216c3087a346db8d7c8a064d2b8f0f49e4694934 commit 216c3087a346db8d7c8a064d2b8f0f49e4694934 Author: Madhavan Srinivasan Date: Tue Apr 16 15:18:29 2019 +0530 powerpc/perf: Add privileged access check for thread_imc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1854071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854895] Re: touchpad stopped working after the update
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 I have this same issue on Ubuntu 16.04. Booting into an older kernel fixes the issue for me. This is on a Dell XPS 13. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854895 Title: touchpad stopped working after the update Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: After the automatic software update the touchpad stopped working in my laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anil 1722 F pulseaudio /dev/snd/controlC0: anil 1722 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 3 10:44:48 2019 InstallationDate: Installed on 2018-12-21 (346 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 3542 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=a85be26b-aca7-48bd-b03b-6a99e1587772 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 09V1VC dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn09V1VC:rvrA14:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1854895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855409] 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 1855409 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 ** Changed in: linux (Ubuntu Eoan) 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/1855409 Title: qede driver causes 100% CPU load Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: Confirmed Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: This bug is similar to #1832082 (bnx2x driver causes 100% CPU load) but applies for qede driver instead of bnx2x. The symptoms are the same: With chrony installed, and configured with "hwtimestamp *", I observe 100% CPU load on 2 CPU cores. Running perf report shows that kernel is busy executing qede_ptp_task function in qede driver. A workaround is to disable "hwtimestamp *" in chrony configuration. --- $ modinfo qede filename: /lib/modules/4.15.0-72-generic/kernel/drivers/net/ethernet/qlogic/qede/qede.ko version:8.10.10.21 license:GPL description:QLogic FastLinQ 4 Ethernet Driver srcversion: D5EC89D815FC81B973EE9F0 alias: pci:v1077d8090sv*sd*bc*sc*i* alias: pci:v1077d8070sv*sd*bc*sc*i* alias: pci:v1077d1664sv*sd*bc*sc*i* alias: pci:v1077d1656sv*sd*bc*sc*i* alias: pci:v1077d1654sv*sd*bc*sc*i* alias: pci:v1077d1644sv*sd*bc*sc*i* alias: pci:v1077d1636sv*sd*bc*sc*i* alias: pci:v1077d1666sv*sd*bc*sc*i* alias: pci:v1077d1634sv*sd*bc*sc*i* depends:ptp,qed retpoline: Y intree: Y name: qede vermagic: 4.15.0-72-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: debug: Default debug msglevel (uint) $ uname -a Linux dcn1-clm-inf-1 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ lspci | grep -i ether 19:00.0 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller (rev 02) 19:00.1 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller (rev 02) 19:00.2 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller (rev 02) 19:00.3 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller (rev 02) # perf report snippet: Children Self Command Shared Object - 44.76% 0.00% kworker/16:5 [kernel.kallsyms] ret_from_fork - kthread - 44.74% worker_thread - 44.57% process_one_work - 42.67% qede_ptp_task - 38.86% qed_ptp_hw_read_tx_ts qed_rd - 3.03% queue_work_on - 2.06% __queue_work - 0.68% get_work_pool - 0.61% radix_tree_lookup __radix_tree_lookup 0.50% set_work_pool_and_clear_pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855059] Re: [Regression] 4.15.0-73.82 Can not boot ThunderX
This is caused by commit 07d6360bfefa "arm64: Do not mask out PTE_RDONLY in pte_same()" (https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/commit/?id=07d6360bfefa4a01ca6b7014f9de2e88da9edba0) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855059 Title: [Regression] 4.15.0-73.82 Can not boot ThunderX Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Bug description: On ThunderX 1socket system. The kernel output log https://pastebin.ubuntu.com/p/35DGgPz5N4/ On ThunderX 2socket system, The kernel output log https://pastebin.ubuntu.com/p/T3fVzwxhmt/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855409] Re: qede driver causes 100% CPU load
Thanks for the report @phausman! I've checked mainline and there's a
commit that matches your report, we should try this one: 9adebac37e7d
("qede: Handle infinite driver spinning for Tx timestamp.") [0].
This is present in Eoan and Focal, but not in Bionic/Disco. After we
confirm this is the fix we can proceed with the SRU - in case this patch
doesn't help to alleviate the problem, then Eoan/Focal will be targeted
too and we'll need to think in a proper solution.
Notice Xenial GA kernel (v4.4) does not have PTP support in qede driver,
so this issue doesn't apply to Xenial (and once it's fixed in Bionic
it'll reach organically Xenial-HWE kernel).
I'll work in building a 4.15 kernel for Bionic with the aforementioned fix, in
order you can test.
Cheers,
Guilherme
[0] http://git.kernel.org/linus/9adebac37e7d
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1855409
Title:
qede driver causes 100% CPU load
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
Invalid
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
New
Status in linux source package in Focal:
New
Bug description:
This bug is similar to #1832082 (bnx2x driver causes 100% CPU load)
but applies for qede driver instead of bnx2x. The symptoms are the
same:
With chrony installed, and configured with "hwtimestamp *", I observe
100% CPU load on 2 CPU cores.
Running perf report shows that kernel is busy executing qede_ptp_task
function in qede driver.
A workaround is to disable "hwtimestamp *" in chrony configuration.
---
$ modinfo qede
filename:
/lib/modules/4.15.0-72-generic/kernel/drivers/net/ethernet/qlogic/qede/qede.ko
version:8.10.10.21
license:GPL
description:QLogic FastLinQ 4 Ethernet Driver
srcversion: D5EC89D815FC81B973EE9F0
alias: pci:v1077d8090sv*sd*bc*sc*i*
alias: pci:v1077d8070sv*sd*bc*sc*i*
alias: pci:v1077d1664sv*sd*bc*sc*i*
alias: pci:v1077d1656sv*sd*bc*sc*i*
alias: pci:v1077d1654sv*sd*bc*sc*i*
alias: pci:v1077d1644sv*sd*bc*sc*i*
alias: pci:v1077d1636sv*sd*bc*sc*i*
alias: pci:v1077d1666sv*sd*bc*sc*i*
alias: pci:v1077d1634sv*sd*bc*sc*i*
depends:ptp,qed
retpoline: Y
intree: Y
name: qede
vermagic: 4.15.0-72-generic SMP mod_unload
signat: PKCS#7
signer:
sig_key:
sig_hashalgo: md4
parm: debug: Default debug msglevel (uint)
$ uname -a
Linux dcn1-clm-inf-1 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
$ lspci | grep -i ether
19:00.0 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series
10/25/40/50GbE Controller (rev 02)
19:00.1 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series
10/25/40/50GbE Controller (rev 02)
19:00.2 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series
10/25/40/50GbE Controller (rev 02)
19:00.3 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series
10/25/40/50GbE Controller (rev 02)
# perf report snippet:
Children Self Command Shared Object
- 44.76% 0.00% kworker/16:5 [kernel.kallsyms]
ret_from_fork
- kthread
- 44.74% worker_thread
- 44.57% process_one_work
- 42.67% qede_ptp_task
- 38.86% qed_ptp_hw_read_tx_ts
qed_rd
- 3.03% queue_work_on
- 2.06% __queue_work
- 0.68% get_work_pool
- 0.61% radix_tree_lookup
__radix_tree_lookup
0.50% set_work_pool_and_clear_pending
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855409/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855409] Re: qede driver causes 100% CPU load
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: linux (Ubuntu Focal) Status: Incomplete => New ** Changed in: linux (Ubuntu Disco) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855409 Title: qede driver causes 100% CPU load Status in linux package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: Confirmed Status in linux source package in Eoan: New Status in linux source package in Focal: New Bug description: This bug is similar to #1832082 (bnx2x driver causes 100% CPU load) but applies for qede driver instead of bnx2x. The symptoms are the same: With chrony installed, and configured with "hwtimestamp *", I observe 100% CPU load on 2 CPU cores. Running perf report shows that kernel is busy executing qede_ptp_task function in qede driver. A workaround is to disable "hwtimestamp *" in chrony configuration. --- $ modinfo qede filename: /lib/modules/4.15.0-72-generic/kernel/drivers/net/ethernet/qlogic/qede/qede.ko version:8.10.10.21 license:GPL description:QLogic FastLinQ 4 Ethernet Driver srcversion: D5EC89D815FC81B973EE9F0 alias: pci:v1077d8090sv*sd*bc*sc*i* alias: pci:v1077d8070sv*sd*bc*sc*i* alias: pci:v1077d1664sv*sd*bc*sc*i* alias: pci:v1077d1656sv*sd*bc*sc*i* alias: pci:v1077d1654sv*sd*bc*sc*i* alias: pci:v1077d1644sv*sd*bc*sc*i* alias: pci:v1077d1636sv*sd*bc*sc*i* alias: pci:v1077d1666sv*sd*bc*sc*i* alias: pci:v1077d1634sv*sd*bc*sc*i* depends:ptp,qed retpoline: Y intree: Y name: qede vermagic: 4.15.0-72-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: debug: Default debug msglevel (uint) $ uname -a Linux dcn1-clm-inf-1 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ lspci | grep -i ether 19:00.0 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller (rev 02) 19:00.1 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller (rev 02) 19:00.2 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller (rev 02) 19:00.3 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller (rev 02) # perf report snippet: Children Self Command Shared Object - 44.76% 0.00% kworker/16:5 [kernel.kallsyms] ret_from_fork - kthread - 44.74% worker_thread - 44.57% process_one_work - 42.67% qede_ptp_task - 38.86% qed_ptp_hw_read_tx_ts qed_rd - 3.03% queue_work_on - 2.06% __queue_work - 0.68% get_work_pool - 0.61% radix_tree_lookup __radix_tree_lookup 0.50% set_work_pool_and_clear_pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853197] Re: Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection
Tested 4.15 bionic with original use case. Memory leak is resolved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853197 Title: Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [SRU Justification] == Impact == An upstream change in v4.11 made xfrm loose memory (8 pages per ipsec connection). This was fixed in v5.4 by: commit 86c6739eda7d "xfrm: Fix memleak on xfrm state destroy" == Fix == Pick the upstream fix into all affected series. == Testcase == see below == Risk of Regression == Low, the change adds a single memory release case in one driver. The effect can be verified. --- Ubuntu linux distro, 4.15.0-62 kernel, server platform. This OS is used as an IPSec VPN gateway. It serves up to several hundred concurrent connections In an attempt to upgrade from the 4.4 kernel to 4.15, the team noticed that VPN gateway VMs were running out of physical memory after 12-48 hours, depending on load. Attachments from a server machine in this state in attached leakinfo.txt output of free -t output of /proc/meminfo in out of memory condition output of /slabtop -o -sc /sys/kernel/debug/page_owner sorted and aggregated after server ran for 12 hrs and ran out of memory Patches for 4.15 and 5.4 Highlight from page_owner, we can see the leak is a buffer associated with the ipsec impelementation. Each connection leaks 32k of memory via alloc_page with order=3 100960 times: Page allocated via order 3, mask 0x1085220(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP) get_page_from_freelist+0xd64/0x1250 __alloc_pages_nodemask+0x11c/0x2e0 alloc_pages_current+0x6a/0xe0 skb_page_frag_refill+0x71/0x100 esp_output_head+0x265/0x3e0 [esp4] esp_output+0xbc/0x180 [esp4] xfrm_output_resume+0x179/0x530 xfrm_output+0x8e/0x230 xfrm4_output_finish+0x2b/0x30 __xfrm4_output+0x3a/0x50 xfrm4_output+0x43/0xc0 ip_forward_finish+0x51/0x80 ip_forward+0x38a/0x480 ip_rcv_finish+0x122/0x410 ip_rcv+0x292/0x360 __netif_receive_skb_core+0x815/0xbd0 Patch to fix this issue in 4.15 (tested and verified on same server exhibiting above leak): diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c index 728272f..7842f83 100644 --- a/net/xfrm/xfrm_state.c +++ b/net/xfrm/xfrm_state.c @@ -451,6 +451,10 @@ static void xfrm_state_gc_destroy(struct xfrm_state *x) } xfrm_dev_state_free(x); security_xfrm_state_free(x); + + if(x->xfrag.page) + put_page(x->xfrag.page); + kfree(x); } Patch for master branch (5.4 I believe) from Paul Wouters (p...@nohats.ca) diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c index c6f3c4a1bd99..f3423562d933 100644 --- a/net/xfrm/xfrm_state.c +++ b/net/xfrm/xfrm_state.c @@ -495,6 +495,8 @@ static void ___xfrm_state_destroy(struct xfrm_state *x) x->type->destructor(x); xfrm_put_type(x->type); } + if (x->xfrag.page) + put_page(x->xfrag.page); xfrm_dev_state_free(x); security_xfrm_state_free(x); xfrm_state_free(x); Severity: Critical - we are unable to use any kernel later than 4.11, and are sticking with 4.4 in production. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854071] Re: Backport In-Memory Collection Counters (IMC) trace-mode patches
** Changed in: linux (Ubuntu Disco) 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/1854071 Title: Backport In-Memory Collection Counters (IMC) trace-mode patches Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Disco: In Progress Bug description: == Comment: #0 - Murilo Opsfelder Araujo - 2019-11-08 06:30:06 == ---Problem Description--- The following patches may be wanted in >= Bionic kernels: 1. powerpc/include: Add data structures and macros for IMC trace mode https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=d1720adff3783a2ba7c128e304a385d18962835b 2. powerpc/perf: Rearrange setting of ldbar for thread-imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=dd50cf7cbc7bdd86483b797ac3d27b37d5aeeaa4 3. powerpc/perf: Add privileged access check for thread_imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=216c3087a346db8d7c8a064d2b8f0f49e4694934 4. powerpc/perf: Trace imc events detection and cpuhotplug https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=72c69dcddce103338de558c5c6e9ef9e4f607ce1 5. powerpc/perf: Trace imc PMU functions https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=012ae244845f19d5f6ca2a90426851bc5044a0dc Patch #3 addresses a security issue. ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. == Comment: #12 - Murilo Opsfelder Araujo - 2019-11-22 07:41:20 == Please mirror to Canonical to backporting this single patch for >= Bionic kernels (or for which kernels they find appropriate): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=216c3087a346db8d7c8a064d2b8f0f49e4694934 commit 216c3087a346db8d7c8a064d2b8f0f49e4694934 Author: Madhavan Srinivasan Date: Tue Apr 16 15:18:29 2019 +0530 powerpc/perf: Add privileged access check for thread_imc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1854071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Hi guys, I also suffer from this problem on my X1 6th gen on Ubuntu as well as Fedora. Looks like there was a change made in Kernel 5.5 addressing the issue (see the last sentence in the commit message, "With this change I can read out the touchpad data correctly on my Lenovo X1 Carbon 6th Gen laptop"): https://github.com/torvalds/linux/commit/a284e11c371e446371675668d8c8120a27227339#diff-02afb07ddbb5e9cae9b7709130f6ec26 Generally speaking, there are a lot of changes in the rmi4 driver since April 2019 or Kernel 5.1 (see https://github.com/torvalds/linux/commits/master/drivers/input/rmi4). Unfortunately I'm still having this problem on Kernel 5.3 so I was hoping 5.4 would improve the situation. I guess we'll have to try 5.5 then! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash
[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
The following link contains a test kernel that can be used to confirm the fix for this issue: https://kernel.ubuntu.com/~kmously/kernel-kmously-2019795-5QnR/ This kernel is the 4.15.0-72-generic kernel plus one change: Revert 'Input: synaptics-rmi4 - avoid processing unknown IRQs' For anyone testing this kernel, a minimum of 2 files need to be installed: linux-image-unsigned-4.15.0-72-generic_4.15.0-72.81~k1_amd64.deb linux-modules-4.15.0-72-generic_4.15.0-72.81~k1_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263):
[Kernel-packages] [Bug 1854071] Re: Backport In-Memory Collection Counters (IMC) trace-mode patches
Since this is not a critical bug fix or regression this might not be a candidate for LTS Bionic kernel. ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Manoj Iyer (manjo) ** Changed in: linux (Ubuntu Disco) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854071 Title: Backport In-Memory Collection Counters (IMC) trace-mode patches Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Disco: New Bug description: == Comment: #0 - Murilo Opsfelder Araujo - 2019-11-08 06:30:06 == ---Problem Description--- The following patches may be wanted in >= Bionic kernels: 1. powerpc/include: Add data structures and macros for IMC trace mode https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=d1720adff3783a2ba7c128e304a385d18962835b 2. powerpc/perf: Rearrange setting of ldbar for thread-imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=dd50cf7cbc7bdd86483b797ac3d27b37d5aeeaa4 3. powerpc/perf: Add privileged access check for thread_imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=216c3087a346db8d7c8a064d2b8f0f49e4694934 4. powerpc/perf: Trace imc events detection and cpuhotplug https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=72c69dcddce103338de558c5c6e9ef9e4f607ce1 5. powerpc/perf: Trace imc PMU functions https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=012ae244845f19d5f6ca2a90426851bc5044a0dc Patch #3 addresses a security issue. ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. == Comment: #12 - Murilo Opsfelder Araujo - 2019-11-22 07:41:20 == Please mirror to Canonical to backporting this single patch for >= Bionic kernels (or for which kernels they find appropriate): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=216c3087a346db8d7c8a064d2b8f0f49e4694934 commit 216c3087a346db8d7c8a064d2b8f0f49e4694934 Author: Madhavan Srinivasan Date: Tue Apr 16 15:18:29 2019 +0530 powerpc/perf: Add privileged access check for thread_imc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1854071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
** Package changed: 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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] 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 1855637 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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Incomplete Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] [NEW] Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
You have been subscribed to a public bug: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 https://bugs.launchpad.net/bugs/1855637 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854071] Re: Backport In-Memory Collection Counters (IMC) trace-mode patches
** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Manoj Iyer (manjo) ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854071 Title: Backport In-Memory Collection Counters (IMC) trace-mode patches Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Murilo Opsfelder Araujo - 2019-11-08 06:30:06 == ---Problem Description--- The following patches may be wanted in >= Bionic kernels: 1. powerpc/include: Add data structures and macros for IMC trace mode https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=d1720adff3783a2ba7c128e304a385d18962835b 2. powerpc/perf: Rearrange setting of ldbar for thread-imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=dd50cf7cbc7bdd86483b797ac3d27b37d5aeeaa4 3. powerpc/perf: Add privileged access check for thread_imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=216c3087a346db8d7c8a064d2b8f0f49e4694934 4. powerpc/perf: Trace imc events detection and cpuhotplug https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=72c69dcddce103338de558c5c6e9ef9e4f607ce1 5. powerpc/perf: Trace imc PMU functions https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=012ae244845f19d5f6ca2a90426851bc5044a0dc Patch #3 addresses a security issue. ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. == Comment: #12 - Murilo Opsfelder Araujo - 2019-11-22 07:41:20 == Please mirror to Canonical to backporting this single patch for >= Bionic kernels (or for which kernels they find appropriate): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=216c3087a346db8d7c8a064d2b8f0f49e4694934 commit 216c3087a346db8d7c8a064d2b8f0f49e4694934 Author: Madhavan Srinivasan Date: Tue Apr 16 15:18:29 2019 +0530 powerpc/perf: Add privileged access check for thread_imc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1854071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled
Same problem on my Intel NUC8i7BEH system running Ubuntu 19.10. Adding the quirk solved the problem for me as well. Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584557 Title: Seagate external drive causes SCSI bus resets when UAS enabled Status in linux package in Ubuntu: Confirmed Bug description: Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes continuous SCSI bus resets by default. As a workaround, disabling UAS causes the device to work fine. To disable UAS, I created a file in /etc/modprobe.d with the following contents: options usb-storage quirks=0bc2:02322:u ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CrashDB: ubuntu Date: Sun May 22 22:02:26 2016 InstallationDate: Installed on 2012-10-07 (1323 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2016-04-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813423] Re: System freezing or flickering with i915 error [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A
*** This bug is a duplicate of bug 1806242 *** https://bugs.launchpad.net/bugs/1806242 I am running with : options i915 enable_psr=0 in my /etc/modprobe.d/i915.conf ( + options i915 enable_guc=2 ). but still getting the error messages in dmesg: $ dmesg | tail [ 4461.136192] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=81211 end=81212) time 3659 us, min 1073, max 1079, scanline start 990, end 112 [ 4462.253219] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=81278 end=81279) time 3613 us, min 1073, max 1079, scanline start 1008, end 126 [ 4462.350517] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=81284 end=81285) time 3645 us, min 1073, max 1079, scanline start 836, end 1082 [ 4462.588911] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=81293 end=81294) time 3695 us, min 1073, max 1079, scanline start 833, end 1082 [ 4462.712018] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe C (start=81608 end=81609) time 3635 us, min 1073, max 1079, scanline start 876, end 4 [ 4464.044487] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe C (start=81688 end=81689) time 3672 us, min 1073, max 1079, scanline start 1055, end 185 [ 4465.185017] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=81454 end=81455) time 3546 us, min 1073, max 1079, scanline start 922, end 36 [ 4465.368990] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=81465 end=81466) time 3642 us, min 1073, max 1079, scanline start 949, end 69 [ 4467.289516] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=81575 end=81576) time 3673 us, min 1073, max 1079, scanline start 871, end 1119 [ 4467.636122] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=81601 end=81602) time 3663 us, min 1073, max 1079, scanline start 979, end 101 ✔ I am waiting for the freeze to come sooner or later.. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813423 Title: System freezing or flickering with i915 error [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: My system keeps freezing on a brand new install of Kubuntu 18.10, always with the kern.log error "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235) time 486 us, min 763, max 767, scanline start 760, end 783" I think it's probably a duplicate of these bugs which were closed unresolved: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was on an older version of Ubuntu) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because it was a duplicate of the first bug) It happens far more frequently if I have desktop effects turned on, and far less frequently when using a live USB key (at always happens eventually though. Usually once every few hours.) Please advise how I can help triage / test. My system is a new install now, so I'm perfectly willing to modify / reinstall to help testing (I've reinstalled 5 times to test things, but never managed to find a solution) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sat Jan 26 14:19:52 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227a] InstallationDate: Installed on 2019-01-18 (8 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1855729] Re: ARM CPU erratum Neoverse-N1 #1542419
** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1855729 Title: ARM CPU erratum Neoverse-N1 #1542419 Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Bionic: New Bug description: linux-aws-bionic needs the mainline patch set for ARM CPU erratum Neoverse-N1 #1542419 and its prerequisites: arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419 arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1 #1542419 arm64: cpufeature: Trap CTR_EL0 access only where it is necessary arm64: Add part number for Neoverse N1 arm64: Add support for new control bits CTR_EL0.DIC and CTR_EL0.IDC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1855729/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855729] [NEW] ARM CPU erratum Neoverse-N1 #1542419
Public bug reported: linux-aws-bionic needs the mainline patch set for ARM CPU erratum Neoverse-N1 #1542419 and its prerequisites: arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419 arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1 #1542419 arm64: cpufeature: Trap CTR_EL0 access only where it is necessary arm64: Add part number for Neoverse N1 arm64: Add support for new control bits CTR_EL0.DIC and CTR_EL0.IDC ** Affects: linux-aws (Ubuntu) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1855729 Title: ARM CPU erratum Neoverse-N1 #1542419 Status in linux-aws package in Ubuntu: In Progress Bug description: linux-aws-bionic needs the mainline patch set for ARM CPU erratum Neoverse-N1 #1542419 and its prerequisites: arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419 arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1 #1542419 arm64: cpufeature: Trap CTR_EL0 access only where it is necessary arm64: Add part number for Neoverse N1 arm64: Add support for new control bits CTR_EL0.DIC and CTR_EL0.IDC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1855729/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806242] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1806242/+attachment/5311144/+files/Xrandr.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/1806242 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: I have this error and arbitrary freezes on the system My System: Hardware: Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 Gigabit + Intel Device a370 Software: OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, Screen Resolution: 1920x1980 dmesg output: Dec 2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, min 894, max 899, scanline start 845, end 903 Dec 2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) Dec 2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized for Method [BRT6] Dec 2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method [BRT6]: (2 arguments defined for method invocation) Dec 2 16:08:50 G5 kernel: [ 2534.448073] Arg0: a83faa08 Integer 0001 Dec 2 16:08:50 G5 kernel: [ 2534.448076] Arg1: 35246c42 Integer Dec 2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution failed \EV5, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution failed \SMEE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution failed \SMIE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution failed \NEVT, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:20:32 G5 kernel: [ 3237.026638] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=88190 end=88191) time 1687 us, min 894, max 899, scanline start 864, end 14 Dec 2 16:22:20 G5 kernel: [ 3344.842212] wlp0s20f3: AP 90:ef:68:2c:31:9b changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: instantcrush 1622 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-28 (4 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G5 5587 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=0017db25-edad-4311-bca6-171f2624432e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0M2MWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd11/01/2018:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn0M2MWX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1806242] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1806242/+attachment/5311145/+files/xdpyinfo.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/1806242 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: I have this error and arbitrary freezes on the system My System: Hardware: Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 Gigabit + Intel Device a370 Software: OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, Screen Resolution: 1920x1980 dmesg output: Dec 2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, min 894, max 899, scanline start 845, end 903 Dec 2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) Dec 2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized for Method [BRT6] Dec 2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method [BRT6]: (2 arguments defined for method invocation) Dec 2 16:08:50 G5 kernel: [ 2534.448073] Arg0: a83faa08 Integer 0001 Dec 2 16:08:50 G5 kernel: [ 2534.448076] Arg1: 35246c42 Integer Dec 2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution failed \EV5, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution failed \SMEE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution failed \SMIE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution failed \NEVT, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:20:32 G5 kernel: [ 3237.026638] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=88190 end=88191) time 1687 us, min 894, max 899, scanline start 864, end 14 Dec 2 16:22:20 G5 kernel: [ 3344.842212] wlp0s20f3: AP 90:ef:68:2c:31:9b changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: instantcrush 1622 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-28 (4 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G5 5587 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=0017db25-edad-4311-bca6-171f2624432e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0M2MWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd11/01/2018:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn0M2MWX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1806242] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1806242/+attachment/5311138/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806242 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: I have this error and arbitrary freezes on the system My System: Hardware: Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 Gigabit + Intel Device a370 Software: OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, Screen Resolution: 1920x1980 dmesg output: Dec 2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, min 894, max 899, scanline start 845, end 903 Dec 2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) Dec 2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized for Method [BRT6] Dec 2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method [BRT6]: (2 arguments defined for method invocation) Dec 2 16:08:50 G5 kernel: [ 2534.448073] Arg0: a83faa08 Integer 0001 Dec 2 16:08:50 G5 kernel: [ 2534.448076] Arg1: 35246c42 Integer Dec 2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution failed \EV5, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution failed \SMEE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution failed \SMIE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution failed \NEVT, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:20:32 G5 kernel: [ 3237.026638] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=88190 end=88191) time 1687 us, min 894, max 899, scanline start 864, end 14 Dec 2 16:22:20 G5 kernel: [ 3344.842212] wlp0s20f3: AP 90:ef:68:2c:31:9b changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: instantcrush 1622 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-28 (4 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G5 5587 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=0017db25-edad-4311-bca6-171f2624432e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0M2MWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd11/01/2018:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn0M2MWX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1806242] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1806242/+attachment/5311137/+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/1806242 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: I have this error and arbitrary freezes on the system My System: Hardware: Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 Gigabit + Intel Device a370 Software: OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, Screen Resolution: 1920x1980 dmesg output: Dec 2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, min 894, max 899, scanline start 845, end 903 Dec 2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) Dec 2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized for Method [BRT6] Dec 2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method [BRT6]: (2 arguments defined for method invocation) Dec 2 16:08:50 G5 kernel: [ 2534.448073] Arg0: a83faa08 Integer 0001 Dec 2 16:08:50 G5 kernel: [ 2534.448076] Arg1: 35246c42 Integer Dec 2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution failed \EV5, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution failed \SMEE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution failed \SMIE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution failed \NEVT, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:20:32 G5 kernel: [ 3237.026638] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=88190 end=88191) time 1687 us, min 894, max 899, scanline start 864, end 14 Dec 2 16:22:20 G5 kernel: [ 3344.842212] wlp0s20f3: AP 90:ef:68:2c:31:9b changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: instantcrush 1622 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-28 (4 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G5 5587 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=0017db25-edad-4311-bca6-171f2624432e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0M2MWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd11/01/2018:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn0M2MWX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1806242] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1806242/+attachment/5311130/+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/1806242 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: I have this error and arbitrary freezes on the system My System: Hardware: Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 Gigabit + Intel Device a370 Software: OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, Screen Resolution: 1920x1980 dmesg output: Dec 2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, min 894, max 899, scanline start 845, end 903 Dec 2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) Dec 2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized for Method [BRT6] Dec 2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method [BRT6]: (2 arguments defined for method invocation) Dec 2 16:08:50 G5 kernel: [ 2534.448073] Arg0: a83faa08 Integer 0001 Dec 2 16:08:50 G5 kernel: [ 2534.448076] Arg1: 35246c42 Integer Dec 2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution failed \EV5, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution failed \SMEE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution failed \SMIE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution failed \NEVT, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:20:32 G5 kernel: [ 3237.026638] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=88190 end=88191) time 1687 us, min 894, max 899, scanline start 864, end 14 Dec 2 16:22:20 G5 kernel: [ 3344.842212] wlp0s20f3: AP 90:ef:68:2c:31:9b changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: instantcrush 1622 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-28 (4 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G5 5587 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=0017db25-edad-4311-bca6-171f2624432e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0M2MWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd11/01/2018:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn0M2MWX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
