From: "Yinghai Lu" <yinghai@kernel.org>
To: "Piotr Łobacz" <kocur666@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: latest kernel 2.6.27 and error message 'pci 0000:01:00.0: BAR 6: can't allocate mem resource [0xe0000000-0xdfffffff]'
Date: Mon, 3 Nov 2008 17:36:01 -0800 [thread overview]
Message-ID: <86802c440811031736l428d90a6we38c7a9c14288194@mail.gmail.com> (raw)
In-Reply-To: <14a58f0b0811031713x3cececb6x670a61eceffb8561@mail.gmail.com>
On Mon, Nov 3, 2008 at 5:13 PM, Piotr Łobacz <kocur666@gmail.com> wrote:> Hi all,> I have strange error message when I boot my linux with latest kerner> just like in the subject.>> I give you my /proc/iomem:> 00000000-0009f7ff : System RAM> 0009f800-0009ffff : reserved> 000a0000-000bffff : Video RAM area> 000c0000-000cdfff : Video ROM> 000ce000-000cf9ff : Adapter ROM> 000dc000-000fffff : reserved> 000f0000-000fffff : System ROM> 00100000-3fecffff : System RAM> 00100000-0048a7c2 : Kernel code> 0048a7c3-00595e97 : Kernel data> 005e4000-0062e767 : Kernel bss> 3fed0000-3fee2fff : ACPI Non-volatile Storage> 3fee3000-3fffffff : reserved> 50000000-500000ff : 0000:00:1f.3> c6000000-c7ffffff : PCI Bus 0000:06> c6000000-c600ffff : 0000:06:00.0> c6000000-c600ffff : tg3> c9000000-caffffff : PCI Bus 0000:01> c9000000-c9ffffff : 0000:01:00.0> c9000000-c9ffffff : nvidia> ca000000-caffffff : 0000:01:00.0> cc000000-cdffffff : PCI Bus 0000:06> d0000000-dfffffff : PCI Bus 0000:01> d0000000-dfffffff : 0000:01:00.0> d0000000-d09fffff : uvesafb> e0000000-efffffff : PCI MMCONFIG 0> e0000000-efffffff : reserved
that should be harmless... your BIOS have mmconf addr in BAR too, andthat BAR is read only, and BIOS should hide it to OS,
YH˙ôčş{.nÇ+ˇŽ+%Ë˙ąéÝś\x17Ľw˙ş{.nÇ+ˇĽ{ąţGŤé˙{ayş\x1dĘÚë,j\a˘fŁ˘ˇhďę˙ęçz_čŽ\x03(éݢj"ú\x1aś^[m§˙˙ž\aŤţGŤé˙˘¸?¨čÚ&Łř§~áśiOćŹzˇvŘ^\x14\x04\x1aś^[m§˙˙Ă\f˙śě˙˘¸?IĽ
prev parent reply other threads:[~2008-11-04 1:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 1:13 Piotr Łobacz
2008-11-04 1:36 ` 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=86802c440811031736l428d90a6we38c7a9c14288194@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=kocur666@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®