[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-09-15 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.13.0-16.16

---
linux (5.13.0-16.16) impish; urgency=medium

  * impish/linux: 5.13.0-16.16 -proposed tracker (LP: #1942611)

  * Miscellaneous Ubuntu changes
- [Config] update toolchain in configs

  * Miscellaneous upstream changes
- Revert "UBUNTU: [Config] Enable CONFIG_UBSAN_BOUNDS"

 -- Andrea Righi   Fri, 03 Sep 2021 16:21:14
+0200

** Changed in: linux (Ubuntu Impish)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-07-20 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1009.10

---
linux-oem-5.13 (5.13.0-1009.10) focal; urgency=medium

  * CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations

linux-oem-5.13 (5.13.0-1007.7) focal; urgency=medium

  * focal/linux-oem-5.13: 5.13.0-1007.7 -proposed tracker (LP: #1934979)

  * intel_pmc_core driver is not probed on ADL (LP: #1934660)
- SAUCE: platform/x86: intel_pmc_core: Add Alderlake support to pmc_core
  driver
- SAUCE: platform/x86: intel_pmc_core: Add Latency Tolerance Reporting (LTR)
  support to Alder Lake
- SAUCE: platform/x86: intel_pmc_core: Add Alder Lake low power mode support
  for pmc_core
- SAUCE: platform/x86: intel_pmc_core: Add GBE Package C10 fix for Alder 
Lake
  PCH

linux-oem-5.13 (5.13.0-1006.6) focal; urgency=medium

  * focal/linux-oem-5.13: 5.13.0-1006.6 -proposed tracker (LP: #1934490)

  * Replace AMD nvme workaround from oem-5.10 with upstream version
(LP: #1930719)
- ACPI: Check StorageD3Enable _DSD property in ACPI code
- ACPI: Add quirks for AMD Renoir/Lucienne CPUs to force the D3 hint

  * Add Thunderbolt support for Intel Alder Lake (LP: #1934240)
- thunderbolt: Add support for Intel Alder Lake

  * Fix Ethernet not working by hotplug - RTL8106E (LP: #1930645)
- SAUCE: r8169: Use PHY_POLL when RTL8106E enable ASPM

  * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle
(LP: #1928242)
- USB: Verify the port status when timeout happens during port suspend
- Revert "USB: Add reset-resume quirk for WD19's Realtek Hub"

  * USB Type-C hotplug event not handled properly in TGL-H system during s2idle
(LP: #1931072)
- drm/i915: Force a TypeC PHY disconnect during suspend/shutdown

  * Miscellaneous Ubuntu changes
- [Config] Sync annotations and config with master

  [ Ubuntu: 5.13.0-11.11 ]

  * impish/linux: 5.13.0-11.11 -proposed tracker (LP: #1933854)
  * Packaging resync (LP: #1786013)
- [Packaging] update variants
  * Support builtin revoked certificates (LP: #1932029)
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys
  * Miscellaneous Ubuntu changes
- [Packaging] Change source package name to linux
  * Miscellaneous upstream changes
- mm/page_alloc: Correct return value of populated elements if bulk array is
  populated

  [ Ubuntu: 5.13.0-10.10 ]

  * impish/linux-unstable: 5.13.0-10.10 -proposed tracker (LP: #1933795)
  * Pixel format change broken for Elgato Cam Link 4K (LP: #1932367)
- media: uvcvideo: Fix pixel format change for Elgato Cam Link 4K
  * initramfs-tools & kernel: use zstd as the default compression method
(LP: #1931725)
- s390/decompressor: correct BOOT_HEAP_SIZE condition
- s390/boot: add zstd support
- [Packaging] use ZSTD to compress s390 kernels
  * Miscellaneous Ubuntu changes
- SAUCE: selftests: tls: fix chacha+bidir tests
- SAUCE: selftests: icmp_redirect: support expected failures
- [Config] update configs and annotations after rebase to 5.13
  * Miscellaneous upstream changes
- tls: prevent oversized sendfile() hangs by ignoring MSG_MORE
  * Rebase to v5.13

 -- Thadeu Lima de Souza Cascardo   Fri, 16 Jul
2021 13:51:37 -0300

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33909

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-07-02 Thread Timo Aaltonen
** Also affects: linux-oem-5.13 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-06-30 Thread Anthony Wong
** Changed in: linux (Ubuntu Impish)
   Status: Fix Released => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-06-29 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-06-22 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-77.86

---
linux (5.4.0-77.86) focal; urgency=medium

  * UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu

  * UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu

linux (5.4.0-76.85) focal; urgency=medium

  * focal/linux: 5.4.0-76.85 -proposed tracker (LP: #1932123)

  * Upstream v5.9 introduced 'module' patches that removed exported symbols
(LP: #1932065)
- SAUCE: Revert "modules: inherit TAINT_PROPRIETARY_MODULE"
- SAUCE: Revert "modules: return licensing information from find_symbol"
- SAUCE: Revert "modules: rename the licence field in struct symsearch to
  license"
- SAUCE: Revert "modules: unexport __module_address"
- SAUCE: Revert "modules: unexport __module_text_address"
- SAUCE: Revert "modules: mark each_symbol_section static"
- SAUCE: Revert "modules: mark find_symbol static"
- SAUCE: Revert "modules: mark ref_module static"

linux (5.4.0-75.84) focal; urgency=medium

  * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
- bpf: Fix mask direction swap upon off reg sign change
- bpf: No need to simulate speculative domain for immediates

  * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle
(LP: #1928242)
- USB: Verify the port status when timeout happens during port suspend

  * CVE-2020-26145
- ath10k: drop fragments with multicast DA for SDIO
- ath10k: add CCMP PN replay protection for fragmented frames for PCIe
- ath10k: drop fragments with multicast DA for PCIe

  * CVE-2020-26141
- ath10k: Fix TKIP Michael MIC verification for PCIe

  * CVE-2020-24588
- mac80211: properly handle A-MSDUs that start with an RFC 1042 header
- cfg80211: mitigate A-MSDU aggregation attacks
- mac80211: drop A-MSDUs on old ciphers
- ath10k: drop MPDU which has discard flag set by firmware for SDIO

  * CVE-2020-26139
- mac80211: do not accept/forward invalid EAPOL frames

  * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases.
- mac80211: extend protection against mixed key and fragment cache attacks

  * CVE-2020-24586 // CVE-2020-24587
- mac80211: prevent mixed key and fragment cache attacks
- mac80211: add fragment cache to sta_info
- mac80211: check defrag PN against current frame
- mac80211: prevent attacks on TKIP/WEP as well

  * CVE-2020-26147
- mac80211: assure all fragments are encrypted

  * raid10: Block discard is very slow, causing severe delays for mkfs and
fstrim operations (LP: #1896578)
- md: add md_submit_discard_bio() for submitting discard bio
- md/raid10: extend r10bio devs to raid disks
- md/raid10: pull the code that wait for blocked dev into one function
- md/raid10: improve raid10 discard request
- md/raid10: improve discard request for far layout
- dm raid: remove unnecessary discard limits for raid0 and raid10

  * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517)
- scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES

  * kvm: properly tear down PV features on hibernate (LP: #1920944)
- x86/kvm: Fix pr_info() for async PF setup/teardown
- x86/kvm: Teardown PV features on boot CPU as well
- x86/kvm: Disable kvmclock on all CPUs on shutdown
- x86/kvm: Disable all PV features on crash
- x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline()

  * Focal update: v5.4.119 upstream stable release (LP: #1929615)
- Bluetooth: verify AMP hci_chan before amp_destroy
- hsr: use netdev_err() instead of WARN_ONCE()
- bluetooth: eliminate the potential race condition when removing the HCI
  controller
- net/nfc: fix use-after-free llcp_sock_bind/connect
- Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL"
- tty: moxa: fix TIOCSSERIAL jiffies conversions
- tty: amiserial: fix TIOCSSERIAL permission check
- USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions
- staging: greybus: uart: fix TIOCSSERIAL jiffies conversions
- USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check
- staging: fwserial: fix TIOCSSERIAL jiffies conversions
- tty: moxa: fix TIOCSSERIAL permission check
- staging: fwserial: fix TIOCSSERIAL permission check
- usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply
- usb: typec: tcpm: Address incorrect values of tcpm psy for pps supply
- usb: typec: tcpm: update power supply once partner accepts
- usb: xhci-mtk: remove or operator for setting schedule parameters
- usb: xhci-mtk: improve bandwidth scheduling with TT
- ASoC: samsung: tm2_wm5110: check o

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-06-22 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.8.0-59.66

---
linux (5.8.0-59.66) groovy; urgency=medium

  * UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu

  * UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu

linux (5.8.0-57.64) groovy; urgency=medium

  * groovy/linux: 5.8.0-57.64 -proposed tracker (LP: #1932047)

  * pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63
(LP: #1931731)
- net: geneve: modify IP header check in geneve6_xmit_skb and 
geneve_xmit_skb

linux (5.8.0-56.63) groovy; urgency=medium

  * groovy/linux: 5.8.0-56.63 -proposed tracker (LP: #1930052)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * scsi: storvsc: Parameterize number hardware queues (LP: #1930626)
- scsi: storvsc: Parameterize number hardware queues

  * CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
- bpf: Fix mask direction swap upon off reg sign change
- bpf: No need to simulate speculative domain for immediates

  * CVE-2021-3490
- SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking 
with
  bitwise ops"
- gpf: Fix alu32 const subreg bound tracking on bitwise operations

  * CVE-2021-3489
- SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of 
read-
  only ringbuf pages"
- bpf: Prevent writable memory-mapping of read-only ringbuf pages

  * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle
(LP: #1928242)
- USB: Verify the port status when timeout happens during port suspend

  * CVE-2020-26145
- ath10k: drop fragments with multicast DA for SDIO
- ath10k: add CCMP PN replay protection for fragmented frames for PCIe
- ath10k: drop fragments with multicast DA for PCIe

  * CVE-2020-26141
- ath10k: Fix TKIP Michael MIC verification for PCIe

  * CVE-2020-24587
- ath11k: Clear the fragment cache during key install

  * CVE-2020-24588
- mac80211: properly handle A-MSDUs that start with an RFC 1042 header
- cfg80211: mitigate A-MSDU aggregation attacks
- mac80211: drop A-MSDUs on old ciphers
- ath10k: drop MPDU which has discard flag set by firmware for SDIO

  * CVE-2020-26139
- mac80211: do not accept/forward invalid EAPOL frames

  * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases.
- mac80211: extend protection against mixed key and fragment cache attacks

  * CVE-2020-24586 // CVE-2020-24587
- mac80211: prevent mixed key and fragment cache attacks
- mac80211: add fragment cache to sta_info
- mac80211: check defrag PN against current frame
- mac80211: prevent attacks on TKIP/WEP as well

  * CVE-2020-26147
- mac80211: assure all fragments are encrypted

  * raid10: Block discard is very slow, causing severe delays for mkfs and
fstrim operations (LP: #1896578)
- md: add md_submit_discard_bio() for submitting discard bio
- md/raid10: extend r10bio devs to raid disks
- md/raid10: pull the code that wait for blocked dev into one function
- md/raid10: improve raid10 discard request
- md/raid10: improve discard request for far layout
- dm raid: remove unnecessary discard limits for raid0 and raid10

  * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517)
- scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES

  * CVE-2021-23133
- sctp: delay auto_asconf init until binding the first addr

  * kvm: properly tear down PV features on hibernate (LP: #1920944)
- x86/kvm: Fix pr_info() for async PF setup/teardown
- x86/kvm: Teardown PV features on boot CPU as well
- x86/kvm: Disable kvmclock on all CPUs on shutdown
- x86/kvm: Disable all PV features on crash
- x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline()

  * CVE-2021-31440
- bpf: Fix propagation of 32 bit unsigned bounds from 64 bit bounds

  * Can't detect intel wifi 6235 (LP: #1920180)
- SAUCE: iwlwifi: add new pci id for 6235

  * [SRU] Patch for flicker and glitching on common LCD display panels, intel
framebuffer (LP: #1925685)
- drm/i915: Try to use fast+narrow link on eDP again and fall back to the 
old
  max strategy on failure
- drm/i915/dp: Use slow and wide link training for everything

  * pmtu.sh from net in ubuntu_kernel_selftests failed with no error message
(LP: #1887661)
- selftests: pmtu.sh: use $ksft_skip for skipped return code

  * IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
(LP: #1926030)
- SAUCE: Revert "media: rc: ite-cir: fix min_timeout calculation"
- SAUCE: Revert "media: rc: fix timeout handling after switch to microsecond
  durations"

  * Groovy update: upstream stable patchset 2021-05-20 (LP: #1929132)
- Input: nspire-keypad - enable interrupt

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-06-22 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.11.0-22.23

---
linux (5.11.0-22.23) hirsute; urgency=medium

  * UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu

  * UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu

linux (5.11.0-20.21) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-20.21 -proposed tracker (LP: #1930854)

  * ath11k WIFI not working in proposed kernel 5.11.0-19-generic (LP: #1930637)
- bus: mhi: core: Download AMSS image from appropriate function

linux (5.11.0-19.20) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-19.20 -proposed tracker (LP: #1930075)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
- bpf: Fix mask direction swap upon off reg sign change
- bpf: No need to simulate speculative domain for immediates

  * AX201 BT will cause system could not enter S0i3 (LP: #1928047)
- SAUCE: drm/i915: Tweaked Wa_14010685332 for all PCHs

  * CVE-2021-3490
- SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking 
with
  bitwise ops"
- gpf: Fix alu32 const subreg bound tracking on bitwise operations

  * CVE-2021-3489
- SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of 
read-
  only ringbuf pages"
- bpf: Prevent writable memory-mapping of read-only ringbuf pages

  * Select correct boot VGA when BIOS doesn't do it properly (LP: #1929217)
- vgaarb: Use ACPI HID name to find integrated GPU

  * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle
(LP: #1928242)
- USB: Verify the port status when timeout happens during port suspend

  * CVE-2020-26145
- ath10k: drop fragments with multicast DA for SDIO
- ath10k: add CCMP PN replay protection for fragmented frames for PCIe
- ath10k: drop fragments with multicast DA for PCIe

  * CVE-2020-26141
- ath10k: Fix TKIP Michael MIC verification for PCIe

  * CVE-2020-24587
- ath11k: Clear the fragment cache during key install

  * CVE-2020-24588
- mac80211: properly handle A-MSDUs that start with an RFC 1042 header
- cfg80211: mitigate A-MSDU aggregation attacks
- mac80211: drop A-MSDUs on old ciphers
- ath10k: drop MPDU which has discard flag set by firmware for SDIO

  * CVE-2020-26139
- mac80211: do not accept/forward invalid EAPOL frames

  * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases.
- mac80211: extend protection against mixed key and fragment cache attacks

  * CVE-2020-24586 // CVE-2020-24587
- mac80211: prevent mixed key and fragment cache attacks
- mac80211: add fragment cache to sta_info
- mac80211: check defrag PN against current frame
- mac80211: prevent attacks on TKIP/WEP as well

  * CVE-2020-26147
- mac80211: assure all fragments are encrypted

  * raid10: Block discard is very slow, causing severe delays for mkfs and
fstrim operations (LP: #1896578)
- md: add md_submit_discard_bio() for submitting discard bio
- md/raid10: extend r10bio devs to raid disks
- md/raid10: pull the code that wait for blocked dev into one function
- md/raid10: improve raid10 discard request
- md/raid10: improve discard request for far layout
- dm raid: remove unnecessary discard limits for raid0 and raid10

  * [SRU][OEM-5.10/H] Fix typec output on AMD Cezanne GPU (LP: #1929646)
- drm/amd/display: use max lb for latency hiding

  * kvm: properly tear down PV features on hibernate (LP: #1920944)
- x86/kvm: Fix pr_info() for async PF setup/teardown
- x86/kvm: Teardown PV features on boot CPU as well
- x86/kvm: Disable kvmclock on all CPUs on shutdown
- x86/kvm: Disable all PV features on crash
- x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline()

  * Add support for AMD wireless button (LP: #1928820)
- platform/x86: hp-wireless: add AMD's hardware id to the supported list

  * Can't detect intel wifi 6235 (LP: #1920180)
- SAUCE: iwlwifi: add new pci id for 6235

  * Speed up resume time on HP laptops (LP: #1929048)
- platform/x86: hp_accel: Avoid invoking _INI to speed up resume

  * Fix kernel panic on Intel Bluetooth (LP: #1928838)
- Bluetooth: Shutdown controller after workqueues are flushed or cancelled

  * build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11,  5.13-rc2
and later (LP: #1921632)
- [Config] enable soundwire audio mach driver

  * [SRU] Patch for flicker and glitching on common LCD display panels, intel
framebuffer (LP: #1925685)
- drm/i915: Try to use fast+narrow link on eDP again and fall back to the 
old
  max strategy on failure
- drm/i915/dp: Use slow and wide link training for everything

  * Fix screen flickering when two 4K 60Hz monitors are connected to AMD Oland

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-06-21 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.11.0-20.21+21.10.1

---
linux (5.11.0-20.21+21.10.1) impish; urgency=medium

  * impish/linux: 5.11.0-20.21+21.10.1 -proposed tracker (LP: #1930056)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  [ Ubuntu: 5.11.0-20.21 ]

  * hirsute/linux: 5.11.0-20.21 -proposed tracker (LP: #1930854)
  * ath11k WIFI not working in proposed kernel 5.11.0-19-generic (LP: #1930637)
- bus: mhi: core: Download AMSS image from appropriate function

  [ Ubuntu: 5.11.0-19.20 ]

  * hirsute/linux: 5.11.0-19.20 -proposed tracker (LP: #1930075)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
- bpf: Fix mask direction swap upon off reg sign change
- bpf: No need to simulate speculative domain for immediates
  * AX201 BT will cause system could not enter S0i3 (LP: #1928047)
- SAUCE: drm/i915: Tweaked Wa_14010685332 for all PCHs
  * CVE-2021-3490
- SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking 
with
  bitwise ops"
- gpf: Fix alu32 const subreg bound tracking on bitwise operations
  * CVE-2021-3489
- SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of 
read-
  only ringbuf pages"
- bpf: Prevent writable memory-mapping of read-only ringbuf pages
  * Select correct boot VGA when BIOS doesn't do it properly (LP: #1929217)
- vgaarb: Use ACPI HID name to find integrated GPU
  * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle
(LP: #1928242)
- USB: Verify the port status when timeout happens during port suspend
  * CVE-2020-26145
- ath10k: drop fragments with multicast DA for SDIO
- ath10k: add CCMP PN replay protection for fragmented frames for PCIe
- ath10k: drop fragments with multicast DA for PCIe
  * CVE-2020-26141
- ath10k: Fix TKIP Michael MIC verification for PCIe
  * CVE-2020-24587
- ath11k: Clear the fragment cache during key install
  * CVE-2020-24588
- mac80211: properly handle A-MSDUs that start with an RFC 1042 header
- cfg80211: mitigate A-MSDU aggregation attacks
- mac80211: drop A-MSDUs on old ciphers
- ath10k: drop MPDU which has discard flag set by firmware for SDIO
  * CVE-2020-26139
- mac80211: do not accept/forward invalid EAPOL frames
  * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases.
- mac80211: extend protection against mixed key and fragment cache attacks
  * CVE-2020-24586 // CVE-2020-24587
- mac80211: prevent mixed key and fragment cache attacks
- mac80211: add fragment cache to sta_info
- mac80211: check defrag PN against current frame
- mac80211: prevent attacks on TKIP/WEP as well
  * CVE-2020-26147
- mac80211: assure all fragments are encrypted
  * raid10: Block discard is very slow, causing severe delays for mkfs and
fstrim operations (LP: #1896578)
- md: add md_submit_discard_bio() for submitting discard bio
- md/raid10: extend r10bio devs to raid disks
- md/raid10: pull the code that wait for blocked dev into one function
- md/raid10: improve raid10 discard request
- md/raid10: improve discard request for far layout
- dm raid: remove unnecessary discard limits for raid0 and raid10
  * [SRU][OEM-5.10/H] Fix typec output on AMD Cezanne GPU (LP: #1929646)
- drm/amd/display: use max lb for latency hiding
  * kvm: properly tear down PV features on hibernate (LP: #1920944)
- x86/kvm: Fix pr_info() for async PF setup/teardown
- x86/kvm: Teardown PV features on boot CPU as well
- x86/kvm: Disable kvmclock on all CPUs on shutdown
- x86/kvm: Disable all PV features on crash
- x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline()
  * Add support for AMD wireless button (LP: #1928820)
- platform/x86: hp-wireless: add AMD's hardware id to the supported list
  * Can't detect intel wifi 6235 (LP: #1920180)
- SAUCE: iwlwifi: add new pci id for 6235
  * Speed up resume time on HP laptops (LP: #1929048)
- platform/x86: hp_accel: Avoid invoking _INI to speed up resume
  * Fix kernel panic on Intel Bluetooth (LP: #1928838)
- Bluetooth: Shutdown controller after workqueues are flushed or cancelled
  * build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11,  5.13-rc2
and later (LP: #1921632)
- [Config] enable soundwire audio mach driver
  * [SRU] Patch for flicker and glitching on common LCD display panels, intel
framebuffer (LP: #1925685)
- drm/i915: Try to use fast+narrow link on eDP again and fall back to the 
old
  max strategy on failure
- drm/i915/dp: Use slow and wide link training for everything
  * Fix screen flickering when two 4K 60Hz monitors are connected to AMD Oland
GFX (LP: #1928361)
- drm/radeon/dpm: Disable sclk switching on Oland when two 4K 60Hz monitors
  are connected
  * Display abnormal on the TGL+

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-06-07 Thread Chris Chiu
** Tags removed: verification-needed-groovy verification-needed-hirsute
** Tags added: verification-done-groovy 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/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-06-05 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the 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-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

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-groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1029.30

---
linux-oem-5.10 (5.10.0-1029.30) focal; urgency=medium

  * focal/linux-oem-5.10: 5.10.0-1029.30 -proposed tracker (LP:
#1930076)

  * CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
- bpf: Fix mask direction swap upon off reg sign change
- bpf: No need to simulate speculative domain for immediates

linux-oem-5.10 (5.10.0-1028.29) focal; urgency=medium

  * focal/linux-oem-5.10: 5.10.0-1028.29 -proposed tracker (LP:
#1929167)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * TGL-H system NV GPU  fallen off the bus after resuming from s2idle with the
external display connected via docking station (LP: #1929166)
- SAUCE: ACPI: avoid NVIDIA GPU fallen with an _OSI string

  * AX201 BT will cause system could not enter S0i3 (LP: #1928047)
- drm/i915: Tweaked Wa_14010685332 for all PCHs

  * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle
(LP: #1928242)
- USB: Verify the port status when timeout happens during port suspend
- Revert "USB: Add reset-resume quirk for WD19's Realtek Hub"

  * Support mic-mute on Dell's platform (LP: #1928750)
- ASoC: rt715: add main capture switch and main capture volume
- ASoC: rt715: remove kcontrols which no longer be used
- ASoC: rt715: modification for code simplicity
- platform/x86: Move all dell drivers to their own subdirectory
- SAUCE: platform/x86: dell-privacy: Add support for Dell hardware privacy
- SAUCE: ASoC: rt715:add micmute led state control supports
- [Config] Update configs for Dell's E-Privacy

linux-oem-5.10 (5.10.0-1027.28) focal; urgency=medium

  * focal/linux-oem-5.10: 5.10.0-1027.28 -proposed tracker (LP:
#1927620)

  * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * On TGL platforms screen shows garbage when browsing website by scrolling
mouse (LP: #1926579)
- SAUCE: drm/i915/display: Disable PSR2 if TGL Display stepping is B1 from 
A0

  * Add s2idle support on AMD Renoir and Cezanne (LP: #1927067)
- drm/amd/display: setup system context in dm_init
- drm/amd/display: add S/G support for Renoir
- drm/amdgpu: drop extra drm_kms_helper_poll_enable/disable calls
- drm/amdgpu: use runpm flag rather than fbcon for kfd runtime suspend (v2)
- drm/amdgpu: reset runpm flag if device suspend fails
- drm/amdgpu: add s0i3 capacity check for s0i3 routine (v2)
- drm/amdgpu: add amdgpu_gfx_state_change_set() set gfx power change entry
  (v2)
- drm/amdgpu: update amdgpu device suspend/resume sequence for s0i3 support
- drm/amd/pm: add gfx_state_change_set() for rn gfx power switch (v2)
- drm/amdgpu: add judgement for suspend/resume sequence
- drm/amdgpu/pm: no need GPU status set since
  mmnbif_gpu_BIF_DOORBELL_FENCE_CNTL added in FSDL
- drm/amdgpu: fix shutdown and poweroff process failed with s0ix
- drm/amdgpu: Only check for S0ix if AMD_PMC is configured
- drm/amdgpu: fix S0ix handling when the CONFIG_AMD_PMC=m
- drm/amdgpu: fix the hibernation suspend with s0ix
- drm/amdgpu: rework S3/S4/S0ix state handling
- drm/amdgpu: don't evict vram on APUs for suspend to ram (v4)
- drm/amdgpu: clean up non-DC suspend/resume handling
- drm/amdgpu: move s0ix check into amdgpu_device_ip_suspend_phase2 (v3)
- drm/amdgpu: re-enable suspend phase 2 for S0ix
- drm/amdgpu/swsmu: skip gfx cgpg on s0ix suspend
- drm/amdgpu: update comments about s0ix suspend/resume
- drm/amdgpu: skip CG/PG for gfx during S0ix
- drm/amdgpu: drop S0ix checks around CG/PG in suspend
- drm/amdgpu: skip kfd suspend/resume for S0ix
- platform/x86: amd-pmc: Add AMD platform support for S2Idle
- platform/x86: amd-pmc: Fix CONFIG_DEBUG_FS check
- platform/x86: amd-pmc: put device on error paths
- ACPI: PM: s2idle: Add AMD support to handle _DSM
- [Config] Enable CONFIG_AMD_PMC=m
- SAUCE: ACPI / idle: override and update c-state latency when not 
conformance
  with s0ix
- SAUCE: usb: pci-quirks: disable D3cold on AMD xhci suspend for s2idle
- SAUCE: PCI: quirks: Quirk PCI d3hot delay for AMD xhci
- SAUCE: Move ASPM quirk flag to MSB
- SAUCE: nvme: put some AMD PCIE downstream NVME device to simple
  suspend/resume path
- SAUCE: platform/x86: Add missing LPS0 functions for AMD
- SAUCE: platform/x86: force LPS0 functions for AMD

  * [SRU] Patch for flicker and glitching on common LCD display panels, intel
framebuffer (LP: #1925685)
- drm/i915: Try to use fast+narrow link on eDP again and fall back to the 
old
  max strategy on failure
- SAUCE: drm/i915/dp: Use slow and wide link training for everything

  * Fix kernel panic at boot o

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-06-02 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the 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-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag 'verification-needed-hirsute' to 'verification-failed-
hirsute'.

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-hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-05-27 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-05-26 Thread Chris Chiu
** 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/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-05-26 Thread Chris Chiu
** Changed in: linux (Ubuntu Focal)
   Status: Invalid => 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/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-05-25 Thread Timo Aaltonen
** Tags added: verification-needed-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-05-20 Thread Timo Aaltonen
** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-05-20 Thread Chris Chiu
** Description changed:

  [SRU Justification]
  
  [Impact]
  All of 3 different WD19(TB/SC/DC) docks have 3 Type-A ports and 2 Type-C 
ports, and there're highspeed Hubs(0bda:5487 and its substream hub 0bda:5413) 
and Superspeed Hubs (0bda:0487 and its downstream hub 0bda:0413). In the bug 
description below, we will refer the 2 highspeed hubs as Hub A and Hub A.3, and 
the 2 superspeed hubs as Hub B and Hub B.3. All devices connected via either 
Type-A or Type-C ports will connect to either Hub A.3 or Hub B.3. If we connect 
a wakup enabled device (keyboard) to a Type-A port, the Hub A.3 will fail to 
activate after exiting s2idle and all downstream devices will not be detected. 
If we have a superspeed device connected to other Type-A port in addition to 
the keyboard, this superspeed device actually connects to Hub B.3, and the Hub 
B.3 will also fails to work after exiting s2idle. If the wakeup enabled device 
connects via Type-C port, there's no such problem.
  
  As a summary, a wakeup enabled device connect to Type-A port will cause
  the failure of Hub A.3 and Hub B.3. Hub B.3 only fails when a wakeup
  enabled device and a superspeed device both connect via Type-A port.
  
  [Fix]
  Before the resume failure, the upstream hub(Hub A or B) will hit the timeout 
problem while doing SetPortFeature(PORT_SUSPEND) to the port of the downstream 
hub (Hub A.3 or Hub B.3). However, the PORT_SUSPEND bit of the wPortStatus is 
actually turned on for the Hub A.3, we simply need to make the kernel believe 
it's already suspended. Then the ClearPortFeature will be done during resume 
and the problem will go away.
  
  The Hub B.3 will be tricky. The PORT_SUSPEND bit is not on after the
- suspend timeout, but we need to reset_resume the Hub B.3 to avoid resume
- failure. It's hard to create a generic fix for it. Because it only
- happens when timeout happens on suspending Hub A.3 and there's a
- superspeed device connecting to Type-A port. I can only reset_resume the
- problematic hub if the timeout happens during suspend and it happens to
- be a Realtek hub.
+ suspend timeout, but it needs the ClearPortFeature(PORT_SUSPEND) for Hub
+ B.3 to avoid resume failure. It doesn't comply with the USB spec so it's
+ hard to create a generic fix for it. Because it only happens when
+ timeout happens on suspending Hub A.3 and there's a superspeed device
+ connecting to Type-A port, we choose to leave it as-is and try to
+ address it in the future.
  
- [Test]
+ [Test Case]
  1. Make sure that the WD19 connects to the laptop
- 2. Connect a USB keyboard and a superspeed USB stick to USB Type-A ports.
+ 2. Connect USB keyboard/mouse to USB Type-A ports.
  3. Suspend the system
  4. Press the Enter key or power button to wake up the system
- 5. Check if the keyboard and USB stick are still working
+ 5. Check if the USB keyboard/mouse are still working
  Repeat 4 and 5 for > 10 times w/o losing any USB devices.
+ 
  
  [Where problems could occur]
  A wakeup enabled device (keyboard) connect to Type-A port will cause the 
failure of Hub A.3 and Hub B.3 during resume. Hub B.3 only fails when a wakeup 
enabled device and a superspeed device both connect via Type-A port. All 
devices connects to Hub A.3 (and B.3 if superspeed device connect via Type-A 
port) will be lost after resume.
  
  [Regression Potential]
  Minimum. The fix is only triggered when timeout happens during USB port 
suspend and it follows the standard USB protocol to do either resume or 
reset_resume.
  
  == Original Bug Description ==
  
  ● Summary
  Plug in USB mouse and USB keyboard to WD19/WD19DC USB ports near LAN port. 
Plug dock into SUT and check USB keyboard and mouse work. SUT enter suspend. 
After 1 min resume SUT, check USB keyboard/mouse function. Sometimes USB 
keyboard/mouse no function.
  
  Isolation:
  1. VP on UMA and Discrete
  2. When issue occur, both front and back port on WD19 can't work using USB 
keyboard/mouse but USB Key.
  
  ● Reproduce Steps
  1.Plug in USB mouse and USB keyboard to WD19/WD19DC USB ports near LAN port.
  2.Plug dock into SUT and check USB keyboard and mouse work.
  3. SUT enter suspend.
  4.After 1 min, resume SUT and check USB keyboard/mouse function.
  5.Sometimes USB keyboard/mouse no function.
  
  ● Results
  ○ Expected Result
  USB mouse or keyboard on dock can use after suspend
  
  ○ Actual Result
  USB mouse or keyboard on dock sometimes no function after suspend
  
  ● Additional Information
  ○ Test Vault ID:60943.011
  ○ SKU:Broadmoor Latitude5421
  ○ BIOS Version:0.3.21
  ○ Image/Manifest:
  dell-bto-focal-fossa-pidgeot-14-X79-20210106-3.iso
  dell-bto-focal-fossa-pidgeot-14-X81-20210121-6.iso
  ○ CPU:TGL ES
  ○ GPU:Intel pGFX 2020
  ○ Failure rate:F/R: 2/2 units, 1/10 times
  ○ WD19 dock, Dock DFU: 1.0.15
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  263

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-05-15 Thread Chris Chiu
upstream patch got ack from https://lkml.org/lkml/2021/5/14/619.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-05-15 Thread Chris Chiu
** Description changed:

  [SRU Justification]
  
  [Impact]
- All of 3 different WD19(TB/SC/DC) docks have 3 Type-A ports and 2 Type-C 
ports, and there're highspeed Hubs(0bda:5487 and its substream hub 0bda:5413) 
and Superspeed Hubs (0bda:0413 and its downstream hub 0bda:5413). In the bug 
description below, we will refer the 2 highspeed hubs as Hub A and Hub A.3, and 
the 2 superspeed hubs as Hub B and Hub B.3. All devices connected via either 
Type-A or Type-C ports will connect to either Hub A.3 or Hub B.3. If we connect 
a wakup enabled device (keyboard) to a Type-A port, the Hub A.3 will fail to 
activate after exiting s2idle and all downstream devices will not be detected. 
If we have a superspeed device connected to other Type-A port in addition to 
the keyboard, this superspeed device actually connects to Hub B.3, and the Hub 
B.3 will also fails to work after exiting s2idle. If the wakeup enabled device 
connects via Type-C port, there's no such problem.
+ All of 3 different WD19(TB/SC/DC) docks have 3 Type-A ports and 2 Type-C 
ports, and there're highspeed Hubs(0bda:5487 and its substream hub 0bda:5413) 
and Superspeed Hubs (0bda:0487 and its downstream hub 0bda:0413). In the bug 
description below, we will refer the 2 highspeed hubs as Hub A and Hub A.3, and 
the 2 superspeed hubs as Hub B and Hub B.3. All devices connected via either 
Type-A or Type-C ports will connect to either Hub A.3 or Hub B.3. If we connect 
a wakup enabled device (keyboard) to a Type-A port, the Hub A.3 will fail to 
activate after exiting s2idle and all downstream devices will not be detected. 
If we have a superspeed device connected to other Type-A port in addition to 
the keyboard, this superspeed device actually connects to Hub B.3, and the Hub 
B.3 will also fails to work after exiting s2idle. If the wakeup enabled device 
connects via Type-C port, there's no such problem.
  
  As a summary, a wakeup enabled device connect to Type-A port will cause
  the failure of Hub A.3 and Hub B.3. Hub B.3 only fails when a wakeup
  enabled device and a superspeed device both connect via Type-A port.
  
  [Fix]
  Before the resume failure, the upstream hub(Hub A or B) will hit the timeout 
problem while doing SetPortFeature(PORT_SUSPEND) to the port of the downstream 
hub (Hub A.3 or Hub B.3). However, the PORT_SUSPEND bit of the wPortStatus is 
actually turned on for the Hub A.3, we simply need to make the kernel believe 
it's already suspended. Then the ClearPortFeature will be done during resume 
and the problem will go away.
  
  The Hub B.3 will be tricky. The PORT_SUSPEND bit is not on after the
  suspend timeout, but we need to reset_resume the Hub B.3 to avoid resume
  failure. It's hard to create a generic fix for it. Because it only
  happens when timeout happens on suspending Hub A.3 and there's a
  superspeed device connecting to Type-A port. I can only reset_resume the
  problematic hub if the timeout happens during suspend and it happens to
  be a Realtek hub.
  
  [Test]
  1. Make sure that the WD19 connects to the laptop
  2. Connect a USB keyboard and a superspeed USB stick to USB Type-A ports.
  3. Suspend the system
  4. Press the Enter key or power button to wake up the system
  5. Check if the keyboard and USB stick are still working
  Repeat 4 and 5 for > 10 times w/o losing any USB devices.
  
  [Where problems could occur]
  A wakeup enabled device (keyboard) connect to Type-A port will cause the 
failure of Hub A.3 and Hub B.3 during resume. Hub B.3 only fails when a wakeup 
enabled device and a superspeed device both connect via Type-A port. All 
devices connects to Hub A.3 (and B.3 if superspeed device connect via Type-A 
port) will be lost after resume.
  
  [Regression Potential]
  Minimum. The fix is only triggered when timeout happens during USB port 
suspend and it follows the standard USB protocol to do either resume or 
reset_resume.
  
  == Original Bug Description ==
  
  ● Summary
  Plug in USB mouse and USB keyboard to WD19/WD19DC USB ports near LAN port. 
Plug dock into SUT and check USB keyboard and mouse work. SUT enter suspend. 
After 1 min resume SUT, check USB keyboard/mouse function. Sometimes USB 
keyboard/mouse no function.
  
  Isolation:
  1. VP on UMA and Discrete
  2. When issue occur, both front and back port on WD19 can't work using USB 
keyboard/mouse but USB Key.
  
  ● Reproduce Steps
  1.Plug in USB mouse and USB keyboard to WD19/WD19DC USB ports near LAN port.
  2.Plug dock into SUT and check USB keyboard and mouse work.
  3. SUT enter suspend.
  4.After 1 min, resume SUT and check USB keyboard/mouse function.
  5.Sometimes USB keyboard/mouse no function.
  
  ● Results
  ○ Expected Result
  USB mouse or keyboard on dock can use after suspend
  
  ○ Actual Result
  USB mouse or keyboard on dock sometimes no function after suspend
  
  ● Additional Information
  ○ Test Vault ID:60943.011
  ○ SKU:Broadmoor Latitude5421
  ○ BIOS Version:0.3.21
  ○ Image/

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-05-12 Thread Chris Chiu
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Invalid

** Also affects: linux (Ubuntu Impish)
   Importance: Undecided
   Status: Incomplete

** Also affects: linux-oem-5.10 (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: linux (Ubuntu Impish)
   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/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-05-12 Thread Chris Chiu
apport information

** Tags added: apport-collected focal

** Description changed:

  [SRU Justification]
  
  [Impact]
  All of 3 different WD19(TB/SC/DC) docks have 3 Type-A ports and 2 Type-C 
ports, and there're highspeed Hubs(0bda:5487 and its substream hub 0bda:5413) 
and Superspeed Hubs (0bda:0413 and its downstream hub 0bda:5413). In the bug 
description below, we will refer the 2 highspeed hubs as Hub A and Hub A.3, and 
the 2 superspeed hubs as Hub B and Hub B.3. All devices connected via either 
Type-A or Type-C ports will connect to either Hub A.3 or Hub B.3. If we connect 
a wakup enabled device (keyboard) to a Type-A port, the Hub A.3 will fail to 
activate after exiting s2idle and all downstream devices will not be detected. 
If we have a superspeed device connected to other Type-A port in addition to 
the keyboard, this superspeed device actually connects to Hub B.3, and the Hub 
B.3 will also fails to work after exiting s2idle. If the wakeup enabled device 
connects via Type-C port, there's no such problem.
  
  As a summary, a wakeup enabled device connect to Type-A port will cause
  the failure of Hub A.3 and Hub B.3. Hub B.3 only fails when a wakeup
  enabled device and a superspeed device both connect via Type-A port.
  
  [Fix]
  Before the resume failure, the upstream hub(Hub A or B) will hit the timeout 
problem while doing SetPortFeature(PORT_SUSPEND) to the port of the downstream 
hub (Hub A.3 or Hub B.3). However, the PORT_SUSPEND bit of the wPortStatus is 
actually turned on for the Hub A.3, we simply need to make the kernel believe 
it's already suspended. Then the ClearPortFeature will be done during resume 
and the problem will go away.
  
  The Hub B.3 will be tricky. The PORT_SUSPEND bit is not on after the
  suspend timeout, but we need to reset_resume the Hub B.3 to avoid resume
  failure. It's hard to create a generic fix for it. Because it only
  happens when timeout happens on suspending Hub A.3 and there's a
  superspeed device connecting to Type-A port. I can only reset_resume the
  problematic hub if the timeout happens during suspend and it happens to
  be a Realtek hub.
  
  [Test]
  1. Make sure that the WD19 connects to the laptop
  2. Connect a USB keyboard and a superspeed USB stick to USB Type-A ports.
  3. Suspend the system
  4. Press the Enter key or power button to wake up the system
  5. Check if the keyboard and USB stick are still working
  Repeat 4 and 5 for > 10 times w/o losing any USB devices.
  
  [Where problems could occur]
  A wakeup enabled device (keyboard) connect to Type-A port will cause the 
failure of Hub A.3 and Hub B.3 during resume. Hub B.3 only fails when a wakeup 
enabled device and a superspeed device both connect via Type-A port. All 
devices connects to Hub A.3 (and B.3 if superspeed device connect via Type-A 
port) will be lost after resume.
  
  [Regression Potential]
  Minimum. The fix is only triggered when timeout happens during USB port 
suspend and it follows the standard USB protocol to do either resume or 
reset_resume.
  
  == Original Bug Description ==
  
  ● Summary
  Plug in USB mouse and USB keyboard to WD19/WD19DC USB ports near LAN port. 
Plug dock into SUT and check USB keyboard and mouse work. SUT enter suspend. 
After 1 min resume SUT, check USB keyboard/mouse function. Sometimes USB 
keyboard/mouse no function.
  
  Isolation:
  1. VP on UMA and Discrete
  2. When issue occur, both front and back port on WD19 can't work using USB 
keyboard/mouse but USB Key.
  
  ● Reproduce Steps
  1.Plug in USB mouse and USB keyboard to WD19/WD19DC USB ports near LAN port.
  2.Plug dock into SUT and check USB keyboard and mouse work.
  3. SUT enter suspend.
  4.After 1 min, resume SUT and check USB keyboard/mouse function.
  5.Sometimes USB keyboard/mouse no function.
  
  ● Results
  ○ Expected Result
  USB mouse or keyboard on dock can use after suspend
  
  ○ Actual Result
  USB mouse or keyboard on dock sometimes no function after suspend
  
  ● Additional Information
  ○ Test Vault ID:60943.011
  ○ SKU:Broadmoor Latitude5421
  ○ BIOS Version:0.3.21
  ○ Image/Manifest:
  dell-bto-focal-fossa-pidgeot-14-X79-20210106-3.iso
  dell-bto-focal-fossa-pidgeot-14-X81-20210121-6.iso
  ○ CPU:TGL ES
  ○ GPU:Intel pGFX 2020
  ○ Failure rate:F/R: 2/2 units, 1/10 times
  ○ WD19 dock, Dock DFU: 1.0.15
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.16
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  u  2632 F pulseaudio
+  /dev/snd/controlC0:  u  2632 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistributionChannelDescriptor:
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-focal-amd64-20200502-85+fossa-pidgey+X90
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-05-12 Thread Chris Chiu
** Tags added: originate-from-1921742

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-05-12 Thread Chris Chiu
** Tags added: oem-priority originate-from-1917005 somerville

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

2021-05-12 Thread Chris Chiu
** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.10 (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 (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.10 (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => Chris Chiu (mschiu77)

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Chris Chiu (mschiu77)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Chris Chiu (mschiu77)

** Changed in: linux-oem-5.10 (Ubuntu Focal)
 Assignee: (unassigned) => Chris Chiu (mschiu77)

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: In Progress => Confirmed

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Confirmed

** Changed in: linux (Ubuntu Groovy)
   Status: In Progress => Confirmed

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Confirmed

** Changed in: linux (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Groovy)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Hirsute)
   Status: Confirmed => In Progress

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: Confirmed => 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/1928242

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs