PRs for tag 'zyd'
This is an experimental report containing PRs for tag 'zyd' as of 5-30-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 'zyd':
S | Submitted | Tracker | Resp. | Description |
---|---|---|---|---|
o | 2011/08/29 | kern/160296 | wireless | [zyd] [panic] 802.11 usb device reboots system on 'ifconfig wlan0 up scan' |
o | 2011/01/01 | usb/153609 | usb | [zyd] [panic] kernel: Fatal trap 12: page fault while in kernel mode |
o | 2010/09/23 | usb/150892 | usb | [zyd] Whenever network contacted in any shape, way or form, "zyd0: unsupported rate 0" presents itself. |
o | 2009/08/28 | kern/138292 | usb | [zyd] [usb8] "zyd0: device timeout" with ZyXEL G-202 |
f | 2008/11/10 | usb/128745 | usb | [zyd] zyd theoretically supported usb device makes kernel panic |
f | 2007/10/13 | usb/117150 | usb | [zyd] usb zyd device under moderate load panics system |
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.