On Wed, Oct 14, 2015 at 10:43:28AM +0200, Joerg Roedel wrote:
> Reviewed-by: Joerg Roedel
>
> The patch is also in SLES for some time now and was successfully tested
> there.
Thanks, I massaged it a bit and ended up applying this:
---
From: Baoquan He
Date: Thu, 24 Sep 2015 11:24:51 +0800
On Thu, Sep 24, 2015 at 11:24:51AM +0800, Baoquan He wrote:
> People reported that when allocating crashkernel memory using
> ",high" and ",low" syntax, there were cases where the reservation
> of the "high" portion succeeds, but the reservation of the "low"
> portion fails. Then kexec can load
Hi all,
Ping.
Any other suggestion for this fix?
On 09/24/15 at 11:24am, Baoquan He wrote:
> People reported that when allocating crashkernel memory using
> ",high" and ",low" syntax, there were cases where the reservation
> of the "high" portion succeeds, but the reservation of the "low"
>
Hi all,
Ping.
Any other suggestion for this fix?
On 09/24/15 at 11:24am, Baoquan He wrote:
> People reported that when allocating crashkernel memory using
> ",high" and ",low" syntax, there were cases where the reservation
> of the "high" portion succeeds, but the reservation of the "low"
>
On Thu, Sep 24, 2015 at 11:24:51AM +0800, Baoquan He wrote:
> People reported that when allocating crashkernel memory using
> ",high" and ",low" syntax, there were cases where the reservation
> of the "high" portion succeeds, but the reservation of the "low"
> portion fails. Then kexec can load
On Wed, Oct 14, 2015 at 10:43:28AM +0200, Joerg Roedel wrote:
> Reviewed-by: Joerg Roedel
>
> The patch is also in SLES for some time now and was successfully tested
> there.
Thanks, I massaged it a bit and ended up applying this:
---
From: Baoquan He
Date:
People reported that when allocating crashkernel memory using
",high" and ",low" syntax, there were cases where the reservation
of the "high" portion succeeds, but the reservation of the "low"
portion fails. Then kexec can load kdump kernel successfully, but
the boot of kdump kernel fails as
People reported that when allocating crashkernel memory using
",high" and ",low" syntax, there were cases where the reservation
of the "high" portion succeeds, but the reservation of the "low"
portion fails. Then kexec can load kdump kernel successfully, but
the boot of kdump kernel fails as
On 07/19/15 at 03:40pm, Borislav Petkov wrote:
> ...
>
> > @@ -552,7 +552,7 @@ static void __init reserve_crashkernel_low(void)
> > if (!auto_set)
> > pr_info("crashkernel low reservation failed - No
> > suitable area found.\n");
> >
> > - return;
> >
On Sun, Jul 19, 2015 at 07:07:44PM +0800, Baoquan He wrote:
> People reported that when allocating crashkernel memory using
> ",high" and ",low" syntax, there were cases where the reservation
> of the "high" portion succeeds, but the reservation of the "low"
> portion fails. Then kexec can load
People reported that when allocating crashkernel memory using
",high" and ",low" syntax, there were cases where the reservation
of the "high" portion succeeds, but the reservation of the "low"
portion fails. Then kexec can load kdump kernel successfully, but
the boot of kdump kernel fails as
People reported that when allocating crashkernel memory using
,high and ,low syntax, there were cases where the reservation
of the high portion succeeds, but the reservation of the low
portion fails. Then kexec can load kdump kernel successfully, but
the boot of kdump kernel fails as there's no
On Sun, Jul 19, 2015 at 07:07:44PM +0800, Baoquan He wrote:
People reported that when allocating crashkernel memory using
,high and ,low syntax, there were cases where the reservation
of the high portion succeeds, but the reservation of the low
portion fails. Then kexec can load kdump kernel
On 07/19/15 at 03:40pm, Borislav Petkov wrote:
...
@@ -552,7 +552,7 @@ static void __init reserve_crashkernel_low(void)
if (!auto_set)
pr_info(crashkernel low reservation failed - No
suitable area found.\n);
- return;
+ return
14 matches
Mail list logo