igb0@pci0:1:0:0:        class=0x020000 card=0x152115d9 chip=0x15218086 rev=0x01 
hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'I350 Gigabit Network Connection'
    class      = network
    subclass   = ethernet
    cap 01[40] = powerspec 3  supports D0 D3  current D0
    cap 05[50] = MSI supports 1 message, 64 bit, vector masks
    cap 11[70] = MSI-X supports 10 messages
                 Table in map 0x1c[0x0], PBA in map 0x1c[0x2000]
    cap 10[a0] = PCI-Express 2 endpoint max data 512(512) FLR RO NS
                 link x4(x4) speed 5.0(5.0) ASPM L1(L0s/L1)
    ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected
    ecap 0003[140] = Serial 1 ac1f6bffff620e0c
    ecap 000e[150] = ARI 1
    ecap 0010[160] = SR-IOV 1 IOV disabled, Memory Space disabled, ARI disabled
                     0 VFs configured out of 8 supported
                     First VF RID Offset 0x0180, VF RID Stride 0x0004
                     VF Device ID 0x1520
                     Page Sizes: 4096 (enabled), 8192, 65536, 262144, 1048576, 
4194304
    ecap 0017[1a0] = TPH Requester 1
    ecap 0018[1c0] = LTR 1
    ecap 000d[1d0] = ACS 1

It's info from system booted with HPET disabled and 
hw.pci.enable_msix: 0
hw.pci.enable_msi: 0

If one of this parameters not set as described system not boot ^( 


Stephen Hurd wrote:
SH> Hrm, it should be trying to allocate three msi-x vectors there, and it
SH> appears that it's reported that 10 are available.  What's the output of
SH> ``pciconf -lcv pci1:0:0''?
SH> 
SH> On Mon, Apr 16, 2018 at 1:27 PM, Conrad Meyer <c...@freebsd.org> wrote:
SH> 
SH> > Hi Vitalij,
SH> >
SH> > On Mon, Apr 16, 2018 at 3:27 AM, Vitalij Satanivskij <sa...@ukr.net>
SH> > wrote:
SH> > > DUMP can be found here http://hell.ukr.net/panic/panic.jpg
SH> > > or even video record from screen http://hell.ukr.net/panic/recorder.webm
SH> >
SH> > Looks like the panic message is printed directly after: "igb0: using 2
SH> > rx queues 2 tx queues" (iflib_msix_init(), called by
SH> > iflib_device_register()).
SH> >
SH> > And stack is indeed coming from iflib in probe (0:17 in linked video):
SH> >
SH> > panic()
SH> > nexus_add_irq()
SH> > msix_alloc()
SH> > pci_alloc_msix_method()
SH> > iflib_device_register()
SH> > iflib_device_attach()
SH> > device_attach()
SH> > ...
SH> >
SH> > Stephen, Matt, or Sean might be able to help diagnose further.
SH> >
SH> > Best,
SH> > Conrad
SH> >
SH> 
SH> 
SH> 
SH> -- 
SH> [image: Limelight Networks] <http://www.limelight.com>
SH> Stephen Hurd* Principal Engineer*
SH> EXPERIENCE FIRST.
SH> +1 616 848 0643 <+1+616+848+0643>
SH> www.limelight.com
SH> [image: Facebook] <https://www.facebook.com/LimelightNetworks>[image:
SH> LinkedIn] <http://www.linkedin.com/company/limelight-networks>[image:
SH> Twitter] <https://twitter.com/llnw>
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to