From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Michael Schanne <michael.schanne@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Random lockups with i915 driver enabled
Date: Mon, 8 Dec 2025 16:58:11 +0100 [thread overview]
Message-ID: <20251208155811.Gb4m8Z9J@linutronix.de> (raw)
In-Reply-To: <CAC_kJhQ53MGieN29Kmx96bk-8hhnLb_7bp7cb_kFQ+Hf-_Gtgg@mail.gmail.com>
On 2025-12-03 16:23:01 [-0500], Michael Schanne wrote:
> Hi,
Hi,
> Can anyone suggest any debug techniques to nail down root cause when
> the next lockup occurs? Or are there any potential i915 fixes I could
> try out?
An 8250-UART would be probably help.
Does lockdep (CONFIG_PROVE_LOCKING) and/ or CONFIG_DEBUG_ATOMIC_SLEEP
complain?
Can you setup pstore and use it for locking?
Does your BIOS reset your memory on reset? If not, and you can force a
reset in the lockup case, you could try to stuff some information into
the tracing buffer. See
https://docs.kernel.org/trace/debugging.html#persistent-buffers-across-boots
Can you try to use the XE driver instead of i915?
> Hardware: Intel i5-6500TE quad core CPU (Skylake), 16 GB RAM
>
> Thanks,
> Mike
Sebastian
prev parent reply other threads:[~2025-12-08 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 21:23 Random lockups with i915 driver enabled Michael Schanne
2025-12-08 15:58 ` Sebastian Andrzej Siewior [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=20251208155811.Gb4m8Z9J@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=michael.schanne@gmail.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