Date: Sat, 6 Apr 1996 19:30:21 +0200 (MET DST) From: =?iso-8859-1?Q?=22=C5ge?= =?iso-8859-1?Q?R=F8bekk=22?= <aagero@aage.priv.no> To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-bugs@freebsd.org Subject: Re: Hangs after editing a disklabel Message-ID: <199604061730.TAA02698@birk04.studby.uio.no> In-Reply-To: <199604061609.SAA01697@uriah.heep.sax.de> (message from J Wunsch on Sat, 6 Apr 1996 18:09:28 %2B0200 (MET DST))
next in thread | previous in thread | raw e-mail | index | archive | help
| > | > And since this does not leave a core dump, it's hard | > | > to identify the cause. | > | | > | You probably need DDB for it. | > | > I'm using X most of the time, so there might be some console output | > which I am not able to read. Is it possible to make the panic routine | > switch to the console? | | Everything else goes to the console. If you had a panic (but no DDB | configured), you would have noticed the reboot :). I'd like to see that there actually _is_ a core dump, to see the "dumping to dev ..." text. E.g. this crash does delay for the usual time to write a core file to the swap device and then reboots, but savecore does not find any core file upon boot. But would switching to the text console require that the kernel has particular knowledge of the graphics card? -aage
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604061730.TAA02698>