Date: Fri, 14 Aug 2009 15:18:26 +0200 From: Marc UBM <ubm.freebsd@googlemail.com> To: freebsd-current@freebsd.org Subject: Re: run interrupt driven hooks: still waiting for xpt_config Message-ID: <20090814151826.66e5077e.ubm.freebsd@gmail.com> In-Reply-To: <20090808235013.eab98028.ubm@u-boot-man.de> 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> <20090808235013.eab98028.ubm@u-boot-man.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 8 Aug 2009 23:50:13 +0200 Marc "UBM" Bocklet <ubm@u-boot-man.de> wrote: > > > 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 :-) I just made sure that the problem still exists with a freshly csupped -current (unfortunately, it does), I'll try removing possible culprits from my kernel next. Bye Marc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090814151826.66e5077e.ubm.freebsd>