On Mon, Apr 16, 2018 at 08:36:57AM -0700, Eric Dumazet wrote:
>
>
> On 04/16/2018 02:15 AM, Kirill A. Shutemov wrote:
> In the mean time, Greg told me that using gcc-4.9 instead of our old
> gcc-4.7 based toolchain was working better.
Hm. Are you saing that switching from gcc-4.7 to gcc-4.9 fixe
On Mon, Apr 16, 2018 at 08:37:52PM +0300, Kirill A. Shutemov wrote:
> On Mon, Apr 16, 2018 at 08:36:57AM -0700, Eric Dumazet wrote:
> >
> >
> > On 04/16/2018 02:15 AM, Kirill A. Shutemov wrote:
> > In the mean time, Greg told me that using gcc-4.9 instead of our old
> > gcc-4.7 based toolchain wa
On 04/16/2018 02:15 AM, Kirill A. Shutemov wrote:
> On Mon, Apr 16, 2018 at 08:07:09AM +0200, Ingo Molnar wrote:
>>
>> * Eric Dumazet wrote:
>>
>>> Hi Kirill
>>>
>>> For some reason, my hosts instantly crash at boot time, with absolutely no
>>> log on console.
>>>
>>> Bisection pointed to :
>>>
On Mon, Apr 16, 2018 at 08:07:09AM +0200, Ingo Molnar wrote:
>
> * Eric Dumazet wrote:
>
> > Hi Kirill
> >
> > For some reason, my hosts instantly crash at boot time, with absolutely no
> > log on console.
> >
> > Bisection pointed to :
> >
> > $ git bisect bad
> > 194a9749c73d650c0b1dfdee04
* Eric Dumazet wrote:
> Hi Kirill
>
> For some reason, my hosts instantly crash at boot time, with absolutely no
> log on console.
>
> Bisection pointed to :
>
> $ git bisect bad
> 194a9749c73d650c0b1dfdee04fb0bdf0a888ba8 is the first bad commit
> commit 194a9749c73d650c0b1dfdee04fb0bdf0a888
Hi Kirill
For some reason, my hosts instantly crash at boot time, with absolutely no log
on console.
Bisection pointed to :
$ git bisect bad
194a9749c73d650c0b1dfdee04fb0bdf0a888ba8 is the first bad commit
commit 194a9749c73d650c0b1dfdee04fb0bdf0a888ba8
Author: Kirill A. Shutemov
Date: Mon M
6 matches
Mail list logo