Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Jun 2022 17:10:56 +0000
From:      bugzilla-noreply@freebsd.org
To:        net@FreeBSD.org
Subject:   [Bug 252626] ixl: panic on attach of X722 on-motherboard interfaces
Message-ID:  <bug-252626-7501-PiRrRSpguR@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-252626-7501@https.bugs.freebsd.org/bugzilla/>
References:  <bug-252626-7501@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252626

benoitc <benoitc@enki-multimedia.eu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |benoitc@enki-multimedia.eu

--- Comment #8 from benoitc <benoitc@enki-multimedia.eu> ---
i hve same chipset intel card on HPE (both media card with 1Gb and 10Gb). W=
hen
IOV is enabled using the stock kernel IXL driver of freebsd I get a panic at
boot.=20

When using the intel-ixl-kmod driver it works but once SRV is enabled I get=
 the
bug #234073. When, I upgrade to latest intel-ixl-kmod, the kernel panics and
reboot.

```
 dmesg |grep ixl
module_register: cannot register pci/ixl from kernel; already loaded from
if_ixl_updated.ko
Module pci/ixl failed to register: 17
ixl0: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.12.2>=
 mem
0xeb000000-0xebffffff,0xef000000-0xef007fff at device 0.0 numa-domain 0 on =
pci9
ixl0: using 1024 tx descriptors and 1024 rx descriptors
ixl0: fw 5.5.67510 api 1.12 nvm 5.50 etid 80003373 oem 1.268.0
ixl0: The driver for the device detected a newer version of the NVM image t=
han
expected.
ixl0: Please install the most recent version of the network driver.
ixl0: PF-ID[0]: VFs 32, MSI-X 129, VF MSI-X 5, QPs 384, MDIO shared
ixl0: Using MSI-X interrupts with 9 vectors
ixl0: Allocating 8 queues for PF LAN VSI; 8 queues active
ixl0: Ethernet address: b4:7a:f1:dd:c6:00
ixl0: SR-IOV ready
ixl0: The device is not iWARP enabled
ixl1: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.12.2>=
 mem
0xec000000-0xecffffff,0xef008000-0xef00ffff at device 0.1 numa-domain 0 on =
pci9
ixl1: using 1024 tx descriptors and 1024 rx descriptors
ixl1: fw 5.5.67510 api 1.12 nvm 5.50 etid 80003373 oem 1.268.0
ixl1: The driver for the device detected a newer version of the NVM image t=
han
expected.
ixl1: Please install the most recent version of the network driver.
ixl1: PF-ID[1]: VFs 32, MSI-X 129, VF MSI-X 5, QPs 384, MDIO shared
ixl1: Using MSI-X interrupts with 9 vectors
ixl1: Allocating 8 queues for PF LAN VSI; 8 queues active
ixl1: Ethernet address: b4:7a:f1:dd:c6:01
ixl1: SR-IOV ready
ixl1: The device is not iWARP enabled
ixl2: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.12.2>=
 mem
0xed000000-0xedffffff,0xef010000-0xef017fff at device 0.2 numa-domain 0 on =
pci9
ixl2: using 1024 tx descriptors and 1024 rx descriptors
ixl2: fw 5.5.67510 api 1.12 nvm 5.50 etid 80003373 oem 1.268.0
ixl2: The driver for the device detected a newer version of the NVM image t=
han
expected.
ixl2: Please install the most recent version of the network driver.
ixl2: PF-ID[2]: VFs 32, MSI-X 129, VF MSI-X 5, QPs 384, I2C
ixl2: Using MSI-X interrupts with 9 vectors
ixl2: Allocating 8 queues for PF LAN VSI; 8 queues active
ixl2: Ethernet address: b4:7a:f1:dd:c6:02
ixl2: SR-IOV ready
ixl2: The device is not iWARP enabled
ixl3: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.12.2>=
 mem
0xee000000-0xeeffffff,0xef018000-0xef01ffff at device 0.3 numa-domain 0 on =
pci9
ixl3: using 1024 tx descriptors and 1024 rx descriptors
ixl3: fw 5.5.67510 api 1.12 nvm 5.50 etid 80003373 oem 1.268.0
ixl3: The driver for the device detected a newer version of the NVM image t=
han
expected.
ixl3: Please install the most recent version of the network driver.
ixl3: PF-ID[3]: VFs 32, MSI-X 129, VF MSI-X 5, QPs 384, I2C
ixl3: Using MSI-X interrupts with 9 vectors
ixl3: Allocating 8 queues for PF LAN VSI; 8 queues active
ixl3: Ethernet address: b4:7a:f1:dd:c6:03
ixl3: SR-IOV ready
ixl3: The device is not iWARP enabled
ixl2: Link is up, 10 Gbps Full Duplex, Requested FEC: None, Negotiated FEC:
None, Autoneg: False, Flow Control: None
ixl2: link state changed to UP
ixl3: Link is up, 10 Gbps Full Duplex, Requested FEC: None, Negotiated FEC:
None, Autoneg: False, Flow Control: None
ixl3: link state changed to UP
```

```
pciconf -vl ixl2
ixl2@pci0:100:0:2:      class=3D0x020000 rev=3D0x09 hdr=3D0x00 vendor=3D0x8=
086
device=3D0x37d3 subvendor=3D0x1590 subdevice=3D0x0219
    vendor     =3D 'Intel Corporation'
    device     =3D 'Ethernet Connection X722 for 10GbE SFP+'
    class      =3D network
    subclass   =3D ethernet
```

ried it (112.35 with netmap support disabled and got a kernel panic:

```
Fatal trap 12: page fault while in kernel mode
cpuid =3D 10; apic id =3D 0a
fault virtual address=3D 0x54
fault code=3D supervisor read data, page not present
instruction pointer=3D 0x20:0xffffffff82f04b8a
stack pointer        =3D 0x28:0xfffffe020d8108a0
frame pointer        =3D 0x28:0xfffffe020d8108e0
code segment=3D base 0x0, limit 0xfffff, type 0x1b
=3D DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags=3D interrupt enabled, resume, IOPL =3D 0
current process=3D 21330 (iovctl)
trap number=3D 12
panic: page fault
cpuid =3D 10
time =3D 1655897957
KDB: stack backtrace:
#0 0xffffffff80c69465 at kdb_backtrace+0x65
#1 0xffffffff80c1bb1f at vpanic+0x17f
#2 0xffffffff80c1b993 at panic+0x43
#3 0xffffffff810afdf5 at trap_fatal+0x385
#4 0xffffffff810afe4f at trap_pfault+0x4f
#5 0xffffffff81087528 at calltrap+0x8
#6 0xffffffff82efe716 at ixl_reconfigure_filters+0x66
#7 0xffffffff82f24b90 at ixl_vf_setup_vsi+0x3b0
#8 0xffffffff82f2469e at ixl_add_vf+0x1ee
#9 0xffffffff8086e407 at pci_iov_ioctl+0x1497
#10 0xffffffff80ab4e46 at devfs_ioctl+0xc6
#11 0xffffffff80d0cde4 at vn_ioctl+0x1a4
#12 0xffffffff80ab54fe at devfs_ioctl_f+0x1e
#13 0xffffffff80c897cb at kern_ioctl+0x25b
#14 0xffffffff80c894d1 at sys_ioctl+0xf1
#15 0xffffffff810b06ec at amd64_syscall+0x10c
#16 0xffffffff81087e3b at fast_syscall_common+0xf8
Uptime: 13s
```

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252626-7501-PiRrRSpguR>