Date: Tue, 4 Mar 2008 16:00:10 -0500 From: Jeff Blank <jb000002@mr-happy.com> To: freebsd-stable@freebsd.org Subject: Re: 7.0-STABLE amd64 kernel trap during boot-time device probe Message-ID: <20080304210010.GT44781@mr-happy.com> In-Reply-To: <20080302080429.GB67687@server.vk2pj.dyndns.org> References: <20080301194404.GA1571@mr-happy.com> <20080301225646.GV67687@server.vk2pj.dyndns.org> <20080302043130.GA1583@mr-happy.com> <20080302080429.GB67687@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080304210010.GT44781>