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(a)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