Date: Sun, 12 Jul 2009 18:10:34 +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: <20090712181034.93811d03.ubm@u-boot-man.de> In-Reply-To: <20090712122316.4f63fc62.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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 12 Jul 2009 12:23:16 +0200 Marc "UBM" Bocklet <ubm@u-boot-man.de> wrote: > > 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. 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. Bye Marc -- "And what rough beast, its hour come round at last, Slouches towards Bethlehem to be born?" W.B. Yeats, The Second Coming
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090712181034.93811d03.ubm>