Date: Thu, 29 May 2003 09:00:14 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.org> To: current@FreeBSD.org Subject: 5.1-RELEASE TODO Message-ID: <200305291300.h4TD0ErX009243@fledge.watson.org>
next in thread | raw e-mail | index | archive | help
This is an automated bi-daily mailing of the FreeBSD 5.1 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.1R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.1.
FreeBSD 5.1 Open Issues
Open Issues
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.
Must Resolve Issues for 5.1-RELEASE
+------------------------------------------------------------------------+
| Issue | Status | Responsible | Description |
|-------------------+-------------+---------------+----------------------|
| | | | There are reports of |
| | | | alignment problems |
| ipfw/ipfw2 | | | with ipfw and/or |
| alignment issues | In progress | Luigi Rizzo | ipfw2 on 64-bit |
| on alpha/sparc64 | | | platforms |
| | | | (specifically alpha |
| | | | and sparc64). |
|-------------------+-------------+---------------+----------------------|
| | | | Kris Kennaway |
| | | | reports high |
| | | | instability of |
| | | | 5.0-CURRENT on ia64 |
| ia64 stability | -- | -- | machines, such as |
| | | | the pluto* machines. |
| | | | These problems need |
| | | | to be fixed in order |
| | | | to get a successful |
| | | | package build. |
|-------------------+-------------+---------------+----------------------|
| | | | Brian Feldman has |
| | | | submitted patches to |
| | | | improve the |
| | | | consistency of the |
| | | | pathnames passed |
| MAC Framework | | | into the MAC |
| devfs path fixes | In progress | Robert Watson | Framework devfs |
| | | | labeling entry |
| | | | points. These |
| | | | patches need to be |
| | | | thoroughly reviewed |
| | | | and tested, then |
| | | | merged. |
|-------------------+-------------+---------------+----------------------|
| | | | If a network device |
| | | | driver, possibly any |
| Panic on | | | driver, is linked |
| load/unload a | | | into the kernel and |
| kernel module for | Patch | Maxime | then loaded and |
| a driver already | approved | Henrion | unloaded as a |
| statically linked | | | module, the kernel |
| into the kernel. | | | will panic. This has |
| | | | been observed with |
| | | | both if_dc and |
| | | | if_fxp. |
|-------------------+-------------+---------------+----------------------|
| | | | Update the run-time |
| rtld-elf | patch | Alexander | link editor (rtld) |
| thread-safety | submitted | Kabaev | thread-safe with |
| | | | libpthread. |
|-------------------+-------------+---------------+----------------------|
| | | | rpc.lockd(8) |
| | | | client-side and |
| | | | server-side NFS |
| | | | locking appears to |
| | | | have a number of |
| | | | serious bugs which |
| rpc.lockd(8) | | | prevent NFS locking |
| stability | In progress | Robert Watson | 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. |
|-------------------+-------------+---------------+----------------------|
| | | | 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 |
| data corruption | | Peter Wemm, | processors, but it's |
| reports | In progress | Bosko Milekic | 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. |
+------------------------------------------------------------------------+
Desired Features for 5.1-RELEASE
+------------------------------------------------------------------------+
| Issue | Status | Responsible | Description |
|---------------+-----------+----------------+---------------------------|
| | | | 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 |
| Race | | | being debugged. A bug |
| conditions in | Errata | Robert Drehmel | also appears to exist |
| truss | candidate | | 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. |
+------------------------------------------------------------------------+
Documentation items that must be resolved for 5.1
+------------------------------------------------------------------------+
| Issue | Status | Responsible | Description |
|------------+-------------+--------------+------------------------------|
| | | | As BUSDMA is now the |
| | | | required driver API for DMA |
| | | | access in hardware device |
| | | | drivers as of 5.1-RELEASE, |
| busdma man | In progress | Hiten Pandya | we need to make sure it's |
| page | | | properly documented. A man |
| | | | page is in progress and |
| | | | needs to be appropriately |
| | | | reviewed and committed prior |
| | | | to the release. |
+------------------------------------------------------------------------+
Areas requiring immediate testing
+------------------------------------------------------------------------+
| Issue | Status | Responsible | Description |
|-------------------+--------+---------------+---------------------------|
| | | | The 20030228 vendor |
| Fresh ACPI-CA | -- | -- | sources have been |
| import | | | imported. Further testing |
| | | | is appreciated. |
|-------------------+--------+---------------+---------------------------|
| | | | PAE support allows the |
| | | | use of up to 64GB of RAM |
| PAE support for | -- | -- | on Pentium Pro and above |
| i386 | | | systems. Virtual |
| | | | addresses are still |
| | | | constrained to 32-bits. |
|-------------------+--------+---------------+---------------------------|
| | | | The recently upgraded |
| | | | if_wi driver is more |
| | | | tuned to Prism hardware |
| | | | than to Lucent hardware, |
| if_wi problems on | | | resulting in system |
| Lucent hardware | -- | -- | lockups and poor |
| | | | performance when using |
| | | | Lucent hardware. These |
| | | | problems are believed to |
| | | | be fixed but more testing |
| | | | is welcome. |
|-------------------+--------+---------------+---------------------------|
| | | | For 5.1-RELEASE, the |
| | | | default file system type |
| | | | for newly created file |
| | | | systems is UFS2 rather |
| UFS2 as | | | than UFS1. newfs(8) and |
| installation, | -- | Robert Watson | sysinstall(8) have been |
| newfs default | | | updated to use this new |
| | | | default. Testing to make |
| | | | sure all goes well after |
| | | | the change (committed on |
| | | | April 20, 2003) is vital. |
|-------------------+--------+---------------+---------------------------|
| | | | Support for pluggable |
| | | | directory services using |
| | | | NSS, including |
| | | | adaptations of current |
| | | Jacques | directory services (local |
| NSSwitch support | -- | Vidrine | databases, NIS), and |
| | | | support for new services |
| | | | (LDAP, Active Directory, |
| | | | etc). This change has |
| | | | been committed, and |
| | | | requires broader testing. |
|-------------------+--------+---------------+---------------------------|
| | | | Kris Kennaway reports |
| | | | that he has seen several |
| | | | unique panics on the |
| Spurious alpha | | | alpha machines, but since |
| panics | -- | -- | 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. |
+------------------------------------------------------------------------+
----------------------------------------------------------------------
freebsd-qa@FreeBSD.ORG
Copyright (c) 1995-2003 The FreeBSD Project. All rights reserved.
Last modified: 2003/05/29 03:17:48
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305291300.h4TD0ErX009243>