Closed marmarek closed 10 months ago
Similar thing happens on 6.5.6 too. Whole disk I/O got frozen, no lvrename involved this time.
At one time I've got the issue without lvm among blocked processes
Upstream report: https://lore.kernel.org/all/ZTNH0qtmint%2FzLJZ@mail-itl/
Automated announcement from builder-github
The component linux-kernel-latest
(including package kernel-latest-6.6.2-1.qubes.fc32
) has been pushed to the r4.1
testing repository for dom0.
To test this update, please install it with the following command:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
Automated announcement from builder-github
The component linux-kernel-latest
(including package kernel-latest-6.6.2-1.qubes.fc32
) has been pushed to the r4.1
stable repository for dom0.
To install this update, please use the standard update command:
sudo qubes-dom0-update
Or update dom0 via Qubes Manager.
How to file a helpful issue
Qubes OS release
R4.2
Brief summary
A test hanged on VM shutdown, specifically lvrename step: https://openqa.qubes-os.org/tests/83530
I'm creating the issue to write down collected logs, but I'll investigate only when it will happen for the second time.
Steps to reproduce
Run integration tests and hope to trigger the issue. I'm not sure if it's hardware dependent, or just hard to reproduce
Expected behavior
No hang
Actual behavior
Shutting down a VM hangs.
Process list:
Task backtraces (via sysrq)
``` [ 3485.834038] task:lvm state:D stack:0 pid:7835 ppid:5665 flags:0x00004006 [ 3485.834043] Call Trace: [ 3485.834046]Blocked tasks
``` [ 4246.558313] sysrq: Show Blocked State [ 4246.558388] task:journal-offline state:D stack:0 pid:8098 ppid:1 flags:0x00000002 [ 4246.558407] Call Trace: [ 4246.558414]