Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uunet!europa.asd.contel.com!wlbr!voder!apple!motcsd!lance From: lance@motcsd.csd.mot.com (lance.norskog) Newsgroups: comp.unix.wizards Subject: Re: Making sense of a system coredump Message-ID: <4281@motcsd.csd.mot.com> Date: 19 Jun 91 00:43:26 GMT References: <1991Jun13.220751.26994@convex.com> <19384@rpp386.cactus.org> Distribution: comp.unix.wizards Organization: Motorola CSD, Cupertino CA Lines: 23 This does not answer his problem, but does explain how to crash on 386 UNIX. (I cannot afford SGI gear, alas.) When Unix does a panic and saves all its RAM to disk, it dumps it into the swap area. After it reboots, it asks you if you want to save the core dump. If you save it to tape, you get a raw disk dump of the swap area. You can then 'dd' the tape into a Unix file, and run /etc/crash -d /tmp/bigcore -n /unix I took this question out of the system start-up, and just run /etc/crash -d /dev/swap after the system startup script does its endless disk preening. There's a trick here: the system startup scripts run one program at a time. With even a 4 megabyte system, it never really needs to page any data out before that first console login prompt. So, your panic dump is still intact in /dev/swap. You can verify this by running '/etc/swap -l'. Lance Norskog