===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata45.html,v
retrieving revision 1.47
retrieving revision 1.48
diff -c -r1.47 -r1.48
*** www/errata45.html 2016/03/21 05:46:20 1.47
--- www/errata45.html 2016/03/22 10:54:42 1.48
***************
*** 96,102 ****
015: RELIABILITY FIX: April 4, 2010
All architectures
When updating sensors showing the state of RAID volumes
! mpi(4)
allocates temporary memory and then returns it to the kernel as
device memory.
This causes kernel memory usage to be misrepresented, eventually
--- 96,102 ----
015: RELIABILITY FIX: April 4, 2010
All architectures
When updating sensors showing the state of RAID volumes
! mpi(4)
allocates temporary memory and then returns it to the kernel as
device memory.
This causes kernel memory usage to be misrepresented, eventually
***************
*** 213,219 ****
On very high system load, an audio interrupt may occur while the
audio process is filling audio ring buffers. This triggers bogus
(and useless) correction code in the
! audio(4)
driver causing the audio application to go out of sync, and in turn causing
continuous stuttering until the application is restarted.
--- 213,219 ----
On very high system load, an audio interrupt may occur while the
audio process is filling audio ring buffers. This triggers bogus
(and useless) correction code in the
! audio(4)
driver causing the audio application to go out of sync, and in turn causing
continuous stuttering until the application is restarted.
***************
*** 225,231 ****
004: RELIABILITY FIX: April 24, 2009
All architectures
In server mode when in full-duplex mode (the default)
! aucat(1)
will send each synchronization message twice, causing client applications
to think that buffer underruns are occuring. Depending on the
application, this may cause the sound to stutter.
--- 225,231 ----
004: RELIABILITY FIX: April 24, 2009
All architectures
In server mode when in full-duplex mode (the default)
! aucat(1)
will send each synchronization message twice, causing client applications
to think that buffer underruns are occuring. Depending on the
application, this may cause the sound to stutter.
***************
*** 240,246 ****
When DMA'able memory is mapped by device drivers, the
mapping flags and protection are partially uninitialized.
Depending on the calling context, this may cause devices to misbehave, like
! audio(4)
to stutter, but other anomalies might be observed for other
device types.
--- 240,246 ----
When DMA'able memory is mapped by device drivers, the
mapping flags and protection are partially uninitialized.
Depending on the calling context, this may cause devices to misbehave, like
! audio(4)
to stutter, but other anomalies might be observed for other
device types.