Date: Mon, 8 Sep 2008 02:22:27 GMT From: FreeBSD bugmaster <bugmaster@FreeBSD.org> To: freebsd-sparc64@FreeBSD.org Subject: Current problem reports assigned to freebsd-sparc64@FreeBSD.org Message-ID: <200809080222.m882MRoq006818@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o sparc/127051 sparc64 [hme] hme interfaces "pause" with the message "device o sparc/119244 sparc64 X11Forwarding to X11 server on sparc crashes Xorg o sparc/119240 sparc64 top has WCPU over 100% on UP system s sparc/119239 sparc64 gdb coredumps on sparc64 o sparc/119017 sparc64 7.0 Beta won't install on U60 o sparc/118932 sparc64 7.0-BETA4/sparc-64 kernel panic in rip_output o sparc/113556 sparc64 panic: trap: memory address not aligned; Rebooting... o sparc/109908 sparc64 apache22 mod_perl issue on sparc64 f sparc/108732 sparc64 ping(8) reports 14 digit time on sparc64 s sparc/107087 sparc64 system is hinged during boot from CD f sparc/106251 sparc64 [libmalloc] malloc fails > for large allocations f sparc/105607 sparc64 [modules] modules on sparc64 don't work with >= 4GB f sparc/105157 sparc64 No reply to ping on Sparc64 o sparc/105048 sparc64 [trm] trm(4) panics on sparc64 o sparc/104428 sparc64 [nullfs] nullfs panics on E4500 (but not E420) o sparc/95297 sparc64 vt100 term does not work in install o sparc/80890 sparc64 [panic] kmem_malloc(73728): kmem_map too small running o sparc/80410 sparc64 [netgraph] netgraph is causing crash with mpd on sparc o sparc/71729 sparc64 printf in kernel thread causes panic on SPARC 19 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200809080222.m882MRoq006818>