From: Lukas Wunner <lukas@wunner.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [Bug 219906] New: Kernel Oops in pcie_update_link_speed when hotplugging TB4 dock on x870e / kernel 6.14.0-rc7
Date: Fri, 21 Mar 2025 20:35:52 +0100 [thread overview]
Message-ID: <Z92_mHU3CcTXdaKV@wunner.de> (raw)
In-Reply-To: <20250321191504.GA1139362@bhelgaas>
On Fri, Mar 21, 2025 at 02:15:04PM -0500, Bjorn Helgaas wrote:
> On Fri, Mar 21, 2025 at 06:30:40PM +0000, bugzilla-daemon@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=219906
> >
> > Bug ID: 219906
> > Summary: Kernel Oops in pcie_update_link_speed when hotplugging
> > TB4 dock on x870e / kernel 6.14.0-rc7
>
> Do you know whether this is a regression? Does any kernel work
> correctly on the system in question?
This is a regression caused by
commit 665745f274870c921020f610e2c99a3b1613519b
Author: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Date: Fri Oct 18 17:47:52 2024 +0300
PCI/bwctrl: Re-add BW notification portdrv as PCIe BW controller
which went into v6.13-rc1. It can be overcome by duplicating
commit 62e4492c3063048a163d238cd1734273f2fc757d
Author: Andreas Noever <andreas.noever@gmail.com>
Date: Mon Jun 9 23:03:32 2014 +0200
PCI: Prevent NULL dereference during pciehp probe
in the bandwidth controller driver.
I can submit a patch tomorrow unless you or Ilpo beat me to it.
(Sorry, I'm still a little sleep deprived today after OSPM Summit.)
Thanks,
Lukas
next prev parent reply other threads:[~2025-03-21 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-219906-41252@https.bugzilla.kernel.org/>
2025-03-21 19:15 ` [Bug 219906] New: Kernel Oops in pcie_update_link_speed when hotplugging TB4 dock on x870e / kernel 6.14.0-rc7 Bjorn Helgaas
2025-03-21 19:35 ` Lukas Wunner [this message]
2025-03-21 19:41 ` Wouter Bijlsma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z92_mHU3CcTXdaKV@wunner.de \
--to=lukas@wunner.de \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-pci@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox