From: Bjorn Helgaas <helgaas@kernel.org>
To: Matthias Dittrich <dittrich.m@gmx.net>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
regressions@lists.linux.dev,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [REGRESSION] PCI BAR allocation/D3cold failure: NVIDIA MX250 inaccessible since Kernel 6.x on Acer Swift 3 (SF314-56G)
Date: Fri, 1 May 2026 11:55:42 -0500 [thread overview]
Message-ID: <20260501165542.GA491695@bhelgaas> (raw)
In-Reply-To: <a27da33f-96da-477b-b7ae-e7bcd3a34796@gmx.net>
[+cc Ilpo]
On Fri, May 01, 2026 at 10:13:41AM +0200, Matthias Dittrich wrote:
> Dear Kernel Developers,
>
> I found a regression and did my best to identify the issue and find a
> workaround, but I am not a developer. I also published the regression in the
> NVIDIA Linux Developer Forum, but it appears to be a kernel regression and
> not a driver issue, as the latest drivers work on older kernels (e.g., 5.15)
> but fail on anything 6.x+. I did not perform a git bisect as compiling on
> this i5-8265U - because of its low performance I can only compile one kernel
> over night.
>
> **Description:**
> The NVIDIA MX250 GPU on Acer Swift 3 (SF314-56G / BIOS 1.14) is inaccessible
> on any Linux distribution using Kernel 6.x or 7.x. The device fails to
> initialize during the driver probe routine.
Thanks for the report. With the newest kernel available to you, can
you please capture the complete dmesg and output of "sudo lspci -vv"?
Don't filter out things that don't seem relevant; we can easily do
that.
Bjorn
next prev parent reply other threads:[~2026-05-01 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 8:13 [REGRESSION] PCI BAR allocation/D3cold failure: NVIDIA MX250 inaccessible since Kernel 6.x on Acer Swift 3 (SF314-56G) Matthias Dittrich
2026-05-01 16:55 ` Bjorn Helgaas [this message]
2026-05-11 9:34 ` Matthias Dittrich
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=20260501165542.GA491695@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=dittrich.m@gmx.net \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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