diff --git a/en/releases/6.1R/todo.sgml b/en/releases/6.1R/todo.sgml
index ce7e73950c..2513bb554a 100644
--- a/en/releases/6.1R/todo.sgml
+++ b/en/releases/6.1R/todo.sgml
@@ -1,7 +1,7 @@
-
+
%navincludes;
@@ -59,6 +59,49 @@
| Description |
+
+ | unreliable serial console |
+ &status.unknown; |
+ |
+ At the manual 'root mount' prompt, the serial console is very
+ unreliable and drops most characters. |
+
+
+
+ | manual root mount lockmgr panics |
+ &status.wip; |
+ ssouhlal |
+ Specifying a manual root mount location causes lockmgr panics.
+ ssouhlal has a patch for this. |
+
+
+
+ | i386 deadlocks with >16GB swap |
+ &status.wip; |
+ 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 alc@ is needed to allow this variable to
+ be increased. |
+
+
+
+ | unmount pending error |
+ &status.unknown; |
+ |
+ When unmounting filesystems Kris reports seeing this warning: /c: unmount pending error: blocks -68512 files 0. This dates back at least to 5.3. It might be associated with
+filesystem corruption reported by many users in which the 'used' space
+on a filesystem is negative; fsck -f is needed to correct this. |
+
+
+
+ | swap_pager warnings |
+ &status.unknown; |
+ truckman? |
+ When swapfiles are in use, there are often warnings printed:
+swap_pager: indefinite wait buffer: bufobj: 0, blkno: 889347, size: 8192. There is also the possibility of deadlock. |
+
+
| umount -f panics |
&status.wip; |
@@ -187,6 +230,16 @@
all attached keyboards Just Work.
+
+ | swap panic on sparc64 |
+ &status.unknown; |
+ kris has panic info |
+
+ Kris reports configuring a 74GB swap-backed md on sparc64 that
+ caused a panic after a week or two of load (during which time
+ swap was slowly filling as more of the md was dirtied). |
+
+
| updated hal and ath drivers |
&status.new; |