Kernel BUG at /build/buildd/linux-2.6.35/drivers/gpu/drm/i915/i915_gem.c:4224!

I also get this error, however for me it's trying to start X with a dual screen setup (xorg.conf is attached).

uname -r :
2.6.35-28-generic

lsb_release -rd:
Description: Ubuntu 10.10
Release: 10.10

/proc/version_signature:
Ubuntu 2.6.35-28.50-generic 2.6.35.11

Attached is xorg.conf, /var/log/Xorg.0.log, relevant portion of /var/log/syslog, and output of lspci -vnvn

I have the same problem as mentioned in the original post - It also happens when coming out of sleep mode:

Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473387] kernel BUG at /build/buildd/linux-2.6.35/drivers/gpu/drm/i915/i915_gem.c:4224!
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473391] invalid opcode: 0000 [#1] SMP
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473395] last sysfs file: /sys/devices/pci0000:00/0000:00:1e.0/0000:06:05.0/rf_kill
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473399] Modules linked in: btrfs zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs pppoe pppox aes_i586 aes_generic lib80211_crypt_ccmp binfmt_misc dm_crypt joydev snd_hda_codec_si3054 snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event ipw2200 snd_seq pcmcia libipw snd_timer snd_seq_device cfg80211 ppdev irda snd yenta_socket fujitsu_laptop parport_pc pcmcia_rsrc psmouse pcmcia_core crc_ccitt serio_raw led_class lib80211 soundcore snd_page_alloc lp parport i915 drm_kms_helper drm ahci intel_agp firewire_ohci tg3 libahci i2c_algo_bit video firewire_core crc_itu_t agpgart output ramzswap(C) lzo_compress
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473456]
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473461] Pid: 32462, comm: Xorg Tainted: G C 2.6.35-28-generic #50-Ubuntu FJNB19C/LIFEBOOK S7020
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473465] EIP: 0060:[<f83cd66b>] EFLAGS: 00013286 CPU: 0
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473484] EIP is at i915_gem_object_unpin+0xbb/0xd0 [i915]
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473487] EAX: f6a46900 EBX: f69f8c00 ECX: 000244ff EDX: fffffff9
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473490] ESI: 00024000 EDI: f71ce000 EBP: e0fa1dc8 ESP: e0fa1dbc
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473493] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473497] Process Xorg (pid: 32462, ti=e0fa0000 task=e0ca32c0 task.ti=e0fa0000)
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473500] Stack:
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473502] 00000002 00000003 ca82cb90 e0fa1e4c f83d347b f71ce014 0244c000 00000000
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473509] <0> 00000004 e893e480 00000000 f01a4000 e0fa1e24 00000001 00000003 00000000
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473516] <0> 0244c000 00000003 f69f8c14 ca82cb90 f71ce014 ca82cb90 00000000 f71ce000
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473524] Call Trace:
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473544] [<f83d347b>] ? i915_gem_do_execbuffer+0x71b/0xca0 [i915]
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473562] [<f83d43fa>] ? i915_gem_execbuffer2+0x4a/0x1b0 [i915]
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473580] [<f83d442c>] ? i915_gem_execbuffer2+0x7c/0x1b0 [i915]
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473602] [<f824498d>] ? drm_ioctl+0x1ad/0x430 [drm]
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473620] [<f83d43b0>] ? i915_gem_execbuffer2+0x0/0x1b0 [i915]
Jun 22 21:37:28 LIFEBOOK-S7020 kernel: [403769.473...

Martin Senft, thank you for reporting this bug and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

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

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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. Please let us know your results.

Thanks in advance.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Christopher M. Penalver,

I'm afraid the issue is still there and has been since at least Ubuntu 10.10.

After installing Ubuntu 12.04-beta2 on a flashdisk and package update yesterday, I still get screen blank and sleep issues, that eventually end in a lockup. Some of these issues might easily be X, Compiz, Mesa or Unity bugs.

Blank doesn't really work, as it does a fake switch to console, while keeping the mouse cursor active and waking up the disabled internal monitor. I have to do a switch to a real console and back to get to my X session. Display sleep works, but sometimes, especially after a longer sleep period, it won't wake up. Also, when I leave both monitors enabled, windows tend to move from external monitor to internal after blank/sleep - wake up. But this should be a Compiz/Unity issue.

Moreover, during this bug update i found another bug message in dmesg. This time the system survived. Running apport again.

Will try mainline kernel later.

PS: Apport crashed on me during the first bug update today, so some things might be damaged or missing.

Had apport issues in the second run as well.

ms@ms-ESPRIMO-Mobile-M9400:~$ sudo apport-collect -p linux 747187
[sudo] password for ms:
linux nevyhovuje žádný balík.
ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/apport/report.py", line 718, in add_hooks_info
    symb['add_info'](self, ui)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 37, in add_info
    match_error_messages(report)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 121, in match_error_messages
    if report['ProblemType'] == 'Package':
  File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
    raise KeyError(key)
KeyError: 'ProblemType'
Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 493, in <lambda>
    GLib.idle_add(lambda: self.collect_info(on_finished=self.ui_update_view))
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 861, in collect_info
    icthread.exc_raise()
  File "/usr/lib/python2.7/dist-packages/apport/REThread.py", line 34, in run
    self._retval = self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 111, in thread_collect_info
    if report['ProblemType'] == 'Crash' and \
  File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
    raise KeyError(key)
KeyError: 'ProblemType'

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

The CurrentDmesg.txt file above is missing the most important part of dmesg output. What I was trying to report was:

[ 34.332043] ------------[ cut here ]------------
[ 34.332084] WARNING: at /build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:930 assert_pipe+0x75/0x80 [i915]()
[ 34.332090] Hardware name: ESPRIMO Mobile M9400
[ 34.332095] pipe A assertion failure (expected on, current off)
[ 34.332098] Modules linked in: rfcomm bnep bluetooth vesafb snd_hda_codec_realtek joydev snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi arc4 snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device iwl3945 iwl_legacy i915 mac80211 ppdev drm_kms_helper snd drm i2c_algo_bit cfg80211 psmouse serio_raw soundcore snd_page_alloc parport_pc video mac_hid lp parport usbhid hid sky2 usb_storage
[ 34.332163] Pid: 25, comm: kworker/1:1 Not tainted 3.2.0-22-generic #35-Ubuntu
[ 34.332168] Call Trace:
[ 34.332181] [<ffffffff8106712f>] warn_slowpath_common+0x7f/0xc0
[ 34.332189] [<ffffffff81067226>] warn_slowpath_fmt+0x46/0x50
[ 34.332215] [<ffffffffa0227485>] assert_pipe+0x75/0x80 [i915]
[ 34.332241] [<ffffffffa022b761>] intel_enable_plane+0x41/0x90 [i915]
[ 34.332271] [<ffffffffa022ede6>] i9xx_crtc_mode_set+0x776/0xd90 [i915]
[ 34.332289] [<ffffffffa022805f>] intel_crtc_mode_set+0x6f/0xa0 [i915]
[ 34.332298] [<ffffffffa013ffc5>] drm_crtc_helper_set_mode+0x275/0x440 [drm_kms_helper]
[ 34.332319] [<ffffffffa023188d>] intel_get_load_detect_pipe+0x24d/0x3a0 [i915]
[ 34.332340] [<ffffffffa02426f9>] intel_tv_detect+0x129/0x220 [i915]
[ 34.332348] [<ffffffffa01405d3>] drm_helper_probe_single_connector_modes+0x1e3/0x380 [drm_kms_helper]
[ 34.332355] [<ffffffffa013ed42>] drm_fb_helper_hotplug_event+0xf2/0x150 [drm_kms_helper]
[ 34.332375] [<ffffffffa02415ec>] intel_fb_output_poll_changed+0x1c/0x20 [i915]
[ 34.332382] [<ffffffffa013fd40>] output_poll_execute+0x190/0x1a0 [drm_kms_helper]
[ 34.332389] [<ffffffffa013fbb0>] ? drm_helper_mode_fill_fb_struct+0x30/0x30 [drm_kms_helper]
[ 34.332395] [<ffffffff81084e1a>] process_one_work+0x11a/0x480
[ 34.332400] [<ffffffff81085bc4>] worker_thread+0x164/0x370
[ 34.332405] [<ffffffff81085a60>] ? manage_workers.isra.29+0x130/0x130
[ 34.332410] [<ffffffff8108a41c>] kthread+0x8c/0xa0
[ 34.332417] [<ffffffff81666bf4>] kernel_thread_helper+0x4/0x10
[ 34.332421] [<ffffffff8108a390>] ? flush_kthread_worker+0xa0/0xa0
[ 34.332426] [<ffffffff81666bf0>] ? gs_change+0x13/0x13
[ 34.332429] ---[ end trace 585b68916a0e9141 ]---
[ 34.388070] [drm:intel_pipe_set_base] *ERROR* No FB bound

Mainline kernel 3.2.14 behaves like the Ubuntu version, I'm still getting some "[drm:drm_mode_getfb] *ERROR* invalid framebuffer id" messages. The mainline kernel 3.2.14 became unusable several times during one day with: "[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung" "[drm:kick_ring] *ERROR* Kicking stuck wait on render ring".

The framebuffer-related messages "[drm:drm_mode_getfb] *ERROR* invalid framebuffer id" do not appear after switch to a mainline kernel version 3.4. However, this kernel crashes somewhere in Intel DRM driver anyway.

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Martin Senft, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, 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 (not the daily folder, but the one all the way at the bottom) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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.12

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.