From owner-freebsd-hardware@freebsd.org Tue Feb 13 13:48:30 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57078F014C2; Tue, 13 Feb 2018 13:48:30 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::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 ECA967946E; Tue, 13 Feb 2018 13:48:29 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (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 97A6C260329; Tue, 13 Feb 2018 14:48:28 +0100 (CET) Subject: Re: Dell R630 unable to detect USB, can't boot To: Lee Brown , freebsd-usb@freebsd.org, freebsd-hardware@freebsd.org References: From: Hans Petter Selasky Message-ID: <2dd2f1e1-dd3f-5e38-5873-81394633799b@selasky.org> Date: Tue, 13 Feb 2018 14:45:33 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 13:48:30 -0000 On 02/04/18 23:47, Lee Brown wrote: > Booting FreeBSD11.1-RELENG from a USB stick, loader works fine keyboard > allows selection, kernel loads and starts OK, gets as far as detecting USB > devices and stops there. imgur for a > screenshot. Tried safe mode same occurrence. > > CDROM is via a USB, so that's a no go and I've not had luck booting UEFI > iSCSI nor PXE yet, so I'm stuck without a keyboard (no PS/2 connectors) or > essentially any boot media. > > For reference Xen 7.2 is running fine so at first blush it's not faulty > hardware. > USB3 mode on and off (ie force USB2) in the BIOS makes no difference. > All Firmwares current. > > Any suggestions on how to move forward with this? I tried turning on > verbose mode, but I'm not sure how to capture that nor where to look. > Hi, USB_ERR_TIMEOUT might be an indication of a PCI IRQ issue. --HPS From owner-freebsd-hardware@freebsd.org Tue Feb 13 14:03:48 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B6C1F029FB; Tue, 13 Feb 2018 14:03:48 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 D18807A0B3; Tue, 13 Feb 2018 14:03:47 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (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 69F75260329; Tue, 13 Feb 2018 15:03:46 +0100 (CET) Subject: Re: Dell R630 unable to detect USB, can't boot From: Hans Petter Selasky To: Lee Brown , freebsd-usb@freebsd.org, freebsd-hardware@freebsd.org References: <2dd2f1e1-dd3f-5e38-5873-81394633799b@selasky.org> Message-ID: <62462b68-2fb9-4e8a-c473-9c1ea9096f09@selasky.org> Date: Tue, 13 Feb 2018 15:00:51 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <2dd2f1e1-dd3f-5e38-5873-81394633799b@selasky.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 14:03:48 -0000 On 02/13/18 14:45, Hans Petter Selasky wrote: > On 02/04/18 23:47, Lee Brown wrote: >> Booting FreeBSD11.1-RELENG from a USB stick, loader works fine keyboard >> allows selection, kernel loads and starts OK, gets as far as detecting >> USB >> devices and stops there.  imgur for a >> screenshot.  Tried safe mode same occurrence. >> >> CDROM is via a USB, so that's a no go and I've not had luck booting UEFI >> iSCSI nor PXE yet, so I'm stuck without a keyboard (no PS/2 >> connectors) or >> essentially any boot media. >> >> For reference Xen 7.2 is running fine so at first blush it's not faulty >> hardware. >> USB3 mode on and off (ie force USB2) in the BIOS makes no difference. >> All Firmwares current. >> >> Any suggestions on how to move forward with this?  I tried turning on >> verbose mode, but I'm not sure how to capture that nor where to look. >> > > Hi, > > USB_ERR_TIMEOUT might be an indication of a PCI IRQ issue. > Try to set: hw.usb.xhci.use_polling=1 from the loader as a temporary quirk. Then try to dump information about IRQ's like "vmstat -i" "dmesg" and so on. --HPS From owner-freebsd-hardware@freebsd.org Tue Feb 13 18:52:48 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F065DF1A2EE for ; Tue, 13 Feb 2018 18:52:47 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8CD056A23A for ; Tue, 13 Feb 2018 18:52:47 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-it0-x233.google.com with SMTP id 140so4004449iti.0 for ; Tue, 13 Feb 2018 10:52:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=XLbLLQmAOlv135Jf5PxaozX+0YVf0RI8oMjbWTQR4Ww=; b=Y+UmBLNcvfzrgnxKer2yhAwIWVbPwCM6HeJg6nELMKlFdCy6oN7JMRbuIEr6j6WE2b V4eEVdJWPxT8VB8NBj9Ifc63qKqsT0zVdWZkHaOC6pF7kLzjnF1xdSapMYV0/DOsezdx CC4+99MX5UODZWMLyz5L706okTOx409CzwMz7BF+Y4L32A48M+Tm1WlhK8/gwuGXdwwd RFU7HY0mlpVyGp4BKGinOC8mh9ALGUMRCuAKygof8FxP3JxHk4gnocuDuCZVOvdk+gCi IBOwLgFiHErSZ8yiB34p+XikhYsqBuJdzs74ZujkSvHsQA6AfPypbWO5/3rfcpv1mupG E54w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=XLbLLQmAOlv135Jf5PxaozX+0YVf0RI8oMjbWTQR4Ww=; b=JBRsMELuSlxwBVqRjN9sWdg4v97hD3+HYDivNdpiVW6ykTgqu3H8477AFR/wR8MZT9 FLMqx4A0BSW0L980nOHKeFE9qbvqYVbN2A3gBvw/hzErHKezPHLzX4lsvSf6Tmfxs2z+ xAQx9H4b8XIQtvgtCAhpilGTg0YGvUNDq2x00AdiscBpqqTN5+9s++V9Cjh5iv+GBdYH LjAFgJRJFzapE2Mhb87gU1uPPP395Gn8v8ulx0TWGnSCJ0tRM/U9s9ZBZQmGRbnidWKQ z7BSMmPBvMuaGgy7iu6KNOSK0j4pVT5Um3oO0TUpwrIILyZXJA8Sw1AyNQ+Pf+FfOJKi KTxw== X-Gm-Message-State: APf1xPAHs0xYkmDpJggNjhNON27j8lpNc7bFdz4gaqqmO2TgOBpUar8g ihhrJGzA+lmIiX3Cyx/XOQauaAJEvYcW+AD8dlxQg8sA X-Google-Smtp-Source: AH8x226931OGImlk2Zw/PQSFNoS7BKVgTA+PHPYw40SfHCFRSTcIy4zHHW1LH0YxjoEvCqqTJUg9/pb1Wu0rIIkTwYw= X-Received: by 10.36.103.148 with SMTP id u142mr2838289itc.83.1518547966790; Tue, 13 Feb 2018 10:52:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.225.66 with HTTP; Tue, 13 Feb 2018 10:52:46 -0800 (PST) In-Reply-To: <62462b68-2fb9-4e8a-c473-9c1ea9096f09@selasky.org> References: <2dd2f1e1-dd3f-5e38-5873-81394633799b@selasky.org> <62462b68-2fb9-4e8a-c473-9c1ea9096f09@selasky.org> From: Lee Brown Date: Tue, 13 Feb 2018 10:52:46 -0800 Message-ID: Subject: Re: Dell R630 unable to detect USB, can't boot To: freebsd-usb@freebsd.org, freebsd-hardware@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 18:52:48 -0000 On Tue, Feb 13, 2018 at 6:00 AM, Hans Petter Selasky wrote: > On 02/13/18 14:45, Hans Petter Selasky wrote: > >> On 02/04/18 23:47, Lee Brown wrote: >> >>> Booting FreeBSD11.1-RELENG from a USB stick, loader works fine keyboard >>> allows selection, kernel loads and starts OK, gets as far as detecting >>> USB >>> devices and stops there. imgur for a >>> screenshot. Tried safe mode same occurrence. >>> >>> CDROM is via a USB, so that's a no go and I've not had luck booting UEFI >>> iSCSI nor PXE yet, so I'm stuck without a keyboard (no PS/2 connectors) >>> or >>> essentially any boot media. >>> >>> For reference Xen 7.2 is running fine so at first blush it's not faulty >>> hardware. >>> USB3 mode on and off (ie force USB2) in the BIOS makes no difference. >>> All Firmwares current. >>> >>> Any suggestions on how to move forward with this? I tried turning on >>> verbose mode, but I'm not sure how to capture that nor where to look. >>> >>> >> Hi, >> >> USB_ERR_TIMEOUT might be an indication of a PCI IRQ issue. >> >> > Try to set: > > hw.usb.xhci.use_polling=1 > > from the loader as a temporary quirk. Then try to dump information about > IRQ's like "vmstat -i" "dmesg" and so on. > > --HPS > > Thanks Hans, but unfortunately that made no difference. Here's my full loader.conf vfs.mountroot.timeout="10" boot_multicons="YES" boot_serial="YES" comconsole_speed="115200" console="comconsole,efi" kern.cam.boot_delay="10000" hw.usb.xhci.use_polling=1 From owner-freebsd-hardware@freebsd.org Tue Feb 13 20:59:12 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BA4D7F23D56; Tue, 13 Feb 2018 20:59:12 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::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 5A68D71050; Tue, 13 Feb 2018 20:59:12 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (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 24C04260809; Tue, 13 Feb 2018 21:59:11 +0100 (CET) Subject: Re: Dell R630 unable to detect USB, can't boot To: Lee Brown , freebsd-usb@freebsd.org, freebsd-hardware@freebsd.org References: <2dd2f1e1-dd3f-5e38-5873-81394633799b@selasky.org> <62462b68-2fb9-4e8a-c473-9c1ea9096f09@selasky.org> From: Hans Petter Selasky Message-ID: <78c5b059-ac39-8946-81f5-3e6ec75d6c39@selasky.org> Date: Tue, 13 Feb 2018 21:56:15 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 20:59:12 -0000 On 02/13/18 19:52, Lee Brown wrote: > On Tue, Feb 13, 2018 at 6:00 AM, Hans Petter Selasky > wrote: > >> On 02/13/18 14:45, Hans Petter Selasky wrote: >> >>> On 02/04/18 23:47, Lee Brown wrote: >>> >>>> Booting FreeBSD11.1-RELENG from a USB stick, loader works fine keyboard >>>> allows selection, kernel loads and starts OK, gets as far as detecting >>>> USB >>>> devices and stops there. imgur for a >>>> screenshot. Tried safe mode same occurrence. >>>> >>>> CDROM is via a USB, so that's a no go and I've not had luck booting UEFI >>>> iSCSI nor PXE yet, so I'm stuck without a keyboard (no PS/2 connectors) >>>> or >>>> essentially any boot media. >>>> >>>> For reference Xen 7.2 is running fine so at first blush it's not faulty >>>> hardware. >>>> USB3 mode on and off (ie force USB2) in the BIOS makes no difference. >>>> All Firmwares current. >>>> >>>> Any suggestions on how to move forward with this? I tried turning on >>>> verbose mode, but I'm not sure how to capture that nor where to look. >>>> >>>> >>> Hi, >>> >>> USB_ERR_TIMEOUT might be an indication of a PCI IRQ issue. >>> >>> >> Try to set: >> >> hw.usb.xhci.use_polling=1 >> >> from the loader as a temporary quirk. Then try to dump information about >> IRQ's like "vmstat -i" "dmesg" and so on. >> >> --HPS >> >> Thanks Hans, but unfortunately that made no difference. Here's my full > loader.conf > > vfs.mountroot.timeout="10" > boot_multicons="YES" > boot_serial="YES" > comconsole_speed="115200" > console="comconsole,efi" > kern.cam.boot_delay="10000" > hw.usb.xhci.use_polling=1 Did you enable USB 3.0 in the BIOS when trying this? --HPS From owner-freebsd-hardware@freebsd.org Tue Feb 13 22:00:54 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06DAFF04BE2 for ; Tue, 13 Feb 2018 22:00:54 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8CF4F745C9 for ; Tue, 13 Feb 2018 22:00:53 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-it0-x231.google.com with SMTP id p204so372197itc.4 for ; Tue, 13 Feb 2018 14:00:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=gtPUF9cRnXxz7YYkkfQMOXHhWoTrr65Dn1WF5yyCgkY=; b=W5G/VZfiClfgV4GvjYwbHWPuSS1BjSUHpmwWH1GbrarfIqhkIkiYMyVOp/twv6Ma5/ jJ0ILxdfYgU+o3QDyCrJRZwYffa5nM+q93+WXvIOozmrbIRVCd7WVJx3b9O8UtwE8FnJ ZosW+af8/N4XrTpTYBjaSgIaB0BvSyxM6XsXvcCk0KntjW6wwLjUm5GXnRlc8nAiIaoD D0fhSEVW3sfzpC8DYn4cdcg0qkNq4EVKNrcQvCCGP4cHRsfXcvDX5NoBWdyd6iIK+Cbd +aPgGoDkZCI7p54Z2bVrjVpDeDbUQFJs4lla56SvfEeU5FMHy43xri7nq4JjQXOLErPm /8UQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=gtPUF9cRnXxz7YYkkfQMOXHhWoTrr65Dn1WF5yyCgkY=; b=HRmGy+MHMqhPcoMt7Uw/S2dTRFq9AzLbKSPDjy8PwtkjSptmCg+3qZd1QRmZw0MTi+ 4wHk2QFe/feAGkFioEuNuCuoJLxmdqIXPN5Z6nJEkynrOQl41kCM24YsAvDSNfP0Rcuy 4TX3mEjX+TV2fsFMQ7AfJso3a13gdCOFa0PZDXd8ie0fAcQHWz7Xq2jjBc1F6Q8KfUr3 MTLbf+4myJNpFTEGfO0fzrVH17IFNEZ68oH2a39D397XvFPY5+5JzrikHmu+JPbEPIFH wvLxCkhhvDYyLEuI46l5SV9r+uP+U7pdJOutZeSlP6bVQBVzRaYRmzGM9z6ThH8LeOO0 qzMA== X-Gm-Message-State: APf1xPC9Bf9JlS0uMGjVkt/sV6hXdam1qvDS5Zg7WtSDQMGZ/4CAXUsa oZykvC7q3k1m70S7b9VuMBBjwAYP3Kf1h+A2YoJOMQ== X-Google-Smtp-Source: AH8x225s5QM+BhCTQ938pVK22VLos85u0fbVQR72rhG8ofMzYYmY4iRN6AzAtOaCxUlDgi+EFVKzN7rFJIzEk8LWtcA= X-Received: by 10.36.79.149 with SMTP id c143mr3591610itb.63.1518559252920; Tue, 13 Feb 2018 14:00:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.225.66 with HTTP; Tue, 13 Feb 2018 14:00:52 -0800 (PST) In-Reply-To: <78c5b059-ac39-8946-81f5-3e6ec75d6c39@selasky.org> References: <2dd2f1e1-dd3f-5e38-5873-81394633799b@selasky.org> <62462b68-2fb9-4e8a-c473-9c1ea9096f09@selasky.org> <78c5b059-ac39-8946-81f5-3e6ec75d6c39@selasky.org> From: Lee Brown Date: Tue, 13 Feb 2018 14:00:52 -0800 Message-ID: Subject: Re: Dell R630 unable to detect USB, can't boot To: freebsd-usb@freebsd.org, freebsd-hardware@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 22:00:54 -0000 On Tue, Feb 13, 2018 at 12:56 PM, Hans Petter Selasky wrote: > On 02/13/18 19:52, Lee Brown wrote: > >> On Tue, Feb 13, 2018 at 6:00 AM, Hans Petter Selasky >> wrote: >> >> On 02/13/18 14:45, Hans Petter Selasky wrote: >>> >>> On 02/04/18 23:47, Lee Brown wrote: >>>> >>>> Booting FreeBSD11.1-RELENG from a USB stick, loader works fine keyboard >>>>> allows selection, kernel loads and starts OK, gets as far as detecting >>>>> USB >>>>> devices and stops there. imgur for a >>>>> screenshot. Tried safe mode same occurrence. >>>>> >>>>> CDROM is via a USB, so that's a no go and I've not had luck booting >>>>> UEFI >>>>> iSCSI nor PXE yet, so I'm stuck without a keyboard (no PS/2 connectors) >>>>> or >>>>> essentially any boot media. >>>>> >>>>> For reference Xen 7.2 is running fine so at first blush it's not faulty >>>>> hardware. >>>>> USB3 mode on and off (ie force USB2) in the BIOS makes no difference. >>>>> All Firmwares current. >>>>> >>>>> Any suggestions on how to move forward with this? I tried turning on >>>>> verbose mode, but I'm not sure how to capture that nor where to look. >>>>> >>>>> >>>>> Hi, >>>> >>>> USB_ERR_TIMEOUT might be an indication of a PCI IRQ issue. >>>> >>>> >>>> Try to set: >>> >>> hw.usb.xhci.use_polling=1 >>> >>> from the loader as a temporary quirk. Then try to dump information about >>> IRQ's like "vmstat -i" "dmesg" and so on. >>> >>> --HPS >>> >>> Thanks Hans, but unfortunately that made no difference. Here's my full >>> >> loader.conf >> >> vfs.mountroot.timeout="10" >> boot_multicons="YES" >> boot_serial="YES" >> comconsole_speed="115200" >> console="comconsole,efi" >> kern.cam.boot_delay="10000" >> hw.usb.xhci.use_polling=1 >> > > Did you enable USB 3.0 in the BIOS when trying this? > > --HPS > > It was configured with USB3.0 OFF I just toggled it ON, same result. I verified the sysctl polling value from the loader before booting From owner-freebsd-hardware@freebsd.org Wed Feb 14 12:36:04 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0647DF1EADB; Wed, 14 Feb 2018 12:36:04 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 9643474F60; Wed, 14 Feb 2018 12:36:03 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (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 6ACEB26009E; Wed, 14 Feb 2018 13:35:56 +0100 (CET) Subject: Re: Dell R630 unable to detect USB, can't boot To: Lee Brown , freebsd-usb@freebsd.org, freebsd-hardware@freebsd.org References: <2dd2f1e1-dd3f-5e38-5873-81394633799b@selasky.org> <62462b68-2fb9-4e8a-c473-9c1ea9096f09@selasky.org> <78c5b059-ac39-8946-81f5-3e6ec75d6c39@selasky.org> From: Hans Petter Selasky Message-ID: <29e9db2f-800d-acbc-1aec-7b2170a571de@selasky.org> Date: Wed, 14 Feb 2018 13:33:00 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2018 12:36:04 -0000 On 02/13/18 23:00, Lee Brown wrote: > On Tue, Feb 13, 2018 at 12:56 PM, Hans Petter Selasky > wrote: > >> On 02/13/18 19:52, Lee Brown wrote: >> >>> On Tue, Feb 13, 2018 at 6:00 AM, Hans Petter Selasky >>> wrote: >>> >>> On 02/13/18 14:45, Hans Petter Selasky wrote: >>>> >>>> On 02/04/18 23:47, Lee Brown wrote: >>>>> >>>>> Booting FreeBSD11.1-RELENG from a USB stick, loader works fine keyboard >>>>>> allows selection, kernel loads and starts OK, gets as far as detecting >>>>>> USB >>>>>> devices and stops there. imgur for a >>>>>> screenshot. Tried safe mode same occurrence. >>>>>> >>>>>> CDROM is via a USB, so that's a no go and I've not had luck booting >>>>>> UEFI >>>>>> iSCSI nor PXE yet, so I'm stuck without a keyboard (no PS/2 connectors) >>>>>> or >>>>>> essentially any boot media. >>>>>> >>>>>> For reference Xen 7.2 is running fine so at first blush it's not faulty >>>>>> hardware. >>>>>> USB3 mode on and off (ie force USB2) in the BIOS makes no difference. >>>>>> All Firmwares current. >>>>>> >>>>>> Any suggestions on how to move forward with this? I tried turning on >>>>>> verbose mode, but I'm not sure how to capture that nor where to look. >>>>>> >>>>>> >>>>>> Hi, >>>>> >>>>> USB_ERR_TIMEOUT might be an indication of a PCI IRQ issue. >>>>> >>>>> >>>>> Try to set: >>>> >>>> hw.usb.xhci.use_polling=1 >>>> >>>> from the loader as a temporary quirk. Then try to dump information about >>>> IRQ's like "vmstat -i" "dmesg" and so on. >>>> >>>> --HPS >>>> >>>> Thanks Hans, but unfortunately that made no difference. Here's my full >>>> >>> loader.conf >>> >>> vfs.mountroot.timeout="10" >>> boot_multicons="YES" >>> boot_serial="YES" >>> comconsole_speed="115200" >>> console="comconsole,efi" >>> kern.cam.boot_delay="10000" >>> hw.usb.xhci.use_polling=1 >>> >> >> Did you enable USB 3.0 in the BIOS when trying this? >> >> --HPS >> >> It was configured with USB3.0 OFF > I just toggled it ON, same result. > > I verified the sysctl polling value from the loader before booting Hi, I suggest you bring this issue up with Dell customer support. Further, maybe Linux XHCI / EHCI has a quirk for Dell R630. Alternativly you can try to debug the XHCI/EHCI debug prints on your own. If you get a timeout it means something is not communicating like expected in the XHCI/EHCI DMA descriptors. --HPS From owner-freebsd-hardware@freebsd.org Thu Feb 15 05:24:44 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0613F225E1 for ; Thu, 15 Feb 2018 05:24:43 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7FA7B8313F for ; Thu, 15 Feb 2018 05:24:43 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-it0-x233.google.com with SMTP id 140so8488012iti.0 for ; Wed, 14 Feb 2018 21:24:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=eWGqh0h5wJUzbB80JzeqQGUSOKrTP6ZDlMekoY30s3Y=; b=lWy1M+9pS/9l5O5rHFkkuJPRd0zsQexuOD9ciC51aJoP5aJcLiQI0ss27BhmhkYHxw 8xZGZzjxgb9FZZvTwA3iw1qKBiFKO57qquOw4N2WcnBSM+8iv2WXNMY0+EY2GiI15Lmz cdmZf0IDnd/ZI0vM0gGgztDlIBoB0Gy0pdGqjEyBnv2n8Arqf8IKQSlOQhKw6RqnxRw9 pNsk2mL3m/3ZqAweKTeNIHHolZxLIKEZFdEH+j+dvFgE0MNhXNCT22sekxBzW9yOyotT ZESfuKmBALL7fYvqQ2UOK1u0pKmNUqlZoS3T0fENCYdqCrOehBFhTXNVpvSip69zqVlw IPYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=eWGqh0h5wJUzbB80JzeqQGUSOKrTP6ZDlMekoY30s3Y=; b=i3ZIaiJGSqP9aTX7g0+6QYYnm92T6w+KW76rIuWnhsXTMtrgIKiblXs4vW3FvWGe+W VRIrxQsfjCgob49WPwVT4XPrkFZ5OZTAFGpHGrORcmp0tkocLF623B38/wUcxIZyV0FG fX5/wGogxT4Gi9Pa2T+PE9QOqlc0eMgk/agaM3YQEI7Limgh4X8j8kd1RZbFwpOVfyuA rClTmTgmxaIQGLK2/a+6AWVplNVwg3SPjiocyPOzVwBQreF//NwwuqnOdGpcrBiEyrAC SOOuVED9T8Fp7agTabQ/PsXFZ+DbnO1dsTlbfo1ZdHJNbG0Rdw/JqM7aLdiOGNjvIhrr +tpg== X-Gm-Message-State: APf1xPBDYfDUn7LBmRN6pgAzuARd8Ozc1zuLlZH8J0QoveNXnDHTicHG WMuYeG1ez/8/nKG2Pl0FWAxMHmGMGjDVn8wRqXyxtA== X-Google-Smtp-Source: AH8x226APZu43D7UpKiIk8w08JEd3Z2YWWgipGgjh/NK5tH4vs6B4EW5ERFYCLu1smE0Ec4dX9bkMG+vsFvFwDV+ves= X-Received: by 10.36.227.71 with SMTP id d68mr719372ith.57.1518672282446; Wed, 14 Feb 2018 21:24:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.225.66 with HTTP; Wed, 14 Feb 2018 21:24:41 -0800 (PST) In-Reply-To: <29e9db2f-800d-acbc-1aec-7b2170a571de@selasky.org> References: <2dd2f1e1-dd3f-5e38-5873-81394633799b@selasky.org> <62462b68-2fb9-4e8a-c473-9c1ea9096f09@selasky.org> <78c5b059-ac39-8946-81f5-3e6ec75d6c39@selasky.org> <29e9db2f-800d-acbc-1aec-7b2170a571de@selasky.org> From: Lee Brown Date: Wed, 14 Feb 2018 21:24:41 -0800 Message-ID: Subject: Re: Dell R630 unable to detect USB, can't boot To: freebsd-usb@freebsd.org, freebsd-hardware@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2018 05:24:44 -0000 q On Wed, Feb 14, 2018 at 4:33 AM, Hans Petter Selasky wrote: > On 02/13/18 23:00, Lee Brown wrote: > >> On Tue, Feb 13, 2018 at 12:56 PM, Hans Petter Selasky >> wrote: >> >> On 02/13/18 19:52, Lee Brown wrote: >>> >>> On Tue, Feb 13, 2018 at 6:00 AM, Hans Petter Selasky >>>> wrote: >>>> >>>> On 02/13/18 14:45, Hans Petter Selasky wrote: >>>> >>>>> >>>>> On 02/04/18 23:47, Lee Brown wrote: >>>>> >>>>>> >>>>>> Booting FreeBSD11.1-RELENG from a USB stick, loader works fine >>>>>> keyboard >>>>>> >>>>>>> allows selection, kernel loads and starts OK, gets as far as >>>>>>> detecting >>>>>>> USB >>>>>>> devices and stops there. imgur for a >>>>>>> screenshot. Tried safe mode same occurrence. >>>>>>> >>>>>>> CDROM is via a USB, so that's a no go and I've not had luck booting >>>>>>> UEFI >>>>>>> iSCSI nor PXE yet, so I'm stuck without a keyboard (no PS/2 >>>>>>> connectors) >>>>>>> or >>>>>>> essentially any boot media. >>>>>>> >>>>>>> For reference Xen 7.2 is running fine so at first blush it's not >>>>>>> faulty >>>>>>> hardware. >>>>>>> USB3 mode on and off (ie force USB2) in the BIOS makes no difference. >>>>>>> All Firmwares current. >>>>>>> >>>>>>> Any suggestions on how to move forward with this? I tried turning on >>>>>>> verbose mode, but I'm not sure how to capture that nor where to look. >>>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>> >>>>>> USB_ERR_TIMEOUT might be an indication of a PCI IRQ issue. >>>>>> >>>>>> >>>>>> Try to set: >>>>>> >>>>> >>>>> hw.usb.xhci.use_polling=1 >>>>> >>>>> from the loader as a temporary quirk. Then try to dump information >>>>> about >>>>> IRQ's like "vmstat -i" "dmesg" and so on. >>>>> >>>>> --HPS >>>>> >>>>> Thanks Hans, but unfortunately that made no difference. Here's my full >>>>> >>>>> loader.conf >>>> >>>> vfs.mountroot.timeout="10" >>>> boot_multicons="YES" >>>> boot_serial="YES" >>>> comconsole_speed="115200" >>>> console="comconsole,efi" >>>> kern.cam.boot_delay="10000" >>>> hw.usb.xhci.use_polling=1 >>>> >>>> >>> Did you enable USB 3.0 in the BIOS when trying this? >>> >>> --HPS >>> >>> It was configured with USB3.0 OFF >>> >> I just toggled it ON, same result. >> >> I verified the sysctl polling value from the loader before booting >> > > Hi, > > I suggest you bring this issue up with Dell customer support. > > Further, maybe Linux XHCI / EHCI has a quirk for Dell R630. > > Alternativly you can try to debug the XHCI/EHCI debug prints on your own. > If you get a timeout it means something is not communicating like expected > in the XHCI/EHCI DMA descriptors. > > > As I only have the hardware replacement level of support and FreeBSD isn't on their list of certified OS's, I'm probably best spending my time debugging this issue. I do find it curious that the loader is able to work the USB hardware but not the kernel. Once I figure out how to capture the kernel output, I'll crank up the debugging and post back here. From owner-freebsd-hardware@freebsd.org Thu Feb 15 08:13:04 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6D77F063E1; Thu, 15 Feb 2018 08:13:03 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::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 5190E6889E; Thu, 15 Feb 2018 08:13:03 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (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 2A57426009E; Thu, 15 Feb 2018 09:13:01 +0100 (CET) Subject: Re: Dell R630 unable to detect USB, can't boot To: Lee Brown , freebsd-usb@freebsd.org, freebsd-hardware@freebsd.org References: <2dd2f1e1-dd3f-5e38-5873-81394633799b@selasky.org> <62462b68-2fb9-4e8a-c473-9c1ea9096f09@selasky.org> <78c5b059-ac39-8946-81f5-3e6ec75d6c39@selasky.org> <29e9db2f-800d-acbc-1aec-7b2170a571de@selasky.org> From: Hans Petter Selasky Message-ID: <882d40df-6082-bcca-a9ee-944aeca115a8@selasky.org> Date: Thu, 15 Feb 2018 09:10:04 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2018 08:13:04 -0000 On 02/15/18 06:24, Lee Brown wrote: > I do find it curious that the loader is able to work the USB hardware but > not the kernel. The loader is using the BIOS's USB code. Usually there is a handover from BIOS to OS, maybe that's where it's broken. --HPS From owner-freebsd-hardware@freebsd.org Fri Feb 16 16:52:33 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1FC02F24639 for ; Fri, 16 Feb 2018 16:52:33 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A54B68572E for ; Fri, 16 Feb 2018 16:52:32 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-io0-x22d.google.com with SMTP id b34so1894613ioj.6 for ; Fri, 16 Feb 2018 08:52:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=OCt513q9tqSWANa9nKmK55jPD+31G5xc6avNGoQk+Uo=; b=RFa+pKauU43FqsWNXe1c1HsXqY4zZKki0wqufKUGChWoV+G0h3kfxB8lprZ4yCUbKl jNtS1rM3lbIkQWpTaf6UgaScMXz+X/tIHu16MWSbQojvv1vLnHz/9d63hBjjgGAPiKvc /DU+DLTFZYmjKzo1Jcvcilc4tROAaLU8oZ3SGRF+JG3rF4OBXQ97trc97xed0bvCnRHh LWRxv2+M6H+wz4jNClmaHDzExnhqId/YcTixnea7TeE5HId9CviFuTui1u8HKg+9o1Cd epI5SBY2CcvxNH7ulqYa7BdklU+dj9QPekX2aiOUiJWYRycf7VD+wGcyCSoukuYlOt7p UA6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=OCt513q9tqSWANa9nKmK55jPD+31G5xc6avNGoQk+Uo=; b=UvUgV1UyH4D73iXJ2YUU8U+gBZajM0hOZKtTXGJVVp/eSYSSUP1mwpNz+Q+v844TpL D8AswYvv8IDb14ygVduijQ6nMRLQbneh7cqRXP8fB17yOJfHFrXc8xGYFR1UKdnZr4U7 prSTwtmrqxgOGzFzMsMcWHxf2RWW1X+UuPxl+cZ1ck6NXZKcZOMhyQ/Xfggxd7Bd9uDk j4uOD1TDOTdTN5JU7akyqFb+kxwbJLrQosWtDq/Ts9H0H76WDhL4OeQzOrxVVZtrAlrE pBRlOiDjgW5mTxJghI5bG8dQpIkhJloc7UwX6pIL7ckfTDs8D0/TjSbsYpje0PRQLIv+ SELQ== X-Gm-Message-State: APf1xPDCCLoRztSlLgQhdqAGiqCm29OYCueOzQBbFse8EjkFFEdC6Upn svFuIVOedlmkzhh8Ccp0oCwAy+e/p7/vdbcPB2zRnw== X-Google-Smtp-Source: AH8x224cCumU5nFzy7tA/t2SXp0jJ4YCT6NZnn3AIIzx97+WzIuhuP0xG2lzUODS9LwMTvfmfsVL+i5v+m3kZuAPHPo= X-Received: by 10.107.129.8 with SMTP id c8mr8967449iod.218.1518799951584; Fri, 16 Feb 2018 08:52:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.225.66 with HTTP; Fri, 16 Feb 2018 08:52:30 -0800 (PST) In-Reply-To: <882d40df-6082-bcca-a9ee-944aeca115a8@selasky.org> References: <2dd2f1e1-dd3f-5e38-5873-81394633799b@selasky.org> <62462b68-2fb9-4e8a-c473-9c1ea9096f09@selasky.org> <78c5b059-ac39-8946-81f5-3e6ec75d6c39@selasky.org> <29e9db2f-800d-acbc-1aec-7b2170a571de@selasky.org> <882d40df-6082-bcca-a9ee-944aeca115a8@selasky.org> From: Lee Brown Date: Fri, 16 Feb 2018 08:52:30 -0800 Message-ID: Subject: Re: Dell R630 unable to detect USB, can't boot To: freebsd-hardware@freebsd.org, freebsd-usb@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Feb 2018 16:52:33 -0000 On Thu, Feb 15, 2018 at 12:10 AM, Hans Petter Selasky wrote: > On 02/15/18 06:24, Lee Brown wrote: > >> I do find it curious that the loader is able to work the USB hardware but >> not the kernel. >> > > The loader is using the BIOS's USB code. Usually there is a handover from > BIOS to OS, maybe that's where it's broken. Got a little more information from watching slow video: pcib1: on apci0 pcib1: _OSC returned error 0x10 I think that may be AE_LIMIT, but I can't be sure. Do you know if ACPI could be the root cause, I do see the ehci device created later on, so it does 'see' the USB bus, but maybe that above error prevents it from finding the hub? I don't know I'm wildly speculating here. Maybe I should address the above first, then circle around to this.