[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
** Changed in: oem-priority Importance: High => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: 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-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 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.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-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: N/A _MarkForUpload: True dmi.bios.date: 12/02/2021 dmi.bios.release: 0.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell
[Kernel-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Incomplete Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964286] Re: Intel AX201 [8086:a0f0] subsys [8086:4070] iwlwifi microcode crash after updating to 5.14.0-1027-oem
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1964286 Title: Intel AX201 [8086:a0f0] subsys [8086:4070] iwlwifi microcode crash after updating to 5.14.0-1027-oem Status in OEM Priority Project: Triaged Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: Mar 09 10:33:40 MDAT-DVT2-D8 kernel: FAT-fs (sda1): unable to read boot sector to mark fs as dirty Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Start IWL Error Log Dump: Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Transport status: 0x004B, valid: 6 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Loaded firmware version: 63.c04f3485.0 QuZ-a0-hr-b0-63.ucode Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x0FAD | ADVANCED_SYSASSERT Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0xA210 | trm_hw_status0 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x | trm_hw_status1 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004CAD42 | branchlink2 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | interruptlink1 Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | interruptlink2 ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1027-oem 5.14.0-1027.30 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 9 11:13:53 2022 InstallationDate: Installed on 2021-10-19 (140 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962799] Re: Bad items from Powertop on oem kernel
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) ** Changed in: oem-priority Importance: Undecided => High ** Tags added: hwe-powerconsumption -- 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/1962799 Title: Bad items from Powertop on oem kernel Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: New Bug description: On Jaguar2, we found some items are bad from powertop, could we set them 'Good' by default from oem kernel, so that we could save more power consumption. System info "ThinkPad X1 Yoga Gen 7", "BIOS": "N3AET52W (1.17 ) 02/21/2022", CPU": "12th Gen Intel(R) Core(TM) i5-1235U", VGA: [8086:46a8], Kernel: 5.14.0-1024-oem Power Consumption === The idle-screen-on-residency-check/cpu-low-power-idle/system-low-power-idle passed. Default value and the value after set all ‘Good’ in powertop ShortIdle: 5.5W, 5W LongIdle: 1.8W, 2W S2Idle: 0.6W, 0.6W Bad items === * VM writeback timeout (echo ‘1500’ > /proc/sys/vm/dirty_writeback_centisecs) * Should we turn off the NMI watchdog for the OEM kernel? It prompt“NMI watchdog should be turned off” (/proc/sys/kernel/nmi_watchdog) * Runtime PM for I2C Adapter i2c-[2-10] (i915 gmbus tc[1-6]/dp[a-c])? By default these values are ‘on’, should we set it to ‘auto’? (/sys/bus/i2c/devices/i2c-2/device/power/control) * Runtime PM for PCI Device Intel Corporation Device [4601,46a8,461d,464f,51a4,51f0,5182,51ed,51ef,51fc]? Host bridge,VGA controller,Signal processing controller,System peripheral,Serial bus controller,Network Controller,ISA bridge,USB controller,RAM memory,Serial controller. (/sys/bus/pci/devices/:00:00.0/power/control) * Runtime PM for PCI Device MEDIATEK Corp. Device 4d75 * Runtime PM for PCI Device Samsung Electronics Co Ltd Device a80a * Autosuspend for USB device USB Bridge [MCHP]? (/sys/bus/usb/devices/3-8/power/control) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958850] Re: USB port lost function after unplugging usb drive
** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1958850 Title: USB port lost function after unplugging usb drive Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Test the proposed 5.14 oem kernel, and get a failure symptom. Unplug a usb drive from WD19TB docking and a BUG reported in kernel, then the other embedded usb port can't detect usb drive anymore after a while. kernel: usb 5-2.3.3: USB disconnect, device number 5 kernel: BUG: kernel NULL pointer dereference, address: 0030 kernel: #PF: supervisor read access in kernel mode kernel: #PF: error_code(0x) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP NOPTI [Fix] 2a19b28f7929) blk-mq: cancel blk-mq dispatch work... is the first regression and it lands mainline since v5.16-rc2. After applied https://lore.kernel.org/all/20210816134624.ga24...@lst.de/#r, issue is gone. the patches has beend landed since v5.15-rc1. [Test Case] 1. plug usb driver on the machine. 2. unplug usb driver. 3. check the dmesg if the oops would be shown [Where problems could occur] Medium ~~~ Test the proposed 5.14 oem kernel, and get a failure symptom. Unplug a usb drive from WD19TB docking and a BUG reported in kernel, then the other embedded usb port can't detect usb drive anymore after a while. kernel: usb 5-2.3.3: USB disconnect, device number 5 kernel: BUG: kernel NULL pointer dereference, address: 0030 kernel: #PF: supervisor read access in kernel mode kernel: #PF: error_code(0x) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP NOPTI --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 2205 F pulseaudio /dev/snd/controlC0: u 2205 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-04-29 (270 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Precision 5750 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1021-oem N/A linux-backports-modules-5.14.0-1021-oem N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.14.0-1021-oem x86_64 UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952823] Re: Screen blinks when entering suspend
** Changed in: oem-priority Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1952823 Title: Screen blinks when entering suspend Status in OEM Priority Project: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: [Summary] The screen turns on for a moment when laptop is entering suspend. This issue happens on Dell Latitude 5421. [Steps to reproduce] 1. Enter suspend via power menu 2. Observe the display (Note that `rtcwake` may not able to reproduce this issue. `systemctl suspend` may reproduce this.) [Expected result] The screen should not turn back on if the system is going to suspend. [Actual result] When "Suspend" is clicked, screen turns off, then turns back on for a moment, then turns off before laptop entering suspend. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956232] Re: ipu6: ov01a1s: failed to init camera
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Shih-Yuan Lee (fourdollars) ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956232 Title: ipu6: ov01a1s: failed to init camera Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: With proposed oem-5.14 kernel from bug 1955383 and latest middleware installed, cheese no longer gives video streaming. Installed middleware are: * linux-firmware: 1.187.24+staging.39 * libipu6: 0~git202112020845.a14b40c-1~ubuntu20.04.1 * libcamhal-common: 0~git202112130639.4585612~ubuntu20.04.1 * libcamhal0: 0~git202112130639.4585612~ubuntu20.04.1 * libgsticamerainterface-1.0-1: 0~git202112230614.eb13eb1~ubuntu20.04.1 * gstreamer1.0-icamera: 0~git202112230614.eb13eb1~ubuntu20.04.1 But when switched back to following ones, same oem-5.14 kernel works just fine: * libipu6: 0~git202104021802.45905c6-1~ubuntu20.04.1 * libcamhal-common: 0~git202105200731.43dcb4c~ubuntu20.04.1 * libcamhal0: 0~git202105200731.43dcb4c~ubuntu20.04.1 * libgsticamerainterface-1.0-1: 0~git202104021904.aeed9b9~ubuntu20.04.1 * gstreamer1.0-icamera: 0~git202104021904.aeed9b9~ubuntu20.04.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2171 F pulseaudio CasperMD5CheckResult: skip Dependencies: 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-mewtwo+X103 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-17 (17 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Latitude 9420 Package: linux-firmware 1.187.24+staging.39 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f010c12a-7bf3-4d44-8e9e-6236b24bdb57 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 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.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.24+staging.39 Tags: focal third-party-packages Uname: Linux 5.14.0-2013-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: N/A _MarkForUpload: True dmi.bios.date: 01/25/2021 dmi.bios.release: 89.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.5.23 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.5.23:bd01/25/2021:br89.5:svnDellInc.:pnLatitude9420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0A32: dmi.product.family: Latitude dmi.product.name: Latitude 9420 dmi.product.sku: 0A32 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1956232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950974] Re: Improve USB Type-C support
** 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950974 Title: Improve USB Type-C support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: [Impact] Error message "ucsi_acpi USBC000:00: GET_CONEECTOR_STATUS failed (-110)" can be found on many systems. [Fix] The main issue is that the PD firmware is unreliable, so use more deterministic methods to make it reliable [Test] The error message is gone. Also tried to plug/unplug USB Type-C power cord, and the status are always reported correctly. [Where problems could occur] This is quite a huge refactor, so regression can be expected. Only target to unstable and latest OEM kernel to reduce risk we are taking. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945083] [NEW] wifi firmware randomly crash
Public bug reported: The wifi device: 00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9462 [8086:02f0] Subsystem: Intel Corporation Wireless-AC 9462 [8086:4070] Kernel driver in use: iwlwifi The wireless AP I connected: tp-link archer c7 v5.0 It's just randomly crashed about browsing we 2~3 hours. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.16 ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1 Uname: Linux 5.13.0-1012-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alextu 1395 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 26 12:05:50 2021 Dependencies: InstallationDate: Installed on 2021-08-13 (43 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: Dell Inc. Latitude 5420 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-1012-oem root=UUID=33eb712e-a5ea-49c5-aa50-4ab1b771318c ro rootflags=subvol=@ i915.enable_psr=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-1012-oem N/A linux-backports-modules-5.13.0-1012-oem N/A linux-firmware 1.187.16 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2020 dmi.bios.release: 0.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.75 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.4.75:bd10/06/2020:br0.4:svnDellInc.:pnLatitude5420:pvr:sku0A40:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5420 dmi.product.sku: 0A40 dmi.sys.vendor: Dell Inc. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug focal ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- 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/1945083 Title: wifi firmware randomly crash Status in linux-firmware package in Ubuntu: Invalid Bug description: The wifi device: 00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9462 [8086:02f0] Subsystem: Intel Corporation Wireless-AC 9462 [8086:4070] Kernel driver in use: iwlwifi The wireless AP I connected: tp-link archer c7 v5.0 It's just randomly crashed about browsing we 2~3 hours. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.16 ProcVersionSignature: Ubuntu 5.13.0-1012.16-oem 5.13.1 Uname: Linux 5.13.0-1012-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alextu 1395 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 26 12:05:50 2021 Dependencies: InstallationDate: Installed on 2021-08-13 (43 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: Dell Inc. Latitude 5420 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-1012-oem root=UUID=33eb712e-a5ea-49c5-aa50-4ab1b771318c ro rootflags=subvol=@ i915.enable_psr=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-1012-oem N/A linux-backports-modules-5.13.0-1012-oem N/A linux-firmware 1.187.16 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2020 dmi.bios.release: 0.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.75 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.4.75:bd10/06/2020:br0.4:svnDellInc.:pnLatitude5420:pvr:sku0A40:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5420 dmi.product.sku: 0A40 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] Re: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] VMD PCI-E bridges on ADL-M/P/S use new device IDs and therefore not covered by previous LTR reset fix in bug 1896598. [Fix] Additional entires to vmd_bridge_tbl in drivers/pci/quirks.c is requierd: * ADL-M: [8086:464d] * ADL-P: [8086:51b0] * ADL-S: [8086:7ab4] [Test Case] $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' ... 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ [Where problems could occur] This will reset zeroed PCI_LTR_MAX_SNOOP_LAT and PCI_LTR_MAX_NOSNOOP_LAT values to a fixed 3145728ns that is used on Windows. Devices might want to set itself to a smaller value, but while this is not yet correctly supported by VMD controller driver, so the device power consumption might be little worse than ideal. [Other Info] VMD ASPM was first supported for Tiger Lake cpus, so all kernel versions newer than 5.6 should have already the supporting function. This patch targets Alder Lake cpus that are supported since 5.10-oem and on. == original bug report == * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384, https://bugs.launchpad.net/bugs/1896598. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 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.13.0-9010-oem N/A
[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
Hi Harrison, Intel used to ask users using the latest proprietary firmware from upstream[1]. The proprietary firmware is a blackbox in opensource, so we are trying to figure out the stable combination of kernel and related firmware. So far there are 2 kernel flavors verified works in the environment of #27 in Focal: 1. HWE kernel 5.11 + latest firmware iwlwifi-QuZ-a0-hr-b0-59.ucode (you can try it from the linux-firmware from #21 which is doing SRU) 2. OEM kernel 5.13 + latest firmware -63 (you can try it from the linux-firmware from #21 which is doing SRU) We did not check the latest mainline kernel[2] + latest upstream firmware [1] because so far the above 2 works well in our WIFI AX environment. We are wondering if any difference from the Steve's environment and yours keep the Intel proprietary firmware crashing. Could you please check if the above 2 kernel flavors plus the linux-firmware doing SRUing work on your environment? If it still failed, could you please share with us the dmesg and lspci (better to get sosreport as well) and which WIFI 6 AP you are connecting to? So that we can try reproducing your issue here :) [1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git [2] https://kernel.ubuntu.com/~kernel-ppa/mainline/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0] Status in Linux Firmware: New Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 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 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Kernel-packages] [Bug 1937415] Re: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
btw, pick up the different firmware binary related to iwlwifi here. $ git diff Ubuntu-1.199 Ubuntu-1.198 https://paste.ubuntu.com/p/t3bpy68MMp/ ``` Binary files a/iwlwifi-ty-a0-gf-a0.pnvm and b/iwlwifi-ty-a0-gf-a0.pnvm differ # and a lot of files in intel/ibt differ ``` -- 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/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 Status in linux-firmware package in Ubuntu: New Bug description: After upgrading from linux-firmware 1.198 to 1.199 my connectivity became unstable and I could see repeating hardware resets in `dmesg` output. Downgrading to linux-firmware 1.198 again resolved the issue. Note: this bug was filed after downgrading the package, but hopefully apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937415] Re: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
Just take a quick look on this issue. from #2, Jul 17 07:05:54 frode-threadripper kernel: [8.847048] iwlwifi :48:00.0: loaded firmware version 59.601f3a66.0 cc-a0-59.ucode op_mode iwlmvm from #1 dmesg, [8.920438] iwlwifi :48:00.0: loaded firmware version 59.601f3a66.0 cc-a0-59.ucode op_mode iwlmvm Looks both boot time (pass and failed) are using the same version of iwlwifi firmware. Compare to linux-firmware 1.199 and 1.198: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-firmware/commit/?h=impish=19185cb1aeb67563dd18f00963f388ceaaa29fcd looks the only firmware change related to iwlwifi is this one: +- iwlwifi: add ty firmware from Core63-43 But there is a bluetooth firmware change for Intel AX200 which not sure will it impact the wifi module on the same chip(after all, the firmware is blackbox binary from IHV): +- linux-firmware: Update firmware file for Intel Bluetooth AX200 Could you please add one of the 2 firmware manually to check if the issue can be reproduced? -- 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/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 Status in linux-firmware package in Ubuntu: New Bug description: After upgrading from linux-firmware 1.198 to 1.199 my connectivity became unstable and I could see repeating hardware resets in `dmesg` output. Downgrading to linux-firmware 1.198 again resolved the issue. Note: this bug was filed after downgrading the package, but hopefully apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
Hi Steve, Looks launchpad does not forward the updated comment through mail. I updated step 3 because of OEM kernel 5.13 is only in focal-proposed now: 3. # to install OEM 5.13 # Please manually click on Pre-released updates(focal-proposed) in `Software & Updates` UI first. $ sudo apt-get install linux-image-oem-20.04c On Fri, Jul 16, 2021 at 10:00 AM Steve Barriault <1932...@bugs.launchpad.net> wrote: > Hi Alex: > > I did steps 1 and 2 already. > > Step 3, I get the following error: could not find > > (Actual message is in French) > > Could you check if this has been uploaded to the database? > > Best Regards, > > Steve > > On Wed, Jul 14, 2021 at 10:01 AM Alex Tu <1932...@bugs.launchpad.net> > wrote: > > > sorry for confusing, let me break down the steps: > > 1. # Add PPA from > > > https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415/comments/2 > > $ sudo add-apt-repository ppa:vicamo/linux-firmware-staging > > > > 2. # to get linux-firmware from Vicamo's PPA > > $ sudo apt-get install linux-firmware > > > > 3. # to install OEM 5.13 > > $ sudo apt-get install linux-image-oem-20.04c > > > > 4. # reboot, and make sure you are running under oem kernel 5.13 > > $ uanme -r > > 5.13.0-1007-oem > > > > 5. # check if the target firmware `-63` loaded > > $ dmesg | grep iwlwifi > > iwlwifi :00:14.3: loaded firmware version 63.c04f3485.0 > > QuZ-a0-hr-b0-63.ucode op_mode iwlmvm > > > > 6. # check if the wifi issue can still be reproduced. > > - if it is there, please also attach the dmesg here. > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1932548 > > > > Title: > > [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on > > wireless [8086:a0f0] > > > > Status in Linux Firmware: > > New > > Status in OEM Priority Project: > > Confirmed > > Status in linux-oem-5.10 package in Ubuntu: > > New > > > > Bug description: > > Whenever I am using a wireless connection, the image freezes roughly > > every two minutes. Sometimes, email cannot be retrieved / computer > > complains the connection was momentarily lost. > > > > - If I am on a wire, this problem does NOT occur. > > - This problems occurs on wireless independent of the platform used > > (behavior seen in both Google Hangout and Zoom) > > - This problem does NOT occur on Windows. I did a meeting where both my > > Linux and Windows machines were connected to the same meeting and using > the > > same wifi router, and while the performance on Windows was flawless, > > unfortunately it was not so on the Ubuntu box. So I don't think my wifi > > router or network is to blame. > > - As far as I can recall, the problem used not to be there 2 weeks ago. > > So it may have been introduced by a recent update. > > - As communicated before, I am on a certified machine from Dell, > > recently purchased with Ubuntu already on board from factory (I assume > the > > logs there were sent to you would contain the information). > > - I tried to generate a log on the wireless, but the process did not > let > > me do this very easily. I am more than happy to send you additional > > information - but please let me know which package you want me to spy > upon > > exactly, as I am not sure what would be helpful in this matter. > > > > ProblemType: Bug > > DistroRelease: Ubuntu 20.04 > > Package: xorg 1:7.7+19ubuntu14 > > ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 > > Uname: Linux 5.10.0-1029-oem x86_64 > > ApportVersion: 2.20.11-0ubuntu27.18 > > Architecture: amd64 > > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > > CasperMD5CheckResult: skip > > CompositorRunning: None > > CurrentDesktop: ubuntu:GNOME > > Date: Fri Jun 18 09:47:58 2021 > > 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 > > DistroCodename: focal > > DistroVariant: ubuntu > > EcryptfsInUse: Yes > > ExtraDebuggingInterest: Yes > > GraphicsCard: > >Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA > > controller]) > > Subsyst
[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
@Zorro, We can not reproduce the AX201 wifi crashing issue with new firmware #9 + kernel 5.10.0-1037-oem on the machine XPS 13 TGL in the certification pool. But it happens to Steve's XPS 13 TGL. Could you please check if this issue can be reproduced on other XPS 13 TGL + AX201 wifi[8086:a0f0] you have? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0] Status in Linux Firmware: New Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 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 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/linux-firmware/+bug/1932548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933415] Re: Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0.
A test result on AX201 might not related to this AX210, but it might able be a
reference for the -63 firmware.
https://bugs.launchpad.net/somerville/+bug/1933755/comments/9
--
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/1933415
Title:
Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW
error detected. Restarting 0x0.
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Focal:
In Progress
Bug description:
[SRU Justification]
[Impact]
iwlwifi may encounter firmware crash when running 5.13 kernel with
outdated firmware.
[Fix]
Commit 2b13afc1a0ff82 ("iwlwifi: add new FWs from core60-51 release")
added new rev -63 firmware.
[Test Case]
1. disconnect/connect stress
$ sudo add-apt-repository ppa:checkbox-dev/ppa
$ sudo apt install plainbox-provider-checkbox
$ checkbox-cli run
com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress
ignore connect bluetooth part, and set the SSID and password to
proceed.
2. suspend/resume stress
$ for i in $(seq 200); do \
echo "Round $i..."; \
nmcli d; \
sleep 15; \
rtcwake -m mem -s 15; \
done
[Where problems could occur]
Rev -63 firmware is only used by 5.13 kernel or newer.
[Other Info]
While 5.13 kernel is only available in Focal and Impish, only Focal is
nominated here.
== original bug description ==
[Reproduce steps]
1. disconnect/connect stress
$ sudo add-apt-repository ppa:checkbox-dev/ppa
$ sudo apt install plainbox-provider-checkbox
$ checkbox-cli run
com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress
ignore connect bluetooth part, and set the SSID and password to proceed.
2. suspend/resume stress
$ for i in $(seq 200); do \
echo "Round $i..."; \
nmcli d; \
sleep 15; \
rtcwake -m mem -s 15; \
done
kernel: iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x0.
[100/1757]
kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
kernel: iwlwifi :03:00.0: Status: 0x0040, count: 6
kernel: iwlwifi :03:00.0: Loaded firmware version: 59.601f3a66.0
ty-a0-gf-a0-59.ucode
kernel: iwlwifi :03:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
kernel: iwlwifi :03:00.0: 0x00A08200 | trm_hw_status0
kernel: iwlwifi :03:00.0: 0x | trm_hw_status1
kernel: iwlwifi :03:00.0: 0x004D9BDC | branchlink2
kernel: iwlwifi :03:00.0: 0x922A | interruptlink1
kernel: iwlwifi :03:00.0: 0x922A | interruptlink2
kernel: iwlwifi :03:00.0: 0x000161C4 | data1
kernel: iwlwifi :03:00.0: 0x0010 | data2
kernel: iwlwifi :03:00.0: 0x | data3
kernel: iwlwifi :03:00.0: 0x1C405003 | beacon time
kernel: iwlwifi :03:00.0: 0x72B40004 | tsf low
kernel: iwlwifi :03:00.0: 0x03E4 | tsf hi
kernel: iwlwifi :03:00.0: 0x | time gp1
kernel: iwlwifi :03:00.0: 0x00EF1CDC | time gp2
kernel: iwlwifi :03:00.0: 0x0001 | uCode revision type
kernel: iwlwifi :03:00.0: 0x003B | uCode version major
kernel: iwlwifi :03:00.0: 0x601F3A66 | uCode version minor
kernel: iwlwifi :03:00.0: 0x0420 | hw version
kernel: iwlwifi :03:00.0: 0x00489002 | board version
kernel: iwlwifi :03:00.0: 0x8011001C | hcmd
kernel: iwlwifi :03:00.0: 0xE6863000 | isr0
kernel: iwlwifi :03:00.0: 0x0104 | isr1
kernel: iwlwifi :03:00.0: 0x68FA | isr2
kernel: iwlwifi :03:00.0: 0x00C44C4F | isr3
kernel: iwlwifi :03:00.0: 0x0020 | isr4
kernel: iwlwifi :03:00.0: 0x007C019C | last cmd Id
kernel: iwlwifi :03:00.0: 0x000161C4 | wait_event
kernel: iwlwifi :03:00.0: 0x00D0 | l2p_control
kernel: iwlwifi :03:00.0: 0x00018034 | l2p_duration
kernel: iwlwifi :03:00.0: 0x003F | l2p_mhvalid
kernel: iwlwifi :03:00.0: 0x00CF00F8 | l2p_addr_match
kernel: iwlwifi :03:00.0: 0x0009 | lmpm_pmg_sel
kernel: iwlwifi :03:00.0: 0x | timestamp
kernel: iwlwifi :03:00.0: 0x9890 | flow_handler
kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
kernel: iwlwifi :03:00.0: Status: 0x0040, count: 7
kernel: iwlwifi :03:00.0: 0x2000345A | ADVANCED_SYSASSERT
kernel: iwlwifi :03:00.0: 0x | umac branchlink1
kernel: iwlwifi :03:00.0: 0x8045D8DE | umac branchlink2
kernel: iwlwifi :03:00.0: 0xC0085288 | umac interruptlink1
kernel: iwlwifi :03:00.0: 0x | umac interruptlink2
kernel: iwlwifi :03:00.0: 0x0007 | umac data1
[Kernel-packages] [Bug 1933415] Re: Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0.
Just checked with xps13-9310-c5-202007-28045 in the certification pool.
The wifi interfaces no response after `iperf -c` for about 20~30 mins.
Can not find iwlwifi related error nor firmware crash show in dmesg.
bios: 1.0.1
kernel: 5.13.0-1007-oem
firmware: linux-firmware 1.187.15+staging.7
wifi module:
00:14.3 Network controller [0280]: Intel Corporation Device [8086:a0f0] (rev 20)
iwlwifi in dmesg:
ubuntu@xps13-9310-c5-202007-28045:~$ dmesg | grep iwlwifi
[4.975000] iwlwifi :00:14.3: enabling device ( -> 0002)
[4.995558] iwlwifi :00:14.3: api flags index 2 larger than supported by
driver
[4.995576] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version:
89.3.35.37
[4.995839] iwlwifi :00:14.3: loaded firmware version 63.c04f3485.0
QuZ-a0-hr-b0-63.ucode op_mode iwlmvm
[5.074969] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX203, REV=0x354
Steps:
# on ubuntu@xps13-9310-c5-202007-28045
$ ssh -o 'StrictHostKeyChecking=no' -o 'UserKnownHostsFile=/dev/null'
'ubuntu@10.101.49.132'
# password is `u`
# connect to ubuntu-cert-ax-wpa by nmtui
# get wifi ip 192.168.50.188
ubuntu@xps13-9310-c5-202007-28045:~$ iperf3 -c 192.168.50.177 -B 192.168.50.188
-t 6000
# on another random machine 202009-28216 for iperf server
$ ssh -o 'StrictHostKeyChecking=no' -o 'UserKnownHostsFile=/dev/null'
'ubuntu@10.101.49.43'
# password is `u`
# connect to ubuntu-cert-ax-wpa by nmtui
# get wifi ip 192.168.50.177
ubuntu@202009-28216:~$ iperf3 -s -B 192.168.50.177
note:
The 2 machines will be re-deploied during next SRU. So, the ssh connection is
not expected preserve for debugging forever.
** Attachment added:
"sosreport-xps13-9310-c5-202007-28045-2021-07-14-jphgowe.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415/+attachment/5510940/+files/sosreport-xps13-9310-c5-202007-28045-2021-07-14-jphgowe.tar.xz
--
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/1933415
Title:
Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW
error detected. Restarting 0x0.
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Focal:
In Progress
Bug description:
[SRU Justification]
[Impact]
iwlwifi may encounter firmware crash when running 5.13 kernel with
outdated firmware.
[Fix]
Commit 2b13afc1a0ff82 ("iwlwifi: add new FWs from core60-51 release")
added new rev -63 firmware.
[Test Case]
1. disconnect/connect stress
$ sudo add-apt-repository ppa:checkbox-dev/ppa
$ sudo apt install plainbox-provider-checkbox
$ checkbox-cli run
com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress
ignore connect bluetooth part, and set the SSID and password to
proceed.
2. suspend/resume stress
$ for i in $(seq 200); do \
echo "Round $i..."; \
nmcli d; \
sleep 15; \
rtcwake -m mem -s 15; \
done
[Where problems could occur]
Rev -63 firmware is only used by 5.13 kernel or newer.
[Other Info]
While 5.13 kernel is only available in Focal and Impish, only Focal is
nominated here.
== original bug description ==
[Reproduce steps]
1. disconnect/connect stress
$ sudo add-apt-repository ppa:checkbox-dev/ppa
$ sudo apt install plainbox-provider-checkbox
$ checkbox-cli run
com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress
ignore connect bluetooth part, and set the SSID and password to proceed.
2. suspend/resume stress
$ for i in $(seq 200); do \
echo "Round $i..."; \
nmcli d; \
sleep 15; \
rtcwake -m mem -s 15; \
done
kernel: iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x0.
[100/1757]
kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
kernel: iwlwifi :03:00.0: Status: 0x0040, count: 6
kernel: iwlwifi :03:00.0: Loaded firmware version: 59.601f3a66.0
ty-a0-gf-a0-59.ucode
kernel: iwlwifi :03:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
kernel: iwlwifi :03:00.0: 0x00A08200 | trm_hw_status0
kernel: iwlwifi :03:00.0: 0x | trm_hw_status1
kernel: iwlwifi :03:00.0: 0x004D9BDC | branchlink2
kernel: iwlwifi :03:00.0: 0x922A | interruptlink1
kernel: iwlwifi :03:00.0: 0x922A | interruptlink2
kernel: iwlwifi :03:00.0: 0x000161C4 | data1
kernel: iwlwifi :03:00.0: 0x0010 | data2
kernel: iwlwifi :03:00.0: 0x | data3
kernel: iwlwifi :03:00.0: 0x1C405003 | beacon time
kernel: iwlwifi :03:00.0: 0x72B40004 | tsf low
kernel: iwlwifi :03:00.0: 0x03E4 | tsf hi
kernel: iwlwifi :03:00.0: 0x | time gp1
kernel: iwlwifi
[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
sorry for confusing, let me break down the steps: 1. # Add PPA from https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415/comments/2 $ sudo add-apt-repository ppa:vicamo/linux-firmware-staging 2. # to get linux-firmware from Vicamo's PPA $ sudo apt-get install linux-firmware 3. # to install OEM 5.13 $ sudo apt-get install linux-image-oem-20.04c 4. # reboot, and make sure you are running under oem kernel 5.13 $ uanme -r 5.13.0-1007-oem 5. # check if the target firmware `-63` loaded $ dmesg | grep iwlwifi iwlwifi :00:14.3: loaded firmware version 63.c04f3485.0 QuZ-a0-hr-b0-63.ucode op_mode iwlmvm 6. # check if the wifi issue can still be reproduced. - if it is there, please also attach the dmesg here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0] Status in Linux Firmware: New Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 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 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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:
[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
progress update: - Vicamo is SRUing related firmware for both oem 5.10, hwe 5.11 and oem 5.13. - for OEM 5.10, HWE 5.11: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934217 - for OEM 5.13: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415 @Steve, per #17, the firmware for OEM 5.10(LP: #1934217) not works for you. Could you please have a try on OEM 5.13 + firmware from LP: #1933415? The firmware crashing looks not happens to every machine using AX201. - Vicamo can not reproduce it with wifi6 AP during both SRU (LP: #1934217 and LP: 1933415) - It passed with OEM 5.10 + firmware(LP: #1934217) - But it failed with OEM 5.10 + firmware(LP: #1934217) on Steve's machine (per #17) So, we are asking Intel for a suggested combination of Kernel and firmware to make sure the stability of AX201. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0] Status in Linux Firmware: New Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 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 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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
[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
** Also affects: linux-firmware Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0] Status in Linux Firmware: New Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 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 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/linux-firmware/+bug/1932548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
Hi Steve, my comment #12 is saying the firmware in #9 works on the machine in certification lab, so that HWE is doing a SRU [1] to land that firmware. But that firmware seems not to work for your case(refer to your comment #10 which I missed when commenting #9). Could you please also provide your dmesg again when for the issue after you applied the firmware from #9 or from [1] [1] https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934217 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0] Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 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 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/1932548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
Hi Steve, is the firmware from #9 fixed the issue? So far, we don't sure if the firmware crashing the root cause of your issue, so KC separated it to LP: #1933755. And firmware from #9 helps LP: #1933755 (see LP: #1933755 comment #2) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0] Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 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 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/1932548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) ** Changed in: oem-priority Importance: Undecided => Critical ** Summary changed: - [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless + [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0] Status in OEM Priority Project: New Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 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 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/1932548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless
pick out some key information: # the bios vesion is 2.1.1 the bios verison of XPS 9310 in the certification pool is 1.0.1 # from lspci the wifi device is: 00:14.3 Network controller [0280]: Intel Corporation Device [8086:a0f0] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1651] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi # the latest available is 5.10.0-1033 - https://qa.debian.org/madison.php?package=linux-image-oem-20.04=ubuntu===# -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 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 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/ubuntu/+source/linux-oem-5.10/+bug/1932548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
It seems still an issue if a user installed Focal by 20.04.1 before then he buy and then plug-in a new Nvidia card to his PC then install nvidia driver. The user will still get this error. The version(2.0.4) of fixed apt not in focal-security, so user not updated apt manually will still get the problem. root@7b676b5fb787:/# apt-cache policy apt apt: Installed: 2.0.5 Candidate: 2.0.5 Version table: *** 2.0.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.0.2ubuntu0.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 2.0.2 500 500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages -- 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/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Invalid Status in nvidia-graphics-drivers-455 package in Ubuntu: Invalid Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818881] Re: ath10k_pci crashing
It can be reproduced on XPS 19 9380 + Ubuntu 20.04 + 5.8.0-45-generic. It's happening for a while on 20.04, I'm not sure the issue start from which version of kernel or firmware. $ apt list linux-firmware Listing... Done linux-firmware/focal-updates,focal-updates,now 1.187.10 all [installed,automatic] 2:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. Killer 1435 Wireless-AC [1a56:143a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818881/+attachment/5481628/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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:
[Kernel-packages] [Bug 1915003] Re: SRU: Always update the initramfs when changing power profile
# suggestion: On nvidia settings UI, there's no message saying it's building initrd after user select on-demand mode. So, the nvidia settings looks like just hangs up when it's building initrd. If user have multiple kernel before selecting on-demand, user might be confused and treat it as nvidia settings UI hangs up then force close it or reboot machine. -- 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/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in nvidia-prime source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915003] Re: SRU: Always update the initramfs when changing power profile
# verified pass on focal: ## package version as expected. ubuntu@dell-bto-focal-fossa-nvstaging-202005-27873:~$ apt list ubuntu-drivers-common nvidia-prime Listing... Done nvidia-prime/focal-proposed,focal-proposed,now 0.8.16~0.20.04.1 all [installed,automatic] ubuntu-drivers-common/focal-updates,now 1:0.8.6.5~0.20.04.1 amd64 [installed,automatic] ## check if module option in initrd in on-demand mode. $ sudo prime-select on-demand Info: selecting the on-demand profile Writing /lib/modprobe.d/nvidia-runtimepm.conf Updating the initramfs. Please wait for the operation to complete: Done ### then I see the module option in initrd correctly. main/usr/lib/modprobe.d/nvidia-runtimepm.conf:1:options nvidia "NVreg_DynamicPowerManagement=0x02" ## check if module option not in initrd in nvidia mode. $ sudo prime-select nvidia Info: selecting the nvidia profile Deleting /lib/modprobe.d/nvidia-runtimepm.conf Done ### then the module option "NVreg_DynamicPowerManagement=0x02" is removed from initrd correctly. -- 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/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in nvidia-prime source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915003] Re: Always update the initramfs when changing power profile
** Also affects: nvidia-drivers-ubuntu Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Triaged -- 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/1915003 Title: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in nvidia-prime source package in Focal: In Progress Status in nvidia-settings source package in Focal: New Status in nvidia-prime source package in Groovy: In Progress Status in nvidia-settings source package in Groovy: In Progress Bug description: The different power profiles require loading the nvidia drivers with different options (or blacklisting them, in case of intel mode). We need to call update-initramfs whenever we switch to a different profile, or things may fall out sync, resulting in a failure. The update-initramfs command takes a few seconds, therefore we also need to provide feedback, so that users know that they have to wait for the operation to complete. For this reason, prime-select will provide a spinner on the command line, and nvidia-settings will show a progress dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series
** Tags removed: verification-done-focal ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Introduce the new NVIDIA 460-server series and update the 460 series. [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] [Changelog] == 460-server == * Initial release: - Added support for the following GPUs: NVIDIA A40 NVIDIA RTX A6000 - Added support for CUDA 11.2. == 460 == * New upstream release: - Added support for the following GPUs: GeForce RTX 3080 Laptop GPU GeForce RTX 3070 Laptop GPU GeForce RTX 3060 Laptop GPU GeForce GT 1010 - Updated the NVIDIA driver to restore functionality of some features, including runtime power management, hotplugging audio-capable display devices, and S0ix-based system suspend, with recent kernels such as Linux 5.10. - Fixed a bug that caused bindless texture samplers to be incorrectly counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS limit. - Fixed a bug that could cause the GPU to hang when attempting to perform link training on an HDMI 2.1 Fixed Rate Link (FRL) display, while the display is powered off. - Fixed a bug that could intermittently cause NvFBC applications to fail with the error message "Unable to send exported fds". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series
I verified it with focal on one machine supported Nvidia runtime pm, machine: 202010-28303 , $ cat /sys/class/dmi/id/product_sku 0A48 $ uname -r 5.10.0-1010-oem $ apt list ubuntu-drivers-common nvidia-prime nvidia-driver-460 Listing... Done nvidia-driver-460/focal-proposed,now 460.39-0ubuntu0.20.04.1 amd64 [installed] nvidia-prime/focal-updates,focal-updates,now 0.8.15.3~0.20.04.1 all [installed,automatic] ubuntu-drivers-common/focal-updates,now 1:0.8.6.3~0.20.04.2 amd64 [installed] $ DISPLAY=:0 checkbox-cli run com.canonical.certification::miscellanea/check-nvidia Outcome: job passed Finalizing session that hasn't been submitted anywhere: checkbox-run-2021-01-28T08.46.29 ==[ Results ]=== ☑ : Generate an entry for each graphics card present in the system. ☑ : check if nvidia dgpu behave as we expected. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913200 Title: Introduce the new NVIDIA 460-server series and update the 460 series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Introduce the new NVIDIA 460-server series and update the 460 series. [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] [Changelog] == 460-server == * Initial release: - Added support for the following GPUs: NVIDIA A40 NVIDIA RTX A6000 - Added support for CUDA 11.2. == 460 == * New upstream release: - Added support for the following GPUs: GeForce RTX 3080 Laptop GPU GeForce RTX 3070 Laptop GPU GeForce RTX 3060 Laptop GPU GeForce GT 1010 - Updated the NVIDIA driver to restore functionality of some features, including runtime power management, hotplugging audio-capable display devices, and S0ix-based system suspend, with recent kernels such as Linux 5.10. - Fixed a bug that caused bindless texture samplers to be incorrectly counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS limit. - Fixed a bug that could cause the GPU to hang when attempting to perform link training on an HDMI 2.1 Fixed Rate Link (FRL) display, while the display is powered off. - Fixed a bug that could intermittently cause NvFBC applications to fail with the error message "Unable to send exported fds". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908885] Re: Fix drm_WARN_ON(common_len <= 0)
** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908885 Title: Fix drm_WARN_ON(common_len <= 0) Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] The TGL machine could show drm_WARN_ON(common_len <= 0) when connect with the TBT dock(WD19TB). [ cut here ] i915 :00:02.0: drm_WARN_ON(common_len <= 0) WARNING: CPU: 4 PID: 194 at drivers/gpu/drm/i915/display/intel_dp.c:2385 intel_dp_compute_link_config+0x820/0x900 [i915] Modules linked in: i915(+) i2c_algo_bit drm_kms_helper crc32_pclmul syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core nvme e1000e(+) c_i801 ahci i2c_smbus thunderbolt(+) xhci_pci xhci_pci_renesas wmi video backlight pinctrl_tigerlake pinctrl_intel CPU: 4 PID: 194 Comm: systemd-udevd Not tainted 5.10.0-051000rc7-generic #202012062330 Hardware name: Dell Inc. OptiPlex 7090 UFF - China HDD Protection/, BIOS 0.6.4 11/07/2020 RIP: 0010:intel_dp_compute_link_config+0x820/0x900 [i915] Code: 4c 8b 77 50 4d 85 f6 75 03 4c 8b 37 e8 b9 b9 60 dc 48 c7 c1 b5 6d 83 c0 4c 89 f2 48 c7 c7 d0 69 83 c0 48 89 c6 e8 a5 84 f2 db <0f> 0b ff e9 60 f8 ff ff 48 8b c2 60 04 82 RSP: 0018:ba120061f6b0 EFLAGS: 00010282 RAX: RBX: 956df17c2000 RCX: RDX: 002f RSI: 9e1b1dcf RDI: 0246 RBP: ba120061f720 R08: 9e1b1da0 R09: 002f R10: 9e1b2180 R11: 9e1b1db2 R12: 956df1e4 R13: 956df17c6000 R14: 956e029a99e0 R15: 956df17c6000 FS: 7fbd08cdd880() GS:956e0e50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 5635d4c41678 CR3: 000271c64006 CR4: 00770ee0 PKRU: 5554 Call Trace: ? dev_printk+0x5d/0x74 intel_dp_compute_config+0x11b/0x570 [i915] intel_ddi_compute_config+0x9f/0xe0 [i915] intel_modeset_pipe_config+0x212/0x9c0 [i915] intel_atomic_check+0x263/0x12c0 [i915] ? __drm_dbg+0x87/0x90 [drm] drm_atomic_check_only+0x2c7/0x450 [drm] drm_atomic_commit+0x18/0x50 [drm] intel_modeset_init_nogem+0x486/0xb10 [i915] i915_driver_probe+0x3e8/0x6e0 [i915] ? mutex_lock+0x13/0x40 i915_pci_probe+0x5a/0x140 [i915] local_pci_probe+0x48/0x80 pci_device_probe+0x10f/0x1c0 really_probe+0x1db/0x440 driver_probe_device+0xe9/0x160 device_driver_attach+0x5d/0x70 __driver_attach+0x8f/0x150 ? device_driver_attach+0x70/0x70 bus_for_each_dev+0x7e/0xc0 driver_attach+0x1e/0x20 bus_add_driver+0x152/0x1f0 driver_register+0x74/0xd0 __pci_register_driver+0x54/0x60 i915_init+0x61/0x75 [i915] ? 0xc08a1000 do_one_initcall+0x4a/0x1fa ? _cond_resched+0x19/0x30 ? kmem_cache_alloc_trace+0x17e/0x2f0 do_init_module+0x62/0x240 load_module+0xfbe/0x11e0 __do_sys_finit_module+0xbe/0x120 ? __do_sys_finit_module+0xbe/0x120 __x64_sys_finit_module+0x1a/0x20 do_syscall_64+0x38/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fbd0925f89d Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 73 01 c3 48 8b 0d c3 f5 0c 00 f7 d8 64 89 01 48 RSP: 002b:7fffa60dc628 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 5635d4c942b0 RCX: 7fbd0925f89d RDX: RSI: 7fbd0913cded RDI: 0014 RBP: 0002 R08: R09: R10: 0014 R11: 0246 R12: 7fbd0913cded R13: R14: 5635d4c92b70 R15: 5635d4c942b0 ---[ end trace c48f367c543f3384 ]-— [Fix] Kernel driver patchset https://patchwork.freedesktop.org/series/82173/ targeting v5.11. [Test Case] 1. Boot with kernel built with these patches applied. 2. check the dmesg. [Where problems could occur] The fix could resolve the drm_WARN_ON. It ease the symptom that can't output the video with the TBT dock(WD19TB) at the first boot, but it may not fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** 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 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 1902861] Re: drm/i915/dp_mst - wait longer during the clock recovery for Display port
** Tags removed: originate-from-1897246 -- 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/1902861 Title: drm/i915/dp_mst - wait longer during the clock recovery for Display port Status in HWE Next: New Status in OEM Priority Project: New Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-5.6 source package in Focal: In Progress Bug description: [Impact] For some TGL platform, connect with the external monitor on the docking station(SC), after cold/warm boot, the external monitor can't output the video and need to hotplug the docking station. [Fix] On the link-training phase, Wait longer during the clock recovery. [test] With the patch, The TGL-machine connect with the external monitor on docking station(SC) and can output the video to the external monitor on docking station after cold/warm boot. [Regression Potential] Medium, it may not the root cause. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902861] Re: drm/i915/dp_mst - wait longer during the clock recovery for Display port
** Changed in: oem-priority Importance: Undecided => Critical ** Tags added: originate-from-1897246 -- 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/1902861 Title: drm/i915/dp_mst - wait longer during the clock recovery for Display port Status in HWE Next: New Status in OEM Priority Project: New Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-5.6 source package in Focal: In Progress Bug description: [Impact] For some TGL platform, connect with the external monitor on the docking station(SC), after cold/warm boot, the external monitor can't output the video and need to hotplug the docking station. [Fix] On the link-training phase, Wait longer during the clock recovery. [test] With the patch, The TGL-machine connect with the external monitor on docking station(SC) and can output the video to the external monitor on docking station after cold/warm boot. [Regression Potential] Medium, it may not the root cause. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902861] Re: drm/i915/dp_mst - wait longer during the clock recovery for Display port
** Tags added: originate-from-1900092 -- 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/1902861 Title: drm/i915/dp_mst - wait longer during the clock recovery for Display port Status in HWE Next: New Status in OEM Priority Project: New Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-5.6 source package in Focal: In Progress Bug description: [Impact] For some TGL platform, connect with the external monitor on the docking station(SC), after cold/warm boot, the external monitor can't output the video and need to hotplug the docking station. [Fix] On the link-training phase, Wait longer during the clock recovery. [test] With the patch, The TGL-machine connect with the external monitor on docking station(SC) and can output the video to the external monitor on docking station after cold/warm boot. [Regression Potential] Medium, it may not the root cause. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10
** 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/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 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
same to #10, the issue is fixed. I verified the installation passed on focal docker image. -- 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 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
It sounds weird to me that focal user will always get an error during installing nvidia-driver-450 after this SRU be done. -- 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 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
got an error message during installation. from a machine from certification pool 201903-26932 $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal $ sudo apt-get install nvidia-driver-450 . E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) ** Attachment added: "install-nv-450.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1887674/+attachment/5409328/+files/install-nv-450.log ** Tags removed: verification-done-focal ** Tags added: verification-needed-focal -- 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 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem
hi reporter and any affected user, I can not find any released image included oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10 Same as #4 comment, the only iwlwifi dkms we provided is backport- iwlwifi-dkms. Could you please show me the `ubuntu-report show`? or bto.xml in the recovery partition, so that I know which OEM image you are using. ** 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/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:
[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: High => Critical -- You 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 gnome-control-center: Unknown Status in HWE Next: New Status in Linux: Unknown Status in Mutter: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown 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. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- 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/gnome-control-center/+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 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) ** Changed in: oem-priority Importance: Undecided => Critical -- 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: Triaged Status in linux-restricted-modules source package in Bionic: Triaged 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: Triaged Status in linux-restricted-modules source package in Focal: Triaged 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 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Also affects: hwe-next 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in gnome-control-center: Unknown Status in HWE Next: New Status in Linux: Unknown Status in Mutter: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown 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. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- 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/gnome-control-center/+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 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
reply to #39, yes it's a trade off that we don't either want user get darkscreen when then randomly plug display port for case like #38 or user get lower bpc on their working display port. So far, there seems no solid way to make sure both requirement. -- You 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 gnome-control-center: Unknown Status in HWE Next: New Status in Linux: Unknown Status in Mutter: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown 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. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- 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/gnome-control-center/+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 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
according to #40 and conversation on mattermost with Kai-Heng. HWE is planning to add quirk for the faulty dongles so that the dark screen during boot time[1] can be fixed. [1] https://gitlab.freedesktop.org/drm/intel/-/issues/1890 -- You 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 gnome-control-center: Unknown Status in Linux: Unknown Status in Mutter: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown 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. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- 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/gnome-control-center/+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 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem
** Tags added: somerville -- You 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.582726] ?
[Kernel-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
I afraid we can not just trust (EDID_version >= 1.4 && EDID_supports_10bit). Because this issue caused by any problematic component in the middle of pipeline. To ensure the compatibility, better to just defautly set bpc=8. Think of one scenario, a speaker get his Ubuntu machine onto stage, plug the HDMI or DP projector which works well on latest speaker who is using Windows machine. Then, he get dark screen or audio function lost I guess the Ubuntu user might not aware it's caused by bpc. The default behavior should offer better user experience. -- You 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 gnome-control-center: Unknown Status in Linux: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown 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. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- 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/gnome-control-center/+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 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1066 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1066 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/-/issues/1066 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in gnome-control-center: Unknown Status in Linux: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown 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. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- 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/gnome-control-center/+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 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1108 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1108 ** Also affects: xorg-server via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1108 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in Linux: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown 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. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- 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/linux/+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 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
Thanks for understanding. There's an upstream bug discussing this similar issue, we can follow their effort there. https://gitlab.freedesktop.org/drm/intel/-/issues/1890 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #1890 https://gitlab.freedesktop.org/drm/intel/-/issues/1890 ** Description changed: 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. + Would like to open this bug to open discussion for enhancing user + experience. + + existed upstream bug: + - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 + --- 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 ** 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 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. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- 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
[Kernel-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
I think different from #32. To adding a GUI configure bpc is a long-term plan. Before that,the default behavior should be designed to get the best user experience. As we all know, there're lot of hardware components on the pipline of display path(e.g. socket, converter, dongle, cable, monitor) With any lower quality component on the pipeline, dark screen or function lost is not acceptable. It should be better to provide lower default bpc than dark user's screen. Afterall, user can adjust the bpc by command in short-term or by UI in long-term plan. But if we just dark user's screen, user mostly thinks the hardware is broken or Ubuntu provides poor compatibility(if they compare the same component to Windows). -- You 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 1889384] Re: ASPM not enabled on child devices behind VMD controller
** Tags added: originate-from-1889754 -- 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/1889384 Title: ASPM not enabled on child devices behind VMD controller Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: ASPM of VMD devices is not automatically enabled even it's said capable in its Link Capabilities Register. $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1831 F pulseaudio CasperMD5CheckResult: skip 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+X38 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-29 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19 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.6.0-1020-oem N/A linux-backports-modules-5.6.0-1020-oem N/A linux-firmware 1.187.2 Tags: focal Uname: Linux 5.6.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.5.4 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.5.4:bd07/21/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1889384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878602] Re: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail
** Tags added: oem-priority originate-from-1880498 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878602 Title: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail Status in OEM Priority Project: New Status in linux package in Ubuntu: Won't Fix Bug description: Since we can't use bugzilla for USB bugs, let's use Launchpad so we can attach dmesg :) System: XPS 9300 ICL Dock: Dell WD19TB Thunderbolt dock Linux: 5.7-rc5 Right after the dock is plugged, [ 127.205823] xhci_hcd :00:0d.0: Get port status 2-1 read: 0x10202a0, return 0x10341 [ 127.205832] usb usb2-port1: status 0341 change 0001 CAS is flagged so warm-reset ensues: [ 127.313467] usb usb2-port1: do warm reset However, it seems nothing is connected to usb2-port1, causes many warm-reset fail, hence this error message: [ 132.158968] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? This issue doesn't happen on CML system with AR/TR TBT controller. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Tags added: originate-from-1887915 -- You 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 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Tags added: oem-priority originate-from-1886778 somerville -- You 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 1889539] Re: System power cutoff unexpectedly when running unigine-heaven benchmark
** 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) ** Tags added: originate-from-1875552 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1889539 Title: System power cutoff unexpectedly when running unigine-heaven benchmark Status in OEM Priority Project: New Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: On Dell Inspiron 5300 machine with nvidia graphic card embedded. The system will shutdown when running unigine-heaven benchmark. It takes less than 10min to reproduce the issue. Reproduce rate: 100/100 Reproduce step: 1. select nvidia card to render(performance mode) 2. download phoronix-test-suite from https://github.com/phoronix-test-suite/phoronix-test-suite 3. ./phoronix-test-suite run pts/unigine-heaven 4. interactive console pop-up: a. select 1920 x 1080 resolution b. select Fullscreen c. it is okay to disallow or allow store test result d. start running unigine-heaven benchmark 5. The benchmark runs for less than 10min 6. The system power cutoff without any further information --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME 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-20190418-59+beaver-osp1-samwell+X42 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-13 (230 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-driver-440 440.36-0ubuntu0~0.18.04.1somerville1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-1032.36-oem-osp1 5.0.21 Tags: bionic Uname: Linux 5.0.0-1032-oem-osp1 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/1889539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
It's seems not just one patch can fix this issue. I found another corner case that still can trigger a blutoothd segmentation fault. I pair one Bluetooth keyboard but cancel before input pairing keycode. Before timeout of latest keyboard pairing, I pair another Bluetooth keyboard and still cancel it before input pairing keycode. Please hold this SRU process and I'm debugging for that corner case. ** Changed in: bluez (Ubuntu Bionic) Status: Confirmed => In Progress -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: In Progress Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] This patch is for this issue: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * This patch workaround the case that a queue node was created but not yet assigned function before user input pairing keycode. If the user cancel the paring before inputting pairing keycode then assign the function pointer a dummy 'direct_match'. * Bluetoothd responses to Bluetooth functions and "queue" is a shared common data structure, so in case of regression happens then blutoothd systemd service would be crashed. * We can verify this by operating add/remove BT devices to trigger queue operations. * I verified on target machine BIOS ID:0983 on BT mouse, keyboard, headset on pairing, remove and functionality checking. [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
** Changed in: bluez (Ubuntu Bionic) Status: In Progress => Confirmed -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: Confirmed Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] This patch is for this issue: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * This patch workaround the case that a queue node was created but not yet assigned function before user input pairing keycode. If the user cancel the paring before inputting pairing keycode then assign the function pointer a dummy 'direct_match'. * Bluetoothd responses to Bluetooth functions and "queue" is a shared common data structure, so in case of regression happens then blutoothd systemd service would be crashed. * We can verify this by operating add/remove BT devices to trigger queue operations. * I verified on target machine BIOS ID:0983 on BT mouse, keyboard, headset on pairing, remove and functionality checking. [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872383] Re: blk_update_request error when mount nvme partition
** Tags added: originate-from-1888359 timbuktu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872383 Title: blk_update_request error when mount nvme partition Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Triaged Bug description: Can't install on this nvme with a focal server installer. As mount a nvme partition with kernel with focal 5.4.0-21-generic kernel endless blk_update_request error will exists in kernel dmesg. the nvme module: PC400 NVMe SK hynix 512GB While mount nvme module: PC SN720 NVMe WDC 256GB, there is no such issue. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (11 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06c4:c401 Bizlink International Corp. DisplayPort ALT mode device Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M MachineType: Dell Inc. Precision 3930 Rack Package: linux-generic 5.4.0.21.25 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=2b73a661-f0a8-453a-ac0d-b93c5eb97f8d ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 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.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/05/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3930Rack:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: Precision dmi.product.name: Precision 3930 Rack dmi.product.sku: 0873 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
sorry for bad habit that I miss-understanded before. I revised it and put detail information there. -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: In Progress Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] This patch is for this issue: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * This patch workaround the case that a queue node was created but not yet assigned function before user input pairing keycode. If the user cancel the paring before inputting pairing keycode then assign the function pointer a dummy 'direct_match'. * Bluetoothd responses to Bluetooth functions and "queue" is a shared common data structure, so in case of regression happens then blutoothd systemd service would be crashed. * We can verify this by operating add/remove BT devices to trigger queue operations. * I verified on target machine BIOS ID:0983 on BT mouse, keyboard, headset on pairing, remove and functionality checking. [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
** Description changed: [Impact] - * only impact Bionic machines because series after Bionic already - included this patch. + This patch is for this issue: + steps: + 1. pair bluetooth keyboard + 2. see the dialog asking user input the code for pairing. + 3. press "esc" to cancel it. + 4. blutoothd segfault shows in dmesg after a while. + 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] + [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] - * low, because the same patch from upstream is already there on Groovy, - Focal and Eoan. + * This patch workaround the case that a queue node was created but not + yet assigned function before user input pairing keycode. If the user + cancel the paring before inputting pairing keycode then assign the + function pointer a dummy 'direct_match'. + + * Bluetoothd responses to Bluetooth functions and "queue" is a shared + common data structure, so in case of regression happens then blutoothd + systemd service would be crashed. + + * We can verify this by operating add/remove BT devices to trigger + queue operations. + + * I verified on target machine BIOS ID:0983 on BT mouse, keyboard, + headset on pairing, remove and functionality checking. [Other Info] * NO. -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: In Progress Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] This patch is for this issue: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * This patch workaround the case that a queue node was created but not yet assigned function before user input pairing keycode. If the user cancel the paring before inputting pairing keycode then assign the function pointer a dummy 'direct_match'. * Bluetoothd responses to Bluetooth functions and "queue" is a shared common data structure, so in case of regression happens then blutoothd systemd service would be crashed. * We can verify this by operating add/remove BT devices to trigger queue operations. * I verified on target machine BIOS ID:0983 on BT mouse, keyboard, headset on pairing, remove and functionality checking. [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
Sorry, the debugging and debdiff was done on the target machine so that the email ID was missed. This attached new debdiff also included the patch and lp number information in the changelog. And also updated the truncated description. ** Patch added: "bluez_5.48-0ubuntu3.5.debdiff" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887910/+attachment/5394261/+files/bluez_5.48-0ubuntu3.5.debdiff -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: In Progress Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] * only impact Bionic machines because series after Bionic already included this patch. [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * low, because the same patch from upstream is already there on Groovy, Focal and Eoan. [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
** Description changed: [Impact] - * only impact Bionic machines because series after Bionic already + * only impact Bionic machines because series after Bionic already included this patch. [Test Case] - 1. pair bluetooth keyboard - 2. see the dialog asking user input the code for pairing. - 3. press "esc" to cancel it. - 4. the bluetooth should still work to pair another bluetooth device. + 1. pair bluetooth keyboard + 2. see the dialog asking user input the code for pairing. + 3. press "esc" to cancel it. + 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] - * low, becuase + * low, because the same patch from upstream is already there on Groovy, + Focal and Eoan. [Other Info] - * NO. + * NO. -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: In Progress Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] * only impact Bionic machines because series after Bionic already included this patch. [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * low, because the same patch from upstream is already there on Groovy, Focal and Eoan. [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
@seb128, yes, I modified the description and the debdiff is there in #4. ** Description changed: - steps: + [Impact] + + * only impact Bionic machines because series after Bionic already + included this patch. + + [Test Case] + 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. - 4. blutoothd segfault shows in dmesg after a while. - 5. Bluetooth shows off on setting UI of right top corner. + 4. the bluetooth should still work to pair another bluetooth device. - dmesg shows: - [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] + [Regression Potential] + + * low, becuase + + [Other Info] + + * NO. -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Incomplete Bug description: [Impact] * only impact Bionic machines because series after Bionic already included this patch. [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * low, becuase [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
this is the debdiff which applied the patch , and I also host the modified code there : https://code.launchpad.net/~alextu/ubuntu/+source/bluez/+git/bluez/+ref/lp1887910 -bluetoothd-segv-keyboard ** Patch added: "bluez_5.48-0ubuntu3.5.debdiff" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887910/+attachment/5393459/+files/bluez_5.48-0ubuntu3.5.debdiff -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Incomplete Bug description: [Impact] * only impact Bionic machines because series after Bionic already included this patch. [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * low, becuase [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] [NEW] [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
Public bug reported: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] ** Affects: oem-priority Importance: Critical Assignee: Alex Tu (alextu) Status: In Progress ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1886187 timbuktu ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => In Progress -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: New Bug description: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
after this patch, the issue can not be reproduced:
commit 24249e091ab3a935f6ea87b7f7355c689c045a80 (HEAD -> refs/heads/master)
Author: Luiz Augusto von Dentz
Date: Mon Apr 9 14:48:41 2018 +0300
shared/queue: Handle NULL as direct match on queue_remove_if
As with queue_find when function is set to NULL use direct_match as
callback.
diff --git a/src/shared/queue.c b/src/shared/queue.c
index 5ddb8326d..60df11143 100644
--- a/src/shared/queue.c
+++ b/src/shared/queue.c
@@ -280,9 +280,12 @@ void *queue_remove_if(struct queue *queue,
queue_match_func_t function,
{
struct queue_entry *entry, *prev = NULL;
- if (!queue || !function)
+ if (!queue)
return NULL;
+ if (!function)
+ function = direct_match;
+
entry = queue->head;
** Tags added: oem-priority originate-from-1886187 timbuktu
--
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/1887910
Title:
[bionic]blutoothd segfault when you cancel the keyboard pairing during
the dialog for pairing code
Status in OEM Priority Project:
In Progress
Status in bluez package in Ubuntu:
New
Bug description:
steps:
1. pair bluetooth keyboard
2. see the dialog asking user input the code for pairing.
3. press "esc" to cancel it.
4. blutoothd segfault shows in dmesg after a while.
5. Bluetooth shows off on setting UI of right top corner.
dmesg shows:
[ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp
7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000]
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844410] Re: [TGL] Thunderbolt support (Tiger Lake)
Does the #10 target to 5.6.0.1019.16 for focal?
--
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/1844410
Title:
[TGL] Thunderbolt support (Tiger Lake)
Status in HWE Next:
New
Status in intel:
Fix Committed
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Confirmed
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
TigerLake platforms fail to probe thunderbolt controller and leaving an
error message:
[2.069944] input: PS/2 Generic Mouse as
/devices/platform/i8042/serio1/input/input5
[ 21.772011] thunderbolt: probe of :00:0d.2 failed with error -110
It also introduces a nearly 20 second idle at boot.
[Fix]
Commit 57d8df68eb53 ("thunderbolt: Add support for Intel Tiger Lake")
recently landed to v5.8-rc1 addressed this issue.
[Test Case]
Check thunderbolt controller probe messages from dmesg:
thunderbolt :00:0d.2: 0: unsupported switch device id 0x9a1b
thunderbolt :00:0d.2: 0: uid crc8 mismatch (expected: 0x8e, got: 0x59)
[Regression Potential]
Low. This only enables devices which are previously failed in device
initialization.
== Original Bug Description ==
Description
TBT enabling in TGL
* 386e5e29d81c ("thunderbolt: Make tb_find_port() available to other files")
v5.6-rc1
* 4deb200d34a7 ("thunderbolt: Call tb_eeprom_get_drom_offset() from
tb_eeprom_read_n()") v5.6-rc1
* 210e9f56e9e1 ("thunderbolt: Populate PG field in hot plug acknowledgment
packet") v5.6-rc1
* b04079837b20 ("thunderbolt: Add initial support for USB4") v5.6-rc1
* 690ac0d20d40 ("thunderbolt: Update Kconfig entries to USB4") v5.6-rc1
* aa43a9dcf7fc ("thunderbolt: Make tb_switch_find_cap() available to other
files") v5.6-rc1
* cf29b9afb121 ("thunderbolt: Add support for Time Management Unit") v5.6-rc1
* e6f818585713 ("thunderbolt: Add support for USB 3.x tunnels") v5.6-rc1
Target Kernel: 5.6
Target Release: 20.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1844410/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
** Tags added: originate-from-1880147 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Released Bug description: This is for alsa-ucm-conf: The patches are already in the mainline alsa-ucm-conf, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] After fixing the kernel, we also need to change the ucm2 to make it support the machine without Intel hdmi audio. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline alsa-ucm-conf. And we already tested them on 4 HP machines. This is for linux kernel: The patch is already in the oem-5.6 kernel and unstable kernel, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] Intel upstream 2 patches in the kernel to fix it. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline kernel. On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880792] Re: linux-firmware: add sof-firmware and tplg files for tgl machines
** Tags added: oem-priority originate-from-1880147 -- 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/1880792 Title: linux-firmware: add sof-firmware and tplg files for tgl machines 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 Focal: Fix Committed Status in linux-firmware source package in Groovy: Fix Committed Bug description: [Impact] When booting our 20.04 + oem-5.6 kernel on tgl platforms, the sof audio driver always fails to load the sof firmware, the audio function deosn't work at all on tgl platforms. [Fix] Intel released sof-firmware including tplg for tgl platforms, after putting them in the /lib/firmware/inte/sof|sof-tplg, the audio works well on those tgl platforms. [Test Case] Put those firmware and tplg to linux-firmware folders, boot 20.04 + oem-5.6 kernel on tgl platforms, the audio works well. [Regression Risk] Low, just adding some new files, no change on existing files. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1880792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882896] Re: cheese not recognize resolution in MJPG format
$ udevadm info /dev/video0 P: /devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/video4linux/video0 N: video0 L: 0 S: v4l/by-path/pci-:00:14.0-usb-0:5:1.0-video-index0 S: v4l/by-id/usb-CN09357GLOG0088EB05MX03_Integrated_Webcam_HD_200901010001-video-index0 E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/video4linux/video0 E: DEVNAME=/dev/video0 E: MAJOR=81 E: MINOR=0 E: SUBSYSTEM=video4linux E: USEC_INITIALIZED=6424906 E: ID_V4L_VERSION=2 E: ID_V4L_PRODUCT=Integrated_Webcam_HD: Integrate E: ID_V4L_CAPABILITIES=:capture: E: ID_VENDOR=CN09357GLOG0088EB05MX03 E: ID_VENDOR_ENC=CN09357GLOG0088EB05MX03 E: ID_VENDOR_ID=0bda E: ID_MODEL=Integrated_Webcam_HD E: ID_MODEL_ENC=Integrated_Webcam_HD E: ID_MODEL_ID=5672 E: ID_REVISION=8813 E: ID_SERIAL=CN09357GLOG0088EB05MX03_Integrated_Webcam_HD_200901010001 E: ID_SERIAL_SHORT=200901010001 E: ID_TYPE=video E: ID_BUS=usb E: ID_USB_INTERFACES=:0e0101:0e0201: E: ID_USB_INTERFACE_NUM=00 E: ID_USB_DRIVER=uvcvideo E: ID_PATH=pci-:00:14.0-usb-0:5:1.0 E: ID_PATH_TAG=pci-_00_14_0-usb-0_5_1_0 E: ID_FOR_SEAT=video4linux-pci-_00_14_0-usb-0_5_1_0 E: COLORD_DEVICE=1 E: COLORD_KIND=camera E: DEVLINKS=/dev/v4l/by-path/pci-:00:14.0-usb-0:5:1.0-video-index0 /dev/v4l/by-id/usb-CN09357GLOG0088EB05MX03_Integrated_Webcam_HD_200901010001-video-index0 E: TAGS=:snap_chromium_chromium:seat:uaccess:snap_chromium_chromedriver: ** Description changed: reproduce step: - - open cheese - - open preferences -> resolution - - only resolution from YUYV format in options + - open cheese + - open preferences -> resolution + - only resolution from YUYV format in options + + the patches there works well and waiting for merge: + https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4 Uname: Linux 5.6.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 15:23:02 2020 InstallationDate: Installed on 2020-04-12 (58 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) MachineType: Dell Inc. XPS 13 9380 RelatedPackageVersions: - cheese3.34.0-1build1 - cheese-common 3.34.0-1build1 + cheese3.34.0-1build1 + cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd08/05/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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882896 Title: cheese not recognize resolution in MJPG format Status in Cheese: Unknown Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: reproduce step: - open cheese - open preferences -> resolution - only resolution from YUYV format in options the patches there works well and waiting for merge: https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4 Uname: Linux 5.6.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 15:23:02 2020 InstallationDate: Installed on 2020-04-12 (58 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) MachineType: Dell Inc. XPS 13 9380 RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd08/05/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. To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1882896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882896] Re: cheese not recognize resolution in MJPG format
$ v4l2-ctl -D -d /dev/video0 --list-formats-ext Driver Info: Driver name : uvcvideo Card type: Integrated_Webcam_HD: Integrate Bus info : usb-:00:14.0-6 Driver version : 5.6.14 Capabilities : 0x84a1 Video Capture Metadata Capture Streaming Extended Pix Format Device Capabilities Device Caps : 0x0421 Video Capture Streaming Extended Pix Format ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'MJPG' (Motion-JPEG, compressed) Size: Discrete 1280x720 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 960x540 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 848x480 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 640x480 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 640x360 Interval: Discrete 0.033s (30.000 fps) [1]: 'YUYV' (YUYV 4:2:2) Size: Discrete 640x480 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 640x360 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 424x240 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 320x240 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 320x180 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 160x120 Interval: Discrete 0.033s (30.000 fps) ** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #28 https://gitlab.gnome.org/GNOME/cheese/-/issues/28 ** Also affects: cheese via https://gitlab.gnome.org/GNOME/cheese/-/issues/28 Importance: Unknown Status: Unknown ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Tags added: oem-priority originate-from-1881688 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882896 Title: cheese not recognize resolution in MJPG format Status in Cheese: Unknown Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: reproduce step: - open cheese - open preferences -> resolution - only resolution from YUYV format in options the patches there works well and waiting for merge: https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4 Uname: Linux 5.6.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 15:23:02 2020 InstallationDate: Installed on 2020-04-12 (58 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) MachineType: Dell Inc. XPS 13 9380 RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd08/05/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. To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1882896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882896] [NEW] cheese not recognize resolution in MJPG format
Public bug reported: reproduce step: - open cheese - open preferences -> resolution - only resolution from YUYV format in options the patches there works well and waiting for merge: https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4 Uname: Linux 5.6.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 15:23:02 2020 InstallationDate: Installed on 2020-04-12 (58 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) MachineType: Dell Inc. XPS 13 9380 RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd08/05/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. ** Affects: cheese Importance: Unknown Status: Unknown ** Affects: oem-priority Importance: High Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal gstreamer-error oem-priority originate-from-1881688 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882896 Title: cheese not recognize resolution in MJPG format Status in Cheese: Unknown Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: reproduce step: - open cheese - open preferences -> resolution - only resolution from YUYV format in options the patches there works well and waiting for merge: https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4 Uname: Linux 5.6.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 15:23:02 2020 InstallationDate: Installed on 2020-04-12 (58 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) MachineType: Dell Inc. XPS 13 9380 RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd08/05/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. To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1882896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
** Tags added: oem-priority originate-from-1880527 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Focal: New Status in linux source package in Focal: Confirmed Bug description: This is for alsa-ucm-conf: The patches are already in the mainline alsa-ucm-conf, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] After fixing the kernel, we also need to change the ucm2 to make it support the machine without Intel hdmi audio. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline alsa-ucm-conf. And we already tested them on 4 HP machines. This is for linux kernel: The patch is already in the oem-5.6 kernel and unstable kernel, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] Intel upstream 2 patches in the kernel to fix it. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline kernel. On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875254] Re: Intermittent display blackouts on event
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Assignee: (unassigned) => Leon Liao (lihow731)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1875254
Title:
Intermittent display blackouts on event
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-osp1 package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Invalid
Status in linux-oem-osp1 source package in Bionic:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-osp1 source package in Focal:
Invalid
Bug description:
[Impact]
When audio device enters runpm D3(idle for 7 seconds) and then wakes it up to
make a sound, it flicks the screen.
This behavior could be observed while plug/remove AC cable or USB disk, or
open a terminal and press backsapce key.
[Fix]
This issue could be fixed by this commit, it fixes the flicker during
boot-time, but it also fixes the flicker during rumtime wakeup.
1ee48a61aa57 drm/i915: Limit audio CDCLK>=2*BCLK constraint back to GLK only
Audio drivers communicate with i915 over HDA bus multiple times during system
boot-up and each of these transactions result in matching
get_power/put_power calls to i915, and depending on the platform,
a modeset change causing visible flicker.
GLK is the only platform with minimum CDCLK significantly lower
than BCLK, and thus for GLK setting a higher CDCLK is mandatory.
For other platforms, minimum CDCLK is close but below 2*BCLK
(e.g. on ICL, CDCLK=176.4kHz with BCLK=96kHz). Spec-wise the constraint
should be set, but in practise no communication errors have been
reported and the downside if set is the flicker observed at boot-time.
[Test]
Verified on Dell XPS 13 9300
[Regression Potential]
Low, it fixes below commit which contains in ubuntu kernel and should have
been applied on ubuntu kernel, too.
Fixes: f6ec9483091f ("drm/i915: extend audio CDCLK>=2*BCLK constraint to more
platforms")
=
Issues with the screen going black for a second on certain events on a dell
XPS 9370 2 in 1, especially when on battery.
Seems to be a known bug in arch
(https://wiki.archlinux.org/index.php/Dell_XPS_13_2-in-1_(7390)).
Last 5.6.7 kernel tested and the issues has disappears but pb with sound card.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lucie 2232 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-04-25 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. XPS 13 7390 2-in-1
Package: linux (not installed)
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=/boot/vmlinuz-5.4.0-26-generic
root=UUID=056fd229-d014-4b3b-a581-1b646105d1ed ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
RelatedPackageVersions:
linux-restricted-modules-5.4.0-26-generic N/A
linux-backports-modules-5.4.0-26-generic N/A
linux-firmware1.187
Tags: focal
Uname: Linux 5.4.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/02/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.1
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.3.1:bd03/02/2020: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/hwe-next/+bug/1875254/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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
verified on focal in machine bios ID 09FB thermald actived well. kernel: 5.6.0-1010-oem BIOS: 0.1.11 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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: Confirmed Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Committed 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 1873441] Re: modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory
** Tags added: originate-from-1873441 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873441 Title: modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Committed Bug description: Error messages printed whenever trying to update initramfs for 5.6 kernels: $ sudo update-initramfs -u -k 5.6.0-1008-oem -> mkinitramfs -v -o a.new 5.6.0-1008-oem -> modinfo -k 5.6.0-1008-oem -F firmware da903x https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?id=b66512b91a5918b01d4cc46ec85d829fb957e989 "UBUNTU: [Packaging] Include modules.builtin.modinfo in linux-modules" is not included in 5.6 tree. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vicamo 1465 F pulseaudio /dev/snd/controlC1: vicamo 1465 F pulseaudio CasperMD5CheckResult: skip Date: Fri Apr 17 19:25:38 2020 InstallationDate: Installed on 2019-09-28 (201 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-24-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash crashkernel=512M-:192M 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.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) 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/1873441/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
@ddstreet I appreciate your quick response and detailed guidance. The description is updated. Thanks. ** Description changed: [impact] thermald doesn't support Tiger Lake cpus [test case] run thermald on Tiger Lake cpu + It can be check by following command, and the patch works if it return "passed". + $ systemctl is-active --quiet thermald && echo passed + [regression potential] - and regression would likely involve incorrect support for Tiger Lake - cpus + because TGL is not supported so current thermald is not working on TGL. + So, there's not potential regression for this patch to make it works. [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 ** Description changed: [impact] thermald doesn't support Tiger Lake cpus [test case] run thermald on Tiger Lake cpu - It can be check by following command, and the patch works if it return "passed". + 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 so current thermald is not working on TGL. So, there's not potential regression for this patch to make it works. [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 ** Description changed: [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 so current thermald is not working on TGL. - So, there's not potential regression for this patch to make it works. + 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 -- 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: Confirmed Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: In Progress 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 1876066] Re: need the id for Intel TGL CPU on Focal
** Patch added: "thermald_1.9.1-1build1ubuntu0.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1876066/+attachment/5363961/+files/thermald_1.9.1-1build1ubuntu0.1.debdiff -- 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: need the id for Intel TGL CPU on Focal Status in OEM Priority Project: Confirmed Status in thermald package in Ubuntu: New Bug 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 1876066] Re: need the id for Intel TGL CPU on Focal
** Patch added: "thermald_1.9.1-1build1lp1876066.debdiff" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1876066/+attachment/5363959/+files/thermald_1.9.1-1build1lp1876066.debdiff -- 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: need the id for Intel TGL CPU on Focal Status in OEM Priority Project: Confirmed Status in thermald package in Ubuntu: New Bug 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 1876066] Re: need the id for Intel TGL CPU on Focal
** Patch added: "patch.debdiff" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1876066/+attachment/5363953/+files/patch.debdiff ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed ** 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 thermald in Ubuntu. https://bugs.launchpad.net/bugs/1876066 Title: need the id for Intel TGL CPU on Focal Status in OEM Priority Project: Confirmed Status in thermald package in Ubuntu: New Bug 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 1876066] [NEW] need the id for Intel TGL CPU on Focal
Public bug reported: need the patch to support Intel TGL CPU on Focal https://github.com/intel/thermal_daemon/blob/master/src/thd_engine.cpp#L666 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: thermald (Ubuntu) Importance: Undecided Status: New ** 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 thermald in Ubuntu. https://bugs.launchpad.net/bugs/1876066 Title: need the id for Intel TGL CPU on Focal Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Bug 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 1872351] Re: Qualcomm Atheros QCA6174 Killer 1435 Wireless-AC: Disabling wifi causes kernel warning in __sta_info_destroy_part2
for reference: I did not see this issue on my XPS 9380 on Focal + kernel 5.6.0-1008-oem 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. Killer 1435 Wireless-AC [1a56:143a] Kernel driver in use: ath10k_pci -- You 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 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]
[Kernel-packages] [Bug 1855954] Re: [TGL] VMD support in TGL
** Changed in: oem-priority Importance: Undecided => Critical -- You 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 HWE Next: New Status in intel: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Bug description: [SRU Justification] [Impact] On platforms with VMD support, block devices won't be scanned if VMD controller is not previously probed. [Fix] Two commits from v5.5-rc1 to be backported. [Test Case] On platforms with VMD support, boot with prebuilt kernel and check if Intel Volume Management Device appears among PCI devices: $ lspci | grep 'Volume Management Device' :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller [Regression Potential] Low. This only enables VMD controller on platforms with such device. == original 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/hwe-next/+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 1859538] Re: Harrison Peak wifi / BT support
** Tags added: oem-priority originate-from-1871037 somerville -- You 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: Won't Fix Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: Description: HrP2 will be supported in CML/TGL platform. Target Release: 20.04 Target Kernel: 5.6 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 1859538] Re: Harrison Peak wifi / BT support
** Changed in: oem-priority Status: New => Triaged ** Changed in: oem-priority Importance: Undecided => Critical -- You 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 intel: Won't Fix Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: Description: HrP2 will be supported in CML/TGL platform. Target Release: 20.04 Target Kernel: 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+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 1859538] Re: Harrison Peak wifi / BT support
** 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/1859538 Title: Harrison Peak wifi / BT support Status in intel: Won't Fix Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: Description: HrP2 will be supported in CML/TGL platform. Target Release: 20.04 Target Kernel: 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+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 1866156] Re: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected.
** Tags added: oem-priority somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866156 Title: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected. Status in HWE Next: New Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: Dell laptops have an option for power management in the BIOS setting to control WLAN radio. If enabled, it will sense the connection of the system to a wired network and subsequently disable the selected wireless radios (WLAN and/or WWAN). Upon disconnection from the wired network, the selected wireless radios will be re-enabled. When Dell docking station (the ethernet is Realtek r8153 USB controller), with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. Disable runtime PM of the r8153 USB device can work around this issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 2160 F pulseaudio CurrentDesktop: ubuntu:GNOME 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-20190418-59+beaver-osp1-highsparrow+X32 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-10 (54 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Latitude 9510 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-1040-oem-osp1 N/A linux-backports-modules-5.0.0-1040-oem-osp1 N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 5.0.0-1040-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.2.6 dmi.board.vendor: Dell Inc. dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 9510 dmi.product.sku: 0983 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1866156/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
** Tags added: oem-priority originate-from-1863233 -- 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/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** 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-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: New Status in linux-firmware package in Ubuntu: New 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 1859538] Re: Harrison Peak wifi / BT support
** 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/1859538 Title: Harrison Peak wifi / BT support Status in intel: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: Description: HrP2 will be supported in CML/TGL platform. Target Release: 20.04 Target Kernel: 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+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 1857496] Re: usb-audio: the mic can't record any sound after resume on Dell Dock WD19
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Assignee: (unassigned) => Leon Liao (lihow731) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux 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: Incomplete 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 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
** Tags added: originate-from-1854420 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux 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 OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress 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] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [ 600.497456] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497457] ---[ end trace 87c55fce1375aae8 ]--- ProblemType: Bug DistroRelease:
[Kernel-packages] [Bug 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Shih-Yuan Lee (fourdollars) -- 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 OEM Priority Project: New 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] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] []
[Kernel-packages] [Bug 1847193] Re: ath10k_pci: firmware crashed randomly (Qualcomm Atheros QCA6174 )
** Tags added: originate-from-1853938 -- 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 1853701] Re: thermald not works on intel GeminiLake
just verified this case on intel glk , platform pci subsystem ID = 08AF with 2 ways to heating CPU: - $ stress -c 20 - $ sudo stress-ng --ignite-cpu --cpu 4 with thermald 1.7.0-5ubuntu5 + kernel 4.15.0-1065-oem , the thermald looks work well and the system was not shut down by overheating. refer to the attached log from thermald with `--loglevel=debug`. by monitoring sensors in /sys/class/thermal/, the temperature is keep closing to critical (95 degree), but thermald will always cool it on time. So, I will mark this issue as invalid. ** Attachment added: "thermal.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853701/+attachment/5307654/+files/thermal.log ** Changed in: oem-priority Status: New => Invalid ** Changed in: oem-priority/bionic Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853701 Title: thermald not works on intel GeminiLake Status in OEM Priority Project: Invalid Status in OEM Priority Project bionic series: Invalid Status in linux package in Ubuntu: Incomplete Bug description: After the patch landed by "LP: #1851506 Add GeminiLake support on Intel int340x thermal device" The thermal zone "TCPU" is corretly created, but thermald still not work as expected on bionic so system will shutdown by cpu stress test. But thermald 1.9 works well with patched kernel, so it might some patches needed for thermald 1.7 on bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1853701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853701] Re: thermald not works on intel GeminiLake
** Also affects: oem-priority/bionic Importance: Undecided Status: New ** Tags added: originate-from-1850248 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853701 Title: thermald not works on intel GeminiLake Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in linux package in Ubuntu: Incomplete Bug description: After the patch landed by "LP: #1851506 Add GeminiLake support on Intel int340x thermal device" The thermal zone "TCPU" is corretly created, but thermald still not work as expected on bionic so system will shutdown by cpu stress test. But thermald 1.9 works well with patched kernel, so it might some patches needed for thermald 1.7 on bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1853701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853701] [NEW] thermald not works on intel GeminiLake
Public bug reported:
After the patch landed by "LP: #1851506 Add GeminiLake support on Intel
int340x thermal device"
The thermal zone "TCPU" is corretly created, but thermald still not work
as expected on bionic so system will shutdown by cpu stress test.
But thermald 1.9 works well with patched kernel, so it might some
patches needed for thermald 1.7 on bionic.
** Affects: oem-priority
Importance: Critical
Assignee: Alex Tu (alextu)
Status: New
** Affects: oem-priority/bionic
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: originate-from-1850248
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Assignee: (unassigned) => Alex Tu (alextu)
** Changed in: oem-priority
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853701
Title:
thermald not works on intel GeminiLake
Status in OEM Priority Project:
New
Status in OEM Priority Project bionic series:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
After the patch landed by "LP: #1851506 Add GeminiLake support on
Intel int340x thermal device"
The thermal zone "TCPU" is corretly created, but thermald still not
work as expected on bionic so system will shutdown by cpu stress test.
But thermald 1.9 works well with patched kernel, so it might some
patches needed for thermald 1.7 on bionic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1853701/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838245] Re: dkms script is missing function find_module
** Changed in: dkms
Status: Confirmed => 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/1838245
Title:
dkms script is missing function find_module
Status in DKMS:
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 Committed
Status in dkms source package in Eoan:
Fix Released
Status in dkms source package in Focal:
Fix Released
Bug description:
update for SRU process:
[Impact]
1. dkms script is missing function find_module
2. priority of OBSOLETE_BY should higher than "force". #89
https://github.com/dell/dkms/issues/89
[Test case]
install the dkms which already patched (also can be found in my ppa[1])
1. install a dkms which for a kernel module system already installed.
e.g. ath10k of my testing ppa : [1]
1.1. the dkms can be installed well.
2. install a dkms which has OBSOLETE_BY and FORCE
e.g.ath10k of my testing ppa : [1] (source code in [2])
- the target dkms defined OBSOLETE_BY and FORCE
- user install dkms on a system which installed kernel version less than
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
- the dkms can be installed well.
[Regression potential]
medium as it touched the version sanity. This change correct the code logic
and land one more change from upstream as well.
The logic has been verified by #5 and me.
Building a kernel module using dkms in Linux Mint 19.1 shows the following
error:
Running module version sanity check.
/usr/sbin/dkms: Zeile 784: find_module: Befehl nicht gefunden
modinfo: ERROR: missing module or filename.
Checking the file the function is indeed missing and another user
confirmed, that it was removed at some point:
https://github.com/linuxmint/linuxmint/issues/142
Possible solution: Readd
find_module()
{
# tree = $1
# module = $2
find "$1" -name "$2$module_uncompressed_suffix" -o -name
"$2$module_suffix" -type f
return $?
}
as found in https://github.com/dell/dkms/blob/master/dkms
To manage notifications about this bug go to:
https://bugs.launchpad.net/dkms/+bug/1838245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
