From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Hans-Joachim Lange <lange-achim@posteo.de>, linux-ide@vger.kernel.org
Subject: Re: PROBLEM: Kernel 6.8.x: VFS: Unable to mount root fs on unknown-block(0,0) – SATA (Intel AHCI) not detected
Date: Mon, 12 Oct 2026 09:45:17 +0200 [thread overview]
Message-ID: <asyQDZ80n6bdpsD0@ryzen> (raw)
In-Reply-To: <e2e16c3e-df02-47de-9205-c5259875211b@kernel.org>
On Sun, Oct 11, 2026 at 05:23:46PM +0200, Damien Le Moal wrote:
> On 2026/10/11 17:22, Damien Le Moal wrote:
> > On 2026/10/09 13:48, Hans-Joachim Lange wrote:
> >> Hello
> >> This the boot video link
> >>
> >> https://cloud.magdeburg.jetzt/s/7dyQZadJxWcsyrM
> >
> > We are always happy to help in case of an issue, but please do not expect us to
> > do all the debugging work ourselves and do your own homework too: can you
> > analyze what you see there and tell us?
> >
>
> +Niklas
Problems I see:
You are booting 6.8.0-138
Looking at the versioning, this seems to be some Linux Mint downstream
kernel.
We asked you to test the latest upstream kernel
(7.3-rc7 at the time of writing).
You get a kernel oops when booting, which includes function:
security_module_from_file().
This is part of Linux Security Module (LSM), which suggests
to me that you are trying to load a signed kernel module,
and something went wrong.
You can read more about this here:
https://docs.kernel.org/admin-guide/module-signing.html
If you build the kernel yourself, you can simply avoid signing
kernel modules, set:
# CONFIG_SECURITY_LOCKDOWN_LSM is not set
# CONFIG_MODULE_SIG is not set
Your eMMC driver is failing to reset the controller.
This looks like a bug in your kernel.
I guess it could be a side effect of you failing to load some
kernel modules already.
If you try the latest kernel, and build without signed modules,
you will probably get further.
But this also asks the question, is your rootfs on eMMC?
If so, it is no wonder that you don't see any AHCI drives.
Kind regards,
Niklas
prev parent reply other threads:[~2026-10-12 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 12:40 PROBLEM: Kernel 6.8.x: VFS: Unable to mount root fs on unknown-block(0,0) – SATA (Intel AHCI) not detected Hans-Joachim Lange
2026-10-09 7:33 ` Damien Le Moal
2026-10-09 15:40 ` Niklas Cassel
[not found] ` <d575b071-50a4-479b-a992-3268f3b37a50@posteo.de>
[not found] ` <08c11d50-a358-4846-badc-7b7cb5c12d35@kernel.org>
[not found] ` <e2e16c3e-df02-47de-9205-c5259875211b@kernel.org>
2026-10-12 7:45 ` Niklas Cassel [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=asyQDZ80n6bdpsD0@ryzen \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=lange-achim@posteo.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox