From: Borislav Petkov <bp@suse.de>
To: "Chen, Rong A" <rong.a.chen@intel.com>
Cc: x86@kernel.org, Kairui Song <kasong@redhat.com>,
Baoquan He <bhe@redhat.com>, Dave Young <dyoung@redhat.com>,
Chao Fan <fanc.fnst@cn.fujitsu.com>,
kexec@lists.infradead.org,
Jun'ichi Nomura <j-nomura@ce.jp.nec.com>,
lkp@01.org
Subject: Re: [LKP] [x86/boot] 5b51ae969e: kexec boot failed
Date: Mon, 5 Aug 2019 15:02:21 +0200 [thread overview]
Message-ID: <20190805130221.GA18887@zn.tnic> (raw)
In-Reply-To: <0f817336-2d87-2110-13c0-e0a417d70e90@intel.com>
On Mon, Aug 05, 2019 at 07:49:54PM +0800, Chen, Rong A wrote:
> We use the following command to boot a new kernel:
> kexec --noefi -l /opt/rootfs/tmp/pkg/linux/x86_64-rhel-7.6/gcc-7/5b51ae969e3d8ab0134ee3c98a769ad6d2cc2e24/vmlinuz-5.2.0-rc3-00004-g5b51ae969e3d8a
> --initrd=/opt/rootfs/tmp/initrd-concatenated
And this "concatenated" initrd, how do you generate that?
FWIW, trying this in a vm doesn't seem to work because of EFI even though
--noefi is supplied on the cmdline:
$ kexec --noefi -l /mnt/tmp/bzImage
Unknown type (Reserved) while parsing /sys/firmware/memmap/5/type. Please report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/1/type. Please report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/6/type. Please report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/4/type. Please report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/2/type. Please report this as bug. Using RANGE_RESERVED now.
I need to try it on a real box.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nürnberg)
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@suse.de>
To: lkp@lists.01.org
Subject: Re: [x86/boot] 5b51ae969e: kexec boot failed
Date: Mon, 05 Aug 2019 15:02:21 +0200 [thread overview]
Message-ID: <20190805130221.GA18887@zn.tnic> (raw)
In-Reply-To: <0f817336-2d87-2110-13c0-e0a417d70e90@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
On Mon, Aug 05, 2019 at 07:49:54PM +0800, Chen, Rong A wrote:
> We use the following command to boot a new kernel:
> kexec --noefi -l /opt/rootfs/tmp/pkg/linux/x86_64-rhel-7.6/gcc-7/5b51ae969e3d8ab0134ee3c98a769ad6d2cc2e24/vmlinuz-5.2.0-rc3-00004-g5b51ae969e3d8a
> --initrd=/opt/rootfs/tmp/initrd-concatenated
And this "concatenated" initrd, how do you generate that?
FWIW, trying this in a vm doesn't seem to work because of EFI even though
--noefi is supplied on the cmdline:
$ kexec --noefi -l /mnt/tmp/bzImage
Unknown type (Reserved) while parsing /sys/firmware/memmap/5/type. Please report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/1/type. Please report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/6/type. Please report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/4/type. Please report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/2/type. Please report this as bug. Using RANGE_RESERVED now.
I need to try it on a real box.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2019-08-05 13:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 7:48 [x86/boot] 5b51ae969e: kexec boot failed kernel test robot
2019-08-02 7:48 ` kernel test robot
2019-08-02 7:59 ` Dave Young
2019-08-02 7:59 ` Dave Young
2019-08-05 11:46 ` Chen, Rong A
2019-08-05 11:46 ` Chen, Rong A
2019-08-02 9:30 ` Borislav Petkov
2019-08-02 9:30 ` Borislav Petkov
2019-08-05 11:49 ` [LKP] " Chen, Rong A
2019-08-05 11:49 ` Chen, Rong A
2019-08-05 13:02 ` Borislav Petkov [this message]
2019-08-05 13:02 ` Borislav Petkov
2019-08-05 13:32 ` [LKP] " Borislav Petkov
2019-08-05 13:32 ` Borislav Petkov
2019-08-12 7:43 ` [LKP] " Rong Chen
2019-08-12 7:43 ` Rong Chen
2019-08-12 8:17 ` [LKP] " Rong Chen
2019-08-12 8:17 ` Rong Chen
2019-08-12 9:35 ` [LKP] " Borislav Petkov
2019-08-12 9:35 ` Borislav Petkov
2019-08-13 9:17 ` [LKP] " Rong Chen
2019-08-13 9:17 ` Rong Chen
2019-08-13 13:42 ` [LKP] " Borislav Petkov
2019-08-13 13:42 ` Borislav Petkov
2019-08-06 8:56 ` [LKP] " Dave Young
2019-08-06 8:56 ` Dave Young
2019-08-06 8:45 ` [LKP] " Dave Young
2019-08-06 8:45 ` Dave Young
2019-08-12 7:49 ` [LKP] " Rong Chen
2019-08-12 7:49 ` Rong Chen
2019-08-14 2:43 ` [LKP] " Dave Young
2019-08-14 2:43 ` Dave Young
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=20190805130221.GA18887@zn.tnic \
--to=bp@suse.de \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=fanc.fnst@cn.fujitsu.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=kasong@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=lkp@01.org \
--cc=rong.a.chen@intel.com \
--cc=x86@kernel.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.