Date: Sat, 8 Aug 2009 17:51:19 +0200 From: Attilio Rao <attilio@freebsd.org> To: Robert Watson <rwatson@freebsd.org> Cc: freebsd-current@freebsd.org, Marc UBM Bocklet <ubm@u-boot-man.de> Subject: Re: run interrupt driven hooks: still waiting for xpt_config Message-ID: <3bbf2fe10908080851j61efcf67g8e638aff9a9c5ba9@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.0908081159270.14907@fledge.watson.org> References: <20090708192642.6b30167e.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>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/8/8 Robert Watson <rwatson@freebsd.org>: > 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 :-). Beyon that, I think that debugging in CAM can be improved by a good factor using alredy existing general infrastructure (KTR logging points, new ddb commands, etc). We need someone which is willing to spend some time on that. Attilio -- Peace can only be achieved by understanding - A. Einstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3bbf2fe10908080851j61efcf67g8e638aff9a9c5ba9>