[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-07-04 Thread Ara Pulido
** Changed in: oem-priority
   Status: In Progress = Fix Released

** Changed in: oem-priority/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:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
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

-- 
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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-07-03 Thread Franz Hsieh
I have installed and verified the intel-gpu-tools 1.3-0ubuntu2.1 on
target machine, the issue is fixed.

-- 
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 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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-07-03 Thread Launchpad Bug Tracker
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 tjaal...@ubuntu.com   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

-- 
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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-07-02 Thread Ara Pulido
** Changed in: oem-priority/trusty
   Status: New = Fix Committed

** Changed in: oem-priority
   Status: New = In Progress

-- 
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 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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-07-02 Thread Timo Aaltonen
works for me, marked verification-done

** Tags removed: verification-needed
** Tags added: verification-done

-- 
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 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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-06-25 Thread Timo Aaltonen
** Description changed:

+ [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

-- 
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:
  [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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-06-25 Thread Chris J Arges
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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-06-25 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-branches/ubuntu/trusty/intel-gpu-tools
/trusty-proposed

-- 
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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-06-24 Thread Timo Aaltonen
Yes, I've just uploaded a version to trusty-proposed that makes intel-
reg-dumper not abort() when it checks the supported register map. That
should prevent crashes which is all that can be backported..

** Changed in: intel-gpu-tools (Ubuntu Trusty)
   Status: Triaged = In Progress

-- 
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

-- 
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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-06-24 Thread Chris J Arges
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

-- 
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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-06-20 Thread Ara Pulido
** Also affects: oem-priority/trusty
   Importance: Undecided
   Status: New

-- 
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:
  Triaged

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

-- 
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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-06-18 Thread Timo Aaltonen
fixed in utopic

** Also affects: intel-gpu-tools (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: intel-gpu-tools (Ubuntu Trusty)
   Status: New = Triaged

** Changed in: intel-gpu-tools (Ubuntu)
   Status: Triaged = 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:
  New
Status in “intel-gpu-tools” package in Ubuntu:
  Fix Released
Status in “intel-gpu-tools” source package in Trusty:
  Triaged

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

-- 
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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-06-18 Thread Franz Hsieh
@Timo

Will it be back ported to trusty?

-- 
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 “intel-gpu-tools” package in Ubuntu:
  Fix Released
Status in “intel-gpu-tools” source package in Trusty:
  Triaged

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

-- 
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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-05-15 Thread Timo Aaltonen
I can reproduce it on broadwell and valleyview (baytrail)

** Changed in: intel-gpu-tools (Ubuntu)
   Status: New = Triaged

** Changed in: intel-gpu-tools (Ubuntu)
 Assignee: (unassigned) = Timo Aaltonen (tjaalton)

-- 
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 “intel-gpu-tools” package in Ubuntu:
  Triaged

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

-- 
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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-05-14 Thread Franz Hsieh
** Description changed:

  The intel_reg_dumper raise SIGABRT on Intel ValleyView Gen7 [8086:0f31]
  platform.
  
  # sudo intel_reg_dumper
  Gen2/3 Ranges are not supported. Please use unsafe access. (Core dump)
+ 
+ OS version: Ubuntu 14.04 LTS (Trusty)

** Description changed:

  The intel_reg_dumper raise SIGABRT on Intel ValleyView Gen7 [8086:0f31]
  platform.
  
  # sudo intel_reg_dumper
  Gen2/3 Ranges are not supported. Please use unsafe access. (Core dump)
  
- OS version: Ubuntu 14.04 LTS (Trusty)
+ 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

-- 
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 “intel-gpu-tools” package in Ubuntu:
  New

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

-- 
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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-05-14 Thread Ara Pulido
** Changed in: oem-priority
 Assignee: (unassigned) = Ara Pulido (apulido)

-- 
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 “intel-gpu-tools” package in Ubuntu:
  New

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

-- 
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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-05-14 Thread Franz Hsieh
** Description changed:

+ 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

-- 
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 “intel-gpu-tools” package in Ubuntu:
  New

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

-- 
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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-05-14 Thread Franz Hsieh
Attach error dialog snapshot.

** Attachment added: intel_reg_dump_error_message.jpg
   
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1316454/+attachment/4112042/+files/intel_reg_dump_error_message.jpg

-- 
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 “intel-gpu-tools” package in Ubuntu:
  New

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

-- 
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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-05-08 Thread Franz Hsieh
** Changed in: oem-priority
   Importance: Undecided = High

-- 
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 “intel-gpu-tools” package in Ubuntu:
  New

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

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

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


[Kernel-packages] [Bug 1316454] Re: intel_reg_dumper crashed with SIGABRT in __libc_start_main()

2014-05-06 Thread Franz Hsieh
The intel_reg_dump of intel-gpu-tools v1.6 works fine.

** Also affects: xserver-xorg-video-intel
   Importance: Undecided
   Status: New

** Project changed: xserver-xorg-video-intel = oem-priority

-- 
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 “intel-gpu-tools” package in Ubuntu:
  New

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

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

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