From: RicArch97 <RicArch97@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Runit startup blocking with a bootable USB plugged in / failed access to Bluetooth hardware
Date: Wed, 22 Jun 2022 04:16:30 +0200 [thread overview]
Message-ID: <20220622021630.N6VpRLhUl3BO7Hs5czEUKXZ_T59mFBi1awSsSGRw_e0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35304@inbox.vuxu.org>
[-- 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.
prev parent reply other threads:[~2022-06-22 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 1:00 [ISSUE] " RicArch97
2022-06-22 2:14 ` github-actions
2022-06-22 2:16 ` RicArch97 [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=20220622021630.N6VpRLhUl3BO7Hs5czEUKXZ_T59mFBi1awSsSGRw_e0@z \
--to=ricarch97@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).