This is a list of open issues that need to be resolved for FreeBSD
5.1. If you have any updates for this list, please e-mail
re@FreeBSD.org.
| Issue | Status | Responsible | Description |
|---|
| ipfw/ipfw2 alignment issues on alpha/sparc64 |
In progress |
&a.luigi; |
There are reports of alignment problems with ipfw and/or ipfw2
on 64-bit platforms (specifically alpha and sparc64). |
| ia64 stability |
-- |
-- |
&a.kris; reports high instability of 5.0-CURRENT on ia64
machines, such as the pluto* machines. These problems need to be
fixed in order to get a successful package build. |
| MAC Framework devfs path fixes |
In progress |
&a.rwatson; |
&a.green; has submitted patches to improve the consistency
of the pathnames passed into the MAC Framework devfs labeling
entry points. These patches need to be thoroughly reviewed
and tested, then merged. |
| Panic on load/unload a kernel module for a driver already
statically linked into the kernel. |
Patch submitted |
&a.mux; |
If a network device driver, possibly any driver, is linked
into the kernel and then loaded and unloaded as a module,
the kernel will panic. This has been observed with both
if_dc and if_fxp. |
| KSE support for sparc64, alpha, ia64 |
-- |
&a.jake;, --, -- |
Currently, the MD elements of KSE are present only for the i386
platform, limiting use of KSE to the i386 platform. It is highly
desirable to make KSE available on non-i386 platforms for
5.1-RELEASE so that KSE can see more broad exposure, and the
performance benefits of KSE can be visible to users of the
64-bit FreeBSD architectures. |
| rtld-elf thread-safety |
-- |
&a.kan; |
Update the run-time link editor (rtld) thread-safe with
libpthread. |
| rpc.lockd(8) stability |
In progress |
&a.rwatson; |
rpc.lockd(8) client-side and server-side NFS locking appears to
have a number of serious bugs which prevent NFS locking from working
properly in a number of common scenarios. These bugs must be
resolved to ship 5.1-RELEASE. Work is underway to classify and
track the bugs. |
| data corruption reports |
In progress |
&a.peter;, &a.bmilekic; |
There have been reports of memory/data corruption on some systems;
one working hypothesis is that this corresponds to an undocumented
bug in a particular line of Intel and AMD processors, but it's
unclear whether current work-arounds are correcting or masking the
problem. Patches are being circulated to test this hypothesis,
but developers are encouraged to be on the lookout for possible
data corruption bugs. |
| Issue | Status | Responsible | Description |
|---|
| ia64 sio support |
In progress |
&a.marcel;, &a.imp; |
ia64 serial console support is reported to not be functional
on HP Itanium2 platforms. A reworking of the sio driver to
improve platform independence and bus handling is likely needed. |
| a.out toolchain port |
-- |
-- |
A.out support in the base system was reduced; the removed build
chain components should be made into a port. |
| Race conditions in truss |
Errata candidate |
&a.robert; |
Truss appears to contain a race condition during the start-up of
debugging, which can result in truss failing to attach to the process
before it exits. The symptom is that truss reports that it cannot
open the procfs node supporting the process being debugged. A bug
also appears to exist where in truss will hang if execve() returns
ENOENT. A further race appears to exist in which truss will return
"PIOCWAIT: Input/output error" occasionally on startup. The fix
for this sufficiently changes process execution handling that we
will defer the fix to post-5.0 and consider this errata. |
| nullfs deadlocks |
-- |
-- |
&a.kris; reports deadlocks involving the use of nullfs in the bento
environment: buildworld -j4 with src and obj mounted via nullfs; the gcc
processes eventually deadlocked in the ufs state. DDB traceback
showed two different codepaths. I've just repeated this, so the bug
still exists. |
| amd/mountd bugs |
In progress |
&a.mbr; |
If amd(8) does mount more than one fs from a host, the second call
to mountd on the server gets aborted even if the read does return
EAGAIN. This is definitly a bug in the nonblocking rpc code. If truss
or ktrace is attached on mountd, the bug happens almost all times,
else 3-10 times of 10 trys. Since there have been several reports
of amd irregularity on 5.1-BETA, it's important to get this fixed
for the release. |
| gdb -k doesn't work on alpha |
-- |
&a.mp; |
gdb -k doesn't work on alpha |
| Issue | Status | Responsible | Description |
|---|
| Fresh ACPI-CA import |
-- |
-- |
The 20030228 vendor sources have been imported. Further testing is
appreciated. |
| PAE support for i386 |
-- |
-- |
PAE support allows the use of up to 64GB of RAM on Pentium Pro and above
systems. Virtual addresses are still constrained to 32-bits. |
| if_wi problems on Lucent hardware |
-- |
-- |
The recently upgraded if_wi driver is more tuned to Prism hardware
than to Lucent hardware, resulting in system lockups and poor performance
when using Lucent hardware. These problems are believed to be fixed
but more testing is welcome. |
| UFS2 as installation, newfs default |
-- |
&a.rwatson; |
For 5.1-RELEASE, the default file system type for newly created
file systems is UFS2 rather than UFS1. newfs(8) and sysinstall(8)
have been updated to use this new default. Testing to make sure all
goes well after the change (committed on April 20, 2003) is
vital. |
| NSSwitch support |
-- |
&a.nectar; |
Support for pluggable directory services using NSS, including
adaptations of current directory services (local databases, NIS),
and support for new services (LDAP, Active Directory, etc).
This change has been committed, and requires broader testing. |
| Spurious alpha panics |
-- |
-- |
&a.kris; reports that he has seen several unique panics on the
alpha machines, but since gdb -k doesn't work on alpha I haven't
been able to get more than a DDB traceback. No-one has looked
into them. |
&footer;