Intel x520-DP SFP+ Not Detected

Status
Not open for further replies.
Joined
Mar 26, 2014
Messages
6
We recently replaced our Intel X540 10Gbps Ethernet cards with Intel X520 10Gbps SFP+ cards. Both are supported by FreeBSDs 10Gb Intel Driver.

FreeNAS is not displaying the cards. ifconfig -a does not list them.

When I do a devinfo -v, I see a lot of " unknown pnpinfo _HID=ACPI0007 _UID=0 at handle=\_SB_.SCK3.C312"

Is there anything special that needs to be done for the x520 series adapters?

 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
Nope. It should "just work".

What FreeNAS version are you using? Are you using the x86 or x64 version?

What does dmesg say about these cards?
 
Joined
Mar 26, 2014
Messages
6
I am running FreeNAS-9.2.1.3-RELEASE-x64.

I am currently upgrading to .5

This is what looks related in DMESG:

ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahcich3: <AHCI channel> at channel 3 on ahci0
ahcich4: <AHCI channel> at channel 4 on ahci0
ahcich5: <AHCI channel> at channel 5 on ahci0
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
pci0: <dasp> at device 31.6 (no driver attached)
pcib8: <ACPI Host-PCI bridge> on acpi0
pci255: <ACPI PCI bus> on pcib8
pci255: <base peripheral> at device 8.0 (no driver attached)
pci255: <base peripheral> at device 8.3 (no driver attached)
pci255: <base peripheral> at device 8.4 (no driver attached)
pci255: <base peripheral> at device 9.0 (no driver attached)
pci255: <base peripheral> at device 9.3 (no driver attached)
pci255: <base peripheral> at device 9.4 (no driver attached)
pci255: <base peripheral> at device 10.0 (no driver attached)
pci255: <base peripheral> at device 10.1 (no driver attached)
pci255: <base peripheral> at device 10.2 (no driver attached)
pci255: <base peripheral> at device 10.3 (no driver attached)
pci255: <base peripheral> at device 11.0 (no driver attached)
pci255: <base peripheral> at device 11.3 (no driver attached)
pci255: <base peripheral> at device 12.0 (no driver attached)
pci255: <base peripheral> at device 12.1 (no driver attached)
pci255: <base peripheral> at device 12.6 (no driver attached)
pci255: <base peripheral> at device 12.7 (no driver attached)
pci255: <base peripheral> at device 13.0 (no driver attached)
pci255: <base peripheral> at device 13.1 (no driver attached)
pci255: <base peripheral> at device 13.6 (no driver attached)
pci255: <base peripheral> at device 14.0 (no driver attached)
pci255: <dasp> at device 14.1 (no driver attached)
pci255: <base peripheral> at device 15.0 (no driver attached)
pci255: <base peripheral> at device 15.1 (no driver attached)
pci255: <base peripheral> at device 15.2 (no driver attached)
pci255: <base peripheral> at device 15.3 (no driver attached)
pci255: <base peripheral> at device 15.4 (no driver attached)
pci255: <base peripheral> at device 15.5 (no driver attached)
pci255: <base peripheral> at device 15.6 (no driver attached)
pci255: <base peripheral> at device 16.0 (no driver attached)
pci255: <base peripheral> at device 16.1 (no driver attached)
pci255: <base peripheral> at device 16.2 (no driver attached)
pci255: <base peripheral> at device 16.3 (no driver attached)
pci255: <base peripheral> at device 16.4 (no driver attached)
pci255: <base peripheral> at device 16.5 (no driver attached)
pci255: <base peripheral> at device 16.6 (no driver attached)
pci255: <base peripheral> at device 16.7 (no driver attached)
pci255: <base peripheral> at device 17.0 (no driver attached)
pci255: <base peripheral> at device 19.0 (no driver attached)
pci255: <dasp> at device 19.1 (no driver attached)
pci255: <dasp> at device 19.4 (no driver attached)
pci255: <dasp> at device 19.5 (no driver attached)
pci255: <base peripheral> at device 19.6 (no driver attached)
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
That is a whole *lot* of hardware that's not attaching. Can you post your system specs/hardware? Something seems very wrong here.
 
Joined
Mar 26, 2014
Messages
6
The Chassis/Motherboard is a SUPERMICRO SSG-6047R-E1R24L 4U. It has an LSI 2308 in IT-Mode (from the factory). Everything appears to be working besides the x520 Adapter. Performance has been great.


Here are the specifications:
Intel Xeon Quad Core 2.4GHz
128GB of DDR3 1600 ECC Registered RAM
Intel X520-DP SFP+ NIC
18x 1TB WD Velociraptors
2x Samsung 1TB 840EVO SSDs (L2ARC)
2x Intel Cherryville 240GB SSDs Mirrored (ZIL)
Nothing else besides that...
 
Joined
Mar 26, 2014
Messages
6
Here is the full dmesg:

Copyright (c) 1992-2013 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 9.2-RELEASE-p4 #0 r262572+17a4d3d: Wed Apr 23 10:09:38 PDT 2014
root@build3.ixsystems.com:/tank/home/jkh/build/9.2.1/freenas/os-base/amd64/fusion/jkh/9.2.1/freenas/FreeBSD/src/sys/FREENAS.amd64 amd64
gcc version 4.2.1 20070831 patched [FreeBSD]
CPU: Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz (2400.05-MHz K8-class CPU)
Origin = "GenuineIntel" Id = 0x206d7 Family = 0x6 Model = 0x2d Stepping = 7
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0x1fbee3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX>
AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
AMD Features2=0x1<LAHF>
TSC: P-state invariant, performance statistics
real memory = 137438953472 (131072 MB)
avail memory = 132942925824 (126784 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: < >
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 2
cpu2 (AP): APIC ID: 4
cpu3 (AP): APIC ID: 6
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
aesni0: <AES-CBC,AES-XTS> on motherboard
padlock0: No ACE support.
acpi0: <SUPERM SMCI--MB> on motherboard
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 550
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
Event timer "HPET3" frequency 14318180 Hz quality 440
Event timer "HPET4" frequency 14318180 Hz quality 440
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 26 at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> irq 32 at device 2.0 on pci0
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> irq 32 at device 2.2 on pci0
pci3: <ACPI PCI bus> on pcib3
mps0: <LSI SAS2308> port 0xe000-0xe0ff mem 0xfba40000-0xfba4ffff,0xfba00000-0xfba3ffff irq 34 at device 0.0 on pci3
mps0: Firmware: 16.00.01.00, Driver: 16.00.00.00-fbsd
mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
pcib4: <ACPI PCI-PCI bridge> irq 40 at device 3.0 on pci0
pci4: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> irq 40 at device 3.2 on pci0
pci5: <ACPI PCI bus> on pcib5
igb0: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0xd060-0xd07f mem 0xfbb60000-0xfbb7ffff,0xfbb8c000-0xfbb8ffff irq 42 at device 0.0 on pci5
igb0: Using MSIX interrupts with 5 vectors
igb0: Ethernet address: 00:25:90:e7:f2:d4
igb0: Bound queue 0 to cpu 0
igb0: Bound queue 1 to cpu 1
igb0: Bound queue 2 to cpu 2
igb0: Bound queue 3 to cpu 3
igb1: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0xd040-0xd05f mem 0xfbb40000-0xfbb5ffff,0xfbb88000-0xfbb8bfff irq 45 at device 0.1 on pci5
igb1: Using MSIX interrupts with 5 vectors
igb1: Ethernet address: 00:25:90:e7:f2:d5
igb1: Bound queue 0 to cpu 0
igb1: Bound queue 1 to cpu 1
igb1: Bound queue 2 to cpu 2
igb1: Bound queue 3 to cpu 3
igb2: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0xd020-0xd03f mem 0xfbb20000-0xfbb3ffff,0xfbb84000-0xfbb87fff irq 44 at device 0.2 on pci5
igb2: Using MSIX interrupts with 5 vectors
igb2: Ethernet address: 00:25:90:e7:f2:d6
igb2: Bound queue 0 to cpu 0
igb2: Bound queue 1 to cpu 1
igb2: Bound queue 2 to cpu 2
igb2: Bound queue 3 to cpu 3
igb3: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0xd000-0xd01f mem 0xfbb00000-0xfbb1ffff,0xfbb80000-0xfbb83fff irq 46 at device 0.3 on pci5
igb3: Using MSIX interrupts with 5 vectors
igb3: Ethernet address: 00:25:90:e7:f2:d7
igb3: Bound queue 0 to cpu 0
igb3: Bound queue 1 to cpu 1
igb3: Bound queue 2 to cpu 2
igb3: Bound queue 3 to cpu 3
pci0: <base peripheral> at device 4.0 (no driver attached)
pci0: <base peripheral> at device 4.1 (no driver attached)
pci0: <base peripheral> at device 4.2 (no driver attached)
pci0: <base peripheral> at device 4.3 (no driver attached)
pci0: <base peripheral> at device 4.4 (no driver attached)
pci0: <base peripheral> at device 4.5 (no driver attached)
pci0: <base peripheral> at device 4.6 (no driver attached)
pci0: <base peripheral> at device 4.7 (no driver attached)
pci0: <base peripheral> at device 5.0 (no driver attached)
pci0: <base peripheral> at device 5.2 (no driver attached)
pcib6: <ACPI PCI-PCI bridge> irq 16 at device 17.0 on pci0
pci7: <ACPI PCI bus> on pcib6
pci0: <simple comms> at device 22.0 (no driver attached)
pci0: <simple comms> at device 22.1 (no driver attached)
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfbc23000-0xfbc233ff irq 16 at device 26.0 on pci0
usbus0: EHCI version 1.0
usbus0 on ehci0
ehci1: <EHCI (generic) USB 2.0 controller> mem 0xfbc22000-0xfbc223ff irq 23 at device 29.0 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci1
pcib7: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci8: <ACPI PCI bus> on pcib7
vgapci0: <VGA-compatible display> mem 0xf9000000-0xf9ffffff,0xfb800000-0xfb803fff,0xfb000000-0xfb7fffff irq 22 at device 1.0 on pci8
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
ahci0: <Intel Patsburg AHCI SATA controller> port 0xf050-0xf057,0xf040-0xf043,0xf030-0xf037,0xf020-0xf023,0xf000-0xf01f mem 0xfbc21000-0xfbc217ff irq 18 at device 31.2 on pci0
ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahcich3: <AHCI channel> at channel 3 on ahci0
ahcich4: <AHCI channel> at channel 4 on ahci0
ahcich5: <AHCI channel> at channel 5 on ahci0
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
pci0: <dasp> at device 31.6 (no driver attached)
pcib8: <ACPI Host-PCI bridge> on acpi0
pci255: <ACPI PCI bus> on pcib8
pci255: <base peripheral> at device 8.0 (no driver attached)
pci255: <base peripheral> at device 8.3 (no driver attached)
pci255: <base peripheral> at device 8.4 (no driver attached)
pci255: <base peripheral> at device 9.0 (no driver attached)
pci255: <base peripheral> at device 9.3 (no driver attached)
pci255: <base peripheral> at device 9.4 (no driver attached)
pci255: <base peripheral> at device 10.0 (no driver attached)
pci255: <base peripheral> at device 10.1 (no driver attached)
pci255: <base peripheral> at device 10.2 (no driver attached)
pci255: <base peripheral> at device 10.3 (no driver attached)
pci255: <base peripheral> at device 11.0 (no driver attached)
pci255: <base peripheral> at device 11.3 (no driver attached)
pci255: <base peripheral> at device 12.0 (no driver attached)
pci255: <base peripheral> at device 12.1 (no driver attached)
pci255: <base peripheral> at device 12.6 (no driver attached)
pci255: <base peripheral> at device 12.7 (no driver attached)
pci255: <base peripheral> at device 13.0 (no driver attached)
pci255: <base peripheral> at device 13.1 (no driver attached)
pci255: <base peripheral> at device 13.6 (no driver attached)
pci255: <base peripheral> at device 14.0 (no driver attached)
pci255: <dasp> at device 14.1 (no driver attached)
pci255: <base peripheral> at device 15.0 (no driver attached)
pci255: <base peripheral> at device 15.1 (no driver attached)
pci255: <base peripheral> at device 15.2 (no driver attached)
pci255: <base peripheral> at device 15.3 (no driver attached)
pci255: <base peripheral> at device 15.4 (no driver attached)
pci255: <base peripheral> at device 15.5 (no driver attached)
pci255: <base peripheral> at device 15.6 (no driver attached)
pci255: <base peripheral> at device 16.0 (no driver attached)
pci255: <base peripheral> at device 16.1 (no driver attached)
pci255: <base peripheral> at device 16.2 (no driver attached)
pci255: <base peripheral> at device 16.3 (no driver attached)
pci255: <base peripheral> at device 16.4 (no driver attached)
pci255: <base peripheral> at device 16.5 (no driver attached)
pci255: <base peripheral> at device 16.6 (no driver attached)
pci255: <base peripheral> at device 16.7 (no driver attached)
pci255: <base peripheral> at device 17.0 (no driver attached)
pci255: <base peripheral> at device 19.0 (no driver attached)
pci255: <dasp> at device 19.1 (no driver attached)
pci255: <dasp> at device 19.4 (no driver attached)
pci255: <dasp> at device 19.5 (no driver attached)
pci255: <base peripheral> at device 19.6 (no driver attached)
acpi_button0: <Power Button> on acpi0
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
ichwd0 on isa0
ichwd0: ICH WDT present but disabled in BIOS or hardware
device_attach: ichwd0 attach returned 6
wbwd0: <Winbond 83627DHG-P> at port 0x2e-0x2f on isa0
ichwd0 at port 0x430-0x437,0x460-0x47f on isa0
ichwd0: ICH WDT present but disabled in BIOS or hardware
device_attach: ichwd0 attach returned 6
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xce000-0xcefff 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
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
coretemp2: <CPU On-Die Thermal Sensors> on cpu2
est2: <Enhanced SpeedStep Frequency Control> on cpu2
p4tcc2: <CPU Frequency Thermal Control> on cpu2
coretemp3: <CPU On-Die Thermal Sensors> on cpu3
est3: <Enhanced SpeedStep Frequency Control> on cpu3
p4tcc3: <CPU Frequency Thermal Control> on cpu3
Timecounters tick every 1.000 msec
ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
DUMMYNET 0xfffffe001509fd00 with IPv6 initialized (100409)
load_dn_sched dn_sched RR loaded
load_dn_sched dn_sched WF2Q+ loaded
load_dn_sched dn_sched FIFO loaded
load_dn_sched dn_sched PRIO loaded
load_dn_sched dn_sched QFQ loaded
usbus0: 480Mbps High Speed USB v2.0
usbus1: 480Mbps High Speed USB v2.0
ugen0.1: <Intel> at usbus0
uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
ses0 at mps0 bus 0 scbus0 target 24 lun 0
ses0: <LSI SAS2X36 0e12> Fixed Enclosure Services SCSI-5 device
ses0: Serial Number
ses0: 600.000MB/s transfers
ses0: Command Queueing enabled
ses0: SCSI-3 ENC Device
da3 at mps0 bus 0 scbus0 target 11 lun 0
da3: <ATA Samsung SSD 840 BB6Q> Fixed Direct Access SCSI-6 device
da3: Serial Number S1D9NSAF418359E
da3: 600.000MB/s transfers
da3: Command Queueing enabled
da3: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da0 at mps0 bus 0 scbus0 target 8 lun 0
da0: <ATA WDC WD1000DHTZ-0 6A00> Fixed Direct Access SCSI-6 device
da0: Serial Number WD-WX11E83F8867
da0: 600.000MB/s transfers
da0: Command Queueing enabled
da0: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da1 at mps0 bus 0 scbus0 target 9 lun 0
da1: <ATA WDC WD1000DHTZ-0 6A00> Fixed Direct Access SCSI-6 device
da1: Serial Number WD-WX11E4393854
da1: 600.000MB/s transfers
da1: Command Queueing enabled
da1: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da2 at mps0 bus 0 scbus0 target 10 lun 0
da2: <ATA WDC WD1000DHTZ-0 6A00> Fixed Direct Access SCSI-6 device
da2: Serial Number WD-WXK1E63ARZYD
da2: 600.000MB/s transfers
da2: Command Queueing enabled
da2: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da4 at mps0 bus 0 scbus0 target 12 lun 0
da4: <ATA WDC WD1000DHTZ-0 6A00> Fixed Direct Access SCSI-6 device
da4: Serial Number WD-WXD1E63RTVM5
da4: 600.000MB/s transfers
da4: Command Queueing enabled
da4: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da5 at mps0 bus 0 scbus0 target 13 lun 0
da5: <ATA WDC WD1000DHTZ-0 6A00> Fixed Direct Access SCSI-6 device
da5: Serial Number WD-WXK1E63DESPJ
da5: 600.000MB/s transfers
da5: Command Queueing enabled
da5: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da7 at mps0 bus 0 scbus0 target 15 lun 0
da7: <ATA Samsung SSD 840 BB6Q> Fixed Direct Access SCSI-6 device
da7: Serial Number S1D9NSAF418360L
da7: 600.000MB/s transfers
da7: Command Queueing enabled
da7: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da6 at mps0 bus 0 scbus0 target 14 lun 0
da6: <ATA WDC WD1000DHTZ-0 6A00> Fixed Direct Access SCSI-6 device
da6: Serial Number WD-WX11E83F9362
da6: 600.000MB/s transfers
da6: Command Queueing enabled
da6: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da8 at mps0 bus 0 scbus0 target 16 lun 0
da8: <ATA WDC WD1000DHTZ-0 6A00> Fixed Direct Access SCSI-6 device
da8: Serial Number WD-WXK1E63CCHSX
da8: 600.000MB/s transfers
da8: Command Queueing enabled
da8: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da9 at mps0 bus 0 scbus0 target 17 lun 0
da9: <ATA WDC WD1000DHTZ-0 6A00> Fixed Direct Access SCSI-6 device
da9: Serial Number WD-WXK1E63ASEET
da9: 600.000MB/s transfers
da9: Command Queueing enabled
da9: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da10 at mps0 bus 0 scbus0 target 18 lun 0
da10: <ATA WDC WD1000DHTZ-0 6A00> Fixed Direct Access SCSI-6 device
da10: Serial Number WD-WX11E83C1687
da10: 600.000MB/s transfers
da10: Command Queueing enabled
da10: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da12 at mps0 bus 0 scbus0 target 20 lun 0
da12: <ATA WDC WD1000DHTZ-0 6A00> Fixed Direct Access SCSI-6 device
da12: Serial Number WD-WXH1E33XPYA5
da12: 600.000MB/s transfers
da12: Command Queueing enabled
da12: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da13 at mps0 bus 0 scbus0 target 21 lun 0
da13: <ATA WDC WD1000DHTZ-0 6A00> Fixed Direct Access SCSI-6 device
da13: Serial Number WD-WX11E83L2242
da13: 600.000MB/s transfers
da13: Command Queueing enabled
da13: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da14 at mps0 bus 0 scbus0 target 22 lun 0
da14: <ATA WDC WD1000DHTZ-0 6A00> Fixed Direct Access SCSI-6 device
da14: Serial Number WD-WX11E83C1039
da14: 600.000MB/s transfers
da14: Command Queueing enabled
da14: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da11 at mps0 bus 0 scbus0 target 19 lun 0
da11: <ATA INTEL SSDSC2CW24 400i> Fixed Direct Access SCSI-6 device
da11: Serial Number CVCV244402K1240CGN
da11: 600.000MB/s transfers
da11: Command Queueing enabled
da11: 228936MB (468862128 512 byte sectors: 255H 63S/T 29185C)
da15 at mps0 bus 0 scbus0 target 23 lun 0
da15: <ATA INTEL SSDSC2CW24 400i> Fixed Direct Access SCSI-6 device
da15: Serial Number CVCV303604V1240CGN
da15: 600.000MB/s transfers
SMP: AP CPU #2 Launched!
da15: Command Queueing enabled
da15: 228936MB (468862128 512 byte sectors: 255H 63S/T 29185C)
SMP: AP CPU #3 Launched!
SMP: AP CPU #1 Launched!
Timecounter "TSC-low" frequency 1200024384 Hz quality 1000
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
ugen0.2: <vendor 0x8087> at usbus0
uhub2: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on usbus0
ugen1.2: <vendor 0x8087> at usbus1
uhub3: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on usbus1
uhub2: 6 ports with 6 removable, self powered
uhub3: 8 ports with 8 removable, self powered
ugen0.3: <Winbond Electronics Corp> at usbus0
ums0: <Winbond Electronics Corp Hermon USB hidmouse Device, class 0/0, rev 1.10/0.01, addr 3> on usbus0
ums0: 3 buttons and [Z] coordinates ID=0
ukbd0: <Winbond Electronics Corp Hermon USB hidmouse Device, class 0/0, rev 1.10/0.01, addr 3> on usbus0
kbd0 at ukbd0
ugen1.3: <Dell> at usbus1
ukbd1: <Dell Dell USB Keyboard, class 0/0, rev 1.10/3.06, addr 3> on usbus1
kbd2 at ukbd1
ugen1.4: <Logitech> at usbus1
ums1: <Logitech USB-PS2 Optical Mouse, class 0/0, rev 2.00/20.00, addr 4> on usbus1
ums1: 3 buttons and [XYZ] coordinates ID=0
ugen1.5: <SanDisk> at usbus1
umass0: <SanDisk Cruzer Blade, class 0/0, rev 2.00/2.01, addr 5> on usbus1
umass0: SCSI over Bulk-Only; quirks = 0x0100
umass0:8:0:-1: Attached to scbus8
da16 at umass-sim0 bus 0 scbus8 target 0 lun 0
da16: <SanDisk Cruzer Blade 2.01> Fixed Direct Access SCSI-6 device
da16: Serial Number 4C530303021018106054
da16: 40.000MB/s transfers
da16: 30532MB (62530624 512 byte sectors: 255H 63S/T 3892C)
da16: quirks=0x2<NO_6_BYTE>
Trying to mount root from ufs:/dev/ufs/FreeNASs2a [ro]...
GEOM_RAID5: Module loaded, version 1.1.20130907.44 (rev 5c6d2a159411)
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
GEOM_ELI: Device da0p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da1p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da2p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da4p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da5p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da8p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da9p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da10p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da11p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da12p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da13p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da14p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da15p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da6p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
ugen1.3: <Dell> at usbus1 (disconnected)
ukbd1: at uhub3, port 1, addr 3 (disconnected)
ugen1.4: <Logitech> at usbus1 (disconnected)
ums1: at uhub3, port 2, addr 4 (disconnected)
 

at1839

Cadet
Joined
Aug 12, 2014
Messages
3
I've got a 10Gbps Ethernet card I'm fighting with :)

The card was took off from a Fujitsu CS800 appliance, It’s a Fujitsu X520-DA2 SFP+ and as for my guess is just a rebranded Intel X520.

But the damn object don’t show up. Not with FreeNAS-9.2.1.7-RELEASE-x64 on a ML370 G4, not with VMware 5.0 on a ML370 G5, not with Windows 2008 server R2 on a Lenovo desktop, not with Debian Jessie.

I quite fear the bios was tampered to only show up on a Fujitsu hardware, anyone can confirm my guess, any hint?

Ty in advance. Paolo.
 
Joined
Mar 26, 2014
Messages
6
Are both processor sockets filled? If not, many mobo's PCI-Express slots are reserved for individual CPUs. For example, slot 1 is dedicated to cpu1, slot 2 to cpu2, slot 3 to cpu1, etc..

That was my problem...lol
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
Yes, that'd be a problem. Also, sometimes a manufacturer changes the PCI ID numbers of rebranded hardware. You'd want to look around with pciconf -l to see what's what if that's the case.
 

at1839

Cadet
Joined
Aug 12, 2014
Messages
3
@edk, yes both

@jgreco, ty, look, I found maybe none0 & none1 ???
host do actually have 4 1mbit detected cards, one broadcomm and 3 intel, bge0 em0/1/2
missing the two 10 gbit.

