run interrupt driven hooks: still waiting for xpt_config
Marc UBM Bocklet
ubm at u-boot-man.de
Fri Aug 7 22:24:00 UTC 2009
On Thu, 6 Aug 2009 23:09:09 +0200
Marc "UBM" Bocklet <ubm at u-boot-man.de> wrote:
> On Wed, 22 Jul 2009 20:17:50 +0200
> Marc "UBM" Bocklet <ubm at u-boot-man.de> wrote:
> > On Sun, 12 Jul 2009 19:45:47 +0200
> > Marc "UBM" Bocklet <ubm at u-boot-man.de> wrote:
> > > On Sun, 12 Jul 2009 18:10:34 +0200
> > > Marc "UBM" Bocklet <ubm at 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?
> 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.
More information about the freebsd-current