Failed to acquire global channel lock #9033
Comments
|
I think the dxg print may not be related to why the PCI devices cannot be accessed. Would need to look at logs of what's happening on the host: /logs |
|
Hello! Could you please provide more logs to help us better diagnose your issue? To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt: The scipt will output the path of the log file once done. Once completed please upload the output files to this Github issue. Click here for more info on logging Thank you! |
ghost
added
the
|
I am getting the same dmesg dgx print error on Windows Server 2022, version 21H2 build 203487.1364. It is the last entry after Ubuntu install and occurs after every invocation of nvidia-smi (post installing CUDA 12 with a GPU). The nvidia-smi command returns: |
|
This Event looks relevant: |
|
Hello, i have probably the same problem i have also a |
|
Hello Journal trace of last connexion |
|
We also saw this issue popping off for #10357. Consider the relevant parts of kernel driver: down_read(&dxgglobal->channel_lock);
if (dxgglobal->channel.channel == NULL) {
DXG_ERR("Failed to acquire global channel lock");
return -ENODEV;
} else {
return 0;
}It seems like But it actually makes sense, here's why: And so there is no VMBus communication whatsoever without the virtual PCIE device. We also observed the same thing with @dfisk. |
Windows Version
Microsoft Windows [Version 10.0.22631.3593]
WSL Version
2.1.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.146.1-2
Distro Version
Debian GNU/Linux trixie/sid
Other Software
No response
Repro Steps
Just run WSL like usual
Expected Behavior
To see no errors
Actual Behavior
Spam of "Failed to acquire global channel lock" messages
Diagnostic Logs
I see the same behavior with the default kernel version either
The text was updated successfully, but these errors were encountered: