Hi there, I'm a long time happy Proxmox VE user, first of all Thanks for this great Product and the impressive feature set you have delivered for many years now!
I recently updated to Proxmox 5.2 with Kernel 4.15, and unfortunately hit a Kernel Bug. I have 2 Identical USB3-PCIe Cards in my Server which I pass through to 2 different VMs. This worked fine till now. In Proxmox 5.2 with the newer kernel 4.15 I can only start one of the VMs, the second one doesn't start, and dmesg shows the Kernel Bug described here: www<dot>spinics<dot>net/lists/stable/msg235182.html on unbinding the device. Afterwards the USB-Controller is no longer usable.
As you can see there is already a Patch for this issue attached to the Message, would it be possible to incorporate this patch into the proxmox kernel, or alternatively disable CONFIG_USB_XHCI_DBGCAP in the Kernel config to prevent this Issue (as described in this bug report: bugzilla<dot>redhat<dot>com/show_bug.cgi?id=1565131 )? Booting with the old 4.13 Kernel works as a workaround for me, so I can circumvent the Issue for now.
If you need any further Infos / Logs / Whatever, I'll gladly provide them. And sorry for the strange links, but as a new user I'm apparently not allowed to post any links here.
Thanks in Advance
seiichiro0185
I recently updated to Proxmox 5.2 with Kernel 4.15, and unfortunately hit a Kernel Bug. I have 2 Identical USB3-PCIe Cards in my Server which I pass through to 2 different VMs. This worked fine till now. In Proxmox 5.2 with the newer kernel 4.15 I can only start one of the VMs, the second one doesn't start, and dmesg shows the Kernel Bug described here: www<dot>spinics<dot>net/lists/stable/msg235182.html on unbinding the device. Afterwards the USB-Controller is no longer usable.
As you can see there is already a Patch for this issue attached to the Message, would it be possible to incorporate this patch into the proxmox kernel, or alternatively disable CONFIG_USB_XHCI_DBGCAP in the Kernel config to prevent this Issue (as described in this bug report: bugzilla<dot>redhat<dot>com/show_bug.cgi?id=1565131 )? Booting with the old 4.13 Kernel works as a workaround for me, so I can circumvent the Issue for now.
If you need any further Infos / Logs / Whatever, I'll gladly provide them. And sorry for the strange links, but as a new user I'm apparently not allowed to post any links here.
Thanks in Advance
seiichiro0185
