On 10/27/14 at 11:31am, Michael Holzheu wrote:
Dave Young <dyoung(a)redhat.com> wrote on 10/27/2014 09:26:11:
> > 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
> > 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
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
IMHO, this has to be documented in the official RHEL (kdump/dasd)
We will modify the howto.