From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from manchmal.in-ulm.de ([217.10.9.201]:55734 "EHLO manchmal.in-ulm.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750954AbcERFxP (ORCPT ); Wed, 18 May 2016 01:53:15 -0400 Date: Wed, 18 May 2016 07:53:10 +0200 From: Christoph Biedl To: Greg KH , stable@vger.kernel.org Subject: Re: [PATCH 3.14 00/17] 3.14.70-stable review Message-ID: <1463550440@msgid.manchmal.in-ulm.de> References: <20160517011346.950684325@linuxfoundation.org> <1463526217@msgid.manchmal.in-ulm.de> <20160517231656.GA19452@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160517231656.GA19452@kroah.com> Sender: stable-owner@vger.kernel.org List-ID: Greg KH wrote... > On Wed, May 18, 2016 at 01:10:16AM +0200, Christoph Biedl wrote: > > Greg Kroah-Hartman wrote... > > > > > Responses should be made by Thu May 19 01:13:32 UTC 2016. > > > Anything received after that time might be too late. > > > > Compilation passes again, however the compiled kernel crashes > > immediately after loading. This happens with a kernel built using gcc5 > > (5.3.1) only, gcc 4.7 or 4.9 result in a fully working one. > > > > Since kernel 4.6 built using gcc5 runs on that particular hardware (a > > very old AMD K6 mainboard), I've tried git reverse bisect which left > > to d34687ab, and me in some confusion. > > Does 3.14.69 work? Neither (if built using gcc5). So do not delay the 3.14.70 release because of my report. The thing that puzzles me: Why did nobody else notice so far? Unless my bisecting went wrong in a very early stage, all versions up to and including 4.4 are affected. Will do more testing. Christoph