Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for tag 'ixgbe'

This is an experimental report containing PRs for tag 'ixgbe' as of 5-25-2012. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.

This report is generated statically.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.


PRs for tag 'ixgbe':
SSubmittedTrackerResp.Description
o2012/05/24kern/168294net[ixgbe] [patch] ixgbe driver compiled in kernel has no Flow Director support although loaded as a module has one
o2011/10/26kern/162028net[ixgbe] [patch] misplaced #endif in ixgbe.c
o2011/01/12kern/153936net[ixgbe] [patch] MPRC workaround incorrectly applied to 82599
o2011/01/09kern/153816net[ixgbe] ixgbe doesn't work properly with the Intel 10gigabit CX4 Dual Port network card
o2011/01/07kern/153772net[ixgbe] [patch] sysctls reference wrong XON/XOFF variables
o2010/09/24kern/150920net[ixgbe][igb] Panic when packets are dropped with header split disabled
o2010/09/03kern/150251net[patch] [ixgbe] Late cable insertion broken
o2010/09/03kern/150249net[ixgbe] Media type detection broken
o2010/03/08kern/144561jfv[ixgbe] [patch] ixgbe driver errors
o2008/11/04kern/128577[ixgbe] [patch] Send queue stall in ixgbe driver when MSIX interrups are used
o2008/08/20kern/126688jfv[ixgbe] [patch] 1.4.7 ixgbe driver panic with 4GB and PAE
11 problems total.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.