stack trace from the i915 module - i915_gem_retire_requests

Bug #337451 reported by Ken VanDine
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Xorg hung when the module crashed with the following output in the messages log:

Mar 3 09:15:12 trabajo kernel: [71050.935467] Modules linked in: binfmt_misc i915 drm bridge stp bnep vboxnetflt vboxdrv input_polldev video output ppdev parport_pc lp parport dcdbas serio_raw psmouse pcspkr iTCO_wdt iTCO_vendor_support snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device usblp snd soundcore snd_page_alloc intel_agp agpgart usbhid e1000 ehci_hcd uhci_hcd e1000e fbcon tileblit font bitblit softcursor fuse
Mar 3 09:15:12 trabajo kernel: [71050.935519] Pid: 4879, comm: Xorg Tainted: G W 2.6.28-8-generic #26-Ubuntu
Mar 3 09:15:12 trabajo kernel: [71050.935521] Call Trace:
Mar 3 09:15:12 trabajo kernel: [71050.935530] [<c04e9111>] ? printk+0x18/0x1f
Mar 3 09:15:12 trabajo kernel: [71050.935535] [<c0139ae4>] warn_on_slowpath+0x54/0x80
Mar 3 09:15:12 trabajo kernel: [71050.935548] [<f7fb1594>] ? drm_gem_object_free+0x44/0x50 [drm]
Mar 3 09:15:12 trabajo kernel: [71050.935557] [<f7fb1550>] ? drm_gem_object_free+0x0/0x50 [drm]
Mar 3 09:15:12 trabajo kernel: [71050.935561] [<c02beb3d>] ? kref_put+0x2d/0x70
Mar 3 09:15:12 trabajo kernel: [71050.935567] [<f81ba629>] ? i915_gem_retire_requests+0xf9/0x150 [i915]
Mar 3 09:15:12 trabajo kernel: [71050.935574] [<f81ba629>] ? i915_gem_retire_requests+0xf9/0x150 [i915]
Mar 3 09:15:12 trabajo kernel: [71050.935580] [<f81bc6f8>] i915_gem_idle+0x3a8/0x3d0 [i915]
Mar 3 09:15:12 trabajo kernel: [71050.935587] [<f81bc764>] i915_gem_leavevt_ioctl+0x14/0x30 [i915]
Mar 3 09:15:12 trabajo kernel: [71050.935596] [<f7fb01f0>] drm_ioctl+0xe0/0x2e0 [drm]
Mar 3 09:15:12 trabajo kernel: [71050.935603] [<f81bc750>] ? i915_gem_leavevt_ioctl+0x0/0x30 [i915]
Mar 3 09:15:12 trabajo kernel: [71050.935609] [<c01c9fc9>] vfs_ioctl+0x79/0x90
Mar 3 09:15:12 trabajo kernel: [71050.935613] [<c01ca45e>] do_vfs_ioctl+0x5e/0x200
Mar 3 09:15:12 trabajo kernel: [71050.935616] [<c01ca663>] sys_ioctl+0x63/0x70
Mar 3 09:15:12 trabajo kernel: [71050.935620] [<c0103f6b>] sysenter_do_call+0x12/0x2f
Mar 3 09:15:12 trabajo kernel: [71050.935623] ---[ end trace 6cc9e9606af0a855 ]---

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
MachineType: Dell Inc. Dell DM061
Package: linux-image-2.6.28-8-generic 2.6.28-8.26
ProcCmdLine: root=UUID=e702e6ae-c74d-4bea-aee3-9968baa0b06f ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-8.26-generic
SourcePackage: linux

Revision history for this message
Ken VanDine (ken-vandine) wrote :
Revision history for this message
Ken VanDine (ken-vandine) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Ken,

Just curious how reproducible this is to trigger? The reason I ask is I see you are running the latest 2.6.28-8 Jaunty kernel. It would be really great if you could test and confirm if this exists with the latest 2.6.29-rc6 upstream mainline kernel as well. We've provided mainline kernel builds to help make testing the upstream kernel easier. Please refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Knowing if this issue exists upstream or not would be extremely useful so we could try to narrow down a fix to pull in from upstream, narrow down if this is an ubuntu specific change we should be looking for, or knowing if this is something we should notify the upstream developers about as well. So please let us know your results. Thanks in advance.

Changed in linux:
status: New → Incomplete
Revision history for this message
Ken VanDine (ken-vandine) wrote :

I will try. It isn't reliably reproducible, however I have had 3 crashes in since yesterday afternoon. Prior to that, it was rock solid, not sure what has triggered it. I will wait for another crash before I install the mainline kernel, just to be confident it will happen again.

Revision history for this message
Alex Denvir (coldfff) wrote :

We are closing this bug report because it has not been updated for some time. Please reopen it if you have more information to submit, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.