All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com>
Cc: "parisc-linux@lists.parisc-linux.org"
	<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] vmlinux header for savecrash.
Date: Tue, 22 Jan 2002 11:34:04 -0700	[thread overview]
Message-ID: <20020122183404.4F8234830@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com> of "Tue, 22 Jan 2002 18:55:31 +0100." <3C4DA793.B17F1D3C@admin.france.hp.com>

Bruno Vidal wrote:
> 	Hi
> I don't know how to retrieve option pass to the kernel,
> but give me some clue, and I'll add this information in
> the dump header asap, because it is a really good idea :-)

(credit: Randolph brought it up first)

Look at arch/parisc/kernel/setup.c:setup_cmdline().
We can add pretty much anything we need here.

It just occurred to me that the source media (ie network, disk)
needs to be identified as well.
Is the vmlinux/System.map required to be on the root file system?
Would it be reasonble if savecrash told the user that /boot/vmlinux
wasn't the matching kernel and where to put the right vmlinux/System.map?

Allowing users to drop the right kernel in place *after* the
crash dump was recovered seems reasonable thing to do.
Someone might want to move the crash dump to a bigger/faster
system to do the actual analysis.

grant

  parent reply	other threads:[~2002-01-22 18:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21 17:45 [parisc-linux] vmlinux header for savecrash Bruno Vidal
2002-01-21 20:25 ` Grant Grundler
2002-01-22  9:20   ` Bruno Vidal
2002-01-22  9:55     ` Enrik Berkhan
2002-01-22 12:25       ` Bruno Vidal
2002-01-22 15:11         ` Enrik Berkhan
2002-01-22 15:13         ` Matthew Wilcox
2002-01-22 12:05     ` James P. Kinney III
2002-01-22 17:45     ` Grant Grundler
2002-01-22 17:53       ` Randolph Chung
2002-01-22 17:59         ` Bruno Vidal
2002-01-22 17:55       ` Bruno Vidal
2002-01-22 18:11         ` Randolph Chung
2002-01-22 18:34         ` Grant Grundler [this message]
2002-01-22  0:43 ` James P. Kinney III
  -- strict thread matches above, loose matches on Subject: below --
2002-01-07  2:58 [parisc-linux] installation problems on an A500 Matthias Klose
2002-01-07  3:46 ` Grant Grundler
2002-01-22 19:59   ` [parisc-linux] vmlinux header for savecrash Paul Bame
2002-01-23  2:13     ` Grant Grundler
2002-01-23 10:23       ` Andreas Deresch
2002-01-25  6:30         ` Grant Grundler
2002-01-23  8:57     ` Enrik Berkhan
2002-01-23  9:29       ` phi 4369

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020122183404.4F8234830@dsl2.external.hp.com \
    --to=grundler@dsl2.external.hp.com \
    --cc=bruno_vidal@hpfrcu03.france.hp.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.