[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180416181642.vuicay5ng2ieuf7h@node.shutemov.name>
Date: Mon, 16 Apr 2018 21:16:42 +0300
From: "Kirill A. Shutemov" <kirill@...temov.name>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Ingo Molnar <mingo@...nel.org>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Greg Thelen <gthelen@...gle.com>
Subject: Re: instant reboot caused by 194a9749c73d650c0
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 was working better.
>
> Hm. Are you saing that switching from gcc-4.7 to gcc-4.9 fixed the issue
> for you? That's worth investigating.
Checked kernel build with gcc-4.6 and it boots fine...
--
Kirill A. Shutemov
Powered by blists - more mailing lists