2 link states coalesced

admbe

Hello everyone,

I have a 3 interface daughter board card that uses the RTL8110S chipset. The chipset is listed on the HCL here http://www.pfsense.com/index.php?id=37
The issue is that I am getting a "no carrier" message on some interfaces when they are indeed plugged in. I have tried PFsense Beta4, latest stable (1.0.1) and the latest 1.2 beta. The 1.2 beta does not show these messages, but experiences the same problem.

When booting, and when connected to the console, I get these messages.

re2: 2 link states coalesced
re2: 2 link states coalesced
re2: 2 link states coalesced
re2: 2 link states coalesced
re2: 2 link states coalesced
re1: 2 link states coalesced
re1: 2 link states coalesced
re1: 2 link states coalesced
re1: 2 link states coalesced
re1: 2 link states coalesced
re1: 2 link states coalesced
re1: 2 link states coalesced

I have done some searching and this seems to be a error specific to FreeBSD and may be driver related.

http://lists.freebsd.org/pipermail/freebsd-net/2006-January/009551.html
http://www.daemonnews.org/mailinglists/FreeBSD/freebsd-net/msg00025.html

# pciconf -lv
hostb0@pci0:0:0:        class=0x060000 card=0x03141106 chip=0x03141106 rev=0x00
hdr=0x00
    class    = bridge
    subclass = HOST-PCI
hostb1@pci0:0:1:        class=0x060000 card=0x00000000 chip=0x13141106 rev=0x00
hdr=0x00
    class    = bridge
    subclass = HOST-PCI
hostb2@pci0:0:2:        class=0x060000 card=0x00000000 chip=0x23141106 rev=0x00
hdr=0x00
    class    = bridge
    subclass = HOST-PCI
hostb3@pci0:0:3:        class=0x060000 card=0x00000000 chip=0x32081106 rev=0x00
hdr=0x00
    class    = bridge
    subclass = HOST-PCI
hostb4@pci0:0:4:        class=0x060000 card=0x00000000 chip=0x43141106 rev=0x00
hdr=0x00
    class    = bridge
    subclass = HOST-PCI
hostb5@pci0:0:7:        class=0x060000 card=0x00000000 chip=0x73141106 rev=0x00
hdr=0x00
    class    = bridge
    subclass = HOST-PCI
pcib1@pci0:1:0: class=0x060400 card=0x00000070 chip=0xb1981106 rev=0x00 hdr=0x01

    class    = bridge
    subclass = PCI-PCI
re0@pci0:9:0:   class=0x020000 card=0x10ec16f3 chip=0x816910ec rev=0x10 hdr=0x00

    class    = network
    subclass = ethernet
fwohci0@pci0:10:0:      class=0x0c0010 card=0x30441106 chip=0x30441106 rev=0x80
hdr=0x00
    class    = serial bus
    subclass = FireWire
re1@pci0:11:0:  class=0x020000 card=0x10ec16f3 chip=0x816910ec rev=0x10 hdr=0x00

    class    = network
    subclass = ethernet
re2@pci0:12:0:  class=0x020000 card=0x10ec16f3 chip=0x816910ec rev=0x10 hdr=0x00

    class    = network
    subclass = ethernet
atapci0@pci0:15:0:      class=0x01018f card=0x31491106 chip=0x31491106 rev=0x80
hdr=0x00
    class    = mass storage
    subclass = ATA
atapci1@pci0:15:1:      class=0x01018a card=0x05711106 chip=0x05711106 rev=0x06
hdr=0x00
    class    = mass storage
    subclass = ATA
isab0@pci0:17:0:        class=0x060100 card=0x32271106 chip=0x32271106 rev=0x00
hdr=0x00
    class    = bridge
    subclass = PCI-ISA
vr0@pci0:18:0:  class=0x020000 card=0x01021106 chip=0x30651106 rev=0x78 hdr=0x00

    class    = network
    subclass = ethernet
none0@pci1:0:0: class=0x030000 card=0x33441106 chip=0x33441106 rev=0x01 hdr=0x00

    class    = display
    subclass = VGA

I have tried to manually assign IRQ's in the possibility that this was resource realted, but the result was the same…

ANY help is appriciated!!

Thanks

admbe

I aslo want to add that the issue is inconsistent. all 3 interfaces may work for a 24 hour period, and then drop off. A more consistent situation is that when all are up, I will release one interface, when it renews it's address, it will show the no carrier message, then bounce back and forth from "up", to "no carrier".

Thanks