Problems with two r8169 nics

[David_Ingram]

I have a test server I am setting up the has 4 nics installed. 2 are onboard Intel using the e1000 driver. 2 are addons and are using the r8169 driver. The problem is that only 1 of the 2 r8169's succesfully loads on boot. See the following truncated dmesg output:

r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:08:03.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
r8169 0000:08:03.0: no PCI Express capability
eth0: RTL8169sc/8110sc at 0xffffc900125ac000, 00:0a:cd:1e:b2:83, XID 18000000 IRQ 16
ata_piix 0000:00:1f.2: version 2.13
ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
ata_piix 0000:00:1f.2: setting latency timer to 64
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:08:04.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
r8169 0000:08:04.0: BAR 1: can't reserve mem region [0xebef4000-0xebef40ff]
r8169 0000:08:04.0: could not request regions.
r8169 0000:08:04.0: PCI INT A disabled
scsi1 : ata_piix
r8169: probe of 0000:08:04.0 failed with error -16

I guess this is a bug with the driver? And if so is there a different kernel I could try out that might fix my problem?

Linux version 2.6.32-6-pve

Thanks in advance if anyone has any advice for me.

 

[tom]

post the output of pveversion -v, showing your full software version.

 

[David_Ingram]

Thanks for the reply Tom. Here is the output from pveversion -v:

root@cassiusclay:~# pveversion -v
pve-manager: 2.0-18 (pve-manager/2.0/16283a5a)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 2.0-55
pve-kernel-2.6.32-6-pve: 2.6.32-55
lvm2: 2.02.88-2pve1
clvm: 2.02.88-2pve1
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.6.0-1
redhat-cluster-pve: 3.1.8-3
pve-cluster: 1.0-17
qemu-server: 2.0-13
pve-firmware: 1.0-14
libpve-common-perl: 1.0-11
libpve-access-control: 1.0-5
libpve-storage-perl: 2.0-9
vncterm: 1.0-2
vzctl: 3.0.29-3pve8
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-1
ksm-control-daemon: 1.1-1

 

[tom]

software version looks fine, I just checked our very latest kernel, no update here.

can you try another slot for your add-on card (just a wild guess ...)

 

[David_Ingram]

I didn't have an extra slot, so I just switched out the slots that cards were in. Lo and behold everything works fine now. I wish I could I could say I understand why but I don't. Regardless, thanks for ideas Tom.

-Dave