Hello Franz, or anyone else affected, Accepted intel-gpu-tools into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/intel-gpu- tools/1.3-0ubuntu2.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: intel-gpu-tools (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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: Fix Committed 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
