Date: Thu, 14 Feb 2019 04:58:15 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 235730] Kernel panic on CURRENT-amd64 with ixl - possibly caused by r344062 Message-ID: <bug-235730-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235730 Bug ID: 235730 Summary: Kernel panic on CURRENT-amd64 with ixl - possibly caused by r344062 Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: jeffrey.e.pieper@intel.com Created attachment 202007 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D202007&action= =3Dedit ixl panic fix The ixl driver panics at attach with GENERIC: Unread portion of the kernel message buffer: ixl0: <Intel(R) Ethernet Connection X722 for 10GBASE-T - 2.1.0-k> mem 0xa1000000-0xa1ffffff,0xa3018000-0xa301ffff at device 0.0 numa-domain 0 on = pci6 ixl0: fw 3.1.52953 api 1.5 nvm 3.04 etid 800008c9 oem 1.262.0 ixl0: PF-ID[0]: VFs 32, MSI-X 129, VF MSI-X 5, QPs 384, MDIO shared ixl0: Using 1024 tx descriptors and 1024 rx descriptors ixl0: queue equality override not set, capping rx_queues at 28 and tx_queue= s at 28 ixl0: Using 28 rx queues 28 tx queues ixl0: Using MSI-X interrupts with 29 vectors panic: Assertion tid >=3D 0 failed at /diskless/os/FreeBSD/13.0-CURRENT_latest/usr/src/sys/net/iflib.c:5652 cpuid =3D 43 time =3D 1550084681 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00e8552= 750 vpanic() at vpanic+0x1b4/frame 0xfffffe00e85527b0 panic() at panic+0x43/frame 0xfffffe00e8552810 iflib_irq_set_affinity() at iflib_irq_set_affinity+0x437/frame 0xfffffe00e85528c0 iflib_softirq_alloc_generic() at iflib_softirq_alloc_generic+0xd1/frame 0xfffffe00e8552910 ixl_if_msix_intr_assign() at ixl_if_msix_intr_assign+0xf2/frame 0xfffffe00e8552980 iflib_device_register() at iflib_device_register+0x972/frame 0xfffffe00e855= 2ce0 iflib_device_attach() at iflib_device_attach+0xb7/frame 0xfffffe00e8552d10 device_attach() at device_attach+0x3ea/frame 0xfffffe00e8552d50 device_probe_and_attach() at device_probe_and_attach+0x71/frame 0xfffffe00e8552d80 pci_driver_added() at pci_driver_added+0xe6/frame 0xfffffe00e8552dc0 devclass_driver_added() at devclass_driver_added+0x7a/frame 0xfffffe00e8552= e00 devclass_add_driver() at devclass_add_driver+0x189/frame 0xfffffe00e8552e40 module_register_init() at module_register_init+0xc0/frame 0xfffffe00e8552e70 linker_load_module() at linker_load_module+0xb78/frame 0xfffffe00e8553190 kern_kldload() at kern_kldload+0xef/frame 0xfffffe00e85531e0 sys_kldload() at sys_kldload+0x5b/frame 0xfffffe00e8553210 amd64_syscall() at amd64_syscall+0x276/frame 0xfffffe00e8553330 fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe00e8553330 --- syscall (304, FreeBSD ELF64, sys_kldload), rip =3D 0x8002dc96a, rsp =3D 0x7fffffffe3d8, rbp =3D 0x7fffffffe950 --- KDB: enter: panic cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1406 1406 CPU_SET_ATOMIC(cpu, &stopped_cpus); (kgdb)=20 This is possibly due to r344062, which touched the iflib taskqueue code. We= do not see this with GENERIC-NODEBUG. Attached is a possible fix thanks to erj. --=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-235730-227>