intel_reg_dumper crashed with SIGABRT in __libc_start_main()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OEM Priority Project |
Fix Released
|
High
|
Ara Pulido | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned | ||
intel-gpu-tools (Ubuntu) |
Fix Released
|
Undecided
|
Timo Aaltonen | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned |
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
Related branches
Changed in oem-priority: | |
importance: | Undecided → High |
description: | updated |
description: | updated |
description: | updated |
Changed in oem-priority: | |
assignee: | nobody → Ara Pulido (apulido) |
description: | updated |
Changed in oem-priority: | |
status: | New → In Progress |
Changed in oem-priority: | |
status: | In Progress → Fix Released |
The intel_reg_dump of intel-gpu-tools v1.6 works fine.