[i945] [maverick] upgrade from lucid to maverick then Xorg freeze after enabling compiz

[Mahyuddin Susanto]

Hello, my laptop is Compaq Presario CQ42-102TU. Using Intel as Chipset

The story begin when i upgrade my laptop from lucid to maverick, everything is okay under lucid but many error while running maverick. 3D acceleration cannot enabled, so i can't enabled compiz, and can't running stellarium

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
DRM.card0.DisplayPort.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.DisplayPort.2:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1366x768
 edid-base64: AP///////wAw5FECAAAAAAATAQOAHxF4CmsVl1lWjCgeUFQAAAABAQEBAQEBAQEBAQEBAQEBEhtWeFAADjAgIDUANq4QAAAZAAAAAAAAAAAAAAAAAAAAAAAAAAAA/gBMRyBEaXNwbGF5CiAgAAAA/gBMUDE0MFdIMS1UTEMzAOw=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Mon Nov 22 04:29:54 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Hewlett-Packard Presario CQ42 Notebook PC
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=a93b9d1d-30e6-49e4-b06a-cb1e3f98a067 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
dmi.bios.date: 01/18/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.04
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1484
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 77.05
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd01/18/2010:svnHewlett-Packard:pnPresarioCQ42NotebookPC:pvr04A0100000002810000000000:rvnHewlett-Packard:rn1484:rvr77.05:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: Presario CQ42 Notebook PC
dmi.product.version: 04A0100000002810000000000
dmi.sys.vendor: Hewlett-Packard
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-22-generic

[Mahyuddin Susanto (udienz)]

update package

[Bryce Harrington (bryce)]

Hi,

Thanks for reporting this X gpu lockup bug in Ubuntu maverick.

In my opinion GPU lockups are one of the most frustrating kinds of bugs, both as a user and a developer. I want take a few moments of your time to explain the situation with these types of bugs.

For some reason, -intel has been plagued with these freeze bugs for a long time. In the past -intel has had options to switch to legacy memory or rendering technologies as workarounds, but Intel tends to drop obsolete code pretty aggressively and unfortunately in maverick these workarounds are not available.

As a policy, Intel engineers look only at bugs that are seen in the most recent release of their drivers. With older versions of their drivers, such as the version in maverick, we're on our own.

On the plus side, they provide good tools for gathering debug data about the bugs, such as the intel_gpu_dump too. Unfortunately, the version of Apport in maverick doesn't capture the dmesg or X logs correctly (it collects the files at the time of freeze, but then overwrites them with clean, unhelpful versions when it goes to file the report for you.)

The version of these diagnostic tools in natty has been fixed up, and is allowing us to analyze GPU lockups a lot easier. This has helped us solve several of the bugs, and given us a handle on some of the more challenging ones.

Backporting these fixes may not be feasible though; by their nature the fixes for these type of bugs tend to be very low level, esoteric, and risky of causing something else to regress. Because the freezes are often hard to reproduce, it's not always possible to verify fixes anyway. It may be that our best bet is to focus on natty.

But for now, since these freezes typically require kernel patches to solve, I'm moving your bug report to the kernel package. They may be able to point you to a newer kernel likely to help with this issue.

[Jeremy Foshee (jeremyfoshee)]

Hi Mahyuddin,

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.]

[Launchpad Janitor (janitor)]

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