From owner-freebsd-current@freebsd.org  Sun Feb 21 13:41:28 2016
Return-Path: <owner-freebsd-current@freebsd.org>
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 37E4CAB0562
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sun, 21 Feb 2016 13:41:28 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 016131D30;
 Sun, 21 Feb 2016 13:41:27 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from laptop015.home.selasky.org (unknown [62.141.129.119])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id 181481FE022;
 Sun, 21 Feb 2016 14:41:19 +0100 (CET)
Subject: Re: new computer, strange usb messages at boot
To: Dimitry Andric <dim@FreeBSD.org>
References: <20160220051951.GA47875@lrosenman-dell.lerctr.org>
 <56C8310B.4010908@selasky.org>
 <9F54F75F-9FF4-4587-8FFD-C6BE6DC20E17@FreeBSD.org>
Cc: freebsd-current@freebsd.org
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <56C9BF13.4000408@selasky.org>
Date: Sun, 21 Feb 2016 14:43:47 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <9F54F75F-9FF4-4587-8FFD-C6BE6DC20E17@FreeBSD.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Feb 2016 13:41:28 -0000

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

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