From: Jani Nikula <jani.nikula@linux.intel.com>
To: Hannes Reinecke <hare@suse.de>, Niklas Cassel <cassel@kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
kernel-dev@rsta79.anonaddy.me
Cc: linux-ide@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: Re: ahci + intel iGPU problems
Date: Mon, 19 May 2025 16:20:00 +0300 [thread overview]
Message-ID: <8734d0vitb.fsf@intel.com> (raw)
In-Reply-To: <29d05b80-1381-436c-8c6a-ec30113c069d@suse.de>
On Mon, 19 May 2025, Hannes Reinecke <hare@suse.de> wrote:
> The nasty thing about i915 is that is reconfigures the _root bride_.
> As the i915 device is always built-in, the driver 'knows' what's
> best for the root bridge, and reconfigures it.
> (IIRC this happens if you several outputs and for some reason they
> are not configured correctly.)
> And if you are particularly unlucky the driver configures it wrong,
> killing other devices in the process. That happened to us once, where
> the i915 driver ended up killing the NVMe device.
>
> Please check the i915 output configuration, and try to get a PCI
> configuration readout before and after loading the i915 driver.
Would you mind pointing me at where you think we're doing nasty stuff,
please? Sincere question.
Side note, i915 supports discrete devices too.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-05-19 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 13:42 ahci + intel iGPU problems Niklas Cassel
2025-05-19 6:12 ` Hannes Reinecke
2025-05-19 13:20 ` Jani Nikula [this message]
2025-05-19 13:11 ` Jani Nikula
2025-05-19 21:02 ` Niklas Cassel
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=8734d0vitb.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=hare@suse.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kernel-dev@rsta79.anonaddy.me \
--cc=linux-ide@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.