Summary: | rage 128 + dri = X lockup | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Ted Rodgers <tedrodgers> | ||||
Component: | Driver/rage128 | Assignee: | Xorg Project Team <xorg-team> | ||||
Status: | RESOLVED DUPLICATE | QA Contact: | Xorg Project Team <xorg-team> | ||||
Severity: | normal | ||||||
Priority: | high | CC: | brice.goglin, clmason, n-roeser, orion, str8bslinux, tedrodgers | ||||
Version: | 7.0.0 | ||||||
Hardware: | All | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Ted Rodgers
2006-01-10 20:26:45 UTC
I see the exact same problem on an iMac G3 400 (Rage 128 RL/VR AGP). Disabling DRI gets it to work, otherwise it hangs. I get the same error others have reported in other places: (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025 (EE) R128(0): Idle timed out, resetting engine... This is still happening after updating to xorg 6.9.0 on Debian unstable. Any improvements by using custom drm modules from dri.freedesktop.org? Also please try with a current version of xorg and the ati driver. I'm using the latest xorg in Ubuntu 6.10 on an iMac DV+ (450MHz G3 and ATI Rage 128 VR RL video). I have the same problem as described in the thread. Anymore work on this yet? Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. Looks like Debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412228 as well, reproducible with 6.6.3 and 6.7.197. Does Option "CCEusecTimeout" "100000" (or even larger values; the default is 10000) work around the problem? I just tested Option "CCEusecTimeout" "100000" it doesn't change anything to the display. (In reply to comment #8) > I just tested > > Option "CCEusecTimeout" "100000" > > it doesn't change anything to the display. Did the log file show the option being effective? What about "1000000"? Anyway, as people claim that this problem doesn't affect x86, maybe there was an architecture specific regression at some point, in which case somebody would need to track that down... Created attachment 23137 [details]
Xorg log
Just saw this with Fedora 10 on Dell Precision 340 with ATI Technologies Inc Rage 128 Pro Ultra TF, so it can happen on x86. This is with no xorg.conf. Will try again with Option "CCEusecTimeout" "1000000"
With: (**) R128(0): Option "CCEusecTimeout" "1000000" X crashes on startup. Display is garbled - seems to be related to what was last displayed. I can always reproduce this on x86, so this bug occurs at least on PowerPC and on x86. This bug is older than the one I'm marking it as a duplicate of. The other has more information and logs, so I figured it'd be better to not lose that stuff. Will move CCs in this bug to the other. *** This bug has been marked as a duplicate of bug 23996 *** Specific to this bug where X never starts, rather than lockups after starting, I have more recent (Ubuntu 12.04) logs in downstream https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-r128/+bug/1023975 Only workarounds I have found are to ForcePCIMode or Disable DRI. Could this be a uninorth_agp problem? Without really understanding what I am reading, the "AGP apterture is 256M @ 0x0" and "AGP V2 device into 0x mode" seem strange to me. On iMac with Rage128 Ultra 16M Summary of relevant (Speculated) from dmesg: dmesg | grep AGP [ 0.585628] Linux agpgart interface v0.103 [ 29.655997] agpgart-uninorth 0000:00:0b.0: Apple UniNorth/Pangea chipset [ 29.658518] agpgart-uninorth 0000:00:0b.0: configuring for size idx: 64 [ 29.736441] agpgart-uninorth 0000:00:0b.0: AGP aperture is 256M @ 0x0 [ 43.502188] agpgart: Couldn't find an AGP VGA controller. [ 43.502261] agpgart-uninorth 0000:00:0b.0: putting AGP V2 device into 0x mode dmesg | grep -i vga [ 0.047384] vgaarb: loaded [ 32.545041] vgaarb: this pci device is not a vga device [ 33.354151] vgaarb: this pci device is not a vga device [ 33.964274] agpgart: Couldn't find an AGP VGA controller. From Xorg.0.log [ 265.172] (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025 [ 265.172] (EE) R128(0): Idle timed out, resetting engine... [ 282.882] (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025 [ 282.882] (EE) R128(0): Idle timed out, resetting engine... [ 298.704] (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025 [ 298.705] (EE) R128(0): Idle timed out, resetting engine... |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.