PRs for tag 'dc'
This is an experimental report containing PRs for tag 'dc' 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 'dc':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2014/04/22 | kern/188897 | net | [dc] dc ethernet driver seems to prevent the detection of other NIC chipsets |
| o | 2008/03/16 | kern/121761 | [cardbus] [dc] a cardbus dc0 causes a system freeze while transferring large data (7.0R) | |
| o | 2008/03/16 | kern/121759 | [cardbus] [dc] cardbus dc0 initialization failure at only first boot (7.0R) | |
| o | 2007/12/31 | kern/119205 | peterj | [dc] [patch] Collect various stats regarding dc(4) interrupts |
| s | 2006/01/24 | kern/92279 | net | [dc] Core faults everytime I reboot, possible NIC issue. |
| o | 2005/06/09 | kern/82070 | [dc] Not all dc(4) devices can be used: MII without any PHY | |
| o | 2003/08/20 | kern/55793 | [dc] Flaky behavior of if_dc when initializing a LNE100TX v2.0 (PNIC II 82c115) | |
| o | 2001/08/24 | kern/30052 | [dc] [patch] dc driver queues outgoing pkts indefinitely if no link |
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.