[Kernel-packages] [Bug 1944382] Re: Enable runtime power management for yellow carp XHCI

2021-11-30 Thread Mario Limonciello
** Changed in: amd
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1944382

Title:
  Enable runtime power management for yellow carp XHCI

Status in amd:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released

Bug description:
  Alex Hung 

  7:01 PM (1 minute ago)

  to kernel-team
  BugLink: https://bugs.launchpad.net/bugs/1944382

  [Impact]

XHCI controllers of yellow carp by default will not use runtime PM

  [Fix]

Add PCI Device IDs to enable runtime PM

The patch can be found @ https://patchwork.kernel.org/project/linux-
  usb/patch/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/

  [Test]

This is requested and tested by AMD as described in LP:1944382

  [Where problems could occur]

Low risk. This only affects devices of AMD's Yellow Carp.

  == original descriptions ==

  
  Like all XHCI controllers yellow carp XHCI by default will not use runtime PM 
and needs to be added to an allow list.  AMD has validated that XHCI runtime PM 
is safe.

  Please include https://lore.kernel.org/linux-
  usb/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/T/#u in
  OEM-5.14 kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1944382/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1944382] Re: Enable runtime power management for yellow carp XHCI

2021-10-18 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1005.5

---
linux-oem-5.14 (5.14.0-1005.5) focal; urgency=medium

  * focal/linux-oem-5.14: 5.14.0-1005.5 -proposed tracker (LP: #1944905)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.09.27)

  * Update ADL-P dmc firmware (LP: #1945438)
- drm/i915: Free all DMC payloads
- drm/i915/dmc: Update to DMC v2.12

  * Enable runtime power management for yellow carp XHCI (LP: #1944382)
- SAUCE: usb: xhci: Enable runtime-pm by default on AMD Yellow Carp platform

  * e1000e extremly slow (LP: #1930754)
- SAUCE: e1000e: Separate TGP board type from SPT
- SAUCE: e1000e: Fixing packet loss issues on new platforms

  * Fix missing HDMI audio on Intel RKL (LP: #1945556)
- drm/i915/audio: Use BIOS provided value for RKL HDA link

  * Focal update: v5.14.9 upstream stable release (LP: #1945656)
- mm, hwpoison: add is_free_buddy_page() in HWPoisonHandlable()
- ocfs2: drop acl cache for directories too
- mm/debug: sync up MR_CONTIG_RANGE and MR_LONGTERM_PIN
- mm: fix uninitialized use in overcommit_policy_handler
- usb: gadget: r8a66597: fix a loop in set_feature()
- usb: gadget: u_audio: EP-OUT bInterval in fback frequency
- usb: dwc2: gadget: Fix ISOC flow for BDMA and Slave
- usb: dwc2: gadget: Fix ISOC transfer complete handling for DDMA
- usb: musb: tusb6010: uninitialized data in tusb_fifo_write_unaligned()
- cifs: Not to defer close on file when lock is set
- cifs: Fix soft lockup during fsstress
- cifs: fix incorrect check for null pointer in header_assemble
- xen/x86: fix PV trap handling on secondary processors
- usb-storage: Add quirk for ScanLogic SL11R-IDE older than 2.6c
- USB: serial: cp210x: add ID for GW Instek GDM-834x Digital Multimeter
- USB: cdc-acm: fix minor-number release
- Revert "USB: bcma: Add a check for devm_gpiod_get"
- binder: make sure fd closes complete
- binder: fix freeze race
- staging: greybus: uart: fix tty use after free
- usb: isp1760: do not sleep in field register poll
- Re-enable UAS for LaCie Rugged USB3-FW with fk quirk
- usb: dwc3: core: balance phy init and exit
- usb: cdns3: fix race condition before setting doorbell
- usb: core: hcd: Add support for deferring roothub registration
- USB: serial: mos7840: remove duplicated 0xac24 device ID
- USB: serial: option: add Telit LN920 compositions
- USB: serial: option: remove duplicate USB device ID
- USB: serial: option: add device id for Foxconn T99W265
- misc: bcm-vk: fix tty registration race
- misc: genwqe: Fixes DMA mask setting
- mcb: fix error handling in mcb_alloc_bus()
- KVM: rseq: Update rseq when processing NOTIFY_RESUME on xfer to KVM guest
- erofs: fix up erofs_lookup tracepoint
- nexthop: Fix division by zero while replacing a resilient group
- btrfs: prevent __btrfs_dump_space_info() to underflow its free space
- xhci: Set HCD flag to defer primary roothub registration
- serial: 8250: 8250_omap: Fix RX_LVL register offset
- serial: mvebu-uart: fix driver's tx_empty callback
- scsi: sd_zbc: Ensure buffer size is aligned to SECTOR_SIZE
- drm/amd/pm: Update intermediate power state for SI
- net: hso: fix muxed tty registration
- platform/x86: amd-pmc: Increase the response register timeout
- arm64: Restore forced disabling of KPTI on ThunderX
- arm64: Mitigate MTE issues with str{n}cmp()
- comedi: Fix memory leak in compat_insnlist()
- regulator: qcom-rpmh-regulator: fix pm8009-1 ldo7 resource name
- afs: Fix page leak
- afs: Fix incorrect triggering of sillyrename on 3rd-party invalidation
- afs: Fix corruption in reads at fpos 2G-4G from an OpenAFS server
- afs: Fix updating of i_blocks on file/dir extension
- platform/x86/intel: punit_ipc: Drop wrong use of ACPI_PTR()
- regulator: max14577: Revert "regulator: max14577: Add proper module 
aliases
  strings"
- NLM: Fix svcxdr_encode_owner()
- virtio-net: fix pages leaking when building skb in big mode
- enetc: Fix illegal access when reading affinity_hint
- enetc: Fix uninitialized struct dim_sample field usage
- net: dsa: tear down devlink port regions when tearing down the devlink 
port
  on error
- net: bgmac-bcma: handle deferred probe error due to mac-address
- napi: fix race inside napi_enable
- bnxt_en: Fix TX timeout when TX ring size is set to the smallest
- net: hns3: fix change RSS 'hfunc' ineffective issue
- net: hns3: fix inconsistent vf id print
- net: hns3: fix misuse vf id and vport id in some logs
- net: hns3: check queue id range before using
- net: hns3: check vlan id before using it
- net: hns3: fix a return value error in hclge_get_reset_status()
- net/smc: add missing error check in smc_clc_prfx_set()
- net/smc: fix 

[Kernel-packages] [Bug 1944382] Re: Enable runtime power management for yellow carp XHCI

2021-10-04 Thread Alex Hung
** Changed in: amd
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1944382

Title:
  Enable runtime power management for yellow carp XHCI

Status in amd:
  Fix Committed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed

Bug description:
  Alex Hung 

  7:01 PM (1 minute ago)

  to kernel-team
  BugLink: https://bugs.launchpad.net/bugs/1944382

  [Impact]

XHCI controllers of yellow carp by default will not use runtime PM

  [Fix]

Add PCI Device IDs to enable runtime PM

The patch can be found @ https://patchwork.kernel.org/project/linux-
  usb/patch/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/

  [Test]

This is requested and tested by AMD as described in LP:1944382

  [Where problems could occur]

Low risk. This only affects devices of AMD's Yellow Carp.

  == original descriptions ==

  
  Like all XHCI controllers yellow carp XHCI by default will not use runtime PM 
and needs to be added to an allow list.  AMD has validated that XHCI runtime PM 
is safe.

  Please include https://lore.kernel.org/linux-
  usb/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/T/#u in
  OEM-5.14 kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1944382/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1944382] Re: Enable runtime power management for yellow carp XHCI

2021-10-04 Thread Mario Limonciello
I checked this on YC and it works properly.

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1944382

Title:
  Enable runtime power management for yellow carp XHCI

Status in amd:
  New
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed

Bug description:
  Alex Hung 

  7:01 PM (1 minute ago)

  to kernel-team
  BugLink: https://bugs.launchpad.net/bugs/1944382

  [Impact]

XHCI controllers of yellow carp by default will not use runtime PM

  [Fix]

Add PCI Device IDs to enable runtime PM

The patch can be found @ https://patchwork.kernel.org/project/linux-
  usb/patch/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/

  [Test]

This is requested and tested by AMD as described in LP:1944382

  [Where problems could occur]

Low risk. This only affects devices of AMD's Yellow Carp.

  == original descriptions ==

  
  Like all XHCI controllers yellow carp XHCI by default will not use runtime PM 
and needs to be added to an allow list.  AMD has validated that XHCI runtime PM 
is safe.

  Please include https://lore.kernel.org/linux-
  usb/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/T/#u in
  OEM-5.14 kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1944382/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1944382] Re: Enable runtime power management for yellow carp XHCI

2021-10-04 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1005.5
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1944382

Title:
  Enable runtime power management for yellow carp XHCI

Status in amd:
  New
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed

Bug description:
  Alex Hung 

  7:01 PM (1 minute ago)

  to kernel-team
  BugLink: https://bugs.launchpad.net/bugs/1944382

  [Impact]

XHCI controllers of yellow carp by default will not use runtime PM

  [Fix]

Add PCI Device IDs to enable runtime PM

The patch can be found @ https://patchwork.kernel.org/project/linux-
  usb/patch/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/

  [Test]

This is requested and tested by AMD as described in LP:1944382

  [Where problems could occur]

Low risk. This only affects devices of AMD's Yellow Carp.

  == original descriptions ==

  
  Like all XHCI controllers yellow carp XHCI by default will not use runtime PM 
and needs to be added to an allow list.  AMD has validated that XHCI runtime PM 
is safe.

  Please include https://lore.kernel.org/linux-
  usb/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/T/#u in
  OEM-5.14 kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1944382/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1944382] Re: Enable runtime power management for yellow carp XHCI

2021-10-01 Thread Timo Aaltonen
** Also affects: linux-oem-5.14 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.14 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-5.14 (Ubuntu)
   Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1944382

Title:
  Enable runtime power management for yellow carp XHCI

Status in amd:
  New
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed

Bug description:
  Alex Hung 

  7:01 PM (1 minute ago)

  to kernel-team
  BugLink: https://bugs.launchpad.net/bugs/1944382

  [Impact]

XHCI controllers of yellow carp by default will not use runtime PM

  [Fix]

Add PCI Device IDs to enable runtime PM

The patch can be found @ https://patchwork.kernel.org/project/linux-
  usb/patch/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/

  [Test]

This is requested and tested by AMD as described in LP:1944382

  [Where problems could occur]

Low risk. This only affects devices of AMD's Yellow Carp.

  == original descriptions ==

  
  Like all XHCI controllers yellow carp XHCI by default will not use runtime PM 
and needs to be added to an allow list.  AMD has validated that XHCI runtime PM 
is safe.

  Please include https://lore.kernel.org/linux-
  usb/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/T/#u in
  OEM-5.14 kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1944382/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp