Date: Fri, 10 Jul 2009 18:48:56 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Marc UBM Bocklet <ubm@u-boot-man.de> Cc: freebsd-current@freebsd.org Subject: Re: run interrupt driven hooks: still waiting for xpt_config Message-ID: <20090710184743.Q245@maildrop.int.zabbadoz.net> In-Reply-To: <20090710200352.72ef6804.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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 10 Jul 2009, Marc UBM Bocklet wrote: > On Wed, 8 Jul 2009 22:50:48 +0200 > Marc "UBM" Bocklet <ubm@u-boot-man.de> wrote: > >> On Wed, 8 Jul 2009 19:26:42 +0200 >> Marc "UBM" Bocklet <ubm@u-boot-man.de> wrote: >> >>> >>> Hiho! :-) >>> >>> I just put a Highpoint RocketRaid 2322 in our file server. There are >>> no drives connected to it yet. >>> >>> I'm running: >>> >>> FreeBSD xxx 8.0-CURRENT FreeBSD 8.0-CURRENT #15: Sat Jul 4 >>> 15:23:12 CEST 2009 >>> >>> Since I put the 2322 in, the machine hangs late in the boot process >>> with above message. It continues to wait until: >>> >>> run interrupt driven hooks: still waiting for xpt_config (300 >>> seconds) and then theres nothing. No panic, keyboard still works, I >>> can still scroll through dmesg, but nothing more. >>> >>> Before it the hptrr(4) attaches, there's the following message: >>> >>> xpt_dev async called. >>> >>> I searched the archives and found some references to firewire, but >>> the machine in question has no firewire controller. >>> >>> Is there anything else I can do to debug this? >>> >>> For the record, the card is PCIe 4x, but I put it in the PCIe 16x >>> slot. The card seems to work fine though, I can access its BIOS and >>> its recognized by the FreeBSD driver. >>> >>> I'm also running with the new ahci driver. >> >> for the record: verbose boot shows no additional info. > > further info: removing the highpoint controller makes the problem > disappear. > > Is there any additional info I should/can provide? hmm I have see similar symptoms with aacp when booting from CD (that I told a few people about privately). I have some logs and will try to produce more Monday morning. /bz -- Bjoern A. Zeeb The greatest risk is not taking one.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090710184743.Q245>