Bug 6766

Summary:	Blender runs its SSE version by default even on systems not supporting it
Product:	Mageia	Reporter:	Julien Gouesse <gouessej>
Component:	RPM Packages	Assignee:	Funda Wang <fundawang>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	fundawang
Version:	2
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	blender-2.63a-1.1.mga2.src.rpm	CVE:
Status comment:

Description Julien Gouesse 2012-07-12 19:27:58 CEST

Description of problem:
Blender cannot be run. /usr/bin/blender runs /usr/bin/blender.sse even on machines not supporting it. My microprocessor is an AMD Sempron 2600+. /usr/bin/blender.nonsse works on mine.

Version-Release number of selected component (if applicable):
2.63a

How reproducible:
Always

Steps to Reproduce:
1. Install the package blender-2.63a-1.1.mga2.i586.rpm
2. Run Blender in command line: /usr/bin/blender
3. The following message appears: /usr/bin/blender : ligne 9 : 10528 Instruction not allowed /usr/bin/blender.sse "$@"

Manuel Hiebel 2012-10-07 11:52:10 CEST

CC: (none) => fundawang
Assignee: bugsquad => dmorganec

Comment 1 Funda Wang 2012-10-07 14:40:31 CEST

What is your output of this command?

cat /proc/cpuinfo

Status: NEW => ASSIGNED
Assignee: dmorganec => fundawang

Comment 2 Julien Gouesse 2012-10-07 17:14:36 CEST

My former computer returned something really similar to that:
http://openbenchmarking.org/system/1103134-IV-1103138IV84/Comparing%20AMD%20Sempron%20to%20Core%202%20Duo/cpuinfo

It uses an AMD Sempron 2600+.

Comment 3 Funda Wang 2012-10-07 23:04:44 CEST

Please note that there are 'sse sse2' in flag list, so we are correct selecting sse flavor of blender.

And, AMD do have two different flavor of Sempron 2600+, looking from wikipedia[1]. One of them supports SSE2, and the other does not. I'm thinking you are now using Socket A family rather than Socket 754. Is it true?

[1]: http://en.wikipedia.org/wiki/List_of_AMD_Sempron_microprocessors

Comment 4 Funda Wang 2013-04-25 04:55:37 CEST

ping?

Comment 5 Manuel Hiebel 2013-10-22 12:09:55 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Comment 6 Manuel Hiebel 2013-11-23 16:13:32 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: ASSIGNED => RESOLVED
Resolution: (none) => OLD