PRs for tag 'em'
This is an experimental report containing PRs for tag 'em' 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 'em':
|o||2014/02/25||kern/187068||net||[em] network data slow/stops with em driver|
|o||2013/02/11||kern/176027||net||[em] [patch] flow control systcl consistency for em drivers|
|o||2012/10/27||kern/173137||net||[em] em(4) unable to run at gigabit with 9.1-RC2|
|o||2012/05/23||kern/168246||net||[em] Multiple em(4) not working with qemu|
|o||2012/05/01||kern/167500||net||[em] [panic] Kernel panics in em driver|
|o||2011/10/29||kern/162153||net||[em] intel em driver 7.2.4 don't compile|
|o||2011/10/04||kern/161277||net||[em] [patch] BMC cannot receive IPMI traffic after loading or enabling the if_em driver|
|o||2011/09/13||kern/160693||net||[gif] [em] Multicast packet are not passed from GIF0 to EM0 interface (Packet Lost)|
|o||2011/07/29||kern/159294||net||[em] em watchdog timeouts|
|o||2011/07/04||kern/158635||net||[em] TSO breaks BPF packet captures with em driver|
|o||2011/05/30||kern/157418||net||[em] em driver lockup during boot on Supermicro X9SCM-F|
|o||2011/04/27||kern/156667||net||[em] em0 fails to init on CURRENT after March 17|
|o||2011/02/11||kern/154679||net||[em] Fatal trap 12: "em1 taskq" only at startup (8.1-RELEASE)|
|o||2010/12/20||kern/153308||net||[em] em interface use 100% cpu|
|o||2010/12/17||kern/153244||net||[em] em(4) fails to send UDP to port 0xffff|
|o||2010/12/05||kern/152853||net||[em] tftpd (and likely other udp traffic) fails over em(4) unless rxcsum/txcsum disabled [regression]|
|o||2010/12/04||kern/152828||net||[em] poor performance on 8.1, 8.2-PRE|
|o||2010/09/13||kern/150516||jfv||[em] e1000 receive queue handling problem|
|o||2010/06/20||kern/148004||jfv||[em] Inconsistent networking with em driver on FreeBSD 8.0-p2|
|o||2010/06/19||kern/147989||jfv||[em] em Receive errors / CRC Errors / Alignment Errors|
|p||2010/03/19||kern/144869||jfv||[em] [panic] Instant kernel panic when adding NAT rules using ipfw on em interfaces|
|o||2010/03/12||kern/144680||jfv||[em] em(4) problem with dual-port adapter|
|o||2010/02/05||kern/143573||jfv||[em] em(4) NIC crashes intermittently|
|o||2010/01/27||kern/143285||jfv||[em] [regression] jumbo frames broken in 8.0|
|f||2010/01/09||kern/142518||net||[em] [lagg] Problem on 8.0-STABLE with em and lagg|
|o||2009/12/25||kern/142019||jfv||[em] em needs "ifconfig em0 down up" when link was gone|
|o||2009/12/21||kern/141843||jfv||[em] [vlan] Intel txcsum and assigned vlan invoke wrong dst MAC in TCP packets|
|o||2009/11/22||kern/140778||jfv||[em] randomly panic in vlan/em|
|o||2009/11/20||kern/140728||jfv||[em] [patch] Fast irq registration in em driver|
|o||2009/11/17||kern/140647||jfv||[em] [patch] e1000 driver does not correctly handle multicast promiscuous mode with 128 or more multicast addresses|
|o||2009/11/06||kern/140326||jfv||[em] em0: watchdog timeout when communicating to windows using 9K MTU|
|o||2009/08/31||kern/138392||jfv||[em] [altq] ALTQ queuing not working on em(4)|
|o||2009/06/29||kern/136168||jfv||[em] em driver initialization fails on Intel 5000PSL motherboard|
|o||2009/05/26||kern/134956||jfv||[em] FreeBSD 7.1 & 7.2, Intel PRO/1000 PT Quad Port Server Adapter (82571), ifconfig reports "status: active" after cable unplugged|
|o||2009/04/29||kern/134079||jfv||[em] "em0: Invalid MAC address" in FreeBSD-Current ( 8.0)|
|o||2008/04/20||kern/122928||jfv||[em] interface watchdog timeouts and stops receiving packets|
|o||2008/04/14||kern/122772||jfv||[em] em0 taskq panic, tcp reassembly bug causes radix tree corruption?|
|o||2008/04/02||kern/122373||jfv||[em] unable to receive on em 82542 w/o promisc|
|o||2008/03/24||kern/122058||jfv||[em] [panic] Panic on em1: taskq|
|o||2008/03/11||kern/121624||jfv||[em] [regression] Intel em WOL fails after upgrade to FreeBSD-6.3 (from 6.2)|
|o||2008/03/02||kern/121298||jfv||[em] [panic] Fatal trap 12: page fault while in kernel mode (em0 taskq)|
|o||2008/01/18||kern/119767||jfv||[em] [patch] if_em fix for systems without msix support|
|o||2008/01/17||kern/119754||jfv||[em] em hung after "watchdog timeout -- resetting" on SMP with 2+ cpus|
|o||2007/12/21||kern/118927||jfv||[em] em(4) broken: link state changed to DOWN (/UP), link states coalesced errors [regression]|
|o||2007/12/14||kern/118695||jfv||[em] device polling + vlan causes panic on "em" interface|
|o||2007/11/08||kern/117926||jfv||[em] Intel S5000-based mobo, em driver does not attach to first ethernet controller|
|o||2007/10/09||kern/117043||jfv||[em] Intel PWLA8492MT Dual-Port Network adapter EEPROM Checksum is Not Valid|
|o||2007/08/29||kern/115930||jfv||[em] Dell nic enumeration problem|
|o||2007/05/24||kern/112937||jfv||[em] Panic in em(4) when issuing a SIOCGIFADDR ioctl|
|o||2007/05/16||kern/112702||jfv||[em] em driver doesn't use MSI on MSI capable device|
|o||2006/10/31||kern/104978||jfv||[em] jumbo frames has been broken in RELENG_6 by last commit|
|o||2006/09/14||kern/103256||jfv||[em] em0: watchdog timeout -- resetting (6.1-STABLE)|
|o||2006/08/01||kern/101226||jfv||[em] Access to IPMI module is lost when the em driver attaches to the network interface.|
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.