Re: So, I had to revert d6d458d42e1 ("Handle DisplayPort tunnel activation asynchronously") too, to stop my resume crashes

Mika Westerberg
2025-03-03T11:53:32Z

On Mon, Mar 03, 2025 at 03:38:58AM -0800, Kenneth Crudup wrote:
>
> On 3/3/25 03:21, Mika Westerberg wrote:
>
> > Now you say that you don't reproduce the DP tunnel issue if you simply plug
> > in monitor so let's try to figure out reliable steps to repro so we can
> > investigate.
> ...
> > So with 9d573d19547b3 only reverted, no other changes to the kernel and
> > "thunderbolt.dyndbg=+p" in the command line do following steps:
> >
> > 1. Boot the system up, nothing connected.
> > 2. Connect TBT 4 dock to the system.
> > 3. Connect monitor to the TBT 4 dock.
> > 4. Suspend the system by closing lid.
> > 5. Resume the system by openling lid.
> >
> > Expectation: Monitor over Thunderbolt still shows picture.
> > Actual result: Screen is blank.
>
> I will do this in a couple of days (got a few things to do first), but what
> actually happens is I get as OOPS and have to power-button-reset to recover,
> not even SysRq-B gets me out of it (I've since added "Panic on OOPS" with a
> 15-second timeout while I was trying to figure out this DP monitor issue).

I thought the system resumes fine after you reverted the other commit
(9d573d19), no? Just you don't get display tunneled so for example if you
login over ethernet (ssh) you should still be able to get full dmesg.

> > Then since now resume at least
> > completes you can provide full dmesg to me and I can try to figure out what
> > is wrong there.
>
> It'll have to be more pstore dumps, as resume doesn't (usually) complete
> with d6d458d42e1.

What you mean does not usually complete?

Let's try to figure out how we can get full dmesg of the crash without need
to dig the pstore things if possible at all. I was hoping it now resumes
just you don't see picture on the screen.

We can actually take PCIe out of the equation so that you ask "boltctl" to
forget the device temporarily (or from the GNOME settings "privacy and
security" -> "Thunderbolt" then "forget device" for each). This means your
docks do not work fully but display should and then we hopefully can get
the dmesg.

I will try to reproduce on my end too. I have serial port connected so I
can see all the messages even if the kernel crashes.