Attach BCM43602 to a VM cause system freeze and shutdown

[Ninlives]

Qubes OS version:

R4.0rc5

Affected component(s):

---

Steps to reproduce the behavior:

run qvm-pci attach <vmname> <backend>:<bdf>, I've tried every combination with permissive and no-strict-reset option.

Expected behavior:

VM(especially sys-net) is attached to the adapter so I can make the wifi work.

Actual behavior:

System freeze immediately when attach to a running VM or the VM attached to the adapter start, then shutdown after a few seconds.

General notes:

The system-freeze will happen in the setup step so I have to detach the adapter from the sys-net to finish installation.
Some one suggested to use sudo xl pci-attach <vmname> <bdf> to attach the adapter directly to a VM, the command seemed to work, but qvm-pci shows that the adapter is still not used by any VM, and the network manager didn't show any wifi device.

---

Related issues:

[andrewdavidwong]

Based on our issue reporting guidelines, this appears to be too localized for qubes-issues, since it depends on a specific hardware configuration. We ask that you please send this to the qubes-users mailing list instead. qubes-users is intended for these sorts of issues and receives much more traffic, which means that your issue is more likely to receive a response there. If, after reading our issue reporting guidelines, you believe we are mistaken, please leave a comment briefly explaining why. We'll be happy to take another look, and, if appropriate, reopen this issue. Thank you for your understanding.

[andrewdavidwong]

Based on our issue reporting guidelines, this appears to be too localized for qubes-issues, since it depends on a specific hardware configuration. We ask that you please send this to the qubes-users mailing list instead. qubes-users is intended for these sorts of issues and receives much more traffic, which means that your issue is more likely to receive a response there. If, after reading our issue reporting guidelines, you believe we are mistaken, please leave a comment briefly explaining why. We'll be happy to take another look, and, if appropriate, reopen this issue. Thank you for your understanding.