Bug 438918

Summary: Optical drive activity in kernel-2.6.24.3-34.fc8 makes system unusable
Product: [Fedora] Fedora Reporter: lehi k davis <slacker>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 8   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-03-31 21:57:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg from 2.6.24 boot none

Description lehi k davis 2008-03-25 22:54:14 UTC
Description of problem:
Doing optical drive intensive operations (burning DVD/CD, playing back video
from DVD/CD) causes the machine to slow down to an unusable state.  For example,
playing an unencryped DVD with mplayer, mplayer will report that the system is
too slow and drop frames.   Burning data to a DVD+RW slowed the system down so
much, it took over 3 minutes for window focus to change after clicking on a
different window.

Version-Release number of selected component (if applicable):
kernel-2.6.24.3-34.fc8

How reproducible:
Every time.   

Steps to Reproduce:
1. Boot from kernel-2.6.24.3-34.fc8
2. attempt to burn data to cd/DVD
  
Actual results:
System slows to an unusable state

Expected results:
maybe 30% cpu utilization, and normal operation from there

Additional info:
I went back kernel-2.6.23.15-137.fc8 and everything works fine again.

Comment 1 Chuck Ebbert 2008-03-27 22:50:34 UTC
Please post the boot messages (file /var/log/dmesg) from booting the 2.6.24 kernel.

Comment 2 lehi k davis 2008-03-27 23:21:10 UTC
Created attachment 299407 [details]
dmesg from 2.6.24 boot

Comment 3 Chuck Ebbert 2008-03-31 21:57:13 UTC

*** This bug has been marked as a duplicate of 437163 ***