diff --git a/en/releases/6.0R/todo.sgml b/en/releases/6.0R/todo.sgml index c6f781fa35..70fbcad69a 100644 --- a/en/releases/6.0R/todo.sgml +++ b/en/releases/6.0R/todo.sgml @@ -1,418 +1,416 @@ - + %includes; %developers; N/A"> Done"> In progress"> Needs testing"> Not done"> Unknown"> ]> &header;

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

Show stopper defects for 6.0-RELEASE

Issue Status Responsible Description
race condition in POSIX named fifos &status.wip; &a.rwatson; There have been multiple reports of panics when running with make -j on SMP systems, which appear to be associated with a race condition in the POSIX named fifo support. A number of regression tests have been written to confirm that any fix doesn't break fifos, and a number of other unrelated bugs were fixed in the process. The cause of the symptoms has been identified, and a workaround has been committed to 7-CURRENT for testing; it will be merged to RELENG_6 after additional testing.

Required features for 6.0-RELEASE

Issue Status Responsible Description
beastie.4th &status.wip; &a.scottl; Need to address the shortcomings of the old beastie.4th boot menu and hook it back into the boot process. This includes making the graphics easier to select and override, and making it use simple scrolling instead of ANSI screen addressing.

Desired features for 6.0-RELEASE

- - - - - - - -
Issue Status Responsible Description
fpudna: fpcurthread == curthread 1 times &status.wip; &a.ups; This warning is appearing sporadically on a dual AMD64 system. It appears to be warning against a legitimate problem, and thus should be investigated and fixed.
devfs umount panic &status.new;   There is a race condition between device removal and devfs umounts that causes "Memory modified after free" panics. Can be reproduced by doing 'mdconfig -u' concurrently with unmounting a devfs instance.
/dev/kmem panic &status.new;   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.
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.wip; &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 6.0.
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 doesn't 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.
"snaplk" livelock &status.wip;   Found by stress tests at http://www.holm.cc/stress/log/cons143.html.
panic: handle_written_inodeblock: live inodedep&status.unknown; Found by stress tests at http://www.holm.cc/stress/log/cons142.html.

Documentation items that must be resolved for 6.0

Issue Status Responsible Description
dhclient &status.new; freebsd-doc The ISC DHCP client v3.x has been removed in favor of the OpenBSD DHCP client which was based on ISC DHCP v2.X. Minimal updates to the FreeBSD Handbook may be required.
WPA / hostap &status.wip; loader@freebsdmall.com, sam@, murray@ Significant new wireless functionality will be available with FreeBSD 6.0. The wireless section of the FreeBSD Handbook should be updated to describe how to connect to networks with WPA keys, setup host access points, etc. A howto in progress is available here.

Testing foci for 6.0-RELEASE

+ + + + + +
Issue Status Responsible Description
New dhclient &status.untested; &a.brooks; The ISC DHCP client v3.x has been removed in favor of the OpenBSD DHCP client which was based on ISC DHCP v2.X. More testing is needed to make sure there are no major regressions in functionality. We are particularly interested in tests involving non-standard environments.
WPA / hostap &status.untested; &a.sam; Significant new wireless functionality is available in FreeBSD 6.0. As this functionality is rather new, further testing would be appreciated.
if_bridge &status.untested;   A new bridge implementation has been added from NetBSD. As this has not seen a wider audience yet, further testing would be appreciated. See if_bridge(4) for configuration details.
sysinstall dhclient problems &status.untested; &a.scottl;, &a.sam; sysinstall has been updated to deal with the new DHCP client in 6.0, more testing is needed.
ULE &status.untested; &a.davidxu; The ULE scheduler has been fixed on both HEAD and RELENG_6. More testing is needed.
aac(4) regression &status.untested; &a.scottl; There had been a regression in the aac device driver on Dell 2550 machines. This should be fixed but more testing would be good.
vnode_pager_init nswbuf initialization bug &status.untested; &a.kan; There had been a serious performance regression due to a very low bound on the number of swap buffers per vnode (1). This should be fixed but more testing would be good.
fdisk & boot0cfg &status.untested; &a.phk; The boot0cfg and fdisk utilities need to be updated to use the proper GEOM model for updating the boot sector of a mounted disk.
Alarming devfs shutdown error needs to be quenched &status.done; &a.rwatson; During system shutdown, devfs generates a spurious error message due to /dev being non-unmountable: "unmount of /dev failed (BUSY)". While this is not a product of serious breakage, it is a potentially alarming error, whose source should either be fixed, or the message should be forceably quenched, in order to avoid many false positive bug reports and user concern.
page fault at if_ethersubr.c: 284 &status.done; &a.glebius; Found by stress tests at http://www.holm.cc/stress/log/cons141.html.
Livelock &status.untested; &a.tegge; Found by stress tests at http://www.holm.cc/stress/log/cons139.html. This is the second most frequent panic reported by Peter Holm.
panic: softdep_setup_inomapdep: found inode &status.untested; &a.tegge; Found by stress tests at http://www.holm.cc/stress/log/cons138.html.
M_SAVEDINO &status.untested; &a.tegge; A 'memory modified after free' bug affecting M_SAVEDINO. Possibly a softupdates bug.
kgdb &status.untested; &a.marcel; kgdb has been modified to handle trap frames on all tier 1 and 2 architectures. This allows tracebacks to provide useful info.
panic: wrong b_bufobj &status.untested; &a.tegge; Found by stress tests at http://www.holm.cc/stress/log/cons140.html. This is high priority and can be provoked within minutes of testing!
Panic when filesystem fills &status.untested; &a.rwatson; Inadequate locking causes panics when calling kernel printf functions. This is most often seen when a filesystem fills up and uprintf() is called to report it to the console, but it can happen in many other places also. Properly locking the upper and lower parts of the tty subsystem likely cannot happen for 6.0, but temporary fixes must be developed and committed. A patch has now been committed that is believed to fix this problem by acquiring Giant in uprintf() and tprintf(), as well as a regression test. This work-around has now been merged to RELENG_6 and is ready for wide-spread testing.
panic on multicast socket close after interface removal &status.untested; &a.rwatson; Due to the addition of multicast locking, a long-present memory corruption bug now generates an immediate panic if an interface is removed while a multicast group is in use on the interface. This can manifest if running routed and using vlans. A regression test has now been committed as msocket_ifnet_remove. A short-term fix will be to GC references to the interface in the IPv4/IPv6 multicast socket options hung off of the inpcb; a long term solution will require determining the correct application semantics for interface removal as relates to multicast sockets. This problem is described in detail in PR kern/77665. A fix has now been committed to 7-CURRENT in the CVS HEAD, and merged to RELENG_6.
panic: handle_written_inodeblock: live inodedep&status.untested;&a.truckman; and &a.tegge;Found by stress tests at http://www.holm.cc/stress/log/cons142.html.

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;