desktop-packages team mailing list archive

[Jamie Jackson <1388612@xxxxxxxxxxxxxxxxxx>]

(In reply to Alex from comment #100)
> Jamie Jackson, having read you issue with www.google.com/chrome, I've
> visited the site at least 10 times using Chrome after yesterday's updates
> and all went just fine.  Are you facing the same issue when you're using
> chrome or is it a firefox issue only?

Not sure if the Chrome/YouTube still persisted after that, because that
was intermittent--I never had a 100% reliable Chrome test case, which is
why I was using the reliable Firefox case.

(In reply to Ryan Underwood from comment #101)
> Jamie, your uname -a output indicates that you haven't installed a kernel
> that contains the other part of the fix.
> Go here: http://kernel.ubuntu.com/~kernel-ppa/mainline/
> Pick a kernel >= v3.19-rc1 and install the proper debs.  Then make sure you
> choose that kernel at your bootloader.

Thanks for putting the pieces together for me, Ryan. I seem to have
success now. (My package management is probably pretty weird as a
result, but I'm going to ignore that.)

For the other n00bs, here was the final piece:

mkdir -p /tmp/kernel && cd /tmp/kernel
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-rc5-vivid/linux-image-3.19.0-031900rc5-generic_3.19.0-031900rc5.201501180935_amd64.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-rc5-vivid/linux-headers-3.19.0-031900rc5_3.19.0-031900rc5.201501180935_all.deb
sudo dkpg -i linux-image*
# In truth, I did this next one in GDebi, after I ran 
# into a problem that "sudo apt-get install -f" fixed
sudo dpkg -i linux-headers*
sudo reboot

uname -a # yields:Linux minty 3.19.0-031900rc5-generic #201501180935 SMP Sun Jan 18 09:36:49 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
# try firefox test case
firefox http://www.google.com/chrome/

=== Yields a black blip, but it recovers! and the followng output ===
(process:3038): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

(firefox:3038): GLib-GObject-WARNING **: Attempt to add property
GnomeProgram::sm-connect after class was initialised

(firefox:3038): GLib-GObject-WARNING **: Attempt to add property
GnomeProgram::show-crash-dialog after class was initialised

(firefox:3038): GLib-GObject-WARNING **: Attempt to add property
GnomeProgram::display after class was initialised

(firefox:3038): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised
ATTENTION: default value of option force_s3tc_enable overridden by environment.
======================================================================

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1388612

Title:
  [GM965] GPU lockup running OpenGL applications on Dell Vostro 1510

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  In Progress

Bug description:
  Hello, I'm suffering a GPU lockup problem with Ubuntu 14.10 64-bit on
  a Dell Vostro 1510 laptop with Intel graphics. The problem used to
  arise also with Ubuntu 14.04 and is always reproducible with glmark2
  on the LiveCD. Just to run the "ideas" benchmark of glmark2 to trigger
  the lockup in few seconds (glmark2 -b ideas). Other OpenGL
  applications also causes the lockup (e.g. FooBillard++, my self-made
  SDL applications). Memory test passed, BIOS at the latest version.
  Don't know if the following is a good point but I think that the
  problem is not caused by a failing hardware because it works fine on
  Windows. I tried with the latest Intel upstream kernel
  (http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-
  next/current/) and upstream X.org (https://launchpad.net/~xorg-
  edgers/+archive/ubuntu/ppa), no change.

  [Personal Notes]
  I'm new to Ubuntu's world, I hope I've done things right, if not please tell me and I will resend the report or supply more information. I've created the bug report with "ubuntu-bug xorg --save" from another machine via SSH while the sick machine was frozen. It seemed to me more logical than using ubuntu-bug directly when the system is working fine. I've collected other information via SSH during the same lockup: dmesg, Xorg.0.log, i915_error_state. The latter was added as attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Nov  2 19:24:31 2014
  DistUpgraded: 2014-10-25 12:05:51,479 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.13.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.16.0-23-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.16.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:0273]
     Subsystem: Dell Device [1028:0273]
  InstallationDate: Installed on 2014-10-11 (22 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
  MachineType: Dell Inc. Vostro1510
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=9b3612b7-c4bf-4840-885b-9fae75d6342c ro splash quiet vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (8 days ago)
  dmi.bios.date: 03/18/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0M277C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnDellInc.:bvrA15:bd03/18/2009:svnDellInc.:pnVostro1510:pvrNull:rvnDellInc.:rn0M277C:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro1510
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
  xserver.bootTime: Sun Nov  2 18:41:51 2014
  xserver.configfile: default
  xserver.errors:
   intel(0): Detected a hung GPU, disabling acceleration.
   intel(0): When reporting this, please include /sys/class/drm/card0/error and the full dmesg.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id                               15873 
   vendor                                     LPL
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1388612/+subscriptions