Bug 698127 - xorg is randomly unresposive using a radeon X1300 + compiz
Summary: xorg is randomly unresposive using a radeon X1300 + compiz
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 14
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: [cat:modesetting]
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-20 09:24 UTC by Davide Corrado
Modified: 2018-04-11 12:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 16:37:49 UTC
Type: ---


Attachments (Terms of Use)

Description Davide Corrado 2011-04-20 09:24:59 UTC
Description of problem:

i have found an exact description of the problem here:
http://ubuntuforums.org/showthread.php?t=1664467

this user describes the same problems i have. He is using ubuntu, im using fedora 14

i quote his description here
"sometimes, X just freezes on me. It's not a total freeze because I can move the mouse pointer around, but the desktop is unresponsive. However, I can VT-switch and work from a shell without any problems. Upon examining the running processes in top, nothing seems out of place. No single process is hogging CPU or memory, system load is good, everything looks fine. I've checked all of the system logs, Xorg's log, and the .xsession-errors log. Nothing wrong that I can tell. Whenever I VT-switch back to X, I can still move the mouse pointer around, but still the desktop doesn't respond.

I've found that I can restart X (sudo /etc/init.d/gdm restart), but this of course means I lose all my windows in X. X restarts just fine, but the system seems a little unstable to me. For instance, pulse audio doesn't always seem to work. A reboot clears everything up, however.

Now for the trigger. I can't figure out what causes the freeze! At first I thought it was Flash locking up on me, but I don't think that's the case anymore. Then I noticed it seems to happen more when I use Google Chrome than Firefox. Finally, I've tried disabling Compiz for over a week and the bug has not showed up. As soon as I re-enable Compiz and spend five minutes with Chrome, then I have this X freeze. It seems to me that it usually happens when I'm in the middle of scrolling a page in Chrome. But it seems to happen at other times, as well. I can't seem to reliably reproduce the bug."

the same behaviour happens to me, but if i do multiple vt switching sometimes the keyboard does not work anymore so i have to kill X the first time i vt-switch... Im using a t60 laptop by lenovo with X1300 video card.


Version-Release number of selected component (if applicable):



How reproducible:
have a laptop with a X1300 video card, enable compiz... wait


Steps to Reproduce:
1.
2.
3.
  
Actual results:

i have to kill Xorg

Expected results:

Xorg is stable using compiz

Additional info:

Comment 1 Davide Corrado 2011-04-21 09:22:31 UTC
for additional info, i have already pointed out (in a previous ticket which i have closed because part of my diagnosis was erroneus) that the radeon module, when it's loaded, sees the video card with 128 MB of VRAM, with sounds odd to me:

...
[    1.564084] [drm] Initialized drm 1.1.0 20060810
[    1.608537] [drm] radeon defaulting to kernel modesetting.
[    1.608541] [drm] radeon kernel modesetting enabled.
[    1.610295] [drm] initializing kernel modesetting (RV515 0x1002:0x7149).
[    1.610485] [drm] register mmio base: 0xEE100000
[    1.610487] [drm] register mmio size: 65536
[    1.610793] [drm] Generation 2 PCI interface, using max accessible memory
[    1.611064] [drm] radeon: irq initialized.
[    1.611838] [drm] Detected VRAM RAM=128M, BAR=128M
[    1.611841] [drm] RAM width 64bits DDR
[    1.611973] [drm] radeon: 64M of VRAM memory ready
[    1.611976] [drm] radeon: 512M of GTT memory ready.
[    1.612027] [drm] GART: num cpu pages 131072, num gpu pages 131072
[    1.613762] [drm] radeon: 1 quad pipes, 1 z pipes initialized.
[    1.615332] [drm] PCIE GART of 512M enabled (table at 0x00040000).
[    1.615401] [drm] Loading R500 Microcode
[    1.617657] [drm] radeon: ring at 0x0000000008000000
[    1.617709] [drm] ring test succeeded in 4 usecs
[    1.617954] [drm] radeon: ib pool ready.
...

i say it is strange because my video card has 64mb onboard...
Maybe the "compiz issue" is related to having a wrong VRAM in the readeon module... I own a desktop which is very close to my laptop (it uses RV530 instead of RV515) and the issue doesnt exist... in that case the video card has 256 MB of video ram and during the radeon module modprobe the amount of detected memory is VRAM=BAR=256M...

Comment 2 Fedora Admin XMLRPC Client 2011-06-01 20:26:59 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora Admin XMLRPC Client 2011-06-01 20:27:00 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora Admin XMLRPC Client 2011-06-01 20:28:53 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Fedora Admin XMLRPC Client 2011-06-01 20:30:56 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Matěj Cepl 2011-07-27 05:41:16 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 add drm.debug=0x04 to the kernel command line, restart computer, and attach

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

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 7 leigh scott 2011-07-27 07:38:25 UTC
Reassigned to mesa as this is clearly a video driver issue.

Comment 8 Dave Airlie 2012-02-12 16:16:56 UTC
does putting radeon.msi=0 on the command line help?

Comment 9 Fedora End Of Life 2012-08-16 16:37:52 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.