linux-kernel - Re: 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots [full dmesg]

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <86802c441003121227j77edc017vd83b2ab866ec79d8@mail.gmail.com>
Date:	Fri, 12 Mar 2010 12:27:16 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
Cc:	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: 2.6.33: pci 0000:00:00.0: address space collision / spontaenous 
	reboots [full dmesg]

On Fri, Mar 12, 2010 at 12:02 PM, Justin Piszcz <jpiszcz@...idpixels.com> wrote:
>
>
> On Fri, 12 Mar 2010, Yinghai Lu wrote:
>
>> On Fri, Mar 12, 2010 at 5:10 AM, Justin Piszcz <jpiszcz@...idpixels.com>
>> wrote:
>>>
>>> [    0.112379] pci 0000:00:00.0: reg 1c: [mem 0xe0000000-0xffffffff
>>> 64bit]
>>
>>> [    0.133510] PCI: pci_cache_line_size set to 64 bytes
>>> [    0.133515] pci 0000:00:00.0: BAR 3: reserving [mem
>>> 0xe0000000-0xffffffff
>>> flags 0x120204] (d=0, p=0)
>>> [    0.133518] pci 0000:00:00.0: address space collision: [mem
>>> 0xe0000000-0xffffffff 64bit] already in use
>>> [    0.133522] pci 0000:00:00.0: can't reserve [mem 0xe0000000-0xffffffff
>>> 64bit]
>>> [    0.137020] system 00:09: [mem 0xe0000000-0xefffffff] has been
>>> reserved
>>> [    0.172034] pci_bus 0000:00: resource 0 [io  0x0000-0xffff]
>>> [    0.172035] pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffff]
>>
>> looks like the silicon report wrong size in that BAR3
>>
>> YH
>
> Hi,
>
> Is there anyway to work around this?  Or is it a bad motherboard?
>

maybe one new BIOS could hide that register

or use pci quirk to hide that in OS.

may need to access the chipset doc.

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/