All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jlan@sgi.com>
To: kexec@lists.infradead.org, Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>
Subject: Re: [makedumpfile] config file -- OSRELEASE
Date: Tue, 29 May 2007 12:46:43 -0700	[thread overview]
Message-ID: <465C8323.7010009@sgi.com> (raw)
In-Reply-To: <20070529193058.GA4229@suse.de>

Bernhard Walle wrote:
> Hi,
> 
> is there any reason why the kernel version saved in the configuration
> file is the version of the running kernel and not the version for
> which the config file is for?

Yep, i figured that was my problem.
I copied my vmlinux, which is a 2.6.18-8.el5, to my disk server,
which is a 2.6.16.43-0.5-default.

I would think the OSRELEASE of the CONFIGFILE generated from
'makedumpfile -g CONFIGFILE -x VMLINUX' would be the version
of VMLINUX. Instead, it said: OSRELEASE=2.6.16.43-0.5-default,
which caused 'makedumpfile -i' to complain about:
   CONFIGFILE and VMCORE don't match

I think it is a bug? You would want to ensure the version of
the VMLINUX and VMCORE match.

> 
> It's a big problem because my plan was to ship the configuration files
> with the kernel RPMs in SLES. 

I love this idea!

Thanks,
 - jay


> However, we don't build the kernels on
> systems which run the kernel that is just built -- so that's not
> possible.
> 
> I think from implementation point of view it's not a problem, that's
> why I ask and didn't create a patch.
> 
> 
> Thanks,
>    Bernhard
> 


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2007-05-29 19:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 19:30 [makedumpfile] config file -- OSRELEASE Bernhard Walle
2007-05-29 19:46 ` Jay Lan [this message]
2007-05-30 11:13 ` Ken'ichi Ohmichi
2007-05-31  8:57   ` Bernhard Walle
2007-05-31 19:14     ` Eric W. Biederman
2007-06-01  9:07       ` Ken'ichi Ohmichi
2007-06-01  9:52         ` Bernhard Walle
2007-06-01 13:40           ` Eric W. Biederman
2007-06-01 13:48             ` Bernhard Walle

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=465C8323.7010009@sgi.com \
    --to=jlan@sgi.com \
    --cc=kexec@lists.infradead.org \
    --cc=oomichi@mxs.nes.nec.co.jp \
    /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.