Some one has no idea how the kdump brings up the devices during the 2nd kernel boots.
The initramfs contains the copy of /etc/dasd.conf, and the kernel will bring up devices which specify in the /etc/dasd.conf.
Signed-off-by: Minfei Huang mhuang@redhat.com --- kexec-kdump-howto.txt | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt index 5582e40..0fd2a41 100644 --- a/kexec-kdump-howto.txt +++ b/kexec-kdump-howto.txt @@ -245,6 +245,11 @@ the Blade Management Console. Select the corresponding blade for which you want to initate the dump and then click "Restart blade with NMI". This issues a system reset and invokes xmon debugger.
+6) System-z specific methods: + +Specify the device option in the /etc/dasd.conf to bring up the device which +you want during the kernel boots. +
Advanced Setups:
On 10/27/14 at 03:43pm, Minfei Huang wrote:
Some one has no idea how the kdump brings up the devices during the 2nd kernel boots.
The initramfs contains the copy of /etc/dasd.conf, and the kernel will bring up devices which specify in the /etc/dasd.conf.
Signed-off-by: Minfei Huang mhuang@redhat.com
kexec-kdump-howto.txt | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt index 5582e40..0fd2a41 100644 --- a/kexec-kdump-howto.txt +++ b/kexec-kdump-howto.txt @@ -245,6 +245,11 @@ the Blade Management Console. Select the corresponding blade for which you want to initate the dump and then click "Restart blade with NMI". This issues a system reset and invokes xmon debugger.
+6) System-z specific methods:
For architecture name under linux maybe "s390x" should be better, even for IBM they specify it as "System z" without the dash.
+Specify the device option in the /etc/dasd.conf to bring up the device which +you want during the kernel boots.
Ccing Michael for his comments about lines.
Thanks Dave
Dave Young dyoung@redhat.com wrote on 10/27/2014 09:26:11: [snip]
Some one has no idea how the kdump brings up the devices during the 2nd kernel boots.
The initramfs contains the copy of /etc/dasd.conf, and the kernel will bring up devices which specify in the /etc/dasd.conf.
Signed-off-by: Minfei Huang mhuang@redhat.com
kexec-kdump-howto.txt | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt index 5582e40..0fd2a41 100644 --- a/kexec-kdump-howto.txt +++ b/kexec-kdump-howto.txt @@ -245,6 +245,11 @@ the Blade Management Console. Select the
corresponding blade for which you want
to initate the dump and then click "Restart blade with NMI". This
issues a
system reset and invokes xmon debugger.
+6) System-z specific methods:
For architecture name under linux maybe "s390x" should be better, even for IBM they specify it as "System z" without the dash.
You are right the spelling is "System z" without the dash. Or also s390x or s390 might be ok, if this is your standard term for mainframe online documentation.
+Specify the device option in the /etc/dasd.conf to bring up the
device which
+you want during the kernel boots.
I assume that this is related to bugzillas 1145315 (RHEL6) / 1151895 (RHEL7), correct?
Shouldn't the text be something like:
You have to specify all required DASDs for your kdump configuration in the /etc/dasd.conf file.
Besides of that I think it is not sufficient to document this in kexec-kdump-howto.txt.
IMHO, this has to be documented in the official RHEL (kdump/dasd) documentation.
Michael
On 10/27/14 at 11:31am, Michael Holzheu wrote:
Dave Young dyoung@redhat.com wrote on 10/27/2014 09:26:11: [snip]
Some one has no idea how the kdump brings up the devices during the 2nd kernel boots.
The initramfs contains the copy of /etc/dasd.conf, and the kernel will bring up devices which specify in the /etc/dasd.conf.
Signed-off-by: Minfei Huang mhuang@redhat.com
kexec-kdump-howto.txt | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt index 5582e40..0fd2a41 100644 --- a/kexec-kdump-howto.txt +++ b/kexec-kdump-howto.txt @@ -245,6 +245,11 @@ the Blade Management Console. Select the
corresponding blade for which you want
to initate the dump and then click "Restart blade with NMI". This
issues a
system reset and invokes xmon debugger.
+6) System-z specific methods:
For architecture name under linux maybe "s390x" should be better, even for IBM they specify it as "System z" without the dash.
You are right the spelling is "System z" without the dash. Or also s390x or s390 might be ok, if this is your standard term for mainframe online documentation.
+Specify the device option in the /etc/dasd.conf to bring up the
device which
+you want during the kernel boots.
I assume that this is related to bugzillas 1145315 (RHEL6) / 1151895 (RHEL7), correct?
Shouldn't the text be something like:
You have to specify all required DASDs for your kdump configuration in the /etc/dasd.conf file.
Besides of that I think it is not sufficient to document this in kexec-kdump-howto.txt.
IMHO, this has to be documented in the official RHEL (kdump/dasd) documentation.
Thanks Michael.
We will modify the howto.
Michael
Minfei Huang mhuang@redhat.com wrote on 10/27/2014 11:40:58:
From: Minfei Huang mhuang@redhat.com To: Michael Holzheu/Germany/IBM@IBMDE, Cc: Dave Young dyoung@redhat.com, kexec@lists.fedoraproject.org, Michael Veigel/Germany/Contr/IBM@IBMDE Date: 10/27/2014 11:41 Subject: Re: [PATCH] kexec-kdump-howto: Add the instruction of the dasd on System-z
On 10/27/14 at 11:31am, Michael Holzheu wrote:
Dave Young dyoung@redhat.com wrote on 10/27/2014 09:26:11: [snip]
Some one has no idea how the kdump brings up the devices during the
2nd
kernel boots.
The initramfs contains the copy of /etc/dasd.conf, and the kernel will bring up devices which specify in the /etc/dasd.conf.
Signed-off-by: Minfei Huang mhuang@redhat.com
kexec-kdump-howto.txt | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt index 5582e40..0fd2a41 100644 --- a/kexec-kdump-howto.txt +++ b/kexec-kdump-howto.txt @@ -245,6 +245,11 @@ the Blade Management Console. Select the
corresponding blade for which you want
to initate the dump and then click "Restart blade with NMI". This
issues a
system reset and invokes xmon debugger.
+6) System-z specific methods:
For architecture name under linux maybe "s390x" should be better, even for IBM they specify it as "System z" without the dash.
You are right the spelling is "System z" without the dash. Or also s390x or s390 might be ok, if this is your standard term for mainframe online documentation.
+Specify the device option in the /etc/dasd.conf to bring up the
device which
+you want during the kernel boots.
I assume that this is related to bugzillas 1145315 (RHEL6) / 1151895 (RHEL7), correct?
Shouldn't the text be something like:
You have to specify all required DASDs for your kdump configuration in the /etc/dasd.conf file.
Besides of that I think it is not sufficient to document this in kexec-kdump-howto.txt.
IMHO, this has to be documented in the official RHEL (kdump/dasd) documentation.
Thanks Michael.
We will modify the howto.
Ok, and what about the official documentation?
Michael
Hi, Michael
IMHO, this has to be documented in the official RHEL (kdump/dasd) documentation.
Do you perfer to document it in release notes? Or put it in crashdump guide?
If you want it in crashdump guide, I think we need change the component to "doc-Kernel_Crash_Dump_Guide"
In case release notes, we can document it in kdump howto and add the text in bugzilla field "Doc Text"
Thanks Dave
Dave Young dyoung@redhat.com wrote on 10/28/2014 03:27:37:
From: Dave Young dyoung@redhat.com To: Michael Holzheu/Germany/IBM@IBMDE, Cc: kexec@lists.fedoraproject.org, Minfei Huang mhuang@redhat.com, Michael Veigel/Germany/Contr/IBM@IBMDE Date: 10/28/2014 03:27 Subject: Re: [PATCH] kexec-kdump-howto: Add the instruction of the dasd on System-z
Hi, Michael
IMHO, this has to be documented in the official RHEL (kdump/dasd) documentation.
Do you perfer to document it in release notes? Or put it in crashdump
guide?
Hi Dave,
I think the correct place is the chapter "The kdump Crash Recovery Service" of your "Red Hat Enterprise Linux 6 Deployment Guide":
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/htm...
What do you think?
Michael
On 10/29/14 at 12:38pm, Michael Holzheu wrote:
Dave Young dyoung@redhat.com wrote on 10/28/2014 03:27:37:
From: Dave Young dyoung@redhat.com To: Michael Holzheu/Germany/IBM@IBMDE, Cc: kexec@lists.fedoraproject.org, Minfei Huang mhuang@redhat.com, Michael Veigel/Germany/Contr/IBM@IBMDE Date: 10/28/2014 03:27 Subject: Re: [PATCH] kexec-kdump-howto: Add the instruction of the dasd on System-z
Hi, Michael
IMHO, this has to be documented in the official RHEL (kdump/dasd) documentation.
Do you perfer to document it in release notes? Or put it in crashdump
guide?
Hi Dave,
I think the correct place is the chapter "The kdump Crash Recovery Service" of your "Red Hat Enterprise Linux 6 Deployment Guide":
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/htm...
What do you think?
I'm fine with it, I change the bug to component "doc-Deployment_Guide"
Thanks Dave
-
Dave Young -
Michael Holzheu -
Minfei Huang