From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luben Tuikov Subject: Re: 2.6.9-rc3-mm3 fails to detect aic7xxx Date: Thu, 07 Oct 2004 16:38:41 -0400 Sender: linux-scsi-owner@vger.kernel.org Message-ID: <4165A951.3060808@adaptec.com> References: <1097178019.24355.39.camel@localhost> <4165A369.60306@cybsft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from magic.adaptec.com ([216.52.22.17]:6303 "EHLO magic.adaptec.com") by vger.kernel.org with ESMTP id S268141AbUJGUiw (ORCPT ); Thu, 7 Oct 2004 16:38:52 -0400 In-Reply-To: <4165A369.60306@cybsft.com> List-Id: linux-scsi@vger.kernel.org To: "K.R. Foley" Cc: Dave Hansen , Andrew Morton , Linux Kernel Mailing List , linux-scsi@vger.kernel.org K.R. Foley wrote: > Dave Hansen wrote: > >> I just booted 2.6.9-rc3-mm3 and got the good ol' >> VFS: Cannot open root device "sda2" or unknown-block(0,0) >> Please append a correct "root=" boot option >> Kernel panic - not syncing: VFS: Unable to mount root fs on >> unknown-block(0,0) >> >> backing out bk-scsi.patch seems to fix it. I believe this worked in >> 2.6.9-rc3-mm2. >> >> -- Dave > > > While I can't verify that backing out bk-scsi.patch fixes it for me yet, > I can verify that I get the exact same error trying to boot this kernel. > I too am using the aic7xxx. It is most likely the PCI ID patch which went into those drivers. You can back out only that change (drivers/scsi/aic7xxx) and try it. (assuming you haven't changed anything else) Luben