Well, now get this- I'm back to running Linus' master (as of
79a61cc3fc0) and I've been trying to get resumes to fail and they
haven't (which means the next time I try after hitting "send" it's going
to fail spectacularly).
My SWAG is it may be related to commits 79a61cc3fc or 3e705251d998c9,
but I'll see if it breaks and if it doesn't, all the better :)
-K
On 9/12/24 22:25, Mika Westerberg wrote:
Hi,
On Thu, Sep 12, 2024 at 02:12:27PM -0700, Kenneth Crudup wrote:
I'll run the stuff you need, but now it looks like whatever is breaking
suspend/resume in Linus' master has been ported down from upstream into
6.10.10; I'm now getting the same panic()s as I did with master. I just had
a failed resume and the crash dump (which happened on its own) looks the
same as the one I'd posted here.
Is the crash you see something different from the hang? If you can catch
that with the backtrace and the register dump it should help.
Couple of additional steps to try:
- Unplug monitors from the dock and see if that makes it work (assuming
you have monitors connected).
- Disable PCIe tunneling and see if that makes it work. This results
that the PCIe devices on the dock are not functional but it can point
us to the direction. You can do this on regular distro (Ubuntu, Fedora
etC) like:
$ boltctl config auth-mode disabled
Or got to "Settings" -> "Privacy & Security" -> "Thunderbolt" and flip
off the "Direct Access" switch.
I may try and find some time to bisect the issue, but it'll take some time.
Sure.
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange
County CA
