Bug 194197 - [igb] [patch] IGB cards need a kernel option to enable legacy mode (to support ALTQ)
Summary: [igb] [patch] IGB cards need a kernel option to enable legacy mode (to suppor...
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 10.1-STABLE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-net (Nobody)
Keywords: IntelNetworking
Depends on:
Blocks: 177402
  Show dependency treegraph
Reported: 2014-10-06 18:15 UTC by Dan
Modified: 2021-04-15 18:06 UTC (History)
3 users (show)

See Also:

Adds IGB_LEGACY_TX and IXGBE_LEGACY_TX to kernel options (1.54 KB, patch)
2014-10-06 18:15 UTC, Dan
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Dan 2014-10-06 18:15:56 UTC
Created attachment 148039 [details]
Adds IGB_LEGACY_TX and IXGBE_LEGACY_TX to kernel options

IGB cards still do not support ALTQ, except in "legacy" mode, since FreeBSD 7/8.  To enable legacy mode, patching of the kernel source is required.  There is no official documentation on how to patch source, although reading between the lines on various forums would point you in the right direction.

I created the attached patch to enable legacy mode in IGB driver through a kernel option, rather than a patch.  A similar patch needs to be created for IXGBE.

Because of bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193053, IXGBE will not compile with the kernel option set, but IGB will.  Still, there should be a way to enable this option for IXGBE, even if it does not currently compile.
Comment 1 skeletor 2014-11-10 08:17:29 UTC
I have tested this patch (with rebuilding kernel with option IGB_LEGACY_TX, but nothing changed. So, this patch doesn't work for me or I do something wrong.
Comment 2 Marcus von Appen freebsd_committer freebsd_triage 2015-02-18 11:54:19 UTC
Updated 10.1-BETA and 10.1-RC versioned bugs to 10.1-STABLE.
Comment 3 Kevin Bowling freebsd_committer 2021-04-15 18:06:34 UTC
This should be fixed in FreeBSD 12+.  Fixing this in 11 would require a direct commit, if you cannot upgrade to 12+ let me know and I can prepare a patch for direct commit.  Be advised however there are no follow up releases to 11 planned, and it will go EoL in September https://www.freebsd.org/security/#sup.