From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 16 04:06:30 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B62D16A4CF for ; Sun, 16 Jan 2005 04:06:30 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F9CA43D4C for ; Sun, 16 Jan 2005 04:06:30 +0000 (GMT) (envelope-from bsdaemon@comcast.net) Received: from fw.home (pcp05404374pcs.norstn01.pa.comcast.net[68.80.144.252]) by comcast.net (sccrmhc13) with SMTP id <20050116040629016006pc33e>; Sun, 16 Jan 2005 04:06:29 +0000 Received: (qmail 74934 invoked from network); 16 Jan 2005 04:06:30 -0000 Received: from kris.home (HELO ?192.168.0.251?) (192.168.0.251) by fw.home with SMTP; 16 Jan 2005 04:06:30 -0000 Message-ID: <41E9E989.8040501@comcast.net> Date: Sat, 15 Jan 2005 23:11:53 -0500 From: Kris Maglione User-Agent: Mozilla Thunderbird 1.0 (X11/20041212) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ata_catch_inflight causes boot freeze X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 04:06:30 -0000 On my laptop, while the call to ata_catch_inflight is in dev/ata/ata-all.c, my laptop freezes at boot, after detecting acd0 and doing GEOM: Configure for ad0. I don't mind commenting out the line in my builds, but others shouldn't have to go through what I did to come to the same conclusion (building the kernel from various dates and burning it to a FreesBIE CD). Anyway, I'm not familiar enought with the kernel archetecture to figure out why the function causes a boot freeze. I only figured out that it did by reviewing commits between the dates that it worked and the dates that it didn't. I'm willing to provide whatever information/help that I can to come up with a more permanent solution.