From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: Boot failure on Arndale with next-20131105 Date: Tue, 05 Nov 2013 10:38:27 -0700 Message-ID: <52792D13.70704@wwwdotorg.org> References: <1451170.jb5zbRXgpt@amdc1227> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from avon.wwwdotorg.org ([70.85.31.133]:48988 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750732Ab3KERic (ORCPT ); Tue, 5 Nov 2013 12:38:32 -0500 In-Reply-To: <1451170.jb5zbRXgpt@amdc1227> Sender: linux-next-owner@vger.kernel.org List-ID: To: Tomasz Figa , Tushar Behera Cc: linux-next@vger.kernel.org, lkml , Jens Axboe , Chris Mason On 11/05/2013 09:42 AM, Tomasz Figa wrote: > Hi, >=20 > On Tuesday 05 of November 2013 17:19:00 Tushar Behera wrote: >> Hi, >> >> We are having a boot-time kernel panic on Samsung's Exynos5250-based >> Arndale board with next-20131105. Bisect points to following commit. >> >> <<< >> commit febca1baea1cfe2d7a0271385d89b03d5fb34f94 >> Author: Chris Mason >> Date: Thu Oct 31 13:32:42 2013 -0600 >> >> block: setup bi_vcnt on clones >> >> commit 9fc6286f347d changed the cloning code to make clones chea= per for >> the case where we don't need to clone the iovec array. But, >> the new clone needs the bi_vnct from the original. >> >> Signed-off-by: Chris Mason >> Signed-off-by: Jens Axboe >> >>> >> >> Reverting above commit, Arndale is able to boot again. >=20 > I can confirm exactly the same behavior on Exynos 4210-based Trats bo= ard, > with exactly the same bisection results. Despite the backtrace looking different, reverting that commit also solves the boot failures on the Tegra-based "Beaver" board. > Also note that I spotted multiple build failures in block layer durin= g > the bisection. I note that compiling next-20131105 generates quite a few warnings re: uninitialized variables. Reverting the commit doesn't solve those. > block/blk-merge.c: In function =91blk_bio_map_sg=92: > block/blk-merge.c:133:8: warning: =91bvprv.bv_len=92 may be used unin= itialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:233:23: note: =91bvprv.bv_len=92 was declared here > block/blk-merge.c:133:8: warning: =91bvprv.bv_offset=92 may be used u= ninitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:233:23: note: =91bvprv.bv_offset=92 was declared he= re > block/blk-merge.c:133:8: warning: =91bvprv.bv_page=92 may be used uni= nitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:233:23: note: =91bvprv.bv_page=92 was declared here > block/blk-merge.c: In function =91blk_rq_map_sg=92: > block/blk-merge.c:133:8: warning: =91bvprv.bv_page=92 may be used uni= nitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:171:23: note: =91bvprv.bv_page=92 was declared here > block/blk-merge.c:133:8: warning: =91bvprv.bv_offset=92 may be used u= ninitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:171:23: note: =91bvprv.bv_offset=92 was declared he= re > block/blk-merge.c:133:8: warning: =91bvprv.bv_len=92 may be used unin= itialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:171:23: note: =91bvprv.bv_len=92 was declared here > block/blk-merge.c: In function =91attempt_merge=92: > block/blk-merge.c:108:7: warning: =91end_bv.bv_offset=92 may be used = uninitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:89:17: note: =91end_bv.bv_offset=92 was declared he= re > block/blk-merge.c:108:7: warning: =91end_bv.bv_page=92 may be used un= initialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:89:17: note: =91end_bv.bv_page=92 was declared here > block/blk-merge.c:108:7: warning: =91end_bv.bv_len=92 may be used uni= nitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:89:17: note: =91end_bv.bv_len=92 was declared here