[karmic] Xorg 100% CPU utilization -- only after first login
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cryptsetup |
Invalid
|
Undecided
|
Unassigned | ||
cryptsetup (Ubuntu) |
Fix Released
|
High
|
Canonical Foundations Team | ||
Karmic |
Fix Released
|
High
|
Canonical Foundations Team | ||
upstart (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Karmic |
Invalid
|
High
|
Unassigned | ||
usplash (Ubuntu) |
Invalid
|
High
|
Canonical Foundations Team | ||
Karmic |
Invalid
|
High
|
Canonical Foundations Team |
Bug Description
On my system, Xorg takes up 100% of (one of the) CPUs after startup. The problem goes away once the X server is restarted. This happens both with the xserver from the archive and the latest 1.7 snapshot. This might be a race related to the fact that ubuntu is installed on an SSD. It seems to be the same problem that is discussed in this ubuntuforums thread:
http://
Here is what I could find out about the problem:
strace reports repeated (failing) calls to
ioctl(5, TCFLSH, 0x2) = -1 EIO (Input/output error)
where fd 5 is /dev/tty7. This translates to a tcflush call in drain_console(). Backtrace:
Breakpoint 6, drain_console (fd=5, closure=0x0) at ../../.
89 ../../.
in ../../.
(gdb) bt
#0 drain_console (fd=5, closure=0x0) at ../../.
#1 0x000000000046ecd1 in xf86Wakeup (blockData=<value optimized out>, err=<value optimized out>, pReadmask=<value optimized out>)
at ../../.
#2 0x0000000000443c7b in WakeupHandler (result=7, pReadmask=0x7d8440) at ../../dix/
#3 0x00000000004609d5 in WaitForSomething (pClientsReady=
#4 0x0000000000440ef2 in Dispatch () at ../../dix/
#5 0x00000000004265fc in main (argc=9, argv=0x7d7228, envp=<value optimized out>) at ../../dix/
o
So we have a fd in some kind of error state that causes select() to always return right away. I don't know enugh about how select() works to identify the problem, though.
summary: |
- [karmic] Xorg 100% CPU utilization after startup + [karmic, intel] Xorg 100% CPU utilization after startup on SSDs |
summary: |
- [karmic, intel] Xorg 100% CPU utilization after startup on SSDs + [karmic] Xorg 100% CPU utilization after startup on SSDs |
summary: |
- [karmic] Xorg 100% CPU utilization after startup on SSDs + [karmic] Xorg 100% CPU utilization -- only after first login |
Changed in xorg-server (Ubuntu): | |
status: | New → Confirmed |
Changed in upstart (Ubuntu Karmic): | |
importance: | Undecided → High |
status: | Invalid → Confirmed |
affects: | xorg-server (Ubuntu Karmic) → gdm (Ubuntu Karmic) |
Changed in gdm (Ubuntu Karmic): | |
assignee: | Bryce Harrington (bryceharrington) → nobody |
Changed in upstart (Ubuntu Karmic): | |
assignee: | nobody → Canonical Foundations Team (canonical-foundations) |
Changed in cryptsetup: | |
status: | New → Confirmed |
status: | Confirmed → Invalid |
affects: | gdm (Ubuntu Karmic) → cryptsetup (Ubuntu Karmic) |
Changed in cryptsetup (Ubuntu Karmic): | |
status: | Incomplete → Confirmed |
Changed in cryptsetup: | |
status: | Invalid → Confirmed |
Changed in upstart (Ubuntu Karmic): | |
assignee: | Canonical Foundations Team (canonical-foundations) → nobody |
Changed in cryptsetup (Ubuntu Karmic): | |
assignee: | nobody → Scott James Remnant (scott) |
Changed in cryptsetup (Ubuntu Karmic): | |
status: | Confirmed → Invalid |
Changed in cryptsetup: | |
status: | Confirmed → Invalid |
affects: | cryptsetup (Ubuntu Karmic) → usplash (Ubuntu Karmic) |
Changed in usplash (Ubuntu Karmic): | |
assignee: | Scott James Remnant (scott) → Robbie Williamson (robbie.w) |
status: | Invalid → Confirmed |
assignee: | Robbie Williamson (robbie.w) → nobody |
affects: | usplash (Ubuntu Karmic) → cryptsetup (Ubuntu Karmic) |
Changed in cryptsetup (Ubuntu Karmic): | |
assignee: | nobody → Robbie Williamson (robbie.w) |
assignee: | Robbie Williamson (robbie.w) → nobody |
assignee: | nobody → Scott James Remnant (scott) |
Changed in cryptsetup (Ubuntu Karmic): | |
assignee: | Scott James Remnant (scott) → Robbie Williamson (robbie.w) |
assignee: | Robbie Williamson (robbie.w) → Canonical Foundations Team (canonical-foundations) |
affects: | cryptsetup (Ubuntu Karmic) → usplash (Ubuntu Karmic) |
Changed in usplash (Ubuntu Karmic): | |
status: | Confirmed → Fix Released |
Changed in usplash (Ubuntu Karmic): | |
status: | Fix Released → Confirmed |
Changed in cryptsetup: | |
status: | Invalid → Confirmed |
Changed in cryptsetup: | |
status: | Confirmed → Invalid |
Changed in cryptsetup (Ubuntu Karmic): | |
status: | New → Confirmed |
Changed in usplash (Ubuntu Karmic): | |
status: | Confirmed → Invalid |
Changed in upstart (Ubuntu Karmic): | |
status: | Invalid → Confirmed |
Changed in cryptsetup (Ubuntu Karmic): | |
milestone: | none → ubuntu-9.10 |
importance: | Undecided → High |
assignee: | nobody → Canonical Foundations Team (canonical-foundations) |
Changed in cryptsetup (Ubuntu Karmic): | |
status: | Fix Released → Fix Committed |
status: | Fix Committed → Fix Released |
tags: | added: iso-testing |
I was going to attach an Xorg.log, but strangly enough the problem hasn't appeared yet after three or four reboots.