From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: linux 4.17.7 not suitable for i386 Date: Tue, 17 Jul 2018 13:58:55 -0400 Message-ID: <87in5du4kg.fsf@netris.org> References: <20180717153608.GA24505@jasmine.lan> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44313) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ffUH1-0006nb-25 for guix-devel@gnu.org; Tue, 17 Jul 2018 14:00:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ffUGw-00068g-Dl for guix-devel@gnu.org; Tue, 17 Jul 2018 14:00:31 -0400 Received: from world.peace.net ([64.112.178.59]:46188) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ffUGw-0005xr-8X for guix-devel@gnu.org; Tue, 17 Jul 2018 14:00:26 -0400 In-Reply-To: <20180717153608.GA24505@jasmine.lan> (Leo Famulari's message of "Tue, 17 Jul 2018 11:36:08 -0400") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Leo Famulari Cc: guix-devel@gnu.org Leo Famulari writes: > FYI, the latest stable Linux release (4.17.7) is not suitable for i386 > (i686-linux) systems. Quoting Greg Kroah-Hartman: > > "NOTE, this kernel release is broken for i386 systems. If you are > running such a machine, do NOT update to this release, you will not be > able to boot properly. > > I did this release anyway with this known problem as there is a fix in > here for x86-64 systems that was nasty to track down and was affecting > people. Given that the huge majority of systems are NOT i386, I felt > this was a safe release to do at this point in time." > > https://lkml.org/lkml/2018/7/17/434 > > So, we should take care to preserve the linux-libre 4.17.6 package > definition for i686-linux, or skip this release. Thanks, Leo. I guess I'll skip the 4.17.6 update for now, but I'm open to other suggestions. Hopefully upstream will resolve this issue soon. Mark