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

Site Navigation

PRs for tag 'rum'

This is an experimental report containing PRs for tag 'rum' as of 4-20-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 'rum':
SSubmittedTrackerResp.Description
o2010/08/14kern/149643net[rum] device not sending proper beacon frames in ap mode
p2010/05/18usb/146693thompsa[rum] Edimax EW&#8208;7318USG not found in usbdevs or if_rum.c
o2009/09/10kern/138688net[rum] possibly broken on 8 Beta 4 amd64: able to wpa authenticate + obtain dhclient address, no communication though.
p2009/08/14kern/137776net[rum] panic in rum(4) driver on 8.0-BETA2
o2009/08/01usb/137341usb[usb8][rum] driver if_rum doesn't work at all and throws panics
o2009/04/02usb/133296usb[rum] driver not working properly in hostap mode
o2009/02/25usb/132080usb[patch] [usb] [rum] [panic] Kernel panic after NOMEM caused by rum card
o2008/10/27usb/128418usb[panic] [rum] loading if_rum causes panic, looks like in usb stack
o2008/06/19usb/124758usb[rum] [panic] rum panics SMP kernel
o2008/05/25kern/123968net[rum] [panic] rum driver causes kernel panic with WPA.
o2008/02/22kern/120966net[rum] kernel panic with if_rum and WPA encryption
o2008/01/24kern/119945net[rum] [panic] rum device in hostap mode, cause kernel core dump.
12 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.