From owner-freebsd-current@FreeBSD.ORG Sat Aug 8 11:02:42 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E7A11065670 for ; Sat, 8 Aug 2009 11:02:42 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 027358FC21 for ; Sat, 8 Aug 2009 11:02:42 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 97D5B46B0D; Sat, 8 Aug 2009 07:02:41 -0400 (EDT) Date: Sat, 8 Aug 2009 12:02:41 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Marc UBM Bocklet In-Reply-To: <20090808002354.61c6c5a3.ubm@u-boot-man.de> Message-ID: References: <20090708192642.6b30167e.ubm@u-boot-man.de> <20090708225048.ec9d9cad.ubm@u-boot-man.de> <20090710200352.72ef6804.ubm@u-boot-man.de> <20090711205837.46b11405.ubm@u-boot-man.de> <20090711222304.fc99056a.ubm@u-boot-man.de> <20090712122316.4f63fc62.ubm@u-boot-man.de> <20090712181034.93811d03.ubm@u-boot-man.de> <20090712194547.9e573116.ubm@u-boot-man.de> <20090722201750.4ff23293.ubm@u-boot-man.de> <20090806230909.d01e844a.ubm@u-boot-man.de> <20090808002354.61c6c5a3.ubm@u-boot-man.de> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: run interrupt driven hooks: still waiting for xpt_config X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 08 Aug 2009 11:02:42 -0000 On Sat, 8 Aug 2009, Marc UBM Bocklet wrote: >>>>> I've got it narrowed down between "2009.06.30.06.00.00" and today. A >>>>> kernel with the "old" date boots, a freshly csupped and compiled kernel >>>>> hangs with the usual symptoms (waiting for interrupt driven hooks). >>>>> >>>>> I'll try csupping to just before the big cam commit to see if there is >>>>> any connection. When I said earlier that I was not running with the ahci >>>>> patch, I was partly wrong. I did not have device ahci in my kernel >>>>> config file nor had it loaded as a module, but I had the patch applied. >>>> >>>> "2009.07.09.06.00.00" fixes the problem. Could it be that there are some >>>> subtle interactions in the cam subsystem that are stirred by the recent >>>> mega-commit? >>> >>> Is there any other info I can / should provide to help debugging this? >> >> Any news on this? This pretty much prevents me from running 8.0 :-/ > > I've a friend with a similar problem (also HighPoint controller, also "run > interrupt driven hooks: still waiting for xpt_config"), who gets a panic. > I'll try to get the panic string and a backtrace, if I do, I'll post it > here. xpt_config basically means that you're waiting on a device driver attached to CAM to finish probing, which could point at a number of potential problem sources (including things like interrupt routing problems). At least in the 7.x line, I've seen firewire and USB at various times cause this issue. It might be interesting to compile down to the smallest set of cam-related drivers required to support necessary hardware (omit firewire, for example) and see if you see any improvement. Pinning it down to a specific driver would have significant debugging value :-). Robert N M Watson Computer Laboratory University of Cambridge