[Kernel-packages] [Bug 1818881] Re: ath10k_pci crashing
** Tags added: ath10k -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818881 Title: ath10k_pci crashing Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias: pci:v168Cd0040sv*sd*bc*sc*i* alias: pci:v168Cd0
[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
** Tags added: ath10k -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828578] Re: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS
** Tags added: ath10k -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1828578 Title: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Hello Team, Env - Dell XPS 9570 Ubuntu 18.04.2 , HWE kernel We are facing intermittently wifi reconnection issue on Ubuntu 18.04. Software upgrade is up-to date. Also some time we facing freezing issue due to this hard reset required to make machine back to normal. Please let me know if there are any known issue with this particular model on 18.04 ? Please let me know. Thanks Jay --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: itops 1579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-25 (17 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 0c45:671d Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=c41f7762-f3a2-4b42-a019-97ca9bd85edc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: IT-07384 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826716] Re: Include Sunix serial/parallel driver
** Tags added: oem-priority -- 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/1826716 Title: Include Sunix serial/parallel driver Status in HWE Next: New Status in linux-oem package in Ubuntu: New Status in linux-oem source package in Bionic: New Bug description: [Impact] We shipped several platform with sunix device, which is enabled by sunix DKMS driver. We should use in-tree driver instead. [Fix] Include not-yet-merged sunix driver: https://lore.kernel.org/lkml/20190319120723.3691-1-sau...@gmail.com/ [Test] Use command `inputattach` to test serial mouse connected to the Sunix board. The mouse works correctly. [Regression Potential] Low. It's a new driver so the regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1826716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827972] Re: The noise keeps occurring when Headset is plugged in on a Dell machine
** No longer affects: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827972 Title: The noise keeps occurring when Headset is plugged in on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: Steps to reproduce: 1. Plug in headset 2. Select Headset mode Expected result: There is no noise when headset is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1827972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775586] Re: after S3 bt icon shows disable
** No longer affects: oem-priority -- 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/1775586 Title: after S3 bt icon shows disable Status in linux-meta-oem package in Ubuntu: New Bug description: machine: WHN7-DVT2-C7 (201803-26164) Bus 001 Device 005: ID 8087:0025 Intel Corp. the steps to reproduce: 1. flash install whole system 2. install latest linux-oem and linux-firmware 3. reboot 4. press wireless key to disable wireless/bt 5. press wireless key to enable wireless/bt 6. trigger S3 by clicking right top icon 7. bluetooth get disabled after S3 resume. <= issue 8. bluetooth could be re-enabled by clicking UI. but if you install latest mainline kernel 4.17.0-rc7, this issue can not be reproduced. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-oem 4.13.0.1028.33 ProcVersionSignature: Ubuntu 4.13.0-1028.31-oem 4.13.16 Uname: Linux 4.13.0-1028-oem x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 7 19:11:10 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 InstallationDate: Installed on 2018-06-07 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 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/1775586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF not work
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: New Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825940] Re: [graphics] Enable ICL
** Tags added: icelake -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825940 Title: [graphics] Enable ICL Status in intel: Fix Committed Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: New Status in mesa source package in Bionic: New Bug description: [Impact] Ice Lake (ICL) graphics needs to be enabled for OEM OSP1 image which is based on 18.04.3 graphics stack with linux-oem-osp1 kernel. [Test case] The usual desktop usage, graphics tests etc. [Regression potential] Linux-oem-osp1 kernel is a new kernel used only on new OEM enablements, and it can't regress any currently running system. Mesa backports are limited to ICL, so they shouldn't regress earlier generations either. -- Original description: ICL graphics is not enabled in 19.04. if you want to use 19.04 on ICL platform, you need do like this Add kernel option i915.alpha_support=1 Target Release:19.10 Target Kernel: 5.2 Target Mesa: 19.1 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1825940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832299] Re: Add new sound card PCIID into the alsa driver
** Tags added: icelake -- 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/1832299 Title: Add new sound card PCIID into the alsa driver Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1832299 The 0001-xxx.patch is for adding the ICL pciid, it is not in the bionic kernel, so bionic kernel needs two patches. The 0002-xxx.patch is in the upstream from v5.2-rc1, it is needed for b/c/d/e. [Impact] We have some cometlake machines, after installing the bionic kernel, the sound can't work at all, we found the sound driver didn't load into the kernel. [Fix] After add the pciid in the pci_driver, the sound driver can be loaded and sound worked well. [Test Case] Boot the system and play sound or record sound, they all worked well [Regression Risk] Low. Adding new pciid, will not change existing functions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1832299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828133] Re: Intel CyclonePeak wifi firmware
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1828133 Title: Intel CyclonePeak wifi firmware Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Bug description: [Impact] New Intel CyclonePeak Wifi cards require new firmware to enable. [Fix] To update the firmware we want only, backport the following 2 commits from iwlwifi tree for-upstream branch[1], and remove all 9000 series related firmwares. 95a93535 iwlwifi: update -46 firmwares for 22260 and 9000 series 68040ceb iwlwifi: add firmware for 22260 and update 9000 series -46 firmwares 1. git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux- firmware.git [Test Case] Verified on AX200NGW & 22560NGW chips & Killer 1653 card, wifi works well. [Regression Risk] Low. This firmware is for new cards and new ABI, it won't affect current Intel wifi cards, and won't take effect on Bionic(4.15) kernel. Only iwlwifi DKMS driver or oem-osp1 kernel loads this firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1828133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)
** Tags added: oem-priority ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1817518 Title: Bluetooth not working (Intel CyclonePeak) Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: In Progress Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in linux-firmware source package in Cosmic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the device will not work. [Fix] 2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029 This change requires new firmware blob as well, which is to be upstreamed & backported from linux-firmware. [Test Case] Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci device. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device. The most lines of the patches actually introduces an helper function that generates firmware blob name. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported
** Tags added: oem-priority ** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1520343 Title: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Bug description: --- STATUS 2016-03-17: == WARNING: You need at least kernel 4.5.0 for the following new fix to work, else refer to the old method described in post #22 == The support for this card has now been merged to https://github.com/kvalo/ath10k-firmware. The repository now contains the required board.bin, board-2.bin and firmware-4.bin files for the card to initialize and connect to a bgn-access point (5GHz (ac- protocol) is still untested, feel free to modify this if you can confirm it works). Here are the new commands to get you online: sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/ sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true Reboot or reload the ath10k_pci module and you should be able to connect! --- STATUS 2015-12-22: Currently there is a fix for this problem in post #22 (originally post #19, but reposted due to command typos!) which seems to have fixed the issue for many. This bug is unique to revision 32 of the card [168c:003e], fixes for older revisions don't seem to work. There are a couple of issues regarding the fix for some people (not all): 1. Wireless works, but network throughput stops some time after connecting to access point 2. Bluetooth communications take a noticeable performance hit when transferring something over WiFi --- Original description: I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card doesn't work in it or 16.04. The card has the device id 168c:003e as many other cards, for example the Qualcomm Atheros Killer (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a newer revision number (32) and the suggested fixes work only partially and the wireless is unusable. The computer has just been released this summer and is Intel Skylake -based. I've tried the patch from bug 1383184, which has a fix for the card revision 20: Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch files: board.bin firmware-4.bin notice_ath10k_firmware-4.txt ath10k_pci succeeds in loading the firmware, but it seems that the firmware is not working correctly: dmesg | grep ath [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [5.678420] ath10k_pci :07:00.0: Direct firmware load for ath10k/cal-pci-:07:00.0.bin failed with error -2 [5.678773] ath10k_pci :07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2 [5.678781] ath10k_pci :07:00.0: failed to load spec board file, falling back to generic: -2 [5.679445] ath10k_pci :07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 htt 3.26 wmi 4 cal otp max_sta 32 [7.802329] ath10k_pci :07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [8.200607] ath: EEPROM regdomain: 0x6c [8.200614] ath: EEPROM indicates we should expect a direct regpair map [8.200619] ath: Country alpha2 being used: 00 [8.200621] ath: Regpair used: 0x6c [8.216605] ath10k_pci :07:00.0 wlp7s0: renamed from wlan0 [ 13.462029] ath10k_pci :07:00.0: failed to enable dynamic BW: -11 [ 16.461416] ath10k_pci :07:00.0: could not suspend target (-11) [ 24.760062] ath10k_pci :07:00.0: failed to enable dynamic BW: -11 [ 27.759534] ath10k_pci
[Kernel-packages] [Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
** Tags added: skylake -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [19.10] Boot hangs at "loading initial ramdisk" So after completing the upgrade from 19.04 to 19.10, my computer got stuck on the solid purple Grub screen upon reboot. After getting into the grub menu on next boot and booting from advanced options, I see that it gets to "loading initial ramdisk" and then just hangs forever. I am able to boot without issues on the old kernel (5.0.0-32-generic), but not the one that got installed with the upgrade (5.3.0-18-generic). Things I've tried based on what worked for other people who got this problem (though I haven't found anyone who has it specifically with 19.10): acpi=off dis_ucode_ldr disabling secure boot recovery mode making sure all packages are up to date I'm kind of at a loss of what to do, other than just keep using the old kernel. (which presumably might cause problems at some point?) I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10 resulted in unable to boot system. Hardware Dell XPS 9550 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 91 structures occupying 5683 bytes. Table at 0x000E. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.11.2 Release Date: 07/30/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.11 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: XPS 15 9550 Version: Not Specified Serial Number: 5QRHRF2 UUID: 4c4c4544-0051-5210-8048-b5c04f524632 Wake-up Type: Power Switch SKU Number: 06E4 Family: XPS Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0N7TVV Version: A01 Serial Number: /5QRHRF2/CN129636CS0026/ Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Dell Inc. Type: Laptop Lock: Not Present Version: Not Specified Serial Number: 5QRHRF2 Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Laptop Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB1 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0005, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB2 Internal Connector Type: None External Reference Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0006, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSBC1 Internal Connector Type: None External Reference Designator: USB TYPEC External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0007, DMI type 8, 9 bytes Port Connector Infor
[Kernel-packages] [Bug 1857409] Re: alsa/sof: load different firmware on different platforms
The patch has been reverted by https://bugs.launchpad.net/bugs/1860642 ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857409 Title: alsa/sof: load different firmware on different platforms Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: [Impact] In our ubuntu kernel, the sof driver will load the sof-cnl.ri (firmware) on all platforms, but mainline kernel already supported the multi firmwares on differnt platforms, and OEM project needs us to support the mutli-firmware names in the ubuntu kernel [Fix] cherry-pick 3 upstream patches, then on cnl platforms, it will load sof-cnl.ri, on cml platfomrs, it will load sof-cml.ri, on cfl platforms, it will load sof-cfl.ri [Test Case] Prepare the firmware from https://github.com/thesofproject/linux-firmware master branch, then boot the kernel with these patches. [Regression Risk] Low, just let different platforms load differnt firmware, and these patches are in the upstream kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857409] Re: alsa/sof: load different firmware on different platforms
Hi, Hui I think we have misalignment here, there are two set of patches 1. The patch to load the firmware from the different path (the patches are reverted by LP #1860642. 2. The patch to fix hanging issues when sof_probe_continue() is failed[2]. Intel (Mengdong@Intel) is not planning to backport [2]patches to sof-v5.0 and mainline-kernel-5.3. But Canonical should still be able to land[1] patches to load the firmware from the different path, isn't it? We need to align how we plan to to ship the firmware, and in which version of path. [1] https://bugs.launchpad.net/bugs/1860642 [2] Fix sof core error handling (v3, alternative to R1743/1745) by kv2019i · Pull Request #1746 · thesofproject/linux - https://github.com/thesofproject/linux/pull/1746/commits -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857409 Title: alsa/sof: load different firmware on different platforms Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: [Impact] In our ubuntu kernel, the sof driver will load the sof-cnl.ri (firmware) on all platforms, but mainline kernel already supported the multi firmwares on differnt platforms, and OEM project needs us to support the mutli-firmware names in the ubuntu kernel [Fix] cherry-pick 3 upstream patches, then on cnl platforms, it will load sof-cnl.ri, on cml platfomrs, it will load sof-cml.ri, on cfl platforms, it will load sof-cfl.ri [Test Case] Prepare the firmware from https://github.com/thesofproject/linux-firmware master branch, then boot the kernel with these patches. [Regression Risk] Low, just let different platforms load differnt firmware, and these patches are in the upstream kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871811] Re: Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled
** Changed in: oem-priority 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/1871811 Title: Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled Status in NULL Project: New Bug description: Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled It seems to lack of https://lore.kernel.org/lkml/20191128081041.6948-1-jian-h...@endlessm.com/. To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1871811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871812] Re: Can not see the storage with Intel RAID On mode enabled
The patch is needed to improve the installer user experience on Focal for Intel RST/RAID mode users, who switch from Windows to Linux. ** Description changed: - Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled - It seems to lack of https://lore.kernel.org/lkml/20191128081041.6948-1-jian-h...@endlessm.com/. + Can not see the storage on Dell Latitude 5310 with Intel RAID On mode + enabled in the BIOS. + + The Dell Latitude 5310 is an Intel Coment Lake platform, which missing + the ID[1] in the kernel. + + [1] https://lore.kernel.org/lkml/20191128081041.6948-1-jian- + h...@endlessm.com/. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1536 F pulseaudio CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 09:55:02 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405) MachineType: Dell Inc. Latitude 5310 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- toram RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.4.12:bd01/09/2020:svnDellInc.:pnLatitude5310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5310 dmi.product.sku: 099F dmi.sys.vendor: Dell Inc. ** Changed in: oem-priority Importance: Undecided => Critical ** Summary changed: - Can not see the storage with Intel RAID On mode enabled + Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake ** Description changed: Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled in the BIOS. - The Dell Latitude 5310 is an Intel Coment Lake platform, which missing + The Dell Latitude 5310 is an Intel Comet Lake platform, which missing the ID[1] in the kernel. [1] https://lore.kernel.org/lkml/20191128081041.6948-1-jian- h...@endlessm.com/. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1536 F pulseaudio CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 09:55:02 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405) MachineType: Dell Inc. Latitude 5310 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- toram RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.4.12:bd01/09/2020:svnDellInc.:pnLatitude5310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5310 dmi.product.sku: 099F dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871812 Title: Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled in the BIOS. The Dell Latitude 5310 is an Intel Comet Lake platform, which missing the ID[1] in the kernel. [1] https://lore.kernel.org/lkml/20191128081041.6948-1-jian- h...@endlessm.com/. ProblemType: B
[Kernel-packages] [Bug 1871812] Re: Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake
@kaihengfeng @anthonywong would it possible to land this before focal release? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871812 Title: Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled in the BIOS. The Dell Latitude 5310 is an Intel Comet Lake platform, which missing the ID[1] in the kernel. [1] https://lore.kernel.org/lkml/20191128081041.6948-1-jian- h...@endlessm.com/. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1536 F pulseaudio CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 09:55:02 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405) MachineType: Dell Inc. Latitude 5310 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- toram RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.4.12:bd01/09/2020:svnDellInc.:pnLatitude5310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5310 dmi.product.sku: 099F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
** Changed in: oem-priority Importance: High => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: In Progress Status in linux-firmware source package in Focal: Invalid Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859387] Re: intel/sof: update the intel sof firmware to v1.3-0f73628 for cml and cnl
** Changed in: oem-priority Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1859387 Title: intel/sof: update the intel sof firmware to v1.3-0f73628 for cml and cnl Status in OEM Priority Project: Fix Committed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Eoan: Fix Released Bug description: [Impact] Intel released a new version sof firmware to Canonical, they suggested that we should integrate the version v1.3-0f73628 and we should only pick the cml and cnl firmwares since other firmwares are not fully tested. Since we have a couple of Lenovo and Dell cnl and cml machines which need to enable sof driver, we integrate the firmwares to ubuntu. [Fix] - fix the hang issue in the firmware for the cml and cnl - introduce the ldc file which helps to do the firmware debug - divide the firmware to cml and cnl specific ones [Test Case] These firmwares are already widely used in oem project, the audio functions worked very well under both Lenovo and Dell dmic machines. [Regression Risk] Low, Intel released these firmware to us, and we already did large numbers audio test in the oem project. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1859387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872034] Re: [Focal] No HDMI output through thunderbolt docking station
** 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/1872034 Title: [Focal] No HDMI output through thunderbolt docking station Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Bug description: I can find monitor in display list, but no output from it. Also, I can't switch to extend mode, it failed to apply the setting and switched back to mirror mode. [Steps] 1. Connect a thunderbolt docking station to thunderbolt port. 2. Connect HDMI monitor to HDMI port on the docking station. 3. Switch mode in display setting ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:44:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=98c0c28f-278e-442b-8fc9-6d663bacd68d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd01/08/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878670] Re: Gnome crash frequently
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Leon Liao (lihow731) ** Changed in: oem-priority Importance: Undecided => Medium ** Changed in: oem-priority 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/1878670 Title: Gnome crash frequently Status in OEM Priority Project: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Triaged Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855954] Re: [TGL] VMD support in TGL
** Tags added: tigerlake -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855954 Title: [TGL] VMD support in TGL Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: VMD support in Tiger Lake Platform Target Kernel: TBD Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1855954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855399] Re: [TGL] graphics kernel support
** Tags added: tigerlake -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855399 Title: [TGL] graphics kernel support Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: This feature tracks the updates TGL graphics updates. We will submit the commit id lists since 5.4. 20.04 will use v5.4 as a base, (2109/11/25) first commit lists will be provided in 2020/01, if you need more before that, please let us know. Target Release: 20.10 Target Kernel: v5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1855399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854244] Re: [TGL][pmc_core]Need patch to support offset number 21 and 22 device LTR ignore
** Tags added: tigerlake -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854244 Title: [TGL][pmc_core]Need patch to support offset number 21 and 22 device LTR ignore Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Description: Intel PMC_CORE driver, the currently device LTR ignore function support covers the IP offset from 0 to 20, while e.g. tgl , which support IP offset 21 and 22 root@p-tgl02/sys/kernel/debug/pmc_core # cat ltr_show SOUTHPORT_A LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 SOUTHPORT_B LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 SATA LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 GIGABIT_ETHERNET LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 XHCI LTR: RAW: 0x9001 Non-Snoop(ns): 0 Snoop(ns): 1048576 Reserved LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 ME LTR: RAW: 0x8000800 Non-Snoop(ns): 0 Snoop(ns): 0 EVA LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 SOUTHPORT_C LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 HD_AUDIO LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 CNV LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 LPSS LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 SOUTHPORT_D LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 SOUTHPORT_E LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 CAMERA LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 ESPI LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 SCC LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 ISH LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 UFSX2 LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 EMMC LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 WIGIG LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 CURRENT_PLATFORM LTR: RAW: 0x40201 Non-Snoop(ns): 0 Snoop(ns): 0 AGGREGATED_SYSTEM LTR: RAW: 0x7dbebf5 Non-Snoop(ns): 0 Snoop(ns): 1037312 and currently pmc_core does not support offset number 21, 22 device LTR ignore: root@p-tgl02/sys/kernel/debug/pmc_core # echo 21 > ltr_ignore -bash: echo: write error: Invalid argument root@p-tgl02/sys/kernel/debug/pmc_core # echo 22 > ltr_ignore -bash: echo: write error: Invalid argument root@p-tgl02/sys/kernel/debug/pmc_core # echo 20 > ltr_ignore root@p-tgl02/sys/kernel/debug/pmc_core # So need your help to have a patch for the offset number 21, 22 device LTR supported. Target Release: 20.04 Target Kernel: 5.7 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1854244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771254] Re: [TGL] SPI support
** Tags added: tigerlake -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771254 Title: [TGL] SPI support Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Description: Adding CSE DMA access capability to SPI and UART controller. Target Release: 20.04 Target Kernel: v5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1771254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842236] Re: [TGL] Trace Hub 2.x Enhancements/NPK
** Tags added: tigerlake -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842236 Title: [TGL] Trace Hub 2.x Enhancements/NPK Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Description Enable Trace Hub 2.x Enhancements/NPK Should be same solution as ICL except for new PCI IDs Target Release: 20.04 Target Kernel: 5.5 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1842236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510570] Re: Bluetooth LE pairing fail
** Changed in: oem-priority Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: Bluetooth LE pairing fail Status in OEM Priority Project: Won't Fix Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Xenial: Won't Fix Bug description: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] On xenial install from ppa: https://launchpad.net/~bluetooth/+archive/ubuntu/bluez Now reboot the machine. The BT adapter shall be powered on. [Regression Potential] If things go wrong the adapter will not be powered on after the system boots up. Therefore while testing please focus on the adapter state, i.e. powered on or off. [Other Info] This fix is included in the development release, see: http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 [What to upload] For xenial as in: ) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez ) https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871812] Re: Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871812 Title: Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: === SRU Justification === [Impact] ID is missing so the devcie isn't bound to AHCI driver. Without the driver, we can't check the existence of remapped NVMe. [Fix] Add one missing ID. [Test] Use lspci to see if the device is bound to ahci driver. Test positive after applying the patch. [Regression Potential] Low. This is a trivial fix which limits to one specific device. === Original Bug Report === Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled in the BIOS. The Dell Latitude 5310 is an Intel Comet Lake platform, which missing the ID[1] in the kernel. [1] https://lore.kernel.org/lkml/20191128081041.6948-1-jian- h...@endlessm.com/. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1536 F pulseaudio CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 09:55:02 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405) MachineType: Dell Inc. Latitude 5310 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- toram RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.4.12:bd01/09/2020:svnDellInc.:pnLatitude5310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5310 dmi.product.sku: 099F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872351] Re: Qualcomm Atheros QCA6174 Killer 1435 Wireless-AC: Disabling wifi causes kernel warning in __sta_info_destroy_part2
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority 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/1872351 Title: Qualcomm Atheros QCA6174 Killer 1435 Wireless-AC: Disabling wifi causes kernel warning in __sta_info_destroy_part2 Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: I have multiple issues with wifi on my Dell XPS 9380. This error was triggered when I tried to disable my wifi. [ 3634.322471] [ cut here ] [ 3634.322524] WARNING: CPU: 3 PID: 1188 at net/mac80211/sta_info.c:1057 __sta_info_destroy_part2+0x14e/0x160 [mac80211] [ 3634.322525] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_hdmi dell_laptop snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_usb_audio ath10k_pci x86_pkg_temp_thermal snd_usbmidi_lib snd_seq_midi snd_hwdep snd_seq_midi_event ath10k_core intel_powerclamp coretemp cdc_ether snd_rawmidi usbnet btusb kvm_intel r8152 ath btrtl mii btbcm kvm snd_seq uvcvideo videobuf2_vmalloc btintel videobuf2_memops intel_cstate videobuf2_v4l2 joydev snd_seq_device snd_pcm dell_wmi intel_rapl_perf videobuf2_common bluetooth mac80211 dell_smbios videodev snd_timer dcdbas mc input_leds ecdh_generic ecc wmi_bmof snd dell_wmi_descriptor serio_raw intel_wmi_thunderbolt cfg80211 soundcore rtsx_pci_ms libarc4 memstick hid_multitouch processor_thermal_device ucsi_acpi typec_ucsi mei_me intel_rapl_common [ 3634.322564] intel_xhci_usb_role_switch mei typec intel_soc_dts_iosf intel_pch_thermal roles int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_pad intel_hid acpi_thermal_rel sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 mmc_block dm_crypt usbhid hid_generic crct10dif_pclmul crc32_pclmul rtsx_pci_sdmmc i915 ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_algo_bit glue_helper drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt i2c_i801 fb_sys_fops nvme_core drm intel_lpss_pci rtsx_pci intel_lpss idma64 i2c_hid virt_dma wmi hid pinctrl_sunrisepoint video pinctrl_intel [ 3634.322599] CPU: 3 PID: 1188 Comm: NetworkManager Tainted: G OE 5.4.0-21-generic #25-Ubuntu [ 3634.322600] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.12.1 12/11/2019 [ 3634.322633] RIP: 0010:__sta_info_destroy_part2+0x14e/0x160 [mac80211] [ 3634.322635] Code: 24 0c 01 00 00 00 0f 84 52 ff ff ff 45 31 c0 b9 01 00 00 00 4c 89 e2 48 89 de 4c 89 ef e8 0a a6 ff ff 85 c0 0f 84 34 ff ff ff <0f> 0b e9 2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 [ 3634.322636] RSP: 0018:a70c009c3918 EFLAGS: 00010282 [ 3634.322638] RAX: ff94 RBX: 9006104cc8c0 RCX: [ 3634.322640] RDX: 90061ba3c740 RSI: RDI: 900613a62f48 [ 3634.322641] RBP: a70c009c3938 R08: 90061e4d78c8 R09: 0004 [ 3634.322642] R10: R11: R12: 900613f28000 [ 3634.322643] R13: 900613a607a0 R14: 9006104cc8c0 R15: 900613a60d68 [ 3634.322644] FS: 7f596b396240() GS:90061e4c() knlGS: [ 3634.322645] CS: 0010 DS: ES: CR0: 80050033 [ 3634.322646] CR2: 0db00945f000 CR3: 000494824005 CR4: 003606e0 [ 3634.322647] Call Trace: [ 3634.322670] __sta_info_flush+0x128/0x180 [mac80211] [ 3634.322696] ieee80211_set_disassoc+0xc0/0x5f0 [mac80211] [ 3634.322719] ieee80211_mgd_deauth+0x104/0x490 [mac80211] [ 3634.322743] ieee80211_deauth+0x18/0x20 [mac80211] [ 3634.322782] cfg80211_mlme_deauth+0xb6/0x1e0 [cfg80211] [ 3634.322804] cfg80211_mlme_down+0x66/0x80 [cfg80211] [ 3634.322823] cfg80211_disconnect+0x127/0x1e0 [cfg80211] [ 3634.322827] ? _raw_spin_unlock_bh+0x1e/0x20 [ 3634.322845] __cfg80211_leave+0x133/0x1b0 [cfg80211] [ 3634.322862] cfg80211_leave+0x2c/0x40 [cfg80211] [ 3634.322879] cfg80211_netdev_notifier_call+0x1b2/0x590 [cfg80211] [ 3634.322902] ? ath10k_warn.cold+0x1a/0x1f [ath10k_core] [ 3634.322911] ? ath10k_config_ps+0x52/0x70 [ath10k_core] [ 3634.322913] ? rtnl_is_locked+0x15/0x20 [ 3634.322917] ? inetdev_event+0x47/0x560 [ 3634.322919] ? skb_dequeue+0x5a/0x70 [ 3634.322923] notifier_call_chain+0x55/0x80 [ 3634.322925] raw_notifier_call_chain+0x16/0x20 [ 3634.322927] call_netdevice_notifiers_info+0x2e/0x60 [ 3634.322929] __dev_close_many+0x63/0x120 [ 3634.322931] dev_close_many+0x91/0x150 [ 3634.322933] dev_close.part.0+0x4a/0x70 [ 3634.322936] dev_close+0x18/0x20 [ 3634.32
[Kernel-packages] [Bug 1880663] Re: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Medium -- 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/1880663 Title: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: In Progress Bug description: With linux-4.15.0-1081 kernel, it usually stuck at purple screen after grub. There is no any log in journal when it fails to boot up, and earlyprintk shows nothing on the screen, either. System Information Manufacturer: Dell Inc. Product Name: Latitude 7300 Version: Not Specified Serial Number: J83ZST2 UUID: 4C4C4544-0038-3310-805A-CAC04F535432 Wake-up Type: Power Switch SKU Number: 08E0 Family: Latitude BIOS Information Vendor: Dell Inc. Version: 1.6.1 Release Date: 11/14/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 24 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Japanese floppy for NEC 9800 1.2 MB is supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.6 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1880663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839124] Re: BT advertising packet wakes up the system from S3 and suspend-to-idle
** Changed in: oem-priority Importance: Critical => High ** Changed in: oem-priority Assignee: Shih-Yuan Lee (fourdollars) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839124 Title: BT advertising packet wakes up the system from S3 and suspend-to-idle Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: A generic issue which happens on Intel BT(8087:0aaa) and Atheros BT(0cf3:e005)(0cf3:e007). Once the system has paired with BT4 devices(disconnected), the system will be waken up randomly from S3/s2idle while receiving advertising packet from any random BT4 devices in the environment which are even not paired/connected. By removing all previously paired BT4 devices(disconnected) from BT menu can fix this issue. The advertising packet could be none connectable undirected or connectable undirected. And the BT4 devices we found can reproduce this issue are 1. Microsoft Surface 1678 2. Logitech K375s 3. Microsoft Designer Mouse --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1539 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3300 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0FN010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3300 dmi.product.sku: 08BB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1839124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839124] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1028:0310] BT advertising packet wakes up the system from S3 and suspend-to-idle
The workaround is to unload the linux kernel module before suspend. But most likely this needs to be fixed in kernel driver or firmware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839124 Title: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1028:0310] BT advertising packet wakes up the system from S3 and suspend-to-idle Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: A generic issue which happens on Intel BT(8087:0aaa) and Atheros BT(0cf3:e005)(0cf3:e007). Once the system has paired with BT4 devices(disconnected), the system will be waken up randomly from S3/s2idle while receiving advertising packet from any random BT4 devices in the environment which are even not paired/connected. By removing all previously paired BT4 devices(disconnected) from BT menu can fix this issue. The advertising packet could be none connectable undirected or connectable undirected. And the BT4 devices we found can reproduce this issue are 1. Microsoft Surface 1678 2. Logitech K375s 3. Microsoft Designer Mouse --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1539 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3300 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0FN010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3300 dmi.product.sku: 08BB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1839124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881097] Re: [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF when USB Headset is attached.
** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881097 Title: [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF when USB Headset is attached. Status in linux package in Ubuntu: Confirmed Bug description: Problem Description: Using Ubuntu 20.04 on a Thinkpad X1C7 machine. Speaker(F1) and Microphone(F4) Hotkey LED Light Stays ON/OFF when USB Headset is attached. - $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Ubuntu Software: 3.36.1 - Expected Result: When LED light of Speaker(F1)/Microphone (F4) hotkeys is ON/OFF and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED light state will change accordingly. Actual Result: 1. When LED light of Speaker(F1)/Microphone (F4) hotkeys is OFF and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED light will STAY OFF and remains in OFF State always on the duration that the USB headset is attached to the machine. 2. If LED light of Speaker(F1)/Microphone (F4) hotkeys is ON and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED will STAY ON and remains in ON State on the duration that the USB headset is attached to the machine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1410 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 18:48:04 2020 InstallationDate: Installed on 2020-05-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20U9SITR38 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=ab59da99-085b-4f8d-af14-4fc4240a8f83 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET11C (1.01C ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9SITR38 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET11C(1.01C):bd02/12/2020:svnLENOVO:pn20U9SITR38:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9SITR38:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9SITR38 dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => hugh chao (hugh712) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Uns
[Kernel-packages] [Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
It's the same issue happens on Dell XPS 13 9300[1], the solution[2] has been proposed to kernel mailing list by Acelan. It's expected to be land in the next SRU cycle (05-Apr). [1] Bug #1865962 “Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fail...” : Bugs : linux package : Ubuntu - https://bugs.launchpad.net/bugs/1865962 [2] [PATCH 0/6][SRU][Focal] Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails to load firmware - https://lists.ubuntu.com/archives/kernel-team/2020-March/107993.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859287 Title: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi there, Laptop: Dell XPS 13 7390 2-in-1 Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04. Firmware crashes after loading and interface doesn't show up. This is with: linux-image-5.4.0-9-generic 5.4.0-9.12 linux-firmware 1.184 I've noticed the driver was trying to load a more recent firmware: Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 I've downloaded this file from upstream iwlwifi firmware git and tried unloading/reloading iwlwifi. Driver crashes as well, but with a different error code. Best, - LM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lool 1579 F pulseaudio /dev/snd/pcmC0D0p: lool 1579 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 15:02:08 2020 InstallationDate: Installed on 2019-12-02 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off plymouth.force-scale=3 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago) dmi.bios.date: 11/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd11/10/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851202] Re: Need iw 5.3 in 18.04 Bionic
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => oem-priority ** Changed in: oem-priority Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851202 Title: Need iw 5.3 in 18.04 Bionic Status in OEM Priority Project: New Status in iw package in Ubuntu: Opinion Bug description: Current iw verion in Bionic is 4.14. Need iw 5.3 for better 802.11ax High-Efficiency Wireless support. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1851202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816548] Re: [MIR] usbguard
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => oem-priority ** Changed in: oem-priority 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/1816548 Title: [MIR] usbguard Status in OEM Priority Project: New Status in usbguard package in Ubuntu: Incomplete Bug description: * Availability In sync with Debian, built on all architectures https://launchpad.net/ubuntu/+source/usbguard/0.7.4+ds-1 * Rationale We want to increase the security of USB devices, GNOME is working on this feature for next cycle and relying on the usbguard service https://wiki.gnome.org/Internships/2018/Projects/USB-Protection The binaries we want to promote are usbguard and libusbguard0. * Security No known security issues, but due to the nature of this package, a security review is probably needed. https://security-tracker.debian.org/tracker/source-package/usbguard https://people.canonical.com/~ubuntu-security/cve/pkg/usbguard.html * Quality assurance The security team is subscribed to the package https://bugs.launchpad.net/ubuntu/+source/usbguard https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=usbguard https://github.com/USBGuard/usbguard/issues The package build does 'make check' on the basic upstream tests, there is an upstream --enable-full-test-suite but some of those tests can't work in a buildd environment. There is no autopkgtest * Dependencies No universe binary dependencies * Standards compliance current 4.2 standards-version, debhelper compat 11, dh 7 style simple rules * Maintenance Upstream is active, the package is maintained in Debian and in sync for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1816548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850886] Re: Auto-rotate is not working properly when system is booted up while not in its regular orientation
** Package changed: linux-meta-oem (Ubuntu) => oem-priority ** Changed in: oem-priority Importance: Undecided => Medium ** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) -- 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/1850886 Title: Auto-rotate is not working properly when system is booted up while not in its regular orientation Status in GNOME Shell: New Status in OEM Priority Project: Confirmed Bug description: [RELEASE VERSION] Description: Ubuntu 18.04.3 LTS Release: 18.04 [PACKAGE VERSION] linux-oem: Installed: 4.15.0.1057.61 Candidate: 4.15.0.1057.61 Version table: *** 4.15.0.1057.61 500 500 http://jp.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1004.2 500 500 http://jp.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [EXPECTED OUTPUT] Upon boot up with auto-rotation enabled, display should show the proper screen orientation of the system accordingly [ACTUAL OUTPUT] Auto-rotation is not working properly when system is booted up while not in its regular orientation [STEPS] 1. Make sure auto-rotation is enabled on the system 2. Before turning the system on, put it on tablet mode, with the inverted landscape rotation (the top part/the part with the camera is adjacent to the surface). The system should follow this orientation when the login screen appears. 3. Login to the system 4. Switch to the clam shell mode. The display suddenly becomes inverted/the opposite direction of the expected output. 5. Switch back to the tablet mode. The display also ends up being inverted/in the opposite direction of the expected output [REMARKS] *Using WHL *The system seems to be setting the orientation according to the orientation during boot up ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21 Uname: Linux 5.0.0-1024-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 14:23:14 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso InstallationDate: Installed on 2019-07-25 (98 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1850886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804028] Re: Surface Go - QCA6174 wifi card not correctly recognized and therefore not working
The driver should has been landed in Ubuntu-1.167, which available in bionic. Please verify with the latest LTS version. ** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1804028 Title: Surface Go - QCA6174 wifi card not correctly recognized and therefore not working Status in linux-firmware package in Ubuntu: Incomplete Status in linux-firmware package in Fedora: Fix Released Bug description: Output of dmesg on Surface Go fresh installed Ubuntu 18.10. "[ 4.242132] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 168c:3370 [ 4.242138] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [ 4.243006] ath10k_pci :01:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [ 4.308059] ath10k_pci :01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370 from ath10k/QCA6174/hw3.0/board-2.bin [ 4.309354] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 ed5f849a" There is a board.bin available directly from the vendor http://www.killernetworking.com/support/K1535_Debian/board.bin The only thing which is missing is getting this added to https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles so the official board-2.bin. My problem is that I dont know how to read the board files and modify them because I do not know the encoding they use. Also there have been some updates in the upstream linux-firmware repo. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=a87eb5f7bac0f70ade57da57d9126d14eee12336 and https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0 but they also do not help to get the wifi card working/recognized. Any ideas how to get this solved? Also there is a guide how to port it to Linux https://developer.qualcomm.com/download/qca9377/wlan-bluetooth-linux- porting-guide.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1804028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic on Dell XPS 13 9370
** Summary changed:
- Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
+ Wireless regularly breaking (ath10k firmware crashed!) after upgrade to
Cosmic on Dell XPS 13 9370
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807974
Title:
Wireless regularly breaking (ath10k firmware crashed!) after upgrade
to Cosmic on Dell XPS 13 9370
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
Cosmic. A handful of times per day, my wireless stops working ("?"
appears in the icon in Network Manager). Turning wireless off and then
on again, or suspending and waking the machine up, makes the wireless
work again.
dmesg output is as follows:
$ dmesg | grep ath10k
[ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid
6317c652-4817-4fdd-b6d7-c7b8336e493f)
[ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[ 6646.270369] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
[ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800 29 29 106 107
[ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00 20 19 18 19
[ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000 8 8 10 8
[ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
[ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 6 6
[ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
[ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
[ 6647.239340] ath10k_pci :02:00.0: device successfully recovered
[17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid
03393f2f-0ce1-4017-b711-40dd14f2ec11)
[17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[17641.848065] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
[17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800 6 6 243 244
[17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00 53 52 51 52
[17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5
[17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
[17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 30 30
[17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
[17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
[17642.835601] ath10k_pci :02:00.0: device successfully recovered
[17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
[17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118
I do not recall having any wireless issues before I upgraded (when
this machine was running Bionic).
Bug #1730331 - ath10k_pci: firmware crashed!
Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
could be related, but appear to be related to earlier releases, whereas my
issue has appeared/become much worse on Cosmic.
ProblemType: Bug
DistroRelease
[Kernel-packages] [Bug 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
The dkms was updated at 29 Mar 2019 ubuntu@201701-25364:/tmp$ dkms status amdgpu-pro, 16.60-377537, 4.4.0-127-generic, x86_64: installed amdgpu-pro, 16.60-377537, 4.4.0-49-generic, x86_64: installed oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-127-generic, x86_64: installed oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-170-generic, x86_64: installed oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 2.0, 4.4.0-170-generic, x86_64: installed ubuntu@201701-25364:/tmp$ apt -o Debug::Acquire::http=true download oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms-dkms 0% [Working]GET /updates/pool/public/o/oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms-dkms/oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms-dkms_2.0_all.deb HTTP/1.1 Host: dell.archive.canonical.com User-Agent: Debian APT-HTTP/1.3 (1.2.32) 0% [Waiting for headers]Answer for: http://dell.archive.canonical.com/updates/pool/public/o/oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms-dkms/oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms-dkms_2.0_all.deb HTTP/1.1 200 OK Date: Wed, 27 Nov 2019 14:24:39 GMT Server: Apache/2.4.7 (Ubuntu) Last-Modified: Fri, 29 Mar 2019 10:56:31 GMT ETag: "6f5c20-5853985faf5c0" Accept-Ranges: bytes Content-Length: 7298080 Content-Type: application/x-debian-package Get:1 http://dell.archive.canonical.com/updates xenial-dell/public amd64 oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms-dkms all 2.0 [7298 kB] Fetched 7298 kB in 3s (1978 kB/s) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-signed source package in Xenial: New Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dum
[Kernel-packages] [Bug 1844102] Re: Can't enable WLAN on Dell platform when enabling control WLAN radio then unplug LAN
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: oem-priority Status: New => Invalid ** Changed in: oem-priority Assignee: Che Cheng (cktenn) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844102 Title: Can't enable WLAN on Dell platform when enabling control WLAN radio then unplug LAN Status in OEM Priority Project: Invalid Status in linux package in Ubuntu: Invalid Bug description: There is a BIOS option to control WLAN radio on Dell laptop. When plugging LAN cable, the WLAN radio is blocked, unplugging LAN cable and the WLAN radio should be unblocked. Dell also has docking stations like WD19 series that equipped with USB LAN. The LAN chip on WD19 series is Realtek 8153 gigabit ethernet. The issue is when turning on WLAN radio control and plugging the docking station with LAN connection, the wireless network will be turned off. While disconnecting LAN, the wireless network remains off. The Realtek 8153 runtime power management is set to auto by TLP package. If the power management is set to on, then this issue can't be reproduced. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1148 F pulseaudio Date: Mon Sep 16 16:24:15 2019 InstallationDate: Installed on 2019-09-12 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190912) MachineType: Dell Inc. XPS 13 9380 ProcEnviron: LANGUAGE=zh_TW:zh TERM=xterm-256color PATH=(custom, no user) LANG=zh_TW.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=UUID=1a9b9bc1-0d98-4e39-9fd1-a1bad1681880 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0SSY11 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:bd03/20/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0SSY11:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1844102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812357] Re: Mobile Broadband panel still shows "Connected" after removing the SIM card
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => oem-priority ** Changed in: oem-priority Importance: Undecided => Low ** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812357 Title: Mobile Broadband panel still shows "Connected" after removing the SIM card Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Triaged Bug description: [Reproduce Steps] 1. Boot to Ubuntu 18.04 desktop and insert a SIM card and make sure can mobile connection could work successfully. 2. Removing the SIM card from the slot. [Result] Expected Result: Mobile Broadband panel should reflect the interruption in network connection and toggle off the "Connected" status Actual Result: Mobile Broadband UI still shows "Connected" even without active network connection To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1812357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847250] Re: update firmware for sound sof driver to fix the hang issue on several Dell machines
Hi, This version of firmware[1] is not signed by Intel. The Comet Lake (CML) processor will validate the PV bits of the firmware, and it will refuse to load the sof-cnl.ri firmware sof-audio-pci :00:1f.3: error: load fw failed ret: -110 This SRU breaks the DMIC on CML platform. Please kindly replace the firmware binary for the CML platforms. [1] 4dbdd3366e840562b2a1da3927b1075e intel/sof/sof-cnl.ri -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1847250 Title: update firmware for sound sof driver to fix the hang issue on several Dell machines Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Status in linux-firmware source package in Eoan: Fix Released Bug description: We expect this firmware update could be released with 19.10 [Impact] We have a couple of Dell machines, after installing the system, it will hang randomly, and this issue was reported by factory, they met this issue a couple of times. Then we tried to reproduce this issue, finally reproduced it. [Fix] Intel debugged this issue as well, and they provided 4 kernel patches and a new firmware, we tested them, they really can fix the issue. And the patches were sent the SRU already, now it is time to update firmware. [Test Case] Install the system repeatedly and there is no hang issue anymore. [Regression Risk] Low, Intel told us there is no ABI change for the firmware, so it is safe to run this firmware both with the old driver (not applied those 4 patches) and the new driver (applied those 4 patches). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838921] Re: ability to install dkms without version checking and retire it when kernel fixed issue
** Changed in: oem-priority
Status: New => Fix Released
--
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/1838921
Title:
ability to install dkms without version checking and retire it when
kernel fixed issue
Status in OEM Priority Project:
Fix Released
Status in dkms package in Ubuntu:
Fix Released
Status in dkms source package in Bionic:
Fix Released
Status in dkms source package in Disco:
Fix Released
Bug description:
refer to https://github.com/dell/dkms/pull/98
[Impact]
to have a way for this case
"user need to force install the dkms, but also would like to retire that dkms
once kernel fixes the issue."
- upstream patch : https://github.com/dell/dkms/pull/98
[Test case]
1. install the dkms package which already patched
2. install a DKMS which has file content "{dkms name}_version-override" under
/usr/share/dkms/modules_to_force_install/
- the installation should ignore module version checking.
3. update that installed DKMS to a new one which added OBSOLETE_BY in
dkms.conf
- on the kernel which version lower than OBSOLETE_BY, the dkms should be
installed.
- on the kernel which version higher than OBSOLETE_BY, the dkms should NOT
be installed.
[Regression potential]
medium as it touched the version sanity. This change already there in
upstream.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1838921/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833405] Re: add firmware and topology file for sound sof driver [cml/cnl]
New firmware has been proposed on mailing list. https://patchwork.ozlabs.org/patch/1119327/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1833405 Title: add firmware and topology file for sound sof driver [cml/cnl] Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Disco: New Status in linux-firmware source package in Eoan: New Bug description: [Impact] We have a couple dell and lenovo laptops which have dmic directly connected to PCH, this needs intel sof driver to work, and intel sof driver is merged oem-osp1-b kernel and it needs to load firmware and topology file to work. [Fix] Intel provides two binary files to us, one is firmware, the other is topology file, these two files are built from https://github.com/thesofproject/sof.git, and the license is BSD 3. [Test Case] put the firmware and topology to rootfs and boot with the oem-osp1-b kernel on those machines, the sof driver works well. [Regression Risk] Low. just adding two new binary files, no change to existing files. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1833405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799389] Re: not use /etc/thermald/thermal-conf.xml by default
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1799389 Title: not use /etc/thermald/thermal-conf.xml by default Status in OEM Priority Project: Confirmed Status in thermald package in Ubuntu: New Bug description: from man thermal-conf.xml, thermald should use /etc/thermald/thermal-conf.xml by default. So, that user can control the behavior. " - If the ACPI data is not optimized or buggy. In this case thermal-conf.xml can be used to correct the behavior without change in BIOS. " But, current thermald will always use the one auto generated: /var/run/thermald/thermal-conf.xml.auto --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 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+bionic-master+X32 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: thermald 1.7.0-5ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-1024.29-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1024-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1799389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832693] Re: System auto suspend again during resuming
** Tags added: oem-priority ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Package changed: linux-oem (Ubuntu) => oem-priority -- 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/1832693 Title: System auto suspend again during resuming Status in OEM Priority Project: New Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: ## Issue In certain case, system wake-up from suspend will suspend again automatically. The issue comes from a target machine turning auto-suspend on and suspends after the idle time-out. Manually suspend, e.g., click suspend icon or execute "systemctl suspend" won't reproduce the issue. When waking up from this situation, the monitor keeps blank, although the monitor has exited low power mode, then suspend again immediately. Can successfully waking up the system after that, but once the system reaches the idle time again, the issue appears repeatedly. From the system log, a sleep request is following the wake request. Hardware configuration also counts. It is hard to reproduce the issue with the system installed on SSD or with a lower resolution monitor; graphics card may also affect. It's likely to be a timing issue. ## Environment Machine: Dell Precision 7920 Tower. Monitor: Philips 288P6L DistroRelease: Ubuntu 18.04.2 Graphics card: Nvidia Quadro P2200 Nvidia driver version: 418.74 CPU: Intel(R) Xeon(R) Platinum 8276 CPU @ 2.20GHz ## Steps to reproduce: Turn on automatic suspend in Settings->Power Wait for the system to suspend Wake up the system via pressing power button or keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1832693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838982] Re: unable to handle kernel NULL pointer dereference at 000000000000002c (IP: iget5_locked+0x9e/0x1f0)
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1838982 Title: unable to handle kernel NULL pointer dereference at 002c (IP: iget5_locked+0x9e/0x1f0) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: Crash happens during the setup (dpkg) phase of sbuild using a overlayfs based chroot with the current bionic-proposed kernel (4.15.0-56-generic #62-Ubuntu). [25553.379381] ? ovl_get_origin_fh+0x23/0x150 [overlay] [25553.379386] ? ovl_inode_test+0x20/0x20 [overlay] [25553.379390] ? ovl_lock_rename_workdir+0x50/0x50 [overlay] [25553.379396] ovl_get_inode+0xa2/0x450 [overlay] [25553.379401] ovl_lookup+0x275/0x760 [overlay] [25553.379406] lookup_slow+0xab/0x170 [25553.379409] ? lookup_slow+0xab/0x170 [25553.379413] walk_component+0x1c3/0x470 [25553.379416] ? path_init+0x177/0x2f0 [25553.379419] path_lookupat+0x84/0x1f0 [25553.379423] ? __put_cred+0x3d/0x50 [25553.379426] ? revert_creds+0x2f/0x40 [25553.379429] filename_lookup+0xb6/0x190 [25553.379434] ? __check_object_size+0xaf/0x1b0 [25553.379438] user_path_at_empty+0x36/0x40 [25553.379441] ? user_path_at_empty+0x36/0x40 [25553.379444] SyS_chown+0x4d/0xe0 [25553.379449] do_syscall_64+0x73/0x130 [25553.379453] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 SRU justication: = [Impact] Crash happens during the setup (dpkg) phase of sbuild using a overlayfs based chroot with the current bionic-proposed kernel (4.15.0-56-generic #62-Ubuntu). [Fix] Fix protential NULL in overlay fs. [Test] Verified on fs test and dpkg installation on overlayfs. [Regression Potential] Low, remove regression of previous bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1838982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859538] Re: Harrison Peak wifi / BT support
** No longer affects: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859538 Title: Harrison Peak wifi / BT support Status in HWE Next: New Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: HrP2 will be supported in CML/TGL platform. Target Release: 20.04 Target Kernel: 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem
** Tags removed: somerville ** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850089 Title: iwlwifi fails with linux-image-4.15.0-1059-oem Status in OEM Priority Project: New Status in backport-iwlwifi-dkms package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: With the linux-image-4.15.0-1059-oem kernel, wifi does not work at all on my Precision 7540 laptop (Intel ax200 wifi) This is a regression from 4.15.0-1057 to -1059. dmesg shows repeated crashes: [ 59.582277] [ cut here ] [ 59.582368] WARNING: CPU: 13 PID: 189 at /var/lib/dkms/oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10/1.0/build/net/mac80211/scan.c:376 __ieee80211_scan_completed+0x19f/0x3d0 [mac80211] [ 59.582369] Modules linked in: rfcomm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc vmnet(OE) vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs snd_hda_codec_hdmi overlay snd_hda_codec_realtek snd_hda_codec_generic joydev hid_multitouch cmac dell_rbtn bnep binfmt_misc nls_iso8859_1 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core btusb btrtl videodev btbcm btintel media bluetooth ecdh_generic nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp dell_wmi dell_laptop dell_smbios dcdbas wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt mxm_wmi xt_addrtype dell_smm_hwmon [ 59.582436] intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw idma64 virt_dma iwlmvm(OE) mac80211(OE) iwlwifi(OE) cfg80211(OE) compat(OE) rtsx_pci_ms memstick snd_hda_intel nf_conntrack_ipv4 nf_defrag_ipv4 snd_hda_codec xt_conntrack snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq mei_me mei snd_seq_device snd_timer snd intel_lpss_pci soundcore ucsi_acpi intel_lpss processor_thermal_device typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal int340x_thermal_zone dell_smo8800 wmi int3400_thermal mac_hid intel_hid acpi_pad acpi_thermal_rel sparse_keymap nvidia_uvm(OE) sch_fq_codel ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp [ 59.582501] nf_nat nf_conntrack_ftp nf_conntrack ib_iser rdma_cm iw_cm ib_cm ib_core iptable_filter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log nvidia_drm(POE) nvidia_modeset(POE) i915 [ 59.582550] ieee80211 phy0: Hardware restart was requested [ 59.582552] crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) rtsx_pci_sdmmc pcbc i2c_algo_bit aesni_intel e1000e drm_kms_helper aes_x86_64 crypto_simd glue_helper syscopyarea ptp sysfillrect cryptd sysimgblt pps_core rtsx_pci thunderbolt fb_sys_fops ahci ipmi_devintf drm libahci ipmi_msghandler i2c_hid hid video [ 59.582588] CPU: 13 PID: 189 Comm: kworker/u32:2 Tainted: PW OE 4.15.0-1059-oem #68-Ubuntu [ 59.582590] Hardware name: Dell Inc. Precision 7540/0CYJDT, BIOS 1.1.3 06/21/2019 [ 59.582618] Workqueue: phy0 ieee80211_scan_work [mac80211] [ 59.582644] RIP: 0010:__ieee80211_scan_completed+0x19f/0x3d0 [mac80211] [ 59.582647] RSP: 0018:b2f5c3bd7de8 EFLAGS: 00010282 [ 59.582650] RAX: 0024 RBX: c2390c30 RCX: [ 59.582652] RDX: RSI: 92043bd56498 RDI: 92043bd56498 [ 59.582654] RBP: b2f5c3bd7e18 R08: 052c R09: 0004 [ 59.582655] R10: R11: 0001 R12: 92042a0a0f80 [ 59.582657] R13: 0001 R14: R15: [ 59.582660] FS: () GS:92043bd4() knlGS: [ 59.582662] CS: 0010 DS: ES: CR0: 80050033 [ 59.582664] CR2: 5558ff22b668 CR3: 00037ae0a004 CR4: 003606e0 [ 59.582666] DR0: DR1: DR2: [ 59.582667] DR3: DR6: fffe0ff0 DR7: 0400 [ 59.582669] Call Trace: [ 59.582678] ? __switch_to_asm+0x41/0x70 [ 59.582703] ieee80211_scan_work+0xf4/0x4b0 [mac80211] [ 59.582710] process_one_work+0x1de/0x420 [ 59.582715] worker_thread+0x32/0x410 [ 59.582719] kthread+0x121/0x140 [ 59.582722] ? process_one_work+0x420/0x420 [ 59.5
[Kernel-packages] [Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850089 Title: iwlwifi fails with linux-image-4.15.0-1059-oem Status in OEM Priority Project: New Status in backport-iwlwifi-dkms package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: With the linux-image-4.15.0-1059-oem kernel, wifi does not work at all on my Precision 7540 laptop (Intel ax200 wifi) This is a regression from 4.15.0-1057 to -1059. dmesg shows repeated crashes: [ 59.582277] [ cut here ] [ 59.582368] WARNING: CPU: 13 PID: 189 at /var/lib/dkms/oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10/1.0/build/net/mac80211/scan.c:376 __ieee80211_scan_completed+0x19f/0x3d0 [mac80211] [ 59.582369] Modules linked in: rfcomm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc vmnet(OE) vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs snd_hda_codec_hdmi overlay snd_hda_codec_realtek snd_hda_codec_generic joydev hid_multitouch cmac dell_rbtn bnep binfmt_misc nls_iso8859_1 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core btusb btrtl videodev btbcm btintel media bluetooth ecdh_generic nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp dell_wmi dell_laptop dell_smbios dcdbas wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt mxm_wmi xt_addrtype dell_smm_hwmon [ 59.582436] intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw idma64 virt_dma iwlmvm(OE) mac80211(OE) iwlwifi(OE) cfg80211(OE) compat(OE) rtsx_pci_ms memstick snd_hda_intel nf_conntrack_ipv4 nf_defrag_ipv4 snd_hda_codec xt_conntrack snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq mei_me mei snd_seq_device snd_timer snd intel_lpss_pci soundcore ucsi_acpi intel_lpss processor_thermal_device typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal int340x_thermal_zone dell_smo8800 wmi int3400_thermal mac_hid intel_hid acpi_pad acpi_thermal_rel sparse_keymap nvidia_uvm(OE) sch_fq_codel ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp [ 59.582501] nf_nat nf_conntrack_ftp nf_conntrack ib_iser rdma_cm iw_cm ib_cm ib_core iptable_filter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log nvidia_drm(POE) nvidia_modeset(POE) i915 [ 59.582550] ieee80211 phy0: Hardware restart was requested [ 59.582552] crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) rtsx_pci_sdmmc pcbc i2c_algo_bit aesni_intel e1000e drm_kms_helper aes_x86_64 crypto_simd glue_helper syscopyarea ptp sysfillrect cryptd sysimgblt pps_core rtsx_pci thunderbolt fb_sys_fops ahci ipmi_devintf drm libahci ipmi_msghandler i2c_hid hid video [ 59.582588] CPU: 13 PID: 189 Comm: kworker/u32:2 Tainted: PW OE 4.15.0-1059-oem #68-Ubuntu [ 59.582590] Hardware name: Dell Inc. Precision 7540/0CYJDT, BIOS 1.1.3 06/21/2019 [ 59.582618] Workqueue: phy0 ieee80211_scan_work [mac80211] [ 59.582644] RIP: 0010:__ieee80211_scan_completed+0x19f/0x3d0 [mac80211] [ 59.582647] RSP: 0018:b2f5c3bd7de8 EFLAGS: 00010282 [ 59.582650] RAX: 0024 RBX: c2390c30 RCX: [ 59.582652] RDX: RSI: 92043bd56498 RDI: 92043bd56498 [ 59.582654] RBP: b2f5c3bd7e18 R08: 052c R09: 0004 [ 59.582655] R10: R11: 0001 R12: 92042a0a0f80 [ 59.582657] R13: 0001 R14: R15: [ 59.582660] FS: () GS:92043bd4() knlGS: [ 59.582662] CS: 0010 DS: ES: CR0: 80050033 [ 59.582664] CR2: 5558ff22b668 CR3: 00037ae0a004 CR4: 003606e0 [ 59.582666] DR0: DR1: DR2: [ 59.582667] DR3: DR6: fffe0ff0 DR7: 0400 [ 59.582669] Call Trace: [ 59.582678] ? __switch_to_asm+0x41/0x70 [ 59.582703] ieee80211_scan_work+0xf4/0x4b0 [mac80211] [ 59.582710] process_one_work+0x1de/0x420 [ 59.582715] worker_thread+0x32/0x410
[Kernel-packages] [Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: In Progress Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: In Progress Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Upstream found a regression[1] with the new patch in #128, Jeremy will review and re-test the solution in focal before asking for sponsorship. [1] Multiple regressions in multi-user environments since 3.36.2 (#602) · Issues · GNOME / gdm · GitLab - https://gitlab.gnome.org/GNOME/gdm/-/issues/602 ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #602 https://gitlab.gnome.org/GNOME/gdm/-/issues/602 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Triaged Status in gdm3 package in Ubuntu: In Progress Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash Upgrad
[Kernel-packages] [Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio
** Tags added: oem-priority timbuktu ** Tags added: originate-from-1889531 ** No longer affects: oem-priority -- 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/1867704 Title: alsa/hdmi: support nvidia mst hdmi/dp audio Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Focal: Fix Committed Bug description: This is the justification for focal: This patchset will introduce a big change on hda_jack and hda_hdmi, So I sent the patcheset to oem-b 4 months ago. After 4 months of running oem-b kernel, there is no any regression reported on this patchset, now I am backporting the patchset to our focal kernel since our oem project is waiting for the patchset to be landed to ubuntu 5.4 kernel ASAP. This patchset are already merged to mainline kernel 5.5-rc and 5.6-rc, so there is no need to send the patchset to oem-5.6 or groovy kernel. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2, users can't find the hdmi audio entry in the gnome-sound-setting. [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work, and check other output/input devices like headphone, microphone, they all worked as well as before. [Regression Risk] one regression possibility is the audio jacks (including analogue and hdmi) can't work anymore, that means after users plug a headphone, headset, hdmi monitor or microphone to the audio jacks or hdmi connectors, the audio driver can't detect the plugging event. But regression's possibility is very low: - this patchset was already applied to oem-b kernel for 4 months, and oem projects didn't report any regression on the patchset - I tested the testing focal kernel with this patchset on many machines, includes a dell hda audio machine, a dell dmic machine, a Lenovo I+N hda audio machine, a lenovo I+N dmic machine, a lenovo I hda audio machine, a lenovo amd hda audio machine. The audio on them all worked as well as before. This is the justification for oem-b Drop the B, so far only need to merge this patchset to OEM-B first, After the patchset is widely verified with oem-b kernel, I send the patchset to B and F then. This patchset will add support of mst audio for nvidia hdmi/dp, this patchset changes lots of common code on hda_jack and hdmi codec, so it is not easy to say it is 100% safe for other machines, but our oem project needs this patchset to be backported to ubuntu kernel, because the tight sechdule of oem project, we backport this patchset to B and OEM-B first, if the hdmi audio works well for a period of time after this patchset is merged, I will backport this patchset to focal, maybe eoan as well. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2 [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work. [Regression Risk] Low, those patches come from mainline kernel, I have tested those patches on the machiens with or without nvidia hdmi, and on the machines with or without docks, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1867704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
** Tags added: originate-from-1879213 sutton ** Tags added: originate-from-1879232 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: In Progress Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: In Progress Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883065] Re: Dell Latitude/Precision, sig=0x806ec/20090609: Linux hangs without plugged in power cable
** Tags added: oem-priority ** Also affects: oem-priority 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/1883065 Title: Dell Latitude/Precision, sig=0x806ec/20090609: Linux hangs without plugged in power cable Status in OEM Priority Project: New Status in intel-microcode package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Already present reported in project *dell-sputnik*. (Note, it happened here also without suspend/resume.): 1. https://bugs.launchpad.net/dell-sputnik/+bug/1661741 2. Quote from https://bugs.launchpad.net/dell-sputnik/+bug/1661741/comments/26: > A similar bug affects several Dell laptop models: > - Dell 5480/5488 : > https://bugs.launchpad.net/dell-sputnik/+bug/1866343 > - Dell E5470 : > https://bugs.launchpad.net/dell-sputnik/+bug/1661741 > (Note that the bug https://bugs.launchpad.net/dell-sputnik/+bug/1661741 is not fixed; it has been changed, by error, to fixed. Please, it will be nice if somebody can change the status to "confirmed") > - Dell 7740 : > https://bugs.launchpad.net/dell-sputnik/+bug/1871491 > > I suppose that the bug can also affect Dell precision 7730 After experiencing this already on the Dell Latitude 5480/5488 (https://bugs.launchpad.net/dell-sputnik/+bug/1866343), we have seen this now too with the Dell Precision 3540 (with dedicated AMD graphics card). Without the power cord plugged in, the system started fine, then updating packages, including the Linux kernel, turning the system off, and right back on, it went to GRUB, and GRUB was able to load Linux and initrd, and starting Linux it hung. Num lock key didn’t respond (but also didn’t blink – no idea if this should work), and Ctrl + Alt + Del didn’t work either. So, the system had to be powered off by pressing the power button for some (ten(?)) seconds. Subsequent tries didn’t help, until we remembered the issues with the other device, and plugging in the power cord fixed it. With the power cable unplugged, it didn’t boot. The state of the connected power cable only mattered, when starting the Linux kernel. That means, plugging it in, when GRUB was active, the system booted. Removing the cable, when GRUB was running, Linux hung. I tried to get Linux messages, but `debug nomodeset earlyprintk=efi` didn’t get Linux to output any messages. ### Workarounds ### I was able to get Linux booting by adding either one of the following Linux kernel parameters. 1. `maxcpus=1` (once it started with `maxcpus=2`) 2. `nosmp` 2. `acpi=off` 3. `nolapic` In this state, there was only one CPU online. Trying to bring one more online, the system always froze instantly. echo 1 | sudo tee /sys/devices/system/cpu/cpu1/online (Nothing in pstore either.) (Where maxcpus=2` worked, we were able to bring a third CPU online, but the system froze when trying the fourth.) ### Reproducibilty ### Letting the system sit over night, and trying again in the morning, unfortunately, we did *not* test without a power cable plugged in, as we had an idea to test the non-USB-Type-C power cable. With that the system started. Powering the system off, and unplugging the cable, the system booted without issues. So something changed. We weren’t able to get it into a state, where it doesn’t boot in the last hour, but we would like this investigated, as we are giving these systems to our users. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1883065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875263] Re: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan
The microphone is broken on the certfieid Dell Inspiron 7591, Dell Inspiron 7590, and Dell Inspiron 3590. due to missing this new firmware. We need to verify and land the solution ASAP. ** Changed in: linux-firmware (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux-firmware (Ubuntu) Importance: High => Critical ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1875263 Title: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: [Impact] some ubuntu eoan/bionic users reported that the audio driver failed to initialize, then the audio didn't work. I checked the dmesg, found the sof driver planed to load sof-cfl.ri, but there is no this firmware under eoan or bionic. [Fix] I consulted with Intel audio team, they told me that the coffeelake platform could share the firmware with cnl/whl platoforms, so we could build a symbol link sof-cfl->sof-cnl. [Test Case] A couple of ubuntu users already tested it on Dell and Asus coffeelake laptops, it worked well. [Regression Risk] Low, users already tested it, and Intel audio team confirmed it is safe. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1875263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875263] Re: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1875263 Title: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: [Impact] some ubuntu eoan/bionic users reported that the audio driver failed to initialize, then the audio didn't work. I checked the dmesg, found the sof driver planed to load sof-cfl.ri, but there is no this firmware under eoan or bionic. [Fix] I consulted with Intel audio team, they told me that the coffeelake platform could share the firmware with cnl/whl platoforms, so we could build a symbol link sof-cfl->sof-cnl. [Test Case] A couple of ubuntu users already tested it on Dell and Asus coffeelake laptops, it worked well. [Regression Risk] Low, users already tested it, and Intel audio team confirmed it is safe. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1875263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884940] Re: after login to gnome, kern.log slowly fills with snd_hda_intel 0000:00:1f.3: No response from codec
** Tags added: beaver-osp1-melisa ** Tags added: oem-priority ** Also affects: oem-priority 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/1884940 Title: after login to gnome, kern.log slowly fills with snd_hda_intel :00:1f.3: No response from codec Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: Laptop : Dell XPS 2020 9300 Pre-loaded with Ubuntu 18.04 LTS Latest BIOS, latest available kernel, all updates applied linux kernel 5.0.0-1059-oem-osp1 After I log to Gnome, the kern.log fills itself with lines reporting this : Jun 24 14:46:22 asgard kernel: [ 158.134245] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2063b000 One per second. This lasts 10 to 15 seconds. Then, I see some lines but I do not know if they are related to this : Jun 24 14:47:08 asgard kernel: [ 203.874519] ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x0003D) is beyond end of object (length 0x10) (20181213/exoparg2-396) Jun 24 14:47:08 asgard kernel: [ 203.874538] No Local Variables are initialized for Method [GINF] Jun 24 14:47:08 asgard kernel: [ 203.874539] Initialized Arguments for Method [GINF]: (2 arguments defined for method invocation) Jun 24 14:47:08 asgard kernel: [ 203.874540] Arg0: 69cda4c2 Integer 003D Jun 24 14:47:08 asgard kernel: [ 203.874543] Arg1: 806e1ac9 Integer Jun 24 14:47:08 asgard kernel: [ 203.874546] ACPI Error: Method parse/execution failed \_SB.GINF, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874550] ACPI Error: Method parse/execution failed \_SB.GADR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874553] ACPI Error: Method parse/execution failed \_SB.SGOV, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874556] ACPI Error: Method parse/execution failed \_SB.CGWR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874559] ACPI Error: Method parse/execution failed \_SB.TBFP, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874562] ACPI Error: Method parse/execution failed \_SB.WMTF.WMTF, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:09 asgard kernel: [ 204.515539] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20278103 Jun 24 14:47:09 asgard kernel: [ 204.515545] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -11 Then it scrolls very quickly and I get a huge amount of "hsw_power_well_enable" No idea if this is related to the messages with the sound card. Those "hsw_power_well_enable" things are also/maybe/no idea related to another reported bug : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878670 Jun 24 14:47:09 asgard kernel: [ 205.219410] [ cut here ] Jun 24 14:47:09 asgard kernel: [ 205.219413] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) Jun 24 14:47:09 asgard kernel: [ 205.219489] WARNING: CPU: 6 PID: 2794 at /build/linux-oem-osp1-cysXhs/linux-oem-osp1-5.0.0/drivers/gpu/drm/i915/intel_runtime_pm.c:308 hsw_wait_for_power_well_enable.isra.8+0x4c/0x50 [i915] Jun 24 14:47:09 asgard kernel: [ 205.219489] Modules linked in: ccm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb videobuf2_common btrtl btbcm btintel videodev bluetooth media ecdh_generic hid_multitouch 8250_dw snd_hda_codec_hdmi dell_laptop arc4 intel_rapl x86_pkg_temp_thermal sof_pci_dev nls_iso8859_1 intel_powerclamp snd_sof_intel_hda_common coretemp snd_soc_hdac_hda snd_sof_intel_hda snd_sof_xtensa_dsp kvm_intel snd_sof snd_hda_codec_realtek snd_hda_ext_core snd_hda_codec_generic snd_soc_acpi_intel_match ledtrig_audio snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core crct10dif_pclmul snd_hwdep crc32_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq aesni_intel dell_wmi dell_smbios iwlmvm aes_x86_64 crypto_simd cryptd glue_helper intel_cstate input_leds joydev dcdbas snd_seq_device intel_rapl_perf snd_timer mac80211 serio_raw wmi_bmof intel_wmi_thunderbolt dell_wmi_descriptor Jun 24 14:47:09 asgard kernel: [ 205.219508] iwlwifi snd soundcore hid_sensor_als hid_sensor_trigger rtsx_pci_ms industrialio_triggered_buffer kfifo_buf mei_me hid_sensor_iio_common idma64 virt_dma cfg80211 memstick mei industrialio intel_lpss_pci intel_lpss ucsi_acpi typec_ucsi typec int3403_thermal int340x_thermal_zone mac_hid acpi_pad intel_hid int3400_thermal sp
[Kernel-packages] [Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)
** Tags added: beaver-osp1-melisa ** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2) Status in OEM Priority Project: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884940] Re: after login to gnome, kern.log slowly fills with snd_hda_intel 0000:00:1f.3: No response from codec
** Tags removed: disco ** 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/1884940 Title: after login to gnome, kern.log slowly fills with snd_hda_intel :00:1f.3: No response from codec Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: Laptop : Dell XPS 2020 9300 Pre-loaded with Ubuntu 18.04 LTS Latest BIOS, latest available kernel, all updates applied linux kernel 5.0.0-1059-oem-osp1 After I log to Gnome, the kern.log fills itself with lines reporting this : Jun 24 14:46:22 asgard kernel: [ 158.134245] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2063b000 One per second. This lasts 10 to 15 seconds. Then, I see some lines but I do not know if they are related to this : Jun 24 14:47:08 asgard kernel: [ 203.874519] ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x0003D) is beyond end of object (length 0x10) (20181213/exoparg2-396) Jun 24 14:47:08 asgard kernel: [ 203.874538] No Local Variables are initialized for Method [GINF] Jun 24 14:47:08 asgard kernel: [ 203.874539] Initialized Arguments for Method [GINF]: (2 arguments defined for method invocation) Jun 24 14:47:08 asgard kernel: [ 203.874540] Arg0: 69cda4c2 Integer 003D Jun 24 14:47:08 asgard kernel: [ 203.874543] Arg1: 806e1ac9 Integer Jun 24 14:47:08 asgard kernel: [ 203.874546] ACPI Error: Method parse/execution failed \_SB.GINF, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874550] ACPI Error: Method parse/execution failed \_SB.GADR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874553] ACPI Error: Method parse/execution failed \_SB.SGOV, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874556] ACPI Error: Method parse/execution failed \_SB.CGWR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874559] ACPI Error: Method parse/execution failed \_SB.TBFP, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874562] ACPI Error: Method parse/execution failed \_SB.WMTF.WMTF, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:09 asgard kernel: [ 204.515539] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20278103 Jun 24 14:47:09 asgard kernel: [ 204.515545] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -11 Then it scrolls very quickly and I get a huge amount of "hsw_power_well_enable" No idea if this is related to the messages with the sound card. Those "hsw_power_well_enable" things are also/maybe/no idea related to another reported bug : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878670 Jun 24 14:47:09 asgard kernel: [ 205.219410] [ cut here ] Jun 24 14:47:09 asgard kernel: [ 205.219413] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) Jun 24 14:47:09 asgard kernel: [ 205.219489] WARNING: CPU: 6 PID: 2794 at /build/linux-oem-osp1-cysXhs/linux-oem-osp1-5.0.0/drivers/gpu/drm/i915/intel_runtime_pm.c:308 hsw_wait_for_power_well_enable.isra.8+0x4c/0x50 [i915] Jun 24 14:47:09 asgard kernel: [ 205.219489] Modules linked in: ccm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb videobuf2_common btrtl btbcm btintel videodev bluetooth media ecdh_generic hid_multitouch 8250_dw snd_hda_codec_hdmi dell_laptop arc4 intel_rapl x86_pkg_temp_thermal sof_pci_dev nls_iso8859_1 intel_powerclamp snd_sof_intel_hda_common coretemp snd_soc_hdac_hda snd_sof_intel_hda snd_sof_xtensa_dsp kvm_intel snd_sof snd_hda_codec_realtek snd_hda_ext_core snd_hda_codec_generic snd_soc_acpi_intel_match ledtrig_audio snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core crct10dif_pclmul snd_hwdep crc32_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq aesni_intel dell_wmi dell_smbios iwlmvm aes_x86_64 crypto_simd cryptd glue_helper intel_cstate input_leds joydev dcdbas snd_seq_device intel_rapl_perf snd_timer mac80211 serio_raw wmi_bmof intel_wmi_thunderbolt dell_wmi_descriptor Jun 24 14:47:09 asgard kernel: [ 205.219508] iwlwifi snd soundcore hid_sensor_als hid_sensor_trigger rtsx_pci_ms industrialio_triggered_buffer kfifo_buf mei_me hid_sensor_iio_common idma64 virt_dma cfg80211 memstick mei industrialio intel_lpss_pci intel_lpss ucsi_acpi typec_ucsi typec int3403_thermal int340x_thermal_zone mac_hid acpi_pad intel_hid int3400_thermal sparse_keymap acpi_tad acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_t
[Kernel-packages] [Bug 1884940] Re: after login to gnome, kern.log slowly fills with snd_hda_intel 0000:00:1f.3: No response from codec
@gilbert
We are not able to reproudce the issue using 5.0.0-1064-oem-osp1 kernel,
need more debug information from you using apport.
It seems you may have a permission problem with the your home folder, maybe you
can fix by running the following command
$ sudo chown -R $UID ${HOME}/.cache/apport
$ apport-collect 1884940
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Assignee: (unassigned) => Rex Tsai (chihchun)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884940
Title:
after login to gnome, kern.log slowly fills with snd_hda_intel
:00:1f.3: No response from codec
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
Laptop : Dell XPS 2020 9300
Pre-loaded with Ubuntu 18.04 LTS
Latest BIOS, latest available kernel, all updates applied
linux kernel 5.0.0-1059-oem-osp1
After I log to Gnome, the kern.log fills itself with lines reporting
this :
Jun 24 14:46:22 asgard kernel: [ 158.134245] snd_hda_intel
:00:1f.3: No response from codec, resetting bus: last
cmd=0x2063b000
One per second. This lasts 10 to 15 seconds.
Then, I see some lines but I do not know if they are related to this :
Jun 24 14:47:08 asgard kernel: [ 203.874519] ACPI Error:
AE_AML_PACKAGE_LIMIT, Index (0x0003D) is beyond end of object (length 0x10)
(20181213/exoparg2-396)
Jun 24 14:47:08 asgard kernel: [ 203.874538] No Local Variables are
initialized for Method [GINF]
Jun 24 14:47:08 asgard kernel: [ 203.874539] Initialized Arguments for
Method [GINF]: (2 arguments defined for method invocation)
Jun 24 14:47:08 asgard kernel: [ 203.874540] Arg0: 69cda4c2
Integer 003D
Jun 24 14:47:08 asgard kernel: [ 203.874543] Arg1: 806e1ac9
Integer
Jun 24 14:47:08 asgard kernel: [ 203.874546] ACPI Error: Method
parse/execution failed \_SB.GINF, AE_AML_PACKAGE_LIMIT (20181213/psparse-531)
Jun 24 14:47:08 asgard kernel: [ 203.874550] ACPI Error: Method
parse/execution failed \_SB.GADR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531)
Jun 24 14:47:08 asgard kernel: [ 203.874553] ACPI Error: Method
parse/execution failed \_SB.SGOV, AE_AML_PACKAGE_LIMIT (20181213/psparse-531)
Jun 24 14:47:08 asgard kernel: [ 203.874556] ACPI Error: Method
parse/execution failed \_SB.CGWR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531)
Jun 24 14:47:08 asgard kernel: [ 203.874559] ACPI Error: Method
parse/execution failed \_SB.TBFP, AE_AML_PACKAGE_LIMIT (20181213/psparse-531)
Jun 24 14:47:08 asgard kernel: [ 203.874562] ACPI Error: Method
parse/execution failed \_SB.WMTF.WMTF, AE_AML_PACKAGE_LIMIT
(20181213/psparse-531)
Jun 24 14:47:09 asgard kernel: [ 204.515539] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20278103
Jun 24 14:47:09 asgard kernel: [ 204.515545] snd_hda_codec_hdmi hdaudioC0D2:
Unable to sync register 0x2f8100. -11
Then it scrolls very quickly and I get a huge amount of
"hsw_power_well_enable"
No idea if this is related to the messages with the sound card.
Those "hsw_power_well_enable" things are also/maybe/no idea related to
another reported bug :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878670
Jun 24 14:47:09 asgard kernel: [ 205.219410] [ cut here
]
Jun 24 14:47:09 asgard kernel: [ 205.219413]
WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) *
2)), (0x1 << ((pw_idx) * 2)), 1))
Jun 24 14:47:09 asgard kernel: [ 205.219489] WARNING: CPU: 6 PID: 2794 at
/build/linux-oem-osp1-cysXhs/linux-oem-osp1-5.0.0/drivers/gpu/drm/i915/intel_runtime_pm.c:308
hsw_wait_for_power_well_enable.isra.8+0x4c/0x50 [i915]
Jun 24 14:47:09 asgard kernel: [ 205.219489] Modules linked in: ccm cmac
bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb
videobuf2_common btrtl btbcm btintel videodev bluetooth media ecdh_generic
hid_multitouch 8250_dw snd_hda_codec_hdmi dell_laptop arc4 intel_rapl
x86_pkg_temp_thermal sof_pci_dev nls_iso8859_1 intel_powerclamp
snd_sof_intel_hda_common coretemp snd_soc_hdac_hda snd_sof_intel_hda
snd_sof_xtensa_dsp kvm_intel snd_sof snd_hda_codec_realtek snd_hda_ext_core
snd_hda_codec_generic snd_soc_acpi_intel_match ledtrig_audio snd_soc_acpi
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel
snd_intel_nhlt snd_hda_codec snd_hda_core crct10dif_pclmul snd_hwdep
crc32_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event
snd_rawmidi snd_seq aesni_intel dell_wmi dell_smbios iwlmvm aes_x86_64
crypto_simd cryptd glue_helper intel_cstate input_leds joydev dcdbas
snd_seq_device intel_rapl_perf snd_timer mac80211 serio_raw wmi_bmof
intel_wmi_thunderbolt dell_wmi_descriptor
Jun
[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Critical ** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Invalid Status in mutter source package in Focal: In Progress Status in nvidia-graphics-drivers-340 source package in Focal: New Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xs
[Kernel-packages] [Bug 1872916] Re: Support Intel Soundwire in 5.6-OEM Kernel 20.04
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1872916 Title: Support Intel Soundwire in 5.6-OEM Kernel 20.04 Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: [Impact] We have 2 Dell laptop modles which have soundwire codec on them, the audio can't work with the current kernel. [Fix] Intel github repo already supported the soundwire codec on those 2 machines, just backport the needed patches. [Test Case] Boot the kenrel on those 2 Dell soundwire machines, the audio could work. Boot the kernel on non-soundwire machines, the audio still work as before. [Regression Risk] Low, I have tested this patch Lenovo / Dell machines, they all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1872916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880623] Re: linux-firmware: generate the symbollink of sof-hda-generic-2ch/4ch.tplg for bionic
** Changed in: linux-firmware (Ubuntu) Assignee: Hui Wang (hui.wang) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1880623 Title: linux-firmware: generate the symbollink of sof-hda-generic- 2ch/4ch.tplg for bionic Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: Fix Released Bug description: [Impact] Users install the focal kernel on the bionic, the sof driver in focal kernel will fail to load the tplg files. [Fix] generate the symbollinks according to the requirement of sof driver in the focal kernel. [Test Case] booting the focal kernel on bionic, the sof driver could load the tplg successfully, and the audio works well. [Regression Risk] Low, the bionic kernel will still load sof-hda-generic.tplg, there is no any impact on the original bionic kernel + linux-firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1880623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
** Tags added: oem-priority originate-from-1896145 sutton ** Changed in: oem-priority Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem
Hi, Peter The backport-iwlwifi-dkms is the offical supported version, that we recommended you to use. Somehow, you receive an OLD image with a non-supported version of dkms. We would like to find out what was the version of the image you are using, could you run `ubuntu-report show`? or bto.xml in the recovery partition or provide the Serial Number of your machine (sudo dmidecode)? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850089 Title: iwlwifi fails with linux-image-4.15.0-1059-oem Status in OEM Priority Project: Incomplete Status in backport-iwlwifi-dkms package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: With the linux-image-4.15.0-1059-oem kernel, wifi does not work at all on my Precision 7540 laptop (Intel ax200 wifi) This is a regression from 4.15.0-1057 to -1059. dmesg shows repeated crashes: [ 59.582277] [ cut here ] [ 59.582368] WARNING: CPU: 13 PID: 189 at /var/lib/dkms/oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10/1.0/build/net/mac80211/scan.c:376 __ieee80211_scan_completed+0x19f/0x3d0 [mac80211] [ 59.582369] Modules linked in: rfcomm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc vmnet(OE) vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs snd_hda_codec_hdmi overlay snd_hda_codec_realtek snd_hda_codec_generic joydev hid_multitouch cmac dell_rbtn bnep binfmt_misc nls_iso8859_1 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core btusb btrtl videodev btbcm btintel media bluetooth ecdh_generic nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp dell_wmi dell_laptop dell_smbios dcdbas wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt mxm_wmi xt_addrtype dell_smm_hwmon [ 59.582436] intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw idma64 virt_dma iwlmvm(OE) mac80211(OE) iwlwifi(OE) cfg80211(OE) compat(OE) rtsx_pci_ms memstick snd_hda_intel nf_conntrack_ipv4 nf_defrag_ipv4 snd_hda_codec xt_conntrack snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq mei_me mei snd_seq_device snd_timer snd intel_lpss_pci soundcore ucsi_acpi intel_lpss processor_thermal_device typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal int340x_thermal_zone dell_smo8800 wmi int3400_thermal mac_hid intel_hid acpi_pad acpi_thermal_rel sparse_keymap nvidia_uvm(OE) sch_fq_codel ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp [ 59.582501] nf_nat nf_conntrack_ftp nf_conntrack ib_iser rdma_cm iw_cm ib_cm ib_core iptable_filter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log nvidia_drm(POE) nvidia_modeset(POE) i915 [ 59.582550] ieee80211 phy0: Hardware restart was requested [ 59.582552] crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) rtsx_pci_sdmmc pcbc i2c_algo_bit aesni_intel e1000e drm_kms_helper aes_x86_64 crypto_simd glue_helper syscopyarea ptp sysfillrect cryptd sysimgblt pps_core rtsx_pci thunderbolt fb_sys_fops ahci ipmi_devintf drm libahci ipmi_msghandler i2c_hid hid video [ 59.582588] CPU: 13 PID: 189 Comm: kworker/u32:2 Tainted: PW OE 4.15.0-1059-oem #68-Ubuntu [ 59.582590] Hardware name: Dell Inc. Precision 7540/0CYJDT, BIOS 1.1.3 06/21/2019 [ 59.582618] Workqueue: phy0 ieee80211_scan_work [mac80211] [ 59.582644] RIP: 0010:__ieee80211_scan_completed+0x19f/0x3d0 [mac80211] [ 59.582647] RSP: 0018:b2f5c3bd7de8 EFLAGS: 00010282 [ 59.582650] RAX: 0024 RBX: c2390c30 RCX: [ 59.582652] RDX: RSI: 92043bd56498 RDI: 92043bd56498 [ 59.582654] RBP: b2f5c3bd7e18 R08: 052c R09: 0004 [ 59.582655] R10: R11: 0001 R12: 92042a0a0f80 [ 59.582657] R13: 0001 R14: R15: [ 59.582660] FS: () GS:92043bd4() knlGS: [ 59.582662] CS: 0010 DS: ES: CR0: 80050033 [ 59.582664] CR2: 5558ff22b668 CR3: 00037ae0a004 CR4: 003606e0 [ 59.582666] DR0: DR1: DR2: [ 59.582667] DR3: DR6: fffe0ff0
[Kernel-packages] [Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem
** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: backport-iwlwifi-dkms (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850089 Title: iwlwifi fails with linux-image-4.15.0-1059-oem Status in OEM Priority Project: Incomplete Status in backport-iwlwifi-dkms package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: With the linux-image-4.15.0-1059-oem kernel, wifi does not work at all on my Precision 7540 laptop (Intel ax200 wifi) This is a regression from 4.15.0-1057 to -1059. dmesg shows repeated crashes: [ 59.582277] [ cut here ] [ 59.582368] WARNING: CPU: 13 PID: 189 at /var/lib/dkms/oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10/1.0/build/net/mac80211/scan.c:376 __ieee80211_scan_completed+0x19f/0x3d0 [mac80211] [ 59.582369] Modules linked in: rfcomm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc vmnet(OE) vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs snd_hda_codec_hdmi overlay snd_hda_codec_realtek snd_hda_codec_generic joydev hid_multitouch cmac dell_rbtn bnep binfmt_misc nls_iso8859_1 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core btusb btrtl videodev btbcm btintel media bluetooth ecdh_generic nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp dell_wmi dell_laptop dell_smbios dcdbas wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt mxm_wmi xt_addrtype dell_smm_hwmon [ 59.582436] intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw idma64 virt_dma iwlmvm(OE) mac80211(OE) iwlwifi(OE) cfg80211(OE) compat(OE) rtsx_pci_ms memstick snd_hda_intel nf_conntrack_ipv4 nf_defrag_ipv4 snd_hda_codec xt_conntrack snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq mei_me mei snd_seq_device snd_timer snd intel_lpss_pci soundcore ucsi_acpi intel_lpss processor_thermal_device typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal int340x_thermal_zone dell_smo8800 wmi int3400_thermal mac_hid intel_hid acpi_pad acpi_thermal_rel sparse_keymap nvidia_uvm(OE) sch_fq_codel ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp [ 59.582501] nf_nat nf_conntrack_ftp nf_conntrack ib_iser rdma_cm iw_cm ib_cm ib_core iptable_filter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log nvidia_drm(POE) nvidia_modeset(POE) i915 [ 59.582550] ieee80211 phy0: Hardware restart was requested [ 59.582552] crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) rtsx_pci_sdmmc pcbc i2c_algo_bit aesni_intel e1000e drm_kms_helper aes_x86_64 crypto_simd glue_helper syscopyarea ptp sysfillrect cryptd sysimgblt pps_core rtsx_pci thunderbolt fb_sys_fops ahci ipmi_devintf drm libahci ipmi_msghandler i2c_hid hid video [ 59.582588] CPU: 13 PID: 189 Comm: kworker/u32:2 Tainted: PW OE 4.15.0-1059-oem #68-Ubuntu [ 59.582590] Hardware name: Dell Inc. Precision 7540/0CYJDT, BIOS 1.1.3 06/21/2019 [ 59.582618] Workqueue: phy0 ieee80211_scan_work [mac80211] [ 59.582644] RIP: 0010:__ieee80211_scan_completed+0x19f/0x3d0 [mac80211] [ 59.582647] RSP: 0018:b2f5c3bd7de8 EFLAGS: 00010282 [ 59.582650] RAX: 0024 RBX: c2390c30 RCX: [ 59.582652] RDX: RSI: 92043bd56498 RDI: 92043bd56498 [ 59.582654] RBP: b2f5c3bd7e18 R08: 052c R09: 0004 [ 59.582655] R10: R11: 0001 R12: 92042a0a0f80 [ 59.582657] R13: 0001 R14: R15: [ 59.582660] FS: () GS:92043bd4() knlGS: [ 59.582662] CS: 0010 DS: ES: CR0: 80050033 [ 59.582664] CR2: 5558ff22b668 CR3: 00037ae0a004 CR4: 003606e0 [ 59.582666] DR0: DR1: DR2: [ 59.582667] DR3: DR6: fffe0ff0 DR7: 0400 [ 59.582669] Call Trace: [ 59.582678] ? __switch_to_asm+0x41/0x70 [ 59.582703] ieee80211_scan_work+0xf4/0x4b0 [mac80211] [ 59.582710] process_one_work+0x1de/0x420 [ 59.582715] worker_thread+0x32
[Kernel-packages] [Bug 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1849947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900883] Re: Add new iwlwifi firmware to solve AX201 hang
The change is proposed on - [PATCH 0/1] Add new iwlwifi firmware to solve AX201 hang - https://lists.ubuntu.com/archives/kernel- team/2020-October/114185.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1900883 Title: Add new iwlwifi firmware to solve AX201 hang Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Confirmed Bug description: [Impact] Intel AX201 firmware crashes or hardware RX ring buffer hangs after S3. [Fix] Use new firmware from linux-firmware.git can solve the issue. [Test] WiFi works for each cycle of 1000 S3 cycles. [Regression Potential] Both Focal 5.4 and OEM 5.6 kernel use this firmware, so it might regress current 5.4 users. I did a smoke test with this firmware on Focal 5.4, and I didn't see any regression. Instead of cherry-pick the commit, only add the firmware needed for AX201 to minimize the regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1900883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905591] Re: no brightness control after update from 450 to 455
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1905591 Title: no brightness control after update from 450 to 455 Status in OEM Priority Project: New Status in nvidia-graphics-drivers-455 package in Ubuntu: Triaged Bug description: On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] Updating to nvidia-driver-455 results in loss of brightness control. On boot, the laptop display brightness is somewhat less than fully bright and cannot be changed. The brightness up/down keys do pop up the gnome gui brightness widget, and /sys/class/backlight/nvidia_0/* values do change, but the actual display's brightness does not. Problem occurs with either version of nvidia-driver-455 (the archive or the ~graphics-drivers/PPA). Normal functionality returns if I downgrade to any version of nvidia-driver-450. Note also that manually applying this to /lib/systemd/system/nvidia-persistenced.service has no effect on the problem: https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5 Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux nvidia-driver-455: 455.38-0ubuntu0.18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1905591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
It seems the V3 patch[1] is merged[2]. Is that patch enough to address the problem we have? [1] [v3] PCI: vmd: Offset Client VMD MSI-X vectors - Patchwork - https://patchwork.kernel.org/project/linux-pci/patch/20200914190128.5114-1-jonathan.derr...@intel.com/ [2] PCI: vmd: Offset Client VMD MSI-X vectors · torvalds/linux@f6b7bb8 - https://github.com/torvalds/linux/commit/f6b7bb847ca821a8aaa1b6da10ee65311e6f15bf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1894778 Title: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [SRU Justification] [Impact] When booting with a certain platforms with boot disk attached to SATA bus behind Intel VMD controller, disk probing may fail with following error messages left in dmesg: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [Fix] Proposed kernel patch https://patchwork.kernel.org/patch/11758345/ [Test Case] Check dmesg/lsblk for disk probe. For pci MSI address, check lspci output: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee0 Data: When it fails, the address is fee0. And with a patched kernel: $ lspci -vvnn Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit- Address: fee01000 Data: [Regression Potential] Low. For previous NVMe based platforms, this patch brings no effective change for NVMe devices because they will still stay in fast-interrupt list. == Original Bug Description == When booting with root filesystem on sata disks under Intel VMD mode, following errors printed in dmesg and no disk is found, nor booting into it: [ 6.163286] ata1.00: qc timeout (cmd 0xec) [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 16.659284] ata1.00: qc timeout (cmd 0xec) [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 48.147294] ata1.00: qc timeout (cmd 0xec) [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) $ lspci ... 1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1894778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem
** Changed in: oem-priority Status: Incomplete => Won't Fix ** Changed in: oem-priority Assignee: Rex Tsai (chihchun) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850089 Title: iwlwifi fails with linux-image-4.15.0-1059-oem Status in OEM Priority Project: Won't Fix Status in backport-iwlwifi-dkms package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: With the linux-image-4.15.0-1059-oem kernel, wifi does not work at all on my Precision 7540 laptop (Intel ax200 wifi) This is a regression from 4.15.0-1057 to -1059. dmesg shows repeated crashes: [ 59.582277] [ cut here ] [ 59.582368] WARNING: CPU: 13 PID: 189 at /var/lib/dkms/oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10/1.0/build/net/mac80211/scan.c:376 __ieee80211_scan_completed+0x19f/0x3d0 [mac80211] [ 59.582369] Modules linked in: rfcomm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc vmnet(OE) vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs snd_hda_codec_hdmi overlay snd_hda_codec_realtek snd_hda_codec_generic joydev hid_multitouch cmac dell_rbtn bnep binfmt_misc nls_iso8859_1 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core btusb btrtl videodev btbcm btintel media bluetooth ecdh_generic nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp dell_wmi dell_laptop dell_smbios dcdbas wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt mxm_wmi xt_addrtype dell_smm_hwmon [ 59.582436] intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw idma64 virt_dma iwlmvm(OE) mac80211(OE) iwlwifi(OE) cfg80211(OE) compat(OE) rtsx_pci_ms memstick snd_hda_intel nf_conntrack_ipv4 nf_defrag_ipv4 snd_hda_codec xt_conntrack snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq mei_me mei snd_seq_device snd_timer snd intel_lpss_pci soundcore ucsi_acpi intel_lpss processor_thermal_device typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal int340x_thermal_zone dell_smo8800 wmi int3400_thermal mac_hid intel_hid acpi_pad acpi_thermal_rel sparse_keymap nvidia_uvm(OE) sch_fq_codel ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp [ 59.582501] nf_nat nf_conntrack_ftp nf_conntrack ib_iser rdma_cm iw_cm ib_cm ib_core iptable_filter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log nvidia_drm(POE) nvidia_modeset(POE) i915 [ 59.582550] ieee80211 phy0: Hardware restart was requested [ 59.582552] crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) rtsx_pci_sdmmc pcbc i2c_algo_bit aesni_intel e1000e drm_kms_helper aes_x86_64 crypto_simd glue_helper syscopyarea ptp sysfillrect cryptd sysimgblt pps_core rtsx_pci thunderbolt fb_sys_fops ahci ipmi_devintf drm libahci ipmi_msghandler i2c_hid hid video [ 59.582588] CPU: 13 PID: 189 Comm: kworker/u32:2 Tainted: PW OE 4.15.0-1059-oem #68-Ubuntu [ 59.582590] Hardware name: Dell Inc. Precision 7540/0CYJDT, BIOS 1.1.3 06/21/2019 [ 59.582618] Workqueue: phy0 ieee80211_scan_work [mac80211] [ 59.582644] RIP: 0010:__ieee80211_scan_completed+0x19f/0x3d0 [mac80211] [ 59.582647] RSP: 0018:b2f5c3bd7de8 EFLAGS: 00010282 [ 59.582650] RAX: 0024 RBX: c2390c30 RCX: [ 59.582652] RDX: RSI: 92043bd56498 RDI: 92043bd56498 [ 59.582654] RBP: b2f5c3bd7e18 R08: 052c R09: 0004 [ 59.582655] R10: R11: 0001 R12: 92042a0a0f80 [ 59.582657] R13: 0001 R14: R15: [ 59.582660] FS: () GS:92043bd4() knlGS: [ 59.582662] CS: 0010 DS: ES: CR0: 80050033 [ 59.582664] CR2: 5558ff22b668 CR3: 00037ae0a004 CR4: 003606e0 [ 59.582666] DR0: DR1: DR2: [ 59.582667] DR3: DR6: fffe0ff0 DR7: 0400 [ 59.582669] Call Trace: [ 59.582678] ? __switch_to_asm+0x41/0x70 [ 59.582703] ieee80211_scan_work+0xf4/0x4b0 [mac80211] [ 59.582710] process_one_work+0x1de/0x420 [ 59.582715]
[Kernel-packages] [Bug 1890257] Re: [RTX6000][20.04.01] The system always stops at "Initramfs unpacking failed: Decoding failed" after selecting "OEM installation" or "Ubuntu" option to run system ins
The NVIDIA RTX6000 is not supporetd by the nouveau, and should be supported when the users use the nvidia proprietary driver from ubuntu 3rd party drivers. The expected behavior would be - the user use "safe graphie" mode to install the system, and install "3rd party drivers." - reboot and the user should have the proprietary driver installed. we can lower the priority . ** Changed in: ubuntu Importance: Undecided => Low ** Package changed: ubuntu => linux ** Project changed: linux => linux (Ubuntu) ** Summary changed: - [RTX6000][20.04.01] The system always stops at "Initramfs unpacking failed: Decoding failed" after selecting "OEM installation" or "Ubuntu" option to run system installation + [RTX6000][20.04.01] RTX6000 is not supported by nouveau -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890257 Title: [RTX6000][20.04.01] RTX6000 is not supported by nouveau Status in linux package in Ubuntu: Confirmed Bug description: [Summary] The system always stop at "Initramfs unpacking failed: Decoding failed" after selecting "OEM install or Ubuntu option (20.04.01). The issue can be observed on the RTX6000, but Nvidia P620 cannot reproduce it. The issue might relate to the graphic driver. [Steps to reproduce] 1. Plug the USB key which has the 20.04.01 build 2. Power on the system 3. Select USB drive to launch the grub menu 4. Select "OEM installation" or "Ubuntu" option to run the installation 5. Check if the system can run the installation [Expected result] The system can run the installation properly [Actual result] The system always stops at "Initramfs unpacking failed: Decoding failed" after selecting "OEM installation" or "Ubuntu" option [Failure rate] 3/3 [Additional information] system-manufacturer: LENOVO system-product-name: P920 CPU: Intel(R) Xeon(R) Gold 6230N CPU @ 2.30GHz GPU: nVidia - 10de:1e30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Changed in: oem-priority 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: Triaged Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847193] Re: ath10k_pci: firmware crashed randomly (Qualcomm Atheros QCA6174 )
** Tags added: oem-priority -- 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/1847193 Title: ath10k_pci: firmware crashed randomly (Qualcomm Atheros QCA6174 ) Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: New Bug description: the wifi failed randomly, and it seems always happens with error message: " ath10k_pci :02:00.0: firmware crashed!" 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:143a] Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 14:52:39 2019 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux-firmware 1.173.9 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1057-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741166] Re: [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device
** Tags added: oem-priority -- 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/1741166 Title: [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Bug description: [Impact] QCA6174A XR can scan but can't pair with bt 4.0 device. [Fix] [0cf3:e010] is one of the QCA ROME family and should be listed in btusb driver. [Test Case] Applied the patch and can pair with bt 4.0 keyboard without any issue. [Regression Potential] Adding the device to the list won't have any regression potential. impacted tickets: LP: #1736330 LP: #1742849 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1741166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876066] Re: Support Intel TGL CPU on Focal
** Tags added: oem-priority ** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1876066 Title: Support Intel TGL CPU on Focal Status in OEM Priority Project: Fix Released Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Released Status in thermald source package in Groovy: Fix Released Bug description: [impact] thermald doesn't support Tiger Lake cpus [test case] run thermald on Tiger Lake cpu It can be checked by following command, and the patch works if it return "passed". $ systemctl is-active --quiet thermald && echo passed [regression potential] because TGL is not supported by current thermald, so thermald always inactive on TGL platform. This patch is to activate it. So, there's not potential regression. [scope] needed for F/G [original description] need the patch to support Intel TGL CPU on Focal https://github.com/intel/thermal_daemon/blob/master/src/thd_engine.cpp#L666 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1876066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781924] Re: Kernel wrong temperature reporting
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781924 Title: Kernel wrong temperature reporting Status in OEM Priority Project: New Status in linux package in Ubuntu: Expired Bug description: I'm having some thermal trouble since I've started using kernel >4.0.x with my new laptop. According to psensor and sensord, CPU temperature jumps above the 90C, stays there for around 1second, and goes back to 50C. All transitions happen in around 100ms. I've cleaned and re- applied thermal paste and checked the connections twice. More interestingly, this doesn't happen when the CPU is under heavy-load, but when it is waiting idly. Sometimes sensord reports the CPU temp has gone over the critical threshold of the CPU and device shuts down itself immediately. There is also Windows 10 installed as a dual boot and didn't see this problem on it when idle or under heavy load. Dmesg output is full of following warnings; [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled (total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu clock throttled (total events = 109) [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.297226] CPU4: Core temperature/speed normal [ 1282.297227] CPU5: Package temperature/speed normal [ 1282.297228] CPU0: Core temperature/speed normal [ 1282.297229] CPU1: Package temperature/speed normal [ 1282.297229] CPU0: Package temperature/speed normal [ 1282.297230] CPU4: Package temperature/speed normal [ 1282.297233] CPU3: Package temperature/speed normal [ 1282.297233] CPU7: Package temperature/speed normal [ 1282.297269] CPU2: Package temperature/speed normal [ 1282.297269] CPU6: Package temperature/speed normal Because of wrong temperature reporting, kernel throttles the CPU and reduces overall performance, which results in frustrating user experience. I've tried followings and find a temporary solution; - intel_pstate enabled, turbo-boost enabled > problem exists - intel_pstate enabled, turbo-boost disabled > problem frequency reduced - intel_pstate disabled, governor set to anythig other than powersave > problem exists - intel_pstate disabled, governor set to powersave > problem frequency reduced I'm suspicious about a kernel bug such as; - https://bugzilla.redhat.com/show_bug.cgi?id=924570 - https://bugzilla.redhat.com/show_bug.cgi?id=1317190 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: burak 1547 F...m pulseaudio /dev/snd/controlC0: burak 1547 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UNR NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash intel_pstate=disable vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-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/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UNR.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UNR dmi.board.vendor: AS
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Triaged Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux package in Arch Linux: New Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Sockets
[Kernel-packages] [Bug 1818881] Re: ath10k_pci crashing
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818881 Title: ath10k_pci crashing Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias: pci:v168Cd0040sv*sd*bc*sc*i* alias: pci:v168C
[Kernel-packages] [Bug 1817058] Re: Fix I219 doesn't get woken up after plugging ethernet cable
** Tags added: oem-priority -- 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/1817058 Title: Fix I219 doesn't get woken up after plugging ethernet cable Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Bug description: [Impact] Plugging ethernet cable doesn't work on new I219 after it runtime suspends to D3. [Fix] Intel confirms that it only supports D0, so disable runtime power management to prevent it from entering D3. [Test] Once the patch applied, the device always stays at D0, which doesn't have this problem. [Regression Potential] Low. This doesn't introduce any functional change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817058/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872351] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem: Killer 1435 Wireless-AC [1a56:143a]: Disabling wifi causes kernel warning in __sta_info_destroy_part2
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872351 Title: Qualcomm Atheros QCA6174 [168c:003e] Subsystem: Killer 1435 Wireless- AC [1a56:143a]: Disabling wifi causes kernel warning in __sta_info_destroy_part2 Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: I have multiple issues with wifi on my Dell XPS 9380. This error was triggered when I tried to disable my wifi. [ 3634.322471] [ cut here ] [ 3634.322524] WARNING: CPU: 3 PID: 1188 at net/mac80211/sta_info.c:1057 __sta_info_destroy_part2+0x14e/0x160 [mac80211] [ 3634.322525] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_hdmi dell_laptop snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_usb_audio ath10k_pci x86_pkg_temp_thermal snd_usbmidi_lib snd_seq_midi snd_hwdep snd_seq_midi_event ath10k_core intel_powerclamp coretemp cdc_ether snd_rawmidi usbnet btusb kvm_intel r8152 ath btrtl mii btbcm kvm snd_seq uvcvideo videobuf2_vmalloc btintel videobuf2_memops intel_cstate videobuf2_v4l2 joydev snd_seq_device snd_pcm dell_wmi intel_rapl_perf videobuf2_common bluetooth mac80211 dell_smbios videodev snd_timer dcdbas mc input_leds ecdh_generic ecc wmi_bmof snd dell_wmi_descriptor serio_raw intel_wmi_thunderbolt cfg80211 soundcore rtsx_pci_ms libarc4 memstick hid_multitouch processor_thermal_device ucsi_acpi typec_ucsi mei_me intel_rapl_common [ 3634.322564] intel_xhci_usb_role_switch mei typec intel_soc_dts_iosf intel_pch_thermal roles int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_pad intel_hid acpi_thermal_rel sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 mmc_block dm_crypt usbhid hid_generic crct10dif_pclmul crc32_pclmul rtsx_pci_sdmmc i915 ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_algo_bit glue_helper drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt i2c_i801 fb_sys_fops nvme_core drm intel_lpss_pci rtsx_pci intel_lpss idma64 i2c_hid virt_dma wmi hid pinctrl_sunrisepoint video pinctrl_intel [ 3634.322599] CPU: 3 PID: 1188 Comm: NetworkManager Tainted: G OE 5.4.0-21-generic #25-Ubuntu [ 3634.322600] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.12.1 12/11/2019 [ 3634.322633] RIP: 0010:__sta_info_destroy_part2+0x14e/0x160 [mac80211] [ 3634.322635] Code: 24 0c 01 00 00 00 0f 84 52 ff ff ff 45 31 c0 b9 01 00 00 00 4c 89 e2 48 89 de 4c 89 ef e8 0a a6 ff ff 85 c0 0f 84 34 ff ff ff <0f> 0b e9 2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 [ 3634.322636] RSP: 0018:a70c009c3918 EFLAGS: 00010282 [ 3634.322638] RAX: ff94 RBX: 9006104cc8c0 RCX: [ 3634.322640] RDX: 90061ba3c740 RSI: RDI: 900613a62f48 [ 3634.322641] RBP: a70c009c3938 R08: 90061e4d78c8 R09: 0004 [ 3634.322642] R10: R11: R12: 900613f28000 [ 3634.322643] R13: 900613a607a0 R14: 9006104cc8c0 R15: 900613a60d68 [ 3634.322644] FS: 7f596b396240() GS:90061e4c() knlGS: [ 3634.322645] CS: 0010 DS: ES: CR0: 80050033 [ 3634.322646] CR2: 0db00945f000 CR3: 000494824005 CR4: 003606e0 [ 3634.322647] Call Trace: [ 3634.322670] __sta_info_flush+0x128/0x180 [mac80211] [ 3634.322696] ieee80211_set_disassoc+0xc0/0x5f0 [mac80211] [ 3634.322719] ieee80211_mgd_deauth+0x104/0x490 [mac80211] [ 3634.322743] ieee80211_deauth+0x18/0x20 [mac80211] [ 3634.322782] cfg80211_mlme_deauth+0xb6/0x1e0 [cfg80211] [ 3634.322804] cfg80211_mlme_down+0x66/0x80 [cfg80211] [ 3634.322823] cfg80211_disconnect+0x127/0x1e0 [cfg80211] [ 3634.322827] ? _raw_spin_unlock_bh+0x1e/0x20 [ 3634.322845] __cfg80211_leave+0x133/0x1b0 [cfg80211] [ 3634.322862] cfg80211_leave+0x2c/0x40 [cfg80211] [ 3634.322879] cfg80211_netdev_notifier_call+0x1b2/0x590 [cfg80211] [ 3634.322902] ? ath10k_warn.cold+0x1a/0x1f [ath10k_core] [ 3634.322911] ? ath10k_config_ps+0x52/0x70 [ath10k_core] [ 3634.322913] ? rtnl_is_locked+0x15/0x20 [ 3634.322917] ? inetdev_event+0x47/0x560 [ 3634.322919] ? skb_dequeue+0x5a/0x70 [ 3634.322923] notifier_call_chain+0x55/0x80 [ 3634.322925] raw_notifier_call_chain+0x16/0x20 [ 3634.322927] call_netdevice_notifiers_info+0x2e/0x60 [ 3634.322929] __dev_close_many+0x63/0x120 [ 3634.322931] dev_close_many+0x91/0x150 [ 3634.322933] dev_close.part.0+0x4a/0x70 [ 3634.322936] dev_close+0x18/0x20 [ 3634.322955] cfg80211_shutdown_all_interfaces+0x77/0xd0 [cfg80211] [ 3634.
[Kernel-packages] [Bug 1872034] Re: [Focal] No HDMI output through thunderbolt docking station
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872034 Title: [Focal] No HDMI output through thunderbolt docking station Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Bug description: I can find monitor in display list, but no output from it. Also, I can't switch to extend mode, it failed to apply the setting and switched back to mirror mode. [Steps] 1. Connect a thunderbolt docking station to thunderbolt port. 2. Connect HDMI monitor to HDMI port on the docking station. 3. Switch mode in display setting ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:44:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=98c0c28f-278e-442b-8fc9-6d663bacd68d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd01/08/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857496] Re: usb-audio: the mic can't record any sound after resume on Dell Dock WD19
** Tags added: oem-priority -- 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/1857496 Title: usb-audio: the mic can't record any sound after resume on Dell Dock WD19 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: 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: Fix Released Bug description: [Impact] There is a heaset jack on the dock, after resume, the mic on that jack can't record sound anymore, need to close the recording app then reopen that app to workaround this issue. [Fix] set the interface and EP, then the mic can record sound again. [Test Case] test the kernel with this patch, the mic can record sound after resume. [Regression Risk] Low, this quirk is specific to WD19 (usb vednor and device id). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847198] Re: amdgpu kernel module should be used instead of radeon on amd graphic
** Tags added: oem-priority -- 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/1847198 Title: amdgpu kernel module should be used instead of radeon on amd graphic Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in linux-oem package in Ubuntu: New Status in linux-oem source package in Bionic: New Bug description: there're some graphic be supported both on amdgpu and radeon. But somehow kernel might pick radeon instead of amdgpu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Oct 8 03:33:43 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-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 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/oem-priority/+bug/1847198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844798] Re: [SRU][OEM-B]UBUNTU: SAUCE: enable adjusting brightness on some samsung OLED panels
** Tags added: oem-priority -- 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/1844798 Title: [SRU][OEM-B]UBUNTU: SAUCE: enable adjusting brightness on some samsung OLED panels Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: SRU justification: [Impact] OLED backlight is not supported by the current kernel. brightness can't be adjusted. [Fix] Fix max brightness value; Follow samsung panel's spec to enable dpcd and support adjusting brightness on OLED. [Test] Verified on several laptops, backlight on and brightness is adjusted. [Regression Potential] Medium, change is limited to specific hardware feature. Verified on no dpcd support laptops, no regression found yet. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1844798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781924] Re: Kernel wrong temperature reporting
** Changed in: oem-priority Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781924 Title: Kernel wrong temperature reporting Status in OEM Priority Project: Won't Fix Status in linux package in Ubuntu: Expired Bug description: I'm having some thermal trouble since I've started using kernel >4.0.x with my new laptop. According to psensor and sensord, CPU temperature jumps above the 90C, stays there for around 1second, and goes back to 50C. All transitions happen in around 100ms. I've cleaned and re- applied thermal paste and checked the connections twice. More interestingly, this doesn't happen when the CPU is under heavy-load, but when it is waiting idly. Sometimes sensord reports the CPU temp has gone over the critical threshold of the CPU and device shuts down itself immediately. There is also Windows 10 installed as a dual boot and didn't see this problem on it when idle or under heavy load. Dmesg output is full of following warnings; [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled (total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu clock throttled (total events = 109) [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.297226] CPU4: Core temperature/speed normal [ 1282.297227] CPU5: Package temperature/speed normal [ 1282.297228] CPU0: Core temperature/speed normal [ 1282.297229] CPU1: Package temperature/speed normal [ 1282.297229] CPU0: Package temperature/speed normal [ 1282.297230] CPU4: Package temperature/speed normal [ 1282.297233] CPU3: Package temperature/speed normal [ 1282.297233] CPU7: Package temperature/speed normal [ 1282.297269] CPU2: Package temperature/speed normal [ 1282.297269] CPU6: Package temperature/speed normal Because of wrong temperature reporting, kernel throttles the CPU and reduces overall performance, which results in frustrating user experience. I've tried followings and find a temporary solution; - intel_pstate enabled, turbo-boost enabled > problem exists - intel_pstate enabled, turbo-boost disabled > problem frequency reduced - intel_pstate disabled, governor set to anythig other than powersave > problem exists - intel_pstate disabled, governor set to powersave > problem frequency reduced I'm suspicious about a kernel bug such as; - https://bugzilla.redhat.com/show_bug.cgi?id=924570 - https://bugzilla.redhat.com/show_bug.cgi?id=1317190 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: burak 1547 F...m pulseaudio /dev/snd/controlC0: burak 1547 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UNR NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash intel_pstate=disable vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-24-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/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UNR.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board
[Kernel-packages] [Bug 1839124] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1028:0310] BT advertising packet wakes up the system from S3 and suspend-to-idle
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839124 Title: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1028:0310] BT advertising packet wakes up the system from S3 and suspend-to-idle Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: A generic issue which happens on Intel BT(8087:0aaa) and Atheros BT(0cf3:e005)(0cf3:e007). Once the system has paired with BT4 devices(disconnected), the system will be waken up randomly from S3/s2idle while receiving advertising packet from any random BT4 devices in the environment which are even not paired/connected. By removing all previously paired BT4 devices(disconnected) from BT menu can fix this issue. The advertising packet could be none connectable undirected or connectable undirected. And the BT4 devices we found can reproduce this issue are 1. Microsoft Surface 1678 2. Logitech K375s 3. Microsoft Designer Mouse --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1539 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3300 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0FN010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3300 dmi.product.sku: 08BB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1839124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883670] Re: Disable IEC958 on HP Thunderbolt Dock
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1883670 Title: Disable IEC958 on HP Thunderbolt Dock Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] On HP Thunderbolt Dock, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Regression Potential] Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Released Status in dkms source package in Disco: Fix Released Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: Fix Released Status in linux-firmware source package in Focal: Invalid Bug description: Updated Description to match SRU requirements for bionic [Impact] linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks/source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. [Test Case] 1) On an Ubuntu 18.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. [Regression Potential] Very limited, as we are just adding a symlink from linux-firmware to the linux source package hook. this change has been available in Focal and Groovy without problem Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Invalid Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800413] Re: It can not use nvidia-settings to switch from the power saving mode to the performance mode
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1800413 Title: It can not use nvidia-settings to switch from the power saving mode to the performance mode Status in NVIDIA Drivers Ubuntu: Confirmed Status in OEM Priority Project: Confirmed Status in nvidia-settings package in Ubuntu: Confirmed Bug description: I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in ppa:graphics-drivers/ppa to switch from the power saving mode to the performance mode on Ubuntu 18.04. But it failed. $ nvidia-settings ERROR: NVIDIA driver is not loaded ERROR: Unable to load info from any available system However `prime-select nvidia` still works fine and there is no such issue by nvidia-settings 390.77-0ubuntu0.18.04.1 in bionic-updates. Private Bug: https://bugs.launchpad.net/bugs/1800081 To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Install Ubuntu16.04 in RAID1 created by Intel RSTe no matter legacy mode or UEFI mode. System hangs while rebooting Not found the issue in RAID0 No issue on Ubuntu14.04 Driver-OS inbox support Below as error messages === INFO: task systemd-shutdow:1 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task jbd2/md126p2-8:1732 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task ext4lazyinit:1873 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task kworker/u66:4:3139 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. === WORKAROUND: edit /etc/sysctl.conf with follow commands and the system don't hang while rebooting: vm.dirty_background_ratio=5 vm.dirty_ratio=10 kernel.panic=3 kernel.hung_task_panic=1 kernel.hung_task_timeout_secs=30 --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=f578df47-a1b8-4e66-bd37-904f943eb01b InstallationDate: Installed on 2016-12-15 (10 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) MachineType: Dell DCS6430G Package: linux (not installed) ProcEnviron: LANGUAGE=en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=bc552762-1955-44b8-a83e-2a414f0e0bd1 ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/22/2016 dmi.bios.vendor: Dell dmi.bios.version: 2.0.3 dmi.board.name: 038VV0 dmi.board.vendor: Dell dmi.board.version: X01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell dmi.modalias: dmi:bvnDell:bvr2.0.3:bd03/22/2016:svnDell:pnDCS6430G:pvr:rvnDell:rn038VV0:rvrX01:cvnDell:ct23:cvr: dmi.product.name: DCS6430G dmi.sys.vendor: Dell To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1648388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840484] Re: linux-oem 4.15 can not suspend to idle XPS-13-9380
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1840484 Title: linux-oem 4.15 can not suspend to idle XPS-13-9380 Status in OEM Priority Project: New Status in linux-signed-oem package in Ubuntu: New Bug description: it somehow s2i failed, from message , it seems the s2i process be blocked by thunderbolt device. dmesg: [193139.391652] pciehp :04:04.0:pcie204: pcie_do_write_cmd: no response from device [193139.391703] pciehp :04:01.0:pcie204: pcie_do_write_cmd: no response from device [193141.012736] PM: noirq suspend of devices failed [193141.772467] ath10k_pci :02:00.0: Unknown eventid: 118809 [193141.775359] ath10k_pci :02:00.0: Unknown eventid: 90118 [193141.872317] thunderbolt :05:00.0: control channel starting... Not sure is it relative that I hot plug out WD19 docking before suspend. reproduce rate: random ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1045-oem 4.15.0-1045.50 ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18 Uname: Linux 4.15.0-1045-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 17 00:02:08 2019 InstallationDate: Installed on 2019-08-11 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1840484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857409] Re: alsa/sof: load different firmware on different platforms
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857409 Title: alsa/sof: load different firmware on different platforms Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] In our ubuntu kernel, the sof driver will load the sof-cnl.ri (firmware) on all platforms, but mainline kernel already supported the multi firmwares on differnt platforms, and OEM project needs us to support the mutli-firmware names in the ubuntu kernel [Fix] cherry-pick 3 upstream patches, then on cnl platforms, it will load sof-cnl.ri, on cml platfomrs, it will load sof-cml.ri, on cfl platforms, it will load sof-cfl.ri [Test Case] Prepare the firmware from https://github.com/thesofproject/linux-firmware master branch, then boot the kernel with these patches. [Regression Risk] Low, just let different platforms load differnt firmware, and these patches are in the upstream kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859387] Re: intel/sof: update the intel sof firmware to v1.3-0f73628 for cml and cnl
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1859387 Title: intel/sof: update the intel sof firmware to v1.3-0f73628 for cml and cnl Status in OEM Priority Project: Fix Committed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Eoan: Fix Released Bug description: [Impact] Intel released a new version sof firmware to Canonical, they suggested that we should integrate the version v1.3-0f73628 and we should only pick the cml and cnl firmwares since other firmwares are not fully tested. Since we have a couple of Lenovo and Dell cnl and cml machines which need to enable sof driver, we integrate the firmwares to ubuntu. [Fix] - fix the hang issue in the firmware for the cml and cnl - introduce the ldc file which helps to do the firmware debug - divide the firmware to cml and cnl specific ones [Test Case] These firmwares are already widely used in oem project, the audio functions worked very well under both Lenovo and Dell dmic machines. [Regression Risk] Low, Intel released these firmware to us, and we already did large numbers audio test in the oem project. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1859387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
