From owner-freebsd-current@freebsd.org Fri Dec 9 23:45:31 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFC6CC6FF30; Fri, 9 Dec 2016 23:45:31 +0000 (UTC) (envelope-from kargl@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AA8A31644; Fri, 9 Dec 2016 23:45:31 +0000 (UTC) (envelope-from kargl@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id uB9NjUCH034476 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 9 Dec 2016 15:45:30 -0800 (PST) (envelope-from kargl@troutmask.apl.washington.edu) Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id uB9NjU9M034475; Fri, 9 Dec 2016 15:45:30 -0800 (PST) (envelope-from kargl) Date: Fri, 9 Dec 2016 15:45:30 -0800 From: "Steven G. Kargl" To: Hans Petter Selasky Cc: kargl@uw.edu, freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: System hangs at boot in xhci0 Message-ID: <20161209234530.GA21666@troutmask.apl.washington.edu> Reply-To: kargl@uw.edu References: <20161209210940.GA1144@troutmask.apl.washington.edu> <5a509678-2a67-b538-ea42-d9e80a6bd3eb@selasky.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5a509678-2a67-b538-ea42-d9e80a6bd3eb@selasky.org> User-Agent: Mutt/1.6.1 (2016-04-27) X-Mailman-Approved-At: Fri, 09 Dec 2016 23:46:58 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2016 23:45:31 -0000 On Fri, Dec 09, 2016 at 11:58:21PM +0100, Hans Petter Selasky wrote: > On 12/09/16 22:09, Steve Kargl wrote: > > I updated my system to > > > > % svn info /usr/src > > Revision: 309748 > > > > Built a shiny new kernel, which hangs during boot. > > There is no panic. Using the dmesg from kernel.old/kernel, > > the last few reported are > > > > > > pci2: on pcib2 > > xhci0: mem 0xfe900000-0xfe900fff > > irq 48 at device 0.0 on pci2 > > xhci0: 32 bytes context size, 64-bit DMA > > > > At this point, the system is completely unresponse and > > needs to be power cycled. > > > > Hi, > > What is the next message in the old kernel which is printed? There has > been zero changes in the XHCI driver recently. > > Can you copy /boot/kernel.old to /boot/kernel.works > > Then add this option to the GENERIC kernel config: > > options VERBOSE_SYSINIT > > What are the last few messages in dmesg when you boot with the above flag? > With a boot_verbose of the new kernel I get the following output: xhci0: 32 bytes context size, 64-bit DMA xhci0: attempting to allocate 1 MSI vectors (4 supported) msi: routing MSI IRQ 260 to local APIC 16 vector 55 xhci0: using IRQ 260 for MSI xhci0: MSI enabled usbus0 on xhci0 xhci0: usbpf: Attached random: harvesting attach, 8 bytes (4 bits) from usbus0 random: harvesting attach, 8 bytes (4 bits) from xhci0 random: harvesting attach, 8 bytes (4 bits) from pci2 random: harvesting attach, 8 bytes (4 bits) from pcib2 and then the system locks up. With the old kernel (circa Oct 10th sources), next few lines from dmesg are pcib3: irq 54 at device 10.0 on pci0 pcib0: allocated type 4 (0xd000-0xdfff) for rid 1c of pcib3 pcib0: allocated type 3 (0xfe800000-0xfe8fffff) for rid 20 of pcib3 pcib3: domain 0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0xd000-0xdfff pcib3: memory decode 0xfe800000-0xfe8fffff pci3: on pcib3 I think that hang isn't caused by xhci, but rather is a victim on being the last successfully probed device. In the last weeks there have been a few commits (309588, 309400, and 308953) that touched ACPI. I'm currently reverting these changes to test if one is causing the problem. I did see that one of these revisions specific mentions the ALASKA AMI bios, which I happen to have. However, that commit also mentions a skylake processor while I have an AMD FX-8350. -- Steve http://troutmask.apl.washington.edu/~kargl/ https://www.youtube.com/watch?v=6hwgPfCcpyQ