Summary: | XBMC can consistently be crashed with BadAccess GLX error, possibly related to UXA etc., need help debugging | ||
---|---|---|---|
Product: | xorg | Reporter: | Leho Kraav (:macmaN :lkraav) <leho> |
Component: | Driver/intel | Assignee: | Ian Romanick <idr> |
Status: | RESOLVED WORKSFORME | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | CC: | leho |
Version: | 7.4 (2008.09) | Keywords: | NEEDINFO |
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Leho Kraav (:macmaN :lkraav)
2009-10-13 10:19:33 UTC
previous desc referred to running XBMC SVN 22528. upgrading to SVN 23692 has improved this issue, will test and report further. handing glx issue to idr. also, please explain what you mean by "improved" I'm also seeing this issue with Boxee, an XBMC fork. It happens 100% of the time after the initial Boxee login screen: X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 26 (X_GLXMakeContextCurrent) Serial number of failed request: 2896 Current serial number in output stream: 2896 The issue started after upgrading from Mythbuntu 9.04 to 9.10, going from intel driver 2.6.99.1+git20090402 to 2.9.0+git20091026. i was actually thinking about closing this particular bug, because the newer XBMC SVN builds don't exhibit the same crash anymore, but obviously it would be nice to know what kind of NEEDINFO we could provide to debug this kind of thing? I can confirm seeing this issue in both XBMC and Boxee with at least Intel drivers 2.8.0 and Xorg server 1.6.2, possibly prior; the older (pre-UXA) drivers worked fine on the same hardware (Intel GMA 4500). (In reply to comment #4) > i was actually thinking about closing this particular bug, because the newer > XBMC SVN builds don't exhibit the same crash anymore, but obviously it would be > nice to know what kind of NEEDINFO we could provide to debug this kind of > thing? I think the NEEDINFO was in reference to the statement in comment #1 "upgrading to SVN 23692 has improved this issue". What is meant by improved? It sounds like XBMC made some changes, and the bug is no longer reproducible. Is that correct? I tried version 9.04.1+svn20091002-0.0 on Debian with tip of Mesa, X server, and xf86-video-intel, and I was not able to reproduce this bug. (In reply to comment #6) > I think the NEEDINFO was in reference to the statement in comment #1 "upgrading > to SVN 23692 has improved this issue". What is meant by improved? It sounds > like XBMC made some changes, and the bug is no longer reproducible. Is that > correct? Yes, it would appear that some changes in XBMC stopped this particular bug. after changing to compiling built-in python in XBMC, i have no more crashes related to this plugin. i believe that was the culprit all along for me. not sure about the other cases here. Since this bug can no longer be reproduced, I'm going to close it. |
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.