Upgrade to 2.6.32-27 breaks Compiz

Bug #693000 reported by Philip Whateley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

(Apologies if I have not followed the correct protocol for reporting bugs - I have not had to file many reports, and would welcome feedback on improving reporting)

Upgrading to 2.6.32-27 appears to break Compositing. Restarting Ubuntu after update switches to basic graphics and Compiz cannot be restarted.

Output of compiz-check (http://forlong.blogage.de/entries/pages/Compiz-Check) is as follows:

Gathering information about your system...

Distribution: Ubuntu 10.04

Desktop environment: GNOME

Graphics chip: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)

Driver in use: vesa

Rendering method: AIGLX

Checking if it's possible to run Compiz on your system... [SKIP]

Checking for hardware/setup problems... [SKIP]

At least one check had to be skipped:

Error: vesa driver in use

Would you like to know more? (Y/n) Y

The vesa driver is not capable of running Compiz, you need to install

the proper driver for your graphics card.

Check if there's an alternate (proprietary) driver available? (Y/n) Y

Compiz was working fine with 2.6.32-26, so I assume that the correct graphics drivers are installed. Please advise if you need further information and I will provide it.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12
Uname: Linux 2.6.32-27-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
CheckboxSubmission: 7b426850a47d066cb8544d3aaa15a5cc
CheckboxSystem: 180458008578891afcb0fb9769804073
Date: Tue Dec 21 13:52:56 2010
MachineType: LENOVO 423379G
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-27-generic root=UUID=183461b9-084f-432f-91ca-5d8122be1d8b ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 12/01/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 6GET13WW(V1.04)
dmi.board.name: KIWDX
dmi.board.vendor: LENOVO
dmi.board.version: REFERENCE
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnLENOVO:bvr6GET13WW(V1.04):bd12/01/2008:svnLENOVO:pn423379G:pvrLenovo3000N500:rvnLENOVO:rnKIWDX:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: 423379G
dmi.product.version: Lenovo 3000 N500
dmi.sys.vendor: LENOVO
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-27-generic

Revision history for this message
Philip Whateley (philip-whateley) wrote :
Revision history for this message
Philip Whateley (philip-whateley) wrote :

Further to bug report above, I have tried reverting to 2.6.32-26 and then 2.6.32-27 repeatedly (only checked once before filing bug). On the third cycle, I was also able to get Compiz working on 2.6.32-27.

compiz-check now shows:

Gathering information about your system...

 Distribution: Ubuntu 10.04
 Desktop environment: GNOME
 Graphics chip: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
 Driver in use: intel
 Rendering method: AIGLX

Checking if it's possible to run Compiz on your system...

 Checking for texture_from_pixmap... [ OK ]
 Checking for non power of two support... [ OK ]
 Checking for composite extension... [ OK ]
 Checking for FBConfig... [ OK ]
 Checking for hardware/setup problems... [ OK ]

Not sure why graphics drives were not being picked up, but it looks like it's my problem - many apologies for wasting time.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :
Download full text (3.3 KiB)

