From owner-freebsd-current@FreeBSD.ORG Sun Jul 12 16:10:39 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C788A1065670 for ; Sun, 12 Jul 2009 16:10:39 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from mail.upper.net (mail.upper.net [62.75.224.33]) by mx1.freebsd.org (Postfix) with ESMTP id 5C5EF8FC23 for ; Sun, 12 Jul 2009 16:10:39 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from ubm.mine.nu (mail.upper.net [62.75.224.33]) (authenticated bits=0) by mail.upper.net (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id n6CGAYuC005869 for ; Sun, 12 Jul 2009 18:10:34 +0200 Received: from ubm.mine.nu ([85.181.47.100] helo=ubm.mine.nu) by ASSP.nospam.UpPeRnEt; 12 Jul 2009 18:10:34 +0200 Date: Sun, 12 Jul 2009 18:10:34 +0200 From: Marc "UBM" Bocklet To: freebsd-current@freebsd.org 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> X-Mailer: Sylpheed 2.6.0 (GTK+ 2.12.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 12 Jul 2009 19:51:04 +0000 Subject: Re: run interrupt driven hooks: still waiting for xpt_config X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jul 2009 16:10:40 -0000 On Sun, 12 Jul 2009 12:23:16 +0200 Marc "UBM" Bocklet 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