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

Site Navigation

PRs for tag 'igb'

This is an experimental report containing PRs for tag 'igb' as of 4-18-2014. 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 'igb':
SSubmittedTrackerResp.Description
o2014/03/19kern/187718net[igb] UDP bad performance and out-of-order packet with iperf3 and igb(4) drivers
o2014/01/02kern/185427net[igb] freebsd 8.4, 9.1 and 9.2 panic Double-Fault with intel 82576 igb driver
o2013/10/12kern/182917net[igb] strange out traffic with igb interfaces
o2013/10/08kern/182828jfv[patch] [igb] Revision 247430 broke outgoing interface stats for stable/8
o2013/08/12kern/181236net[igb] igb driver unstable work
o2013/03/26kern/177402net[igb] [pf] problem with ethernet driver igb + pf / altq [regression]
o2013/03/20kern/177139net[igb] igb drops ethernet ports 2 and 3
o2012/03/06kern/165782jfv[igb] igb driver should identify hardware, not software
f2012/02/22kern/165399jfv[igb] turn off port on SWITCH do not change status of igb
o2012/02/15kern/165181net[igb] igb freezes after about 2 weeks of uptime
o2012/01/25kern/164495net[igb] connect double head igb to switch cause system to halt
o2012/01/08kern/163903net[igb] "igb0:tx(0)","bpf interface lock" v2.2.5 9-STABLE
o2011/10/28kern/162110net[igb] [panic] RELENG_9 panics on boot in IGB driver - [regression] from 8.2
o2011/09/21kern/160873net[igb] igb(4) from HEAD fails to build on 7-STABLE
o2011/05/17kern/157118[igb] cleanup error in igb driver - igb_setup_receive_structures()
o2010/10/20kern/151593net[igb] [panic] Kernel panic when bringing up igb network adapter with MSI-X enabled
o2010/09/24kern/150920net[ixgbe][igb] Panic when packets are dropped with header split disabled
o2010/09/14kern/150557net[igb] igb0: Watchdog timeout -- resetting
o2010/08/11kern/149532jfv[igb] igb/ixgb controllers panic on FreeBSD 8.1-RELEASE
o2009/09/09kern/138660jfv[igb] igb driver troubles in 8.0-BETA4
o2009/06/03kern/135222jfv[igb] low speed routing between two igb interfaces
o2008/11/13kern/128840jfv[igb] page fault under load with igb/LRO
22 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.