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

Site Navigation

PRs for tag 'firewire'

This is an experimental report containing PRs for tag 'firewire' as of 4-24-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 'firewire':
SSubmittedTrackerResp.Description
p2013/03/02kern/176596ae[firewire] [ip6] Crash with IPv6 and Firewire
o2011/10/16kern/161702firewire[firewire] Firewire messages on DELL E6520 running 8.2 or 9.0-BETA3
o2011/03/06kern/155303firewire[firewire] Mounted firewire disks prevent reboot
o2010/03/18kern/144843firewire[firewire] [panic] fwcontrol(8) -S causes kernel panic
o2010/02/07kern/143623firewire[firewire] firewire fails to attach DV camera and download DV stream
o2009/10/12kern/139549firewire[firewire] reconnecting a firewire disk does not cause the disklabel to update correctly/invalidate the cache
o2008/11/28kern/129261firewire[firewire] Kernel crash on boot with disconnected firewire
p2008/07/16kern/125673firewire[firewire] [panic] FreeBSD7 panics when kldunloading firewire
o2008/04/21kern/122951firewire[firewire] video-transfer via fwcontrol triggers a panic (fwdev)
o2007/11/16kern/118093firewire[firewire] firewire bus reset hogs CPU, causing data to be lost
o2007/06/17kern/113785firewire[firewire] dropouts when playing DV on firewire
o2006/05/13kern/97208firewire[firewire] System hangs / locks up when a firewire disk is attached
o2004/11/22kern/74238firewire[firewire] fw_rcv: unknown response; firewire ad-hoc work around fails;
s2004/07/18kern/69218firewire[firewire] [patch] failure: 4.10-BETA and later do not boot on Asus A7N8X motherboards
14 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.