PRs for tag 'irq'
This is an experimental report containing PRs for tag 'irq' 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 'irq':
S | Submitted | Tracker | Resp. | Description |
---|---|---|---|---|
o | 2010/09/15 | arm/150581 | arm | [irq] Unknown error generates IRQ address decoding error |
o | 2009/12/24 | i386/141942 | mav | [irq] interrupt storm (VIA 6421A atapci controller) |
o | 2009/11/17 | i386/140645 | i386 | [irq] High INTERRUPT rate on CPU 0 |
o | 2008/01/15 | kern/119696 | [irq] [ral] ral device causes massive interrupt storm sometimes | |
o | 2008/01/10 | kern/119513 | wireless | [ath] [irq] inserting dlink dwl-g630 wireless card results in interrupt storm [regression] |
o | 2007/10/28 | usb/117613 | usb | [uhci] [irq] uhci interrupt storm & USB leaked memory on destroy |
o | 2004/12/06 | kern/74786 | [irq] [patch] Smartlink Modem causes interrupt storm on RELENG_4 and RELENG_5 |
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.