[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2024-02-29 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.


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: kernel-spammed-jammy-linux-mtk-v2 
verification-needed-jammy-linux-mtk

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-04-11 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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-jammy' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-nvidia-5.19 verification-needed-jammy

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-03-30 Thread Chris Chiu
** Tags removed: verification-needed-focal verification-needed-jammy 
verification-needed-kinetic
** Tags added: verification-done-focal verification-done-jammy 
verification-done-kinetic

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-03-30 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-azure/5.19.0-1023.24
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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

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: kernel-spammed-kinetic-linux-azure

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-03-29 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-aws/5.19.0-1023.24
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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

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 removed: verification-done-kinetic
** Tags added: kernel-spammed-kinetic-linux-aws verification-needed-kinetic

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-03-22 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.19.0-38.39

---
linux (5.19.0-38.39) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088)

  * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assigning access cache timestamp

linux (5.19.0-37.38) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305)

  * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516)
- SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457

  * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161)
- platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table

  * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19
(LP: #2000709)
- selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor
  compatibility

  * rtcpie in timers from ubuntu_kernel_selftests randomly failing
(LP: #1814234)
- SAUCE: selftest: rtcpie: Force passing unreliable subtest

  * CVE-2023-0469
- io_uring/filetable: fix file reference underflow

  * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546)
- selftests: net: return non-zero for failures reported in
  arp_ndisc_evict_nocarrier

  * Make cm32181 sensor work after system suspend (LP: #1981773)
- iio: light: cm32181: Add PM support

  * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock
(LP: #1991366)
- PCI: Fix used_buses calculation in pci_scan_child_bus_extend()
- PCI: Pass available buses even if the bridge is already configured
- PCI: Move pci_assign_unassigned_root_bus_resources()
- PCI: Fix whitespace and indentation
- PCI: Fix typo in pci_scan_child_bus_extend()

  * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on
J-oem-5.17 / K (LP: #1968310)
- selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier

  * Screen freeze after resuming from suspend (nvme0: I/O timeout)
(LP: #1996048)
- PCI: vmd: Disable MSI remapping after suspend

  * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode
(LP: #1993561)
- drm/i915/display: Drop check for doublescan mode in modevalid
- drm/i915/display: Prune Interlace modes for Display >=12

  * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19
(Missing nat6to4 helper) (LP: #2000708)
- selftests/net: mv bpf/nat6to4.c to net folder

  * selftests/.../nat6to4  breaks the selftests build (LP: #1996536)
- selftests: net: Add cross-compilation support for BPF programs
- selftests: net: Fix O=dir builds

  * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue.
- ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF

  * CVE-2022-4382
- USB: gadgetfs: Fix race between mounting and unmounting

  * CVE-2022-2196
- KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS

  * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447)
- selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs

  * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602)
- clk: generalize devm_clk_get() a bit
- clk: Provide new devm_clk helpers for prepared and enabled clocks
- mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse()
- arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4
  series
- arm: dts: rockchip: fix node name for hym8563 rtc
- arm: dts: rockchip: remove clock-frequency from rtc
- ARM: dts: rockchip: fix ir-receiver node names
- arm64: dts: rockchip: fix ir-receiver node names
- ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name
- fs: use acquire ordering in __fget_light()
- ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels
- ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation
- ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register
- spi: mediatek: Fix DEVAPC Violation at KO Remove
- ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188
- ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine
  transitions
- 9p/fd: Use P9_HDRSZ for header size
- regulator: slg51000: Wait after asserting CS pin
- ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event
- btrfs: send: avoid unaligned encoded writes when attempting to clone range
- ASoC: soc-pcm: Add NULL check in BE reparenting
- regulator: twl6030: fix get status of twl6032 regulators
- fbcon: Use kzalloc() in fbcon_prepare_logo()
- usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer
- 9p/xen: check logical size for buffer size
- net: usb: qmi_wwan: add u-blox 0x1342 composition
- mm/khugepaged: take the right locks for page table retraction
- mm/khugepaged: fix GUP-fast 

[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-03-16 Thread Chris Chiu
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-03-03 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.19.0-37.38 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

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: kernel-spammed-kinetic-linux verification-needed-kinetic

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-02-21 Thread Luke Nowakowski-Krijger
Applied patches to kinetic:linux except the one ("Revert "PCI:
Distribute available resources for root buses, too"") patch that was
reverted upstream.

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

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-02-16 Thread Luke Nowakowski-Krijger
** Changed in: linux (Ubuntu Kinetic)
   Status: New => Fix Committed

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

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-01-30 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1030.34~20.04.1 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: kernel-spammed-focal-linux-aws-5.15

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  New
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-01-30 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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-jammy' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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: kernel-spammed-jammy-linux-bluefield

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  New
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-01-27 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~20.04.1 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: kernel-spammed-focal-linux-azure-5.15

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  New
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-01-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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: kernel-spammed-jammy-linux-aws

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  New
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-01-17 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-azure/5.15.0-1032.39
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-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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: kernel-spammed-jammy-linux-azure

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  New
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-01-17 Thread Anthony Wong
** Changed in: linux (Ubuntu Kinetic)
 Assignee: (unassigned) => Chris Chiu (mschiu77)

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  New
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-01-16 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
gke-5.15/5.15.0-1025.30~20.04.1 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: kernel-spammed-focal-linux-gke-5.15 verification-needed-focal

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  New
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-01-10 Thread Anthony Wong
** Changed in: linux-oem-6.0 (Ubuntu Kinetic)
   Status: New => Invalid

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

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  New
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-01-05 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-57.63

---
linux (5.15.0-57.63) jammy; urgency=medium

  * jammy/linux: 5.15.0-57.63 -proposed tracker (LP: #1997737)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * Expose built-in trusted and revoked certificates (LP: #1996892)
- [Packaging] Expose built-in trusted and revoked certificates

  * TEE Support for CCP driver (LP: #1991608)
- crypto: ccp: Add support for TEE for PCI ID 0x14CA

  * alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41
codec (LP: #1996121)
- ASoC: cs35l41: Add one more variable in the debug log
- ASoC: cs35l41: Fix an out-of-bounds access in otp_packed_element_t

  * Fix ath11k deadlock on WCN6855 (LP: #1995041)
- wifi: ath11k: avoid deadlock during regulatory update in
  ath11k_regd_update()

  * [UBUNTU 20.04] boot: Add s390x secure boot trailer (LP: #1996071)
- s390/boot: add secure boot trailer

  * Fix rfkill causing soft blocked wifi (LP: #1996198)
- platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi

  * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock
(LP: #1991366)
- PCI: Fix used_buses calculation in pci_scan_child_bus_extend()
- PCI: Pass available buses even if the bridge is already configured
- PCI: Move pci_assign_unassigned_root_bus_resources()
- PCI: Distribute available resources for root buses, too
- PCI: Fix whitespace and indentation
- PCI: Fix typo in pci_scan_child_bus_extend()

  * md: Replace snprintf with scnprintf (LP: #1993315)
- md: Replace snprintf with scnprintf

  * input/keyboard: the keyboard on some Asus laptops can't work (LP: #1992266)
- ACPI: resource: Skip IRQ override on Asus Vivobook K3402ZA/K3502ZA
- ACPI: resource: Add ASUS model S5402ZA to quirks

  * Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU
(LP: #1991365)
- tools/power turbostat: Add support for RPL-S

  * pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal),
type=Transaction Layer, (Requester ID) (LP: #1988797)
- PCI/PTM: Cache PTM Capability offset
- PCI/PTM: Add pci_upstream_ptm() helper
- PCI/PTM: Separate configuration and enable
- PCI/PTM: Add pci_suspend_ptm() and pci_resume_ptm()
- PCI/PTM: Move pci_ptm_info() body into its only caller
- PCI/PTM: Preserve RsvdP bits in PTM Control register
- PCI/PTM: Reorder functions in logical order
- PCI/PTM: Consolidate PTM interface declarations
- PCI/PM: Always disable PTM for all devices during suspend
- PCI/PM: Simplify pci_pm_suspend_noirq()

  * Fix RPL-S support on powercap/intel_rapl (LP: #1990161)
- x86/cpu: Drop spurious underscore from RAPTOR_LAKE #define
- x86/cpu: Add new Alderlake and Raptorlake CPU model numbers
- x86/cpu: Add new Raptor Lake CPU model number
- powercap: intel_rapl: add support for RaptorLake
- powercap: intel_rapl: Add support for RAPTORLAKE_P
- powercap: intel_rapl: Add support for RAPTORLAKE_S

  * AMD Yellow Carp system hang on HDMI plug in/out over HP hook2 docking
(LP: #1991974)
- drm/amd/display: Fix for link encoder access for MST.
- drm/amd/display: Fix MST link encoder availability check.
- drm/amd/display: FEC configuration for dpia links
- drm/amd/display: FEC configuration for dpia links in MST mode
- drm/amd/display: Add work around for tunneled MST.

  * Jammy update: v5.15.74 upstream stable release (LP: #1995638)
- nilfs2: fix use-after-free bug of struct nilfs_root
- nilfs2: fix leak of nilfs_root in case of writer thread creation failure
- nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
- ceph: don't truncate file in atomic_open
- random: restore O_NONBLOCK support
- random: clamp credited irq bits to maximum mixed
- ALSA: hda: Fix position reporting on Poulsbo
- efi: Correct Macmini DMI match in uefi cert quirk
- USB: serial: qcserial: add new usb-id for Dell branded EM7455
- Revert "powerpc/rtas: Implement reentrant rtas call"
- Revert "crypto: qat - reduce size of mapped region"
- random: avoid reading two cache lines on irq randomness
- random: use expired timer rather than wq for mixing fast pool
- Input: xpad - add supported devices as contributed on github
- Input: xpad - fix wireless 360 controller breaking after suspend
- misc: pci_endpoint_test: Aggregate params checking for xfer
- misc: pci_endpoint_test: Fix pci_endpoint_test_{copy,write,read}() panic
- Linux 5.15.74

  * Jammy update: v5.15.73 upstream stable release (LP: #1995637)
- Makefile.extrawarn: Move -Wcast-function-type-strict to W=1
- docs: update mediator information in CoC docs
- xsk: Inherit need_wakeup flag for shared sockets
- mm: gup: fix the fast GUP race against THP 

[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2023-01-04 Thread Anthony Wong
** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.17 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.0 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  New
Status in linux-oem-5.17 source package in Kinetic:
  New
Status in linux-oem-6.0 source package in Kinetic:
  New

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-12-15 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1025.26

---
linux-oem-5.17 (5.17.0-1025.26) jammy; urgency=medium

  * jammy/linux-oem-5.17: 5.17.0-1025.26 -proposed tracker (LP:
#1997739)

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

  * Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
(LP: #1998905)
- SAUCE: ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and 
lock.

  * Micron NVME storage failure [1344,5407] (LP: #1998883)
- nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH

  * CVE-2022-42896
- Bluetooth: L2CAP: Fix l2cap_global_chan_by_psm

  * Fix AMD-PState driver for Genoa CPU (LP: #1998106)
- Documentation: amd-pstate: add tracer tool introduction
- Documentation: amd-pstate: grammar and sentence structure updates
- Documentation: amd-pstate: Add unit test introduction
- cpufreq: amd-pstate: cpufreq: amd-pstate: reset MSR_AMD_PERF_CTL register 
at
  init
- cpufreq: amd-pstate: change amd-pstate driver to be built-in type
- cpufreq: amd-pstate: add amd-pstate driver parameter for mode selection
- Documentation: amd-pstate: add driver working mode introduction
- Documentation: add amd-pstate kernel command line options

  * Mediatek WLAN RZ616(MT7922) SAR table control (LP: #1997200)
- mt76: add 6 GHz band support in mt76_sar_freq_ranges
- mt76: mt7921: introduce ACPI SAR support
- mt76: mt7921: introduce ACPI SAR config in tx power
- wifi: mt76: mt7921: fix use after free in mt7921_acpi_read()

  * Add cs35l41 firmware loading support (LP: #1995957)
- ASoC: cs35l41: Remove unnecessary param
- ALSA: cs35l41: Unify hardware configuration
- ALSA: cs35l41: Check hw_config before using it
- ALSA: cs35l41: Move cs35l41_gpio_config to shared lib
- ALSA: hda: cs35l41: Fix I2S params comments
- ALSA: hda: cs35l41: Always configure the DAI
- ALSA: hda: cs35l41: Add Boost type flag
- ALSA: hda: cs35l41: Put the device into safe mode for external boost
- ALSA: hda: cs35l41: Mute the device before shutdown
- ALSA: cs35l41: Enable Internal Boost in shared lib
- ALSA: hda: cs35l41: Move boost config to initialization code
- ALSA: hda: cs35l41: Remove cs35l41_hda_reg_sequence struct
- ALSA: hda: cs35l41: Reorganize log for playback actions
- ALSA: hda: cs35l41: Handle all external boost setups the same way
- ALSA: hda: cs35l41: Move external boost handling to lib for ASoC use
- ASoC: cs35l41: Document CS35l41 External Boost
- ASoC: cs35l41: Support external boost
- ALSA: hda: cs35l41: Fix error in spi cs35l41 hda driver name
- ALSA: hda: cs35l41: Set Speaker Position for CLSA0100 Laptop
- ALSA: hda: cs35l41: Remove Set Channel Map api from binding
- ALSA: hda: cs35l41: Add Support for Interrupts
- ALSA: hda: cs35l41: Enable GPIO2 Interrupt for CLSA0100 laptops
- ASoC: cs35l41: Move cs35l41_set_cspl_mbox_cmd to shared code
- ASoC: cs35l41: Move cs35l41 fs errata into shared code
- ASoC: cs35l41: Move cs_dsp config struct into shared code
- ALSA: hda: cs35l41: Add Amp Name based on channel and index
- ASoC: cs35l41: Move cs35l41 exit hibernate function into shared code
- ASoC: cs35l41: Add common cs35l41 enter hibernate function
- ASoC: cs35l41: Do not print error when waking from hibernation
- ALSA: hda: cs35l41: Don't dereference fwnode handle
- ALSA: hda: cs35l41: Allow compilation test on non-ACPI configurations
- ALSA: hda: cs35l41: Drop wrong use of ACPI_PTR()
- ALSA: hda: cs35l41: Consolidate selections under SND_HDA_SCODEC_CS35L41
- ALSA: hda: hda_cs_dsp_ctl: Add Library to support CS_DSP ALSA controls
- ALSA: hda: hda_cs_dsp_ctl: Add apis to write the controls directly
- ALSA: hda: cs35l41: Save codec object inside component struct
- ALSA: hda: cs35l41: Add initial DSP support and firmware loading
- ALSA: hda: cs35l41: Save Subsystem ID inside CS35L41 Driver
- ALSA: hda: cs35l41: Support reading subsystem id from ACPI
- ALSA: hda: cs35l41: Support multiple load paths for firmware
- ALSA: hda: cs35l41: Support Speaker ID for laptops
- ALSA: hda: cs35l41: Support Hibernation during Suspend
- ALSA: hda: cs35l41: Read Speaker Calibration data from UEFI variables
- ALSA: hda: hda_cs_dsp_ctl: Add fw id strings
- ALSA: hda: cs35l41: Add defaulted values into dsp bypass config sequence
- ALSA: hda: cs35l41: Support Firmware switching and reloading
- ALSA: hda: cs35l41: Add module parameter to control firmware load
- Revert "ALSA: hda: cs35l41: Allow compilation test on non-ACPI
  configurations"
- [Config] updateconfigs for SND_HDA_CS_DSP_CONTROLS

  * Screen freeze after resuming from suspend (nvme0: I/O timeout)
(LP: #1996048)
- SAUCE: PCI: vmd: Disable MSI remapping after suspend

  * Screen cannot 

[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-12-12 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-nvidia verification-needed-jammy

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-12-11 Thread Chris Chiu
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-12-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-oem-5.17/5.17.0-1025.26
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-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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: kernel-spammed-jammy-linux-oem-5.17

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-12-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.15.0-57.63 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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: kernel-spammed-jammy-linux verification-needed-jammy

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-11-10 Thread Stefan Bader
** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Medium

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

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-11-10 Thread Timo Aaltonen
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-10-26 Thread Timo Aaltonen
fixed in 6.0 1006

so the revert needs a follow-up bug..

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: In Progress => Fix Released

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-10-26 Thread Timo Aaltonen
or maybe not, just reopen this for 6.0 when the reverts are sent

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-10-25 Thread Mario Limonciello
FYI - one of those commits has reverted in 6.1 due to regressions.

See this commit:
5632e2beaf9d5 ("Revert "PCI: Distribute available resources for root buses, 
too"")

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-10-24 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1006.6
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-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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!

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-10-20 Thread Chris Chiu
** No longer affects: linux-hwe-5.15 (Ubuntu Jammy)

** No longer affects: linux-hwe-5.15 (Ubuntu)

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-10-20 Thread Chris Chiu
** Also affects: linux-hwe-5.15 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe-5.15 package in Ubuntu:
  New
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-hwe-5.15 source package in Jammy:
  New
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-10-20 Thread Chris Chiu
** Changed in: linux (Ubuntu Jammy)
   Status: Invalid => In Progress

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-10-04 Thread Timo Aaltonen
should end up in 6.1

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

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

** No longer affects: linux (Ubuntu Kinetic)

** No longer affects: linux-oem-5.17 (Ubuntu Kinetic)

** No longer affects: linux-oem-6.0 (Ubuntu Kinetic)

** Changed in: linux (Ubuntu)
   Status: Invalid => Triaged

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-10-02 Thread Chris Chiu
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
   Status: New => In Progress

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

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  New
Status in linux-oem-6.0 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  New
Status in linux-oem-6.0 source package in Kinetic:
  New

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-09-30 Thread Chris Chiu
** Description changed:

  [SRU Justification]
  
  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
- the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found. 
+ the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.
  
  [Fix]
- Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same.
+ Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.
  
  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.
  
  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  New
Status in linux-oem-6.0 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  New
Status in linux-oem-6.0 source package in Jammy:
  New
Status in linux source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  New
Status in linux-oem-6.0 source package in Kinetic:
  New

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

2022-09-30 Thread Chris Chiu
** Tags added: oem-priority originate-from-1961654 somerville

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  New
Status in linux-oem-6.0 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  New
Status in linux-oem-6.0 source package in Jammy:
  New
Status in linux source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  New
Status in linux-oem-6.0 source package in Kinetic:
  New

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found. 

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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