Re: 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots

[Justin Piszcz]

On Fri, 12 Mar 2010, Yinghai Lu wrote:

> On Fri, Mar 12, 2010 at 4:56 AM, Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx> wrote:
> > On Fri, 12 Mar 2010, Justin Piszcz 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
>
> how about current linus' tree with pci=nocrs or pci=use_crs?

Hi, I saw your second e-mail, so it sounds like a bad board or something
that Linux does not have a quirk for yet, but in any case, per your
recommendations:

pci=nocrs:
http://home.comcast.net/~jpiszcz/20100312/dmesg-pci-nocrs.txt

pci=use_crs:
http://home.comcast.net/~jpiszcz/20100312/dmesg-use-crs.txt

No collision when pci=use_crs is used, BUT the system still crashes.

Instead of collision, it says this:

[    0.133598] PCI: pci_cache_line_size set to 64 bytes
[    0.133603] pci 0000:00:00.0: BAR 3: reserving [mem 0xe0000000-0xffffffff flags 0x120204] (d=0, p=0)
[    0.133606] pci 0000:00:00.0: no compatible bridge window for [mem 0xe0000000-0xffffffff 64bit]
[    0.133610] pci 0000:00:00.0: can't reserve [mem 0xe0000000-0xffffffff 64bit]
[    0.133617] pci 0000:00:11.0: BAR 0: reserving [io  0xff00-0xff07 flags 0x20101] (d=0, p=0)

[    0.133735] Expanded resource reserved due to conflict with PCI Bus 0000:00

Ideas?

Justin.