From: Luben Tuikov <luben_tuikov@adaptec.com>
To: "K.R. Foley" <kr@cybsft.com>
Cc: Dave Hansen <haveblue@us.ibm.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: 2.6.9-rc3-mm3 fails to detect aic7xxx
Date: Thu, 07 Oct 2004 16:38:41 -0400 [thread overview]
Message-ID: <4165A951.3060808@adaptec.com> (raw)
In-Reply-To: <4165A369.60306@cybsft.com>
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
next prev parent reply other threads:[~2004-10-07 21:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 19:40 2.6.9-rc3-mm3 fails to detect aic7xxx Dave Hansen
2004-10-07 20:13 ` K.R. Foley
2004-10-07 20:38 ` Luben Tuikov [this message]
2004-10-07 20:45 ` Dave Hansen
2004-10-08 3:53 ` K.R. Foley
2004-10-07 20:39 ` Andrew Morton
2004-10-07 20:41 ` Dave Hansen
2004-10-07 20:49 ` K.R. Foley
2004-10-07 22:42 ` J.A. Magallon
2004-10-08 3:57 ` K.R. Foley
2004-10-08 12:08 ` Luben Tuikov
2004-10-22 13:58 ` Ingo Molnar
2004-10-22 14:02 ` Luben Tuikov
2004-10-22 14:07 ` Ingo Molnar
2004-10-22 14:40 ` Luben Tuikov
2004-10-22 14:55 ` Ingo Molnar
2004-10-22 15:04 ` Luben Tuikov
2004-10-22 17:36 ` K.R. Foley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4165A951.3060808@adaptec.com \
--to=luben_tuikov@adaptec.com \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=kr@cybsft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).