#1151632 linux: config: consider setting DRIVER_DEFERRED_PROBE_TIMEOUT to -1 (arm64 luks laptops)

Package:
src:linux
Source:
src:linux
Submitter:
Agathe Porte
Date:
2026-11-05 13:59:02 UTC
Severity:
normal
Tags:
#1151632#5
Date:
2026-10-22 13:48:25 UTC
From:
To:
Dear Maintainer,

(self-reporting, I intent to create the necessary PRs in salsa)

arm64 laptops that are using luks encryption need to set the
deferred_probe_timeout=30 command-line option to avoid having a timeout
while typing the LUKS password.

Quoting the commit [1] that introduced DRIVER_DEFERRED_PROBE_TIMEOUT as
a Kconfig option for the justification:

Since this option now allows for distributions to change the default 10s
value to something else, we can now tweak the Debian kernel to have a
more generous timeout (eg. 30s) or even disable the timeout so that
taking time to enter a LUKS decryption key does not lead to driver
timeouts on arm64 laptops.

Thanks,

Agathe.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/base/Kconfig?id=56e3ee721b33bdc4ce0765d370983aa4384f8a59

#1151632#10
Date:
2026-11-05 13:52:58 UTC
From:
To:
What specifically times-out here?

I don't entirely follow the logic here.  If the dependencies aren't
needed in the initramfs, that means the drivers depending on them also
aren't needed, so then shouldn't those also be excluded from the
initramfs?  (I understand that the dependencies are discovered at boot
time from the device tree and the initramfs builder won't be able to see
them.  But this still seems strange to me.)

It sounds like there have been multiple fixes here that weren't entirely
thought out:

1. Sometimes devices don't get detected in the right order, and probes
fail because dependencies haven't yet been probed.
2. Introduce -EPROBE_DEFER and retry all probes that return that.  But
now we can keep retrying probes that will never succeeed.
3. Add a timeout to (some) retries.  But now a long wait in the
initramfs will mean we timeout probes that can succeed after it hands
over to the main system.
4. Allow the time limit to be turned off at build or boot time.  GOTO 2.

You are proposing step 4, and I do agree with the reasoning for it, yet
that can also be a regression.  Would it not be better to add a way to
reduce the timeout once the main system is running?

Ben.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/base/Kconfig?id=56e3ee721b33bdc4ce0765d370983aa4384f8a59