[Bug 2056125] [NEW] Intel CNL: audio device disappear during suspend then resume
Public bug reported: [Description] On CNL platform, after suspend, the audio device is disappleared. $sudo rtcwake -m mem -s 5 or $systemctl suspend it happens with the latest 6.5.0-lowtency and doesn't be observed with 6.2.0-1017-lowlatency. get some errors in dmesg ~~~ 1719 [ 61.041002] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1720 [ 61.041009] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1721 [ 61.041011] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 1722 [ 61.045196] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1723 [ 61.045205] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1724 [ 61.045208] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 1725 [ 61.049050] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1726 [ 61.049066] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1727 [ 61.049068] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 1728 [ 61.052840] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1729 [ 61.052848] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1730 [ 61.052850] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 1731 [ 61.056868] sof-audio-pci-intel-cnl :00:1f.3: ipc tx error for 0x6001 (msg/reply size: 108/20): -22 1732 [ 61.056876] sof-audio-pci-intel-cnl :00:1f.3: HW params ipc failed for stream 1 1733 [ 61.056878] sof-audio-pci-intel-cnl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 ~~~ the culprit is 82b18242ae68) ASoC: SOF: pcm: do not free widgets during suspend trigger. it landed since v6.3. the version of sof-bin is ~~~ $ sudo apt policy firmware-sof-signed firmware-sof-signed: Installed: 2.0-1ubuntu4.5 Candidate: 2.0-1ubuntu4.5 ~~~ after upgrade the sof-bin to upstream-sof-bin-2023.12, the issue is gone. ** Affects: firmware-sof (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg_upstreamKernel202403040039" https://bugs.launchpad.net/bugs/2056125/+attachment/5752774/+files/dmesg_upstreamKernel202403040039 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056125 Title: Intel CNL: audio device disappear during suspend then resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2056125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971417] Re: Fix REG_WAIT timeout for Yellow Carp
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971417 Title: Fix REG_WAIT timeout for Yellow Carp To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976587] Re: Fix can't boot up after change to vmd
** Description changed:
[Impact]
+ the previous commit has been SRUed that enable CONFIG_INTEL_IOMMU_DEFAULT_ON.
+ https://bugs.launchpad.net/subiquity/+bug/1937295
+ but it would caused the regression with AMD/NVIDIA GPUs.
+ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965882
+ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146
+
+ [Fix]
+ Revert the vmd: Revert 2565e5b69c44 ("PCI: vmd: Do not disable MSI-X
remapping if interrupt remapping is enabled by IOMMU.")
+ Assign VMD irq domain before enumeration, irq domain comes from pci driver.
+
+ [Test Case]
+ 1. In BIOS, change to VMD
+ 2. Check if SKU could boot-up.
+
+ [Where problems could occur]
+ it reduce the affected region to only VMD.
** Tags added: oem-priority originate-from-1967153 somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976587
Title:
Fix can't boot up after change to vmd
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1976587/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976587] [NEW] Fix can't boot up after change to vmd
Public bug reported: [Impact] ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976587 Title: Fix can't boot up after change to vmd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966089] Re: Update OS policy capability handshake
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966089 Title: Update OS policy capability handshake To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965882] Re: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker)
could someone help to verify this kernel on target w/o intel_iommu=off?thanks https://drive.google.com/drive/folders/1c1p8y265T9urgOwKoJLXaiGUrlKpJlKO?usp=sharing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965882 Title: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971146] Re: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (fixed with intel_iommu=off)
could someone help to verify this kernel on target w/o intel_iommu=off?thanks https://drive.google.com/drive/folders/1c1p8y265T9urgOwKoJLXaiGUrlKpJlKO?usp=sharing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971146 Title: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (fixed with intel_iommu=off) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967986] Re: Fix ADL, WD22TB4, Dual monitors display resolution can't reach 4K 60hz
** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Tags added: originate-from-1974155 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967986 Title: Fix ADL, WD22TB4,Dual monitors display resolution can't reach 4K 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962731] Re: No SYS%LPI residency in suspend when ethernet is connected
@KC, do you know if the ethernet presents during estar assessment? If ethernet is not essential, estar may be passed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962731 Title: No SYS%LPI residency in suspend when ethernet is connected To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962731] Re: No SYS%LPI residency in suspend when ethernet is connected
the root cause is the i219-lm keeps the link up during suspend. Is there a requirement that ethernet links must be down during suspend? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962731 Title: No SYS%LPI residency in suspend when ethernet is connected To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971417] Re: Fix REG_WAIT timeout for Yellow Carp
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Assignee: koba (kobako) => (unassigned) ** No longer affects: linux-oem-5.14 (Ubuntu Kinetic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971417 Title: Fix REG_WAIT timeout for Yellow Carp To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
there's a regression so change it to in-progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937295 Title: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965882] Re: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker)
There's dmar error, i thought Device[01:00.0] may access a out-of-bound address. [ 843.730480] DMAR: DRHD: handling fault status reg 3 [ 843.730488] DMAR: [DMA Read NO_PASID] Request device [01:00.0] fault addr 0x6e00 [fault reason 0x0c] non-zero reserved fields in PTE [ 843.730494] DMAR: DRHD: handling fault status reg 3 [ 843.730496] DMAR: [DMA Read NO_PASID] Request device [01:00.0] fault addr 0x6e016000 [fault reason 0x0c] non-zero reserved fields in PTE [ 843.730499] DMAR: DRHD: handling fault status reg 3 [ 843.730501] DMAR: [DMA Read NO_PASID] Request device [01:00.0] fault addr 0x6e01e000 [fault reason 0x0c] non-zero reserved fields in PTE [ 843.730505] DMAR: DRHD: handling fault status reg 3 Could someone dump sudo cat /sys/bus/pci/devices/\:01\:00.0/iommu/intel-iommu/* sudo cat /sys/bus/pci/devices/\:01\:00.0/iommu_group/reserved_regions sudo cat /sys/bus/pci/devices/\:01\:00.0/iommu_group/type -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965882 Title: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971146] Re: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (fixed with intel_iommu=off)
There's dmar error, i thought Device[01:00.0] may access a out-of-bound address. [ 843.730480] DMAR: DRHD: handling fault status reg 3 [ 843.730488] DMAR: [DMA Read NO_PASID] Request device [01:00.0] fault addr 0x6e00 [fault reason 0x0c] non-zero reserved fields in PTE [ 843.730494] DMAR: DRHD: handling fault status reg 3 [ 843.730496] DMAR: [DMA Read NO_PASID] Request device [01:00.0] fault addr 0x6e016000 [fault reason 0x0c] non-zero reserved fields in PTE [ 843.730499] DMAR: DRHD: handling fault status reg 3 [ 843.730501] DMAR: [DMA Read NO_PASID] Request device [01:00.0] fault addr 0x6e01e000 [fault reason 0x0c] non-zero reserved fields in PTE [ 843.730505] DMAR: DRHD: handling fault status reg 3 Could someone dump sudo cat /sys/bus/pci/devices/\:01\:00.0/iommu/intel-iommu/* sudo cat /sys/bus/pci/devices/\:01\:00.0/iommu_group/reserved_regions sudo cat /sys/bus/pci/devices/\:01\:00.0/iommu_group/type -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971146 Title: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (fixed with intel_iommu=off) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
** Tags added: oem-priority originate-from-1967153 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937295 Title: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937295 Title: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966089] Re: Update OS policy capability handshake
SRUed, (OEM-5.14/OEM-5.17) https://lists.ubuntu.com/archives/kernel-team/2022-May/130093.html ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Tags added: oem-priority originate-from-1965785 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966089 Title: Update OS policy capability handshake To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966089] Re: Update OS policy capability handshake
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966089 Title: Update OS policy capability handshake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967986] Re: Fix ADL, WD22TB4, Dual monitors display resolution can't reach 4K 60hz
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967986 Title: Fix ADL, WD22TB4,Dual monitors display resolution can't reach 4K 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971417] Re: Fix REG_WAIT timeout for Yellow Carp
** No longer affects: linux (Ubuntu Kinetic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971417 Title: Fix REG_WAIT timeout for Yellow Carp To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971417] Re: Fix REG_WAIT timeout for Yellow Carb
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-5.14 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971417 Title: Fix REG_WAIT timeout for Yellow Carb To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971417] Re: Fix REG_WAIT timeout for Yellow Carb
** Tags added: amd oem-priority originate-from-1970872 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971417 Title: Fix REG_WAIT timeout for Yellow Carb To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971417] [NEW] Fix REG_WAIT timeout for Yellow Carb
Public bug reported: [Impact] During hotplug built-in hdmi, the error message show up. #REG_WAIT timeout for yellow Carb [Fix] This tends to take miliseconds in certain scenarios and we'd rather not wait that long. Due to how this interacts with det size update and locking waiting should not be necessary as compbuf updates before unlock. Add a watch for config error instead as that is something we actually do care about. [Test Case] 1. Plug and unplug hdmi 2. cant get the error message in dmesg. [Where problems could occur] Low ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd oem-priority originate-from-1970872 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971417 Title: Fix REG_WAIT timeout for Yellow Carb To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962731] Re: No SYS%LPI residency in suspend when ethernet is connected
** Attachment added: "lspci_202204142303" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1962731/+attachment/5580744/+files/lspci_202204142303 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962731 Title: No SYS%LPI residency in suspend when ethernet is connected To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962731] Re: No SYS%LPI residency in suspend when ethernet is connected
** Attachment added: "dmesg_518rc1_202204141714" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1962731/+attachment/5580640/+files/dmesg_518rc1_202204141714 ** Changed in: linux-signed-oem-5.14 (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962731 Title: No SYS%LPI residency in suspend when ethernet is connected To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962731] Re: No SYS%LPI residency in suspend when ethernet is connected
with 518rc1, there would encounter e1000e hang issue, even this patch has landed since 5.17rc7. git tag --contains 1866aa0d0d v5.17 v5.17-rc7 v5.17-rc8 v5.18-rc1 v5.18-rc2 ~~~ Need Intel's help to figure out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962731 Title: No SYS%LPI residency in suspend when ethernet is connected To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962731] Re: No SYS%LPI residency in suspend when ethernet is connected
** Attachment added: "dmesg_202204141708" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1962731/+attachment/5580633/+files/dmesg_202204141708 ** Changed in: linux-signed-oem-5.14 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962731 Title: No SYS%LPI residency in suspend when ethernet is connected To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962731] Re: No SYS%LPI residency in suspend when ethernet is connected
With 5.14-oem-1032, with lan connected, PHM show PCIeLPM always L1 and GBE is on. here's phm screen shot, ** Attachment added: "Screenshot from 2022-04-14 17-07-30.png" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1962731/+attachment/5580632/+files/Screenshot%20from%202022-04-14%2017-07-30.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962731 Title: No SYS%LPI residency in suspend when ethernet is connected To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968475] Re: Fix broken HDMI audio on AMD PRO VII after S3
** Tags added: originate-from-1967711 ** Tags added: somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968475 Title: Fix broken HDMI audio on AMD PRO VII after S3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967986] Re: Fix ADL, WD22TB4, Dual monitors display resolution can't reach 4K 60hz
** Description changed: [Impact] SUT attach WD22TB4 dock, plug in two 4K monitor, the monitor resolution can't reach 4K 60Hz [Fix] Fix maximum DP source rate. this patch should be taken first, - https://lore.kernel.org/intel-gfx/20211026104342.198300-2-ankit.k.nauti...@intel.com/ + 73867c8709) drm/i915/display: Remove check for low voltage sku for max dp source rate Then, on U/J/OEM-5.14, apply 3fd6afb623ba) drm/i915/intel_combo_phy: Print I/O voltage info, [Test Case] 1. Connect two 4K external monitor to WD22TB4 2. the monitor resolution can reach 4K 60Hz [Where problems could occur] Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967986 Title: Fix ADL, WD22TB4,Dual monitors display resolution can't reach 4K 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967986] Re: Fix ADL, WD22TB4, Dual monitors display resolution can't reach 4K 60hz
** Description changed: [Impact] SUT attach WD22TB4 dock, plug in two 4K monitor, the monitor resolution can't reach 4K 60Hz [Fix] Fix maximum DP source rate. - For unstable, because the patch set has been landed since 5.16-rc1 on mainline, - https://patchwork.freedesktop.org/series/93622/ this patch should be taken first, https://lore.kernel.org/intel-gfx/20211026104342.198300-2-ankit.k.nauti...@intel.com/ Then, on U/J/OEM-5.14, apply 3fd6afb623ba) drm/i915/intel_combo_phy: Print I/O voltage info, [Test Case] 1. Connect two 4K external monitor to WD22TB4 2. the monitor resolution can reach 4K 60Hz [Where problems could occur] Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967986 Title: Fix ADL, WD22TB4,Dual monitors display resolution can't reach 4K 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967986] Re: Fix ADL, WD22TB4, Dual monitors display resolution can't reach 4K 60hz
** Description changed: [Impact] SUT attach WD22TB4 dock, plug in two 4K monitor, the monitor resolution can't reach 4K 60Hz [Fix] - Fix maximum DP source rate + Fix maximum DP source rate. + + For unstable, because the patch set has been landed since 5.16-rc1 on mainline, + https://patchwork.freedesktop.org/series/93622/ + this patch should be taken first, + https://lore.kernel.org/intel-gfx/20211026104342.198300-2-ankit.k.nauti...@intel.com/ + + Then, on U/J/OEM-5.14, apply 3fd6afb623ba) drm/i915/intel_combo_phy: + Print I/O voltage info, [Test Case] 1. Connect two 4K external monitor to WD22TB4 2. the monitor resolution can reach 4K 60Hz [Where problems could occur] Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967986 Title: Fix ADL, WD22TB4,Dual monitors display resolution can't reach 4K 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967986] [NEW] Fix ADL, WD22TB4, Dual monitors display resolution can't reach 4K 60hz
Public bug reported: [Impact] SUT attach WD22TB4 dock, plug in two 4K monitor, the monitor resolution can't reach 4K 60Hz [Fix] Fix maximum DP source rate [Test Case] 1. Connect two 4K external monitor to WD22TB4 2. the monitor resolution can reach 4K 60Hz [Where problems could occur] Low ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1961653 somerville ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Tags added: oem-priority originate-from-1961653 somerville ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967986 Title: Fix ADL, WD22TB4,Dual monitors display resolution can't reach 4K 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966680] Re: Revert drm/amd/pm: enable ASPM by default
have verified with 5.14-oem-1032. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966680 Title: Revert drm/amd/pm: enable ASPM by default To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940485] Re: thermald often limits CPU frequency while on AC
@chirs, would you please try this test kernel and thermald 2.4.9. https://drive.google.com/drive/folders/12jIHUbGFnYyPzZbo3qO8XeIalyBDSrtW?usp=sharing I have applied the related kernel patches https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220318=c7ff29763989bd09c433f73fae3c1e1c15d9cda4 https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220318=668f69a5f863b877bc3ae129efe9a80b6f055141 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940485 Title: thermald often limits CPU frequency while on AC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@Rick, would you please try this test kernel and thermald 2.4.9. https://drive.google.com/drive/folders/12jIHUbGFnYyPzZbo3qO8XeIalyBDSrtW?usp=sharing I have applied the related kernel patches https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220318=c7ff29763989bd09c433f73fae3c1e1c15d9cda4 https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220318=668f69a5f863b877bc3ae129efe9a80b6f055141 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958328] Re: thermald package 1.9.1 causes CPU throttling problems
@Joshua, would you please try this test kernel and thermald 2.4.9. https://drive.google.com/drive/folders/12jIHUbGFnYyPzZbo3qO8XeIalyBDSrtW?usp=sharing I have applied the related kernel patches https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220318=c7ff29763989bd09c433f73fae3c1e1c15d9cda4 https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220318=668f69a5f863b877bc3ae129efe9a80b6f055141 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958328 Title: thermald package 1.9.1 causes CPU throttling problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1958328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966680] Re: Revert drm/amd/pm: enable ASPM by default
** Tags added: oem-priority originate-from-1952981 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966680 Title: Revert drm/amd/pm: enable ASPM by default To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966680] [NEW] Revert drm/amd/pm: enable ASPM by default
Public bug reported:
[Impact]
With WX3200 and 20.04d kernel the unit freezes on resume
[Fix]
commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
by default but a variety of hardware configurations it turns out that this
caused a regression.
Multiple SKUs with wx3200 gpus encounter the resume issue.
Before the real fix is landed, revert commit 0064b0ce85bb first.
[Test Case]
1. plug wx3200 on the adl machine and make it as a output.
2. suspend machine
3. check if machine could resume successfully
[Where problems could occur]
Low, don't make AMDGPU ASPM by default.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Affects: linux-oem-5.14 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags: oem-priority originate-from-1952981 somerville
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Description changed:
[Impact]
With WX3200 and 20.04d kernel the unit freezes on resume
[Fix]
commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
by default but a variety of hardware configurations it turns out that this
caused a regression.
- Multiple SKUs with wx3200 gpus encounter the resume issues.
+ Multiple SKUs with wx3200 gpus encounter the resume issue.
Before the real fix is landed, revert commit 0064b0ce85bb first.
[Test Case]
1. plug wx3200 on the adl machine and make it as a output.
2. suspend machine
3. check if machine could resume successfully
[Where problems could occur]
Low, don't make AMDGPU ASPM by default.
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Assignee: (unassigned) => koba (kobako)
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => koba (kobako)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966680
Title:
Revert drm/amd/pm: enable ASPM by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1966680/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940485] Re: thermald often limits CPU frequency while on AC
@Chris, could you reproduce with thermald 2.4.7? thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940485 Title: thermald often limits CPU frequency while on AC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940485] Re: thermald often limits CPU frequency while on AC
@Chris, which upstream version did you use? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940485 Title: thermald often limits CPU frequency while on AC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962731] Re: No SYS%LPI residency in suspend when ethernet is connected
** Changed in: linux-signed-oem-5.14 (Ubuntu) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962731 Title: No SYS%LPI residency in suspend when ethernet is connected To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961855] Re: Fix With 20.04d kernel and WX3200, unit freezes on resume
still reproduce it on the 5.14-oem-1025. ** Tags removed: verification-needed-focal ** Tags added: verification-failed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961855 Title: Fix With 20.04d kernel and WX3200, unit freezes on resume To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961855] Re: Fix With 20.04d kernel and WX3200, unit freezes on resume
** Tags added: oem-priority originate-from-1952981 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961855 Title: Fix With 20.04d kernel and WX3200, unit freezes on resume To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961855] [NEW] Fix With 20.04d kernel and WX3200, unit freezes on resume
Public bug reported:
[Impact]
With WX3200 and 20.04d kernel the unit freezes on resume
[Fix]
commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
by default but a variety of hardware configurations it turns out that this
caused a regression.
* PPC64LE hardware does not support ASPM at a hardware level.
CONFIG_PCIEASPM is often disabled on these architectures.
* Some dGPUs on ALD platforms don't work with ASPM enabled and PCIe
subsystem disables it
Check with the PCIe subsystem to see that ASPM has been enabled
or not.
[Test Case]
1. plug wx3200 on the adl machine and make it as a output.
2. suspend machine
3. check if machine could resume successfully
[Where problems could occur]
Low, just disable AMDGPU ASPM if system doesn't enable it.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Affects: linux-oem-5.14 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => koba (kobako)
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Assignee: (unassigned) => koba (kobako)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961855
Title:
Fix With 20.04d kernel and WX3200, unit freezes on resume
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961855/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958328] Re: thermald package 1.9.1 causes CPU throttling problems
** Changed in: thermald (Ubuntu) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958328 Title: thermald package 1.9.1 causes CPU throttling problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1958328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958850] Re: USB port lost function after unplugging usb drive
SRUed on this, (U/OEM-5.14) https://lists.ubuntu.com/archives/kernel-team/2022-January/127554.html ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958850 Title: USB port lost function after unplugging usb drive To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958850] Re: USB port lost function after unplugging usb drive
** Description changed: + [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] + 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 + Â 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 + Â 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. ** Description changed: [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: Â USER
[Bug 1958850] Re: USB port lost function after unplugging usb drive
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958850 Title: USB port lost function after unplugging usb drive To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958850] Re: USB port lost function after unplugging usb drive
the first regression is 2a19b28f7929) blk-mq: cancel blk-mq dispatch work... with mainline v5.14 and this commit, also could get the same issue. After applied these patches, issue would be gone. https://lore.kernel.org/all/20210816134624.ga24...@lst.de/#r -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958850 Title: USB port lost function after unplugging usb drive To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958850] Re: USB port lost function after unplugging usb drive
@Timo, 5.14-oem-1020 is ok, the regression is with 5.14-oem-1021. im bisecting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958850 Title: USB port lost function after unplugging usb drive To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Assignee: koba (kobako) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@Rick, here's built mainline kernel image, you could find the deb files for amd64 platform. https://kernel.ubuntu.com/~kernel-ppa/mainline/ just download them and file this command. #dpkg -i *.deb please find the first bad or last good kernel version. thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@Rick, would you mind to help bisect the kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955692] Re: Update - Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
** Tags added: oem-priority originate-from-1923568 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955692 Title: Update - Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955692] [NEW] Update - Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
Public bug reported: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. with the Bug #1945932 SRU, some target machine still got the garbage frames during bootup. [Fix] Need the one more patch to fix, this has been laned on mainline since v5.13-rc1. 1835bf459df7) drm/i915: Wait for scanout to stop when sanitizing planes [Test] 1. Power on the failed machine. 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, but didn't observe the issue on the failed machine. ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Description changed: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. with the lp1945932 SRU, some target machine still got the garbage frame during bootup. [Fix] - Nedd the one more patch to fix, this has been laned on mainline since v5.13-rc1. + Need the one more patch to fix, this has been laned on mainline since v5.13-rc1. 1835bf459df7) drm/i915: Wait for scanout to stop when sanitizing planes [Test] 1. Power on the failed machine. 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, but didn't observe the issue on the failed machine. ** Description changed: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. - with the lp1945932 SRU, some target machine still got the garbage frame - during bootup. + with the Bug #1945932 SRU, some target machine still got the garbage + frame during bootup. [Fix] Need the one more patch to fix, this has been laned on mainline since v5.13-rc1. 1835bf459df7) drm/i915: Wait for scanout to stop when sanitizing planes [Test] 1. Power on the failed machine. 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, but didn't observe the issue on the failed machine. ** Description changed: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. with the Bug #1945932 SRU, some target machine still got the garbage - frame during bootup. + frames during bootup. [Fix] Need the one more patch to fix, this has been laned on mainline since v5.13-rc1. 1835bf459df7) drm/i915: Wait for scanout to stop when sanitizing planes [Test] 1. Power on the failed machine. 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, but didn't observe the issue on the failed machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955692 Title: Update - Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1955692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954728] Re: Fix No Screen after login to Desktop on sku with 3840x2400 panel
During i switched 2k to 4k multiple times, didn't get the error. after idle 2~3 hours and keep in 4k, i found the underrun error would be shown up. but 4k works well -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954728 Title: Fix No Screen after login to Desktop on sku with 3840x2400 panel To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954728] Re: Fix No Screen after login to Desktop on sku with 3840x2400 panel
** Tags added: oem-priority originate-from-1947298 somerville ** Description changed: [Impact] Got kernel report CPU pipe A FIFO underrun: soft,transcoder kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder, [Fix] + Fix has been landed on linux-next, 4fe7907f3775(drm/i915/display/adlp: Disable underrun recovery). Defeature the underrun feature for intel display gen13+. [Test Case] 1. change resolution to 3840x2400 2. monitor works well and doesn't black out. [Where problems could occur] low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954728 Title: Fix No Screen after login to Desktop on sku with 3840x2400 panel To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954728] [NEW] Fix No Screen after login to Desktop on sku with 3840x2400 panel
Public bug reported: [Impact] Got kernel report CPU pipe A FIFO underrun: soft,transcoder kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder, [Fix] Defeature the underrun feature for intel display gen13+. [Test Case] 1. change resolution to 3840x2400 2. monitor works well and doesn't black out. [Where problems could occur] low ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Description changed: [Impact] Got kernel report CPU pipe A FIFO underrun: soft,transcoder kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder, [Fix] - Defeatur the underrun feature for intel display gen13+. + Defeature the underrun feature for intel display gen13+. [Test Case] 1. change resolution to 3840x2400 2. monitor works well and doesn't black out. [Where problems could occur] low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954728 Title: Fix No Screen after login to Desktop on sku with 3840x2400 panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954617] Re: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
** Tags added: originate-from-1950432 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954617 Title: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954617] Re: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
** Description changed: [Impact] + On ADL platform, I+N sku, get the cpufreq errors during boot-up, [ 1.058427] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) [ 1.058451] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 1 (-19) [ 1.058469] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 2 (-19) [Fix] Fixed by 46573fd6369f(cpufreq: intel_pstate: hybrid: Rework HWP calibration) The commit has been landed on mainline since v5.15-rc1. [Test Case] 1. boot-up the machine. 2. check dmesg if the cpufreq error is presented. [Where problems could occur] low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954617 Title: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954617] Re: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
** Description changed: [Impact] + get the cpufreq errors during boot-up, + [ 1.058427] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) + [ 1.058451] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 1 (-19) + [ 1.058469] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 2 (-19) [Fix] + Fixed by 46573fd6369f(cpufreq: intel_pstate: hybrid: Rework HWP calibration) + The commit has been landed on mainline since v5.15-rc1. [Test Case] + 1. boot-up the machine. + 2. check dmesg if the cpufreq error is presented. [Where problems could occur] + low ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954617 Title: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954617] Re: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
** Tags added: oem-priority originate-from-1942730 somerville ** Tags added: originate-from-1950548 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954617 Title: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954617] [NEW] Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
Public bug reported: [Impact] [Fix] [Test Case] [Where problems could occur] ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954617 Title: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@Srinivas, could you please list the situations when the lock would be triggered? here's first, #PROCHOT is flagged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@Rick, could you try to disable thermald.service on systemd and reboot then enter active mode, check the issue status. thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940485] Re: thermald often limits CPU frequency while on AC
@Chris, if you use the upstream thermald, the issue didn't occur? thanks ** Changed in: thermald (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940485 Title: thermald often limits CPU frequency while on AC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@Rick, did you try this one? sudo cpufreq-set -f `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
found one interesting thing in the log CONFIG_TDP_CONTROL is locked, could you check the bios first? e.g. c-state control cpu4: MSR_CONFIG_TDP_NOMINAL: 0x0018 (base_ratio=24) cpu4: MSR_CONFIG_TDP_LEVEL_1: 0x () cpu4: MSR_CONFIG_TDP_LEVEL_2: 0x () cpu4: MSR_CONFIG_TDP_CONTROL: 0x8000 ( lock=1) cpu4: MSR_TURBO_ACTIVATION_RATIO: 0x (MAX_NON_TURBO_RATIO=0 lock=0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@Rick, could you list the using kernel version? Do you remember which kernel version you didn't observe the issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@Rick, please dump frequency info before doing any changed #sudo cpupower -c all frequency-info if governor is powersave, please change to performance then run some loadings, and observe the cpu current frequency #cpupower frequency-set --governor performance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
** Changed in: thermald (Ubuntu) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@Rick, could you please run some loadings and log the turbstat? thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949050] Re: Fix Screen freeze after resume from suspend with iGPU [1002:6987]
** Tags removed: verification-needed-hirsute verification-needed-impish ** Tags added: verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949050 Title: Fix Screen freeze after resume from suspend with iGPU [1002:6987] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922334] Re: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16)
@Georgi, could try these 1. prime-select intel and reboot, check the issue. 2. prime-select nvidia and reboot, check the issue. please remove "i915.enable_psr=0 i915.modeset=1 nvidia_drm.modeset=1" from cmdline -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922334 Title: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1922334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940485] Re: thermald often limits CPU frequency while on AC
@Chris, could you upload the log? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940485 Title: thermald often limits CPU frequency while on AC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949321] Re: Fix System hangs on black screen when reboot
** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949321 Title: Fix System hangs on black screen when reboot To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949321] Re: Fix System hangs on black screen when reboot
** Tags added: oem-priority originate-from-1946057 somerville ** Tags added: originate-from-1942069 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949321 Title: Fix System hangs on black screen when reboot To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949321] Re: Fix System hangs on black screen when reboot
** Description changed:
[Impact]
-
+ System hangs on black screen when reboot
[Fix]
-
+ Looks like our VBIOS/GOP generally fail to turn the DP dual mode adater
+ TMDS output buffers back on after a reboot. This leads to a black screen
+ after reboot if we turned the TMDS output buffers off prior to reboot.
+ And if i915 decides to do a fastboot the black screen will persist even
+ after i915 takes over.
+
+ Apparently this has been a problem ever since commit b2ccb822d376
("drm/i915:Enable/disable TMDS output buffers in DP++ adaptor as needed") if
one rebooted while the display was turned off. And things became worse with
commit fe0f1e3bfdfe ("drm/i915: Shut down displays gracefully on reboot") since
now we always turn the display off before a reboot.
+
+ This was reported on a RKL, but I confirmed the same behaviour on my
+ SNB as well. So looks pretty universal.
+
+ Let's fix this by explicitly turning the TMDS output buffers back on
+ in the encoder->shutdown() hook. Note that this gets called after irqs
+ have been disabled, so the i2c communication with the DP dual mode
+ adapter has to be performed via polling (which the gmbus code is
+ perfectly happy to do for us).
+
+ We also need a bit of care in handling DDI encoders which may or may
+ not be set up for HDMI output. Specifically ddc_pin will not be
+ populated for a DP only DDI encoder, in which case we don't want to
+ call intel_gmbus_get_adapter(). We can handle that by simply doing
+ the dual mode adapter type check before calling
+ intel_gmbus_get_adapter().
+ Ref: https://patchwork.freedesktop.org/series/96433/
[Test]
-
+ 1. install kernel
+ 2. reboot
+ 3. check the monitor works well.
[Regression Potential]
+ Medium, patch has sent to patchwork but may have a upgraded version in the
furtue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949321
Title:
Fix System hangs on black screen when reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949321/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949321] [NEW] Fix System hangs on black screen when reboot
Public bug reported:
[Impact]
System hangs on black screen when reboot
[Fix]
Looks like our VBIOS/GOP generally fail to turn the DP dual mode adater
TMDS output buffers back on after a reboot. This leads to a black screen
after reboot if we turned the TMDS output buffers off prior to reboot.
And if i915 decides to do a fastboot the black screen will persist even
after i915 takes over.
Apparently this has been a problem ever since commit b2ccb822d376
("drm/i915:Enable/disable TMDS output buffers in DP++ adaptor as needed") if
one rebooted while the display was turned off. And things became worse with
commit fe0f1e3bfdfe ("drm/i915: Shut down displays gracefully on reboot") since
now we always turn the display off before a reboot.
This was reported on a RKL, but I confirmed the same behaviour on my
SNB as well. So looks pretty universal.
Let's fix this by explicitly turning the TMDS output buffers back on
in the encoder->shutdown() hook. Note that this gets called after irqs
have been disabled, so the i2c communication with the DP dual mode
adapter has to be performed via polling (which the gmbus code is
perfectly happy to do for us).
We also need a bit of care in handling DDI encoders which may or may
not be set up for HDMI output. Specifically ddc_pin will not be
populated for a DP only DDI encoder, in which case we don't want to
call intel_gmbus_get_adapter(). We can handle that by simply doing
the dual mode adapter type check before calling
intel_gmbus_get_adapter().
Ref: https://patchwork.freedesktop.org/series/96433/
[Test]
1. install kernel
2. reboot
3. check the monitor works well.
[Regression Potential]
Medium, patch has sent to patchwork but may have a upgraded version in the
furtue.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Affects: linux-oem-5.10 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: linux-oem-5.10 (Ubuntu Focal)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Affects: linux (Ubuntu Hirsute)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Affects: linux-oem-5.10 (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Affects: linux-oem-5.14 (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Impish)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Affects: linux-oem-5.10 (Ubuntu Impish)
Importance: Undecided
Status: New
** Affects: linux-oem-5.14 (Ubuntu Impish)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Affects: linux-oem-5.10 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: linux-oem-5.14 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: linux (Ubuntu Hirsute)
Assignee: (unassigned) => koba (kobako)
** Changed in: linux (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => koba (kobako)
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
[Bug 1949050] Re: Fix Screen freeze after resume from suspend with iGPU [1002:6987]
** Description changed: [Impact] + Screen freeze after resume from suspend [Fix] - + Perform proper cleanups on UVD/VCE suspend: powergate enablement, + clockgating enablement and dpm disablement. This can fix some hangs + observed on suspending when UVD/VCE still using(e.g. issue + "pm-suspend" when video is still playing). [Test] - 1. Add rx640 on machine - 2. suspend & resume machine. - 3. Machine would work well and doesn't hang. + 1. Plug AMD RX640/Radeon 540 into the system + 2. Connect with DP monitor to iGPU + 3. Power on + 4. Suspend the system + 5. Resume from suspend + 6. Do something for a while (terminal, nautilus, gnome-control-center, etc). + 7. System could resume normally [Regression Potential] - Low, + Low ** Tags added: oem-priority originate-from-1947881 somerville ** Description changed: [Impact] Screen freeze after resume from suspend [Fix] - Perform proper cleanups on UVD/VCE suspend: powergate enablement, - clockgating enablement and dpm disablement. This can fix some hangs - observed on suspending when UVD/VCE still using(e.g. issue - "pm-suspend" when video is still playing). + Perform proper cleanups on UVD/VCE suspend: powergate enablement, + clockgating enablement and dpm disablement. This can fix some hangs + observed on suspending when UVD/VCE still using(e.g. issue + "pm-suspend" when video is still playing). [Test] 1. Plug AMD RX640/Radeon 540 into the system 2. Connect with DP monitor to iGPU 3. Power on 4. Suspend the system 5. Resume from suspend 6. Do something for a while (terminal, nautilus, gnome-control-center, etc). 7. System could resume normally [Regression Potential] Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949050 Title: Fix Screen freeze after resume from suspend with iGPU [1002:6987] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949050] [NEW] Fix Screen freeze after resume from suspend with iGPU [1002:6987]
Public bug reported: [Impact] [Fix] [Test] 1. Add rx640 on machine 2. suspend & resume machine. 3. Machine would work well and doesn't hang. [Regression Potential] Low, ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949050 Title: Fix Screen freeze after resume from suspend with iGPU [1002:6987] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
** Changed in: linux (Ubuntu Focal) Status: Incomplete => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: In Progress => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Assignee: koba (kobako) => (unassigned) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
** Tags added: oem-priority originate-from-1923568 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945932] Re: A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Hirsute) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Impish) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => koba (kobako) ** Summary changed: - A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system + Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945932] [NEW] Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
Public bug reported: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. [Fix] do what intel_color_commit() does to make sure the bottom color state matches whatever out hardware readout produced. Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171=1 [Test] 1. Power on the system 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, maintainer still not totally sure what should do about color management features here in general. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922334] Re: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16)
@Georgi, would you please try 5.15, please get the ARCH=amd generic files and a header with "all" postfix file. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15-rc2/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922334 Title: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1922334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941696] Re: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry
** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941696 Title: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1941696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940204] Re: AMDGPU: Fix System hang after resume from suspend
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940204 Title: AMDGPU: Fix System hang after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942830] Re: Fix sluggish r8169 by disaling ASPM L1.2
** Attachment added: "lspci_vv_20210907" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942830/+attachment/5523429/+files/lspci_vv_20210907 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942830 Title: Fix sluggish r8169 by disaling ASPM L1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1942830] [NEW] Fix sluggish r8169 by disaling ASPM L1.2
@KaiHeng, with aspm 1.2 enabled, can't observe the issue on JSL machine. Could you narrow down to one Realtek's model? ** Attachment added: "iperf3_log_20210907" https://bugs.launchpad.net/bugs/1942830/+attachment/5523407/+files/iperf3_log_20210907 ** Attachment added: "dmesg_20210907" https://bugs.launchpad.net/bugs/1942830/+attachment/5523408/+files/dmesg_20210907 ** Attachment added: "lspci_s_01000_vvv" https://bugs.launchpad.net/bugs/1942830/+attachment/5523409/+files/lspci_s_01000_vvv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942830 Title: Fix sluggish r8169 by disaling ASPM L1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941696] Re: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry
Verified on 5.13-oem-1011. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941696 Title: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1941696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940204] Re: AMDGPU: Fix System hang after resume from suspend
Verified with 5.13-oem-1011. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940204 Title: AMDGPU: Fix System hang after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941696] Re: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry
** Tags added: oem-priority originate-from-1934141 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941696 Title: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1941696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941696] Re: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry
** Description changed: [Impact] - + 1. On Troy JSL platform, add AC9560 + 2. Enter Settings -> Bluetooth menu + 3. Default Bluetooth option is ON, try to toggle the BT option to OFF + 4. Into suspend mode(S3) and resume the system + 5. Enter BT settings and try to turn on BT, + 6. BT function cannot enabled until reboot. [Fix] + Turn off the msft ext only for AC9560. + Maintainer thought Intel should take care this and reject this workaround. + https://marc.info/?l=linux-bluetooth=162938546804458=2 + Intel is working on this issue and sru the workaround for the schedule. [Test] + Verified with the bellow steps 10 times. + 1. On Troy JSL and add AC9560 + 2. Turn off BT + 3. suspend the machine 10 times. + 4. turn on BT and works well. [Regression Potential] - Medium, turn off the MSFT ext only for ac9560. + Medium, it's a workaround to turn off the MSFT ext only for ac9560. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941696 Title: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941696] [NEW] Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry
Public bug reported: [Impact] [Fix] [Test] [Regression Potential] Medium, turn off the MSFT ext only for ac9560. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941696 Title: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930645] Re: Fix Ethernet not working by hotplug - RTL8106E
verified on 5.11.0-33-generic ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930645 Title: Fix Ethernet not working by hotplug - RTL8106E To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
