[Compaq Presario V6613TU Notebook PC] Xorg crash

[m]

Clicking on some links while using Chromium Browser causes Xorg to crash

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-40.68~precise1-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic i686
.tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
CompizPlugins: [core,composite,opengl,decor,compiztoolbox,gnomecompat,imgpng,workarounds,resize,place,grid,move,regex,shift,mousepoll,unitymtgrabhandles,switcher,vpswitch,session,wall,wobbly,scale,expo]
CompositorRunning: None
Date: Thu Nov 20 12:46:17 2014
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes,
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:30cc]
   Subsystem: Hewlett-Packard Company Device [103c:30cc]
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
MachineType: Hewlett-Packard Presario V6500 Notebook PC
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=8fd0ae1b-f68f-46d7-91a9-7fc0a6f0bd1e ro splash vga=789 nomodset quiet splash resume=UUID=594e6e91-23cc-42cb-aae0-fda5a355f215 acpi_osi=Linux pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.5A
dmi.board.name: 30CC
dmi.board.vendor: Quanta
dmi.board.version: 79.2E
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.5A:bd03/22/2010:svnHewlett-Packard:pnPresarioV6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.2E:cvnQuanta:ct10:cvrN/A:
dmi.product.name: Presario V6500 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.7.12-0ubuntu4
version.libdrm2: libdrm2 2.4.52-1~precise1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

[m (anonymouser)]

The specific model is Compaq Presario V6613TU, but the general product is Presario V6500. Product number is KB092PA#ABG.

Here is a link to the product page: http://h10025.www1.hp.com/ewfrf/wc/manualCategory?cc=us&dlc=en&lc=en&product=3593126&

[penalvch (penalvch)]

m, could you please comment on if you return the kernel boot parameters to the default by removing:
acpi_osi=Linux pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 nomodeset

does this change anything?

As well, could you please advise on why each of these are in use?

[m (anonymouser)]

I will try tonight; I can not reboot now.

I'm not sure about all of the boot parameters, actually. There were problems some time back with font corruption and desktop background corruption as well as problems with power management which I tried to solve before by setting boot parameters. I'm happy to try without them but I've noticed that it's becoming more difficult to reproduce the bug consistently lately. It may take some time to report back.

Thanks for your help.

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[m (anonymouser)]

apport information

[penalvch (penalvch)]

m, just to clarify you don't have to apport-collect further unless specifically asked to do so.

[m (anonymouser)]

I see. I thought there might be new or different information since this occurred without without the boot parameters you asked about.

It's more difficult to trigger the bug now, so something has changed. I used to reload the crashed Chromium session and since the page that caused the crash would be reloaded, it would occur again as soon as the page loaded. However, I've just rebooted and restarted Chromium with the pages that caused the crash and everything works fine. It's kind of random now; I thought it had been fixed in a recent update that included some intel/vesa packages, but I guess not.

Let me know if you need me to check anything else. Thanks for your help.

[m (anonymouser)]

actually, I can reproduce it. I just had to scroll down far enough so that the troublesome page made an ajax call to load more content then the GPU hung again.

[penalvch (penalvch)]

m, to see if this is fixed already in a later version, could you please test for this in a live environment via http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

[m (anonymouser)]

I'm downloading it now and will get back to you. I've tried the same steps three times in Chrome and the GPU always hangs. I've done it twice in Firefox now without any problems. There are also no problems in Chrome on Arch Linux.

[m (anonymouser)]

Out of frustration with losing work at random times when using Chromium, I have decided to to disable video acceleration options in Chromium and upgrad to 14.04 LTS. This appears to have resolved the GPU hang issue, but it is very frustrating that this appeared at all. I was staying with 12.04 LTS because, as the name implies, it is supposed to be stable. For some reason, one of the updates made it very unstable.

also, this is most likely a duplicate. There are many reports of Chromium causing GPU hangs:

https://bugs.freedesktop.org/show_bug.cgi?id=80568
http://blogs.fsfe.org/the_unconventional/2014/11/12/debian-x-drivers/

Thanks for your help, @penalvch, but I think it's a much bigger issue and I don't have enough time to fully look into it.

[penalvch (penalvch)]

m, stating there are "many reports of Chromium causing GPU hangs" is unfortunately too vague to be actionable, and not how bug reports work here on Launchpad, as further documented in https://wiki.ubuntu.com/ReportingBugs . Despite this, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1394424/comments/31 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[m (anonymouser)]

@penalvch the link I provided at freedesktop.org appears to be the cannonical bug reference and the second one describes the same problem I was experiencing with a lot more detail and links to related discussions on dev lists. Both links provide more detailed information than I ever could.

Also, I left it open because it's a bug related to an LTS which is why I filed the bug report. It appears that many people are experiencing it and since there are so many different bug reports for the same symptoms, including on Launchpad, it might be useful to leave it open until it is marked as a duplicate of whatever report becomes canonical.

But anyway, thanks again for your help. I do appreciate it and I'm sorry I don't have more time to help track down the source. I don't have enough time at the moment and based on the links I provided, others are already looking at it very deeply.