5.1-RELEASE TODO

From: Robert Watson <rwatson_at_FreeBSD.org>
Date: Tue, 27 May 2003 09:00:14 -0400 (EDT)
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_at_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  | submitted   | 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.              |
   |-------------------+-------------+---------------+----------------------|
   |                   |             |               | 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  |
   | KSE support for   |             | Jake          | make KSE available   |
   | sparc64, alpha,   | --          | Burkholder,   | on non-i386          |
   | ia64              |             | --, --        | 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.       |
   |-------------------+-------------+---------------+----------------------|
   |                   |             |               | Update the run-time  |
   | rtld-elf          | --          | Alexander     | link editor (rtld)   |
   | thread-safety     |             | 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       |
   |---------------+-------------+----------------+-------------------------|
   |               |             |                | ia64 serial console     |
   |               |             |                | support is reported to  |
   |               |             |                | not be functional on HP |
   | ia64 sio      |             | Marcel         | Itanium2 platforms. A   |
   | support       | In progress | Moolenaar,     | reworking of the sio    |
   |               |             | Warner Losh    | driver to improve       |
   |               |             |                | platform independence   |
   |               |             |                | and bus handling is     |
   |               |             |                | likely needed.          |
   |---------------+-------------+----------------+-------------------------|
   |               |             |                | A.out support in the    |
   | a.out         |             |                | base system was         |
   | toolchain     | --          | --             | reduced; the removed    |
   | port          |             |                | build chain components  |
   |               |             |                | should be made into a   |
   |               |             |                | port.                   |
   |---------------+-------------+----------------+-------------------------|
   |               |             |                | 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       |
   | Race          |             |                | debugged. A bug also    |
   | conditions in | Errata      | Robert Drehmel | appears to exist where  |
   | truss         | candidate   |                | 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.   |
   |---------------+-------------+----------------+-------------------------|
   |               |             |                | Kris Kennaway reports   |
   |               |             |                | deadlocks involving the |
   |               |             |                | use of nullfs in the    |
   |               |             |                | bento environment:      |
   |               |             |                | buildworld -j4 with src |
   |               |             |                | and obj mounted via     |
   | nullfs        | --          | --             | nullfs; the gcc         |
   | deadlocks     |             |                | processes eventually    |
   |               |             |                | deadlocked in the ufs   |
   |               |             |                | state. DDB traceback    |
   |               |             |                | showed two different    |
   |               |             |                | codepaths. I've just    |
   |               |             |                | repeated this, so the   |
   |               |             |                | bug still exists.       |
   |---------------+-------------+----------------+-------------------------|
   |               |             |                | 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.   |
   | amd/mountd    | In progress | Martin Blapp   | If truss or ktrace is   |
   | bugs          |             |                | 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        |             |                | gdb -k doesn't work on  |
   | doesn't work  | --          | Mark Peek      | alpha                   |
   | on alpha      |             |                |                         |
   +------------------------------------------------------------------------+

  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, we need to |
   | busdma man page | In progress | Hiten Pandya | make sure it's properly |
   |                 |             |              | documented. A man page  |
   |                 |             |              | is in progress and      |
   |                 |             |              | needs to be             |
   |                 |             |              | appropriately reviewed  |
   |                 |             |              | and committed prior to  |
   |                 |             |              | the release.            |
   |-----------------+-------------+--------------+-------------------------|
   |                 |             |              | rcNG is now the         |
   |                 |             |              | supported (and only)    |
   |                 |             |              | boot scripting          |
   | rcNG            |             |              | mechanism in 5.x, but   |
   | documentation   | In progress | Tom Rhodes   | it's not currently      |
   |                 |             |              | documented in the       |
   |                 |             |              | handbook. We need this  |
   |                 |             |              | documentation for       |
   |                 |             |              | 5.1-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_at_FreeBSD.ORG
    Copyright (c) 1995-2003 The FreeBSD Project. All rights reserved.
    Last modified: 2003/05/23 22:39:47
Received on Tue May 27 2003 - 04:01:01 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:09 UTC