Skip to contentSkip to conversation

the recommended crash memory reservation is too small for x86_64.

PATCH In review [email protected] 4 participants 5 messages Mar 25, 2013 – Mar 27, 2013

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 the recommended crash memory reservation is too small for x86_64.

From: root <root@zzy-Lenovo.(none)>

On Documentation/kdump/kdump.txt, section Boot into System Kernel: On x86 and x86_64, use "crashkernel=64M@16M", but some OSes like ubuntu 12.10 use ram fs larger than 64M, so in these cases the memory reserved for crashkernel should be at least 128M.

---
 Documentation/kdump/kdump.txt |    4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
Documentation/kdump/kdump.txt +3 -1
index 13f1aa0..1e850e0 100644
@@ -290,7 +290,9 @@ Boot into System Kernel
    "crashkernel=64M@16M" tells the system kernel to reserve 64 MB of memory
    starting at physical address 0x01000000 (16MB) for the dump-capture kernel.
 
-   On x86 and x86_64, use "crashkernel=64M@16M".
+   On x86 and x86_64, use "crashkernel=64M@16M" (some OSes use init ram fs larger
+than 64M, for example ubuntu-12.10, use crashkernel=128M@16M instead, or dump-capture
+kernel will out of memory).
 
    On ppc64, use "crashkernel=128M@32M".
 
Signature · 7 lines
1.7.10.4


_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
#1 lore raw
Quoted 6 lines · On 03/25/2013 06:56 PM, [email protected] wrote:

From: root <root@zzy-Lenovo.(none)>

On Documentation/kdump/kdump.txt, section Boot into System Kernel: On x86 and x86_64, use "crashkernel=64M@16M", but some OSes like ubuntu 12.10 use ram fs larger than 64M, so in these cases the memory reserved for crashkernel should be at least 128M.

People use different initramfs generators for different purpose. That means the size of initramfs and also its memory consuming can vary very much from each other. You just can't list all these generators and their recommended reserved memory here. Though I have to say crashkernel=128M is good choice.

I think it would be better to leave this to user or distribution itself to determine how much memory should be reserved for crash kernel, then export this value to kernel in some ways.

Thanks,
WANG Chao

Quoted 13 lines
---
 Documentation/kdump/kdump.txt |    4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
Documentation/kdump/kdump.txt +0 -0
index 13f1aa0..1e850e0 100644

Documentation/kdump/kdump.txt Boot into System Kernel · line 298

Quoted 10 lines
Documentation/kdump/kdump.txt +3 -1
@@ -290,7 +290,9 @@ Boot into System Kernel
    "crashkernel=64M@16M" tells the system kernel to reserve 64 MB of memory
    starting at physical address 0x01000000 (16MB) for the dump-capture kernel.
 
-   On x86 and x86_64, use "crashkernel=64M@16M".
+   On x86 and x86_64, use "crashkernel=64M@16M" (some OSes use init ram fs larger
+than 64M, for example ubuntu-12.10, use crashkernel=128M@16M instead, or dump-capture
+kernel will out of memory).
 
    On ppc64, use "crashkernel=128M@32M".
 

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#2 lore raw

Thanks for reviewing
Is it sounds good to add following line into section "Boot into System Kernel":

The memory reserved for crash kernel should be no less than the unpacked init ram disk size
that loaded with dump-capture kernel plus wired memory used by kernel itself.

#################
After all, I have been trapped into "hang after capture" problem when sticking strictly to this document.
Cheers
Zhouyi

Quoted 37 lines


 On 03/25/2013 06:56 PM, [email protected] wrote:
 > From: root <root@zzy-Lenovo.(none)>
 >
 >
 >  On Documentation/kdump/kdump.txt, section Boot into  System Kernel: On x86 and x86_64, use >  "crashkernel=64M@16M", but some OSes like ubuntu 12.10 use ram fs larger than 64M, so in these cases the >  memory reserved for crashkernel should be at least 128M.

 People use different initramfs generators for different purpose. That means
 the size of initramfs and also its memory consuming can vary very much from
 each other. You just can't list all these generators and their recommended
 reserved memory here. Though I have to say crashkernel=128M is good choice.

 I think it would be better to leave this to user or distribution itself to
 determine how much memory should be reserved for crash kernel, then export
 this value to kernel in some ways.

 Thanks,
 WANG Chao

 >
 >
 > Signed-off-by: Zhouyi Zhou <[email protected]>
 > ---
 >  Documentation/kdump/kdump.txt |    4 +++-
 >  1 file changed, 3 insertions(+), 1 deletion(-)
 >
 > diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
 > index 13f1aa0..1e850e0 100644
 > --- a/Documentation/kdump/kdump.txt
 > +++ b/Documentation/kdump/kdump.txt
 > @@ -290,7 +290,9 @@ Boot into System Kernel
 >     "crashkernel=64M@16M" tells the system kernel to reserve 64 MB of memory
 >     starting at physical address 0x01000000 (16MB) for the dump-capture kernel.
 >
 > -   On x86 and x86_64, use "crashkernel=64M@16M".

