On Tue, May 10, 2005 at 07:32:25PM -0700, Andrew Morton wrote:
>
> We have some kexec/kdump testers over on
> linux-kernel. Results: not good.
>
>
>
> Begin forwarded message:
>
> Date: Tue, 10 May 2005 21:11:31 +0800
> From: Coywolf Qi Hunt <[email protected]>
> To: Borislav Petkov <[email protected]>
> Cc: "Randy.Dunlap" <[email protected]>, Ralf Hildebrandt <[email protected]>, [email protected]
> Subject: Re: kexec?
>
>
> On 5/10/05, Borislav Petkov <[email protected]> wrote:
> > I've been doing some kexec tests (as described in Documentation/kdump.txt) too
> > but can't get to load the image and get similar error messages. Let me know
> > if you need more info about the hardware. The first_kernel was booted with
> > "crashkernel=64M@16M" and the 16M value was configured into the second during
> > kconfig in "Physical address where the kernel is loaded" as 0x1000000.
> >
> > [root@zmei]: kexec -p vmlinux --args-linux --append="root=/dev/hda1 maxcpus=1
> > init 1"
>
> kexec-tools-1.101 loads for me, but if cmdline is used, it hangs up
> after "Starting new kernel"
maxcpus=1 is the culprit. Even through bios/grub kernel does not boot with
option maxcpus=1. It is a known issue with got notieced 2.6.12-rc2-mm1 onwards.
So build second kernel as uniprocessor kernel and don't specify maxcpus=1 and
test it out. It should work.
Thanks
Vivek
> > > I've been doing some kexec tests (as described in Documentation/kdump.txt) too
> > > but can't get to load the image and get similar error messages. Let me know
> > > if you need more info about the hardware. The first_kernel was booted with
> > > "crashkernel=64M@16M" and the 16M value was configured into the second during
> > > kconfig in "Physical address where the kernel is loaded" as 0x1000000.
> > >
> > > [root@zmei]: kexec -p vmlinux --args-linux --append="root=/dev/hda1 maxcpus=1
> > > init 1"
> >
> > kexec-tools-1.101 loads for me, but if cmdline is used, it hangs up
> > after "Starting new kernel"
>
> maxcpus=1 is the culprit. Even through bios/grub kernel does not boot with
> option maxcpus=1. It is a known issue with got notieced 2.6.12-rc2-mm1 onwards.
> So build second kernel as uniprocessor kernel and don't specify maxcpus=1 and
> test it out. It should work.
>
Vivek,
kexec-tools-1.101 does not contain your last patch series (that includes
--crashdump which is lacking from the above cmdline). Currently you need
to patch up 1.101 with the stuff from
[RFC/PATCH 5/17][kexec-tools-1.101] Add command line option
"--crash-dump" etc.
It would be good having a 1.2 or something with the patches included on
the site...
> >
> > maxcpus=1 is the culprit. Even through bios/grub kernel does not boot with
> > option maxcpus=1. It is a known issue with got notieced 2.6.12-rc2-mm1 onwards.
> > So build second kernel as uniprocessor kernel and don't specify maxcpus=1 and
> > test it out. It should work.
> >
>
> Vivek,
>
> kexec-tools-1.101 does not contain your last patch series (that includes
> --crashdump which is lacking from the above cmdline). Currently you need
> to patch up 1.101 with the stuff from
> [RFC/PATCH 5/17][kexec-tools-1.101] Add command line option
> "--crash-dump" etc.
>
> It would be good having a 1.2 or something with the patches included on
> the site...
We have uploaded the kdump related user space patches which can be
accessed at following link.
http://lse.sourceforge.net/kdump/patches/
A single consolidated patch can be applied on top of kexec-tools-1.101.tar.gz
to get kdump working.
Thanks
Vivek
> > kexec-tools-1.101 does not contain your last patch series (that includes
> > --crashdump which is lacking from the above cmdline). Currently you need
> > to patch up 1.101 with the stuff from
> > [RFC/PATCH 5/17][kexec-tools-1.101] Add command line option
> > "--crash-dump" etc.
> >
> > It would be good having a 1.2 or something with the patches included on
> > the site...
>
> We have uploaded the kdump related user space patches which can be
> accessed at following link.
>
> http://lse.sourceforge.net/kdump/patches/
>
> A single consolidated patch can be applied on top of kexec-tools-1.101.tar.gz
> to get kdump working.
I had no idea this address existed, only when looking at my lkml-archive
i saw it posted this monday (!), prior to that I had not seen it and I
watch things quite closely.
How is anyone gonna try it out if it isn't announced and the proper
procedure of getting it going known? Randys recent kdump.txt update made
things alot clearer but it won't help finding the right source and
patches. Although personally I'd put up a complete tarball instead of a
patch so users/testers don't have to manually patch it up.
Also the latest kexec patches are at http://www.xmission.com/~ebiederm/files/kexec/
nowdays and not with Randy. And there is even more confusion to it as there is:
kexec-tools-1.101.tar.gz
kexec-tools-1.99.tar.gz
I don't know about you but if I didn't know i'd definately go with the 1.99 one
even if 1.101 is the latest version.
Index: mm/Documentation/kdump.txt
===================================================================
--- mm.orig/Documentation/kdump.txt 2005-05-06 08:55:43.000000000 +0200
+++ mm/Documentation/kdump.txt 2005-05-11 10:16:38.000000000 +0200
@@ -35,7 +35,9 @@
SETUP
=====
-1) Download and build the appropriate version of kexec-tools.
+1) Download http://www.xmission.com/~ebiederm/files/kexec/kexec-tools-1.101.tar.gz
+ and apply http://lse.sourceforge.net/kdump/patches/kexec-tools-1.101-kdump.patch
+ and after that build the source.
2) Download and build the appropriate (latest) kexec/kdump (-mm) kernel
patchset and apply it to the vanilla kernel tree.
Index: mm/MAINTAINERS
===================================================================
--- mm.orig/MAINTAINERS 2005-05-06 08:55:57.000000000 +0200
+++ mm/MAINTAINERS 2005-05-11 10:24:35.000000000 +0200
@@ -1339,7 +1339,6 @@
M: [email protected]
M: [email protected]
W: http://www.xmission.com/~ebiederm/files/kexec/
-W: http://developer.osdl.org/rddunlap/kexec/
L: [email protected]
L: [email protected]
S: Maintained
On Wed, May 11, 2005 at 10:30:28AM +0200, Alexander Nyberg wrote:
> > > kexec-tools-1.101 does not contain your last patch series (that includes
> > > --crashdump which is lacking from the above cmdline). Currently you need
> > > to patch up 1.101 with the stuff from
> > > [RFC/PATCH 5/17][kexec-tools-1.101] Add command line option
> > > "--crash-dump" etc.
> > >
> > > It would be good having a 1.2 or something with the patches included on
> > > the site...
> >
> > We have uploaded the kdump related user space patches which can be
> > accessed at following link.
> >
> > http://lse.sourceforge.net/kdump/patches/
> >
> > A single consolidated patch can be applied on top of kexec-tools-1.101.tar.gz
> > to get kdump working.
>
> I had no idea this address existed, only when looking at my lkml-archive
> i saw it posted this monday (!), prior to that I had not seen it and I
> watch things quite closely.
Yes, you are right. Earlier the kexec-tools patches implementing kdump
were just posted on mailing lists but now they are on the mentioned site.
> How is anyone gonna try it out if it isn't announced and the proper
> procedure of getting it going known? Randys recent kdump.txt update made
> things alot clearer but it won't help finding the right source and
> patches. Although personally I'd put up a complete tarball instead of a
> patch so users/testers don't have to manually patch it up.
>
> Also the latest kexec patches are at http://www.xmission.com/~ebiederm/files/kexec/
> nowdays and not with Randy. And there is even more confusion to it as there is:
> kexec-tools-1.101.tar.gz
> kexec-tools-1.99.tar.gz
>
> I don't know about you but if I didn't know i'd definately go with the 1.99 one
> even if 1.101 is the latest version.
>
You are right again and your patch for kdump.txt should clarify the confusions. Thanks for the patch.
Andrew,
Please include the following kdump.txt patch.
Thanks
Vivek
> Index: mm/Documentation/kdump.txt
> ===================================================================
> --- mm.orig/Documentation/kdump.txt 2005-05-06 08:55:43.000000000 +0200
> +++ mm/Documentation/kdump.txt 2005-05-11 10:16:38.000000000 +0200
> @@ -35,7 +35,9 @@
> SETUP
> =====
>
> -1) Download and build the appropriate version of kexec-tools.
> +1) Download http://www.xmission.com/~ebiederm/files/kexec/kexec-tools-1.101.tar.gz
> + and apply http://lse.sourceforge.net/kdump/patches/kexec-tools-1.101-kdump.patch
> + and after that build the source.
>
> 2) Download and build the appropriate (latest) kexec/kdump (-mm) kernel
> patchset and apply it to the vanilla kernel tree.
> Index: mm/MAINTAINERS
> ===================================================================
> --- mm.orig/MAINTAINERS 2005-05-06 08:55:57.000000000 +0200
> +++ mm/MAINTAINERS 2005-05-11 10:24:35.000000000 +0200
> @@ -1339,7 +1339,6 @@
> M: [email protected]
> M: [email protected]
> W: http://www.xmission.com/~ebiederm/files/kexec/
> -W: http://developer.osdl.org/rddunlap/kexec/
> L: [email protected]
> L: [email protected]
> S: Maintained
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
Hi John,
The kexec directory at
http://developer.osdl.org/rddunlap/kexec/
is confusing people and hasn't been updated in ages.
Please nuke it...
Thanks,
~Randy
On Wed, 11 May 2005 10:30:28 +0200 Alexander Nyberg wrote:
| > > kexec-tools-1.101 does not contain your last patch series (that includes
| > > --crashdump which is lacking from the above cmdline). Currently you need
| > > to patch up 1.101 with the stuff from
| > > [RFC/PATCH 5/17][kexec-tools-1.101] Add command line option
| > > "--crash-dump" etc.
| > >
| > > It would be good having a 1.2 or something with the patches included on
| > > the site...
| >
| > We have uploaded the kdump related user space patches which can be
| > accessed at following link.
| >
| > http://lse.sourceforge.net/kdump/patches/
| >
| > A single consolidated patch can be applied on top of kexec-tools-1.101.tar.gz
| > to get kdump working.
|
| I had no idea this address existed, only when looking at my lkml-archive
| i saw it posted this monday (!), prior to that I had not seen it and I
| watch things quite closely.
|
| How is anyone gonna try it out if it isn't announced and the proper
| procedure of getting it going known? Randys recent kdump.txt update made
| things alot clearer but it won't help finding the right source and
| patches. Although personally I'd put up a complete tarball instead of a
| patch so users/testers don't have to manually patch it up.
|
| Also the latest kexec patches are at http://www.xmission.com/~ebiederm/files/kexec/
| nowdays and not with Randy. And there is even more confusion to it as there is:
| kexec-tools-1.101.tar.gz
| kexec-tools-1.99.tar.gz
|
| I don't know about you but if I didn't know i'd definately go with the 1.99 one
| even if 1.101 is the latest version.
|
| Index: mm/Documentation/kdump.txt
| ===================================================================
| --- mm.orig/Documentation/kdump.txt 2005-05-06 08:55:43.000000000 +0200
| +++ mm/Documentation/kdump.txt 2005-05-11 10:16:38.000000000 +0200
| @@ -35,7 +35,9 @@
| SETUP
| =====
|
| -1) Download and build the appropriate version of kexec-tools.
| +1) Download http://www.xmission.com/~ebiederm/files/kexec/kexec-tools-1.101.tar.gz
| + and apply http://lse.sourceforge.net/kdump/patches/kexec-tools-1.101-kdump.patch
| + and after that build the source.
|
| 2) Download and build the appropriate (latest) kexec/kdump (-mm) kernel
| patchset and apply it to the vanilla kernel tree.
| Index: mm/MAINTAINERS
| ===================================================================
| --- mm.orig/MAINTAINERS 2005-05-06 08:55:57.000000000 +0200
| +++ mm/MAINTAINERS 2005-05-11 10:24:35.000000000 +0200
| @@ -1339,7 +1339,6 @@
| M: [email protected]
| M: [email protected]
| W: http://www.xmission.com/~ebiederm/files/kexec/
| -W: http://developer.osdl.org/rddunlap/kexec/
| L: [email protected]
| L: [email protected]
| S: Maintained