Created attachment 18097 [details] xorg.conf System Environment: -------------------------- --Platform: 945g --Architecture(32-bit,64-bit,compatiblity): 32-bit --2D driver: drm-gem 286ff63f83db8ea16514512385e6f8c6875871ef --3D driver: mesa_7_0_branch 97eb33529ae2f96220eec5238d8d0e9a07ce91d5 --DRM: master 4585787bd1a1d782b9e7c06095f98d09165b8c23 --Xserver: server-1.4-branch --Kernel: 2.6.26-rc5 --Display connector: VGA Bug detailed description: -------------------------- Using the overlay mode,system crash when playing video for a while. Reproduce steps: ---------------- 1 xinit & 2 mplayer -vo xv:port=88 vediofile Current result: ---------------- fail Expected result: ---------------- normal
Created attachment 18098 [details] Xorg.0.log
Sometimes this issue occured in several minutes,about 7 minutes. But with texture video, it goes well.
Log shows you're using xserver 1.3 and intel 2.1.1 driver, could you double-check?
Created attachment 18117 [details] Xorg.0.log
How about 2D driver master branch? You seems mixing drm-gem branch with origin ttm code, which suggests a failure path. If you want to test gem, following guide on which branches to build.
what guide ?
(In reply to comment #5) > How about 2D driver master branch? > > You seems mixing drm-gem branch with origin ttm code, which suggests a failure > path. If you want to test gem, following guide on which branches to build. > We are testing 2d driver/drm-gem branch + drm master. Because drm module with drm-gem will take a long time to merge to formal kernel, intel driver with drm-gem will coexist with current drm master for a long time. So we test intel driver(with drm-gem) against drm master on purpose. We will test intel master branch to see if this bug is drm-gen specific. Also for #16988.
(In reply to comment #7) > (In reply to comment #5) > > How about 2D driver master branch? > > > > You seems mixing drm-gem branch with origin ttm code, which suggests a failure > > path. If you want to test gem, following guide on which branches to build. > > > We are testing 2d driver/drm-gem branch + drm master. Because drm module with > drm-gem will take a long time to merge to formal kernel, intel driver with > drm-gem will coexist with current drm master for a long time. So we test intel > driver(with drm-gem) against drm master on purpose. > We will test intel master branch to see if this bug is drm-gen specific. Also > for #16988. We do this test using drm master + 2D /drm-gem
Are you guys sure about this? I see this's totally wrong. There will be only one memory manager, gem that we will do. drm master's ttm is far from mainstream kernel, but Eric has already sent drm gem patches to lkml for comments. Please reconsider.
Yes, I'm sure.(In reply to comment #9) > Are you guys sure about this? I see this's totally wrong. There will be only > one memory manager, gem that we will do. drm master's ttm is far from > mainstream kernel, but Eric has already sent drm gem patches to lkml for > comments. Please reconsider. Yes, I'm sure. Actually our testing with xf86-video-intel/drm-gem + drm/master is requested by Jesse, as he would like to merge drm-gem into master for xf86-video-intel soon. And I agree this testing makes sense at this point, as we can't expect gem kernel becomes popular quite soon. So we'll have to make sure the compatibility for 2.5 release with non-gem kernel.
So for compat test, then use mainline kernel instead of drm master.
Yeah, kernel master might be better than DRM master for testing, since the DRM master is going through some major changes right now.
If this's still there in current build, pls reopen.
Using the current build with drm in stable kernel and from unstable version are both have this issue.So reopen this issue.
Is this the same hw as #17088? We might mark this as invalid if the issue is only on that 945g.
suspicious hardware
Close bugs on suspicious 945G.
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.