Qubes 4.1 Freeze after start sys-net #8216
Labels
affects-4.1
This issue affects Qubes OS 4.1.
C: other
diagnosed
Technical diagnosis has been performed (see issue comments).
hardware support
P: default
Priority: default. Default priority for new issues, to be replaced given sufficient information.
R: upstream issue
Resolution: This issue pertains to software that the Qubes OS Project does not develop or control.
T: bug
Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Comments
alexsok-bit
added
P: default
andrewdavidwong
added
C: other
hardware support
needs diagnosis
|
What I can do to speed up the diagnostic? |
|
I have also noticed that this usually happens after the NetworkManager icon appears. If the bug occurs during operation, the NetworkManager's icon disappears first and then sys-net crashes. |
|
I'm got from systemctl all logs. And incedent log too. Looking from 2023-06-08 15:01:59 |
|
Disabling UAS fixed the problem https://forum.qubes-os.org/t/do-freezing-system-after-boot/18600/11 |
|
Closing as "not our bug" (the Qubes OS Project does not develop the software that is causing this bug). If anyone believes this resolution is a mistake, please leave a comment, and we'll be happy to take another look. Thank you. Related FAQ: Why don’t you fix upstream bugs that affect Qubes OS? |
andrewdavidwong
added
R: upstream issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to file a helpful issue
Qubes OS release
OS: Qubes 4.1
USB Devices: Keyboard and Mouse
Installetion destination device: External NVME. Plug in Thunderbolt via USB-C to NVME adapter (pic).
PC: Laptop Lenovo ThinkPad T14
Brief summary
No sys-usb is created during installation. Because I am using a usb device and installing the system on an external drive connected via Thunderbolt.
After installing Qubes it hangs immediately after booting. I tried reinstalling the system several times. However, I still experienced a chance of getting a system freeze after startup every time I turned it on.
I started to look into what the problem was and found that the freeze was happening during sys-net startup. To rule out cable or overheating problems I disabled sys-net autorun and all Qubes that require internet.
After that the system always starts up normally. I also left vault and KeePass on autorun to rule out breakdown options from other Qubes.
I now have a high chance of catching a hang-up after starting sys-net. The chance of hanging increases if I connect the drive to Qubes via USB-3.0 using the adapter which you can see in the photo with the cable.
I also collected the systemctl logs at the time of the incident. Unfortunately due to the nature of the failure it was not possible to extract the logs in text so I took photos.
From the logs you can see that the drive shuts down after starting sys-net. I think it is a bug as the OS should not disable the device controllers it needs to work. For example I want to put the /boot and /boot/efi partition on a flash drive to protect myself from changing the boot loader on the disabled OS and in general to hide the presence of any OS on the drive.
The system cannot be used at the moment. I like it very much. Can I make sys-net ignore the Thunderbolt controller or will I have to wait for a fix?
Steps to reproduce
All you need to do is install Qubes on a USB device and try to use it. I can film the whole process from installation to the incident. I can also call up the incident as many times as I like.
Frieze does not always happen.
Expected behavior
Qubes should not disable the controllers from which the partitions in
/boot,/boot/efi, and/Actual behavior
Qubes disables the device it needs to operate.
The text was updated successfully, but these errors were encountered: