Bug 16106

Summary:

[i915] i915_driver_lastclose BUG resulting in xorg lockup

Product:

DRI

Reporter:

Tobias Jakobi <liquid.acid>

Component:

DRM/other

Assignee:

Default DRI bug account <dri-devel>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

medium

Version:

DRI git

Hardware:

x86 (IA32)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
extract from kern.log	none

Description Tobias Jakobi 2008-05-26 07:40:52 UTC

Created attachment 16741 [details]
extract from kern.log

Hi there,

I'm using a X GIT setup that's around 2 days old. I'm experiencing random X server lockups with the kernel still active (I could restart the system via ACPI).
X however was locked, I couldn't use keyboard to kill it.

I already experienced this thrice, a snip from the kernel log is attached. It seems to have something to do with the i915 DRM kernel module.

The kernel module, libdrm, mesa and xorg-server were built from GIT. Like I said the age is around 2 days.

Distro is gentoo linux, I'm not using any fancy optimization options - so this should not be a problem.

uname -a:
Linux leena 2.6.25-gentoo-r4 #1 Sun May 25 14:57:33 CEST 2008 i686 Intel(R) Celeron(R) M processor 1.50GHz GenuineIntel GNU/Linux

lspci:
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)

Each time this happens (X goes static, then screen goes black, fades like the server tries some restarting, comes up but stays black only with the cursor still there) multiple BUGs appear in kern.log.

I separated the occurences with two empty lines each.

Greets,
Tobias Jakobi

Comment 1 Tobias Jakobi 2008-06-25 08:25:26 UTC

After my last DRM GIT update I can't reproduce the bug anymore. I'm not sure what fixed it but my X.org is rather stable since the update.

Resolving to FIXED. If the bug reappears I'm going to reopen this one.

Cheers,
Tobias

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.