[HD 3870] Display Preferences causes 100% CPU usage and does not open correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xorg
Ubuntu 9.04
1. I activated ATI/AMD proprietary FGLRX graphics driver from within Harware Drivers.
2. I restarted PC.
3. I tried to open Display Preferences
4. CPU usage shoots up to 100% on one of my two cores. Other core % is low. Cores alternate with one always near 100% and the other hardly being used. Display Properties is white with a green/blue streak across it.
My GPU is one ATI Radeon HD3870. Photograph of screen attached.
[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82X38/X48 Express DRAM Controller [8086:29e0] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:8295]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon HD 3870 [1002:9501]
Subsystem: ASUSTeK Computer Inc. Device [1043:81f8]
Related branches
description: | updated |
affects: | xorg (Ubuntu) → fglrx-installer (Ubuntu) |
Changed in fglrx-installer (Ubuntu): | |
status: | Incomplete → Confirmed |
description: | updated |
summary: |
- Display Preferences causes 100% CPU usage and does not open correctly + [HD 3870] Display Preferences causes 100% CPU usage and does not open + correctly |
If you switch to the "Processes" TAB in which specific program does it show 100% CPU?
Also it would be useful if you downloaded debug symbols for the program that hogs CPU and the you attach gdb to it and collect a couple of backtraces continuing the program between each backtrace. That way we can see which functions the program is running while consuming all that CPU.
To get debug symbols you need follow these steps (add the "deb http:// ddebs..." lines and do the gpg command and then the sudo apt-get update thing etc): /wiki.ubuntu. com/DebuggingPr ogramCrash
https:/
Then, if the CPU is spinning inside the gnome-display- preferences you can use "dpkg -S gnome-display- preferences" command to see what package that file ships with (which in this case in gnome-control- center) . And then you do: center- dbgsym
sudo apt-get install gnome-control-
And then you attach gdb using "gdb -p $(pidof gnome-display- preferences) " and you can activate logging in gdb using "set logging file gdb.txt" followed by "set logging file on". Finally you just press CTRL-C to break the program and run "bt full" to collect the stack. Then you run "c" to resume execution of the program, wait like 1 second then you press CTRL-C again and repeat "bt full".
Afterwards, attach the gdb.txt file to this bug report.
---
Also, I recommend reporting this bug to the ATI proprietary driver devs because no one else can fix a bug in that code since it's closed source.