On Mon, Oct 07, 2024 at 12:33:54PM -0500, Mario Limonciello wrote:
> On 10/7/2024 12:21, Christian Heusel wrote:
> > On 24/10/07 06:49PM, Fabian Stäber wrote:
> > > Hi,
> >
> > Hey Fabian,
> >
> > > sorry for the delay, I ran git bisect, here's the output. If you need
> > > any additional info please let me know.
> > >
> > > 3c1d704d9266741fc5a9a0a287a5c6b72ddbea55 is the first bad commit
> > > commit 3c1d704d9266741fc5a9a0a287a5c6b72ddbea55 (HEAD)
> > > Author: Sanath S <Sanath.S@xxxxxxx>
> > > Date: Sat Jan 13 10:52:48 2024
> > >
> > > thunderbolt: Reset topology created by the boot firmware
> > >
> > > commit 59a54c5f3dbde00b8ad30aef27fe35b1fe07bf5c upstream.
> >
> > So there is a commit c67f926ec870 ("thunderbolt: Reset only non-USB4
> > host routers in resume") that carries a fixes tag for the commit that
> > you have bisected to. The commits should both be in v6.6.29 and onwards,
> > so in the same release that's causing you problems. Maybe the fix is
> > incomplete or has a missing dependency 🤔
>
> You mean mainline commit 8cf9926c537c ("thunderbolt: Reset only non-USB4
> host routers in resume").
>
> >
> > > [...]
> > > Suggested-by: Mario Limonciello <mario.limonciello@xxxxxxx>
> > > Signed-off-by: Sanath S <Sanath.S@xxxxxxx>
> > > Signed-off-by: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> >
> > I have added Mika, Mario and Sanath to the recipients, maybe they have
> > inputs on what would be useful debugging output.
> >
> > In the meantime maybe also test if the issue is present with the latest
> > stable kernel ("linux" in the Arch packages) and with the latest release
> > candidate (you can find a precompiled version [here][0].
>
> To double confirm, does thunderbolt.host_reset=0 on the kernel command line
> help your issue? Based on the bisect I would expect it should help. Yes;
> comments on both 6.6.y as well as 6.12-rc2 would be ideal.
>
> Also assuming it helps can you please post your dmesg from 6.12-rc2 both
> with thunderbolt.host_reset=0 and without? A github gist or a new kernel
> bugzilla are good places to post it.
Also to understand the flow, you are booting with the dock connected
right?
Can you see also what:
$ boltctl
outputs (after you have booted up, and the problem is reproduced)? It
should list the dock and show it as "authorized" but I'm not familiar
with Arch Linux so it could be that they are not using bolt and that
explains why things do not appear working as nobody is going to
re-create that PCIe tunnel that was torn down during host router reset.
