From owner-freebsd-www@FreeBSD.ORG Mon Mar 13 21:01:36 2006 Return-Path: X-Original-To: freebsd-www@hub.freebsd.org Delivered-To: freebsd-www@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1BE916A44F for ; Mon, 13 Mar 2006 21:01:36 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D356543D79 for ; Mon, 13 Mar 2006 21:01:05 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k2DL15Zc000736 for ; Mon, 13 Mar 2006 21:01:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k2DL154F000735; Mon, 13 Mar 2006 21:01:05 GMT (envelope-from gnats) Resent-Date: Mon, 13 Mar 2006 21:01:05 GMT Resent-Message-Id: <200603132101.k2DL154F000735@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-www@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Daniel Gerzo Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF24D16A401 for ; Mon, 13 Mar 2006 21:00:28 +0000 (UTC) (envelope-from danger@tomas.elvandar.org) Received: from tomas.elvandar.org (tomas.elvandar.org [217.148.169.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1D6543D55 for ; Mon, 13 Mar 2006 21:00:27 +0000 (GMT) (envelope-from danger@tomas.elvandar.org) Received: by tomas.elvandar.org (Postfix, from userid 1002) id E7C83483FB8; Mon, 13 Mar 2006 21:00:26 +0000 (UTC) Message-Id: <20060313210026.E7C83483FB8@tomas.elvandar.org> Date: Mon, 13 Mar 2006 21:00:26 +0000 (UTC) From: Daniel Gerzo To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: www/94423: [patch] XML'ified release todo list X-BeenThere: freebsd-www@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Gerzo List-Id: FreeBSD Project Webmasters List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2006 21:01:37 -0000 >Number: 94423 >Category: www >Synopsis: [patch] XML'ified release todo list >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-www >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon Mar 13 21:01:05 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Daniel Gerzo >Release: FreeBSD 6.1-PRERELEASE i386 >Organization: rulez.sk >Environment: System: FreeBSD tomas.elvandar.org 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Wed Feb 15 02:22:30 CET 2006 root@redqueen.elvandar.org:/usr/obj/usr/src/sys/REDQUEEN i386 >Description: I'm submitting this PR because I don't want my work to get lost and since I've spent a few hours working on this and the work is finished, it would be really nice to see it commited sometime in future. Please, see this thread: http://lists.freebsd.org/mailman/htdig/freebsd-doc/2006-February/009667.html The patch has been updated against the latest todo list. >How-To-Repeat: >Fix: --- todo.diff begins here --- diff -ruN 6.1R/Makefile 6.1R.new/Makefile --- 6.1R/Makefile Sun Feb 12 15:36:17 2006 +++ 6.1R.new/Makefile Mon Mar 13 20:45:43 2006 @@ -7,19 +7,21 @@ .include "../Makefile.inc" .endif -DOCS= todo.sgml approvals.sgml -DOCS+= schedule.sgml +DOCS= approvals.sgml schedule.sgml + +SRCS.DEFAULT= todo.xsl +XMLDOCS= todo FETCHFILE= http://people.freebsd.org/~pho/stress/log/news.rdf FETCHCMD= /usr/bin/fetch -CLEANFILES+= news.rdf stress.html +CLEANFILES+= news.rdf stress.xml news.rdf: ${FETCHCMD} ${FETCHFILE} -stress.html: news.rdf stress.xsl - ${XSLTPROC} stress.xsl news.rdf > stress.html +stress.xml: news.rdf stress.xsl + ${XSLTPROC} stress.xsl news.rdf > stress.xml -todo.html: stress.html +todo.html: stress.xml .include "${WEB_PREFIX}/share/mk/web.site.mk" diff -ruN 6.1R/stress.xsl 6.1R.new/stress.xsl --- 6.1R/stress.xsl Wed Jan 25 23:58:36 2006 +++ 6.1R.new/stress.xsl Sun Jan 29 13:36:47 2006 @@ -7,25 +7,22 @@ version="1.0"> + method="xml" + indent="yes" + encoding="utf-8" + omit-xml-declaration="no"/> - Generated from XSLT -
    + -
  • - - - - -
    • + + <xsl:value-of select="*[local-name()='title']"/> + +     -
- + diff -ruN 6.1R/todo.dtd 6.1R.new/todo.dtd --- 6.1R/todo.dtd Thu Jan 1 00:00:00 1970 +++ 6.1R.new/todo.dtd Sun Jan 29 13:27:35 2006 @@ -0,0 +1,37 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff -ruN 6.1R/todo.sgml 6.1R.new/todo.sgml --- 6.1R/todo.sgml Wed Mar 8 03:48:13 2006 +++ 6.1R.new/todo.sgml Thu Jan 1 00:00:00 1970 @@ -1,494 +0,0 @@ - - - - - - %navincludes; - %includes; - %developers; - -N/A"> -Done"> -In progress"> -Needs testing"> -Not done"> -Unknown"> -Deferred for future release"> - - - - - - -]> - - - - -&header; - -

This is a list of open issues that need to be resolved for FreeBSD - &local.rel;. If you have any updates for this list, please e-mail - re@FreeBSD.org.

- - - -

Show stopper defects for &local.rel;-RELEASE

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IssueStatusResponsibleDescription
unreliable serial console&status.unknown;At the manual 'root mount' prompt, the serial console is very - unreliable and drops most characters.
i386 deadlocks with >16GB swap&status.deferred;&a.alc;i386 deadlocks if more than 16GB of swap is in use. - Increasing the kern.maxswzone tunable would be a workaround - this. Although a patch from &a.alc; is needed to allow this variable to - be increased, this is not suitable for 6.1R. This limitation should - be documented in the Release Notes.
unmount pending error&status.wip;&a.ssouhlal;When unmounting filesystems &a.kris; reports seeing this warning: /c: unmount pending error: blocks -68512 files 0. This dates back at least to 5.3. It might be associated with -filesystem corruption reported by many users in which the 'used' space -on a filesystem is negative; fsck -f is needed to correct this.
swap_pager warnings&status.unknown;&a.truckman;?When swapfiles are in use, there are often warnings printed: -swap_pager: indefinite wait buffer: bufobj: 0, blkno: 889347, size: 8192. There is also the possibility of deadlock.
umount -f panics&status.wip;&a.jeff;, &a.ssouhlal;panics from race conditions. - A patch from &a.jeff; seems to fix some of them.
quota deadlocks&status.wip;&a.jeff;Quota support is not locked properly and causes deadlocks. - A patch from &a.jeff; seems to fix some of them.
UFS deadlocks on amd64&status.unknown;&a.tegge;Seen by &a.kris;.
UFS deadlocks&status.unknown;Seen by Peter Jeremy.
sparc64 instability&status.unknown;&a.marius;sparc64 instability when accessing /dev/mem. Contact - &a.marius; or &a.kris; for debugging information.
sparc64 frequent hangs&status.unknown;no DDB break possible, so impossible to diagnose
serious sparc64 IPv6 panic&status.wip;&a.gnn;Triggered by just ping6'ing the box. It may even be a MI - issue, the reporter of this bug only uses IPv6 with - sparc64. This problem seems to be triggered even when debug.mpsafenet=0.
sort(1) does not work with some locales&status.new; sort(1) can cause a coredump with some locales. - See also gnu/93629.
exec_map depletion&status.wip;&a.ups;The exec_map is regularly running out of space - on machines running 7.0. &a.ups; has a proposed - patch and it seems to fix this problem.
NFS data corruption between two 7.0 machines&status.wip;&a.mohans;Running fsx between a 7.0 NFS client and server - detects data corruption. This problem can also be reproduced - by using 6.1 NFS server.
panic in fxp driver&status.wip;&a.andre;See http://people.freebsd.org/~pho/stress/log/cons186.html.
deadlock in vn_start_write() consumers&status.wip;&a.tegge;
panic in bpf&status.wip;&a.sam;killing tcpdump (e.g. with ^C) can cause panics in bpf.
devfs locking problem&status.wip;&a.jeff;It is trivial to deadlock it on an SMP system, and - there are other panics with device removal.
pty leak&status.wip;&a.cognet;Since 6.x has a hard-coded limit, once all ptys are - leaked things like ssh and login no longer work. - This seems devfs-related.
cpu_ipi_selected() can cause a trap on FreeBSD/sparc64&status.wip;&a.kmacy;On sparc64, cpu_ipi_selected() can cause a trap (which is bad since - it appears in the trap code path).
rpc.lockd interoperability problems&status.unknown;&a.kuriyama;After this commit - rpc.lockd seems to have interoperability problems. - This may be the cause of the many "rpc.lockd no longer interoperates" - bug reports seen on -stable.
dup(2) regression on 6.x&status.unknown;&a.des;Simple "close(0); dup(fd)" does not return descriptor "0" in some cases. - This problem has been reported in - kern/87208, - and there is a proposed patch in the PR, too.
ifconfig regression on 6.x&status.wip;&a.yar;ifconfig cannot handle vlan and mtu parameters at the same time - after rev.1.7.2.3 of sbin/ifconfig/ifvlan.c commit. - For more information and a proposed patch, see - bin/94028.
"calcru: runtime went backwards" problem for threaded program&status.unknown; stress2 thr1 test can trigger "calcru: runtime went backwards" problem - and there are also many similar reports on -stable and -current. - &a.phk; committed a possible fix (src/sys/kern/kern_tc.c rev.1.169) to - update the calibration code to be more precise on 2 March.
- -

Required features for &local.rel;-RELEASE

- - - - - - - - - - -
IssueStatusResponsibleDescription
- -

Desired features for &local.rel;-RELEASE

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IssueStatusResponsibleDescription
SMP kernels for install&status.unknown;From the ideas - page. Right now we only install a UP kernel, for performance - reasons. We should be able to package both a UP and SMP kernel - into the release bits, and have sysinstall install both. It - should also select the correct one for the target system and - make that the default on boot. The easiest way to do this would - be to have sysinstall boot an SMP kernel and then look at the - hw.ncpu sysctl. The only problem is being able to have - sysinstall fall back to booting a UP kernel for itself if the - SMP one fails. This can probably be 'faked' by setting one of - the SMP-disabling variables in the loader. But in any case, the - point is to make the process Just Work for the user, without the - user needing to know arcane loader/sysctl knobs. SMP laptops are - here, and we should be ready to support SMP out-of-the-box.
swap panic on sparc64&status.unknown;&a.kris; has panic info&a.kris; reports configuring a 74GB swap-backed md on sparc64 that - caused a panic after a week or two of load (during which time - swap was slowly filling as more of the md was dirtied).
updated hal and ath drivers&status.new;&a.sam;
fix ntpdate(1) bogus output on amd64.&status.unknown;&a.roberto;
Improve performance&status.unknown;What seem to be 4BSD scheduler bugs in 6.0 that - cause performance to be anomalously low in certain situations. - &a.davidxu; has expressed some interest in this problem.
/dev/kmem panic&status.wip;&a.ups;&a.kris; has noticed panics on SMP machines when there was ABI - breakage of libkvm and world was not rebuilt and utilities like - fstat were used. This suggests panics can be caused by incorrect - accesses to /dev/kmem. &a.ups; committed a fix for i386.
KLDs on sparc64&status.new; On sparc64 machines with more than 4Gb memory KLDs are not usable - and will panic the system. The problem is reportedly with how the - KLDs are compiled, it only works if the code ends up below 4G.
Max RAM on sparc64&status.new; Maximum RAM on sparc64 appears to be limited to 16Gb.
make -jN&status.new; Doing 'make -jN', then suspending/resuming it may result in make - reporting it lost child process(es).
OpenBSM&status.unknown;&a.rwatson;The integration of OpenBSM is waiting on some final licensing hurdles. - Once those are cleared, it will be a very desirable feature for &local.rel;.
update sysinstall disk labeling&status.wip;&a.rodrigc;Sysinstall could use the same fixes recently made to fdisk so it - plays nice with GEOM and disk labeling. This does not cause problems - during install because nothing on the disk is mounted when its label - is being manipulated but it can cause problems if sysinstall gets - used on a live system to adjust labels on existing disks which - sys-admins tend to do.
swapping on 6.0 is slower than on 4.x&status.new; Performance on swap handling is much slower than 4.x and - this can make a system essentially unusable when moderate - paging activity is going on.
- -

Documentation items that must be resolved for &local.rel;

- - - - - - - - - - -
IssueStatusResponsibleDescription
- -

Testing foci for &local.rel;-RELEASE

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IssueStatusResponsibleDescription
manual root mount lockmgr panics&status.untested;&a.ssouhlal;Specifying a manual root mount location causes lockmgr panics. - &a.ssouhlal; has committed a patch for this.
dhclient causes ipv6 panics.&status.untested;&a.dougb;&a.dougb; has more details about this.
amd64 panics in ipv6 with date(1)&status.untested;&a.ume;amd64 panics in ipv6 when the date is changed using date(1) or - ntpdate(1). This may be a MI issue.
grep(1) -w does not work with multibyte locales&status.untested;&a.tjr;grep(1) -w generates wrong results with non-UTF-8 - multibyte locales. &a.tjr; has committed a patch - to -HEAD. See also gnu/91909.
Improve kbdmux&status.wip;&a.emax;From the ideas - page. We need this for the growing number of systems - that assume that USB is the primary keyboard. Current status - appears to be that the kbdmux driver breaks very easily. We need - this working well enough where it can be enabled by default, and - all attached keyboards Just Work. &a.emax; commit kbdmux and - rc.d/syscons patches in HEAD and RELENG_6. It is not yet enabled - by default. See kbdmux(4) and contact &a.emax; if you have - problems.
- -

Stress Test Panics

- - -

The system is continuously being subjected to Peter Holm's Kernel Stress Test Suite. The - following issues have recently been discovered from this test - suite.

- -&stresstest; - - &footer; - - - diff -ruN 6.1R/todo.xml 6.1R.new/todo.xml --- 6.1R/todo.xml Thu Jan 1 00:00:00 1970 +++ 6.1R.new/todo.xml Mon Mar 13 20:33:54 2006 @@ -0,0 +1,401 @@ + + + + + + + + + $FreeBSD:$ + + + + + Unreliable serial console + + At the manual 'root mount' prompt, the serial console is very + unreliable and drops most characters. + + + + + Manual root mount lockmgr panics + Suleiman Souhlal + + Specifying a manual root mount location causes lockmgr panics. + ssouhlal@ has committed a patch for this. + + + + + i386 deadlocks with more than 16GB swap + Alan L. Cox + + i386 deadlocks if more than 16GB of swap is in use. Increasing + the kern.maxswzone tunable would be a workaround this, but a patch + from alc@ is needed to allow this variable to be increased. + + + + + Unmount pending error + Suleiman Souhlal + + When unmounting filesystems Kris Kennaway reports seeing this + warning: /c: unmount pending error: blocks -68512 files 0. + This dates back at least to 5.3. It might be associated with + filesystem corruption reported by many users in which the 'used' + space on a filesystem is negative; fsck -f is needed to correct + this. + + + + + swap_pager warnings + Don Lewis? + + When swapfiles are in use, there are often warnings printed: + swap_pager: indefinite wait buffer: bufobj: 0, blkno: 889347, + size: 8192. There is also the possibility of deadlock. + + + + + umount -f panics + Jeff Roberson, Suleiman Souhlal + + Panics from race conditions. A patch from Jeff Roberson seems to + fix some of them. + + + + + UFS deadlocks on amd64 + Tor Egge + + Seen by Kris Kennaway. + + + + + UFS deadlocks + + Seen by Peter Jeremy. + + + + + amd64 panics in ipv6 with date(1) + Hajimu UMEMOTO + + amd64 panics in ipv6 when the date is changed using date(1) or + ntpdate(1). This may be a MI issue. + + + + + sparc64 instability. + Marius Strobl + + sparc64 instability when accessing /dev/mem. Contact marius@ or + kris@ for debugging information. + + + + + dhclient causes ipv6 panics. + Doug Barton + + dougb@ has more details about this. + + + + + sparc64 frequent hangs + unknown + + No DDB break possible, so impossible to diagnose. + + + + + Serious sparc64 IPv6 panic + George V. Neville-Neil + + Triggered by just ping6'ing the box. It may even be a MI issue, + the reporter of this bug only uses IPv6 with sparc64. This problem + seems to be triggered even when debug.mpsafenet=0. + + + + + SMP kernels for install + + From the ideas + page. Right now we only install a UP kernel, for + performance reasons. We should be able to package both a UP and + SMP kernel into the release bits, and have sysinstall install + both. It should also select the correct one for the target system + and make that the default on boot. The easiest way to do this + wouldbe to have sysinstall boot an SMP kernel and then look at the + hw.ncpu sysctl. The only problem is being able to have sysinstall + fall back to booting a UP kernel for itself if the SMP one fails. + This can probably be 'faked' by setting one of the SMP-disabling + variables in the loader. But in any case, the point is to make + the process Just Work for the user, without the user needing to + know arcane loader/sysctl knobs. SMP laptops are here, and we + should be ready to support SMP out-of-the-box. + + + + + Improve kbdmux + Maksim Yevmenkin + + From the ideas + page. We need this for the growing number of systems + that assume that USB is the primary keyboard. Current status + appears to be that the kbdmux driver breaks very easily. We need + this working well enough where it can be enabled by default, and + all attached keyboards Just Work. + + + + + swap panic on sparc64 + Kris Kennaway has panic info + + Kris reports configuring a 74GB swap-backed md on sparc64 that + caused a panic after a week or two of load (during which time swap + was slowly filling as more of the md was dirtied). + + + + + Updated hal and ath drivers + Sam Leffler + + + + Fix ntpdate(1) bogus output on amd64. + Ollivier Robert + + + + Improve performance + + What seem to be 4BSD scheduler bugs in 6.0 that cause performance + to be anomalously low in certain situations. davidxu@ has + expressed some interest in this problem. + + + + + /dev/kmem panic + Stephan Uphoff + + Kris has noticed panics on SMP machines when there was ABI + breakage of libkvm and world was not rebuilt and utilities like + fstat were used. This suggests panics can be caused by incorrect + accesses to /dev/kmem. Stephan Uphoff committed a fix for i386. + + + + + KLDs on sparc64 + + On sparc64 machines with more than 4Gb memory KLDs are not usable + and will panic the system. The problem is reportedly with how the + KLDs are compiled, it only works if the code ends up below 4G. + + + + + Max RAM on sparc64 + + Maximum RAM on sparc64 appears to be limited to 16Gb. + + + + + make -jN + + Doing 'make -jN', then suspending/resuming it may result in make + reporting it lost child process(es). + + + + + OpenBSM + Robert Watson + + The OpenBSM has been MFC'ed to RELENG_6 and needs some testing. + + + + + Update sysinstall disk labeling + Craig Rodrigues + + Sysinstall could use the same fixes recently made to fdisk so it + plays nice with GEOM and disk labeling. This does not cause + problems during install because nothing on the disk is mounted + when its label is being manipulated but it can cause problems if + sysinstall gets used on a live system to adjust labels on existing + disks which sys-admins tend to do. + + + + + Quota deadlocks + Jeff Roberson + + Quota support is not locked properly and causes deadlocks. A + patch from Jeff Roberson seems to fix some of them. + + + + + sort(1) does not work with some locales + + sort(1) can cause a coredump with some locales. See also + gnu/93629. + + + + + exec_map depletion + Stephan Uphoff + + The exec_map is regularly running out of space on machines running + 7.0. Stephan Uphoff has a proposed patch and it seems to fix this + problem. + + + + + NFS data corruption between two 7.0 machines + Mohan Srinivasan + + Running fsx between a 7.0 NFS client and server detects data + corruption. This problem can also be reproduced by using 6.1 NFS + server. + + + + + Panic in fxp driver + Andre Oppermann + + See + http://people.freebsd.org/~pho/stress/log/cons186.html. + + + + + Deadlock in vn_start_write() consumers + Tor Egge + + + + panic in bpf + Sam Leffler + + Killing tcpdump (e.g. with ^C) can cause panics in bpf. + + + + + devfs locking problem + Jeff Roberson + + It is trivial to deadlock it on an SMP system, and there are other + panics with device removal. + + + + + pty leak + Olivier Houchard + + Since 6.x has a hard-coded limit, once all ptys are leaked things + like ssh and login no longer work. This seems to be related to + devfs. + + + + + cpu_ipi_selected() can cause a trap on sparc64 + Kip Macy + + On sparc64, cpu_ipi_selected() can cause a trap (which is bad + since it appears in the trap code path). + + + + + rpc.lockd interoperability problems + Jun Kuriyama + + After + this commit rpc.lockd seems to have interoperability + problems. This may be the cause of the many "rpc.lockd no longer + interoperates" bug reports seen on -stable. + + + + + dup(2) regression on 6.x + Dag-Erling Smorgrav + + Simple "close(0); dup(fd)" does not return descriptor "0" in some + cases. This problem has been reported in kern/87208, and there is + a proposed patch in the PR, too. + + + + + ifconfig regression on 6.x + Yar Tikhiy + + ifconfig can not handle vlan and mtu parameters at the same time + after rev.1.7.2.3 of sbin/ifconfig/ifvlan.c commit. For more + information and a proposed patch, see bin/94028. + + + + + "calcru: runtime went backwards" problem for threaded + program + + stress2 thr1 test can trigger "calcru: runtime went backwards" + problem and there are also many similar reports on -stable and + -current. Poul-Henning Kamp committed a possible fix + (src/sys/kern/kern_tc.c rev.1.169) to update the calibration code + to be more precise on 2 March. + + + + + Swapping on 6.0 is slower than on 4.x + + Performance on swap handling is much slower than 4.x and this can + make a system essentially unusable when moderate paging activity + is going on. + + + diff -ruN 6.1R/todo.xsl 6.1R.new/todo.xsl --- 6.1R/todo.xsl Thu Jan 1 00:00:00 1970 +++ 6.1R.new/todo.xsl Mon Mar 13 20:39:50 2006 @@ -0,0 +1,221 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ + + +
+ + + +
+ + + +

This is a list of open issues that need to be resolved for + FreeBSD -RELEASE. If you + have any updates for this list, please e-mail + re@FreeBSD.org.

+ + + +

Show stopper defects for -RELEASE

+ + + + + + + + + + + + +
IssueStatusResponsibleDescription
+ +

Required features for -RELEASE

+ + + + + + + + + + + + +
IssueStatusResponsibleDescription
+ +

Desired features for -RELEASE

+ + + + + + + + + + + + +
IssueStatusResponsibleDescription
+ +

Documentation items that must be resolved for -RELEASE

+ + + + + + + + + + + + +
IssueStatusResponsibleDescription
+ +

Testing focuses for -RELEASE

+ + + + + + + + + + + + +
IssueStatusResponsibleDescription
+ +

Stress Test Panics

+ +

The system is continuously being subjected to Peter Holm's Kernel Stress Test Suite. + The following issues have recently been discovered from this + test suite.

+ +
    + +
  • + + + + +
    • +     +
+ +
+
+ +
+ + + +
+
+ + + + + + + + + + + N/A + + + Done + + + In progress + + + Needs testing + + + Not done + + + Unknown + + + Deferred for future release + + + + + + + --- todo.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: