diff --git a/en/releases/6.1R/todo.sgml b/en/releases/6.1R/todo.sgml
index 1d60ad713e..75e26e02a7 100644
--- a/en/releases/6.1R/todo.sgml
+++ b/en/releases/6.1R/todo.sgml
@@ -1,7 +1,7 @@
-
+
%navincludes;
@@ -69,12 +69,13 @@
| i386 deadlocks with >16GB swap |
- &status.wip; |
+ &status.deferred; |
&a.alc; |
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. |
+ 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.
@@ -98,14 +99,16 @@ on a filesystem is negative; fsck -f is needed to correct this.
| umount -f panics |
&status.wip; |
&a.jeff;, &a.ssouhlal; |
- panics from race conditions. |
+ panics from race conditions.
+ A patch from &a.jeff; seems to fix some of them. |
| quota deadlocks |
&status.wip; |
&a.jeff; |
- Quota support is not locked properly and causes deadlocks. |
+ Quota support is not locked properly and causes deadlocks.
+ A patch from &a.jeff; seems to fix some of them. |
@@ -122,14 +125,6 @@ on a filesystem is negative; fsck -f is needed to correct this.
| Seen by Peter Jeremy. |
-
- | amd64 panics in ipv6 with date(1) |
- &status.untested; |
- &a.ume; and &a.dwmalone; |
- amd64 panics in ipv6 when the date is changed using date(1) or
- ntpdate(1). This may be a MI issue. |
-
-
| sparc64 instability. |
&status.unknown; |
@@ -138,13 +133,6 @@ on a filesystem is negative; fsck -f is needed to correct this.
&a.marius; or &a.kris; for debugging information.
-
- | dhclient causes ipv6 panics. |
- &status.unknown; |
- |
- &a.dougb; has more details about this. |
-
-
| sparc64 frequent hangs |
&status.unknown; |
@@ -161,6 +149,13 @@ on a filesystem is negative; fsck -f is needed to correct this.
sparc64.
+
+ | sort(1) does not work with some locales |
+ &status.new; |
+ |
+ sort(1) can cause a coredump with some locales.
+ See also gnu/93629. |
+
Required features for &local.rel;-RELEASE
@@ -257,12 +252,12 @@ on a filesystem is negative; fsck -f is needed to correct this.
| /dev/kmem panic |
- &status.new; |
- |
+ &status.wip; |
+ &a.ups; |
&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. |
+ accesses to /dev/kmem. &a.ups; committed a fix for i386.
@@ -317,7 +312,6 @@ on a filesystem is negative; fsck -f is needed to correct this.
this can make a system essentially unusable when moderate
paging activity is going on.
-
Documentation items that must be resolved for &local.rel;
@@ -352,6 +346,30 @@ on a filesystem is negative; fsck -f is needed to correct this.
&a.ssouhlal; has committed a patch for this.
+
+ | dhclient causes ipv6 panics. |
+ &status.untested; |
+ &a.dougb; |
+ &a.dougb; has more details about this. |
+
+
+
+ | amd64 panics in ipv6 with date(1) |
+ &status.untested; |
+ &a.ume; |
+ amd64 panics in ipv6 when the date is changed using date(1) or
+ ntpdate(1). This may be a MI issue. |
+
+
+
+ | grep(1) -w does not work with multibyte locales |
+ &status.untested; |
+ &a.tjr; |
+ grep(1) -w generates wrong results with non-UTF-8
+ multibyte locales. &a.tjr; has committed a patch
+ to -HEAD. See also gnu/91909. |
+
+
Stress Test Panics