Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967187Ab3DROot (ORCPT ); Thu, 18 Apr 2013 10:44:49 -0400 Received: from cn.fujitsu.com ([222.73.24.84]:10591 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S967153Ab3DROos (ORCPT ); Thu, 18 Apr 2013 10:44:48 -0400 X-IronPort-AV: E=Sophos;i="4.87,502,1363104000"; d="scan'208";a="7088107" Message-ID: <517006F6.7030806@cn.fujitsu.com> Date: Thu, 18 Apr 2013 22:45:10 +0800 From: Wanlong Gao Reply-To: gaowanlong@cn.fujitsu.com Organization: Fujitsu User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130402 Thunderbird/17.0.5 MIME-Version: 1.0 To: Jens Axboe CC: Steven Rostedt , Tejun Heo , namhyung@gmail.com, agk@redhat.com, dm-devel@redhat.com, neilb@suse.de, LKML , Linus Torvalds , Wanlong Gao Subject: Re: [BUG REPORT] Kernel panic on 3.9.0-rc7-4-gbb33db7 References: <516E5EF8.9090507@cn.fujitsu.com> <1366209997.8817.12.camel@pippen.local.home> <20130418123738.GV4816@kernel.dk> <516FED09.1040008@cn.fujitsu.com> <20130418133546.GX4816@kernel.dk> <516FFFAC.8040103@cn.fujitsu.com> <20130418143014.GZ4816@kernel.dk> In-Reply-To: <20130418143014.GZ4816@kernel.dk> X-MIMETrack: Itemize by SMTP Server on mailserver/fnst(Release 8.5.3|September 15, 2011) at 2013/04/18 22:43:21, Serialize by Router on mailserver/fnst(Release 8.5.3|September 15, 2011) at 2013/04/18 22:43:21, Serialize complete at 2013/04/18 22:43:21 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1129 Lines: 34 On 04/18/2013 10:30 PM, Jens Axboe wrote: > On Thu, Apr 18 2013, Wanlong Gao wrote: >> On 04/18/2013 09:35 PM, Jens Axboe wrote: >>> On Thu, Apr 18 2013, Wanlong Gao wrote: >>>>> A bio is always fully initialized, regardless of which internal >>>>> allocator it came from. If people are doing private kmallocs, then they >>>>> better be using bio_init() as well. >>>>> >>>>> Wanlong, would it be possible to get a full dmesg on boot see I can see >>>>> what drivers and file systems are in use? Anything special about your >>>>> setup. >>>> >>>> Sure, attached. >>> >>> Does the below help? >> >> Still got panic with this patch. :-( > > Could you capture the full dump? I'd like to see what rcx was, and that > seems to have scrolled off. OK, but I should capture it tomorrow morning because this remote machine has already panicked and need hard reboot. Thanks, Wanlong Gao > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/