Propose for Several Dump types

From: Jun Su (csujun_at_gmail.com)
Date: 12/14/04

  • Next message: Poul-Henning Kamp: "Re: Propose for Several Dump types" 
    Date: Tue, 14 Dec 2004 15:43:37 +0800
To: arch@freebsd.org

    Backgroud
    ========
    Many modern server machines have over 4G, even 16G memory. Full Memory
    Dump is nightmare for them. In the Linux world, there is a project
    named LKD that support several dump methods. In Windows, it also
    supports MiniDump, KernelOnlyDump and FullDump.

    In our use base, many users can only report the call-stack to the
    newsgroup. For these users, a MiniDump can severve them very well.
    Most important message can be generagte at the dumptime and save into
    dump file.

    For the limitation of our current kgdb, we can not trace the stack
    into user memory space. In this scenerio, a KernelOnly dump contains
    the informaiton that we can used. And in most panic scenerio, VM
    system is not the root cause and its data structure are very well. It
    is not so risky to rely on the data of VM subsystem. And we can even
    create a method to check if the VM subsystem is in a good state before
    we did KernelOnlyDump.

    Kernel-Only Dump
    ==============
    We now can use /dev/kmem as the core file. If we can generate a dump file with
    the same information with it, then we can enable kernel-only dump with
    very limit code changes.

    1. Change KVM library to support a new type of file that only contains
    kernel memory.
    2. Change kernel side to write only kernel memory when dumping.
    3. Change dumpon utility to do the right checking on the partiction size.

    MiniDump
    =======
    In a minidump, Register info, plus the crash stack is enough.

    New Dump MI interface
    =================
    There is only dumpsys method as the MI interface for the dump system.
    And if we look at the implementation of AMD, x86, Alpha, we will find
    they are very similiar.
    We need revise this interface when importing these new feature in.

    I post this in order to get some feedback and thinking about this idea.

    Thanks,

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

  • Next message: Poul-Henning Kamp: "Re: Propose for Several Dump types"

    Relevant Pages

    • Kernel panic. Unsure of cause.
      ... Unread portion of the kernel message buffer: ... page fault while in kernel mode ... Physical memory: 3058 MB ... Dump Length: 326086656B ...
      (freebsd-questions)
    • [RFC] [PATCH 1/2] s390: SCSI dump kernel and userspace application
      ... Kernel part of the s390 SCSI dumper: ... +s390 SCSI dump tool (zfcpdump) ... +hardware saves some memory plus the register sets of the boot cpu before the ...
      (Linux-Kernel)
    • Daily Report #4852
      ... Verify Guide Star Acquisition with Continuing FGSs ... Load and Dump Onboard Memory ... At the beginning of each test, the attitude control law ...
      (sci.astro.hubble)
    • [PATCH] Documentation update for kdump
      ... We have updated much of the document to reflect the current state of kdump and reformatted the document for readability. ... -Kdump uses kexec to reboot to a second kernel whenever a dump needs to be ... This second kernel is booted with very little memory. ...
      (Linux-Kernel)
    • Problems installing 5.1A on XP1000
      ... The drive I'm attempting an install to is an IBM ... 640 MBytes of System Memory ... isa0 at pci0 ... DUMP: Warning: no disk available for dump. ...
      (Tru64-UNIX-Managers)