Re: Nasty console and xe driver interactions

[Rodrigo Vivi <rodrigo.vivi@intel.com>]

On Thu, Oct 15, 2026 at 08:30:42AM -0700, Dave Hansen wrote:
> 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. 

Thanks for being brave! :)

> 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.

the force probe proves that we can still probe safely, but apparently
on my first attempt I missed the fact that pcim_enable_device will
touch the device and register a pci_disable_device that might
clear stuff and mess with the VGA fb...

Perhaps if we move just one step over:

https://github.com/rodrigovivi/linux/commit/616cd8c1b4d4414cd1f7ad56fa5d8abd36d7968d