[gm45] Dual head corruption on 2.6.37 lucid backport

Bug #698120 reported by Minh Ha Duong
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Lenovo X301 laptop, 4G ram, Intel(R) Core(TM)2 Duo CPU U9400 @ 1.40GHz. Intel GM45 Express graphic chipset, Kubuntu 10.4.1 LTS Lucid 32 bits, Xorg driver "intel"

# uname -a
Linux wall-e 2.6.37-12-generic-pae #26~lucid1-Ubuntu SMP Wed Jan 5 22:54:38 UTC 2011 i686 GNU/Linux

# version.log
Ubuntu 2.6.37-12.26~lucid1-generic-pae 2.6.37

Symptoms:
When starting X with the external screen attached to the VGA connector, I can't type anything in the login/password at the kdm greeter dialog. I can switch to VT1. Then I can kill kdm. Restarting kdm gives fatal error with technical messages about gem.

Starting without the external screen is okay. If I plug the external screen and start using it (xrandr), the cursor becomes corrupted when it is inside a konsole window on the laptop screen, but gets back to normal outside this window. Then X freezes after a while.

Working single-headed without plugging the external screen at all is fine so far.

Previous versions 2.6.35 and 2.6.32 did not do this
Previous version 2.6.37-11 already had the problem.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image (not installed)
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.37-12.26~lucid1-generic-pae 2.6.37
Uname: Linux 2.6.37-12-generic-pae i686
Architecture: i386
Date: Thu Jan 6 14:52:34 2011
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: linux

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07)
     Subsystem: Lenovo Device [17aa:20e0]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
     Subsystem: Lenovo Device [17aa:20e4]

Revision history for this message
Minh Ha Duong (haduong) wrote :
Revision history for this message
Minh Ha Duong (haduong) wrote :

dmesg attached (without X freezing).

Revision history for this message
Minh Ha Duong (haduong) wrote :

Earlier version 2.6.37-11 also had the bug.

description: updated
Revision history for this message
Minh Ha Duong (haduong) wrote :

In /var/log/kern.log I get a long sequence of:

[drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap a purgeable buffer

that ends up finally with a

[drm:i915_gem_object_bind_to_gtt] *ERROR* Attempting to bind a purgeable object

then X freezes

Minh Ha Duong (haduong)
description: updated
Revision history for this message
Minh Ha Duong (haduong) wrote :

It looks like memory allocation trouble in DRM with the "intel" video driver.

I booted today with the 2.6.36-1-generic-pae #7~lucind1-Ubuntu kernel.
It does not set the external screen at the correct resolution (regression compared to .32)

Usually it works otherwise, but I had the bug occur today also with 2.6.36.

I switched between VT1 (console) and VT7 (the stuck X at kdm greeter stage) a few times for experiment.

In /var/log/kern.log I had about a dozen of the following:
Jan 7 09:41:46 wall-e kernel: [ 7.128517] [drm:i915_gem_madvise_ioctl] *ERROR* Attempted i915_gem_madvise_ioctl() on a pinned object

and a few pairs of:
Jan 7 09:42:37 wall-e kernel: [ 56.828954] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

These messages also appear in dmsg, where they are followed by
[ 56.856042] Skipping EDID probe due to cached edid

In xorg.log when I switch to the VT7 there is:
(II) Open ACPI successful (/var/run/acpid.socket)
(II) AIGLX: Resuming AIGLX clients after VT switch
(II) intel(0): No memory allocations
(EE) intel(0): Couldn't create pixmap for fbcon
(II) intel(0): EDID vendor "LEN", prod id 16500
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1440x900"x0.0 102.00 1440 1488 1520 1836 900 903 909 926 -hsync -vsync (55.6 kHz)
(II) intel(0): Modeline "1440x900"x0.0 85.00 1440 1488 1520 1836 900 903 909 926 -hsync -vsync (46.3 kHz)

Revision history for this message
Minh Ha Duong (haduong) wrote :

Looking at updating the "intel" video driver. The officials PPA route seem perilous:
The xserver-xorg-video-intel in maverik depends on libdrm-intel1 >= 2.4.21 , xorg-video-abi-8.0 nonexistent package, and xserver-xorg-core >= 1.8.995.

Revision history for this message
Minh Ha Duong (haduong) wrote :

Updating to
xserver-xorg-video-intel 2:2.11.0-1ubuntu1~xup
from the Ubuntu-x-swat PPA does not resolve the bug.

Adding in xorg.conf
  Option "DRI" "false"
seem to workaround the problem

Revision history for this message
Minh Ha Duong (haduong) wrote :

Note: package libdrm-intel1 is also suspicious.

affects: linux (Ubuntu) → xserver-xorg-video-intel (Ubuntu)
Revision history for this message
Minh Ha Duong (haduong) wrote :
Revision history for this message
Minh Ha Duong (haduong) wrote :

Looking at the "debugging X freeze" page.

The GPU itself does not seem stuck; VT swiches are possible, /sys/kernel/debug/dri/0/i915_error_state is clean, as is i915_wedged and the content of i915_ringbuffer_info keeps changing.

Option "AIGLX" "off" does not resolve.

Option "NoMTRR" "true" prevents the freeze.

bugbot (bugbot)
tags: added: kubuntu
tags: added: regression-release
removed: regression-potential
bugbot (bugbot)
description: updated
bugbot (bugbot)
summary: - Dual head corruption on 2.6.37 lucid backport
+ [gm45] Dual head corruption on 2.6.37 lucid backport
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Revision history for this message
Bryce Harrington (bryce) wrote :

Looks like a kernel drm bug.

Also note that the new kernels are supported only for Server use cases, not Desktop.

affects: xserver-xorg-video-intel (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Confirmed
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Thanks in advance.

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
penalvch (penalvch) wrote :

Minh Ha Doung, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: needs-kernel-logs
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Rolf Leggewie (r0lf) wrote :

closing as obsolete

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Brad Figg (brad-figg)
tags: added: cscc
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.