Bug 798724 - The total drop performance after upgrading from Fedora 16 to Fedora 17 alpha. CPU load is constantly above 50% and 30% use the process of Xorg.
Summary: The total drop performance after upgrading from Fedora 16 to Fedora 17 alpha....
Keywords:
Status: CLOSED DUPLICATE of bug 735268
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-29 16:33 UTC by Mikhail
Modified: 2012-03-03 16:53 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-02-29 17:37:21 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Mikhail 2012-02-29 16:33:50 UTC 
Description of problem:
The total drop performance after upgrading from Fedora 16 to Fedora 17 alpha. CPU load is constantly above 50% and 30% use the process of Xorg.
Comment 1 Josh Boyer 2012-02-29 17:37:21 UTC 
Yeah, this is a known issue with debug kernels.  Grab the first rc5 build out of koji and it will have the debug options disabled.

*** This bug has been marked as a duplicate of bug 735268 ***
Comment 2 Mikhail 2012-03-01 04:36:04 UTC 
Do you plan fix it? Or live all time with workaround?
Comment 3 Josh Boyer 2012-03-01 13:23:06 UTC 
(In reply to comment #2)
> Do you plan fix it? Or live all time with workaround?

The kernels starting with the Beta release always have the debugging options disabled.  The impact of them won't be present in the GA.
Comment 4 Mikhail 2012-03-01 13:50:25 UTC 
Enabled debugging options should not be so kill performance.
The more this happens only on processors from AMD.
Comment 5 Mikhail 2012-03-03 09:46:36 UTC 
Tested on the Intel Core 2 Duo processors, too slow. Why not make the switch as an option to debug?
Comment 6 Mikhail 2012-03-03 16:53:17 UTC 
Now I couldn't find koji kernel rc5 build. How find it?
Note You need to log in before you can comment on or make changes to this bug.