Bug 20690 - After resuming from suspend, playing a movie crashes the X server
Summary: After resuming from suspend, playing a movie crashes the X server
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Gordon Jin
QA Contact: Xorg Project Team
URL: http://bugs.debian.org/cgi-bin/bugrep...
Keywords: NEEDINFO
Depends on:
Reported: 2009-03-16 08:16 UTC by Sam Morris
Modified: 2009-03-31 04:01 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

console output (4.17 KB, application/octet-stream)
2009-03-16 08:16 UTC, Sam Morris
no flags Details

Description Sam Morris 2009-03-16 08:16:03 UTC
Created attachment 23919 [details]
console output

After I resume from suspend, trying to play a movie in totem or mplayer causes
the x server to exit. I guess it's actually the use of XVideo that causes the

Unfortunately, nothing shows up in the x server log. However, the following
kernel messages are logged:

Feb 10 12:00:35 durandal kernel: [208836.264371] [drm:i915_getparam] *ERROR* Unknown parameter 5
Feb 10 12:00:36 durandal kernel: [208837.311684] [drm:i915_getparam] *ERROR* Unknown parameter 5

To the console is printed:

        X: ../../../libdrm/intel/intel_bufmgr_fake.c:1107: drm_intel_fake_bo_validate: Assertion `bo_fake->block->bo == &bo_fake->bo' failed.
        xinit:  connection to X server lost.

Full output attached.

I am using version 2.6.1 of the driver. I have libdrm-intel1 version 2.4.4+git+20090205+8b88036 which I assume refers to commit 8b88036.
Comment 1 Gordon Jin 2009-03-17 18:16:04 UTC
Could you try newer kernel like 2.6.29-rcX or at least 2.6.28?
It will also be good to try a newer intel version like
Comment 2 Sam Morris 2009-03-31 04:01:30 UTC
I've not seen this with 2.6.29 for some time. Will re-open if it occurs again.

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.