From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755521Ab3KEUe4 (ORCPT ); Tue, 5 Nov 2013 15:34:56 -0500 Received: from merlin.infradead.org ([205.233.59.134]:39198 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752906Ab3KEUey (ORCPT ); Tue, 5 Nov 2013 15:34:54 -0500 Message-ID: <5279565A.4050206@kernel.dk> Date: Tue, 05 Nov 2013 13:34:34 -0700 From: Jens Axboe User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Olof Johansson CC: Tushar Behera , "linux-next@vger.kernel.org" , lkml , Chris Mason Subject: Re: Boot failure on Arndale with next-20131105 References: <52794823.7080503@kernel.dk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/05/2013 01:23 PM, Olof Johansson wrote: >> Very weird! What file system is being used? > > Most of my failures have happened on regular MMC cards with ext4 > filesystems on them. > > Note that the panic happens during device probe / partition table > scanning, not after mounting the filesystem. Hmm ok. > Giving your patch a go now across the board. I'm very concerned about > the reports of bisectability, build failures and heaps of warnings > though. Did the 0-day builder pick up any of those? :-/ Yeah, unfortunately the immutable conversion has turned out to be quite messy :-( -- Jens Axboe