From owner-freebsd-current@FreeBSD.ORG Mon Mar 14 01:34:45 2011 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 C9959106566C for ; Mon, 14 Mar 2011 01:34:45 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 94BE78FC1D for ; Mon, 14 Mar 2011 01:34:45 +0000 (UTC) Received: from [192.168.1.100] (m206-63.dsl.tsoft.com [198.144.206.63]) by ns1.feral.com (8.14.4/8.14.3) with ESMTP id p2E1Yhd4098457; Sun, 13 Mar 2011 17:34:44 -0800 (PST) (envelope-from mj@feral.com) Message-ID: <4D7D70B8.9020803@feral.com> Date: Sun, 13 Mar 2011 18:34:48 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: Yuri Pankov References: <20110313230138.GA1291@darklight.org.ru> <20110313233637.GB1291@darklight.org.ru> <4D7D5646.3080004@feral.com> <20110314000337.GC1291@darklight.org.ru> In-Reply-To: <20110314000337.GC1291@darklight.org.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.2.6 (ns1.feral.com [192.67.166.1]); Sun, 13 Mar 2011 17:34:44 -0800 (PST) Cc: freebsd-current@freebsd.org Subject: Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8 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: Mon, 14 Mar 2011 01:34:45 -0000 On 3/13/2011 5:03 PM, Yuri Pankov wrote: > On Sun, Mar 13, 2011 at 04:41:58PM -0700, Matthew Jacob wrote: >> Yes they are. The full messages from the failed boot would be helpful. >> Looks like we have ATA in CAM now, so it's possible that the disk reset >> failed, etc... > What are my options for saving the output from failed boot other than > handtyping it (no serial ports, no serial USB adapters)? None that I can think of :-(