Bug 491817 - Flag sse3 missing in /proc/cpuinfo for Opteron 146, socket 939
Summary: Flag sse3 missing in /proc/cpuinfo for Opteron 146, socket 939
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 10
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-24 08:48 UTC by Joachim Frieben
Modified: 2009-03-24 20:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-24 20:37:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Content of /proc/cpuinfo for Opteron 146, socket 939. (560 bytes, text/plain)
2009-03-24 08:48 UTC, Joachim Frieben
no flags Details
Output of x86info for Opteron 146, socket 939. (583 bytes, text/plain)
2009-03-24 08:49 UTC, Joachim Frieben
no flags Details

Description Joachim Frieben 2009-03-24 08:48:22 UTC
Created attachment 336429 [details]
Content of /proc/cpuinfo for Opteron 146, socket 939.

Description of problem:
File /proc/cpuinfo only displays SSE related flags sse and sse2 for an Opteron 146, socket 939. I believe that no stepping earlier than E4 was available for socket 939. Thus I would expect sse3 to be supported,too.

Version-Release number of selected component (if applicable):
kernel-2.6.29-0.67.rc8.git4.fc10.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Cat /proc/cpuinfo.
  
Actual results:
Capabilities sse and sse2 are reported.

Expected results:
Flag sse3 is returned, too.

Additional info:
Utility x86info actually reports the processor being an "Opteron/Athlon 64/Athlon 64 FX (SH-E4)", and feature flags also includes sse3.

Comment 1 Joachim Frieben 2009-03-24 08:49:40 UTC
Created attachment 336430 [details]
Output of x86info for Opteron 146, socket 939.

Comment 2 Chuck Ebbert 2009-03-24 20:37:12 UTC
sse3 is called pni in linux for historical reasons.


Note You need to log in before you can comment on or make changes to this bug.