From owner-freebsd-current@freebsd.org Sun Feb 21 16:27:05 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E8CCAB074B; Sun, 21 Feb 2016 16:27:05 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thebighonker.lerctr.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A2D01D0A; Sun, 21 Feb 2016 16:27:04 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date: Content-Transfer-Encoding:Content-Type:MIME-Version; bh=frBPcLTF9bGBmJGKB8WfLtpSVoc6w+c7+sFU0+iHUCI=; b=AENET6DwoFq4IofV5inw0CsM1s Pjh12bcsEHrdYmKy87ZFBathfLNerXEjculDuT6bOzxZcOV7G6+H9WIYzgqnWd1cVEAqlfQQCjLVm wEygoHp85qoB0xd//bwyCVwvuRLuqvX9Hi8SIZnlPpHKna4dgBYS90A3cQiEi82a1OL0=; Received: from thebighonker.lerctr.org ([2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]:24710 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86 (FreeBSD)) (envelope-from ) id 1aXWqd-0007cQ-Df; Sun, 21 Feb 2016 10:27:03 -0600 Received: from rrcs-50-84-90-98.sw.biz.rr.com ([50.84.90.98]) by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Sun, 21 Feb 2016 10:27:03 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 21 Feb 2016 10:27:03 -0600 From: Larry Rosenman To: Hans Petter Selasky Cc: Dimitry Andric , freebsd-current@freebsd.org, owner-freebsd-current@freebsd.org Subject: Re: new computer, strange usb messages at boot 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> Message-ID: X-Sender: ler@lerctr.org User-Agent: Roundcube Webmail/1.1.4 X-Spam-Score: -1.0 (-) X-LERCTR-Spam-Score: -1.0 (-) X-Spam-Report: SpamScore (-1.0/5.0) ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 X-LERCTR-Spam-Report: SpamScore (-1.0/5.0) ALL_TRUSTED=-1, SHORTCIRCUIT=-0.0001 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Feb 2016 16:27:05 -0000 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