Date: Thu, 15 Apr 2021 10:02:40 +0200 From: Harry Schmalzbauer <freebsd@omnilan.de> To: freebsd-virtualization@freebsd.org Subject: Re: ConfigRefactor-621b5090487d rises XHCI issues [Was: Re: stable/13 (PCI reset) yet to be identified regression] Message-ID: <026c2234-c3be-acc5-2064-de096040c1d8@omnilan.de> In-Reply-To: <6f4f329a-02cb-e7cc-68dd-15e47c8b2c6b@omnilan.de> References: <3aa19f4c-7b25-8256-bb37-f260ce20863a@omnilan.de> <6f4f329a-02cb-e7cc-68dd-15e47c8b2c6b@omnilan.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 21.03.2021 um 16:35 schrieb Harry Schmalzbauer: > Am 20.03.2021 um 23:48 schrieb Harry Schmalzbauer: : : : >> but with stable/13 from yesterday the XHCI USB hub is marked >> non-functional in the Windows device manager with the hint "error >> during reset" >> and the passthrough NIC doesn"t work anymore -> looks like D3D0 or >> the like initialization fails. I'm not 100% sure for the XHCI hub >> issue, but the NIC worked without Forgot to drop the note that ab899f8937c1 fixes the XHCI issue on stable/13 with 621b5090487d (ConfigRefactor, enabling vm.cfg support)(actually using 621b5090487d+9f40a3be3d5d+4d5460a720c5+ab899f8937c1 in production on stable/13). Thanks, -harry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?026c2234-c3be-acc5-2064-de096040c1d8>