Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    SOLVED: Nc380t not working after 2.2 upgrade

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    18 Posts 4 Posters 5.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K Offline
      keithmcp
      last edited by

      Here is the dmesg.boot file.  It looks like a driver issue as it is showing Reset failed and Controller reset failed and then PCI memory allocation failed. Hope it helps find the issue.

      Copyright © 1992-2014 The FreeBSD Project.
      Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
              The Regents of the University of California. All rights reserved.
      FreeBSD is a registered trademark of The FreeBSD Foundation.
      FreeBSD 10.1-RELEASE-p4 #0 36d7dec(releng/10.1)-dirty: Thu Jan 22 15:12:35 CST 2
      015
          root@pfsense-22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_
      SMP.10 amd64
      FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
      CPU: Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz (2128.05-MHz K8-class CPU)
        Origin = "GenuineIntel"  Id = 0x6f6  Family = 0x6  Model = 0xf  Stepping = 6
        Features=0xbfebfbff<fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,c<br>MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
        Features2=0xe3bd <sse3,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm>AMD Features=0x20100800 <syscall,nx,lm>AMD Features2=0x1 <lahf>VT-x: HLT,PAUSE
        TSC: P-state invariant, performance statistics
      real memory  = 4294967296 (4096 MB)
      avail memory = 4088528896 (3899 MB)
      Event timer "LAPIC" quality 400
      ACPI APIC Table: <ptltd   ="" apic ="">FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
      FreeBSD/SMP: 1 package(s) x 2 core(s)
      cpu0 (BSP): APIC ID:  0
      cpu1 (AP): APIC ID:  1
      ioapic0 <version 2.0="">irqs 0-23 on motherboard
      wlan: mac acl policy registered
      random: <software, yarrow="">initialized
      kbd1 at kbdmux0
      cryptosoft0: <software crypto="">on motherboard
      padlock0: No ACE support.
      acpi0: <ptltd  rsdt="">on motherboard
      acpi0: Power Button (fixed)
      cpu0: <acpi cpu="">on acpi0
      cpu1: <acpi cpu="">on acpi0
      atrtc0: <at realtime="" clock="">port 0x70-0x71 irq 8 on acpi0
      Event timer "RTC" frequency 32768 Hz quality 0
      attimer0: <at timer="">port 0x40-0x43,0x50-0x53 irq 0 on acpi0
      Timecounter "i8254" frequency 1193182 Hz quality 0
      Event timer "i8254" frequency 1193182 Hz quality 100
      Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
      acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
      pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
      pci0: <acpi pci="" bus="">on pcib0
      vgapci0: <vga-compatible display="">port 0x30c0-0x30c7 mem 0xd4000000-0xd40fffff,0
      xc0000000-0xcfffffff irq 16 at device 2.0 on pci0
      agp0: <intel 946gz="" svga="" controller="">on vgapci0
      agp0: aperture size is 256M, detected 7676k stolen memory
      vgapci0: Boot video device
      pcib1: <acpi pci-pci="" bridge="">irq 16 at device 28.0 on pci0
      pcib1: failed to allocate initial memory window: 0xd0000000-0xd3ffffff
      pci1: <acpi pci="" bus="">on pcib1
      pcib2: <acpi pci-pci="" bridge="">at device 0.0 on pci1
      pcib2: failed to allocate initial memory window: 0xd0000000-0xd1ffffff
      pci2: <acpi pci="" bus="">on pcib2
      bce0: <hp nc380t="" pcie="" dp="" multifunc="" gig="" server="" adapter="" (a2)="">irq 16 at device 4.0
      on pci2
      bce0: /usr/pfSensesrc/src/sys/dev/bce/if_bce.c(5034): Reset failed!
      bce0: /usr/pfSensesrc/src/sys/dev/bce/if_bce.c(1305): Controller reset failed!
      device_attach: bce0 attach returned 6
      pcib3: <pci-pci bridge="">at device 0.2 on pci1
      pcib3: failed to allocate initial memory window: 0xd2000000-0xd3ffffff
      pci3: <pci bus="">on pcib3
      bce0: <hp nc380t="" pcie="" dp="" multifunc="" gig="" server="" adapter="" (a2)="">irq 17 at device 5.0
      on pci3
      bce0: 0x2000000 bytes of rid 0x10 res 3 failed (0, 0xffffffffffffffff).
      bce0: /usr/pfSensesrc/src/sys/dev/bce/if_bce.c(1060): PCI memory allocation fail
      ed
      device_attach: bce0 attach returned 6
      pcib4: <acpi pci-pci="" bridge="">irq 16 at device 28.4 on pci0
      pci4: <acpi pci="" bus="">on pcib4
      em0: <intel(r) 1000="" pro="" network="" connection="" 7.4.2="">port 0x4000-0x401f mem 0xd4100
      000-0xd411ffff irq 16 at device 0.0 on pci4
      em0: Using an MSI interrupt
      pcib5: <acpi pci-pci="" bridge="">irq 17 at device 28.5 on pci0
      pci5: <acpi pci="" bus="">on pcib5
      em1: <intel(r) 1000="" pro="" network="" connection="" 7.4.2="">port 0x5000-0x501f mem 0xd4200
      000-0xd421ffff irq 17 at device 0.0 on pci5
      em1: Using an MSI interrupt
      uhci0: <intel 82801g="" (ich7)="" usb="" controller="" usb-a="">port 0x3000-0x301f irq 16 at d
      evice 29.0 on pci0
      usbus0 on uhci0
      uhci1: <intel 82801g="" (ich7)="" usb="" controller="" usb-b="">port 0x3020-0x303f irq 17 at d
      evice 29.1 on pci0
      usbus1 on uhci1
      uhci2: <intel 82801g="" (ich7)="" usb="" controller="" usb-c="">port 0x3040-0x305f irq 18 at d
      evice 29.2 on pci0
      usbus2 on uhci2
      uhci3: <intel 82801g="" (ich7)="" usb="" controller="" usb-d="">port 0x3060-0x307f irq 19 at d
      evice 29.3 on pci0
      usbus3 on uhci3
      ehci0: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller="">mem 0xd4500000-0xd45003ff irq
      16 at device 29.7 on pci0
      usbus4: EHCI version 1.0
      usbus4 on ehci0
      pcib6: <acpi pci-pci="" bridge="">at device 30.0 on pci0
      pci6: <acpi pci="" bus="">on pcib6
      isab0: <pci-isa bridge="">at device 31.0 on pci0
      isa0: <isa bus="">on isab0
      atapci0: <intel ich7="" sata300="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x37
      6,0x30b0-0x30bf at device 31.2 on pci0
      ata0: <ata channel="">at channel 0 on atapci0
      ata1: <ata channel="">at channel 1 on atapci0
      acpi_button0: <power button="">on acpi0
      atkbdc0: <keyboard controller="" (i8042)="">port 0x60,0x64 irq 1 on acpi0
      atkbd0: <at keyboard="">irq 1 on atkbdc0
      kbd0 at atkbd0
      atkbd0: [GIANT-LOCKED]
      orm0: <isa option="" roms="">at iomem 0xc0000-0xcafff,0xcb000-0xcbfff on isa0
      sc0: <system console="">at flags 0x100 on isa0
      sc0: VGA <16 virtual consoles, flags=0x300>
      vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
      ppc0: cannot reserve I/O port range
      est0: <enhanced speedstep="" frequency="" control="">on cpu0
      est: CPU supports Enhanced Speedstep, but is not recognized.
      est: cpu_vendor GenuineIntel, msr 828082806000828
      device_attach: est0 attach returned 6
      p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
      est1: <enhanced speedstep="" frequency="" control="">on cpu1
      est: CPU supports Enhanced Speedstep, but is not recognized.
      est: cpu_vendor GenuineIntel, msr 828082806000828
      device_attach: est1 attach returned 6
      p4tcc1: <cpu frequency="" thermal="" control="">on cpu1
      Timecounters tick every 1.000 msec
      IPsec: Initialized Security Association Processing.
      random: unblocking device.
      usbus0: 12Mbps Full Speed USB v1.0
      usbus1: 12Mbps Full Speed USB v1.0
      usbus2: 12Mbps Full Speed USB v1.0
      usbus3: 12Mbps Full Speed USB v1.0
      usbus4: 480Mbps High Speed USB v2.0
      ugen2.1: <intel>at usbus2
      uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus2
      ugen1.1: <intel>at usbus1
      uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
      ugen0.1: <intel>at usbus0
      uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
      ugen4.1: <intel>at usbus4
      uhub3: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus4
      Copyright © 1992-2014 The FreeBSD Project.
      Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
              The Regents of the University of California. All rights reserved.
      FreeBSD is a registered trademark of The FreeBSD Foundation.
      FreeBSD 10.1-RELEASE-p4 #0 36d7dec(releng/10.1)-dirty: Thu Jan 22 15:12:35 CST 2
      015
          root@pfsense-22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_
      SMP.10 amd64
      FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
      CPU: Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz (2128.05-MHz K8-class CPU)
        Origin = "GenuineIntel"  Id = 0x6f6  Family = 0x6  Model = 0xf  Stepping = 6
        Features=0xbfebfbff<fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,c<br>MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
        Features2=0xe3bd <sse3,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm>AMD Features=0x20100800 <syscall,nx,lm>AMD Features2=0x1 <lahf>VT-x: HLT,PAUSE
        TSC: P-state invariant, performance statistics
      real memory  = 4294967296 (4096 MB)
      avail memory = 4088528896 (3899 MB)
      Event timer "LAPIC" quality 400
      ACPI APIC Table: <ptltd   ="" apic ="">FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs</ptltd ></lahf></syscall,nx,lm></sse3,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,c<br></intel></intel></intel></intel></intel></intel></intel></intel></cpu></enhanced></cpu></enhanced></generic></system></isa></at></keyboard></power></ata></ata></intel></isa></pci-isa></acpi></acpi></intel></intel></intel></intel></intel></intel(r)></acpi></acpi></intel(r)></acpi></acpi></hp></pci></pci-pci></hp></acpi></acpi></acpi></acpi></intel></vga-compatible></acpi></acpi></at></at></acpi></acpi></ptltd ></software></software,></version></ptltd ></lahf></syscall,nx,lm></sse3,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,c<br>

      If it doesn't fly Mach 1, it's not worth flying!!!

      1 Reply Last reply Reply Quote 0
      • stephenw10S Offline
        stephenw10 Netgate Administrator
        last edited by

        Well interesting that your box finds the Intel NICs no problem. Can you change the slot the card is in?
        If you look at the logs the OS finds PCI bus 2 and fails to allocate some memory. Then it finds a bce NIC on PCI bus 2 and fails to attach to it. Then it finds PCI bus and again fails to allocate memory before finding another bce NIC on it and failing to attach.

        Steve

        1 Reply Last reply Reply Quote 0
        • K Offline
          keithmcp
          last edited by

          It is interesting that it does that.  Almost like it is trying to start but can't and tries again.  Unfortunately, I cannot change slots as this system has only one PCI Express slot. Maybe something with the driver in Freebsd 10.1 versus 8.3?

          If it doesn't fly Mach 1, it's not worth flying!!!

          1 Reply Last reply Reply Quote 0
          • K Offline
            keithmcp
            last edited by

            Should I file a bug report on this one?

            If it doesn't fly Mach 1, it's not worth flying!!!

            1 Reply Last reply Reply Quote 0
            • stephenw10S Offline
              stephenw10 Netgate Administrator
              last edited by

              This is almost certainly a FreeBSD bug rather than a pfSense bug. If you can, try running FreeBSD 10.1. If that does exactly the same thing then file a bug report there.

              Steve

              1 Reply Last reply Reply Quote 0
              • C Offline
                charliem
                last edited by

                @stephenw10:

                Looks like you may have hit the same thing as this:
                https://forum.pfsense.org/index.php?topic=84909.0
                I don't think a solution has been found yet.  :(

                Steve

                Edit: Typo

                Yes, a workaround solution was found, suggested by John Baldwin:
                https://forum.pfsense.org/index.php?topic=84909.msg475793#msg475793  Specifically:

                hint.agp.0.disabled=1
                in loader.conf fixes the problem. :)

                Interesting, both systems have the same agp0 video device, and the comments in the bug report implicate agp, so maybe that will work here too.  If that doesn't work, you could instead try:

                debug.acpi.disabled="hostres"

                I'm not sure debug.acpi.disabled is still an option on FreeBSD 10.1; it was on 9.0.  Even if it doesn't fix the problem, looking at the dmesg difference with and without the debug option set may provide some insight.  Oh, and those changes should go into /boot/loader.conf.local rather than /boot/loader.conf (otherwise the change(s) would not survive an upgrade).

                1 Reply Last reply Reply Quote 0
                • stephenw10S Offline
                  stephenw10 Netgate Administrator
                  last edited by

                  That was only a few weeks ago. Clearly my memory is failing.  ::)

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • K Offline
                    keithmcp
                    last edited by

                    Thanks charliem that did the trick. ;D

                    Yes, a workaround solution was found, suggested by John Baldwin:
                    https://forum.pfsense.org/index.php?topic=84909.msg475793#msg475793  Specifically:
                    Quote

                    hint.agp.0.disabled=1
                        in loader.conf fixes the problem. :)

                    The card is now found and working just like before. dmesg.boot now shows the card and both interfaces are showing up in pfsense.  Thanks to John Baldwin too.  My pfsense box is back!!

                    If it doesn't fly Mach 1, it's not worth flying!!!

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S Offline
                      stephenw10 Netgate Administrator
                      last edited by

                      Nice.  :)
                      You should put that in /boot/loader.conf.local, create the file. That gets copied across an update and is intended for custom loader tweaks like this.

                      Steve

                      1 Reply Last reply Reply Quote 0
                      • K Offline
                        keithmcp
                        last edited by

                        I originally had it in the loader.conf and then read the entire post and saw that it should be in the .local file (as you mentioned).  I created the .local file and added that plus the Intel license ack stuff also. So faro so good.  :D

                        If it doesn't fly Mach 1, it's not worth flying!!!

                        1 Reply Last reply Reply Quote 0
                        • R Offline
                          rekd0514
                          last edited by

                          This fix does not seem to be working for me with a EXPI9301CT card. Any other ideas?

                          1 Reply Last reply Reply Quote 0
                          • stephenw10S Offline
                            stephenw10 Netgate Administrator
                            last edited by

                            You're seeing the same memory allocation error in the boot log?

                            Steve

                            1 Reply Last reply Reply Quote 0
                            • R Offline
                              rekd0514
                              last edited by

                              Never mind, I think the NIC randomly died on me. It is not being detected in Windows on another PC either now.

                              Just for future reference, how would you go about getting the dmesg.boot file or edit the loader.conf if you don't have access to the GUI. Can you do this by shell/SSH somehow?  I don't have a VLAN capable switch, so I don't think I can get access to pfsense with only 1 NIC installed in it.

                              1 Reply Last reply Reply Quote 0
                              • stephenw10S Offline
                                stephenw10 Netgate Administrator
                                last edited by

                                Yes, if you have ssh access you can use SCP to get the files directly from a connected client.

                                If you only have local console access you can view the boot files like:

                                cat /var/log/dmesg.boot
                                

                                Or edit the loader.conf (or better loader.conf.local) like:

                                ee /boot/loader.conf.local
                                

                                That will use the built in EasyEditor but you could use vi instead.

                                Steve

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post
                                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.