Date: Sun, 12 Jul 2009 12:23:16 +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: <20090712122316.4f63fc62.ubm@u-boot-man.de> In-Reply-To: <20090711222304.fc99056a.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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 11 Jul 2009 22:23:04 +0200 Marc "UBM" Bocklet <ubm@u-boot-man.de> wrote: > On Sat, 11 Jul 2009 20:58:37 +0200 > Marc "UBM" Bocklet <ubm@u-boot-man.de> wrote: > > > On Fri, 10 Jul 2009 20:03:52 +0200 > > Marc "UBM" Bocklet <ubm@u-boot-man.de> wrote: > > [...] > > > Another followup: it also makes no difference if there's an actual > > device attached to the controller. I'll try reverting the ahci patch > > next and see if that changes anything. > > enabling or disabling the ahci patch makes no difference, neither does > disabling the onboard usb controller in the bios. For further > reference, this is also a Gigabye mainboard. > > I'm thinking about "downgrading" FreeBSD on that machine to maybe find > out where the trouble started. Can I safely csup back to a certain > date and then buildkernel, installworld the usual way or are there any > caveats? A kernel csupped with "2009.04.20.06.00.00" boots and discovers the highpoint controller + attached disks. I'm in the process of narrowing it down further. Bye Marc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090712122316.4f63fc62.ubm>