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
| Summary: | X use a lot of CPU power and keyboard is malfunctioning | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mattia Verga <mattia.verga> | ||||||||||||||||
| Component: | mingetty | Assignee: | Bernie Innocenti <bernie+fedora> | ||||||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||||
| Priority: | low | ||||||||||||||||||
| Version: | 13 | CC: | anton, bernie+fedora, dougsland, gansalmon, itamar, jonathan, kernel-maint, mcepl, rrakus, xgl-maint | ||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | All | ||||||||||||||||||
| OS: | Linux | ||||||||||||||||||
| Whiteboard: | card_R700/M | ||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||
| Last Closed: | 2010-04-13 17:50:21 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
Mattia Verga
2010-03-22 17:08:53 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. 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.
Created attachment 402345 [details]
messages log
Created attachment 402346 [details]
Xorg.0.log
Created attachment 402348 [details]
xorg.9.log
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.
> 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....
(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 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...
Created attachment 403545 [details]
messages log
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). Created attachment 403804 [details]
messages log from a day when everything is working fine
I've just realized I only changed the component, not the assignation... can someone reassign this bug to the right person? *** This bug has been marked as a duplicate of bug 577482 *** |