Date: Tue, 4 Jan 2000 12:11:16 +0100 (CET) From: Nick Hibma <n_hibma@webweaving.org> To: Vallo Kallaste <vallo@matti.ee> Cc: Alex <ak@freenet.co.uk>, freebsd-current@FreeBSD.ORG Subject: Re: panic in newpcm ( was Re: Ouch! Something broke (possibly ATA)) Message-ID: <Pine.BSF.4.20.0001041210010.2117-100000@localhost> In-Reply-To: <20000104124628.A40560@myhakas.matti.ee>
next in thread | previous in thread | raw e-mail | index | archive | help
> > ....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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.20.0001041210010.2117-100000>