Date: Sat, 8 Aug 2009 23:50:13 +0200 From: Marc "UBM" Bocklet <ubm@u-boot-man.de> To: current@freebsd.org Subject: Re: run interrupt driven hooks: still waiting for xpt_config Message-ID: <20090808235013.eab98028.ubm@u-boot-man.de> In-Reply-To: <alpine.BSF.2.00.0908081159270.14907@fledge.watson.org> 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> <alpine.BSF.2.00.0908081159270.14907@fledge.watson.org>
index | next in thread | previous in thread | raw e-mail
On Sat, 8 Aug 2009 12:02:41 +0100 (BST) Robert Watson <rwatson@FreeBSD.org> wrote: > 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 :-). Thanks a lot for the suggestion, I'll be on holiday for one week starting tomorrow, I'll try narrowing it down as soon as I'm back :-) Bye Marc -- "And what rough beast, its hour come round at last, Slouches towards Bethlehem to be born?" W.B. Yeats, The Second Cominghelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090808235013.eab98028.ubm>