PRs for tag 'ohci'
This is an experimental report containing PRs for tag 'ohci' as of 5-25-2012. 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 'ohci':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| f | 2009/09/16 | usb/138882 | usb | [ohci] [panic] [usb67] Can't install FreeBSD 7.2 due to ohci panic |
| o | 2008/04/07 | usb/122539 | usb | [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci_abort_xfer: not in process context |
| f | 2007/01/17 | usb/108056 | gavin | [usb67] [ohci] Mouse gets powered off during probe when plugged into second ohci-controller |
| o | 2007/01/11 | usb/107827 | usb | [usb67] [ohci] [panic] ohci_add_done addr not found |
| f | 2006/08/05 | usb/101448 | gavin | [usb67] [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/OHCI load |
| o | 2006/02/25 | usb/93828 | usb | [ohci] [panic] ohci causes panic on boot (HP Pavillion d4100e) |
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.