diff --git a/en/releases/6.1R/todo.sgml b/en/releases/6.1R/todo.sgml index 0c0b9eff81..d1823c8850 100644 --- a/en/releases/6.1R/todo.sgml +++ b/en/releases/6.1R/todo.sgml @@ -1,7 +1,7 @@ - + %navincludes; @@ -46,6 +46,7 @@
  • Documentation Items
  • Testing foci
  • Problems Discovered by Kernel Stress Test Suite
    • +
  • Problems specific to the sparc64 architecture

    • Show stopper defects for &local.rel;-RELEASE

    @@ -162,23 +163,6 @@ on a filesystem is negative; fsck -f is needed to correct this. 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; @@ -192,16 +176,6 @@ on a filesystem is negative; fsck -f is needed to correct this. looks to handle this better and might be a suitable replacement. - - swap panic on sparc64 - &status.unknown; - &a.kris; has panic info - - &a.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.done; @@ -235,22 +209,6 @@ on a filesystem is negative; fsck -f is needed to correct this. accesses to /dev/kmem. &a.ups; committed a fix for i386. - - KLDs on sparc64 - &status.new; -   - On sparc64 machines with more than 4Gb memory KLDs are not usable - and will panic the system. The problem is reportedly with how the - KLDs are compiled, it only works if the code ends up below 4G. - - - - Max RAM on sparc64 - &status.new; -   - Maximum RAM on sparc64 appears to be limited to 16Gb. - - make -jN &status.new; @@ -505,6 +463,64 @@ on a filesystem is negative; fsck -f is needed to correct this. &stresstest; +

    sparc64 problems

    + +

    These are problems that range in severity for FreeBSD/sparc64. They +will not hold up the release, but they will still be tracked for future +releases.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    IssueStatusResponsibleDescription
    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.
    swap panic on sparc64&status.unknown;&a.kris; has panic info&a.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).
    KLDs on sparc64&status.new; On sparc64 machines with more than 4Gb memory KLDs are not usable + and will panic the system. The problem is reportedly with how the + KLDs are compiled, it only works if the code ends up below 4G.
    Max RAM on sparc64&status.new; Maximum RAM on sparc64 appears to be limited to 16Gb.
    + &footer;