Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 510083[details]
Kickstart file to reproduce the issue...
Description of problem:
After I boot the machine with autologin using mingetty, the X is eating 100% of CPU.
Version-Release number of selected component (if applicable):
RHEL 6.1
How reproducible:
Use the attached kickstart file or setup the server like like described below.
I was able to reproduce the issue in KVM Virtual Machine and also on my Laptop with Intel graphic card.
Steps to Reproduce:
Set up the following configuration files:
cat >> /home/gsstv-client/.bashrc << EOF
set DISPLAY=:0.0
if [ \`tty\` == /dev/tty7 ];
then
echo "Starting X ..."
xinit
fi
EOF
cat > /etc/init/tty7.conf << EOF
# tty7 - getty
#
# This service maintains a getty on tty7 from the point the system is
# started until it is shut down again.
start on runlevel [23]
stop on runlevel [!23]
respawn
exec /sbin/mingetty --autologin=gsstv-client tty7
EOF
Actual results:
Output of top command:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1013 root 20 0 104m 8844 4480 R 100.0 0.9 40:16.35 X
Expected results:
X should take just few percents of CPU.
Additional info:
Comment 2RHEL Program Management
2011-07-06 01:32:54 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
I often experience high CPU load on Xorg process. Most of the time the behavior cannot be reproduced. However, with RHEL 6.5, I have noticed quite often the Firefox with various splash displays trigger heavy CPU load. Once the FF tab is closed or the FF is closed then the Xorg settles to normal cpu utilization.
Lately I have been experiencing heavy CPU loads with RHEL 6.7 kernel. Sometimes Xorg high CPU load is experienced with some home grown applications. I am using nVidia driver, which was provided by nVidia. In my environment using Vesa driver doesn't produce the desired rendering. Further since I have multi-displays, using generic nouveau driver is not an option.
Any resolution or a workaround is appreciated.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/
Created attachment 510083 [details] Kickstart file to reproduce the issue... Description of problem: After I boot the machine with autologin using mingetty, the X is eating 100% of CPU. Version-Release number of selected component (if applicable): RHEL 6.1 How reproducible: Use the attached kickstart file or setup the server like like described below. I was able to reproduce the issue in KVM Virtual Machine and also on my Laptop with Intel graphic card. Steps to Reproduce: Set up the following configuration files: cat >> /home/gsstv-client/.bashrc << EOF set DISPLAY=:0.0 if [ \`tty\` == /dev/tty7 ]; then echo "Starting X ..." xinit fi EOF cat > /etc/init/tty7.conf << EOF # tty7 - getty # # This service maintains a getty on tty7 from the point the system is # started until it is shut down again. start on runlevel [23] stop on runlevel [!23] respawn exec /sbin/mingetty --autologin=gsstv-client tty7 EOF Actual results: Output of top command: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1013 root 20 0 104m 8844 4480 R 100.0 0.9 40:16.35 X Expected results: X should take just few percents of CPU. Additional info: