From owner-freebsd-bugs Tue Dec 19 12:40:07 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA04623 for bugs-outgoing; Tue, 19 Dec 1995 12:40:07 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA04588 Tue, 19 Dec 1995 12:40:02 -0800 (PST) Date: Tue, 19 Dec 1995 12:40:02 -0800 (PST) Message-Id: <199512192040.MAA04588@freefall.freebsd.org> To: freebsd-bugs Cc: From: "Garrett A. Wollman" Subject: kern/903: panic: m_copydata Reply-To: "Garrett A. Wollman" Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR kern/903; it has been noted by GNATS. From: "Garrett A. Wollman" To: scrappy@hub.org Cc: FreeBSD-gnats-submit@freebsd.org Subject: kern/903: panic: m_copydata Date: Tue, 19 Dec 1995 15:36:31 -0500 < said: > and reboot of the system. Having enabled DDB and DODUMP, I'm not > getting a 'savecore', but it does put me into the kernel debugger > instead of rebooting. `options DODUMP' has not been meaningful for some time. You should use the dumpon(8) command to set up a swap area for dumps during bootup. (There should be hooks in /etc/sysconfig for this, but I don't recall if they are mine or in the distribution version.) > I have a /var/crash directory created, but not core dump... > In transcribing the Trace to paper, do I need *all* the lines, > or is there only one or two that are significant? This is precisely the sort of situation where having a port-mortem dump is incredibly valuable, since otherwise I can but guess at the cause of your problem. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant