Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753380AbeAEXPd (ORCPT + 1 other); Fri, 5 Jan 2018 18:15:33 -0500 Received: from mail-it0-f68.google.com ([209.85.214.68]:36543 "EHLO mail-it0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752612AbeAEXPa (ORCPT ); Fri, 5 Jan 2018 18:15:30 -0500 X-Google-Smtp-Source: ACJfBosVW4jGsooyq5VoQIK0hH0ykftGJ4WkDgnGBe70JbCehsGXG49zfy2z6mastMsTumfcNa+Fh7rkF2Zd8arXUzI= MIME-Version: 1.0 In-Reply-To: References: <630fd5c7-61bb-6af7-897e-b3ac254730bb@oracle.com> <192D254D-57C6-49F0-809C-2391FCB4F341@amacapital.net> <0C00DC80-5F7E-4417-872D-66473A6387A0@amacapital.net> <20180105175229.GA29834@kroah.com> <20180105204557.GA8839@kroah.com> From: Hugh Dickins Date: Fri, 5 Jan 2018 15:15:27 -0800 Message-ID: Subject: Re: [PATCH 4.4 00/37] 4.4.110-stable review To: Pavel Tatashin Cc: Greg Kroah-Hartman , Andy Lutomirski , Linus Torvalds , Thomas Voegtle , Linux Kernel Mailing List , Andrew Morton , Guenter Roeck , Shuah Khan , patches@kernelci.org, Ben Hutchings , lkft-triage@lists.linaro.org, stable Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Fri, Jan 5, 2018 at 1:03 PM, Pavel Tatashin wrote: > The hardware works :) I meant that before the patch linked in > https://lkml.org/lkml/2018/1/5/534, I was never able to boot 4.4.110. But > with that patch applied, I was able to boot it at least once, but it could > be accidental. The hang/panic does not happen at the same time on every > boot. I get the feeling that it was accidental: it seems to me that you have a memory corruption problem, that gets shifted around by the different patches (or "noefi" or "nopti"). Because yesterday your boots were able to get way beyond the "EFI Variables Facility" message, and I can't imagine why the EFI issue would not have been equally debilitating on yesterday's 110-rc, if it were in play. I did intend to ask you to send your System.map, for us to scan through: maybe some variable is marked __init and should not be, then the "Freeing unused kernel memory" frees it for random reuse. But today you didn't get anywhere near the "Freeing unused kernel memory", so that can't be it - or do you sometimes get that far today? You mention that the hang/panic does not happen at the same time on every boot: I think all I can ask is for you to keep supplying us with different examples (console messages) of where it occurs, in the hope that one of them will point us in the right direction. And it even seems possible that this has nothing to do with the 4.4.110 changes - that 4.4.109 plus some other random patches would unleash similar corruption. Though on balance that does seem unlikely. Hugh > > Pasha > > > On 01/05/2018 03:45 PM, Greg Kroah-Hartman wrote: >> >> On Fri, Jan 05, 2018 at 02:18:32PM -0500, Pavel Tatashin wrote: >>> >>> Actually it helps, if before 4.4.110 never booted on my machine, not i >>> was able to boot on a second try. >> >> >> Wait, what? This has never booted on 4.4.x before? Did 4.4.108 work? >> 109? Are you sure this hardware even works? :) >> >> thanks, >> >> greg k-h >> >