Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #83778 > unrolled thread

Bug#1080203: initramfs-tools: USB keyboard stopped working on LUKS prompt

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1080203: initramfs-tools: USB keyboard stopped working on LUKS prompt Henrik Ahlgren <pablo@seestieto.com> - 2024-08-31 17:10 +0200
    Bug#1080203: initramfs-tools: USB keyboard stopped working on LUKS prompt Ben Hutchings <ben@decadent.org.uk> - 2024-08-31 23:30 +0200
    Processed: Re: initramfs-tools: USB keyboard stopped working on  LUKS prompt "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-08-31 23:30 +0200
    Bug#1080203: initramfs-tools: USB keyboard stopped working on LUKS prompt Ben Hutchings <ben@decadent.org.uk> - 2024-09-01 00:00 +0200
    Bug#1080203: marked as done (initramfs-tools: USB keyboard  stopped working on LUKS prompt) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-09-01 15:40 +0200

#83778 — Bug#1080203: initramfs-tools: USB keyboard stopped working on LUKS prompt

Package: initramfs-tools
Version: 0.142+deb12u1
Severity: important

Dear Maintainer,

After upgrading to 12.7 point release and rebooting, I was unable to
enter my FDE LUKS password. The keyboard was totally unresponsive to any key presses
(no asterisks were echoed when typing the password, and hitting Enter did nothing).

My keyboard is a standard USB keyboard (Topre Realforce) connected to
an AMD-based HP desktop machine.

I then booted to a rescue environment from an USB stick and downgraded
initramfs-tools(-core) to the previous version (0.142). After that everything
worked normally again.

According to the changelog, there are several recent keyboard and USB
related changes in this u1 release that might be relevant.

Please take a look, I think this is fairly important since it renders at least
some systems with LUKS unbootable.

Pablo

-- System Information:
Debian Release: 12.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-25-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages initramfs-tools depends on:
ii  initramfs-tools-core  0.142
ii  linux-base            4.9

initramfs-tools recommends no packages.

Versions of packages initramfs-tools suggests:
ii  bash-completion  1:2.11-6

-- no debconf information

[toc] | [next] | [standalone]

#83784

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 moreinfo

On Sat, 31 Aug 2024 17:53:32 +0300 Henrik Ahlgren <pablo@seestieto.com> wrote:
> Package: initramfs-tools
> Version: 0.142+deb12u1
> Severity: important
> 
> Dear Maintainer,
> 
> After upgrading to 12.7 point release and rebooting, I was unable to
> enter my FDE LUKS password. The keyboard was totally unresponsive to any key presses
> (no asterisks were echoed when typing the password, and hitting Enter did nothing).
> 
> My keyboard is a standard USB keyboard (Topre Realforce) connected to
> an AMD-based HP desktop machine.
> 
> I then booted to a rescue environment from an USB stick and downgraded
> initramfs-tools(-core) to the previous version (0.142). After that everything
> worked normally again.
> 
> According to the changelog, there are several recent keyboard and USB
> related changes in this u1 release that might be relevant.

None of the driver changes are relevant to this system.  You are not
using Hyper-V and Linux 6.1 does not include the USB drivers that
initramfs-tools tries to add.
 
> Please take a look, I think this is fairly important since it renders at least
> some systems with LUKS unbootable.

I can't reproduce this.

I suspect that probing of your USB keyboard is slightly unreliable and
that it just happened to fail on the first boot after you upgraded. 
Please try again with the new initramfs-tools packages.  Also, if the
keyboard is not detected at first, try unplugging and re-plugging it.

If this problem persists, please send:

- The /etc/initramfs-tools/initramfs.conf file
- The output of "lsinitramfs /boot/initrd.img-6.1.0-25-amd64" when
  the old version of initramfs-tools is installed
- The output of "lsinitramfs /boot/initrd.img-6.1.0-25-amd64" when
  the new version of initramfs-tools is installed

Ben.

-- 
Ben Hutchings
For every complex problem
there is a solution that is simple, neat, and wrong.

[toc] | [prev] | [next] | [standalone]

#83785 — Processed: Re: initramfs-tools: USB keyboard stopped working on LUKS prompt

Processing control commands:

> tag -1 moreinfo
Bug #1080203 [initramfs-tools] initramfs-tools: USB keyboard stopped working on LUKS prompt
Added tag(s) moreinfo.

-- 
1080203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080203
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#83786

[Multipart message — attachments visible in raw view] — view raw

On Sun, 2024-09-01 at 00:40 +0300, Henrik Ahlgren wrote:
> On Sat, 2024-08-31 at 23:22 +0200, Ben Hutchings wrote:
> > None of the driver changes are relevant to this system.  You are not
> > using Hyper-V and Linux 6.1 does not include the USB drivers that
> > initramfs-tools tries to add.
> 
> I suspect this commit might be relevant:
> 
> https://salsa.debian.org/kernel-team/initramfs-tools/-/commit/5d28dad0e24020d43daf51a5c1e70eb2fe5b4ee2
> 
> Both onboard_usb_hub and onboard_usb_dev are listed. From kernel git
> history it seems to me that it is the same module, but it was renamed from
> _hub to _dev (31e7f6c015d). Bookworm 6.1 kernel does include
> onboard_usb_hub I believe, but I don't quite understand what it is exactly.

Well, the driver source is there, but we didn't enable it until later
and then only on arm64.

> When I have time, I might try to disable this part from hook-functions to
> see if it helps. I would not be surprised if this is was hardware-relevant,
> of course.
> 
> > I suspect that probing of your USB keyboard is slightly unreliable and
> > that it just happened to fail on the first boot after you upgraded. 
> > Please try again with the new initramfs-tools packages.  Also, if the
> > keyboard is not detected at first, try unplugging and re-plugging it.
> 
> I did try rebooting many times with same results each time. Also tried
> unpluggint and re-plugging and even switching to a different keyboard. I
> have never seen this issue with 0.142.

Well this is very weird.

Another possibility is a USB hub getting into a broken state which
isn't cleared by rebooting.  But this doesn't seem very likely.

Ben.

-- 
Ben Hutchings
For every complex problem
there is a solution that is simple, neat, and wrong.

[toc] | [prev] | [next] | [standalone]

#83789 — Bug#1080203: marked as done (initramfs-tools: USB keyboard stopped working on LUKS prompt)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sun, 01 Sep 2024 15:31:01 +0200
with message-id <cb9421fe453053ef2089117a109edc1992ba51fa.camel@decadent.org.uk>
and subject line Re: initramfs-tools: USB keyboard stopped working on LUKS prompt
has caused the Debian Bug report #1080203,
regarding initramfs-tools: USB keyboard stopped working on LUKS prompt
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1080203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080203
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web