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. |
| 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 |
|---|---|---|---|
| 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. |
| Issue | Status | Responsible | Description |
|---|---|---|---|
| busdma man page | -In progress | -&a.hmp; | -As BUSDMA is now the required driver API for DMA access in - hardware device drivers as of 5.1-RELEASE, we need to make sure - it's properly documented. A man page is in progress and needs - to be appropriately reviewed and committed prior to the release. | -
| 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. |