Date: Sun, 21 Feb 2016 10:27:03 -0600 From: Larry Rosenman <ler@lerctr.org> To: Hans Petter Selasky <hps@selasky.org> Cc: Dimitry Andric <dim@freebsd.org>, freebsd-current@freebsd.org, owner-freebsd-current@freebsd.org Subject: Re: new computer, strange usb messages at boot Message-ID: <de4e88850e47dc95aa86de8991485044@thebighonker.lerctr.org> In-Reply-To: <56C9BF13.4000408@selasky.org> References: <20160220051951.GA47875@lrosenman-dell.lerctr.org> <56C8310B.4010908@selasky.org> <9F54F75F-9FF4-4587-8FFD-C6BE6DC20E17@FreeBSD.org> <56C9BF13.4000408@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-02-21 07:43, Hans Petter Selasky wrote: > On 02/21/16 14:33, Dimitry Andric wrote: >> If you ask me, something is just seriously broken in the way the xhci >> driver works on Haswell or higher Intel CPUs. For example, on an >> embedded Haswell box with USB3 ports: > > Hi, > > Nothing is seriously broken in the XHCI driver. Try to set: > > hw.usb.xhci.xhci_port_route=0 Does this DISABLE USB3? > > Which will route all devices to the EHCI, in your /boot/loader.conf > > Does it make any difference? > > Refer to the following print: >> xhci0: Port routing mask set to 0xffffffff > > The chipset you're using is special in that the binding of ports > between XHCI and EHCI is not fixed. Maybe some combinations are simply > not supported. > > --HPS Why is it "special"? It seems it's the norm for haswell and newer (in my case Skylake). -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?de4e88850e47dc95aa86de8991485044>