From owner-freebsd-bugs  Sun Feb 11 00:00:04 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA18823
          for bugs-outgoing; Sun, 11 Feb 1996 00:00:04 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA18796
          Sun, 11 Feb 1996 00:00:02 -0800 (PST)
Date: Sun, 11 Feb 1996 00:00:02 -0800 (PST)
Message-Id: <199602110800.AAA18796@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Bruce Evans <bde@zeta.org.au>
Subject: Re: kern/1016: panic: vm_page_free: freeing free page, sddump: no slices
Reply-To: Bruce Evans <bde@zeta.org.au>
Sender: owner-bugs@FreeBSD.ORG
Precedence: bulk

The following reply was made to PR kern/1016; it has been noted by GNATS.

From: Bruce Evans <bde@zeta.org.au>
To: FreeBSD-gnats-submit@FreeBSD.ORG, hsu@clinet.fi
Cc:  Subject: Re: kern/1016: panic: vm_page_free: freeing free page, sddump: no slices
Date: Sun, 11 Feb 1996 18:50:00 +1100

 >>Description:
 
 >The machine was sitting dead and this was on the console:
 
 >panic: vm_page_free: freeing free page
 
 I don't know what caused this.
 
 >dumping to dev 401, offset 0
 >dump Debugger("sddump: no slices") called
 >panic: vm_page_free: freeing free page
 
 >dumping to dev 401, offset 0
 >dump Debugger("sddump: no slices") called
 >panic: vm_page_free: freeing free page
 
 >...
 
 The "no slices" message is probably because no minor on sd0 was opened.
 Normally the dump device is the same as the swap device so it gets opened
 by swapon().  Relevant bugs:
 - setdumpdev() neglects to open the dump device.
 - autoconf.c neglects to call setdumpdev() for the compile-time configured
   dump device, if any.
 
 I don't know what caused the repeated (recursive?) panics.
 
 Bruce