linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Michael Guntsche <michael.guntsche@it-loops.com>,
	"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
	linux-pm@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Re: Oops when returning from hibernation with changed thunderbolt status
Date: Sat, 22 Nov 2025 11:42:10 +0100	[thread overview]
Message-ID: <aSGTghJyX-u-leL6@wunner.de> (raw)
In-Reply-To: <20251120055748.GM2912318@black.igk.intel.com>

[cc += linux-efi]

On Thu, Nov 20, 2025 at 06:57:48AM +0100, Mika Westerberg wrote:
> On Wed, Nov 19, 2025 at 06:43:16PM +0100, Michael Guntsche wrote:
> > I started seeing this issue with kernel v6.15, it worked fine up to 6.14.
> > If my notebook went into hibernation with the docking station plugged
> > in and I then started it up again with the docking station unplugged
> > it would panic. Some times but not always it would also panic if the
> > dock was still connected.
> 
> Did you try to disable RTC_DRV_EFI? At least from the backtrace that's
> where it crashes.

The backtrace in the photo doesn't seem to betray what kind of call
was queued up on efi_rts_wq.  It doesn't have to be a set/get time
request.  efi_queue_work() is also called for set/get variable requests
among other things.  I recommend instrumenting __efi_queue_work()
with a call to dump_stack() to see where this is coming from.
Maybe add an msleep(5000) afterwards to allow time to take a picture.

Also the photo shows a UBSAN splat in drm/display/drm_mst_topology.c
220 msec before the oops, maybe it's related?

Thanks,

Lukas

  parent reply	other threads:[~2025-11-22 10:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 17:43 Oops when returning from hibernation with changed thunderbolt status Michael Guntsche
2025-11-20  5:57 ` Mika Westerberg
2025-11-20  6:53   ` Michael Guntsche
2025-11-22 10:42   ` Lukas Wunner [this message]
2025-11-24 18:02     ` Kenneth Crudup
2025-12-01 19:09       ` Michael Guntsche
2025-12-01 20:51         ` Kenneth Crudup

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=aSGTghJyX-u-leL6@wunner.de \
    --to=lukas@wunner.de \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).