From: "Darrick J. Wong" <djwong@us.ibm.com>
To: tarjei@nu.no
Cc: dougg@torque.net, linux-scsi@vger.kernel.org, "Wu,
Gilbert" <Gilbert_Wu@adaptec.com>,
"Chim, Ed" <ed_chim@adaptec.com>,
Alexis Bruemmer <alexisb@us.ibm.com>
Subject: Re: Adaptect 9405w: What is the best solution?
Date: Mon, 15 Jan 2007 12:50:40 -0800 [thread overview]
Message-ID: <45ABE920.7090304@us.ibm.com> (raw)
In-Reply-To: <45AA4A7B.7070607@scanventure.no>
Tarjei Huse wrote:
> Duh! Thanks :-)
>
> After doing as you suggested, and running make oldconfig using the
> configuration from Ubuntu Dapper (2.6.15-23-server) and the stock Ubuntu
> Edgy I get the same error when booting the kernel:
>
> PCI: BIOS Bug: MCFG area at e00000000 is not E820-reserved
> PCI: Not using MMCONFIG
> PCI Cannot allocate resource region 7 of bridge 0000:00:01.1
> PCI Cannot allocate resource region 8 of bridge 0000:00:01.1
> PCI Cannot allocate resource region 9 of bridge 0000:00:01.1
This is a known conflict between the kernel and the BIOS. As far as I
know this should not affect the operation of the aic94xx because it is a
PCIX device, and bridge 0:0:1.1 is a PCIe port. At least on the x306m...
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown
> wn-block(0,0)
>
> Is this some missing compile option or a bug?
Perhaps. Could you send a full output? It does not appear that the
aic94xx driver is loading at all...?
--D
next prev parent reply other threads:[~2007-01-15 20:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 11:02 Adaptect 9405w: What is the best solution? Tarjei Huse
2007-01-11 15:26 ` Douglas Gilbert
2007-01-11 19:30 ` Darrick J. Wong
2007-01-11 19:48 ` Tarjei Huse
2007-01-11 20:08 ` Darrick J. Wong
[not found] ` <45A6C33C.8060900@scanventure.no>
2007-01-12 23:37 ` Darrick J. Wong
2007-01-14 15:30 ` Tarjei Huse
[not found] ` <45AA4A7B.7070607@scanventure.no>
2007-01-15 20:50 ` Darrick J. Wong [this message]
2007-01-16 14:12 ` Tarjei Huse
2007-01-16 23:14 ` Alexis Bruemmer
2007-01-17 10:51 ` Tarjei Huse
2007-01-17 16:32 ` Mark Rustad
2007-01-17 16:54 ` James Bottomley
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=45ABE920.7090304@us.ibm.com \
--to=djwong@us.ibm.com \
--cc=Gilbert_Wu@adaptec.com \
--cc=alexisb@us.ibm.com \
--cc=dougg@torque.net \
--cc=ed_chim@adaptec.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tarjei@nu.no \
/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).