lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <86802c440811031736l428d90a6we38c7a9c14288194@mail.gmail.com>
Date:	Mon, 3 Nov 2008 17:36:01 -0800
From:	"Yinghai Lu" <yinghai@...nel.org>
To:	"Piotr Łobacz" <kocur666@...il.com>
Cc:	linux-kernel@...r.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]'

On Mon, Nov 3, 2008 at 5:13 PM, Piotr Łobacz <kocur666@...il.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, and
that BAR is read only, and BIOS should hide it to OS,

YH

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