Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933790Ab1CXSvf (ORCPT ); Thu, 24 Mar 2011 14:51:35 -0400 Received: from mx2.fusionio.com ([64.244.102.31]:57277 "EHLO mx2.fusionio.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933125Ab1CXSvc (ORCPT ); Thu, 24 Mar 2011 14:51:32 -0400 X-ASG-Debug-ID: 1300992690-01de284cf8b63b0001-xx1T2L X-Barracuda-Envelope-From: JAxboe@fusionio.com Message-ID: <4D8B92AE.8090308@fusionio.com> Date: Thu, 24 Mar 2011 19:51:26 +0100 From: Jens Axboe MIME-Version: 1.0 To: Markus Trippelsdorf CC: Linus Torvalds , "linux-kernel@vger.kernel.org" , Chris Mason Subject: Re: [GIT PULL] Core block IO bits for 2.6.39 - early Oops References: <4D8B4A89.80608@fusionio.com> <20110324183019.GA1676@gentoo.trippels.de> <4D8B8F34.5000203@fusionio.com> X-ASG-Orig-Subj: Re: [GIT PULL] Core block IO bits for 2.6.39 - early Oops In-Reply-To: <4D8B8F34.5000203@fusionio.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Barracuda-Connect: mail1.int.fusionio.com[10.101.1.21] X-Barracuda-Start-Time: 1300992690 X-Barracuda-URL: http://10.101.1.181:8000/cgi-mod/mark.cgi X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.58854 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1062 Lines: 35 On 2011-03-24 19:36, Jens Axboe wrote: > On 2011-03-24 19:30, Markus Trippelsdorf wrote: >> On 2011.03.24 at 14:43 +0100, Jens Axboe wrote: >>> >>> This is the main pull request for the block IO layer and friends for >>> 2.6.39. >> >> This merge results in an early oops on my system (amd64, xfs). >> See the attached photo. >> > > Auch. Can you ensure that you have CONFIG_DEBUGINFO=y in your .config > and then do: > > $ gdb vmlinux > ... > l *cfq_insert_request+0x32 > > and send that output? I took a closer look at the oops, and it most likely looks like q == NULL (offset 0x18 == q->elevator). You left out the Code part, so I can't verify that for certain. Which makes very little sense. I take it this is 100% reproducible? When you send the gdb output, please also attach your .config. -- Jens Axboe -- 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/