[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <517006F6.7030806@cn.fujitsu.com>
Date: Thu, 18 Apr 2013 22:45:10 +0800
From: Wanlong Gao <gaowanlong@...fujitsu.com>
To: Jens Axboe <axboe@...nel.dk>
CC: Steven Rostedt <rostedt@...dmis.org>, Tejun Heo <tj@...nel.org>,
namhyung@...il.com, agk@...hat.com, dm-devel@...hat.com,
neilb@...e.de, LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Wanlong Gao <gaowanlong@...fujitsu.com>
Subject: Re: [BUG REPORT] Kernel panic on 3.9.0-rc7-4-gbb33db7
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists