memtest86+ and lshw show wrong data about AMD Phenom II CPU

Bug #378087 reported by LAZA
2
Affects Status Importance Assigned to Milestone
lshw (Ubuntu)
New
Undecided
Unassigned
memtest86+ (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

On screen appears:

memtest86+ 2.11
Athlon 64 (0.13) 2612 MHz
L1 Cache: 64 K
L2 Cache: 512 K
L3 Cache: NONE
Memory: 8191 M
Chipset: AMD K8 (ECC: Disabled)

Mainboard: Gigabyte GA-MA790GP-UD4H F1 (now it's F3a)
RAM: 2 x 2 x 2048 MB KingstonHyperX 1066 MHz CL5
CPU: AMD Phenom II 810; 2.6 GHz; 95 W; AM3

http://products.amd.com/de-de/DesktopCPUDetail.aspx?id=526&f1=AMD+Phenom%E2%84%A2+II+X4&f2=&f3=&f4=512&f5=&f6=C2&f7=45nm+SOI&f8=&f9=&f10=False&f11=&f12=True

LAZA (laza74)
description: updated
LAZA (laza74)
description: updated
description: updated
Revision history for this message
Simon Déziel (sdeziel) wrote :

Your CPU is fairly recent. Currently Ubuntu (even the development version) is still using memtest86+ version 2.11.

If version 4.00 (ISO available here http://www.memtest.org/download/4.00/memtest86+-4.00.iso.gz) shows the right data about your CPU you should add a comment in this bug https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/435575

In the changelog of version 4.00 you have this :

- Added detection for AMD "Magny-Cours" CPU
- Corrected detection for AMD 45nm K10 CPU

Burt P. (pburt0)
summary: - shows wrong data about AMD Phenom II 810
+ memtest86+ and lshw show wrong data about AMD Phenom II CPU
Changed in memtest86+ (Ubuntu):
status: New → Confirmed
Revision history for this message
Burt P. (pburt0) wrote :

lshw also shows incorrect information about the AMD Phenom II cache:

Phenom II caches:
L1 64k data, 64k instruction
L2 512K per core
L3 6M shared

Output of lshw:
--snip--
    *-cpu:0
          description: CPU
          product: AMD Phenom(tm) II X2 550 Processor
          vendor: Advanced Micro Devices [AMD]
          physical id: 4
          bus info: cpu@0
          version: 15.4.2
          slot: Socket M2
          size: 800MHz
          capacity: 3200MHz
          width: 64 bits
          clock: 200MHz
          capabilities: boot fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 3dnowext 3dnow constant_tsc nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt cpufreq
        *-cache:0
             description: L1 cache
             physical id: a
             slot: Internal Cache
             size: 128KiB
             capacity: 128KiB
             capabilities: synchronous internal write-back
        *-cache:1
             description: L3 cache
             physical id: c
             slot: External Cache
             size: 512KiB
             capacity: 512KiB
             capabilities: synchronous internal write-back
     *-cache
          description: L1 cache
          physical id: b
          slot: Internal Cache
          size: 128KiB
          capacity: 128KiB
          capabilities: synchronous internal write-back
--snip--

Information in the /sys is correct:
:~$ cd /sys/devices/system/cpu/cpu0/cache/; cat */type */size */level
Data
Instruction
Unified
Unified
64K
64K
512K
6144K
1
1
2
3

Revision history for this message
LAZA (laza74) wrote :

Could be closed(?) cause of the corrected, updated version of memtest+in Lucid:

https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/435575

Thanks in advance!

Chris Cheney (ccheney)
Changed in memtest86+ (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Burt P. (pburt0) wrote :

The problem with lshw is not fixed in 10.04.

Revision history for this message
Burt P. (pburt0) wrote :
Revision history for this message
Savvas Radevic (medigeek) wrote :

perhaps fixed in 10.10?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.