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: <86802c441003121201y4c946fecrda5463b056f1ba58@mail.gmail.com>
Date:	Fri, 12 Mar 2010 12:01:11 -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 5:10 AM, Justin Piszcz <jpiszcz@...idpixels.com> wrote:
>>> On Fri, 12 Mar 2010, Justin Piszcz wrote:
>>>
>>> Problem persists.
>>>
>>> Others seem to have similar issues:
>>> http://lkml.org/lkml/2010/1/9/157
>>>
>>> Some boards not compatible it appears..
>>>
>>> Justin.
>>>
>>>
>>
>> Even with all boards removed:
>> [    0.133537] pci 0000:00:00.0: address space collision: [mem
>> 0xe0000000-0xffffffff 64bit] already in use
>>
>> 00:00.0 Host bridge: ATI Technologies Inc RD790 Northbridge only dual slot
>> PCI-e_GFX and HT3 K8 part
>>
>>
>
> Hi,
>
> Here is a full dmesg with PCI debugging enabled:
>
> Of interest:
> [    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.000000] Linux version 2.6.33 (root@...ver) (gcc version 4.3.3 (Debian
> 4.3.3-14) ) #9 SMP Fri Mar 12 08:05:50 EST 2010
> [    0.000000]  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
> [    0.000000]  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
> [    0.000000] Notice: NX (Execute Disable) protection cannot be enabled:
> [    0.097716] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem
> 0xe0000000-0xefffffff] (base 0xe0000000)
> [    0.097721] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
> [    0.097724] PCI: Using MMCONFIG for extended config space
> [    0.097726] PCI: Using configuration type 1 for base access
> [    0.112158] ACPI: PCI Root Bridge [PCI0] (0000:00)
> [    0.112211] pci_root PNP0A03:00: ignoring host bridge windows from ACPI;
> boot with "pci=use_crs" to use them
> [    0.112346] pci_root PNP0A03:00: host bridge window [io  0x0000-0x0cf7]
> (ignored)
> [    0.112348] pci_root PNP0A03:00: host bridge window [io  0x0d00-0xffff]
> (ignored)
> [    0.112351] pci_root PNP0A03:00: host bridge window [mem
> 0x000a0000-0x000bffff] (ignored)
> [    0.112353] pci_root PNP0A03:00: host bridge window [mem
> 0x000c0000-0x000dffff] (ignored)
> [    0.112355] pci_root PNP0A03:00: host bridge window [mem
> 0x40000000-0xfed0ffff] (ignored)
> [    0.112356] pci_bus 0000:00: scanning bus
...
> [    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
--
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/