diff --git a/en/releases/6.1R/todo.sgml b/en/releases/6.1R/todo.sgml index 1d60ad713e..75e26e02a7 100644 --- a/en/releases/6.1R/todo.sgml +++ b/en/releases/6.1R/todo.sgml @@ -1,370 +1,388 @@ - + %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

- + + 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. - + - + - - - - - - - - - - - - - - + + + + + +
Issue Status Responsible Description
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.wip;&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, but a patch from &a.alc; is needed to allow this variable to - be increased.
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.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.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.
amd64 panics in ipv6 with date(1)&status.untested;&a.ume; and &a.dwmalone;amd64 panics in ipv6 when the date is changed using date(1) or - ntpdate(1). This may be a MI issue.
sparc64 instability. &status.unknown; &a.marius; sparc64 instability when accessing /dev/mem. Contact &a.marius; or &a.kris; for debugging information.
dhclient causes ipv6 panics.&status.unknown;&a.dougb; has more details about this.
sparc64 frequent hangs &status.unknown; no DDB break possible, so impossible to diagnose
serious sparc64 IPv6 panic &status.unknown; &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.
sort(1) does not work with some locales&status.new; sort(1) can cause a coredump with some locales. + See also gnu/93629.

Required features for &local.rel;-RELEASE

Issue Status Responsible Description

Desired features for &local.rel;-RELEASE

- - + + + accesses to /dev/kmem. &a.ups; committed a fix for i386. -
Issue Status Responsible Description
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.
Improve kbdmux &status.unknown; &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.
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.new; &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.
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;

Issue Status Responsible Description

Testing foci for &local.rel;-RELEASE

+ + + + + + + + + + + + + + + + + + + + +
Issue Status Responsible Description
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.

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;