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

Site Navigation

PRs for tag 're'

This is an experimental report containing PRs for tag 're' 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 're':
SSubmittedTrackerResp.Description
o2014/02/21kern/186949net[re] re0 driver crashes under load every 10-20 minutes
f2014/02/03kern/186401yongari[re] Problem with RTL8111/8168B initialization
o2014/01/05kern/185496net[re] RTL8169 doesn't receive unicast ethernet packets unless in promiscuous mode
f2013/11/04kern/183647yongari[re] re ethernet driver broken
o2013/09/09kern/181970net[re] LAN RealtekŪ 8111G is not supported by re driver
o2013/08/31kern/181703net[re] [patch] Fix Realtek 8111G Ethernet controller not being detected
o2013/07/25kern/180844net[panic] [re] Intermittent panic (re driver?)
o2013/03/12kern/176884net[re] re0 flapping up/down
o2013/02/05kern/175864net[re] Intel MB D510MO, onboard ethernet not working after update to 9.1 [regression]
o2012/09/01kern/171228net[re] [patch] if_re - eeprom write issues
f2012/07/13kern/169826yongari[re] if_re no longer working in 9.x [regression]
f2012/05/23kern/168268yongari[re] if_re doesn't work if you set MAC address
f2012/05/12kern/167827yongari[re] RTL8111/8168B Issues (stalling/only 100Mb)
f2012/04/07kern/166724yongari[re] if_re watchdog timeout
f2011/11/12kern/162509yongari[re] [panic] Kernel panic may be related to if_re.c (realtek 8168 )
f2011/06/23kern/158201yongari[re] re0 driver quit working on Acer AO751h between 8.0 and 8.2 (also 9.0) [regression]
f2011/05/30kern/157429yongari[re] Realtek RTL8169 doesn't work with re(4)
o2011/05/24kern/157287net[re] [panic] INVARIANTS panic (Memory modified after free)
18 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.