From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: Boot failure on Arndale with next-20131105 Date: Tue, 5 Nov 2013 15:33:08 -0500 Message-ID: <20131105203308.3802.45122@localhost.localdomain> References: <52794823.7080503@kernel.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8BIT Return-path: Received: from dkim2.fusionio.com ([66.114.96.54]:37318 "EHLO dkim2.fusionio.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754403Ab3KEUdP convert rfc822-to-8bit (ORCPT ); Tue, 5 Nov 2013 15:33:15 -0500 Received: from mx1.fusionio.com (unknown [10.101.1.160]) by dkim2.fusionio.com (Postfix) with ESMTP id 5B8649A0372 for ; Tue, 5 Nov 2013 13:33:15 -0700 (MST) In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Olof Johansson , Jens Axboe Cc: Tushar Behera , "linux-next@vger.kernel.org" , lkml Quoting Olof Johansson (2013-11-05 15:23:51) > On Tue, Nov 5, 2013 at 11:33 AM, Jens Axboe wrote: [ horrible crashes fixed by removing my patch ] > > 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. > > 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? :-/ > Hmmm, is bcache in your config? -chris