From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Hansen Subject: Re: aic7xxx broken in 2.6.18-rc3-mm2 Date: Fri, 11 Aug 2006 15:31:46 -0700 Message-ID: <1155335506.7574.54.camel@localhost.localdomain> References: <1155334308.7574.50.camel@localhost.localdomain> <1155335237.3552.48.camel@mulgrave.il.steeleye.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from e31.co.us.ibm.com ([32.97.110.149]:44432 "EHLO e31.co.us.ibm.com") by vger.kernel.org with ESMTP id S1751203AbWHKWcD (ORCPT ); Fri, 11 Aug 2006 18:32:03 -0400 In-Reply-To: <1155335237.3552.48.camel@mulgrave.il.steeleye.com> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: James Bottomley Cc: Linux Kernel Mailing List , linux scsi , Andrew Morton , Alexis Bruemmer , Mike Anderson On Fri, 2006-08-11 at 17:27 -0500, James Bottomley wrote: > On Fri, 2006-08-11 at 15:11 -0700, Dave Hansen wrote: > > My scsi card stopped being detected in 2.6.18-rc3-mm2, but works in > > plain 2.6.18-rc3. I bisected all the way down to the git-sas.patch. > > I > > then noticed that if I enable the AIC94XX driver, my card works again. > > > > I'm digging through it right now, but I figured I'd post in case > > anyone > > else had seen this. This error mode seems vaguely familiar as well. > > Any ideas? > > There's nothing in the driver diff that interferes with the aic7xxx ... > my best guess would be some cockup over duplicate pci id claims ... > what's the lspci -n output for the card? 0000:02:01.0 0100: 9005:00cf (rev 01) 0000:02:01.1 0100: 9005:00cf (rev 01) -- Dave