savecore: first and last dump headers disagree

From: Palle Girgensohn (girgen_at_FreeBSD.org)
Date: 05/23/05

  • Next message: Mipam: "Re: em and bge driver MPSAFE?"
    Date: Mon, 23 May 2005 10:30:47 +0200
    To: stable@freebsd.org, amd64@freebsd.org
    
    
    

    Hi!

    We have an amd64 system that still experiences crashes after installing
    5.4, mostly during high loads. (It's been unstable all the time, really;
    see previous posts.)

    I've added dumpdev="/dev/amrd0s2b", and some time ago I did get coredumps,
    but with latest versions of the kernel, savecore does not give me a dump,
    instead it says:

    savecore: first and last dump headers disagree on /dev/amrd0s2b
    savecore: unsaved dumps found but not saved

    What can I do to fix this? I guess I need a core dump to proceed in finding
    the problem?

    Also, the machine does not reboot after a panic, that's an even bigger
    problem, really, it needs console hands-on to revive every time.

    Last time it crashed (last week, before updating to 5.4-RELEASE, that
    system was a few weeks older on the RELENG_5_4 branch), it seems to have
    get stuck on dumping the core, can this be the problem:

    -------
    Fatal trap 12: page fault while in kernel mode
    cpuid = 0: apic id = 00
    fault virtual address = 0x00
    ...
    trap number = 12
    panic: page fault
    cpuid = 0
    boot() called on cpu#0
    Uptime: 1d23h50m36s
    Dumping 2047 MB
     16 32
    --------
    The cursor sits at the position after "32".

    Seems to me it fails to dump the core, can this be it? On previous crashes,
    before dumpdev was set, it would hang before that

    The machine is Dell 2850 w/ Perc raid, Dual CPUs, SMP with hyperthreading
    OFF in BIOS. Enclosing the KERNEL config, almost a GENERIC kernel. I can
    provide more info if required.

    So, in short, three question, really.

    - How can I get rid of the crashes? (heh)
    - How can I get the system to do unattended reboot when crashed?
    - How do I get a coredump?

    Any help appreciated.

    /Palle

    Diffing GENERIC vs KERNEL:

    --- GENERIC Tue Apr 12 15:57:01 2005
    +++ KERNEL Fri Apr 29 22:27:41 2005
    @@ -20,7 +20,9 @@

     machine amd64
     cpu HAMMER
    -ident GENERIC
    +ident KERNEL
    +
    +makeoptions DEBUG=-g

     # To statically compile in device wiring instead of /boot/device.hints
     #hints "GENERIC.hints" # Default places to look for
    devices.
    @@ -45,7 +47,7 @@
     options COMPAT_43 # Needed by COMPAT_LINUX32
     options COMPAT_IA32 # Compatible with i386 binaries
     options COMPAT_FREEBSD4 # Compatible with FreeBSD4
    -options COMPAT_LINUX32 # Compatible with i386 linux
    binaries
    +#options COMPAT_LINUX32 # Compatible with i386 linux
    binaries
     options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI
     options KTRACE # ktrace(1) support
     options SYSVSHM # SYSV-style shared memory
    @@ -64,10 +66,10 @@

     # Enabling NO_MIXED_MODE gives a performance improvement on some
    motherboards
     # but does not work with some boards (mostly nVidia chipset based).
    -#options NO_MIXED_MODE # Don't penalize working chipsets
    +options NO_MIXED_MODE # Don't penalize working chipsets

     # Linux 32-bit ABI support
    -options LINPROCFS # Cannot be a module yet.
    +#options LINPROCFS # Cannot be a module yet.

     # Bus support. Do not remove isa, even if you have no isa slots
     device acpi
    @@ -260,3 +262,19 @@
     device firewire # FireWire bus code
     device sbp # SCSI over FireWire (Requires scbus and
    da)
     device fwe # Ethernet over FireWire (non-standard!)
    +
    +# SMP
    +options SMP
    +
    +# SysV stuff
    +# This provides support for System V shared memory.
    +#
    +options SYSVSHM
    +options SYSVSEM
    +options SYSVMSG
    +options SHMMAXPGS=65536
    +options SEMMNI=40
    +options SEMMNS=240
    +options SEMUME=40
    +options SEMMNU=120

    
    
    
    

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"




  • Next message: Mipam: "Re: em and bge driver MPSAFE?"

    Relevant Pages

    • Re: Crash with recent kernel on wireless
      ... You should use the kernel image with the debugging symbols here. ... Dump Length: 190091264B ... pointer. ... Most of crashes even failed to save vmdump due to double faults. ...
      (freebsd-stable)
    • Re: Crash with recent kernel on wireless
      ... build and install a kernel, you get two kernel images on 7.x; ... Dump Length: 190091264B ... pointer. ... Most of crashes even failed to save vmdump due to double faults. ...
      (freebsd-stable)
    • Re: Crash with recent kernel on wireless
      ... You should use the kernel image with the debugging symbols here. ... Dump Length: 190091264B ... pointer. ... Most of crashes even failed to save vmdump due to double faults. ...
      (freebsd-stable)
    • system does not reboot after panic (Was: savecore: first and last dump headers disagree)
      ... > We have an amd64 system that still experiences crashes after installing ... > coredumps, but with latest versions of the kernel, savecore does not give ... > me a dump, instead it says: ... core next time. ...
      (freebsd-stable)
    • Re: Question About Kernal Dumps, system crashing
      ... It's interesting that all three crashes may have happened at the same time, ... After you set the minidump settings, it'll be interesting to see if a dump file is created at this time. ... if the sbs crashes again. ...
      (microsoft.public.windows.server.sbs)