On 3/4/25 00:27, Mika Westerberg wrote:
If possible add "thunderbolt.dyndbg=+p" now to your kernel command line so
if this happens again, we hopefully have full dmesg to investigate.
I've not seen any further instances of weird behavior, but I've added
that to the command line going further.
But I have been doing a fair amount of testing of the kernel with your
patch and Lucas' NVMe adaptor (etc.) patch and am concerned that you're
still seeing his issue, as it (at least as of now) hasn't occurred here
since applying it.
In any case, on the next reboot it'll be applied.
-Kenny
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange
County CA
