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.
| Issue |
Status |
Responsible |
Description |
| 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.deferred; |
&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 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. |
| 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.done; |
&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.done; |
&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;, &a.tegge; |
Found by stress tests at http://www.holm.cc/stress/log/cons142.html. |
| "snaplk" livelock |
&status.untested; |
&a.truckman; |
Found by stress tests at http://www.holm.cc/stress/log/cons143.html. |
| fpudna: fpcurthread == curthread 1 times |
&status.untested; |
&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. |
| race condition in POSIX named fifos |
&status.done; |
&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 does not 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 has been merged to RELENG_6 for testing. |
| UFS_EXTATTR_AUTOSTART |
&status.done; |
&a.rwatson; |
Changes in VFS locking as part of the SMPng work have resulted in a
new panic during the auto-starting of UFS1 extended attributes. A
patch to fix this has been committed (ufs_extattr.c:1.82), and now
requires further testing before it is merged to RELENG_6 and
RELENG_6_0. |
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.
| Issue |
Status |
Responsible |
Description |
| 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, and occurs only under extreme stress
testing, not normal use. |
| 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. |
| 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. |
| "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. |
| 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. The problem seems to be avoidable by
turning off the attribute cache on the NFS client. |
| sort(1) does not work with some locales |
&status.new; |
|
sort(1) can cause a coredump with some locales.
See also gnu/93629. |
| unreliable serial console |
&status.unknown; |
|
At the manual 'root mount' prompt, the serial console is very
unreliable and drops most characters. This appears to be caused
by cngetc() polling the sio driver for input, and the sio driver
resetting the chip on every poll iteration. That results in a very
small window for it to accept input. Fixing this requires a
large review of the operation of the sio driver. The uart driver
looks to handle this better and might be a suitable replacement. |
| fix ntpdate(1) bogus output on amd64. |
&status.unknown; |
&a.roberto; |
|
| make -jN |
&status.new; |
|
Doing 'make -jN', then suspending/resuming it may result in make
reporting it lost child process(es). |
| 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. |
| 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. |
| panic in bpf |
&status.deferred; |
&a.sam; |
killing tcpdump (e.g. with ^C) can cause panics in bpf.
To fix this problem, some architectural changes are needed. |
| OpenBSM |
&status.deferred; |
&a.rwatson; |
The integration of OpenBSM is waiting on some final licensing hurdles.
It is expected to be available in the next 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; |
Doug Barton |
Doug Barton 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.untested; |
&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. |
| umount -f panics |
&status.untested; |
&a.jeff;, &a.ssouhlal; |
panics from race conditions.
A patch from &a.jeff; seems to fix some of them. |
| quota deadlocks |
&status.untested; |
&a.jeff; |
Quota support is not locked properly and causes deadlocks.
A patch from &a.jeff; seems to fix some of them. |
| ifconfig regression on 6.x |
&status.untested; |
&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. |
| SMP kernels for install |
&status.untested; |
&a.sam; |
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. |
| dup(2) regression on 6.x |
&status.untested; |
&a.csjp; |
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. &a.csjp; has committed a
fix for this. |
| cpu_ipi_selected() can cause a trap on FreeBSD/sparc64 |
&status.untested; |
&a.marius; |
On sparc64, cpu_ipi_selected() can cause a trap (which is bad since
it appears in the trap code path). |
| UFS deadlocks on amd64 |
&status.untested; |
&a.tegge; |
Seen by &a.kris;. This problem seems MI. |
| UFS deadlocks |
&status.untested; |
&a.tegge; |
Seen by Peter Jeremy. |
| panic in fxp driver |
&status.untested; |
&a.andre; |
See http://people.freebsd.org/~pho/stress/log/cons186.html. |
| exec_map depletion |
&status.untested; |
&a.ups; |
The exec_map is regularly running out of space
on machines running 7.0. &a.ups; has a committed a
patch that seems to fix this problem. |
| /dev/mem instability |
&status.untested; |
&a.marius;, &a.ups; |
Instability when accessing /dev/mem. A fix was committed
for i386. amd64 does not seem to have the problem. A sparc64
fix is still in progress. |
| deadlock in vn_start_write() consumers |
&status.untested; |
&a.tegge; |
Many potential deadlocks have been fixed. |
These are problems that range in severity for FreeBSD/sparc64. They
will not hold up the release, but they will still be tracked for future
releases.
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.
| Issue |
Status |
Responsible |
Description |
| bce(4) stability fixes |
&status.untested; |
&a.scottl; |
Several stability fixes for bce(4) were merged from HEAD to
RELENG_6 around 20061024. Initial testing results have been
promising, but more testing reports would be useful. |
| em(4) stability fixes |
&status.untested; |
&a.scottl;, &a.jfv;, &a.glebius;, &a.kris; |
Several difficult-to-diagnose stability issues have been
observed in the em(4) driver since August. As of 20061027, a
newer driver provided by Intel (version 6.2.9) has been
committed to RELENG_6 for testing.
UPDATE: Additional changes committed 20061110 fix some
other observed stability problems and restore missing jumbo
frame functionality. |
| sysinstall(8) kernel selection fix |
&status.untested; |
&a.erwin; |
A bug in sysinstall(8) could result in it failing to install a
kernel on a new disk if the user did not choose a distribution
from the distribution menu. This is believed to have been
fixed as of 20061029, but could use more testing. |
| ggated(8) |
&status.untested; |
&a.pjd; |
A recently-committed patch to ggated(8) is believed to fix
some fairly serious problems, as reported in PR
kern/104829. |
| devfs(5) fixes |
&status.untested; |
&a.kib; |
Several deadlocks and locking bugs have been fixed in devfs(5). |
| tty(4) fixes |
&status.untested; |
&a.mbr; |
Several workarounds have been committed for known problems in
the tty(4) layer. |
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.
| Issue |
Status |
Responsible |
Description |
| routed not working |
&status.done; |
&a.rwatson; |
Routed should have been updated because of updates made to the
underlying network infrastructure. The old interface was added
back in but marked as depreciated. |
| TCP accept race condition |
&status.done; |
&a.glebius;, &a.rwatson; |
A race in TCP will lead to very occasional returning of 0.0.0.0:0
rather than the correct IP address via the socket address returned by
accept(). A patch has been merged to HEAD, RELENG_7 and RELENG_7_0.
|
| sleepq race condition |
&status.done; |
&a.jhb; |
Races in the sleepq implementation will occasionally result in
sleeps with timeouts failing to wake up, as well as other symptoms. A
patch has been merged to HEAD, RELENG_7, and RELENG_7_0. |
| pty race condition |
&status.done; |
&a.kib; |
Multiple race conditions in the tty/pty code have lead to
occasional panics. One set of problems has been fixed, but others
are still being explored It is aniticipated that the remaining
problems will be fixed for 7.0RC2. |
| amd64 minidump race condition |
&status.done; |
&a.ru; |
A race condition during minidump generation on SMP amd64 could lead
trashed file systems due to writing outside of the swap area. A patch
has been merged to HEAD, RELENG_7, and RELENG_7_0. |
| libkse fork process wedge |
&status.done; |
&a.julian;, &a.deischen; |
A bug in libkse could lead the processes hanging after fork if they
fork while running multiple threads. A patch has been committed to
HEAD that properly reinitializes internal thread library locks after
fork; it has been merged to RELENG_7 and RELENG_7_0. |