|
Lines 99-133
Link Here
|
| 99 |
<sect1 id="open-issues"> |
99 |
<sect1 id="open-issues"> |
| 100 |
<title>Open Issues</title> |
100 |
<title>Open Issues</title> |
| 101 |
|
101 |
|
| 102 |
<para>(31 Oct 2004) Sometimes the performance of the &man.re.4; and &man.em.4; |
102 |
<para>(31 Oct 2004) The &man.re.4; and &man.em.4; |
| 103 |
drivers can become poor under heavy load. Especially, there are |
103 |
drivers may behave poorly under heavy load. In particular, there are |
| 104 |
reports of &man.em.4; on the IBM ThinkPad T40 locking up |
104 |
reports of &man.em.4; on the IBM ThinkPad T40 locking up |
| 105 |
under such conditions.</para> |
105 |
under such conditions.</para> |
| 106 |
|
106 |
|
| 107 |
<para>(31 Oct 2004) There are reports of the &man.sk.4; driver |
107 |
<para>(31 Oct 2004) There are reports of the &man.sk.4; driver |
| 108 |
locking up under heavy load, especially when on-board NICs |
108 |
locking up under heavy load, especially when ASUStek on-board NICs |
| 109 |
of ASUStek motherboards are used. To clear the condition, |
109 |
are used. To clear the condition, |
| 110 |
bringing the interface down then back up and/or rebooting |
110 |
bringing the interface down then back up and/or rebooting |
| 111 |
the system are needed.</para> |
111 |
the system may be needed.</para> |
| 112 |
|
112 |
|
| 113 |
<para>(31 Oct 2004) The &man.burncd.8; utility is functional but may behave erratically |
113 |
<para>(31 Oct 2004) The &man.burncd.8; utility is functional but may behave erratically |
| 114 |
on some systems. Reported symptoms include that &man.burncd.8; |
114 |
on some systems. Reported symptoms include that &man.burncd.8; |
| 115 |
can appear to hang up and never complete while the operation actually |
115 |
can appear to hang and never complete while the operation actually |
| 116 |
does complete, and the progress indicator does not show the correct value. |
116 |
does complete, and the progress indicator does not show the correct value. |
| 117 |
Workarounds include:</para> |
117 |
Workarounds include:</para> |
| 118 |
|
118 |
|
| 119 |
<itemizedlist> |
119 |
<itemizedlist> |
| 120 |
<listitem> |
120 |
<listitem> |
| 121 |
<para>Eject and re-insert a media after burning a CD.</para> |
121 |
<para>Eject and re-insert the media after burning a CD.</para> |
| 122 |
</listitem> |
122 |
</listitem> |
| 123 |
|
123 |
|
| 124 |
<listitem> |
124 |
<listitem> |
| 125 |
<para>Press Ctrl-C when &man.burncd.8; appears to hang up |
125 |
<para>Press Ctrl-C when &man.burncd.8; appears to hang up |
| 126 |
in spite the access LED goes inactive.</para> |
126 |
while the access LED goes inactive.</para> |
| 127 |
</listitem> |
127 |
</listitem> |
| 128 |
</itemizedlist> |
128 |
</itemizedlist> |
| 129 |
|
129 |
|
| 130 |
<para>(31 Oct 2004) When the user/group rule modificators in &man.pf.4; and &man.ipfw.4; |
130 |
<para>(31 Oct 2004) When the user/group rule clauses in &man.pf.4; and &man.ipfw.4; |
| 131 |
are used, the loader tunable <varname>debug.mpsafenet</varname> |
131 |
are used, the loader tunable <varname>debug.mpsafenet</varname> |
| 132 |
must be set to <literal>0</literal> (this is <literal>1</literal> by |
132 |
must be set to <literal>0</literal> (this is <literal>1</literal> by |
| 133 |
default). For example, the following rules are affected:</para> |
133 |
default). For example, the following rules are affected:</para> |
|
Lines 149-176
Link Here
|
| 149 |
<para>More specifically, the <literal>group</literal> and <literal>user</literal> |
149 |
<para>More specifically, the <literal>group</literal> and <literal>user</literal> |
| 150 |
filter parameters in &man.pf.4;, and the <literal>gid</literal>, |
150 |
filter parameters in &man.pf.4;, and the <literal>gid</literal>, |
| 151 |
<literal>jail</literal>, and <literal>uid</literal> rule options |
151 |
<literal>jail</literal>, and <literal>uid</literal> rule options |
| 152 |
in &man.ipfw.4; are relevant. |
152 |
in &man.ipfw.4; are affected. |
| 153 |
If <varname>debug.mpsafenet</varname> is set to <literal>1</literal>, |
153 |
If <varname>debug.mpsafenet</varname> is set to <literal>1</literal>, |
| 154 |
the system can hang up when the rule is evaluated due to a lock order |
154 |
the system can hang when the rule is evaluated due to a lock order |
| 155 |
reversal with the socket layer. More details can be found in the |
155 |
reversal with the socket layer. More details can be found in the |
| 156 |
&man.ipfw.8; and &man.pf.conf.5; manual pages.</para> |
156 |
&man.ipfw.8; and &man.pf.conf.5; manual pages.</para> |
| 157 |
|
157 |
|
| 158 |
<para>(31 Oct 2004) The &man.vinum.4; subsystem |
158 |
<para>(31 Oct 2004) The &man.vinum.4; subsystem |
| 159 |
works fine on 5.3, but it can cause a system panic at boot time. |
159 |
works on 5.3, but it can cause a system panic at boot time. |
| 160 |
As a workaround you can add <literal>vinum_load="YES"</literal> |
160 |
As a workaround you can add <literal>vinum_load="YES"</literal> |
| 161 |
to <filename>/boot/loader.conf</filename>.</para> |
161 |
to <filename>/boot/loader.conf</filename>.</para> |
| 162 |
|
162 |
|
| 163 |
<para>As an alternative you can also use the new, &man.geom.4;-based |
163 |
<para>As an alternative you can also use the new &man.geom.4;-based |
| 164 |
&man.vinum.4; subsystem. To activate the &man.geom.4;-aware |
164 |
&man.vinum.4; subsystem. To activate the &man.geom.4;-aware |
| 165 |
vinum at boot time, add <literal>geom_vinum_load="YES"</literal> |
165 |
vinum at boot time, add <literal>geom_vinum_load="YES"</literal> |
| 166 |
to <filename>/boot/loader.conf</filename>.</para> |
166 |
to <filename>/boot/loader.conf</filename>.</para> |
| 167 |
|
167 |
|
| 168 |
<para>While some sort of uncommon configurations such as |
168 |
<para>While some uncommon configurations, such as |
| 169 |
multiple vinum drives in a disk are not supported, |
169 |
multiple vinum drives on a disk, are not supported, |
| 170 |
it is basically backward compatible. |
170 |
it is generally backward compatible. |
| 171 |
Note that for the &man.geom.4;-aware vinum the new userland |
171 |
Note that for the &man.geom.4;-aware vinum, its new userland |
| 172 |
control program, <command>gvinum</command> should be used, |
172 |
control program, <command>gvinum</command>, should be used, |
| 173 |
and it still lacks some functionality.</para> |
173 |
and it is not yet feature-complete.</para> |
| 174 |
|
174 |
|
| 175 |
<para>(31 Oct 2004) The results of <command>netstat -m</command> |
175 |
<para>(31 Oct 2004) The results of <command>netstat -m</command> |
| 176 |
can become incorrect on SMP systems when <varname>debug.mpsafenet</varname> |
176 |
can become incorrect on SMP systems when <varname>debug.mpsafenet</varname> |
|
Lines 182-188
Link Here
|
| 182 |
For &os;/i386 and &os;/amd64, when installing &os; 5.3 |
182 |
For &os;/i386 and &os;/amd64, when installing &os; 5.3 |
| 183 |
using an USB keyboard the keyboard will stop |
183 |
using an USB keyboard the keyboard will stop |
| 184 |
working once the kernel boots, because a PS/2 keyboard is |
184 |
working once the kernel boots, because a PS/2 keyboard is |
| 185 |
always attached. As a workaround, select |
185 |
always considered to be attached. As a workaround, select |
| 186 |
<quote>Escape to loader prompt</quote> in the boot loader menu |
186 |
<quote>Escape to loader prompt</quote> in the boot loader menu |
| 187 |
and enter the following lines at the prompt:</para> |
187 |
and enter the following lines at the prompt:</para> |
| 188 |
|
188 |
|
|
Lines 192-228
Link Here
|
| 192 |
<para>Note that if you use the boot floppies, this is set |
192 |
<para>Note that if you use the boot floppies, this is set |
| 193 |
by default.</para> |
193 |
by default.</para> |
| 194 |
|
194 |
|
| 195 |
<para>After the installation, add the following line into |
195 |
<para>After the installation, add the following line to |
| 196 |
<filename>/boot/loader.conf</filename>:</para> |
196 |
<filename>/boot/loader.conf</filename>:</para> |
| 197 |
|
197 |
|
| 198 |
<programlisting>hint.atkbd.0.flags="0x1"</programlisting> |
198 |
<programlisting>hint.atkbd.0.flags="0x1"</programlisting> |
| 199 |
|
199 |
|
| 200 |
<para>(1 Nov 2004) The ULE scheduler described in the release note |
200 |
<para>(1 Nov 2004) The ULE scheduler described in the release notes |
| 201 |
has been completely disabled to discourage its use because it has |
201 |
has been completely disabled to discourage its use because it has |
| 202 |
several stability problems.</para> |
202 |
stability problems.</para> |
| 203 |
|
203 |
|
| 204 |
<para>(1 Nov 2004) Programs linked with <application>libpthread</application> |
204 |
<para>(1 Nov 2004) Programs linked with <application>libpthread</application> |
| 205 |
may not report any CPU usage statistics according to &man.top.1;, |
205 |
may not report any CPU usage statistics according to &man.top.1;, |
| 206 |
while ones linked with <application>libthr</application> have |
206 |
while those linked with <application>libthr</application> show |
| 207 |
the correct statistics.</para> |
207 |
the correct statistics.</para> |
| 208 |
|
208 |
|
| 209 |
<para>(1 Nov 2004) When CMD649 or SiI0680 ATA controller is used, |
209 |
<para>(1 Nov 2004) ATA RAID support for the CMD649 and SiI0680 ATA |
| 210 |
the ATA RAID support of &man.ata.4; (ataraid) on 5.3 can corrupt |
210 |
controllers is non-functional in this release. When such a |
| 211 |
the existing RAID configuration which was created on 5.2 or prior. |
211 |
controller is brough up under &man.ata.4; (ataraid) on 5.3, the |
| 212 |
The ATA RAID support for these controllers is non-functional |
212 |
RAID configuration stored under 5.2 or prior may be corrupted.</para> |
| 213 |
for this release.</para> |
|
|
| 214 |
|
213 |
|
| 215 |
<para>(3 Nov 2004) For &os;/i386 and &os;/amd64, the SMP support |
214 |
<para>(3 Nov 2004) For &os;/i386 and &os;/amd64, SMP support |
| 216 |
in the <filename>GENERIC</filename> kernel has been disabled |
215 |
in the <filename>GENERIC</filename> kernel has been disabled |
| 217 |
by default because the SMP kernel can degrade the performance |
216 |
by default because the SMP kernel can degrade the performance |
| 218 |
on UP machines. A kernel configuration file <filename>SMP</filename> |
217 |
on UP machines. A kernel configuration file <filename>SMP</filename>, |
| 219 |
which can be used to enable the SMP support has been added. |
218 |
which can be used to enable SMP support, has been added. |
| 220 |
More details on building the custom kernel can be found in |
219 |
More details on building the custom kernel can be found at |
| 221 |
<ulink url="&url.books.handbook;/kernelconfig.html"></ulink>.</para> |
220 |
<ulink url="&url.books.handbook;/kernelconfig.html"></ulink>.</para> |
| 222 |
|
221 |
|
| 223 |
<para>(4 Nov 2004) The &man.tar.1; (also known as &man.bsdtar.1;) utility |
222 |
<para>(4 Nov 2004) The &man.tar.1; utility (also known as &man.bsdtar.1;) |
| 224 |
does not detect the end of a recording medium such as a tape |
223 |
does not detect the end of media such as tape and |
| 225 |
and a floppy disk properly when it is specified in the <option>-f</option> |
224 |
floppy disk properly when it is specified with the <option>-f</option> |
| 226 |
option. As an alternative &man.gtar.1; (<application>GNU tar</application>) |
225 |
option. As an alternative &man.gtar.1; (<application>GNU tar</application>) |
| 227 |
can be used.</para> |
226 |
can be used.</para> |
| 228 |
</sect1> |
227 |
</sect1> |