From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Wouter Bijlsma <wouter@wouterbijlsma.nl>
Cc: "Lukas Wunner" <lukas@wunner.de>,
"Bjorn Helgaas" <helgaas@kernel.org>,
linux-pci@vger.kernel.org,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Krzysztof Wilczyński" <kw@linux.com>
Subject: Re: [PATCH] PCI/bwctrl: Fix NULL pointer deref on bus number exhaustion
Date: Fri, 4 Apr 2025 16:06:30 +0300 (EEST) [thread overview]
Message-ID: <9155d44f-f750-d678-ead7-3b27e389bb4a@linux.intel.com> (raw)
In-Reply-To: <20250323125652.GJ1902347@rocinante>
[-- Attachment #1: Type: text/plain, Size: 1794 bytes --]
On Sun, 23 Mar 2025, Krzysztof Wilczyński wrote:
> Hello,
>
> > The patch is working, no kernel crashes and shutting down after hotplugging the Thunderbolt 4 dock does not hang anymore, thanks!
>
> Thank you for testing! Appreciated!
>
> > I still see messages in the kernel log that 'devices behind bridge are
> > unusable' because 'no bus can be assigned to them', 'Hotplug bridge
> > without secondary bus, ignoring', etc. These all refer to the
> > Thunderbolt 4 bridge. Adding "pci=hpbussize=0x33" to the kernel
> > doesn't make a difference. Adding
> > "pci=realloc,asssign-busses,hpbussize=0x33" actually does 'fix' the
Hi,
Hmm, it seems this reply got stuck into postponed messages so sending it
only now.
There's a typo (3 x s) in the value, perhaps just for the email as it
worked.
> > bus allocation failures (or at least I don't see any messages in the
> > log anymore), but then amdgpu fails to initialize the IGP.
That is very likely independent issue. I can try to look at it if it's
some resource assignment related problem that occurs with pci=realloc.
Please could you take a dmesg with this added into the kernel command
line:
dyndbg="file drivers/pci/*.c +p"
I might also benefit from contents /proc/iomem if it turns out to be a
resource assignment problem but we'll see.
--
i.
> We can fix any outstanding issues or drop this patch. I leave it to hot
> plug experts like Ilpo, Bjorn and Lukas to make the call here.
>
> > Anyway, all devices connected to the Thunderbolt 4 dock appear to work (USB, screens, ethernet) even despite these bus allocation failures, so I will just ignore them.
> >
> > Thanks again!
>
> Would you be happy to provide your "Tested-by:" tag?
>
> Krzysztof
>
prev parent reply other threads:[~2025-04-04 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 18:52 [PATCH] PCI/bwctrl: Fix NULL pointer deref on bus number exhaustion Lukas Wunner
2025-03-23 11:24 ` Krzysztof Wilczyński
[not found] ` <2e16d6af-7d7d-47a7-9c69-26f0765a83d6@app.fastmail.com>
2025-03-23 12:56 ` Krzysztof Wilczyński
2025-03-23 13:07 ` Wouter Bijlsma
2025-03-23 13:39 ` Krzysztof Wilczyński
2025-04-04 13:06 ` Ilpo Järvinen [this message]
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=9155d44f-f750-d678-ead7-3b27e389bb4a@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mika.westerberg@linux.intel.com \
--cc=wouter@wouterbijlsma.nl \
/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