Bug 74704 - Kernel re-prioritizing X (ioperm?)..
Summary: Kernel re-prioritizing X (ioperm?)..
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 8.0
Hardware: i386
OS: Linux
low
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-01 01:04 UTC by Ali-Reza Anghaie
Modified: 2005-10-31 22:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-06-05 19:25:30 UTC
Embargoed:


Attachments (Terms of Use)

Description Ali-Reza Anghaie 2002-10-01 01:04:30 UTC
Description of Problem:   
   
The default kernel automagically nices X to -10. Why is the kernel futzing   
with userland process priorities? 
 
Version-Release number of selected component (if applicable):   
   
kernel-2.4.18-14   
XFree86-4.2.0-72   
   
How Reproducible:   
 
Always.  
 
Steps to Reproduce:   
1. Start X. Or boot into runlevel 5.  
2. ps -efl |grep X  or  top  
3. Cock head sideways at the X process priority. 
   
Actual Results:   
  
X is niced -10.  
   
Expected Results:   
   
X should be regular priority unless launched otherwise.  
  
Additional Information:   
  
I think it's much more sane to prioritize X by start-up scripts instead of  
handling it via the kernel. I really don't think the kernel should molest  
userland priorities as such. 
 
Setting to low/high as I think it's a low priority but it's a severe mistake 
IMO. 
 
Cheers, -Ali


Note You need to log in before you can comment on or make changes to this bug.