Re: crashkernel=512M is no longer working on this aarch64 server

2018-11-12 Thread Qian Cai
On 11/12/18 at 1:01 AM, Martin Schwidefsky wrote: > On Sun, 11 Nov 2018 08:36:09 -0500 > Qian Cai wrote: > > > > On Nov 11, 2018, at 6:35 AM, Martin Schwidefsky > > > wrote: > > > > > > On Sat, 10 Nov 2018 23:41:34 -0500 > > > Qian Cai wrote: > > > > > >> It was broken somewhere between

Re: crashkernel=512M is no longer working on this aarch64 server

2018-11-12 Thread Qian Cai
On 11/12/18 at 1:01 AM, Martin Schwidefsky wrote: > On Sun, 11 Nov 2018 08:36:09 -0500 > Qian Cai wrote: > > > > On Nov 11, 2018, at 6:35 AM, Martin Schwidefsky > > > wrote: > > > > > > On Sat, 10 Nov 2018 23:41:34 -0500 > > > Qian Cai wrote: > > > > > >> It was broken somewhere between

Re: crashkernel=512M is no longer working on this aarch64 server

2018-11-11 Thread Martin Schwidefsky
On Sun, 11 Nov 2018 08:36:09 -0500 Qian Cai wrote: > > On Nov 11, 2018, at 6:35 AM, Martin Schwidefsky > > wrote: > > > > On Sat, 10 Nov 2018 23:41:34 -0500 > > Qian Cai wrote: > > > >> It was broken somewhere between b00d209241ff and 3541833fd1f2. > >> > >> [0.00] cannot

Re: crashkernel=512M is no longer working on this aarch64 server

2018-11-11 Thread Martin Schwidefsky
On Sun, 11 Nov 2018 08:36:09 -0500 Qian Cai wrote: > > On Nov 11, 2018, at 6:35 AM, Martin Schwidefsky > > wrote: > > > > On Sat, 10 Nov 2018 23:41:34 -0500 > > Qian Cai wrote: > > > >> It was broken somewhere between b00d209241ff and 3541833fd1f2. > >> > >> [0.00] cannot

Re: crashkernel=512M is no longer working on this aarch64 server

2018-11-11 Thread Qian Cai
> On Nov 11, 2018, at 6:35 AM, Martin Schwidefsky > wrote: > > On Sat, 10 Nov 2018 23:41:34 -0500 > Qian Cai wrote: > >> It was broken somewhere between b00d209241ff and 3541833fd1f2. >> >> [0.00] cannot allocate crashkernel (size:0x2000) >> >> Where a good one looks like

Re: crashkernel=512M is no longer working on this aarch64 server

2018-11-11 Thread Qian Cai
> On Nov 11, 2018, at 6:35 AM, Martin Schwidefsky > wrote: > > On Sat, 10 Nov 2018 23:41:34 -0500 > Qian Cai wrote: > >> It was broken somewhere between b00d209241ff and 3541833fd1f2. >> >> [0.00] cannot allocate crashkernel (size:0x2000) >> >> Where a good one looks like

Re: crashkernel=512M is no longer working on this aarch64 server

2018-11-11 Thread Martin Schwidefsky
On Sat, 10 Nov 2018 23:41:34 -0500 Qian Cai wrote: > It was broken somewhere between b00d209241ff and 3541833fd1f2. > > [0.00] cannot allocate crashkernel (size:0x2000) > > Where a good one looks like this, > > [0.00] crashkernel reserved: 0x0860 -

Re: crashkernel=512M is no longer working on this aarch64 server

2018-11-11 Thread Martin Schwidefsky
On Sat, 10 Nov 2018 23:41:34 -0500 Qian Cai wrote: > It was broken somewhere between b00d209241ff and 3541833fd1f2. > > [0.00] cannot allocate crashkernel (size:0x2000) > > Where a good one looks like this, > > [0.00] crashkernel reserved: 0x0860 -

crashkernel=512M is no longer working on this aarch64 server

2018-11-10 Thread Qian Cai
It was broken somewhere between b00d209241ff and 3541833fd1f2. [0.00] cannot allocate crashkernel (size:0x2000) Where a good one looks like this, [0.00] crashkernel reserved: 0x0860 - 0x2860 (512 MB) Some commits look more suspicious than others.

crashkernel=512M is no longer working on this aarch64 server

2018-11-10 Thread Qian Cai
It was broken somewhere between b00d209241ff and 3541833fd1f2. [0.00] cannot allocate crashkernel (size:0x2000) Where a good one looks like this, [0.00] crashkernel reserved: 0x0860 - 0x2860 (512 MB) Some commits look more suspicious than others.