Quoted 8 lines

 > +   On x86 and x86_64, use "crashkernel=64M@16M" (some OSes use init ram fs larger > +than 64M, for example ubuntu-12.10, use crashkernel=128M@16M instead, or dump-capture > +kernel will out of memory).
 >
 >     On ppc64, use "crashkernel=128M@32M".
 >
 >

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#3 lore raw
Quoted 5 lines · 周洲仪

Thanks for reviewing
Is it sounds good to add following line into section "Boot into System Kernel":

The memory reserved for crash kernel should be no less than the unpacked init ram disk size
that loaded with dump-capture kernel plus wired memory used by kernel itself.

Sorry, that is just basic knowledge for everyone.

Quoted 55 lines

#################
After all, I have been trapped into "hang after capture" problem when sticking strictly to this document.
Cheers
Zhouyi

Quoted 45 lines · On 03/25/2013 06:56 PM, [email protected] wrote:
Quoted 6 lines

From: root <root@zzy-Lenovo.(none)>

On Documentation/kdump/kdump.txt, section Boot into System Kernel: On x86 and x86_64, use "crashkernel=64M@16M", but some OSes like ubuntu 12.10 use ram fs larger than 64M, so in these cases the memory reserved for crashkernel should be at least 128M.

People use different initramfs generators for different purpose. That means the size of initramfs and also its memory consuming can vary very much from each other. You just can't list all these generators and their recommended reserved memory here. Though I have to say crashkernel=128M is good choice.

I think it would be better to leave this to user or distribution itself to determine how much memory should be reserved for crash kernel, then export this value to kernel in some ways.

Thanks,
WANG Chao

Quoted 23 lines
---
 Documentation/kdump/kdump.txt |    4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
Documentation/kdump/kdump.txt +3 -1
index 13f1aa0..1e850e0 100644
@@ -290,7 +290,9 @@ Boot into System Kernel
    "crashkernel=64M@16M" tells the system kernel to reserve 64 MB of memory
    starting at physical address 0x01000000 (16MB) for the dump-capture kernel.
 
-   On x86 and x86_64, use "crashkernel=64M@16M".
+   On x86 and x86_64, use "crashkernel=64M@16M" (some OSes use init ram fs larger
+than 64M, for example ubuntu-12.10, use crashkernel=128M@16M instead, or dump-capture
+kernel will out of memory).
 
    On ppc64, use "crashkernel=128M@32M".
 

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#4 lore raw
In reply to [email protected]
Quoted 1 line · On Mon, Mar 25, 2013 at 06:56:49PM +0800, [email protected] wrote:

From: root <root@zzy-Lenovo.(none)>

The above line is bogus.

Quoted 3 lines

On Documentation/kdump/kdump.txt, section Boot into System Kernel: On x86 and x86_64, use "crashkernel=64M@16M", but some OSes like ubuntu 12.10 use ram fs larger than 64M, so in these cases the memory reserved for crashkernel should be at least 128M.

The above lines are way to wide. Something less than 80 columns is normal.

Quoted 10 lines
---
 Documentation/kdump/kdump.txt |    4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
Documentation/kdump/kdump.txt +0 -0
index 13f1aa0..1e850e0 100644

Documentation/kdump/kdump.txt Boot into System Kernel · line 295

Quoted 7 lines
Documentation/kdump/kdump.txt +3 -1
@@ -290,7 +290,9 @@ Boot into System Kernel
    "crashkernel=64M@16M" tells the system kernel to reserve 64 MB of memory
    starting at physical address 0x01000000 (16MB) for the dump-capture kernel.
 
-   On x86 and x86_64, use "crashkernel=64M@16M".
+   On x86 and x86_64, use "crashkernel=64M@16M" (some OSes use init ram fs larger
+than 64M, for example ubuntu-12.10, use crashkernel=128M@16M instead, or dump-capture
+kernel will out of memory).

I believe lines of kdmump.txt should also be 80 columns wide or less.

Quoted 11 lines
Documentation/kdump/kdump.txt +0 -0
    On ppc64, use "crashkernel=128M@32M".
 
Signature · 7 lines
1.7.10.4


_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec