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
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
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
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
> 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
> 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
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 -
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 -
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.
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.
10 matches
Mail list logo