[ 0.943239] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 0.943346] IP: [<ffffffff81542bdb>] __mutex_lock_slowpath+0xcb/0x180
[ 0.943424] PGD 37f6e067 PUD b6bdd067 PMD 0
[ 0.943553] Oops: 0002 [#1] SMP
[ 0.943649] last sysfs file: /sys/module/intel_agp/initstate
[ 0.943689] CPU 1
[ 0.943752] Modules linked in: i915(+) drm_kms_helper drm i2c_algo_bit intel_agp tg3(+) ahci video output .####
[ 0.944100] Pid: 296, comm: plymouthd Not tainted 2.6.32-27-generic #49-Ubuntu 423379G
[ 0.944144] RIP: 0010:[<ffffffff81542bdb>] [<ffffffff81542bdb>] __mutex_lock_slowpath+0xcb/0x180
[ 0.944220] RSP: 0018:ffff880037473d98 EFLAGS: 00010246
[ 0.944259] RAX: 0000000000000000 RBX: ffff8800b6bed408 RCX: 0000000000000006
[ 0.944300] RDX: ffff880037473da8 RSI: 0000000000000000 RDI: ffff8800b6bed40c
[ 0.944341] RBP: ffff880037473df8 R08: 0000000000000128 R09: 000000000000e200
[ 0.944383] R10: 00000000007a7bb0 R11: 0000000000000246 R12: ffff8800b9f0db80
[ 0.944424] R13: ffff8800b6bed40c R14: ffffffffffffffff R15: ffff8800b6bed410
[ 0.944466] FS: 00007fc9bba0d700(0000) GS:ffff880001d00000(0000) knlGS:0000000000000000
[ 0.944509] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.944548] CR2: 0000000000000000 CR3: 0000000037997000 CR4: 00000000000406e0
[ 0.944590] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 0.944631] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 0.944673] Process plymouthd (pid: 296, threadinfo ffff880037472000, task ffff8800b9f0db80)
[ 0.944737] Stack:
[ 0.944781] ffffffffa0081020 ffffffffa0066670 ffff8800b6bed410 0000000000000000
[ 0.944925] <0> 0000000000000000 ffffffffa0068d50 ffffea0002879998 ffff8800b6bed408
[ 0.945138] <0> ffff8800b6665840 ffff8800b6bed408 ffff8800b6bed310 ffff8800b66658e8
[ 0.945391] Call Trace:
[ 0.945452] [<ffffffffa0066670>] ? drm_version+0x0/0xb0 [drm]
[ 0.945509] [<ffffffffa0068d50>] ? drm_gem_object_release_handle+0x0/0x40 [drm]
[ 0.945573] [<ffffffff81542aeb>] mutex_lock+0x2b/0x50
[ 0.945631] [<ffffffffa00714ff>] drm_fb_release+0x2f/0xd0 [drm]
[ 0.945689] [<ffffffffa0067958>] drm_release+0x448/0x510 [drm]
[ 0.945743] [<ffffffff81144c25>] __fput+0xf5/0x210
[ 0.945793] [<ffffffff81144d65>] fput+0x25/0x30
[ 0.945844] [<ffffffff81140e5d>] filp_close+0x5d/0x90
[ 0.945894] [<ffffffff81140f47>] sys_close+0xb7/0x120
[ 0.945945] [<ffffffff810121b2>] system_call_fastpath+0x16/0x1b
[ 0.945995] Code: 4c 8d 6b 04 4c 8d 7b 08 49 c7 c6 ff ff ff ff 4c 89 ef e8 39 15 00 00 48 8b 43 10 48 8d 55 b0 48 89 53 10 4c 89 7d b0 48 89 45 b8 <48> 89 10 4c 89 f0 4c 89 65 c0 87 03 83 f8 01 75 23 eb 2b 66 90
[ 0.948057] RIP [<ffffffff81542bdb>] __mutex_lock_slowpath+0xcb/0x180
[ 0.948143] RSP <ffff880037473d98>
[ 0.948191] CR2: 0000000000000000
[ 0.948240] ---[ end trace 5129bb3a5594227d ]---

Hello
Can you please install the latest mainline kernel:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc1-lucid/linux-headers-2.6.35-020635rc1_2.6.35-020635rc1_all.deb

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc1...

Read more...

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Philip Whateley (philip-whateley) wrote : Re: [Bug 693000] Re: Upgrade to 2.6.32-27 breaks Compiz
Download full text (3.8 KiB)

