Date: Tue, 21 Feb 2017 16:18:16 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213257] Crash in IGB driver with ALTQ Message-ID: <bug-213257-2472-42BNUL2feG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-213257-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-213257-2472@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=3D213257 --- Comment #20 from freebsd@mcwest.org --- (In reply to Kenneth D. Merry from comment #19) I hear you about the downtime. My gateway router only has igb(4) interface= s, so I must use ALTQ on the external one. Although I don't need ALTQ on the internal interface, choking it with ALTQ keeps the system stable even with IGB_LEGACY_TX turned on. My original goal when reporting bug #208409 was to resolve the discrepancy between the documented list of interfaces that support ALTQ and the actual = OS behavior which reports ALTQ is not supported on igb(4) in the default configuration. Since ALTQ does work with igb(4) as the documentation state= s, I suggest we expose an additional kernel config option that will allow it to = be enabled separately from ALTQ as a whole, and eliminating the need to modify= the kernel source code. Along with a small note in the man page for altq(4), t= his would resolve the original problem. For example, an option like this: options ALTQ_IGB # Enable ALTQ on igb devices Unlike exposing IGB_LEGACY_TX, this would be implementation-neutral, and eliminate any future confusion over its intent. And when the bugs in the i= gb driver are fixed, it could be easily removed again. --=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-213257-2472-42BNUL2feG>