Summary: | [r128] DRI causes lock-up | ||
---|---|---|---|
Product: | xorg | Reporter: | Rhys Ickeringill <ickers> |
Component: | Driver/rage128 | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | major | ||
Priority: | medium | CC: | brice.goglin, clmason, n-roeser, tedrodgers |
Version: | 7.2 (2007.02) | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | 2011BRB_Reviewed | ||
i915 platform: | i915 features: | ||
Attachments: |
Description
Rhys Ickeringill
2009-09-17 07:36:58 UTC
Created attachment 29632 [details]
Kernel log from about time of foobillard system lockup
DRM debug and this kernel log apply to the same foobillard system lockup (note the timestamps). Last line of this file is my futile attempt to reboot my system via ACPI...
Created attachment 29635 [details]
Kernel log associated with mplayer+xv+dma X freeze
Not sure about exact timing of the error logged with respect to the X freeze - it might be before, at or after the time of the freeze. However it *is* associated in some way, as i don't see this unless X freezes due to mplayer usage.
Created attachment 29636 [details]
X config file
Created attachment 29637 [details]
Xorg log associated with wine semi-random X freezes
R128CCEWaitForIdle errors are near EOF. Log captured prior to addition of DMAforXv setting.
Comment on attachment 29631 [details]
DRM debug output from foobillard crash
Am guessing that the repeated logging of "[drm:r128_freelist_get] returning NULL!" towards the DRM debug log EOF is significant. Perhaps the multiple calls to drm_lock near the beginning of this same log are too?
*** Bug 5562 has been marked as a duplicate of this bug. *** There's no longer an r128 DRI driver. |
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.