Date: Wed, 22 Jul 2009 20:17:50 +0200 From: Marc "UBM" Bocklet <ubm@u-boot-man.de> To: freebsd-current@freebsd.org Subject: Re: run interrupt driven hooks: still waiting for xpt_config Message-ID: <20090722201750.4ff23293.ubm@u-boot-man.de> In-Reply-To: <20090712194547.9e573116.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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 12 Jul 2009 19:45:47 +0200 Marc "UBM" Bocklet <ubm@u-boot-man.de> wrote: > On Sun, 12 Jul 2009 18:10:34 +0200 > Marc "UBM" Bocklet <ubm@u-boot-man.de> 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? Is there anybody on this list who has the same controller but does not suffer from this problem? Bye Marc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090722201750.4ff23293.ubm>