PCI Address Space Collision (11.4 and 12.2) Dell R320 Ethernet Interfaces

Hi

I am seeing the following message in the dmesg for the Dell R320 servers after booting.

pci 0000:02:00.0: Address Space Collision: [mem 0xdd000000 - 0xdd03ffff pref] conflicts with 0000:02:00.1

I have seen the same message using both openSUSE 11.4 x86_64 and openSUSE 12.2 x86_64

12.2
Under 12.2 the interfaces are still usable, however if yast is opened to the Network Devices page in order to configure
the Ethernet parameters, the system freezes twice for about 10 seconds each, then finally opens the page and allows the
interfaces to be configured.

11.4
In Yast under 11.4 the intefaces are shown but cannot be configured or deleted.
The results in the the Ethernet Interfaces not being setup and not even mentioned in the usev 70-persistent-net.rules file
No ifcfg-eth0 or ifcfg-eth1 config file are created in the /etc/sysconfig/network folder.

Is the conflict perhaps caused by the driver which is shown by 12.2 to be: tg3 ???

Is there someway to get this corrected for both the 12.2 and 11.4 distro’s of openSUSE?

Many thanks

:expressionless:

On 02/08/2013 02:56 PM, CNConrad wrote:
>
> 11.4

sorry, i can’t help you with the problem you posted about, but maybe i
can help you keep from getting script-kiddy kracked:

11.4 is past its end of life (cite:
http://en.opensuse.org/Lifetime) and no longer receiving
security patches through normal means (since November 2012!). It
therefore should not be
exposed to untrusted networks (like the internet) as it has numerous
known to the bad guys security problems.

However if it incorporates Evergreen, http://tinyurl.com/4aflkpy it is
good until July 2014!! and it is easy to switch it to Evergreen.


dd
openSUSE®, the “German Engineered Automobile” of operating systems!
http://tinyurl.com/DD-Caveat

On 2013-02-08 14:56, CNConrad wrote:
> Is there someway to get this corrected for both the 12.2 and 11.4
> distro’s of openSUSE?

11.4 is EOL, so no. Try the beta version, 12.3.

But this looks to me to be a hardware problem :-?


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

On 2013-02-08 16:10, dd wrote:
> However if it incorporates Evergreen, http://tinyurl.com/4aflkpy it is
> good until July 2014!! and it is easy to switch it to Evergreen.

Yes, however if there is a bug in the handling of his hardware it will
not be ever corrected in 11.4. His only practical chance there is 12.3,
if it is a bug.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

On 02/08/2013 02:56 PM, CNConrad wrote:
> Is there someway to get this corrected for both the 12.2 and 11.4
> distro’s of openSUSE?

i have not looked, but i guess the Dell R320 server is certified for
SUSE Linux Enterprise Server (SLES), and not for any version of
openSUSE…nor will it ever be…

so, the answer to your question above might best be: it probably is not
a problem with either SLES 10 or 11, and if the problem exists there
it is NO doubt it can be fixed by the SLES folks…talk with them, suse.com

the two products are not the same, not nearly…(if you are familiar
with Red Hat: openSUSE is like the Fedora to Red Hat, and not the
CentOS to Red Hat)


dd
openSUSE®, the “German Engineered Automobile” of operating systems!

Looks like you’ve got memory addressing problems! Do you have multiple (arrayed) NICs with that particular server?

This is a kernel issue and if it’s for multiple devices you may have a HW error, ex 2 devices sharing a PCI ID.
Error message on boot: Address space collision: host bridge window conflicts with Adaptor ROM - Alpine Linux
This user shows that it’s a issue that occurs in 2.6.34 and later, so I’d say that installing the new version won’t fix it. Fortunately, you only need to add “pci=nocrs” into the boot options for grub. And hopefully it’ll start addressing memory per-device for you!

Here’s a post on what it does -
Gentoo Forums :: View topic - Is pci=nocrs bad?

Hope this helps!

As ngschmidt notes, this is a memory addressing problem for a pci device.

But unlike all previous posts, I cannot see anything in your post that suggests your problem has anything to do with a networking device.

You likely need to post lines previous and after the error you posted.

Also, don’t know exactly how your error was captured and displayed or logged.

If not from the syslog, recommend analyzing that for errors.

TSU