[cc += Evert]
On Fri, Dec 06, 2024 at 07:12:37PM +0100, Niklas Schnelle wrote:
> On Fri, 2024-10-18 at 17:47 +0300, Ilpo Järvinen wrote:
> > This mostly reverts the commit b4c7d2076b4e ("PCI/LINK: Remove
> > bandwidth notification"). An upcoming commit extends this driver
> > building PCIe bandwidth controller on top of it.
> >
> > The PCIe bandwidth notification were first added in the commit
> > e8303bb7a75c ("PCI/LINK: Report degraded links via link bandwidth
> > notification") but later had to be removed. The significant changes
> > compared with the old bandwidth notification driver include:
[...]
> I bisected a v6.13-rc1 boot hang on my personal workstation to this
> patch. Sadly I don't have much details like a panic or so because the
> boot hangs before any kernel messages, or at least they're not visible
> long enough to see. I haven't yet looked into the code as I wanted to
> raise awareness first. Since the commit doesn't revert cleanly on
> v6.13-rc1 I also haven't tried that yet.
Hi Niklas,
another regression caused by bandwidth control was reported,
this time it's a hang on shutdown (instead of on boot) and
this time we root-caused it instead of just working around it.
Here's the proposed fix:
https://lore.kernel.org/r/0ee5faf5395cad8d29fb66e1ec444c8d882a4201.1735852688.git.lukas@xxxxxxxxx/
Could you test this on top of v6.13-rc1 (or any other rc which
does not include 774c71c52aa4 ("PCI/bwctrl: Enable only if more
than one speed is supported")?
I suspect that it may fix the issue you were seeing as well and
I'm curious whether that suspicion is correct.
Thanks!
Lukas
