From owner-freebsd-current Wed Jan 5 7:25: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (dialfwn11.fwn.rug.nl [129.125.32.161]) by hub.freebsd.org (Postfix) with ESMTP id 191C6153EE for ; Wed, 5 Jan 2000 07:24:56 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id MAA02123; Tue, 4 Jan 2000 12:11:16 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Tue, 4 Jan 2000 12:11:16 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Vallo Kallaste Cc: Alex , freebsd-current@FreeBSD.ORG Subject: Re: panic in newpcm ( was Re: Ouch! Something broke (possibly ATA)) In-Reply-To: <20000104124628.A40560@myhakas.matti.ee> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ....and I apologise for wrongfully accusing it. The panic is in fact > > caused by newpcm (Cameron CC'd). DDB trace can be provided upon request > > (is there a way to save it into a file instead of having to write it > > down on a piece of paper?) > > Sure. Hook up serial console or some terminal program to appropriate > serial port using null-modem cable, then rebuild your kernel and boot > with right flag. Look at sys/i386/LINT, man sio(4) and man boot(8). Or, if the panic happens after rc.conf has been run / you can log in, set the dump device to something sensible. From DDB type panic. When the system boots up again, you type savecore /some/dir and possibly copy the debugging kernel from /sys/compile/KERNELNAME to /some/dir/kernel.0 as well. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message