On Tue, 2010-12-21 at 16:28 +0000, Fabio Marconi wrote:
> [ 0.943239] BUG: unable to handle kernel NULL pointer dereference at (null)
> [ 0.943346] IP: [<ffffffff81542bdb>] __mutex_lock_slowpath+0xcb/0x180
> [ 0.943424] PGD 37f6e067 PUD b6bdd067 PMD 0
> [ 0.943553] Oops: 0002 [#1] SMP
> [ 0.943649] last sysfs file: /sys/module/intel_agp/initstate
> [ 0.943689] CPU 1
> [ 0.943752] Modules linked in: i915(+) drm_kms_helper drm i2c_algo_bit intel_agp tg3(+) ahci video output .####
> [ 0.944100] Pid: 296, comm: plymouthd Not tainted 2.6.32-27-generic #49-Ubuntu 423379G
> [ 0.944144] RIP: 0010:[<ffffffff81542bdb>] [<ffffffff81542bdb>] __mutex_lock_slowpath+0xcb/0x180
> [ 0.944220] RSP: 0018:ffff880037473d98 EFLAGS: 00010246
> [ 0.944259] RAX: 0000000000000000 RBX: ffff8800b6bed408 RCX: 0000000000000006
> [ 0.944300] RDX: ffff880037473da8 RSI: 0000000000000000 RDI: ffff8800b6bed40c
> [ 0.944341] RBP: ffff880037473df8 R08: 0000000000000128 R09: 000000000000e200
> [ 0.944383] R10: 00000000007a7bb0 R11: 0000000000000246 R12: ffff8800b9f0db80
> [ 0.944424] R13: ffff8800b6bed40c R14: ffffffffffffffff R15: ffff8800b6bed410
> [ 0.944466] FS: 00007fc9bba0d700(0000) GS:ffff880001d00000(0000) knlGS:0000000000000000
> [ 0.944509] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 0.944548] CR2: 0000000000000000 CR3: 0000000037997000 CR4: 00000000000406e0
> [ 0.944590] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ 0.944631] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [ 0.944673] Process plymouthd (pid: 296, threadinfo ffff880037472000, task ffff8800b9f0db80)
> [ 0.944737] Stack:
> [ 0.944781] ffffffffa0081020 ffffffffa0066670 ffff8800b6bed410 0000000000000000
> [ 0.944925] <0> 0000000000000000 ffffffffa0068d50 ffffea0002879998 ffff8800b6bed408
> [ 0.945138] <0> ffff8800b6665840 ffff8800b6bed408 ffff8800b6bed310 ffff8800b66658e8
> [ 0.945391] Call Trace:
> [ 0.945452] [<ffffffffa0066670>] ? drm_version+0x0/0xb0 [drm]
> [ 0.945509] [<ffffffffa0068d50>] ? drm_gem_object_release_handle+0x0/0x40 [drm]
> [ 0.945573] [<ffffffff81542aeb>] mutex_lock+0x2b/0x50
> [ 0.945631] [<ffffffffa00714ff>] drm_fb_release+0x2f/0xd0 [drm]
> [ 0.945689] [<ffffffffa0067958>] drm_release+0x448/0x510 [drm]
> [ 0.945743] [<ffffffff81144c25>] __fput+0xf5/0x210
> [ 0.945793] [<ffffffff81144d65>] fput+0x25/0x30
> [ 0.945844] [<ffffffff81140e5d>] filp_close+0x5d/0x90
> [ 0.945894] [<ffffffff81140f47>] sys_close+0xb7/0x120
> [ 0.945945] [<ffffffff810121b2>] system_call_fastpath+0x16/0x1b
> [ 0.945995] Code: 4c 8d 6b 04 4c 8d 7b 08 49 c7 c6 ff ff ff ff 4c 89 ef e8 39 15 00 00 48 8b 43 10 48 8d 55 b0 48 89 53 10 4c 89 7d b0 48 89 45 b8 <48> 89 10 4c 89 f0 4c 89 65 c0 87 03 83 f8 01 75 23 eb 2b 66 90
> [ 0.948057] RIP [<ffffffff81542bdb>] __mutex_lock_slowpath+0xcb/0x180
> [ 0.948143] RSP <ffff880037473d98>
> [ 0.948191] CR2: 0000000000000000
> [ 0.948240] ---[ end trace 5129bb3a5594227d ]---
>
> Hello
> Can you please install the latest mainline kernel:
>
> http://kernel.ubuntu.com/~ker...

Read more...

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Philip,

If you could also please 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.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

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