Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Zack Rusin <zack.rusin@broadcom.com>,
	dri-devel@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	intel-xe@lists.freedesktop.org
Subject: Re: Nasty console and xe driver interactions
Date: Thu, 15 Oct 2026 08:30:42 -0700	[thread overview]
Message-ID: <d4d5302f-9768-4122-bbab-4384ef7aa9fe@intel.com> (raw)
In-Reply-To: <atDXDlI-EhrA791a@intel.com>

On 10/15/26 06:37, Rodrigo Vivi wrote:
> So, perhaps what could be done in this specific case while we don't have
> the proper one is something like trying to pre-fetch the mandatory fw.
> Before we steal the fb. Something like:
> 
> (Untested warning)
> 
> https://github.com/rodrigovivi/linux/commit/5589d2883a604d52e89f44620e16d16c7fd278e8

I threw caution to the wind and tried this. Id didn't seem to help. I
don't seem the messages about unregistering the old console, but I still
never get any output. The only "xe" gunk in dmesg is:

> [    0.739464] xe 0000:00:02.0: GuC firmware xe/ptl_guc_70.bin not found, can be downloaded from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> [    0.739501] xe 0000:00:02.0: probe with driver xe failed with error -2

BTW, "xe.force_probe=!*" on the command-line also gets the output back
to normal.

  reply	other threads:[~2026-10-15 15:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 23:04 Nasty console and xe driver interactions Dave Hansen
2026-10-15 13:37 ` Rodrigo Vivi
2026-10-15 15:30   ` Dave Hansen [this message]
2026-10-15 16:10     ` Rodrigo Vivi
2026-10-15 16:41       ` Zack Rusin

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=d4d5302f-9768-4122-bbab-4384ef7aa9fe@intel.com \
    --to=dave.hansen@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=zack.rusin@broadcom.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