From owner-freebsd-usb@freebsd.org  Fri Jan 13 21:18:38 2017
Return-Path: <owner-freebsd-usb@freebsd.org>
Delivered-To: freebsd-usb@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60D2ACAE4A1
 for <freebsd-usb@mailman.ysv.freebsd.org>;
 Fri, 13 Jan 2017 21:18:38 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
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 50A9E1212
 for <freebsd-usb@FreeBSD.org>; Fri, 13 Jan 2017 21:18:38 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0DLIcRH018866
 for <freebsd-usb@FreeBSD.org>; Fri, 13 Jan 2017 21:18:38 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-usb@FreeBSD.org
Subject: [Bug 215898] Usb Acting weird
Date: Fri, 13 Jan 2017 21:18:38 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: usb
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jhb@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-215898-17-p3K9rDvWxm@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-215898-17@https.bugs.freebsd.org/bugzilla/>
References: <bug-215898-17@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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.23
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb/>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jan 2017 21:18:38 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215898

--- Comment #16 from John Baldwin <jhb@FreeBSD.org> ---
The _ADR is probably not relevant.  The pcib driver uses _ADR as part of a
fallback to determine the PCI bus number of the bus under a Host-PCI bridge=
 if
_BBN doesn't work or isn't present.  However, if you only have a single
Host-PCI bridge it is going to be using PCI bus 0 which is what it will end=
 up
using (and that works since you find PCI devices).  If it was truly broken =
you
wouldn't find any PCI devices at all under the bridge.

Carlos, can you try disabling EARLY_AP_STARTUP in your kernel config to see=
 if
that makes a difference?

--=20
You are receiving this mail because:
You are the assignee for the bug.=