Date: Sat, 31 May 2003 14:24:59 -0700 From: Luigi Rizzo <rizzo@icir.org> To: re@FreeBSD.org Cc: current@FreeBSD.org Subject: Re: 5.1-RELEASE TODO Message-ID: <20030531142459.A90361@xorpc.icir.org> In-Reply-To: <200305311300.h4VD0GUE084477@fledge.watson.org>; from rwatson@FreeBSD.org on Sat, May 31, 2003 at 09:00:16AM -0400 References: <200305311300.h4VD0GUE084477@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 31, 2003 at 09:00:16AM -0400, Robert Watson wrote: > 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 | > | ipfw/ipfw2 | | | alignment problems with | > | alignment issues | In progress | Luigi Rizzo | ipfw and/or ipfw2 on | > | on alpha/sparc64 | | | 64-bit platforms | > | | | | (specifically alpha and | > | | | | sparc64). | > +------------------------------------------------------------------------+ i posted patches and a detailed description for this item 3 weeks ago to re@ and then the same was forwarded a couple of weeks ago to the relevant lists (ipfw, sparc64, alpha) and got no useful feedback (in detail, two message: one 'cannot apply the patch', the other one 'it dumps core' without further details). As i do not have access to these platforms, all i can do is provide code and make sure that it compiles (which i did, using a cross-build), but for running it (part of the problem involves the kernel) i need someone with root&console access to test them. I would interpret the absence of feedback as a "nobody cares enough" (which is perfectly fine given that these platforms are a negligible fraction of the installed base, there are more important issues to address and these particular ones should have a relatively trivial fix). cheers luigi > Desired Features for 5.1-RELEASE > > +------------------------------------------------------------------------+ > | Issue | Status | Responsible | Description | > +------------------------------------------------------------------------+ > > Documentation items that must be resolved for 5.1 > > +------------------------------------------------------------------------+ > | Issue | Status | Responsible | Description | > +------------------------------------------------------------------------+ > > 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/31 07:19:32
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030531142459.A90361>