NetBSD Problem Report #11781

Received: (qmail 14917 invoked from network); 20 Dec 2000 02:19:54 -0000
Message-Id: <200012200219.VAA28438@cowboy-burt.mcmahill.net>
Date: Tue, 19 Dec 2000 21:19:53 -0500 (EST)
From: dmcmahill@netbsd.org
Reply-To: dmcmahill@netbsd.org
To: gnats-bugs@gnats.netbsd.org
Subject: dump didn't happen
X-Send-Pr-Version: 3.95

>Number:         11781
>Category:       port-vax
>Synopsis:       dump didn't happen
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    port-vax-maintainer
>State:          dead
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 20 02:20:00 +0000 2000
>Closed-Date:    Sat Mar 05 09:06:19 +0000 2016
>Last-Modified:  Sat Mar 05 09:06:19 +0000 2016
>Originator:     Dan McMahill
>Release:        1.5
>Organization:
NetBSD
>Environment:

System: NetBSD catholic-girls 1.5 NetBSD 1.5 (GENERIC) #1: Sun Nov 19 15:44:10 PST 2000     matt@cheetah.local:/u1/kobj/GENERIC vax

>Description:

my vax paniced.  So at the db> prompt I did 'c' and got:

syncing disks... 7 7 7 7 7 7 6 6 6 6 6 6 6 6 6 6 6 5 5 5 5 5 giving up

dumping to dev 20,9 offset 99122
dump succeeded

the above 2 lines happend fairly quickly.

and when the machine rebooted, I saw:
Checking for core dump...
savecore: no core dump

a few comments from people who have more of a clue than I:
<briggs> The vax calls: (...d_dump)(dumpdev, 0, 0, 0)
<cgd> that's almost certainly wrong.


>How-To-Repeat:
panic the machine
db> c

see it claim to produce a dump

reboot and see none.


>Fix:

>Release-Note:
>Audit-Trail:

From: mcmahill@mtl.mit.edu
To: gnats-bugs@netbsd.org
Cc:  
Subject: port-vax/11781
Date: Wed, 20 Dec 2000 08:23:32 -0500 (EST)

 ---------- Forwarded message ----------
 Date: Wed, 20 Dec 2000 10:47:10 +0100 (MET)
 From: Anders Magnusson <ragge@ludd.luth.se>
 To: dmcmahill@netbsd.org
 Subject: Re: port-vax/11781: dump didn't happen

 This is because there are no support for crash dump.
 What should be written is:
 - Code to save info about the dump device and to turn off the VM system.
 - Standalone device drivers that can actually do the dump.

State-Changed-From-To: open->suspended 
State-Changed-By: ragge 
State-Changed-When: Wed Mar 5 05:27:44 PST 2003 
State-Changed-Why:  
Vax don't have any code for doing crash dumps (yet). 
State-Changed-From-To: suspended->dead
State-Changed-By: ragge@NetBSD.org
State-Changed-When: Sat, 05 Mar 2016 09:06:19 +0000
State-Changed-Why:
Dump code isn't implemented for any VAX discs, and it's not likely to happen :-/


>Unformatted:

Home	PR Database Search