From owner-freebsd-current@FreeBSD.ORG Thu May 15 06:00:29 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BA0637B401; Thu, 15 May 2003 06:00:29 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EF6043F93; Thu, 15 May 2003 06:00:28 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h4FD0FOn020008; Thu, 15 May 2003 09:00:15 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: (from robert@localhost) by fledge.watson.org (8.12.9/8.12.9/Submit) id h4FD0EbK020007; Thu, 15 May 2003 09:00:14 -0400 (EDT) (envelope-from robert) Date: Thu, 15 May 2003 09:00:14 -0400 (EDT) Message-Id: <200305151300.h4FD0EbK020007@fledge.watson.org> From: Robert Watson To: current@FreeBSD.org Subject: 5.1-RELEASE TODO X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: re@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2003 13:00:29 -0000 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 | |-------------------+-------------+---------------+----------------------| | | | | Kris Kennaway | | | | | reports that he has | | | | | seen several unique | | | | | panics on the alpha | | | | | machines, but since | | Spurious alpha | -- | -- | gdb -k doesn't work | | panics | | | 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 | | work on alpha | | | on alpha | |-------------------+-------------+---------------+----------------------| | | | | 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. | |-------------------+-------------+---------------+----------------------| | | | | ia64 serial console | | | | | support is not | | | | | currently | | | | Marcel | functional, and | | ia64 sio support | In progress | Moolenaar, | requires a reworking | | | | Warner Losh | of the sio support | | | | | to improve platform | | | | | independence and bus | | | | | handling. | |-------------------+-------------+---------------+----------------------| | | | | 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. | +------------------------------------------------------------------------+ Desired Features for 5.1-RELEASE +------------------------------------------------------------------------+ | Issue | Status | Responsible | Description | |----------------+-----------+----------------+--------------------------| | | | | A.out support in the | | a.out | | | base system was reduced; | | toolchain port | -- | -- | the removed 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 | | Race | Errata | | also appears to exist | | conditions in | candidate | Robert Drehmel | where in truss will hang | | truss | | | 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. | +------------------------------------------------------------------------+ 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. | |-----------------+-----------+-----------------+------------------------| | | | | 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@FreeBSD.ORG Copyright (c) 1995-2003 The FreeBSD Project. All rights reserved. Last modified: 2003/05/14 14:21:54