From: "Yinghai Lu" <yinghai.lu@amd.com>
To: "Jeff Chua" <jeff.chua.linux@gmail.com>
Cc: "Adrian Bunk" <bunk@stusta.de>,
linux-kernel@vger.kernel.org,
"David Miller" <davem@davemloft.net>
Subject: Re: linux-2.6.19-rc2 tg3 problem
Date: Sat, 28 Oct 2006 01:23:47 -0700 [thread overview]
Message-ID: <86802c440610280123m3051f6cj8d361b06b347186f@mail.gmail.com> (raw)
In-Reply-To: <b6a2187b0610271805w154ca251tb7db33ed0926623@mail.gmail.com>
On 10/27/06, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
it seems pci_assign_unassigned_resource ( in
drivers/pci/setup-bus.c) is getting to smart to allocate more
unassigned resource that is not allocated by BIOS.
YH
> PCI: Bridge: 0000:00:01.0
> IO window: disabled.
> MEM window: fe900000-fe9fffff
> PREFETCH window: disabled.
> PCI: Bridge: 0000:00:1c.0
> IO window: disabled.
> MEM window: fe800000-fe8fffff
> PREFETCH window: disabled.
> PCI: Bridge: 0000:00:1c.1
> IO window: disabled.
> MEM window: fe700000-fe7fffff
> PREFETCH window: disabled.
> PCI: Bridge: 0000:00:1e.0
> IO window: disabled.
> MEM window: disabled.
> PREFETCH window: disabled.
===>
151a170,179
> PCI: Cannot allocate resource region 8 of bridge 0000:00:01.0
> PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.0
> PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.1
> PCI: Cannot allocate resource region 0 of device 0000:00:02.0
> PCI: Cannot allocate resource region 3 of device 0000:00:02.0
> PCI: Cannot allocate resource region 0 of device 0000:00:02.1
> PCI: Cannot allocate resource region 0 of device 0000:00:1d.7
> PCI: Cannot allocate resource region 2 of device 0000:00:1e.2
> PCI: Cannot allocate resource region 3 of device 0000:00:1e.2
> PCI: Cannot allocate resource region 0 of device 0000:02:00.0
164a193,199
> PCI: Failed to allocate mem resource #8:100000@e1000000 for 0000:00:1c.0
> PCI: Failed to allocate mem resource #0:80000@e1000000 for 0000:00:02.0
> PCI: Failed to allocate mem resource #0:80000@e1000000 for 0000:00:02.1
> PCI: Failed to allocate mem resource #3:40000@e1000000 for 0000:00:02.0
> PCI: Failed to allocate mem resource #0:400@e1000000 for 0000:00:1d.7
> PCI: Failed to allocate mem resource #2:200@e1000000 for 0000:00:1e.2
> PCI: Failed to allocate mem resource #3:100@e1000000 for 0000:00:1e.2
167c202
< MEM window: fe900000-fe9fffff
---
> MEM window: disabled.
168a204
> PCI: Failed to allocate mem resource #0:10000@0 for 0000:02:00.0
171c207
< MEM window: fe800000-fe8fffff
---
> MEM window: disabled.
175c211
< MEM window: fe700000-fe7fffff
---
> MEM window: disabled.
prev parent reply other threads:[~2006-10-28 8:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 15:24 Jeff Chua
2006-10-23 21:19 ` David Miller
2006-10-25 1:30 ` Adrian Bunk
2006-10-26 0:54 ` Jeff Chua
2006-10-26 15:24 ` Adrian Bunk
2006-10-27 13:49 ` Jeff Chua
2006-10-27 20:31 ` Adrian Bunk
2006-10-28 1:05 ` Jeff Chua
2006-10-28 3:20 ` linux-2.6.19-rc2 PCI problem Adrian Bunk
2006-10-28 10:24 ` Jeff Chua
2006-10-28 15:45 ` Matthew Wilcox
2006-10-29 1:20 ` Jeff Chua
2006-10-28 8:23 ` Yinghai Lu [this message]
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=86802c440610280123m3051f6cj8d361b06b347186f@mail.gmail.com \
--to=yinghai.lu@amd.com \
--cc=bunk@stusta.de \
--cc=davem@davemloft.net \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®