openkylin
/
linux
mirror of https://gitee.com/openkylin/linux.git
9
0
Fork 0
Code Issues Projects Releases Wiki Activity

[PATCH] kexec: fix references to init in documentation for kexec 

I've noticed that the boot options are not correct for in the documentation
for kdump.  The "init" keyword is not necessary, and causes a kernel panic
when booting with an initrd on Fedora 5.

[horms@verge.net.au: put original comment with the latest version of the patch]
Signed-off-by: Judith Lebzeelter <judith@osdl.org>
Acked-by: Vivek Goyal <vgoyal@in.ibm.com>
Signed-off-by: Simon Horman <horms@verge.net.au>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
Horms 2007-02-12 00:52:18 -08:00 committed by Linus Torvalds
parent be6b026785
commit 473e66fd24
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/kdump/kdump.txt
View File

@ -311,10 +311,10 @@ Following are the arch specific command line options to be used while
loading dump-capture kernel. loading dump-capture kernel.
For i386, x86_64 and ia64: For i386, x86_64 and ia64:
"init 1 irqpoll maxcpus=1" "1 irqpoll maxcpus=1"
For ppc64: For ppc64:
"init 1 maxcpus=1 noirqdistrib" "1 maxcpus=1 noirqdistrib"
Notes on loading the dump-capture kernel: Notes on loading the dump-capture kernel:
@ -332,8 +332,8 @@ Notes on loading the dump-capture kernel:
* You must specify <root-dev> in the format corresponding to the root * You must specify <root-dev> in the format corresponding to the root
device name in the output of mount command. device name in the output of mount command.
* "init 1" boots the dump-capture kernel into single-user mode without * Boot parameter "1" boots the dump-capture kernel into single-user
networking. If you want networking, use "init 3." mode without networking. If you want networking, use "3".
* We generally don' have to bring up a SMP kernel just to capture the * We generally don' have to bring up a SMP kernel just to capture the
dump. Hence generally it is useful either to build a UP dump-capture dump. Hence generally it is useful either to build a UP dump-capture