From: Kenneth Crudup <kenny@panix.com>
To: Michael Guntsche <michael.guntsche@it-loops.com>
Cc: Lukas Wunner <lukas@wunner.de>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
linux-pm@vger.kernel.org, linux-efi@vger.kernel.org,
maarten.lankhorst@linux.intel.com
Subject: Re: Oops when returning from hibernation with changed thunderbolt status
Date: Mon, 1 Dec 2025 12:51:48 -0800 [thread overview]
Message-ID: <628342c2-15c5-4890-84ae-dc29df2c5f16@panix.com> (raw)
In-Reply-To: <CALG0vJv7ZA8byAF25pKqh9fEBpfgbXk+cAE6s9K1N6ZvVRroUw@mail.gmail.com>
On 12/1/25 11:09, Michael Guntsche wrote:
>> FWIW, this sounds really familiar (resume crashes if I changed TB docks
>> between suspend and resume) and was getting an OOPS there I'd bisected to:
>>
>> Resume OOPS from f6971d7427 ("drm/i915/mst: adapt
>> intel_dp_mtp_tu_compute_config() for 128b/132b SST") if MST displays
>> disconnected while suspended
>>
>> ... and this was fixed in 732b87a (Fix determining SST/MST mode during
>> MTP TU state computation) back in 6.15 (which IIRC, is when your crashes
>> started happening).
>>
>> I wonder if this is related? Maybe reach out to the i915 guys?
>
> I tried this now with 6.18 and got the same issues, now it even fails
> for me if I unplug the dock while hibernating.
> The last entry I see is the UBSAN message and an out of bounds index error.
I guess what I'm wondering is if the fix for me broke things for you ...
can you revert that change in 6.15.1 and see if things unbreak for you?
-K
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange
County CA
prev parent reply other threads:[~2025-12-01 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALG0vJuaU_5REU55Hg170LipPLj7Tt0V3icn7XzxLY-8+jsx-A@mail.gmail.com>
[not found] ` <20251120055748.GM2912318@black.igk.intel.com>
2025-11-22 10:42 ` Oops when returning from hibernation with changed thunderbolt status Lukas Wunner
2025-11-24 18:02 ` Kenneth Crudup
2025-12-01 19:09 ` Michael Guntsche
2025-12-01 20:51 ` Kenneth Crudup [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=628342c2-15c5-4890-84ae-dc29df2c5f16@panix.com \
--to=kenny@panix.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=maarten.lankhorst@linux.intel.com \
--cc=michael.guntsche@it-loops.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
/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