Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 575907 - X use a lot of CPU power and keyboard is malfunctioning
Summary: X use a lot of CPU power and keyboard is malfunctioning
Keywords:
Status: CLOSED DUPLICATE of bug 577482
Alias: None
Product: Fedora
Classification: Fedora
Component: mingetty
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bernie Innocenti
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: card_R700/M
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-22 17:08 UTC by Mattia Verga
Modified: 2018-04-11 06:57 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-13 17:50:21 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
output from dmesg (deleted)
2010-03-24 15:52 UTC, Mattia Verga 		no flags Details
messages log (deleted)
2010-03-24 15:55 UTC, Mattia Verga 		no flags Details
Xorg.0.log (deleted)
2010-03-24 15:56 UTC, Mattia Verga 		no flags Details
xorg.9.log (deleted)
2010-03-24 15:56 UTC, Mattia Verga 		no flags Details
output from dmesg (deleted)
2010-03-30 18:13 UTC, Mattia Verga 		no flags Details
messages log (deleted)
2010-03-30 18:14 UTC, Mattia Verga 		no flags Details
messages log from a day when everything is working fine (deleted)
2010-03-31 18:33 UTC, Mattia Verga 		no flags Details
Show Obsolete (2) View All

Description Mattia Verga 2010-03-22 17:08:53 UTC 
Description of problem:
I notice that very often the X process use high CPU load (25% e.g. one core of my quad CPU is saturated from X). At same time keyboard leds numlock, capslock and scrollock light up and off while typing.
When this happens keyboard seems to work, the only thing I can see isn't working is changing vt by pressing CTRL-ALT-Fx.


Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg.x86_64        1.7.99.901-8.20100223.fc13


How reproducible:
It happens 9 times on 10, but I don't know why the tenth time it works...

Steps to Reproduce:
1.Start Fedora 13 and log in (I use KDE)
2.Using gkrellm I view a core used at 100%. In process list X is using from 20% to 25% fixed.
3.Keyboard leds light up and off while typing
Comment 1 Matěj Cepl 2010-03-23 17:21:17 UTC 
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach

* your X server config file (/etc/X11/xorg.conf, if available),
* output of the dmesg command,
* system log (/var/log/messages), and
* X server log file (/var/log/Xorg.*.log)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.


We will review this issue again once you've had a chance to attach this information.

Thanks in advance.
Comment 2 Mattia Verga 2010-03-24 15:52:53 UTC 
Created attachment 402344 [details]
output from dmesg

Here are the logs you requested.
Also notice I tried to update X server to
xorg-x11-server-Xorg.x86_64        1.7.99.902-2.20100319.fc13

At first reboot it worked without problems and I thought that the bug was resolved, but today when I boot up the PC it gives me the same strange behaviour.
Comment 3 Mattia Verga 2010-03-24 15:55:26 UTC 
Created attachment 402345 [details]
messages log
Comment 4 Mattia Verga 2010-03-24 15:56:07 UTC 
Created attachment 402346 [details]
Xorg.0.log
Comment 5 Mattia Verga 2010-03-24 15:56:44 UTC 
Created attachment 402348 [details]
xorg.9.log
Comment 6 Mattia Verga 2010-03-26 18:08:59 UTC 
Seems that upgrading to kernel 2.6.33.1-19.fc13.x86_64 have definitely fixed the problem (before I was using 2.6.33.1.fc13.x86_64).

I will check for a couple of days and if I will not see the problem anymore I will close the bug.
Comment 7 Mattia Verga 2010-03-27 07:54:31 UTC 
> I will check for a couple of days and if I will not see the problem anymore I
> will close the bug.    

No, problem is still present....
Comment 8 Matěj Cepl 2010-03-30 15:48:19 UTC 
(In reply to comment #2)
> Created an attachment (id=402344) [details]
> output from dmesg
> 
> Here are the logs you requested.
> Also notice I tried to update X server to
> xorg-x11-server-Xorg.x86_64        1.7.99.902-2.20100319.fc13

I don't see anything Xorg-related but your logs (both /var/log/messages and dmesg) are overflowing with hard drive related crashes. One example of many:

dracut: /dev/sdb: "pdc" and "nvidia" formats discovered (using nvidia)!
dracut: /dev/sda: "pdc" and "nvidia" formats discovered (using nvidia)!
dracut: no raid sets and with names: ""nvidia""
dracut: Activating formats
dracut: ERROR: nvidia: wrong # of devices in RAID set "nvidia_ceibceci" [1/2] on /dev/sdb
dracut: ERROR: nvidia: wrong # of devices in RAID set "nvidia_ceibceci" [1/2] on /dev/sda
dracut: ERROR: either the required RAID set not found or more options required

(repeats many times). Not sure why top shows Xorg as possible culprit, but it is very unreliable in terms of indicating process in fault, when kernel issues are involved. So, I am reassigning this to kernel component, without prejudice to get this back, if this is still present when kernel issues are resolved.

Thanks for reporting the bug
Comment 9 Mattia Verga 2010-03-30 18:13:30 UTC 
Created attachment 403544 [details]
output from dmesg

Yes, I had a problem with an hard drive that was assigned to a BIOS Raid... in the meantime I removed both the raid and the faulty hard drive, so I attach the new logs.

I'm wondering what is that process that is continuously killed and respawned in /dev/tty4...
Comment 10 Mattia Verga 2010-03-30 18:14:28 UTC 
Created attachment 403545 [details]
messages log
Comment 11 Mattia Verga 2010-03-31 18:31:21 UTC 
At the moment I'm getting no problem: X is using a reasonable CPU time (from 1% to 8%) and keyboard is functioning. Looking in /var/log/messages I cannot see any line such as 

"tty (/dev/tty4) main process (9108) killed by QUIT signal" 

and 

"tty (/dev/tty4) main process ended, respawning"

So I can say that those lines are referred to the high cpu usage. I notice that all those lines start after

Mar 30 16:42:56 localhost /sbin/mingetty[1582]: tty4: invalid character 0x14 in login name
Mar 30 16:43:01 localhost init: tty (/dev/tty4) main process (1582) terminated with status 1
Mar 30 16:43:01 localhost init: tty (/dev/tty4) main process ended, respawning

So I will reassign this bug to mingetty component. I thing problems I get with X and keyboard are directly related to these error lines.

I will attach also another log from today, where you can see there are no errors from mingetty (and as I said everything is working fine).
Comment 12 Mattia Verga 2010-03-31 18:33:22 UTC 
Created attachment 403804 [details]
messages log from a day when everything is working fine
Comment 13 Mattia Verga 2010-04-04 09:48:46 UTC 
I've just realized I only changed the component, not the assignation... can someone reassign this bug to the right person?
Comment 14 Mattia Verga 2010-04-13 17:50:21 UTC 

*** This bug has been marked as a duplicate of bug 577482 ***
Note You need to log in before you can comment on or make changes to this bug.