From: Demi Marie Obenour <demiobenour@gmail.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
netdev <netdev@vger.kernel.org>
Cc: regressions@lists.linux.dev
Subject: Re: [REGRESSION]: mlx5_core does not autoload in Linux 6.18
Date: Thu, 4 Dec 2025 22:21:29 -0500 [thread overview]
Message-ID: <2af9d46e-647c-44a7-8c19-32a749408130@gmail.com> (raw)
In-Reply-To: <418484c3-e65b-414d-ad2c-71e832ae7af2@leemhuis.info>
[-- Attachment #1.1.1: Type: text/plain, Size: 2232 bytes --]
On 12/4/25 06:53, Thorsten Leemhuis wrote:
> Lo! Thx for the report.
>
> Let me CC the maintainers of said driver, maybe they have an idea or
> even head about the problem already. If not, you might need to bisect this.
Interestingly, the problem does not reproduce after a reboot and
a further Nixpkgs upgrade. This either means that NixOS failed to
regenerate the initramfs, or that the problem is not reproducible
reliably.
> On 12/4/25 08:54, Demi Marie Obenour wrote:
>> In Linux 6.18, mlx5_core does not load automatically. This causes
>> my server to not be accessible from the network. Manually loading
>> the module in the initramfs fixes the problem. Everything worked
>> with Linux 6.17.x.
>>
>> I'm using the linuxPackages_latest package from Nixpkgs.
>
> Mentioning it like that might scare kernel developers, as they have no
> idea what this is and thus might suspect that it's a vendor kernel with
> lots of patches applied. Is that the case? Or is that vanilla or at
> least close to vanilla?
https://github.com/NixOS/nixpkgs/tree/7905606cfa51a1815787377b9cb04291e87ebcb4/pkgs/os-specific/linux/kernel
shows that there are very few patches. The only ones I see are:
- Change the RANDSTRUCT seed to one provided by NixOS.
- Replace hard-coded paths with ones that are present in NixOS.
- Make Kconfig print ### after every question.
- Change two EXPORT_SYMBOL_GPL to EXPORT_SYMBOL
so that ZFS works with PREEMPT_RT.
Of those, the first one is needed for reproducible builds with
RANDSTRUCT. The second is needed because of NixOS's filesystem
structure, which isn't FHS-conforming. The third is used by
NixOS-specific automation, and the last one is clearly not upstreamable
but also will not break anything.
>> The server is a RISE-7 OVH dedicated server with an AMD Epyc 7402 CPU.
>
> Ciao, Thorsten
>
> #regzbot ^introduced: v6.17..v6.18
> #regzbot title: net: mlx5_core: module does not autoload anymore Linux 6.18
I wonder if this is even a kernel bug. It could be that NixOS
generated a broken userspace that couldn't load the module.
The problem going away after nixos-rebuild supports this.
--
Sincerely,
Demi Marie Obenour (she/her/hers)
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-12-05 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a939e5fc-c5ea-4a9e-8566-54dfa54bb0da@gmail.com>
2025-12-04 11:53 ` [REGRESSION]: mlx5_core does not autoload in Linux 6.18 Thorsten Leemhuis
2025-12-05 3:21 ` Demi Marie Obenour [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=2af9d46e-647c-44a7-8c19-32a749408130@gmail.com \
--to=demiobenour@gmail.com \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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;
as well as URLs for NNTP newsgroup(s).