From: Yinghai Lu <yinghai@kernel.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots [full dmesg]
Date: Fri, 12 Mar 2010 12:01:11 -0800 [thread overview]
Message-ID: <86802c441003121201y4c946fecrda5463b056f1ba58@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1003120809030.15732@p34.internal.lan>
On Fri, Mar 12, 2010 at 5:10 AM, Justin Piszcz <jpiszcz@lucidpixels.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@server) (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
next prev parent reply other threads:[~2010-03-12 20:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 10:25 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots Justin Piszcz
2010-03-12 10:49 ` Justin Piszcz
2010-03-12 10:57 ` Justin Piszcz
2010-03-12 12:44 ` Justin Piszcz
2010-03-12 12:56 ` Justin Piszcz
2010-03-12 13:10 ` 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots [full dmesg] Justin Piszcz
2010-03-12 20:01 ` Yinghai Lu [this message]
2010-03-12 20:02 ` Justin Piszcz
2010-03-12 20:27 ` Yinghai Lu
2010-03-12 20:34 ` Justin Piszcz
2010-03-12 20:39 ` Justin Piszcz
2010-03-12 21:30 ` 2.6.34-rc1: pci 0000:00:00.0: address space collision / spontaenous reboots [now 2.6.34-rc1] Justin Piszcz
2010-03-12 21:43 ` Yinghai Lu
2010-03-12 21:48 ` Justin Piszcz
2010-03-12 21:50 ` Yinghai Lu
2010-03-12 21:52 ` Justin Piszcz
2010-03-12 21:52 ` Yinghai Lu
2010-03-13 9:01 ` Justin Piszcz
2010-03-18 22:58 ` Bjorn Helgaas
2010-03-18 23:00 ` Justin Piszcz
2010-03-18 23:19 ` Bjorn Helgaas
2010-03-19 9:45 ` Justin Piszcz
2010-03-12 21:43 ` 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots [full dmesg] Yinghai Lu
2010-03-12 19:44 ` 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots Yinghai Lu
2010-03-12 20:32 ` Justin Piszcz
2010-03-12 21:10 ` Yinghai Lu
2010-03-12 21:59 ` Bjorn Helgaas
2010-03-12 22:07 ` Justin Piszcz
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=86802c441003121201y4c946fecrda5463b056f1ba58@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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®