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

Site Navigation

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