The sparc64 problems are numerous, but do not affect the viability of the
release. Create a separate section for them so that they can be interpreted appropriately.
This commit is contained in:
Scott Long
parent
db96c0f4f0
commit
0acd9d1959
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=27675
1 changed files with 60 additions and 44 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.26 2006/04/13 08:18:44 scottl Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/releases/6.1R/todo.sgml,v 1.27 2006/04/25 11:43:09 hrs Exp $">
|
||||
<!ENTITY local.rel "6.1">
|
||||
<!ENTITY title "FreeBSD 6.1 Open Issues">
|
||||
<!ENTITY % navincludes SYSTEM "../../includes.navdownload.sgml"> %navincludes;
|
||||
|
|
@ -46,6 +46,7 @@
|
|||
<li><a href="#docs">Documentation Items</a></li>
|
||||
<li><a href="#testing">Testing foci</a></li>
|
||||
<li><a href="#stresstest">Problems Discovered by Kernel Stress Test Suite</a></li>
|
||||
<li><a href="#sparc64">Problems specific to the sparc64 architecture</a></li>
|
||||
</ul>
|
||||
|
||||
<h3>Show stopper defects for &local.rel;-RELEASE</h3>
|
||||
|
|
@ -162,23 +163,6 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
|
|||
See also gnu/93629.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>sparc64 frequent hangs</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.marius;</td>
|
||||
<td>Some of the more serious hangs on sparc64 have been fixed, but more
|
||||
remain.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>serious sparc64 IPv6 panic</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.gnn;</td>
|
||||
<td>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.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>unreliable serial console</td>
|
||||
<td>&status.unknown;</td>
|
||||
|
|
@ -192,16 +176,6 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
|
|||
looks to handle this better and might be a suitable replacement.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>swap panic on sparc64</td>
|
||||
<td>&status.unknown;</td>
|
||||
<td>&a.kris; has panic info</td>
|
||||
|
||||
<td>&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).</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>updated hal and ath drivers</td>
|
||||
<td>&status.done;</td>
|
||||
|
|
@ -235,22 +209,6 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
|
|||
accesses to /dev/kmem. &a.ups; committed a fix for i386.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>KLDs on sparc64</td>
|
||||
<td>&status.new;</td>
|
||||
<td> </td>
|
||||
<td>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.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Max RAM on sparc64</td>
|
||||
<td>&status.new;</td>
|
||||
<td> </td>
|
||||
<td>Maximum RAM on sparc64 appears to be limited to 16Gb.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>make -jN</td>
|
||||
<td>&status.new;</td>
|
||||
|
|
@ -505,6 +463,64 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
|
|||
|
||||
&stresstest;
|
||||
|
||||
<h3>sparc64 problems</h3>
|
||||
<a name="sparc64"></a>
|
||||
<p>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.</p>
|
||||
|
||||
<table class="tblbasic">
|
||||
<tr class="heading">
|
||||
<th>Issue</th>
|
||||
<th>Status</th>
|
||||
<th>Responsible</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>sparc64 frequent hangs</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.marius;</td>
|
||||
<td>Some of the more serious hangs on sparc64 have been fixed, but more
|
||||
remain.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>serious sparc64 IPv6 panic</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.gnn;</td>
|
||||
<td>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.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>swap panic on sparc64</td>
|
||||
<td>&status.unknown;</td>
|
||||
<td>&a.kris; has panic info</td>
|
||||
|
||||
<td>&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).</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>KLDs on sparc64</td>
|
||||
<td>&status.new;</td>
|
||||
<td> </td>
|
||||
<td>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.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Max RAM on sparc64</td>
|
||||
<td>&status.new;</td>
|
||||
<td> </td>
|
||||
<td>Maximum RAM on sparc64 appears to be limited to 16Gb.</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
&footer;
|
||||
|
||||
</body>
|
||||
|
|
|
|||
Loading…
Reference in a new issue