From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750767AbXCVMyk (ORCPT ); Thu, 22 Mar 2007 08:54:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750717AbXCVMyk (ORCPT ); Thu, 22 Mar 2007 08:54:40 -0400 Received: from mail.velocity.net ([66.211.211.55]:53253 "EHLO mail.velocity.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750767AbXCVMyj (ORCPT ); Thu, 22 Mar 2007 08:54:39 -0400 X-AV-Checked: Thu Mar 22 08:54:38 2007 clean Subject: Re: PROBLEM: null pointer dereference in cfq_dispatch_requests (2.6.21-rc2 and 2.6.20) From: Dale Blount To: Jens Axboe Cc: Chuck Ebbert , linux-kernel@vger.kernel.org In-Reply-To: <20070321195928.GG15024@kernel.dk> References: <1172685755.5773.6.camel@dwillia2-linux.ch.intel.com> <200703011308.28266.linux@f-seidel.de> <20070301123057.GO23985@kernel.dk> <460174EC.8000608@redhat.com> <1174501407.14261.34.camel@dale.velocity.net> <20070321195928.GG15024@kernel.dk> Content-Type: text/plain Date: Thu, 22 Mar 2007 08:54:38 -0400 Message-Id: <1174568078.15723.2.camel@dale.velocity.net> Mime-Version: 1.0 X-Mailer: Evolution 2.8.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2007-03-21 at 20:59 +0100, Jens Axboe wrote: > On Wed, Mar 21 2007, Dale Blount wrote: > > On Wed, 2007-03-21 at 14:09 -0400, Chuck Ebbert wrote: > > > Dale Blount wrote: > > > >> I'm puzzled why this is hitting Dan, but no one else has reported > > > >> anything. Dan, did 2.6.19 work for you? > > > > > > > > Actually, I believe it is happening to me too. This is on a 4-disk raid5 with > > > > one failed disk on two 2-port sata_sil pci controller cards. > > > > > > > > The BUG below is from 2.6.20.3, but I will try 2.6.21-rc4 tonight. > > > > The disk didn't fail until 2.6.20, so I don't know if 2.6.19 would have worked > > > > or not. > > > > > > > > > > > > > > Just to be clear: you have a RAID array (what level?) with a failed disk > > > and it's giving you the same error that Dan gets? > > > > > > Yes, the BUG looks to be pretty similar to me. It's a 4 disk raid5 with > > one disk missing (dead and sent in for RMA). > > Interesting, I'll definitely see if I can reproduce it like that. > FWIW, the server made it through a round using 2.6.21-rc4 without errors. 2.6.20.x failed 5 times straight and worked 4 times prior to that (also with a missing disk), so it could be a coincidence too. The disk is back from RMA, do you need me to hold off replacing it? Thanks, Dale