From owner-freebsd-usb@FreeBSD.ORG Tue Nov 4 00:07:08 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D90F0F20 for ; Tue, 4 Nov 2014 00:07:08 +0000 (UTC) Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6905DF1C for ; Tue, 4 Nov 2014 00:07:07 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id n3so7905114wiv.8 for ; Mon, 03 Nov 2014 16:07:00 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=Ray/xZQQ9mBtWTUEMy6F1up0UcFnn2Km3nnc/+Q9W1k=; b=IG4PkKQ2X2yRkg/J+uVPEzVT2RSDUD6OHFQPhBNeYF7dZxSmQBubinRvc+oebSTfhr nMP1AXmCT/SI3gXGmZ2EEz5ahulGO+Fp+nqpvyo0E8K2tyfleS3+Y0NBj3a9fR9jpy0j 07wQseNYwXTPKkLOd3tY65ThudLICs+6OMzrFk3TrTIFv5F5vvkefXafcQ77NmxrZieA pVIJGrfSLGfVQBh5GCzlFRUmM+LP8On0t7bdScJXVXww9M1xX58VPlExZk0wPF8AIB5E DoPEgQAZx8x5aw7PNepenL3gcCfb+K+pUKsE9yveTxrPtcdVNHwIMPIWAq6dB+rLmrLZ 16rw== X-Gm-Message-State: ALoCoQnprtkGDEkzs1KvQRsiYVxMQy8PQJGE631Z5oY9sKVxrUXGmEoePy4p6g3UbwkbonQ3N/xJ X-Received: by 10.194.209.180 with SMTP id mn20mr52359366wjc.49.1415059620572; Mon, 03 Nov 2014 16:07:00 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id ud9sm2484247wjc.20.2014.11.03.16.06.59 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Nov 2014 16:06:59 -0800 (PST) Message-ID: <5458184E.5020801@multiplay.co.uk> Date: Tue, 04 Nov 2014 00:05:34 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: "freebsd-usb@freebsd.org" Subject: ehci breaking Supermicro IPMI keyboard on uhci? Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 00:07:08 -0000 Had the problem where the Supermicro IPMI keyboard wouldn't work on some machines for a while, tonight I finally had time to play with all the options to see if anything would make it work. Turns out adding the following to loader.conf does fixes the issue: hint.ehci.0.disabled="1" So the question is why would this help? Surely disabling one controller shouldn't make devices attached to another work? Messages when working (with ehci.0 disabled): Nov 3 23:18:42 test1 kernel: usbus0 on uhci0 Nov 3 23:18:42 test1 kernel: usbus1 on uhci1 Nov 3 23:18:42 test1 kernel: usbus2 on uhci2 Nov 3 23:18:42 test1 kernel: usbus0: 12Mbps Full Speed USB v1.0 Nov 3 23:18:42 test1 kernel: usbus1: 12Mbps Full Speed USB v1.0 Nov 3 23:18:42 test1 kernel: usbus2: 12Mbps Full Speed USB v1.0 Nov 3 23:18:42 test1 kernel: ugen1.1: at usbus1 Nov 3 23:18:42 test1 kernel: uhub0: on usbus1 Nov 3 23:18:42 test1 kernel: ugen0.1: at usbus0 Nov 3 23:18:42 test1 kernel: uhub1: on usbus0 Nov 3 23:18:42 test1 kernel: ugen2.1: at usbus2 Nov 3 23:18:42 test1 kernel: uhub2: on usbus2 Nov 3 23:18:42 test1 kernel: Root mount waiting for: usbus2 Nov 3 23:18:42 test1 kernel: ugen2.2: at usbus2 Nov 3 23:18:42 test1 kernel: ukbd0: on usbus2 usbconfig list ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen2.2: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) Messages when not working: Nov 3 23:02:45 test1 kernel: usbus0 on uhci0 Nov 3 23:02:45 test1 kernel: usbus1 on uhci1 Nov 3 23:02:45 test1 kernel: usbus2 on uhci2 Nov 3 23:02:45 test1 kernel: usbus3: EHCI version 1.0 Nov 3 23:02:45 test1 kernel: usbus3 on ehci0 Nov 3 23:02:45 test1 kernel: usbus0: 12Mbps Full Speed USB v1.0 Nov 3 23:02:45 test1 kernel: usbus1: 12Mbps Full Speed USB v1.0 Nov 3 23:02:45 test1 kernel: usbus2: 12Mbps Full Speed USB v1.0 Nov 3 23:02:45 test1 kernel: usbus3: 480Mbps High Speed USB v2.0 Nov 3 23:02:45 test1 kernel: ugen1.1: at usbus1 Nov 3 23:02:45 test1 kernel: uhub0: on usbus1 Nov 3 23:02:45 test1 kernel: ugen0.1: at usbus0 Nov 3 23:02:45 test1 kernel: uhub1: on usbus0 Nov 3 23:02:45 test1 kernel: ugen3.1: at usbus3 Nov 3 23:02:45 test1 kernel: uhub2: on usbus3 Nov 3 23:02:45 test1 kernel: ugen2.1: at usbus2 Nov 3 23:02:45 test1 kernel: uhub3: on usbus2 Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: usb_alloc_device: set address 2 failed (USB_ERR_IOERROR, ignored) Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, ignored) Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, ignored) Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, ignored) Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, ignored) Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, ignored) Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: Root mount waiting for: usbus3 Nov 3 23:02:45 test1 kernel: usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR Nov 3 23:02:45 test1 kernel: usb_alloc_device: Failure selecting configuration index 0:USB_ERR_IOERROR, port 6, addr 2 (ignored) Nov 3 23:02:45 test1 kernel: ugen3.2: at usbus3 usbconfig list ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) From owner-freebsd-usb@FreeBSD.ORG Tue Nov 4 07:21:53 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 95998562 for ; Tue, 4 Nov 2014 07:21:53 +0000 (UTC) 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 52B75D67 for ; Tue, 4 Nov 2014 07:21:52 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (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 0195F1FE022; Tue, 4 Nov 2014 08:21:49 +0100 (CET) Message-ID: <54587E9B.50709@selasky.org> Date: Tue, 04 Nov 2014 08:22:03 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Steven Hartland , "freebsd-usb@freebsd.org" Subject: Re: ehci breaking Supermicro IPMI keyboard on uhci? References: <5458184E.5020801@multiplay.co.uk> In-Reply-To: <5458184E.5020801@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 07:21:53 -0000 On 11/04/14 01:05, Steven Hartland wrote: > Had the problem where the Supermicro IPMI keyboard wouldn't work on some > machines for a while, tonight I finally had time to play with all the > options to see if anything would make it work. > > Turns out adding the following to loader.conf does fixes the issue: > hint.ehci.0.disabled="1" > > So the question is why would this help? > > Surely disabling one controller shouldn't make devices attached to > another work? > Hi, The USB device is failing to enumerate. Are you sure there is no XHCI controller on this device? --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Nov 4 16:42:27 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5BF78E20 for ; Tue, 4 Nov 2014 16:42:27 +0000 (UTC) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DEE9EC74 for ; Tue, 4 Nov 2014 16:42:26 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id q5so9829525wiv.11 for ; Tue, 04 Nov 2014 08:42:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=nwyYEhi2k37N6EsS0y+19Xl+TAvZ4Yq8IymuQ6oirkk=; b=N0j5/95Hr1xIc4ubqcdhBy2Pysm+6FSmorVLHpE0nLZN/1VnUZeBlKT4UPs/1vQZzb kO8joz61QNWB4HWXpU+GyospWxpCuo+G3mr9mjgnSYiEXS/q6BddQYdiGOWOgW1hq/+D DMQCBvnxhR8QVgoHi//G2rzqrWsgMJ/VjYHyX4DTVOeRnyxFCyKpVlIAO9hRMZ4+FeGZ cIRlx5NPNO4MjszTQmsVGAed1QnVJE81xJi7Or25C0bWR8stJCee6i/sS7WZqqLgeSbh hkFzCAoB1Nwe/PHOEJKOIIxH5q9ZWueJd9Ch6MAXDFfjInGVzEc5ZJvZqZ1Mv08O8Df5 L5aA== X-Gm-Message-State: ALoCoQlwqg3gDagueR8c++dAcu1CVCfQsMeCrn5xsba1wU78JY8C5RlJv8mn2Y/popCi4xICZQsX X-Received: by 10.194.103.230 with SMTP id fz6mr56959722wjb.53.1415119339431; Tue, 04 Nov 2014 08:42:19 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id bf6sm1116581wjb.13.2014.11.04.08.42.17 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Nov 2014 08:42:18 -0800 (PST) Message-ID: <54590195.7090600@multiplay.co.uk> Date: Tue, 04 Nov 2014 16:40:53 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Hans Petter Selasky , "freebsd-usb@freebsd.org" Subject: Re: ehci breaking Supermicro IPMI keyboard on uhci? References: <5458184E.5020801@multiplay.co.uk> <54587E9B.50709@selasky.org> In-Reply-To: <54587E9B.50709@selasky.org> Content-Type: multipart/mixed; boundary="------------000703050905000707080702" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 16:42:27 -0000 This is a multi-part message in MIME format. --------------000703050905000707080702 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 04/11/2014 07:22, Hans Petter Selasky wrote: > On 11/04/14 01:05, Steven Hartland wrote: >> Had the problem where the Supermicro IPMI keyboard wouldn't work on some >> machines for a while, tonight I finally had time to play with all the >> options to see if anything would make it work. >> >> Turns out adding the following to loader.conf does fixes the issue: >> hint.ehci.0.disabled="1" >> >> So the question is why would this help? >> >> Surely disabling one controller shouldn't make devices attached to >> another work? >> > > Hi, > > The USB device is failing to enumerate. Are you sure there is no XHCI > controller on this device? I did try removing xhci from my kernel config, but that had no effect, only when I disabled the ehci controller did it correctly enumerate the devices attached to the uhci controller. Attached is the outuput from pciconf -l -v in case that helps. If there's anything else I can provide which will help just let me know. For reference I'm currently testing 10.1-RC4 on this box. Regards Steve --------------000703050905000707080702 Content-Type: text/plain; charset=windows-1252; name="pciconfig.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="pciconfig.txt" pciconf -l -v hostb0@pci0:0:0:0: class=0x060000 card=0xa28015d9 chip=0x40038086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset Memory Controller Hub' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0xa28015d9 chip=0x40218086 rev=0x20 hdr=0x01 vendor = 'Intel Corporation' device = '5400 Chipset PCI Express Port 1' class = bridge subclass = PCI-PCI pcib2@pci0:0:3:0: class=0x060400 card=0xa28015d9 chip=0x40238086 rev=0x20 hdr=0x01 vendor = 'Intel Corporation' device = '5400 Chipset PCI Express Port 3' class = bridge subclass = PCI-PCI pcib3@pci0:0:5:0: class=0x060400 card=0xa28015d9 chip=0x40258086 rev=0x20 hdr=0x01 vendor = 'Intel Corporation' device = '5400 Chipset PCI Express Port 5' class = bridge subclass = PCI-PCI pcib4@pci0:0:7:0: class=0x060400 card=0xa28015d9 chip=0x40278086 rev=0x20 hdr=0x01 vendor = 'Intel Corporation' device = '5400 Chipset PCI Express Port 7' class = bridge subclass = PCI-PCI pcib10@pci0:0:9:0: class=0x060400 card=0xa28015d9 chip=0x40298086 rev=0x20 hdr=0x01 vendor = 'Intel Corporation' device = '5400 Chipset PCI Express Port 9' class = bridge subclass = PCI-PCI hostb1@pci0:0:16:0: class=0x060000 card=0xa28015d9 chip=0x40308086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FSB Registers' class = bridge subclass = HOST-PCI hostb2@pci0:0:16:1: class=0x060000 card=0xa28015d9 chip=0x40308086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FSB Registers' class = bridge subclass = HOST-PCI hostb3@pci0:0:16:2: class=0x060000 card=0xa28015d9 chip=0x40308086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FSB Registers' class = bridge subclass = HOST-PCI hostb4@pci0:0:16:3: class=0x060000 card=0xa28015d9 chip=0x40308086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FSB Registers' class = bridge subclass = HOST-PCI hostb5@pci0:0:16:4: class=0x060000 card=0xa28015d9 chip=0x40308086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FSB Registers' class = bridge subclass = HOST-PCI hostb6@pci0:0:17:0: class=0x060000 card=0xa28015d9 chip=0x40318086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset CE/SF Registers' class = bridge subclass = HOST-PCI hostb7@pci0:0:21:0: class=0x060000 card=0xa28015d9 chip=0x40358086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FBD Registers' class = bridge subclass = HOST-PCI hostb8@pci0:0:21:1: class=0x060000 card=0xa28015d9 chip=0x40358086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FBD Registers' class = bridge subclass = HOST-PCI hostb9@pci0:0:22:0: class=0x060000 card=0xa28015d9 chip=0x40368086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FBD Registers' class = bridge subclass = HOST-PCI hostb10@pci0:0:22:1: class=0x060000 card=0xa28015d9 chip=0x40368086 rev=0x20 hdr=0x00 vendor = 'Intel Corporation' device = '5400 Chipset FBD Registers' class = bridge subclass = HOST-PCI pcib11@pci0:0:28:0: class=0x060400 card=0xa28015d9 chip=0x26908086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset PCI Express Root Port 1' class = bridge subclass = PCI-PCI uhci0@pci0:0:29:0: class=0x0c0300 card=0xa28015d9 chip=0x26888086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset UHCI USB Controller' class = serial bus subclass = USB uhci1@pci0:0:29:1: class=0x0c0300 card=0xa28015d9 chip=0x26898086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset UHCI USB Controller' class = serial bus subclass = USB uhci2@pci0:0:29:2: class=0x0c0300 card=0xa28015d9 chip=0x268a8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset UHCI USB Controller' class = serial bus subclass = USB ehci0@pci0:0:29:7: class=0x0c0320 card=0xa28015d9 chip=0x268c8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset EHCI USB2 Controller' class = serial bus subclass = USB pcib12@pci0:0:30:0: class=0x060401 card=0xa28015d9 chip=0x244e8086 rev=0xd9 hdr=0x01 vendor = 'Intel Corporation' device = '82801 PCI Bridge' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0: class=0x060100 card=0xa28015d9 chip=0x26708086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset LPC Interface Controller' class = bridge subclass = PCI-ISA atapci0@pci0:0:31:1: class=0x01018a card=0xa28015d9 chip=0x269e8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB IDE Controller' class = mass storage subclass = ATA none0@pci0:0:31:3: class=0x0c0500 card=0xa28015d9 chip=0x269b8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset SMBus Controller' class = serial bus subclass = SMBus pcib5@pci0:4:0:0: class=0x060400 card=0xa28015d9 chip=0x35008086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '6311ESB/6321ESB PCI Express Upstream Port' class = bridge subclass = PCI-PCI pcib9@pci0:4:0:3: class=0x060400 card=0xa28015d9 chip=0x350c8086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '6311ESB/6321ESB PCI Express to PCI-X Bridge' class = bridge subclass = PCI-PCI pcib6@pci0:5:0:0: class=0x060400 card=0xa28015d9 chip=0x35108086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '6311ESB/6321ESB PCI Express Downstream Port E1' class = bridge subclass = PCI-PCI pcib7@pci0:6:0:0: class=0x060400 card=0x00000000 chip=0x03708086 rev=0x00 hdr=0x01 vendor = 'Intel Corporation' device = '80333 Segment-A PCI Express-to-PCI Express Bridge' class = bridge subclass = PCI-PCI pcib8@pci0:6:0:2: class=0x060400 card=0x00000000 chip=0x03728086 rev=0x00 hdr=0x01 vendor = 'Intel Corporation' device = '80333 Segment-B PCI Express-to-PCI Express Bridge' class = bridge subclass = PCI-PCI arcmsr0@pci0:7:14:0: class=0x010400 card=0x122017d3 chip=0x122017d3 rev=0x00 hdr=0x00 vendor = 'Areca Technology Corp.' device = 'ARC-1220 8-Port PCI-Express to SATA RAID Controller' class = mass storage subclass = RAID igb0@pci0:10:0:0: class=0x020000 card=0x10a715d9 chip=0x10a78086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82575EB Gigabit Network Connection' class = network subclass = ethernet igb1@pci0:10:0:1: class=0x020000 card=0x10a715d9 chip=0x10a78086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82575EB Gigabit Network Connection' class = network subclass = ethernet vgapci0@pci0:12:1:0: class=0x030000 card=0xa28015d9 chip=0x515e1002 rev=0x02 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'ES1000' class = display subclass = VGA --------------000703050905000707080702-- From owner-freebsd-usb@FreeBSD.ORG Tue Nov 4 16:45:30 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EFFFCF65 for ; Tue, 4 Nov 2014 16:45:30 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (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 B2A0CC9A for ; Tue, 4 Nov 2014 16:45:30 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (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 8EBF31FE022; Tue, 4 Nov 2014 17:45:28 +0100 (CET) Message-ID: <545902B4.8030001@selasky.org> Date: Tue, 04 Nov 2014 17:45:40 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Steven Hartland , "freebsd-usb@freebsd.org" Subject: Re: ehci breaking Supermicro IPMI keyboard on uhci? References: <5458184E.5020801@multiplay.co.uk> <54587E9B.50709@selasky.org> <54590195.7090600@multiplay.co.uk> In-Reply-To: <54590195.7090600@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 16:45:31 -0000 On 11/04/14 17:40, Steven Hartland wrote: > On 04/11/2014 07:22, Hans Petter Selasky wrote: >> On 11/04/14 01:05, Steven Hartland wrote: >>> Had the problem where the Supermicro IPMI keyboard wouldn't work on some >>> machines for a while, tonight I finally had time to play with all the >>> options to see if anything would make it work. >>> >>> Turns out adding the following to loader.conf does fixes the issue: >>> hint.ehci.0.disabled="1" >>> >>> So the question is why would this help? >>> >>> Surely disabling one controller shouldn't make devices attached to >>> another work? >>> >> >> Hi, >> >> The USB device is failing to enumerate. Are you sure there is no XHCI >> controller on this device? > I did try removing xhci from my kernel config, but that had no effect, > only when I disabled the ehci controller did it correctly enumerate the > devices attached to the uhci controller. > > Attached is the outuput from pciconf -l -v in case that helps. If > there's anything else I can provide which will help just let me know. > > For reference I'm currently testing 10.1-RC4 on this box. > > Regards > Steve Maybe you can check the PCI IDs with Linux EHCI driver, if your hardware requires some special quirks? --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Nov 4 17:51:52 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A00E4D1D for ; Tue, 4 Nov 2014 17:51:52 +0000 (UTC) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3173A68A for ; Tue, 4 Nov 2014 17:51:51 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id d1so10031345wiv.3 for ; Tue, 04 Nov 2014 09:51:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=wNglIAEzS2+AZ2mWZ53yPNZ4K2OOauENbPLLNWQSXSk=; b=EG7GzmsopbYxXwf5fg1Bwtbcrt/LIhn+Li33l8e0pyJKmOO+3sqqr8lmzL/7oihgHS NcBgfb6SF2AGFz9LhYuo/oHLXtOsNxWIkktta8HC0SFwSCrBei0LWM9yFky4e1j8unV/ b7JnAC59m3KOBsSHmjHHIm9CL+SCIlxuQLqnLrOSdtaDtCi5W7EnpZ2kGnkTBHD1SB4f FjpxrxEXphj1xF346MXvGVQe4BXjo6apB5+/UYvam4CvGd2ViEsRjiCPS4BpOK8/Hih9 3myuiVOPrSN81riVTYy36ZMiKRKEHN518KU81aRGDNcLCyEU4uAfI9kHqT/qG+qwfbPj GEbQ== X-Gm-Message-State: ALoCoQnTifK9XKFg9/leo89++Mb2q7eIime+1e0EKvXm1CL2sfVM7PSrxgpZnaypd8uhVpZy4KyL X-Received: by 10.194.240.68 with SMTP id vy4mr58957627wjc.36.1415123038268; Tue, 04 Nov 2014 09:43:58 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id bq8sm1304523wjb.6.2014.11.04.09.43.56 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Nov 2014 09:43:57 -0800 (PST) Message-ID: <54591009.5020401@multiplay.co.uk> Date: Tue, 04 Nov 2014 17:42:33 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Hans Petter Selasky , "freebsd-usb@freebsd.org" Subject: Re: ehci breaking Supermicro IPMI keyboard on uhci? References: <5458184E.5020801@multiplay.co.uk> <54587E9B.50709@selasky.org> <54590195.7090600@multiplay.co.uk> <545902B4.8030001@selasky.org> In-Reply-To: <545902B4.8030001@selasky.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 17:51:52 -0000 On 04/11/2014 16:45, Hans Petter Selasky wrote: > On 11/04/14 17:40, Steven Hartland wrote: >> On 04/11/2014 07:22, Hans Petter Selasky wrote: >>> On 11/04/14 01:05, Steven Hartland wrote: >>>> Had the problem where the Supermicro IPMI keyboard wouldn't work on >>>> some >>>> machines for a while, tonight I finally had time to play with all the >>>> options to see if anything would make it work. >>>> >>>> Turns out adding the following to loader.conf does fixes the issue: >>>> hint.ehci.0.disabled="1" >>>> >>>> So the question is why would this help? >>>> >>>> Surely disabling one controller shouldn't make devices attached to >>>> another work? >>>> >>> >>> Hi, >>> >>> The USB device is failing to enumerate. Are you sure there is no XHCI >>> controller on this device? >> I did try removing xhci from my kernel config, but that had no effect, >> only when I disabled the ehci controller did it correctly enumerate the >> devices attached to the uhci controller. >> >> Attached is the outuput from pciconf -l -v in case that helps. If >> there's anything else I can provide which will help just let me know. >> >> For reference I'm currently testing 10.1-RC4 on this box. >> >> Regards >> Steve > > Maybe you can check the PCI IDs with Linux EHCI driver, if your > hardware requires some special quirks? I cant find any mention of quirks for the Intel USB controller PCI IDs but I might be looking in the wrong place, do you have a link to what I should be searching though? I did however find the following which is for the exact device I'm having issues with and seems to indicate the HW might have an issue with HighSpeed mode. https://lkml.org/lkml/2012/4/19/224 http://lkml.iu.edu//hypermail/linux/kernel/1204.3/03115.html Which makes me wonder if hw.usb.ehci.no_hs=1 would also result in a working device. Regards Steve From owner-freebsd-usb@FreeBSD.ORG Tue Nov 4 20:23:49 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6C29A2BE for ; Tue, 4 Nov 2014 20:23:49 +0000 (UTC) Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 001719DF for ; Tue, 4 Nov 2014 20:23:48 +0000 (UTC) Received: by mail-wg0-f46.google.com with SMTP id x13so14499768wgg.33 for ; Tue, 04 Nov 2014 12:23:40 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=93oZJzf4l94q1wMloBomJi5kLeQXnXbPy5Gx9zcxsYs=; b=eCr16qO16S15E3rUBDMiHrjIlSZaL1j5FZqwZLTI6YGQa+brPROyzNTRClMvycWuoQ K6+ZsyubUQXJSYpQM9gSKo/OctDdJOKPQEf6G6trtMqEgufoUe0Q5HXlpMW5EKvxjBTP MEfKfcsWUcK0BtC75yJoXYoN1a/MtC3So8I77QPeTSXpbE1zPop+jVXxA183reuKGhEG TPW3bue+gdiuFZJ0gXXMfn11913ur3kI3bh+s0twOnNoETIfqEtTkFc5LxyuFRt7PR8c lgAHAp9gf2NWsnEeIbCMuqZ8UNEmtY73Wert2aTG/kXvhvzC1ncTy89WxXzqBkqa+xhT y4pg== X-Gm-Message-State: ALoCoQlyTcYrDitS7JpW8OF5BGKYWd5o96N+ePTeFDykQ/rU0MLngH5zNIDuBfv9J0+gs0aAs5E5 X-Received: by 10.180.11.227 with SMTP id t3mr229807wib.45.1415132620811; Tue, 04 Nov 2014 12:23:40 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id dc8sm2212802wib.7.2014.11.04.12.23.39 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Nov 2014 12:23:39 -0800 (PST) Message-ID: <54593576.9050100@multiplay.co.uk> Date: Tue, 04 Nov 2014 20:22:14 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Hans Petter Selasky , "freebsd-usb@freebsd.org" Subject: Re: ehci breaking Supermicro IPMI keyboard on uhci? References: <5458184E.5020801@multiplay.co.uk> <54587E9B.50709@selasky.org> <54590195.7090600@multiplay.co.uk> <545902B4.8030001@selasky.org> <54591009.5020401@multiplay.co.uk> In-Reply-To: <54591009.5020401@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 20:23:49 -0000 On 04/11/2014 17:42, Steven Hartland wrote: > > On 04/11/2014 16:45, Hans Petter Selasky wrote: >> On 11/04/14 17:40, Steven Hartland wrote: >>> On 04/11/2014 07:22, Hans Petter Selasky wrote: >>>> On 11/04/14 01:05, Steven Hartland wrote: >>>>> Had the problem where the Supermicro IPMI keyboard wouldn't work >>>>> on some >>>>> machines for a while, tonight I finally had time to play with all the >>>>> options to see if anything would make it work. >>>>> >>>>> Turns out adding the following to loader.conf does fixes the issue: >>>>> hint.ehci.0.disabled="1" >>>>> >>>>> So the question is why would this help? >>>>> >>>>> Surely disabling one controller shouldn't make devices attached to >>>>> another work? >>>>> >>>> >>>> Hi, >>>> >>>> The USB device is failing to enumerate. Are you sure there is no XHCI >>>> controller on this device? >>> I did try removing xhci from my kernel config, but that had no effect, >>> only when I disabled the ehci controller did it correctly enumerate the >>> devices attached to the uhci controller. >>> >>> Attached is the outuput from pciconf -l -v in case that helps. If >>> there's anything else I can provide which will help just let me know. >>> >>> For reference I'm currently testing 10.1-RC4 on this box. >>> >>> Regards >>> Steve >> >> Maybe you can check the PCI IDs with Linux EHCI driver, if your >> hardware requires some special quirks? > I cant find any mention of quirks for the Intel USB controller PCI IDs > but I might be looking in the wrong place, do you have a link to what > I should be searching though? > > I did however find the following which is for the exact device I'm > having issues with and seems to indicate the HW might have an issue > with HighSpeed mode. > > https://lkml.org/lkml/2012/4/19/224 > http://lkml.iu.edu//hypermail/linux/kernel/1204.3/03115.html > > Which makes me wonder if hw.usb.ehci.no_hs=1 would also result in a > working device. > Ok so without the disabled hit but with no_hs=1 the devices still works and usbconfig list shows: ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen2.2: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) and messages: Nov 4 19:28:53 test1 kernel: usbus0 on uhci0 Nov 4 19:28:53 test1 kernel: usbus1 on uhci1 Nov 4 19:28:53 test1 kernel: usbus2 on uhci2 Nov 4 19:28:53 test1 kernel: usbus3: EHCI version 1.0 Nov 4 19:28:53 test1 kernel: usbus3 on ehci0 Nov 4 19:28:53 test1 kernel: usbus0: 12Mbps Full Speed USB v1.0 Nov 4 19:28:53 test1 kernel: usbus1: 12Mbps Full Speed USB v1.0 Nov 4 19:28:53 test1 kernel: usbus2: 12Mbps Full Speed USB v1.0 Nov 4 19:28:53 test1 kernel: usbus3: 480Mbps High Speed USB v2.0 Nov 4 19:28:53 test1 kernel: ugen1.1: at usbus1 Nov 4 19:28:53 test1 kernel: uhub0: on usbus1 Nov 4 19:28:53 test1 kernel: ugen0.1: at usbus0 Nov 4 19:28:53 test1 kernel: uhub1: on usbus0 Nov 4 19:28:53 test1 kernel: ugen3.1: at usbus3 Nov 4 19:28:53 test1 kernel: uhub2: on usbus3 Nov 4 19:28:53 test1 kernel: ugen2.1: at usbus2 Nov 4 19:28:53 test1 kernel: uhub3: on usbus2 Nov 4 19:28:53 test1 kernel: Root mount waiting for: usbus3 Nov 4 19:28:53 test1 kernel: Root mount waiting for: usbus3 Nov 4 19:28:53 test1 kernel: Root mount waiting for: usbus3 Nov 4 19:28:53 test1 kernel: ugen2.2: at usbus2 Nov 4 19:28:53 test1 kernel: ukbd0: on usbus2 So now I'm even more confused :( Regards Steve From owner-freebsd-usb@FreeBSD.ORG Tue Nov 4 21:58:47 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5D348F4 for ; Tue, 4 Nov 2014 21:58:47 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (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 08BB360F for ; Tue, 4 Nov 2014 21:58:46 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (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 668F91FE022; Tue, 4 Nov 2014 22:58:44 +0100 (CET) Message-ID: <54594C20.6090006@selasky.org> Date: Tue, 04 Nov 2014 22:58:56 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Steven Hartland , "freebsd-usb@freebsd.org" Subject: Re: ehci breaking Supermicro IPMI keyboard on uhci? References: <5458184E.5020801@multiplay.co.uk> <54587E9B.50709@selasky.org> <54590195.7090600@multiplay.co.uk> <545902B4.8030001@selasky.org> <54591009.5020401@multiplay.co.uk> <54593576.9050100@multiplay.co.uk> In-Reply-To: <54593576.9050100@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 21:58:47 -0000 On 11/04/14 21:22, Steven Hartland wrote: > > On 04/11/2014 17:42, Steven Hartland wrote: >> >> On 04/11/2014 16:45, Hans Petter Selasky wrote: >>> On 11/04/14 17:40, Steven Hartland wrote: >>>> On 04/11/2014 07:22, Hans Petter Selasky wrote: >>>>> On 11/04/14 01:05, Steven Hartland wrote: >>>>>> Had the problem where the Supermicro IPMI keyboard wouldn't work >>>>>> on some >>>>>> machines for a while, tonight I finally had time to play with all the >>>>>> options to see if anything would make it work. >>>>>> >>>>>> Turns out adding the following to loader.conf does fixes the issue: >>>>>> hint.ehci.0.disabled="1" >>>>>> >>>>>> So the question is why would this help? >>>>>> >>>>>> Surely disabling one controller shouldn't make devices attached to >>>>>> another work? >>>>>> >>>>> >>>>> Hi, >>>>> >>>>> The USB device is failing to enumerate. Are you sure there is no XHCI >>>>> controller on this device? >>>> I did try removing xhci from my kernel config, but that had no effect, >>>> only when I disabled the ehci controller did it correctly enumerate the >>>> devices attached to the uhci controller. >>>> >>>> Attached is the outuput from pciconf -l -v in case that helps. If >>>> there's anything else I can provide which will help just let me know. >>>> >>>> For reference I'm currently testing 10.1-RC4 on this box. >>>> >>>> Regards >>>> Steve >>> >>> Maybe you can check the PCI IDs with Linux EHCI driver, if your >>> hardware requires some special quirks? >> I cant find any mention of quirks for the Intel USB controller PCI IDs >> but I might be looking in the wrong place, do you have a link to what >> I should be searching though? >> >> I did however find the following which is for the exact device I'm >> having issues with and seems to indicate the HW might have an issue >> with HighSpeed mode. >> >> https://lkml.org/lkml/2012/4/19/224 >> http://lkml.iu.edu//hypermail/linux/kernel/1204.3/03115.html >> >> Which makes me wonder if hw.usb.ehci.no_hs=1 would also result in a >> working device. >> > Ok so without the disabled hit but with no_hs=1 the devices still works > and usbconfig list shows: > ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=SAVE (0mA) > ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=SAVE (0mA) > ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=SAVE (0mA) > ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=SAVE (0mA) > ugen2.2: at usbus2, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON (100mA) > > and messages: > Nov 4 19:28:53 test1 kernel: usbus0 on uhci0 > Nov 4 19:28:53 test1 kernel: usbus1 on uhci1 > Nov 4 19:28:53 test1 kernel: usbus2 on uhci2 > Nov 4 19:28:53 test1 kernel: usbus3: EHCI version 1.0 > Nov 4 19:28:53 test1 kernel: usbus3 on ehci0 > Nov 4 19:28:53 test1 kernel: usbus0: 12Mbps Full Speed USB v1.0 > Nov 4 19:28:53 test1 kernel: usbus1: 12Mbps Full Speed USB v1.0 > Nov 4 19:28:53 test1 kernel: usbus2: 12Mbps Full Speed USB v1.0 > Nov 4 19:28:53 test1 kernel: usbus3: 480Mbps High Speed USB v2.0 > Nov 4 19:28:53 test1 kernel: ugen1.1: at usbus1 > Nov 4 19:28:53 test1 kernel: uhub0: rev 1.00/1.00, addr 1> on usbus1 > Nov 4 19:28:53 test1 kernel: ugen0.1: at usbus0 > Nov 4 19:28:53 test1 kernel: uhub1: rev 1.00/1.00, addr 1> on usbus0 > Nov 4 19:28:53 test1 kernel: ugen3.1: at usbus3 > Nov 4 19:28:53 test1 kernel: uhub2: rev 2.00/1.00, addr 1> on usbus3 > Nov 4 19:28:53 test1 kernel: ugen2.1: at usbus2 > Nov 4 19:28:53 test1 kernel: uhub3: rev 1.00/1.00, addr 1> on usbus2 > Nov 4 19:28:53 test1 kernel: Root mount waiting for: usbus3 > Nov 4 19:28:53 test1 kernel: Root mount waiting for: usbus3 > Nov 4 19:28:53 test1 kernel: Root mount waiting for: usbus3 > Nov 4 19:28:53 test1 kernel: ugen2.2: at usbus2 > Nov 4 19:28:53 test1 kernel: ukbd0: 0/0, rev 2.00/0.01, addr 2> on usbus2 > > So now I'm even more confused :( > > Regards > Steve > Maybe we could set the no-hs as a fallback from the EHCI controller to the UHC/OHCI ones ... Looks like a HW issue. BTW: are there any high speed devices connected to this board? --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Nov 4 23:27:47 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4D148C51 for ; Tue, 4 Nov 2014 23:27:47 +0000 (UTC) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CEFE6F1 for ; Tue, 4 Nov 2014 23:27:46 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id q5so514378wiv.5 for ; Tue, 04 Nov 2014 15:27:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=FIGlRzI582pKWbzLMzvsEsfIz04zE1hRlaVZ75cBLFo=; b=LLqH6hrKT1U1r9P4i59w5ZvFjWCNl6cgaom/RyCjx5G2c1Mcdf9H5pHBao4G8/lBTY a/C5HjK7qSIyG3gZ5T14I8EPdRVOteiU5Q2q1xF5ZiwpwSJx6Mfs3QMNYv/WThaW0Lbo SHMrF2zCcZx2lkDafaXWzceOhjckyhDtoEWI316eSMJxWW7a1PHzDz4TRS65pyCYgtbD D1HOnzq1DaO7if2iGMcX5txh6tUKZR5ygDqko9qZts09P+6aOR0b06hND307LsvwQAOq 7UO8tOcNKTf96kVTu7bgd0ZVOaHr3UbWSM6HHZ35zebKnmm6hmbEH3iX55uDPlRgzr+X 0fXw== X-Gm-Message-State: ALoCoQnj2noVPEk0C+19zGUprWBforAIzhONKu4IxYRKAFaQBjS4T7ksbzDhBjMwh9A7TaAvRNfA X-Received: by 10.194.77.142 with SMTP id s14mr3801422wjw.94.1415143664078; Tue, 04 Nov 2014 15:27:44 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id bf6sm2116571wjb.13.2014.11.04.15.27.42 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Nov 2014 15:27:43 -0800 (PST) Message-ID: <5459609B.10502@multiplay.co.uk> Date: Tue, 04 Nov 2014 23:26:19 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Hans Petter Selasky , "freebsd-usb@freebsd.org" Subject: Re: ehci breaking Supermicro IPMI keyboard on uhci? References: <5458184E.5020801@multiplay.co.uk> <54587E9B.50709@selasky.org> <54590195.7090600@multiplay.co.uk> <545902B4.8030001@selasky.org> <54591009.5020401@multiplay.co.uk> <54593576.9050100@multiplay.co.uk> <54594C20.6090006@selasky.org> In-Reply-To: <54594C20.6090006@selasky.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 23:27:47 -0000 On 04/11/2014 21:58, Hans Petter Selasky wrote: > On 11/04/14 21:22, Steven Hartland wrote: >> >> On 04/11/2014 17:42, Steven Hartland wrote: >>> >>> On 04/11/2014 16:45, Hans Petter Selasky wrote: >>>> On 11/04/14 17:40, Steven Hartland wrote: >>>>> On 04/11/2014 07:22, Hans Petter Selasky wrote: >>>>>> On 11/04/14 01:05, Steven Hartland wrote: >>>>>>> Had the problem where the Supermicro IPMI keyboard wouldn't work >>>>>>> on some >>>>>>> machines for a while, tonight I finally had time to play with >>>>>>> all the >>>>>>> options to see if anything would make it work. >>>>>>> >>>>>>> Turns out adding the following to loader.conf does fixes the issue: >>>>>>> hint.ehci.0.disabled="1" >>>>>>> >>>>>>> So the question is why would this help? >>>>>>> >>>>>>> Surely disabling one controller shouldn't make devices attached to >>>>>>> another work? >>>>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> The USB device is failing to enumerate. Are you sure there is no >>>>>> XHCI >>>>>> controller on this device? >>>>> I did try removing xhci from my kernel config, but that had no >>>>> effect, >>>>> only when I disabled the ehci controller did it correctly >>>>> enumerate the >>>>> devices attached to the uhci controller. >>>>> >>>>> Attached is the outuput from pciconf -l -v in case that helps. If >>>>> there's anything else I can provide which will help just let me know. >>>>> >>>>> For reference I'm currently testing 10.1-RC4 on this box. >>>>> >>>>> Regards >>>>> Steve >>>> >>>> Maybe you can check the PCI IDs with Linux EHCI driver, if your >>>> hardware requires some special quirks? >>> I cant find any mention of quirks for the Intel USB controller PCI IDs >>> but I might be looking in the wrong place, do you have a link to what >>> I should be searching though? >>> >>> I did however find the following which is for the exact device I'm >>> having issues with and seems to indicate the HW might have an issue >>> with HighSpeed mode. >>> >>> https://lkml.org/lkml/2012/4/19/224 >>> http://lkml.iu.edu//hypermail/linux/kernel/1204.3/03115.html >>> >>> Which makes me wonder if hw.usb.ehci.no_hs=1 would also result in a >>> working device. >>> >> Ok so without the disabled hit but with no_hs=1 the devices still works >> and usbconfig list shows: >> ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL >> (12Mbps) pwr=SAVE (0mA) >> ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL >> (12Mbps) pwr=SAVE (0mA) >> ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH >> (480Mbps) pwr=SAVE (0mA) >> ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL >> (12Mbps) pwr=SAVE (0mA) >> ugen2.2: at usbus2, cfg=0 md=HOST spd=FULL >> (12Mbps) pwr=ON (100mA) >> >> and messages: >> Nov 4 19:28:53 test1 kernel: usbus0 on uhci0 >> Nov 4 19:28:53 test1 kernel: usbus1 on uhci1 >> Nov 4 19:28:53 test1 kernel: usbus2 on uhci2 >> Nov 4 19:28:53 test1 kernel: usbus3: EHCI version 1.0 >> Nov 4 19:28:53 test1 kernel: usbus3 on ehci0 >> Nov 4 19:28:53 test1 kernel: usbus0: 12Mbps Full Speed USB v1.0 >> Nov 4 19:28:53 test1 kernel: usbus1: 12Mbps Full Speed USB v1.0 >> Nov 4 19:28:53 test1 kernel: usbus2: 12Mbps Full Speed USB v1.0 >> Nov 4 19:28:53 test1 kernel: usbus3: 480Mbps High Speed USB v2.0 >> Nov 4 19:28:53 test1 kernel: ugen1.1: at usbus1 >> Nov 4 19:28:53 test1 kernel: uhub0: > rev 1.00/1.00, addr 1> on usbus1 >> Nov 4 19:28:53 test1 kernel: ugen0.1: at usbus0 >> Nov 4 19:28:53 test1 kernel: uhub1: > rev 1.00/1.00, addr 1> on usbus0 >> Nov 4 19:28:53 test1 kernel: ugen3.1: at usbus3 >> Nov 4 19:28:53 test1 kernel: uhub2: > rev 2.00/1.00, addr 1> on usbus3 >> Nov 4 19:28:53 test1 kernel: ugen2.1: at usbus2 >> Nov 4 19:28:53 test1 kernel: uhub3: > rev 1.00/1.00, addr 1> on usbus2 >> Nov 4 19:28:53 test1 kernel: Root mount waiting for: usbus3 >> Nov 4 19:28:53 test1 kernel: Root mount waiting for: usbus3 >> Nov 4 19:28:53 test1 kernel: Root mount waiting for: usbus3 >> Nov 4 19:28:53 test1 kernel: ugen2.2: at usbus2 >> Nov 4 19:28:53 test1 kernel: ukbd0: > 0/0, rev 2.00/0.01, addr 2> on usbus2 >> >> So now I'm even more confused :( >> > > Maybe we could set the no-hs as a fallback from the EHCI controller to > the UHC/OHCI ones ... > > Looks like a HW issue. BTW: are there any high speed devices connected > to this board? > The only connected devices are the onboard IPMI which provides the keyboard and mouse + virtual media. From what I can see its meant to be USB 2.0 compilient but there's a lot of reports of issues with them, so I wouldn't rule out a implementation issue. The following seems related: http://www.supermicro.com/support/faqs/faq.cfm?faq=11530 I've asked Supermicro for an updated firmware, we're already running the latest they have on their site (1.64) Falling back to full speed if high speed fails to negotiate seems like a good plan though. Do you think that's going to be easy to do? Count me in as tester if that will help :) Regards Steve From owner-freebsd-usb@FreeBSD.ORG Wed Nov 5 02:10:51 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D423890C for ; Wed, 5 Nov 2014 02:10:51 +0000 (UTC) Received: from host.cinglenet.com (mail.cinglenet.com [50.28.38.180]) (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 AC9B9A43 for ; Wed, 5 Nov 2014 02:10:51 +0000 (UTC) Received: from nobody by host.cinglenet.com with local (Exim 4.82) (envelope-from ) id 1XlpSw-0000Np-Hf for freebsd-usb@freebsd.org; Tue, 04 Nov 2014 19:32:54 -0600 To: freebsd-usb@freebsd.org Subject: Delivery Notification From: "FedEx Ship Manager" X-Mailer: MMailerv3.0 Reply-To: "FedEx Ship Manager" Mime-Version: 1.0 Message-Id: Date: Tue, 04 Nov 2014 19:32:54 -0600 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.cinglenet.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [99 99] / [47 12] X-AntiAbuse: Sender Address Domain - host.cinglenet.com X-Get-Message-Sender-Via: host.cinglenet.com: uid via acl_c_vhost_owner from authenticated_id: nobody from /only user confirmed/virtual account not confirmed Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2014 02:10:52 -0000   FedEx Dear Customer, Your parcel has arrived at October 30. Courier was unable to deliver the parcel to you. To receive your parcel, print this label and go to the nearest office. Get Shipment Label FedEx 1995-2014 From owner-freebsd-usb@FreeBSD.ORG Wed Nov 5 07:17:21 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8B9E2E3E for ; Wed, 5 Nov 2014 07:17:21 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (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 38793BA6 for ; Wed, 5 Nov 2014 07:17:21 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (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 F19A41FE022; Wed, 5 Nov 2014 08:17:18 +0100 (CET) Message-ID: <5459CF0A.5080900@selasky.org> Date: Wed, 05 Nov 2014 08:17:30 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Steven Hartland , "freebsd-usb@freebsd.org" Subject: Re: ehci breaking Supermicro IPMI keyboard on uhci? References: <5458184E.5020801@multiplay.co.uk> <54587E9B.50709@selasky.org> <54590195.7090600@multiplay.co.uk> <545902B4.8030001@selasky.org> <54591009.5020401@multiplay.co.uk> <54593576.9050100@multiplay.co.uk> <54594C20.6090006@selasky.org> <5459609B.10502@multiplay.co.uk> In-Reply-To: <5459609B.10502@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2014 07:17:21 -0000 On 11/05/14 00:26, Steven Hartland wrote: > > On 04/11/2014 21:58, Hans Petter Selasky wrote: >> On 11/04/14 21:22, Steven Hartland wrote: >>> >>> On 04/11/2014 17:42, Steven Hartland wrote: >>>> >>>> On 04/11/2014 16:45, Hans Petter Selasky wrote: >>>>> On 11/04/14 17:40, Steven Hartland wrote: >>>>>> On 04/11/2014 07:22, Hans Petter Selasky wrote: >>>>>>> On 11/04/14 01:05, Steven Hartland wrote: >>>>>>>> Had the problem where the Supermicro IPMI keyboard wouldn't work >>>>>>>> on some >>>>>>>> machines for a while, tonight I finally had time to play with >>>>>>>> all the >>>>>>>> options to see if anything would make it work. >>>>>>>> >>>>>>>> Turns out adding the following to loader.conf does fixes the issue: >>>>>>>> hint.ehci.0.disabled="1" >>>>>>>> >>>>>>>> So the question is why would this help? >>>>>>>> >>>>>>>> Surely disabling one controller shouldn't make devices attached to >>>>>>>> another work? >>>>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> The USB device is failing to enumerate. Are you sure there is no >>>>>>> XHCI >>>>>>> controller on this device? >>>>>> I did try removing xhci from my kernel config, but that had no >>>>>> effect, >>>>>> only when I disabled the ehci controller did it correctly >>>>>> enumerate the >>>>>> devices attached to the uhci controller. >>>>>> >>>>>> Attached is the outuput from pciconf -l -v in case that helps. If >>>>>> there's anything else I can provide which will help just let me know. >>>>>> >>>>>> For reference I'm currently testing 10.1-RC4 on this box. >>>>>> >>>>>> Regards >>>>>> Steve >>>>> >>>>> Maybe you can check the PCI IDs with Linux EHCI driver, if your >>>>> hardware requires some special quirks? >>>> I cant find any mention of quirks for the Intel USB controller PCI IDs >>>> but I might be looking in the wrong place, do you have a link to what >>>> I should be searching though? >>>> >>>> I did however find the following which is for the exact device I'm >>>> having issues with and seems to indicate the HW might have an issue >>>> with HighSpeed mode. >>>> >>>> https://lkml.org/lkml/2012/4/19/224 >>>> http://lkml.iu.edu//hypermail/linux/kernel/1204.3/03115.html >>>> >>>> Which makes me wonder if hw.usb.ehci.no_hs=1 would also result in a >>>> working device. >>>> >>> Ok so without the disabled hit but with no_hs=1 the devices still works >>> and usbconfig list shows: >>> ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL >>> (12Mbps) pwr=SAVE (0mA) >>> ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL >>> (12Mbps) pwr=SAVE (0mA) >>> ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH >>> (480Mbps) pwr=SAVE (0mA) >>> ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL >>> (12Mbps) pwr=SAVE (0mA) >>> ugen2.2: at usbus2, cfg=0 md=HOST spd=FULL >>> (12Mbps) pwr=ON (100mA) >>> >>> and messages: >>> Nov 4 19:28:53 test1 kernel: usbus0 on uhci0 >>> Nov 4 19:28:53 test1 kernel: usbus1 on uhci1 >>> Nov 4 19:28:53 test1 kernel: usbus2 on uhci2 >>> Nov 4 19:28:53 test1 kernel: usbus3: EHCI version 1.0 >>> Nov 4 19:28:53 test1 kernel: usbus3 on ehci0 >>> Nov 4 19:28:53 test1 kernel: usbus0: 12Mbps Full Speed USB v1.0 >>> Nov 4 19:28:53 test1 kernel: usbus1: 12Mbps Full Speed USB v1.0 >>> Nov 4 19:28:53 test1 kernel: usbus2: 12Mbps Full Speed USB v1.0 >>> Nov 4 19:28:53 test1 kernel: usbus3: 480Mbps High Speed USB v2.0 >>> Nov 4 19:28:53 test1 kernel: ugen1.1: at usbus1 >>> Nov 4 19:28:53 test1 kernel: uhub0: >> rev 1.00/1.00, addr 1> on usbus1 >>> Nov 4 19:28:53 test1 kernel: ugen0.1: at usbus0 >>> Nov 4 19:28:53 test1 kernel: uhub1: >> rev 1.00/1.00, addr 1> on usbus0 >>> Nov 4 19:28:53 test1 kernel: ugen3.1: at usbus3 >>> Nov 4 19:28:53 test1 kernel: uhub2: >> rev 2.00/1.00, addr 1> on usbus3 >>> Nov 4 19:28:53 test1 kernel: ugen2.1: at usbus2 >>> Nov 4 19:28:53 test1 kernel: uhub3: >> rev 1.00/1.00, addr 1> on usbus2 >>> Nov 4 19:28:53 test1 kernel: Root mount waiting for: usbus3 >>> Nov 4 19:28:53 test1 kernel: Root mount waiting for: usbus3 >>> Nov 4 19:28:53 test1 kernel: Root mount waiting for: usbus3 >>> Nov 4 19:28:53 test1 kernel: ugen2.2: at usbus2 >>> Nov 4 19:28:53 test1 kernel: ukbd0: >> 0/0, rev 2.00/0.01, addr 2> on usbus2 >>> >>> So now I'm even more confused :( >>> >> >> Maybe we could set the no-hs as a fallback from the EHCI controller to >> the UHC/OHCI ones ... >> >> Looks like a HW issue. BTW: are there any high speed devices connected >> to this board? >> > The only connected devices are the onboard IPMI which provides the > keyboard and mouse + virtual media. > > From what I can see its meant to be USB 2.0 compilient but there's a > lot of reports of issues with them, so I wouldn't rule out a > implementation issue. > > The following seems related: > http://www.supermicro.com/support/faqs/faq.cfm?faq=11530 > > I've asked Supermicro for an updated firmware, we're already running the > latest they have on their site (1.64) > > Falling back to full speed if high speed fails to negotiate seems like a > good plan though. Do you think that's going to be easy to do? Count me > in as tester if that will help :) Hi, It's just a matter of switching a bit in the port status register of the EHCI controller. --HPS From owner-freebsd-usb@FreeBSD.ORG Thu Nov 6 22:09:38 2014 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E7C44F45 for ; Thu, 6 Nov 2014 22:09:38 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 CF880188 for ; Thu, 6 Nov 2014 22:09:38 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sA6M9cCE056944 for ; Thu, 6 Nov 2014 22:09:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 194752] libusb-0.1.pc should be libusb.pc for compatibility Date: Thu, 06 Nov 2014 22:09:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: tijl@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2014 22:09:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194752 Tijl Coosemans changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-usb@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@FreeBSD.ORG Fri Nov 7 12:25:19 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CF398C10 for ; Fri, 7 Nov 2014 12:25:19 +0000 (UTC) Received: from mail-qg0-x236.google.com (mail-qg0-x236.google.com [IPv6:2607:f8b0:400d:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 899DEB57 for ; Fri, 7 Nov 2014 12:25:19 +0000 (UTC) Received: by mail-qg0-f54.google.com with SMTP id q108so2220519qgd.41 for ; Fri, 07 Nov 2014 04:25:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=S0+uJCXE8QLrCrxfTRHgM+FUBTAz/0mzKhJ9gdRvteA=; b=pLVWNgc2Cxhx5icg+Ry+64tbNeGQieps3Pe/jRzt4WC3ThNr48EtU9TJGPrIYauAZR JT1MgWDBm6HR3/+toOycuFGFgVR7yGe7JRlM/K3HTPfxUC3m5bq/jbN3Yd5+jQxF3KiS V4185RrbxrSKNIoMx02C29FjzzNk/gNiTEP4WunHRsM/BMBAM5M2AQdTDdSPEcfDu0T0 fzN1VW0IHHuDrdLJbIQ4GeyF1otfx/IJSyaoSrw3oLR81TDVXVnZtkEDZvpt8rXsjFgd XHUTPmjiFoG2h7BMoFWt/yjokEdFLE2I/LViLfJGiJdCPrUT/NbtoMuLApn3oQtXdnK6 3Apg== MIME-Version: 1.0 X-Received: by 10.224.4.197 with SMTP id 5mr17038113qas.74.1415363118653; Fri, 07 Nov 2014 04:25:18 -0800 (PST) Received: by 10.96.169.229 with HTTP; Fri, 7 Nov 2014 04:25:18 -0800 (PST) Date: Fri, 7 Nov 2014 13:25:18 +0100 Message-ID: Subject: g_vfs_done() error=5 USB disk on raspberrypi. Decrease the speed of USB From: Aurelien Martin <01aurelien@gmail.com> To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 12:25:20 -0000 Dear all, My raspberry-pi is crashing in g_vfs_done error 5 () when I'm trying to copy data from the rpi (with dd) to my USB drive on UFS2 I can notice a high %system load ~100% on the rpi before the crash Apparently people succeed to "fix it" by decreasing the speed of the USB bus with sysctl hw.usb.ehci.no_hs = 1 But in my case I cannot set this sysctl. And I didn't succeed to fix it with camcontrol Can you guide me on my investigation to decrease the speed of USB ? Thanks for your work. Cheers,Aurelien Log -- # uname -a FreeBSD rpi-aurelien 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r271779: Fri Sep 19 01:18:53 UTC 2014 root@grind.freebsd.org:/usr/obj/arm.armv6/usr/src/sys/RPI-B arm # sysctl hw.usb.ehci sysctl: unknown oid 'hw.usb.ehci': No such file or directory # usbconfig -d ugen0.5 show_ifdrv ugen0.5: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) ugen0.5.0: umass0: # camcontrol devlist at scbus0 target 0 lun 0 (da0) # kldstat -v | grep ehci 47 ehci/usbus From owner-freebsd-usb@FreeBSD.ORG Fri Nov 7 13:03:32 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D55C88AA for ; Fri, 7 Nov 2014 13:03:32 +0000 (UTC) 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 94481FBA for ; Fri, 7 Nov 2014 13:03:32 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (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 DD0C41FE022; Fri, 7 Nov 2014 14:03:23 +0100 (CET) Message-ID: <545CC328.4070006@selasky.org> Date: Fri, 07 Nov 2014 14:03:36 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Aurelien Martin <01aurelien@gmail.com>, freebsd-usb@freebsd.org Subject: Re: g_vfs_done() error=5 USB disk on raspberrypi. Decrease the speed of USB References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 13:03:32 -0000 On 11/07/14 13:25, Aurelien Martin wrote: > Dear all, > > My raspberry-pi is crashing in g_vfs_done error 5 () when I'm trying to > copy data from the rpi (with dd) to my USB drive on UFS2 > I can notice a high %system load ~100% on the rpi before the crash > > Apparently people succeed to "fix it" by decreasing the speed of the USB > bus with sysctl hw.usb.ehci.no_hs = 1 > > But in my case I cannot set this sysctl. And I didn't succeed to fix it > with camcontrol > > Can you guide me on my investigation to decrease the speed of USB ? > Hi, If you connect your USB device through an external full speed USB HUB, it will go full speed. It is possible to make all RPI-B devices enumerate at full speed too, but then you will have decreased network performance. Is you external USB device known to be buggy? --HPS From owner-freebsd-usb@FreeBSD.ORG Fri Nov 7 13:05:23 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8EE2C9B9 for ; Fri, 7 Nov 2014 13:05:23 +0000 (UTC) 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 4D5E0FE0 for ; Fri, 7 Nov 2014 13:05:22 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (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 C7E311FE022; Fri, 7 Nov 2014 14:05:20 +0100 (CET) Message-ID: <545CC39E.4020504@selasky.org> Date: Fri, 07 Nov 2014 14:05:34 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Aurelien Martin <01aurelien@gmail.com>, freebsd-usb@freebsd.org Subject: Re: g_vfs_done() error=5 USB disk on raspberrypi. Decrease the speed of USB References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 13:05:23 -0000 Hi, If you set: hw.usb.umass.throttle=xxx Then it might have the same effect! Needs "options USB_DEBUG" in the kernel configuration file. SYSCTL_INT(_hw_usb_umass, OID_AUTO, throttle, CTLFLAG_RWTUN, &umass_throttle, 0, "Forced delay between commands in milliseconds"); --HPS From owner-freebsd-usb@FreeBSD.ORG Fri Nov 7 18:50:48 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5181FE24 for ; Fri, 7 Nov 2014 18:50:48 +0000 (UTC) Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 09874CE6 for ; Fri, 7 Nov 2014 18:50:48 +0000 (UTC) Received: by mail-qc0-f174.google.com with SMTP id r5so2975402qcx.33 for ; Fri, 07 Nov 2014 10:50:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ble2kmUz5TFiUZRJU5tZ6xgiQNvAbbcwmWAbcpi2CgA=; b=rG4T9SxJxAX7Ayj+5x2D9bRJnXMqkaO/osfnZBu/Pr9ze2QDbnB5a9sbxrSdh7TB/T mlU1+W7u37eB+mqv+lpT0lqj2G7nNunLSK+DQyrK5GJxGmQEoUQghottbXNVx8JOBcuZ e0eucMOOGz7ZqEpUVxI6EA0uqlP63Ji6LFtUWXMqnOR2OWCYLiPpcYCifoddTkZua/HA vuU1f34zQmn98Nc5ymvNY+EvTeCsU4dtqcdh2jvGhkmjIaqjLvrCAMp122g7rC7kVYkM LwEiOJC/jOJ8bPbKES23BLqLKmSaZEeN8VA+NXFUKCzW4xd8I93CkOfNIfBi1UqTlXVx y3Yg== MIME-Version: 1.0 X-Received: by 10.140.107.37 with SMTP id g34mr18995449qgf.38.1415386247179; Fri, 07 Nov 2014 10:50:47 -0800 (PST) Received: by 10.96.169.229 with HTTP; Fri, 7 Nov 2014 10:50:47 -0800 (PST) In-Reply-To: <545CC39E.4020504@selasky.org> References: <545CC39E.4020504@selasky.org> Date: Fri, 7 Nov 2014 19:50:47 +0100 Message-ID: Subject: Re: g_vfs_done() error=5 USB disk on raspberrypi. Decrease the speed of USB From: Aurelien Martin <01aurelien@gmail.com> To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-usb@freebsd.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 18:50:48 -0000 Hello, The drive is healthy (SMART OK) I played with hw.usb.umass.throttle, with value 10 and 100. It slow down the USB transfert and decresase the %system load ~10%. But I kept the normal value (0), the system succeed to dd 10GB to the USB drive without crashing If it reoccur I'll rebuild a kernel with USB_DEBUG, and this thread will be updated. Thanks for your support Hans. Cheers,Aurelien 2014-11-07 14:05 GMT+01:00 Hans Petter Selasky : > Hi, > > If you set: > > hw.usb.umass.throttle=xxx > > Then it might have the same effect! > > Needs "options USB_DEBUG" in the kernel configuration file. > > SYSCTL_INT(_hw_usb_umass, OID_AUTO, throttle, CTLFLAG_RWTUN, > &umass_throttle, 0, "Forced delay between commands in milliseconds"); > > --HPS > From owner-freebsd-usb@FreeBSD.ORG Sat Nov 8 17:50:12 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A4843953 for ; Sat, 8 Nov 2014 17:50:12 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 362F495E for ; Sat, 8 Nov 2014 17:50:12 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id n3so6872423wiv.2 for ; Sat, 08 Nov 2014 09:50:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=ttcwGiqagbFCkDr0HSyS4eYXehEt94kGccJfmx6KXNE=; b=nOKeZiwYno+R7i95tSk3tWFZAfhglnwmTSXNudl5i7dDzYmpKaDlEDMOeJxsibuevB aabAPdAuXl0WVzDPXmoEY+/9g4i74aUtZs9Klo3pTZ/G1ljBer7hUXKX2WWuVHN38Zfl CyV9paCLI8ZgRKBDOWsJrMrCv6S9T0/h2dleU9zoEiZCWCKH9VU3TakR48M1C3hBuSmd yfO1f2A/VS9av+7pThdVtD68oyw2CpVwXP1B3CKeU+i3tgvYPk1w1bGgQLoOXHTEKvWZ AahieBIwRr/iPbFm4aQmnpDbpBCs0NlZZVu9y2zJD0Tv2OFugvL2YFDqasVCTd3km50R e87A== MIME-Version: 1.0 X-Received: by 10.194.85.83 with SMTP id f19mr4311257wjz.20.1415469010715; Sat, 08 Nov 2014 09:50:10 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.136 with HTTP; Sat, 8 Nov 2014 09:50:10 -0800 (PST) Date: Sat, 8 Nov 2014 09:50:10 -0800 X-Google-Sender-Auth: Pju8cQ34CDLePOJ91Y7Je8gtsPc Message-ID: Subject: request: including uhidd in base From: Adrian Chadd To: "freebsd-usb@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Nov 2014 17:50:12 -0000 hi! The surface pro device keyboard/touchpad combos have a multi-HID device, which we don't support without uhidd installed. So, would anyone mind if it was just added in as a base daemon? Without it it's impossible to install FreeBSD on the Surface Pro / Pro 2. (I haven't tried the Pro 3, but I'm waiting for Haswell DRI support to show up first.) Thanks, -adrian From owner-freebsd-usb@FreeBSD.ORG Sat Nov 8 22:45:39 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 95225816; Sat, 8 Nov 2014 22:45:39 +0000 (UTC) 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 5529D822; Sat, 8 Nov 2014 22:45:38 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (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 3DF5B1FE022; Sat, 8 Nov 2014 23:45:30 +0100 (CET) Message-ID: <545E9D19.5070806@selasky.org> Date: Sat, 08 Nov 2014 23:45:45 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Adrian Chadd , "freebsd-usb@freebsd.org" Subject: Re: request: including uhidd in base References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Nov 2014 22:45:39 -0000 On 11/08/14 18:50, Adrian Chadd wrote: > hi! > > The surface pro device keyboard/touchpad combos have a multi-HID > device, which we don't support without uhidd installed. > > So, would anyone mind if it was just added in as a base daemon? > > Without it it's impossible to install FreeBSD on the Surface Pro / Pro > 2. (I haven't tried the Pro 3, but I'm waiting for Haswell DRI support > to show up first.) > > Thanks, > Hi, UHIDD might need a bit more testing, so that you don't remove keyboard or mouse functionality from existing users. Is UHIDD up to date with the kernel mouse and keyboard drivers? --HPS