[ISSUE] Runit startup blocking with a bootable USB plugged in / failed access to Bluetooth hardware

[ISSUE] Runit startup blocking with a bootable USB plugged in / failed access to Bluetooth hardware

[RicArch97]

[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]

New issue by RicArch97 on void-packages repository

https://github.com/void-linux/void-packages/issues/35304

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  Void 5.15.17_1 x86_64 AuthenticAMD uptodate rrrmFFFFFFF
* package:  
  Linux5.15

### Expected behavior

Immediate startup of the system.

### Actual behavior

Runit blocks on "Setting up udev and waiting for devices to settle..." when a bootable USB drive is plugged in.

After like 10 seconds or so, it prints a dmesg error, and then goes on with the init of the system.

Blocking can also occur when booting after previously being booted into Windows, when it probably fails to get access to the Bluetooth controller, guessing from the HCI errors that follow.

This behaviour wasn't always there, but got introduced in one of the updates (5.15-something? i can't remember exactly). Before it just started and then the errors came afterwards. Those errors aren't really a problem, but the blocking is.

### Steps to reproduce the behavior

Stick a **bootable** USB drive (memtest86 for example, or some Linux distro)  in one of your USB ports, and then restart Void Linux. 

Re: Runit startup blocking with a bootable USB plugged in / failed access to Bluetooth hardware

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/35304#issuecomment-1162547836

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: [ISSUE] [CLOSED] Runit startup blocking with a bootable USB plugged in / failed access to Bluetooth hardware

[RicArch97]

[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]

Closed issue by RicArch97 on void-packages repository

https://github.com/void-linux/void-packages/issues/35304

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  Void 5.15.17_1 x86_64 AuthenticAMD uptodate rrrmFFFFFFF
* package:  
  Linux5.15

### Expected behavior

Immediate startup of the system.

### Actual behavior

Runit blocks on "Setting up udev and waiting for devices to settle..." when a bootable USB drive is plugged in.

After like 10 seconds or so, it prints a dmesg error, and then goes on with the init of the system.

Blocking can also occur when booting after previously being booted into Windows, when it probably fails to get access to the Bluetooth controller, guessing from the HCI errors that follow.

This behaviour wasn't always there, but got introduced in one of the updates (5.15-something? i can't remember exactly). Before it just started and then the errors came afterwards. Those errors aren't really a problem, but the blocking is.

### Steps to reproduce the behavior

Stick a **bootable** USB drive (memtest86 for example, or some Linux distro)  in one of your USB ports, and then restart Void Linux.