On Wednesday 10 May 2017 08:28 PM, Michal Suchánek wrote:
On Wed, 3 May 2017 12:43:33 +0530
Hari Bathini wrote:
On Tuesday 02 May 2017 09:26 PM, Michal Suchanek wrote:
With fadump (dump capture) kernel booting like a regular kernel, it
almost needs the same amount of memory to boot as the p
On Wed, 3 May 2017 12:43:33 +0530
Hari Bathini wrote:
> On Tuesday 02 May 2017 09:26 PM, Michal Suchanek wrote:
> > With fadump (dump capture) kernel booting like a regular kernel, it
> > almost needs the same amount of memory to boot as the production
> > kernel, which is unwarranted for a dump
On Wednesday 03 May 2017 12:43 PM, Hari Bathini wrote:
On Tuesday 02 May 2017 09:26 PM, Michal Suchanek wrote:
With fadump (dump capture) kernel booting like a regular kernel, it
almost
needs the same amount of memory to boot as the production kernel,
which is
unwarranted for a dump capture
On Tuesday 02 May 2017 09:26 PM, Michal Suchanek wrote:
With fadump (dump capture) kernel booting like a regular kernel, it almost
needs the same amount of memory to boot as the production kernel, which is
unwarranted for a dump capture kernel. But with no option to disable some
of the unnecess
Hi Michal,
On Tuesday 02 May 2017 09:26 PM, Michal Suchanek wrote:
With fadump (dump capture) kernel booting like a regular kernel, it almost
needs the same amount of memory to boot as the production kernel, which is
unwarranted for a dump capture kernel. But with no option to disable some
of t
With fadump (dump capture) kernel booting like a regular kernel, it almost
needs the same amount of memory to boot as the production kernel, which is
unwarranted for a dump capture kernel. But with no option to disable some
of the unnecessary subsystems in fadump kernel, that much memory is wasted
6 matches
Mail list logo