Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

system freezes on NovaCustom V54 (SSD polling?) #9548

Open
mouflon72 opened this issue Oct 29, 2024 · 2 comments
Open

system freezes on NovaCustom V54 (SSD polling?) #9548

mouflon72 opened this issue Oct 29, 2024 · 2 comments
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: other hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@mouflon72
Copy link

mouflon72 commented Oct 29, 2024

Qubes OS release

4.2.3 running kernel-latest

Brief summary

  • certain actions in VMs cause the whole system to partially freeze

Steps to reproduce

a few actions that seemed to trigger this behaviour so far (will update if there are more observations):

  • running a fast (~20MB/s) download in a Debian 12 VM over some time
  • mounting an external Exfat USB drive on a Debian 12 VM
  • attaching and using a USB microphone on a Debian 12 VM
  • edit: sometimes just starting the system i enough, where e.g. sys-net freezes and forces me to hard reset

Expected behavior

system runs smoothly, no freezes

Actual behavior

  • system partly freezes, only some interaction with windows is still possible, e.g: I can click on an e-mail in a Thunderbird window, but the content won't get displayed
  • VMs that seem to cause this can't be shut down / killed any more, only hard system reset helps
  • dom0 terminal, e.g. running dmesg remains working

The difference I see in kernel log between functioning / non-functioning state is that I see repeated messages like "nvme nvme0: I/O xxx QID x timeout, completion polled".
I haven't really found any issues here referencing this message except referring to AMD Ryzen systems with hyperthreading enabled.

Note: I am not using NovaCustom OEM SSD but a SanDisk Extreme PRO M.2 NVMe, which I already previously used in another Qubes installation on a Thinkpad (not using kernel-latest though). It was working fine there.

@mouflon72 mouflon72 added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. labels Oct 29, 2024
@andrewdavidwong andrewdavidwong added C: other hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. affects-4.2 This issue affects Qubes OS 4.2. labels Oct 30, 2024
@mouflon72
Copy link
Author

I moved my system to a Goodram PX-700 now, which seems to have fixed the SSD timeouts. The SanDisk was PCIe 3, the new one is PCIe 4.0.
Partial freeze wih Exfat drive remains, but that seems to have a different cause. Will open a seperate issue, if that persists.

@apparatius
Copy link

The difference I see in kernel log between functioning / non-functioning state is that I see repeated messages like "nvme nvme0: I/O xxx QID x timeout, completion polled".

Try to switch the storage mode from RAID to AHCI/NVME or disable Intel Volume Management Device (VMD) in BIOS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: other hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

3 participants