Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752689AbcDOBZX (ORCPT ); Thu, 14 Apr 2016 21:25:23 -0400 Received: from mail-oi0-f51.google.com ([209.85.218.51]:34547 "EHLO mail-oi0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751775AbcDOBZW (ORCPT ); Thu, 14 Apr 2016 21:25:22 -0400 MIME-Version: 1.0 In-Reply-To: <39499.1460661743@turing-police.cc.vt.edu> References: <3689.1460593786@turing-police.cc.vt.edu> <20160414013546.GA9198@js1304-P5Q-DELUXE> <39499.1460661743@turing-police.cc.vt.edu> Date: Fri, 15 Apr 2016 10:25:21 +0900 Message-ID: Subject: Re: linux-next crash during very early boot From: Joonsoo Kim To: Valdis.Kletnieks@vt.edu Cc: Joonsoo Kim , Andrew Morton , LKML , Linux Memory Management List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 575 Lines: 16 2016-04-15 4:22 GMT+09:00 : > On Thu, 14 Apr 2016 10:35:47 +0900, Joonsoo Kim said: > >> My fault. It should be assgined every time. Please test below patch. >> I will send it with proper SOB after you confirm the problem disappear. >> Thanks for report and analysis! > > Still bombs out, sorry. Will do more debugging this evening if I have > a chance - will follow up tomorrow morning US time.... Hmm... could you also apply the patch on below link? There is another issue from me and fix is there. https://lkml.org/lkml/2016/4/10/703 Thanks.