any further hint?

Paolo


[root@freenas30] ~# pciconf -l
hostb0@pci0:0:0:0: class=0x060000 card=0x32000e11 chip=0x35908086 rev=0x0c hdr=0x00
pcib1@pci0:0:2:0: class=0x060400 card=0x00000000 chip=0x35958086 rev=0x0c hdr=0x01
pcib5@pci0:0:4:0: class=0x060400 card=0x00000000 chip=0x35978086 rev=0x0c hdr=0x01
pcib6@pci0:0:5:0: class=0x060400 card=0x00000000 chip=0x35988086 rev=0x0c hdr=0x01
uhci0@pci0:0:29:0: class=0x0c0300 card=0x32010e11 chip=0x24d28086 rev=0x02 hdr=0x00
uhci1@pci0:0:29:1: class=0x0c0300 card=0x32010e11 chip=0x24d48086 rev=0x02 hdr=0x00
uhci2@pci0:0:29:2: class=0x0c0300 card=0x32010e11 chip=0x24d78086 rev=0x02 hdr=0x00
uhci3@pci0:0:29:3: class=0x0c0300 card=0x32010e11 chip=0x24de8086 rev=0x02 hdr=0x00
ehci0@pci0:0:29:7: class=0x0c0320 card=0x32010e11 chip=0x24dd8086 rev=0x02 hdr=0x00
pcib7@pci0:0:30:0: class=0x060400 card=0x00000000 chip=0x244e8086 rev=0xc2 hdr=0x01
isab0@pci0:0:31:0: class=0x060100 card=0x00000000 chip=0x24d08086 rev=0x02 hdr=0x00
atapci0@pci0:0:31:1: class=0x01018a card=0x32010e11 chip=0x24db8086 rev=0x02 hdr=0x00
pcib2@pci0:2:0:0: class=0x060400 card=0x00000000 chip=0x03298086 rev=0x09 hdr=0x01
pcib4@pci0:2:0:2: class=0x060400 card=0x00000000 chip=0x032a8086 rev=0x09 hdr=0x01
em0@pci0:3:1:0: class=0x020000 card=0x11078086 chip=0x10088086 rev=0x02 hdr=0x00
pcib3@pci0:3:2:0: class=0x060400 card=0x00000000 chip=0x01a71014 rev=0x02 hdr=0x01
mpt0@pci0:3:3:0: class=0x010000 card=0x00da0e11 chip=0x00301000 rev=0x08 hdr=0x00
mpt1@pci0:3:3:1: class=0x010000 card=0x00da0e11 chip=0x00301000 rev=0x08 hdr=0x00
ciss0@pci0:4:4:0: class=0x010400 card=0x409c0e11 chip=0x00460e11 rev=0x01 hdr=0x00
em1@pci0:7:1:0: class=0x020000 card=0x00db0e11 chip=0x10108086 rev=0x01 hdr=0x00
em2@pci0:7:1:1: class=0x020000 card=0x00db0e11 chip=0x10108086 rev=0x01 hdr=0x00
bge0@pci0:7:3:0: class=0x020000 card=0x00cb0e11 chip=0x16c714e4 rev=0x10 hdr=0x00
mpt2@pci0:14:0:0: class=0x010000 card=0x03941014 chip=0x00581000 rev=0x08 hdr=0x00
vgapci0@pci0:1:3:0: class=0x030000 card=0x001e0e11 chip=0x47521002 rev=0x27 hdr=0x00
none0@pci0:1:4:0: class=0x088000 card=0xb2060e11 chip=0xb2030e11 rev=0x01 hdr=0x00
none1@pci0:1:4:2: class=0x088000 card=0xb2060e11 chip=0xb2040e11 rev=0x01 hdr=0x00
[root@freenas30] ~#
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
none0 and none1 appear to be related to your iLO management system. I'm not thinking of anything else obvious to try, though you could remove the card and see if the above list changes.
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
Well the important bit is to get the info out here so someone with experience with your particular device can compare it to their system, or analyze it with a more critical eye. I know there've been problems reported with the Intel 10GbE stuff in recent months but don't have any 10GbE stuff on a bare metal FreeNAS box, sorry.
 

