kernel-packages team mailing list archive

[Chris J Arges <1316454@xxxxxxxxxxxxxxxxxx>]

Hi Timo, can you update the bug description with the SRU template? Also I'd like to know why removing the abort() call makes sense, because in the 1.7-1 version that call is still present. Is the abort() call the right way to handle that code path?
Thanks,

-- 
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:
  New
Status in OEM Priority Project trusty series:
  New
Status in “intel-gpu-tools” package in Ubuntu:
  Fix Released
Status in “intel-gpu-tools” source package in Trusty:
  In Progress

Bug description:
  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.

  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)

  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