On 11/05/2013 09:42 AM, Tomasz Figa wrote: > Hi, > > 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 <chris.mason@xxxxxxxxxxxx> >> Date: Thu Oct 31 13:32:42 2013 -0600 >> >> block: setup bi_vcnt on clones >> >> commit 9fc6286f347d changed the cloning code to make clones cheaper 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 <chris.mason@xxxxxxxxxxxx> >> Signed-off-by: Jens Axboe <axboe@xxxxxxxxx> >> >>> >> >> Reverting above commit, Arndale is able to boot again. > > I can confirm exactly the same behavior on Exynos 4210-based Trats board, > 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 during > 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 ‘blk_bio_map_sg’: > block/blk-merge.c:133:8: warning: ‘bvprv.bv_len’ may be used uninitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:233:23: note: ‘bvprv.bv_len’ was declared here > block/blk-merge.c:133:8: warning: ‘bvprv.bv_offset’ may be used uninitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:233:23: note: ‘bvprv.bv_offset’ was declared here > block/blk-merge.c:133:8: warning: ‘bvprv.bv_page’ may be used uninitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:233:23: note: ‘bvprv.bv_page’ was declared here > block/blk-merge.c: In function ‘blk_rq_map_sg’: > block/blk-merge.c:133:8: warning: ‘bvprv.bv_page’ may be used uninitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:171:23: note: ‘bvprv.bv_page’ was declared here > block/blk-merge.c:133:8: warning: ‘bvprv.bv_offset’ may be used uninitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:171:23: note: ‘bvprv.bv_offset’ was declared here > block/blk-merge.c:133:8: warning: ‘bvprv.bv_len’ may be used uninitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:171:23: note: ‘bvprv.bv_len’ was declared here > block/blk-merge.c: In function ‘attempt_merge’: > block/blk-merge.c:108:7: warning: ‘end_bv.bv_offset’ may be used uninitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:89:17: note: ‘end_bv.bv_offset’ was declared here > block/blk-merge.c:108:7: warning: ‘end_bv.bv_page’ may be used uninitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:89:17: note: ‘end_bv.bv_page’ was declared here > block/blk-merge.c:108:7: warning: ‘end_bv.bv_len’ may be used uninitialized in this function [-Wmaybe-uninitialized] > block/blk-merge.c:89:17: note: ‘end_bv.bv_len’ was declared here -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
