[pfSense 1.2.3] GigEth port - no carrier



  • Hi all,

    I've searched this forum to "no carrier" posts, however I haven't find the answer so I created this new topic.

    We've VIA NFR7500 Appliance with pfSense 1.2.3 installed on it. We've set up three of five interfaces w/o problems and now we'd like to set up nex one, however the interface's status is "no carrier". The port on the switch and Cat.5e cable is good, so the problem is in pfSense/hardware.

    Here is all info that cross my mind:

    
    uname -a 
    
    FreeBSD <hostname>7.2-RELEASE-p5 FreeBSD 7.2-RELEASE-p5 #0: Mon Dec  7 23:21:27 EST 2009     sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.7.i386  i386
    
    -----
    dmesg | grep CPU
    
    CPU: VIA C7 Processor 1500MHz (1496.26-MHz 686-class CPU)
    cpu0: <acpi cpu="">on acpi0
    
    -----
    dmesg | grep vge
    
    vge0: <via networking="" gigabit="" ethernet="">port 0xcc00-0xccff mem 0xdfcff000-0xdfcff0ff irq 24 at device 0.0 on pci2
    miibus0: <mii bus="">on vge0
    vge0: WARNING: using obsoleted if_watchdog interface
    vge0: Ethernet address: 00:40:63:fd:b4:38
    vge0: [ITHREAD]
    vge1: <via networking="" gigabit="" ethernet="">port 0xbc00-0xbcff mem 0xdfeff000-0xdfeff0ff irq 28 at device 0.0 on pci3
    miibus1: <mii bus="">on vge1
    vge1: WARNING: using obsoleted if_watchdog interface
    vge1: Ethernet address: 00:40:63:fd:b4:37
    vge1: [ITHREAD]
    vge2: <via networking="" gigabit="" ethernet="">port 0x9c00-0x9cff mem 0xdfaff000-0xdfaff0ff irq 19 at device 14.0 on pci4
    miibus2: <mii bus="">on vge2
    vge2: WARNING: using obsoleted if_watchdog interface
    vge2: Ethernet address: 00:40:63:fd:b4:34
    vge2: [ITHREAD]
    vge3: <via networking="" gigabit="" ethernet="">port 0x8c00-0x8cff mem 0xc7fff000-0xc7fff0ff irq 16 at device 0.0 on pci129
    miibus3: <mii bus="">on vge3
    vge3: WARNING: using obsoleted if_watchdog interface
    vge3: Ethernet address: 00:40:63:fd:b4:35
    vge3: [ITHREAD]
    vge4: <via networking="" gigabit="" ethernet="">port 0x7c00-0x7cff mem 0xc7dff000-0xc7dff0ff irq 16 at device 0.0 on pci130
    miibus4: <mii bus="">on vge4
    vge4: WARNING: using obsoleted if_watchdog interface
    vge4: Ethernet address: 00:40:63:fd:b4:36
    vge4: [ITHREAD]
    vge2: link state changed to UP
    vge0: link state changed to UP
    vge1: link state changed to UP
    
    -----
    netstat -sI vge3
    
    ip6 on vge3:
    	0 total input datagrams
    	0 datagrams with invalid header received
    	0 datagrams exceeded MTU received
    	0 datagrams with no route received
    	0 datagrams with invalid dst received
    	0 datagrams with unknown proto received
    	0 truncated datagrams received
    	0 input datagrams discarded
    	0 datagrams delivered to an upper layer protocol
    	0 datagrams forwarded to this interface
    	3 datagrams sent from an upper layer protocol
    	0 total discarded output datagrams
    	0 output datagrams fragmented
    	0 output datagrams failed on fragment
    	0 output datagrams succeeded on fragment
    	0 incoming datagrams fragmented
    	0 datagrams reassembled
    	0 datagrams failed on reassembly
    	0 multicast datagrams received
    	3 multicast datagrams sent
    icmp6 on vge3:
    	0 total input messages
    	0 total input error messages
    	0 input destination unreachable errors
    	0 input administratively prohibited errors
    	0 input time exceeded errors
    	0 input parameter problem errors
    	0 input packet too big errors
    	0 input echo requests
    	0 input echo replies
    	0 input router solicitations
    	0 input router advertisements
    	0 input neighbor solicitations
    	0 input neighbor advertisements
    	0 input redirects
    	0 input MLD queries
    	0 input MLD reports
    	0 input MLD dones
    	3 total output messages
    	0 total output error messages
    	0 output destination unreachable errors
    	0 output administratively prohibited errors
    	0 output time exceeded errors
    	0 output parameter problem errors
    	0 output packet too big errors
    	0 output echo requests
    	0 output echo replies
    	0 output router solicitations
    	0 output router advertisements
    	1 output neighbor solicitation
    	0 output neighbor advertisements
    	0 output redirects
    	0 output MLD queries
    	2 output MLD reports
    	0 output MLD dones
    
    -----
    ifconfig -m vge3
    
    vge3: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
    	options=1b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging>capabilities=5b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,polling>ether 00:40:63:fd:b4:35
    	inet6 fe80::240:63ff:fefd:b435%vge3 prefixlen 64 scopeid 0x4 
    	media: Ethernet autoselect (none)
    	status: no carrier
    	supported media:
    		media autoselect
    		media 1000baseTX mediaopt full-duplex
    		media 1000baseTX
    		media 100baseTX mediaopt full-duplex
    		media 100baseTX
    		media 10baseT/UTP mediaopt full-duplex
    		media 10baseT/UTP</rxcsum,txcsum,vlan_mtu,vlan_hwtagging,polling></rxcsum,txcsum,vlan_mtu,vlan_hwtagging></up,broadcast,running,simplex,multicast></mii></via></mii></via></mii></via></mii></via></mii></via></acpi></hostname> 
    

    We're using vge0, vge1 and vge2, now we're trying to set up vge3.

    Any hints and/or suggestions?

    Thanks!


  • Netgate Administrator

    You could try going to 2.0 with updated drivers.
    I notice that vge3 and vge4 are both using IRQ 16, not neccessarily a problem but the others are on separate irqs.

    Does the other interface, vge4, behave similarly?

    Steve



  • Hi Steve,

    thanks for reply! I'm afraid the upgrade is not possible at this moment - it's heavily used box and I can't afford the upgrade and potential problem solving…

    However, the vge4 is behaving the same way. As I understood from the datasheet, vge0 is separate PCI port and vge1-4 are PCIe ports - may be single quad-port chip, I do not know, but most probably it seems as two dual-port chips - so I assume it's not a driver issue.

    I'll try to schedule the shutdown of the box and try to change the IRQ of the fourth port.

    If there is any other information needed, please, let me know.

    Thanks!



  • When you connect vge3 and vge4 to something else does the other thing see carrier?

    What do the LED status lights (if any) on vge3 and vge4 sockets indicate when they are connected to something else?

    Please provide the output from pSense shell command pciconf -l -v. Perhaps vge3 and vge4 are different revisions from the other ports and there might be something in the driver edit history about that.



  • Hi wallabybob,
    thanks for reply!

    There is no mark of carrier, no LED is lighting or blinking.
    See below the result of command you asked for. vge0, vge1 and vge2 is working w/o problems, vge3 and vge4 have this issue.

    $ pciconf -l -v
    hostb0@pci0:0:0:0:	class=0x060000 card=0xaa0d1106 chip=0x03641106 rev=0x00 hdr=0x00
        class      = bridge
        subclass   = HOST-PCI
    hostb1@pci0:0:0:1:	class=0x060000 card=0x00000000 chip=0x13641106 rev=0x00 hdr=0x00
        class      = bridge
        subclass   = HOST-PCI
    hostb2@pci0:0:0:2:	class=0x060000 card=0x00000000 chip=0x23641106 rev=0x00 hdr=0x00
        class      = bridge
        subclass   = HOST-PCI
    hostb3@pci0:0:0:3:	class=0x060000 card=0x00000000 chip=0x33641106 rev=0x00 hdr=0x00
        class      = bridge
        subclass   = HOST-PCI
    hostb4@pci0:0:0:4:	class=0x060000 card=0x00000000 chip=0x43641106 rev=0x00 hdr=0x00
        class      = bridge
        subclass   = HOST-PCI
    ioapic0@pci0:0:0:5:	class=0x080020 card=0x00000000 chip=0x53641106 rev=0x00 hdr=0x00
        class      = base peripheral
        subclass   = interrupt controller
    hostb5@pci0:0:0:6:	class=0x060000 card=0x00000000 chip=0x63641106 rev=0x00 hdr=0x00
        class      = bridge
        subclass   = HOST-PCI
    hostb6@pci0:0:0:7:	class=0x060000 card=0x00000000 chip=0x73641106 rev=0x00 hdr=0x00
        class      = bridge
        subclass   = HOST-PCI
    pcib1@pci0:0:1:0:	class=0x060400 card=0x00000000 chip=0xb1981106 rev=0x00 hdr=0x01
        class      = bridge
        subclass   = PCI-PCI
    pcib2@pci0:0:2:0:	class=0x060400 card=0xc3231106 chip=0xa3641106 rev=0x80 hdr=0x01
        class      = bridge
        subclass   = PCI-PCI
    pcib3@pci0:0:3:0:	class=0x060400 card=0xc3231106 chip=0xc3641106 rev=0x80 hdr=0x01
        class      = bridge
        subclass   = PCI-PCI
    atapci0@pci0:0:15:0:	class=0x010601 card=0x33491106 chip=0x62871106 rev=0x20 hdr=0x00
        class      = mass storage
        subclass   = SATA
    atapci1@pci0:0:15:1:	class=0x01018a card=0x05711106 chip=0x05711106 rev=0x07 hdr=0x00
        class      = mass storage
        subclass   = ATA
    uhci0@pci0:0:16:0:	class=0x0c0300 card=0x30381106 chip=0x30381106 rev=0x91 hdr=0x00
        class      = serial bus
        subclass   = USB
    uhci1@pci0:0:16:1:	class=0x0c0300 card=0x30381106 chip=0x30381106 rev=0x91 hdr=0x00
        class      = serial bus
        subclass   = USB
    uhci2@pci0:0:16:2:	class=0x0c0300 card=0x30381106 chip=0x30381106 rev=0x91 hdr=0x00
        class      = serial bus
        subclass   = USB
    uhci3@pci0:0:16:3:	class=0x0c0300 card=0x30381106 chip=0x30381106 rev=0x91 hdr=0x00
        class      = serial bus
        subclass   = USB
    ehci0@pci0:0:16:4:	class=0x0c0320 card=0x31041106 chip=0x31041106 rev=0x90 hdr=0x00
        class      = serial bus
        subclass   = USB
    isab0@pci0:0:17:0:	class=0x060100 card=0xaa0d1106 chip=0x32871106 rev=0x00 hdr=0x00
        class      = bridge
        subclass   = PCI-ISA
    hostb7@pci0:0:17:7:	class=0x060000 card=0x287e1106 chip=0x287e1106 rev=0x00 hdr=0x00
        class      = bridge
        subclass   = HOST-PCI
    hostb8@pci0:0:19:0:	class=0x060000 card=0x00000000 chip=0x287b1106 rev=0x00 hdr=0x00
        class      = bridge
        subclass   = HOST-PCI
    pcib4@pci0:0:19:1:	class=0x060401 card=0x00000000 chip=0x287a1106 rev=0x00 hdr=0x01
        class      = bridge
        subclass   = PCI-PCI
    vgapci0@pci0:1:0:0:	class=0x030000 card=0x33711106 chip=0x33711106 rev=0x01 hdr=0x00
        class      = display
        subclass   = VGA
    vge0@pci0:2:0:0:	class=0x020000 card=0x01101106 chip=0x31191106 rev=0x82 hdr=0x00
        class      = network
        subclass   = ethernet
    vge1@pci0:3:0:0:	class=0x020000 card=0x01101106 chip=0x31191106 rev=0x82 hdr=0x00
        class      = network
        subclass   = ethernet
    vge2@pci0:4:14:0:	class=0x020000 card=0x01101106 chip=0x31191106 rev=0x11 hdr=0x00
        class      = network
        subclass   = ethernet
    pcib6@pci0:128:0:0:	class=0x060400 card=0x287c1106 chip=0x287c1106 rev=0x00 hdr=0x01
        class      = bridge
        subclass   = PCI-PCI
    pcib7@pci0:128:0:1:	class=0x060400 card=0x287d1106 chip=0x287d1106 rev=0x00 hdr=0x01
        class      = bridge
        subclass   = PCI-PCI
    vge3@pci0:129:0:0:	class=0x020000 card=0x01101106 chip=0x31191106 rev=0x82 hdr=0x00
        class      = network
        subclass   = ethernet
    vge4@pci0:130:0:0:	class=0x020000 card=0x01101106 chip=0x31191106 rev=0x82 hdr=0x00
        class      = network
        subclass   = ethernet
    
    


  • @tata_tulen:

    $ pciconf -l -v
    vge0@pci0:2:0:0:	class=0x020000 card=0x01101106 chip=0x31191106 rev=0x82 hdr=0x00
        class      = network
        subclass   = ethernet
    vge1@pci0:3:0:0:	class=0x020000 card=0x01101106 chip=0x31191106 rev=0x82 hdr=0x00
        class      = network
        subclass   = ethernet
    vge2@pci0:4:14:0:	class=0x020000 card=0x01101106 chip=0x31191106 rev=0x11 hdr=0x00
        class      = network
        subclass   = ethernet
    vge3@pci0:129:0:0:	class=0x020000 card=0x01101106 chip=0x31191106 rev=0x82 hdr=0x00
        class      = network
        subclass   = ethernet
    vge4@pci0:130:0:0:	class=0x020000 card=0x01101106 chip=0x31191106 rev=0x82 hdr=0x00
        class      = network
        subclass   = ethernet
    
    

    vge3 and vge4 (which don't work) have the same chip id and rev as vge0 and vge1 which work so different revs doesn't look likely to be a problem.

    Have you done a search on the board model number to see if anyone else is reporting similar problems? Is the BIOS up to date?



  • Hi wallabybob,

    it seems like I'm the only one who runs pfSense on this VIA MB or has problem with it. I've found just this thread on this forum :)

    We'd noticed this behaviour seems like the LAN Bypass feature is turned on - luckily we'll maybe have a chance to check the BIOS configuration and revision tomorrow.

    I'll let you in.


Log in to reply