From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org, linux-ia64@vger.kernel.org
Cc: Terry Loftin <terry.loftin@hp.com>, Khalid Aziz <khalid_aziz@hp.com>
Subject: [IA64] [kdump] machveg=dig on hpzx1 platforms
Date: Thu, 21 Jun 2007 20:24:41 +0200 [thread overview]
Message-ID: <20070621182441.GA21840@suse.de> (raw)
Hello,
on most HP machines, the 'machveg=dig' parameter is needed for the
kdump kernel to avoid problems with the HP ioc. In the original kdump
patches, a function ioc_iova_disable() was used, which (as I
understand) disabled the IOC before executing the new kernel. However,
that function wasn't added to mainline [2].
However, with a 2.6.22-rc kernel, booting into the kdump kernel works
surprisingly. I haven't found a fix in the git history that could be
responsible. Was there a fix? Or is it just a random result on a
machine I tested that it works?
Are there any plans to bring back ioc_iova_disable(), or would some
automatic kernel code that uses machvec=dig in the kernel without
forcing the user to pass an additional command line work?
Thanks,
Bernhard
[1] http://article.gmane.org/gmane.linux.ports.ia64/15192
[2] http://article.gmane.org/gmane.linux.ports.ia64/15147
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org, linux-ia64@vger.kernel.org
Cc: Terry Loftin <terry.loftin@hp.com>, Khalid Aziz <khalid_aziz@hp.com>
Subject: [IA64] [kdump] machveg=dig on hpzx1 platforms
Date: Thu, 21 Jun 2007 18:24:41 +0000 [thread overview]
Message-ID: <20070621182441.GA21840@suse.de> (raw)
Hello,
on most HP machines, the 'machveg=dig' parameter is needed for the
kdump kernel to avoid problems with the HP ioc. In the original kdump
patches, a function ioc_iova_disable() was used, which (as I
understand) disabled the IOC before executing the new kernel. However,
that function wasn't added to mainline [2].
However, with a 2.6.22-rc kernel, booting into the kdump kernel works
surprisingly. I haven't found a fix in the git history that could be
responsible. Was there a fix? Or is it just a random result on a
machine I tested that it works?
Are there any plans to bring back ioc_iova_disable(), or would some
automatic kernel code that uses machvec=dig in the kernel without
forcing the user to pass an additional command line work?
Thanks,
Bernhard
[1] http://article.gmane.org/gmane.linux.ports.ia64/15192
[2] http://article.gmane.org/gmane.linux.ports.ia64/15147
next reply other threads:[~2007-06-21 18:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 18:24 Bernhard Walle [this message]
2007-06-21 18:24 ` [IA64] [kdump] machveg=dig on hpzx1 platforms Bernhard Walle
2007-06-21 20:41 ` Terry Loftin
2007-06-21 20:41 ` Terry Loftin
2007-06-22 9:41 ` Bernhard Walle
2007-06-22 9:41 ` Bernhard Walle
2007-06-26 4:28 ` Milton Miller
2007-07-05 15:39 ` Prarit Bhargava
2007-07-05 15:39 ` Prarit Bhargava
2007-07-11 20:34 ` Luck, Tony
2007-07-11 20:34 ` Luck, Tony
2007-07-12 17:33 ` Terry Loftin
2007-07-12 17:33 ` Terry Loftin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070621182441.GA21840@suse.de \
--to=bwalle@suse.de \
--cc=kexec@lists.infradead.org \
--cc=khalid_aziz@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=terry.loftin@hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.