From owner-freebsd-stable@FreeBSD.ORG Tue Mar 4 21:17:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E181910656C5 for ; Tue, 4 Mar 2008 21:17:02 +0000 (UTC) (envelope-from jfb@mr-paradox.net) Received: from vexbert.mr-paradox.net (vexbert.mr-paradox.net [208.4.93.28]) by mx1.freebsd.org (Postfix) with ESMTP id B8B938FC1A for ; Tue, 4 Mar 2008 21:17:02 +0000 (UTC) (envelope-from jfb@mr-paradox.net) Received: by vexbert.mr-paradox.net (Postfix, from userid 16139) id 985CC84460; Tue, 4 Mar 2008 16:00:11 -0500 (EST) Date: Tue, 4 Mar 2008 16:00:10 -0500 From: Jeff Blank To: freebsd-stable@freebsd.org Message-ID: <20080304210010.GT44781@mr-happy.com> References: <20080301194404.GA1571@mr-happy.com> <20080301225646.GV67687@server.vk2pj.dyndns.org> <20080302043130.GA1583@mr-happy.com> <20080302080429.GB67687@server.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080302080429.GB67687@server.vk2pj.dyndns.org> X-Face: #0jV*~a}VtKS-&E/!EJpH('H1Va}24dxF0oT&+.R3Gu8C; xhSC+<|+H84&YLbMvphuRT4cp3.|8EN_(2Eix/6{.Up~u`a^}0Ln&b+9Fw|BPig@-{y\pL_46d&ZwA]5%_AU?}DezfE&1!>H?3E$!Yve7.O<+..Jnb4:'6Ey_]FtFzU9=*l$1p/@gA,Ze>^5<]+r(XJ+m7`/vMDc$'wy|`e Subject: Re: 7.0-STABLE amd64 kernel trap during boot-time device probe X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Mar 2008 21:17:03 -0000 On Sun, Mar 02, 2008 at 07:04:29PM +1100, Peter Jeremy wrote: > It looks like there's an unexpected ATA interrupt. I can't think of > any reason why either sound or netgraph would cause this - neither > should be touching the hardware directly. Unless someone else has > seen this before, tracking it down could be time-consuming. > > I think you'll need a serial console to continue. Are you still mainly interested in the 'boot -v' output, or did you have something else in mind for the serial console? I looked over the 'remote GDB' section of the handbook, and I gather I'd need a second amd64 host for that, but I unfortunately don't. Jeff