|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
|Significant new wireless functionality
is available in FreeBSD 6.0. As this functionality is rather new,
further testing would be appreciated.
|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
|sysinstall dhclient problems
|Scott Long, Sam Leffler
|sysinstall has been updated to deal
with the new DHCP client in 6.0, more testing is needed.
|The ULE scheduler has been fixed on
both HEAD and RELENG_6. More testing is needed.
|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
|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
|fdisk & boot0cfg
|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
|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
|page fault at if_ethersubr.c: 284
|Found by stress tests at http://www.holm.cc/stress/log/cons141.html.
|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
|Found by stress tests at http://www.holm.cc/stress/log/cons138.html.
|A 'memory modified after free' bug
affecting M_SAVEDINO. Possibly a softupdates bug.
|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
|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
|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
|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
|Don “Truck” Lewis, Tor Egge
|Found by stress tests at http://www.holm.cc/stress/log/cons142.html.
|Don “Truck” Lewis
|Found by stress tests at http://www.holm.cc/stress/log/cons143.html.
|fpudna: fpcurthread == curthread 1
|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
|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.
|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.