[Bug 213257] Crash in IGB driver with ALTQ

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Feb 20 19:07:39 UTC 2017


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257

Kenneth D. Merry <ken at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ken at FreeBSD.org

--- Comment #17 from Kenneth D. Merry <ken at FreeBSD.org> ---
I have run into this as well.  IGB_LEGACY_TX has been broken for quite some
time, at least for me.  (Since mid-2015 at least.)  I bought an em(4) card to
use with ALTQ, since it was easier and cheaper than trying to figure out why
igb(4) was broken.  I'm using igb(4) on the internal ports on my gateway
router.

Change 299182 bit me last night when I updated my gateway router from an April
2016 10-stable to a February 2017 10-stable.

So, I've got ALTQ enabled, but I'm not using it on igb(4), just on em(4) ports.

In my opinion, we should not automatically enable IGB_LEGACY_TX until it has
been fixed to work reliably at any traffic rate.  Anyone enabling ALTQ with an
igb(4) interface in their system may well run into problems.

It only took about 15 minutes for my router to hang, and another 15 minutes to
panic after that.

FreeBSD mithlond.kdm.org 10.3-STABLE FreeBSD 10.3-STABLE #20 r313925: Sat Feb
18
 17:36:43 EST 2017    
ken at mithlond.kdm.org:/usr/obj/usr/home/ken/src/freebsd/st
able/10/sys/mithlond  amd64

panic: sbsndptr: sockbuf 0xfffff80158d796f8 and mbuf 0xfffff80196bad600
clashing

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...

Unread portion of the kernel message buffer:
panic: sbsndptr: sockbuf 0xfffff80158d796f8 and mbuf 0xfffff80196bad600
clashing
cpuid = 2
KDB: stack backtrace:
db_trace_self_wrapper() at 0xffffffff80364dab =
db_trace_self_wrapper+0x2b/frame 0xfffffe0000359160
kdb_backtrace() at 0xffffffff809904c9 = kdb_backtrace+0x39/frame
0xfffffe0000359210
vpanic() at 0xffffffff80950e46 = vpanic+0x126/frame 0xfffffe0000359250
panic() at 0xffffffff80950d13 = panic+0x43/frame 0xfffffe00003592b0
sbsndmbuf() at 0xffffffff809d4b90 = sbsndmbuf/frame 0xfffffe00003592c0
tcp_output() at 0xffffffff80b16b9c = tcp_output+0xe6c/frame 0xfffffe00003594c0
tcp_do_segment() at 0xffffffff80b14858 = tcp_do_segment+0x2ff8/frame
0xfffffe00003595d0
tcp_input() at 0xffffffff80b10f06 = tcp_input+0x1036/frame 0xfffffe0000359730
ip_input() at 0xffffffff80a9b217 = ip_input+0x97/frame 0xfffffe0000359780
netisr_dispatch_src() at 0xffffffff80a352e2 = netisr_dispatch_src+0x62/frame
0xfffffe00003597f0
ether_demux() at 0xffffffff80a2bba6 = ether_demux+0x126/frame
0xfffffe0000359820
ether_nh_input() at 0xffffffff80a2c84e = ether_nh_input+0x35e/frame
0xfffffe0000359880
netisr_dispatch_src() at 0xffffffff80a352e2 = netisr_dispatch_src+0x62/frame
0xfffffe00003598f0
igb_rxeof() at 0xffffffff805104d6 = igb_rxeof+0x616/frame 0xfffffe0000359990
igb_msix_que() at 0xffffffff80510b7b = igb_msix_que+0x11b/frame
0xfffffe00003599e0
intr_event_execute_handlers() at 0xffffffff8091eb99 =
intr_event_execute_handlers+0xb9/frame 0xfffffe0000359a20
ithread_loop() at 0xffffffff8091f556 = ithread_loop+0x96/frame
0xfffffe0000359a70
fork_exit() at 0xffffffff8091c45a = fork_exit+0x9a/frame 0xfffffe0000359ab0
fork_trampoline() at 0xffffffff80d957ce = fork_trampoline+0xe/frame
0xfffffe0000359ab0

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


More information about the freebsd-net mailing list