jamiejunk

Contributor
Joined
Jan 13, 2013
Messages
134
Well the important bit is to get the info out here so someone with experience with your particular device can compare it to their system, or analyze it with a more critical eye. I know there've been problems reported with the Intel 10GbE stuff in recent months but don't have any 10GbE stuff on a bare metal FreeNAS box, sorry.

Yep, we have found the intel 10 gig nics don't work with freenas. They usually show up, but have problems when trying to actually use them.
 

vikingboy

Explorer
Joined
Aug 3, 2014
Messages
71
Its taken some tweaking but my x520 is working perfectly....

[ 5] local 192.168.125.201 port 5001 connected with 192.168.125.200 port 57472
[ 5] 0.0-10.0 sec 11.4 GBytes 9.74 Gbits/sec
[ 4] local 192.168.125.201 port 5001 connected with 192.168.125.200 port 57473
[ 4] 0.0-10.0 sec 11.2 GBytes 9.62 Gbits/sec
[ 5] local 192.168.125.201 port 5001 connected with 192.168.125.200 port 57474
[ 5] 0.0-10.0 sec 11.3 GBytes 9.72 Gbits/sec
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
They usually show up, but have problems when trying to actually use them.

Flashbacks of about 10 years ago, when there were Intel multiport server gigE knockoffs flooding into the market (new, through reputable vendors, not eBay).

Not sayin' the 10G's are knockoffs, but boy, it was just like what you've described.
 

vikingboy

Explorer
Joined
Aug 3, 2014
Messages
71
Ive been meaning to buy a knock off / Chinese i350 and x520 to bench just to cure my curiosity....
 
Status
Not open for further replies.
Top