kernel-packages team mailing list archive

[Launchpad Bug Tracker <1316454@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package intel-gpu-tools - 1.3-0ubuntu2.1

---------------
intel-gpu-tools (1.3-0ubuntu2.1) trusty-proposed; urgency=medium

  * dont-abort-regdumper.diff: No need to abort() on unsupported systems.
    (LP: #1316454)
 -- Timo Aaltonen <tjaalton@xxxxxxxxxx>   Tue, 24 Jun 2014 13:15:46 +0300

** Changed in: intel-gpu-tools (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1316454

Title:
  intel_reg_dumper crashed with SIGABRT in __libc_start_main()

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  Fix Committed
Status in “intel-gpu-tools” package in Ubuntu:
  Fix Released
Status in “intel-gpu-tools” source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  An error dialog will be shown after user login to the desktop environment.
  The error is :

  The intel_reg_dumper raise SIGABRT on Intel ValleyView Gen7
  [8086:0f31] platform.

  Bumping intel-gpu-tools to 1.7 as SRU is unrealistic, and backporting
  new hw support didn't fix it, so the easiest way to work around this
  issue is to not abort() when it fails to detect the chip gen related
  register maps. This should prevent core dumps and the crash reports.

  [Test Case]
  This issue can be reproduced by running the command:

  # sudo intel_reg_dumper
  Gen2/3 Ranges are not supported. Please use unsafe access. (Core dump)

  [Regression potential]
  None really, it just won't dump core which hardly anything relies on..

  
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-05-02 (0 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140502-08:19

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1316454/+subscriptions