os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Move the truss race condition issue into the Desired section from the

Browse source 
Must section.

Update the ii3 driver item: Intel is apparently working the issue and
has a driver update, which we need to review, adapt, and import.
Assign to scottl.

Change responsible part from &a.chris; to no-one for the gbde(8)
documentation issue.
This commit is contained in:
Robert Watson 2003-04-18 22:23:12 +00:00
parent b866db4e92
commit 9dc2e7c805
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=16597
1 changed files with 21 additions and 21 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

42
en/releases/5.1R/todo.sgml
View file

@ -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/5.1R/todo.sgml,v 1.3 2003/04/18 22:06:29 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.1R/todo.sgml,v 1.4 2003/04/18 22:09:31 rwatson Exp $">
<!ENTITY title "FreeBSD 5.1 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -22,30 +22,15 @@
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
<tr>
<td>Race conditions in truss</td>
<td>Errata candidate</td>
<td>&a.robert;</td>
<td>Truss appears to contain a race condition during the start-up of
debugging, which can result in truss failing to attach to the process
before it exits. The symptom is that truss reports that it cannot
open the procfs node supporting the process being debugged. A bug
also appears to exist where in truss will hang if execve() returns
ENOENT. A further race appears to exist in which truss will return
"PIOCWAIT: Input/output error" occasionally on startup. The fix
for this sufficiently changes process execution handling that we
will defer the fix to post-5.0 and consider this errata.</td>
</tr>
<tr>
<td>iir driver fails to probe disks</td>
<td>--</td>
<td>--</td>
<td>In progress</td>
<td>&a.scottl;</td>
<td>During the install, the iir controller appears to correctly
probe, but finds no disk devices. The card in question is an
Intel srcu32 RAID controller with 32Mb RAM, Firmware revision
2.33.01. Direct access to real iir hardware for SCSI
developers would be very helpful in resolving this problem.</td>
2.33.01. Intel developers have released an update driver, which
must be adapted and imported prior to 5.1-RELEASE.</td>
</tr>
<tr>
@ -120,6 +105,21 @@
continue to support UFS1.</td>
</tr>
<tr>
<td>Race conditions in truss</td>
<td>Errata candidate</td>
<td>&a.robert;</td>
<td>Truss appears to contain a race condition during the start-up of
debugging, which can result in truss failing to attach to the process
before it exits. The symptom is that truss reports that it cannot
open the procfs node supporting the process being debugged. A bug
also appears to exist where in truss will hang if execve() returns
ENOENT. A further race appears to exist in which truss will return
"PIOCWAIT: Input/output error" occasionally on startup. The fix
for this sufficiently changes process execution handling that we
will defer the fix to post-5.0 and consider this errata.</td>
</tr>
</table>
<h3>Documentation items that must be resolved for 5.1</h3>
@ -148,7 +148,7 @@
<tr>
<td>Documentation wanted: gdbe</td>
<td>--</td>
<td>&a.chris;</td>
<td>--</td>
<td>5.0 includes GDBE, supporting encryption of swap and storage.
It would be nice if that was documented in the handbook.</td>
</tr>