Skip to content

Commit

Permalink
---
Browse files Browse the repository at this point in the history
yaml
---
r: 47911
b: refs/heads/master
c: 473e66f
h: refs/heads/master
i:
  47909: f1eb3a9
  47907: 10610db
  47903: 3213de8
v: v3
  • Loading branch information
Horms authored and Linus Torvalds committed Feb 12, 2007
1 parent 67307ac commit 2640dd5
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion [refs]
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
---
refs/heads/master: be6b026785414033aac36887cb9ea0ee1244254c
refs/heads/master: 473e66fd24a230e03f6f164913bedb81c0ba052a
8 changes: 4 additions & 4 deletions trunk/Documentation/kdump/kdump.txt
Original file line number Diff line number Diff line change
Expand Up @@ -311,10 +311,10 @@ Following are the arch specific command line options to be used while
loading dump-capture kernel.

For i386, x86_64 and ia64:
"init 1 irqpoll maxcpus=1"
"1 irqpoll maxcpus=1"

For ppc64:
"init 1 maxcpus=1 noirqdistrib"
"1 maxcpus=1 noirqdistrib"


Notes on loading the dump-capture kernel:
Expand All @@ -332,8 +332,8 @@ Notes on loading the dump-capture kernel:
* You must specify <root-dev> in the format corresponding to the root
device name in the output of mount command.

* "init 1" boots the dump-capture kernel into single-user mode without
networking. If you want networking, use "init 3."
* Boot parameter "1" boots the dump-capture kernel into single-user
mode without networking. If you want networking, use "3".

* 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
Expand Down

0 comments on commit 2640dd5

Please sign in to comment.