Hide Forgot
Description of problem: During routine activity system freezes for a few seconds Version-Release number of selected component (if applicable): 3.2.1-3.fc16.i686.PAE How reproducible: ransom Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Here's the situation, offered in the hope that the data might be of some use. The system in question is a DVR. It has two functions. Play mp4 files using mplayer that directs output to an HDMI port and writing the output of a SiliconDust HD tuner to disk. When mplayer is running, there are no pauses. CPU usage is 3%, memory is adequate. Adding the SiliconDust tuner interface to the mix CPU usage is 3% for both, memory is still adequate and the mp4 playback pauses for 1-3 seconds at random intervals. The following kernel processes have been observed to be associated with the pausing: ksoftirqd/0 flush-8:0 kswapd0 jbd2/sda7-8 migration/0 kworker/u:33
The function of the SiliconDust tuner interface is to read from an HD tuner connected via a dedicated Ethernet port and write the result to disk, the same disk as is being read by mplayer. The data rate is approximately 100 MB per minute.
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
Tested. Alas, no change.
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.