diff --git a/en/releases/6.1R/todo.sgml b/en/releases/6.1R/todo.sgml index 033d6f5ca7..8aec544d16 100644 --- a/en/releases/6.1R/todo.sgml +++ b/en/releases/6.1R/todo.sgml @@ -1,7 +1,7 @@ - + %navincludes; @@ -59,124 +59,6 @@ Description - - unreliable serial console - &status.unknown; - - At the manual 'root mount' prompt, the serial console is very - unreliable and drops most characters. - - - - unmount pending error - &status.wip; - &a.ssouhlal; - When unmounting filesystems &a.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; - &a.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. - - - - /dev/mem instability - &status.unknown; - &a.marius; - Instability when accessing /dev/mem. Contact - &a.marius; or &a.kris; for debugging information. - - - - sparc64 frequent hangs - &status.unknown; - - no DDB break possible, so impossible to diagnose - - - - serious sparc64 IPv6 panic - &status.wip; - &a.gnn; - Triggered by just ping6'ing the box. It may even be a MI - issue, the reporter of this bug only uses IPv6 with - sparc64. This problem seems to be triggered even when debug.mpsafenet=0. - - - - sort(1) does not work with some locales - &status.new; -   - sort(1) can cause a coredump with some locales. - See also gnu/93629. - - - - exec_map depletion - &status.wip; - &a.ups; - The exec_map is regularly running out of space - on machines running 7.0. &a.ups; has a proposed - patch and it seems to fix this problem. - - - - NFS data corruption between two 7.0 machines - &status.wip; - &a.mohans; - Running fsx between a 7.0 NFS client and server - detects data corruption. This problem can also be reproduced - by using 6.1 NFS server. - - - - deadlock in vn_start_write() consumers - &status.wip; - &a.tegge; - - - - - devfs locking problem - &status.wip; - &a.jeff; - It is trivial to deadlock it on an SMP system, and - there are other panics with device removal. - - - - pty leak - &status.wip; - &a.cognet; - Since 6.x has a hard-coded limit, once all ptys are - leaked things like ssh and login no longer work. - This seems devfs-related. - - - - rpc.lockd interoperability problems - &status.unknown; - &a.kuriyama; - After this commit - rpc.lockd seems to have interoperability problems. - This may be the cause of the many "rpc.lockd no longer interoperates" - bug reports seen on -stable. - - - - "calcru: runtime went backwards" problem for threaded program - &status.unknown; -   - stress2 thr1 test can trigger "calcru: runtime went backwards" problem - and there are also many similar reports on -stable and -current. - &a.phk; committed a possible fix (src/sys/kern/kern_tc.c rev.1.169) to - update the calibration code to be more precise on 2 March. -

Required features for &local.rel;-RELEASE

@@ -203,6 +85,111 @@ on a filesystem is negative; fsck -f is needed to correct this. Description + + devfs locking problem + &status.wip; + &a.jeff; + It is trivial to deadlock it on an SMP system, and + there are other panics with device removal. + + + + pty leak + &status.wip; + &a.cognet; + Since 6.x has a hard-coded limit, once all ptys are + leaked things like ssh and login no longer work. + This seems devfs-related. + + + + swap_pager warnings + &status.unknown; + &a.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. + + + + unmount pending error + &status.wip; + &a.ssouhlal; + When unmounting filesystems &a.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. + + + + "calcru: runtime went backwards" problem for threaded program + &status.unknown; +   + stress2 thr1 test can trigger "calcru: runtime went backwards" problem + and there are also many similar reports on -stable and -current. + &a.phk; committed a possible fix (src/sys/kern/kern_tc.c rev.1.169) to + update the calibration code to be more precise on 2 March. + + + + rpc.lockd interoperability problems + &status.unknown; + &a.kuriyama; + After this commit + rpc.lockd seems to have interoperability problems. + This may be the cause of the many "rpc.lockd no longer interoperates" + bug reports seen on -stable. Unfortunately, rpc.lockd contains a + number of severe architectural issues that make it unsuitable for a + production environment. Fixing these is beyond the scope of the + 6.1 release. + + + + NFS data corruption between two 7.0 machines + &status.wip; + &a.mohans; + Running fsx between a 7.0 NFS client and server + detects data corruption. This problem can also be reproduced + by using 6.1 NFS server. The problem seems to be avoidable by + turning off the attribute cache on the NFS client. + + + + sort(1) does not work with some locales + &status.new; +   + sort(1) can cause a coredump with some locales. + See also gnu/93629. + + + + sparc64 frequent hangs + &status.wip; + &a.marius; + Some of the more serious hangs on sparc64 have been fixed, but more + remain. + + + + serious sparc64 IPv6 panic + &status.wip; + &a.gnn; + Triggered by just ping6'ing the box. It may even be a MI + issue, the reporter of this bug only uses IPv6 with + sparc64. This problem seems to be triggered even when debug.mpsafenet=0. + + + + unreliable serial console + &status.unknown; + + At the manual 'root mount' prompt, the serial console is very + unreliable and drops most characters. This appears to be caused + by cngetc() polling the sio driver for input, and the sio driver + resetting the chip on every poll iteration. That results in a very + small window for it to accept input. Fixing this requires a + large review of the operation of the sio driver. The uart driver + looks to handle this better and might be a suitable replacement. + + swap panic on sparc64 &status.unknown; @@ -477,6 +464,32 @@ on a filesystem is negative; fsck -f is needed to correct this. &a.andre; See http://people.freebsd.org/~pho/stress/log/cons186.html. + + + exec_map depletion + &status.untested; + &a.ups; + The exec_map is regularly running out of space + on machines running 7.0. &a.ups; has a committed a + patch that seems to fix this problem. + + + + /dev/mem instability + &status.untested; + &a.marius;, &a.ups; + Instability when accessing /dev/mem. A fix was committed + for i386. amd64 does not seem to have the problem. A sarc64 + fix is still in progress. + + + + deadlock in vn_start_write() consumers + &status.untested; + &a.tegge; + Many potential deadlocks have been fixed. + +

Stress Test Panics