Re: bin/41583: savecore problem with netbsd-5

[David Holland <dholland-bugs%netbsd.org@localhost>]

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

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: bin/41583: savecore problem with netbsd-5
Date: Sun, 21 Jun 2009 17:39:17 +0000

 On Fri, Jun 12, 2009 at 10:35:00PM +0000, AndreasBurghardt%gmx.de@localhost 
wrote:
  > since some days I discover a strange error message from savecore
  > and cannot find any reason for this:
  > 
  > Jun 12 22:13:43 savecore: warning: (null) version mismatch: NetBSD
  >   5.0_STABLE (GENERIC) #0: Fri Jun 12 20:39:57 CEST 2009
  >   root@sadar:/usr/obj/obj/sys/arch/i386/compile/GENERIC and Sat Jun 6
  >   16:41:01 CEST 2009
  >   root@sadar:/usr/obj/obj/sys/arch/i386/compile/GENERIC
  > Jun 12 22:13:43  savecore: reboot after panic: panic: trap
  > 
  > This shows up everytime I boot. Of caurse I could set savecore=NO
  > to /etc/rc.conf, but ...
 
 Do you have version 1.76.2.1 of savecore.c? (ident /sbin/savecore will
 tell you) If not, try updating savecore and see if the problem goes
 away. If so, you're seeing PR 38425.
 
 If not, you may still be seeing something related, or it may be
 something else.
 
 Anyway, what the message means is that you have a kernel crash dump in
 your swap partition that savecore thinks came from a kernel dated June
 6, and you're currently running a kernel dated June 12. Theoretically
 savecore is supposed to still save the dump out and clear it from the
 swap partition, but apparently it isn't.
 
 If you want the dump, the path of least resistance is to boot the June
 6 kernel, if you still have it.
 
 If you don't want the dump and you just want savecore to shut up, the
 easiest approach is probably to clear the dump header from the swap
 partition. (I don't know offhand what offset the header appears at,
 but I can easily look it up if necessary.)
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost