5.1-RELEASE TODO

From: Robert Watson <rwatson_at_FreeBSD.org>
Date: Wed, 7 May 2003 09:00:39 -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         |
   |------------------+----------+-------------+----------------------------|
   |                  |          |             | Kris Kennaway reports that |
   |                  |          |             | he has seen several unique |
   |                  |          |             | panics on the alpha        |
   | Spurious alpha   |          |             | machines, but since gdb -k |
   | panics           | --       | --          | doesn't work on alpha I    |
   |                  |          |             | haven't been able to get   |
   |                  |          |             | more than a DDB traceback. |
   |                  |          |             | No-one has looked into     |
   |                  |          |             | them.                      |
   |------------------+----------+-------------+----------------------------|
   | gdb -k doesn't   | --       | Mark Peek   | gdb -k doesn't work on     |
   | work on alpha    |          |             | alpha                      |
   |------------------+----------+-------------+----------------------------|
   |                  |          |             | There are reports of       |
   | ipfw/ipfw2       |          |             | alignment problems with    |
   | alignment issues | In       | Luigi Rizzo | ipfw and/or ipfw2 on       |
   | on alpha/sparc64 | progress |             | 64-bit platforms           |
   |                  |          |             | (specifically alpha and    |
   |                  |          |             | sparc64).                  |
   |------------------+----------+-------------+----------------------------|
   |                  |          |             | Kris Kennaway reports high |
   |                  |          |             | instability of 5.0-CURRENT |
   |                  |          |             | on ia64 machines, such as  |
   | ia64 stability   | --       | --          | the pluto* machines. These |
   |                  |          |             | problems need to be fixed  |
   |                  |          |             | in order to get a          |
   |                  |          |             | successful package build.  |
   |------------------+----------+-------------+----------------------------|
   |                  |          |             | Kris Kennaway reports that |
   |                  |          |             | there is a gcc bug on      |
   |                  |          |             | sparc64 that prevents the  |
   | gcc sparc64      | --       | --          | build of                   |
   | problems         |          |             | XFree86-4-libraries.       |
   |                  |          |             | Alexander Kabaev is        |
   |                  |          |             | working on a gcc 3.3       |
   |                  |          |             | patchset for test.         |
   |------------------+----------+-------------+----------------------------|
   |                  |          |             | ia64 serial console        |
   |                  |          |             | support is not currently   |
   |                  | In       | Marcel      | functional, and requires a |
   | ia64 sio support | progress | Moolenaar,  | reworking of the sio       |
   |                  |          | Warner Losh | support to improve         |
   |                  |          |             | platform independence and  |
   |                  |          |             | bus handling.              |
   |------------------+----------+-------------+----------------------------|
   |                  |          |             | Brian Feldman has          |
   |                  |          |             | submitted patches to       |
   |                  |          |             | improve the consistency of |
   | MAC Framework    | In       | Robert      | the pathnames passed into  |
   | devfs path fixes | progress | Watson      | the MAC Framework devfs    |
   |                  |          |             | labeling entry points.     |
   |                  |          |             | These patches need to be   |
   |                  |          |             | thoroughly reviewed and    |
   |                  |          |             | tested, then merged.       |
   |------------------+----------+-------------+----------------------------|
   |                  |          |             | MAC Framework              |
   |                  |          |             | synchronization currently  |
   |                  |          |             | costs two mutex lock and   |
   |                  |          |             | unlock operations for each |
   | MAC Framework    |          |             | entry point, even if no    |
   | locking          | In       | Robert      | dynamically                |
   | performance      | progress | Watson      | loadable/unloadable        |
   | improvements     |          |             | policies are present.      |
   |                  |          |             | Patches are currently      |
   |                  |          |             | being tested that halve    |
   |                  |          |             | this locking cost when     |
   |                  |          |             | dynamic policies are not   |
   |                  |          |             | loaded.                    |
   |------------------+----------+-------------+----------------------------|
   | Panic on         |          |             | If a network device        |
   | load/unload a    |          |             | driver, possibly any       |
   | kernel module    |          |             | driver, is linked into the |
   | for a driver     | --       | --          | kernel and then loaded and |
   | already          |          |             | unloaded as a module, the  |
   | statically       |          |             | kernel will panic. This    |
   | linked into the  |          |             | has been observed with     |
   | kernel.          |          |             | both if_dc and if_fxp.     |
   +------------------------------------------------------------------------+

  Desired Features for 5.1-RELEASE

   +------------------------------------------------------------------------+
   |      Issue      |  Status   |   Responsible    |      Description      |
   |-----------------+-----------+------------------+-----------------------|
   |                 |           |                  | A.out support in the  |
   |                 |           |                  | base system was       |
   | a.out 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         |
   |                 |           |                  | debugged. A bug also  |
   | Race conditions | Errata    |                  | appears to exist      |
   | in truss        | candidate | Robert Drehmel   | 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.               |
   |-----------------+-----------+------------------+-----------------------|
   |                 |           |                  | Currently, the MD     |
   |                 |           |                  | elements of KSE are   |
   |                 |           |                  | present only for the  |
   |                 |           |                  | i386 platform,        |
   |                 |           |                  | limiting use of KSE   |
   |                 |           |                  | to the i386 platform. |
   |                 |           |                  | It is highly          |
   | KSE support for |           |                  | desirable to make KSE |
   | sparc64, alpha, | --        | Jake Burkholder, | available 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        | --        | --               | link editor (rtld)    |
   | thread-safety   |           |                  | thread-safe with      |
   |                 |           |                  | libpthread.           |
   |-----------------+-----------+------------------+-----------------------|
   |                 |           |                  | Kris Kennaway reports |
   |                 |           |                  | deadlocks involving   |
   |                 |           |                  | the use of nullfs in  |
   |                 |           |                  | the bento             |
   |                 |           |                  | environment:          |
   |                 |           |                  | buildworld -j4 with   |
   | nullfs          |           |                  | src and obj mounted   |
   | deadlocks       | --        | --               | 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.     |
   +------------------------------------------------------------------------+

  Documentation items that must be resolved for 5.1

   +------------------------------------------------------------------------+
   |      Issue      |   Status    | Responsible  |       Description       |
   |-----------------+-------------+--------------+-------------------------|
   |                 |             |              | We now use OPIE instead |
   | Documentation   |             | Christian    | of S/Key. The handbook  |
   | rottage: S/Key  | In progress | Brueffer     | doesn't cover OPIE as   |
   |                 |             |              | well as it covers       |
   |                 |             |              | S/Key.                  |
   |-----------------+-------------+--------------+-------------------------|
   |                 |             |              | The hardware notes for  |
   |                 |             |              | ia64 needs some large   |
   | ia64 Hardware   | --          | --           | infusions of text. They |
   | Notes           |             |              | probably haven't been   |
   |                 |             |              | synched with reality    |
   |                 |             |              | for awhile.             |
   |-----------------+-------------+--------------+-------------------------|
   |                 |             |              | 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.            |
   +------------------------------------------------------------------------+

  Areas requiring immediate testing

   +------------------------------------------------------------------------+
   |      Issue      |  Status   |   Responsible   |      Description       |
   |-----------------+-----------+-----------------+------------------------|
   |                 |           |                 | The 20030228 vendor    |
   | Fresh ACPI-CA   |           |                 | sources have been      |
   | import          | --        | --              | imported. Further      |
   |                 |           |                 | testing is             |
   |                 |           |                 | appreciated.           |
   |-----------------+-----------+-----------------+------------------------|
   |                 |           |                 | During the install,    |
   |                 |           |                 | the iir controller     |
   |                 |           |                 | appears to correctly   |
   |                 |           |                 | probe, but finds no    |
   |                 |           |                 | disk devices. The card |
   |                 |           |                 | in question is an      |
   |                 |           |                 | Intel srcu32 RAID      |
   | iir driver      |           |                 | controller with 32Mb   |
   | fails to probe  | --        | --              | RAM, Firmware revision |
   | disks           |           |                 | 2.33.01. Intel         |
   |                 |           |                 | developers have        |
   |                 |           |                 | released an update     |
   |                 |           |                 | driver, which has      |
   |                 |           |                 | recently been adapted  |
   |                 |           |                 | and imported into      |
   |                 |           |                 | 5-CURRENT, and must be |
   |                 |           |                 | tested.                |
   |-----------------+-----------+-----------------+------------------------|
   |                 |           |                 | PAE support allows the |
   |                 |           |                 | use of up to 64GB of   |
   | PAE support for |           |                 | RAM on Pentium Pro and |
   | i386            | --        | --              | above systems. Virtual |
   |                 |           |                 | addresses are still    |
   |                 |           |                 | constrained to         |
   |                 |           |                 | 32-bits.               |
   |-----------------+-----------+-----------------+------------------------|
   |                 |           |                 | The recently upgraded  |
   |                 |           |                 | if_wi driver is more   |
   |                 |           |                 | tuned to Prism         |
   |                 |           |                 | hardware than to       |
   | if_wi problems  |           |                 | Lucent hardware,       |
   | on Lucent       | --        | --              | resulting in system    |
   | hardware        |           |                 | lockups and poor       |
   |                 |           |                 | performance when using |
   |                 |           |                 | Lucent hardware. These |
   |                 |           |                 | problems are believed  |
   |                 |           |                 | to be fixed but more   |
   |                 |           |                 | testing is welcome.    |
   |-----------------+-----------+-----------------+------------------------|
   |                 |           |                 | There are reports that |
   |                 |           |                 | kernels build with     |
   | No console      |           |                 | smbus, viapm, and smb  |
   | (term) if smbus | --        | --              | devices may not        |
   | is enable in    |           |                 | properly probe and     |
   | the kernel      |           |                 | support the system     |
   |                 |           |                 | console following      |
   |                 |           |                 | boot.                  |
   |-----------------+-----------+-----------------+------------------------|
   |                 |           |                 | For 5.1-RELEASE, the   |
   |                 |           |                 | default file system    |
   |                 |           |                 | type for newly created |
   |                 |           |                 | file systems is UFS2   |
   |                 |           |                 | rather than UFS1.      |
   | UFS2 as         |           |                 | newfs(8) and           |
   | installation,   | --        | Robert Watson   | sysinstall(8) have     |
   | newfs default   |           |                 | been updated to use    |
   |                 |           |                 | this new default.      |
   |                 |           |                 | Testing to make sure   |
   |                 |           |                 | all goes well after    |
   |                 |           |                 | the change (committed  |
   |                 |           |                 | on April 20, 2003) is  |
   |                 |           |                 | vital.                 |
   |-----------------+-----------+-----------------+------------------------|
   |                 |           |                 | Kris Kennaway reports  |
   |                 |           |                 | mutex panics in wait4  |
   |                 |           |                 | in the bento           |
   |                 |           |                 | environment:           |
   | wait4           |           |                 | "Impossible" mutex     |
   | "impossible"    | --        | Tim J. Robbins  | panic in wait4()       |
   | mutex panic     |           |                 | (reported to -current  |
   |                 |           |                 | a while ago). Believed |
   |                 |           |                 | to be related to (and  |
   |                 |           |                 | fixed along with)      |
   |                 |           |                 | uidinfo "impossible"   |
   |                 |           |                 | panic below.           |
   |-----------------+-----------+-----------------+------------------------|
   |                 |           |                 | Kris Kennaway reports  |
   |                 |           |                 | that there appears to  |
   |                 |           |                 | be a resource leak of  |
   |                 |           |                 | uidinfo reference      |
   | uidinfo         |           |                 | counts that is causing |
   | "impossible"    | --        | Tim J. Robbins  | the gohan machines to  |
   | panic           |           |                 | panic after about 18   |
   |                 |           |                 | days of load.          |
   |                 |           |                 | Tim J. Robbins has     |
   |                 |           |                 | committed a fix that   |
   |                 |           |                 | is believed to solve   |
   |                 |           |                 | the problem.           |
   |-----------------+-----------+-----------------+------------------------|
   |                 |           |                 | Support for pluggable  |
   |                 |           |                 | directory services     |
   |                 |           |                 | using NSS, including   |
   |                 |           |                 | adaptations of current |
   |                 |           |                 | directory services     |
   | NSSwitch        |           |                 | (local databases,      |
   | support         | --        | Jacques Vidrine | NIS), and support for  |
   |                 |           |                 | new services (LDAP,    |
   |                 |           |                 | Active Directory,      |
   |                 |           |                 | etc). This change has  |
   |                 |           |                 | been committed, and    |
   |                 |           |                 | requires broader       |
   |                 |           |                 | testing.               |
   |-----------------+-----------+-----------------+------------------------|
   |                 |           |                 | Starting in late       |
   |                 |           |                 | April, reports of a    |
   |                 |           |                 | new UFS panic, "panic: |
   |                 |           |                 | ffs_blkfree: freeing   |
   |                 |           |                 | free frag" began to    |
   |                 |           |                 | pop up with a high     |
   |                 |           |                 | frequency in some      |
   |                 |           |                 | environments. This     |
   |                 |           |                 | problem appears to     |
   |                 |           |                 | have been associated   |
   |                 |           |                 | with a bug introduced  |
   |                 |           |                 | in the VM system that  |
   |                 |           |                 | has now been resolved. |
   | panic:          | Patch     | Alan L. Cox     | Users who updated to a |
   | ffs_blkfree     | committed |                 | kernel between         |
   |                 |           |                 | approximately May 1    |
   |                 |           |                 | and May 4 will want to |
   |                 |           |                 | run a full foreground  |
   |                 |           |                 | fsck on all file       |
   |                 |           |                 | systems to make sure   |
   |                 |           |                 | that no remaining free |
   |                 |           |                 | space accounting       |
   |                 |           |                 | errors exist. However, |
   |                 |           |                 | we should be on the    |
   |                 |           |                 | lookout for any        |
   |                 |           |                 | recurrence of this     |
   |                 |           |                 | problem due to its     |
   |                 |           |                 | serious nature.        |
   |-----------------+-----------+-----------------+------------------------|
   |                 |           |                 | Due to TCP state       |
   |                 |           |                 | efficiency             |
   |                 |           |                 | improvements in the    |
   |                 |           |                 | TIMEWAIT state, it is  |
   |                 |           |                 | now possible for the   |
   |                 |           |                 | PCB socket pointer to  |
   |                 |           |                 | be NULL in situations  |
   | TIMEWAIT panic  |           |                 | it previously wasn't.  |
   | for network     | Patch     |                 | As a result, TCP       |
   | labeled MAC     | committed | Robert Watson   | responses generated in |
   | policy modules  |           |                 | the TIMEWAIT state     |
   |                 |           |                 | lacked properly        |
   |                 |           |                 | initialized MAC        |
   |                 |           |                 | labels, resulting in   |
   |                 |           |                 | panics for network     |
   |                 |           |                 | labeled MAC policies.  |
   |                 |           |                 | A fix has been         |
   |                 |           |                 | committed, and needs   |
   |                 |           |                 | more broad testing.    |
   +------------------------------------------------------------------------+

     ----------------------------------------------------------------------

    freebsd-qa_at_FreeBSD.ORG
    Copyright (c) 1995-2003 The FreeBSD Project. All rights reserved.
    Last modified: 2003/05/07 05:38:29
Received on Wed May 07 2003 - 04:00:34 UTC

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