Update 6.1R TODO list:
- i386 deadlocks with >16GB swap: deferred to the future releases. - umount -f panics: mention jeff's patch. - quota deadlocks: mention jeff's patch. - sort(1) does not work with some locales: new. - /dev/kmem panic: ups committed a fix for i386. - dhclient causes ipv6 panics: moved to testing foci. - amd64 panics in ipv6 with date(1): moved to testing foci (www/93611). - grep(1) -w does not work with multibyte locales: new, fixed on -HEAD.
This commit is contained in:
parent
cfde8d98ba
commit
b003798dc3
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=27209
1 changed files with 43 additions and 25 deletions
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY email 'freebsd-qa'>
|
||||
<!ENTITY date "$FreeBSD: www/en/releases/6.1R/todo.sgml,v 1.11 2006/02/14 01:40:16 hrs Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/releases/6.1R/todo.sgml,v 1.12 2006/02/15 03:02:29 hrs Exp $">
|
||||
<!ENTITY local.rel "6.1">
|
||||
<!ENTITY title "FreeBSD 6.1 Open Issues">
|
||||
<!ENTITY % navincludes SYSTEM "../../includes.navdownload.sgml"> %navincludes;
|
||||
|
@ -69,12 +69,13 @@
|
|||
|
||||
<tr>
|
||||
<td>i386 deadlocks with >16GB swap</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&status.deferred;</td>
|
||||
<td>&a.alc;</td>
|
||||
<td>i386 deadlocks if more than 16GB of swap is in use.
|
||||
Increasing the kern.maxswzone tunable would be a workaround
|
||||
this, but a patch from &a.alc; is needed to allow this variable to
|
||||
be increased.</td>
|
||||
this. Although a patch from &a.alc; is needed to allow this variable to
|
||||
be increased, this is not suitable for 6.1R. This limitation should
|
||||
be documented in the Release Notes.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
|
@ -98,14 +99,16 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
|
|||
<td>umount -f panics</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.jeff;, &a.ssouhlal;</td>
|
||||
<td>panics from race conditions.</td>
|
||||
<td>panics from race conditions.
|
||||
A patch from &a.jeff; seems to fix some of them.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>quota deadlocks</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.jeff;</td>
|
||||
<td>Quota support is not locked properly and causes deadlocks.</td>
|
||||
<td>Quota support is not locked properly and causes deadlocks.
|
||||
A patch from &a.jeff; seems to fix some of them.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
|
@ -122,14 +125,6 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
|
|||
<td>Seen by Peter Jeremy.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>amd64 panics in ipv6 with date(1)</td>
|
||||
<td>&status.untested;</td>
|
||||
<td>&a.ume; and &a.dwmalone;</td>
|
||||
<td>amd64 panics in ipv6 when the date is changed using date(1) or
|
||||
ntpdate(1). This may be a MI issue.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>sparc64 instability.</td>
|
||||
<td>&status.unknown;</td>
|
||||
|
@ -138,13 +133,6 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
|
|||
&a.marius; or &a.kris; for debugging information.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>dhclient causes ipv6 panics.</td>
|
||||
<td>&status.unknown;</td>
|
||||
<td></td>
|
||||
<td>&a.dougb; has more details about this.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>sparc64 frequent hangs</td>
|
||||
<td>&status.unknown;</td>
|
||||
|
@ -161,6 +149,13 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
|
|||
sparc64.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>sort(1) does not work with some locales</td>
|
||||
<td>&status.new;</td>
|
||||
<td> </td>
|
||||
<td>sort(1) can cause a coredump with some locales.
|
||||
See also gnu/93629.</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<h3>Required features for &local.rel;-RELEASE</h3>
|
||||
|
@ -257,12 +252,12 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
|
|||
|
||||
<tr>
|
||||
<td>/dev/kmem panic</td>
|
||||
<td>&status.new;</td>
|
||||
<td> </td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.ups;</td>
|
||||
<td>&a.kris; has noticed panics on SMP machines when there was ABI
|
||||
breakage of libkvm and world was not rebuilt and utilities like
|
||||
fstat were used. This suggests panics can be caused by incorrect
|
||||
accesses to /dev/kmem.</td>
|
||||
accesses to /dev/kmem. &a.ups; committed a fix for i386.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
|
@ -317,7 +312,6 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
|
|||
this can make a system essentially unusable when moderate
|
||||
paging activity is going on.</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
<h3>Documentation items that must be resolved for &local.rel;</h3>
|
||||
|
@ -352,6 +346,30 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
|
|||
&a.ssouhlal; has committed a patch for this.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>dhclient causes ipv6 panics.</td>
|
||||
<td>&status.untested;</td>
|
||||
<td>&a.dougb;</td>
|
||||
<td>&a.dougb; has more details about this.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>amd64 panics in ipv6 with date(1)</td>
|
||||
<td>&status.untested;</td>
|
||||
<td>&a.ume;</td>
|
||||
<td>amd64 panics in ipv6 when the date is changed using date(1) or
|
||||
ntpdate(1). This may be a MI issue.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>grep(1) -w does not work with multibyte locales</td>
|
||||
<td>&status.untested;</td>
|
||||
<td>&a.tjr;</td>
|
||||
<td>grep(1) -w generates wrong results with non-UTF-8
|
||||
multibyte locales. &a.tjr; has committed a patch
|
||||
to -HEAD. See also gnu/91909.</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
<h3>Stress Test Panics</h3>
|
||||
|
|
Loading…
Reference in a new issue