kernel BUG at /build/buildd/linux-3.2.0/drivers/gpu/drm/i915/i915_gem.c:1952!

Bug #960692 reported by Markus Mueller
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

it died when I opened the display of my notebook while it was still in the docking station

ProblemType: KernelOops
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-19-generic
Uname: Linux 3.2.0-19-generic x86_64
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
Date: Tue Mar 20 23:53:36 2012
Failure: oops
SourcePackage: linux
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mmu 2313 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2920000 irq 49'
   Mixer name : 'Conexant CX20561 (Hermosa)'
   Components : 'HDA:14f15051,17aa20ff,00100000'
   Controls : 20
   Simple ctrls : 12
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7XHT24WW-1.06'
   Mixer name : 'ThinkPad EC 7XHT24WW-1.06'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
CurrentDmesg: [ 125.500811] init: plymouth-stop pre-start process (3132) terminated with status 1
DistroRelease: Ubuntu 12.04
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
MachineType: LENOVO 74663RG
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-19-generic root=UUID=df8e9771-d8e0-4461-9987-4768dd769b43 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-19-generic N/A
 linux-backports-modules-3.2.0-19-generic N/A
 linux-firmware 1.71
StagingDrivers: mei
Tags: precise staging
Uname: Linux 3.2.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
dmi.bios.date: 03/10/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET63WW (3.13 )
dmi.board.name: 74663RG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6DET63WW(3.13):bd03/10/2010:svnLENOVO:pn74663RG:pvrThinkPadX200s:rvnLENOVO:rn74663RG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 74663RG
dmi.product.version: ThinkPad X200s
dmi.sys.vendor: LENOVO

Revision history for this message
Markus Mueller (mmu) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 960692

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: precise
Revision history for this message
Markus Mueller (mmu) wrote : AcpiTables.txt

apport information

tags: added: apport-collected staging
description: updated
Revision history for this message
Markus Mueller (mmu) wrote : AlsaDevices.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : BootDmesg.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : CRDA.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : IwConfig.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : Lspci.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : Lsusb.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : PciMultimedia.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : ProcModules.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : PulseList.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : RfKill.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : UdevDb.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : UdevLog.txt

apport information

Revision history for this message
Markus Mueller (mmu) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Luis Henriques (henrix) wrote :

Apparentely, this is very similar to bug #903010, which is now solved by reverting commit eb1711bb94991e93669c5a1b5f84f11be2d51ea1.

Unfortunately, the oopstext seems to be incomplete and misses useful information. Can you reproduce this issue? If so, could you please send again the log?

Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-19.31)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-19.31
Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: i915-wait-request
Revision history for this message
Markus Mueller (mmu) wrote :

The oopstext somehow got messed up. I got the complete one with the call trace from syslog, but I was not yet able to reproduce the bug.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Luis Henriques (henrix) wrote :

Thank you for the update.

Are you able to reproduce this issue? If so, it would be great if you could test the latest mainline kernel to check if the issue is still present there. Please refer to https://wiki.ubuntu.com/KernelMainlineBuilds for details on how to run mainline kernels.

Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-20.32)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-20.32
Revision history for this message
Luis Henriques (henrix) wrote :

Marking this bug as a duplicated of bug #903010, which is "Fix Released".

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.