Date: Sat, 17 Oct 1998 12:28:58 -0400 (EDT) From: Chuck Robey <chuckr@mat.net> To: freebsd-current@FreeBSD.ORG Subject: Latest kernel Message-ID: <Pine.BSF.4.05.9810171223540.344-100000@picnic.mat.net>
next in thread | raw e-mail | index | archive | help
I am getting panics immediately after startup on the latest kernel now, which I wasn't getting a few days ago. I haven't used crash dumps before, but I want to report something useful, so I want to start this, and I have a question. I've built the debugging kernel, about 10M in size, but I don't really have room in /var to stick it, is there any problem with it being in /usr2, where there's lots of room? I have 2 swap partitions, and either will easily handle the crash dump. When the crash occurs, right after starting the smp stuff, and drops to ddb, what's the command to get it to dump the crash dump? Is it just there automatically, and do I just type "panic" to get ddb to exit and dump the core? I understand I have to save the crash dump immediately after rebooting -s with my good kernel, using savecore. All the savecore examples give /var/crash as the target, is that hardcoded in, or can I move it as I showed above to /usr2 (/usr2/crash) after mounting /usr2 in single, so it's writeable? Thanks. I'll report the results soon's I get them. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- 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.05.9810171223540.344-100000>