Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#10545 - i686 only utilizes one core of AMD64 X2 4200+ processor

Attached to Project: Arch Linux
Opened by Trevor Hooten (marathe25) - Saturday, 31 May 2008, 06:45 GMT
Last edited by Greg (dolby) - Tuesday, 17 June 2008, 10:51 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Aaron Griffin (phrakture)
Thomas Bächler (brain0)
Architecture i686
Severity High
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: When running the i686 kernel, only one core of my AMD64X2 processor is being used, despite the fact that both are recognized as existing. The x86_64 kernel properly utilizes both cores. SMP is enabled.


Additional info:

cat /proc/cpuinfo:

processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 107
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
stepping : 2
cpu MHz : 2194.561
cache size : 512 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch ts fid vid ttp tm stc 100mhzsteps
bogomips : 4505.83
clflush size : 64



dmesg | grep -i proc:

Processor #0 15:11 APIC version 16
Processor #1 15:11 APIC version 16
Detected 2194.561 MHz processor.
Checking if this processor honours the WP bit even in supervisor mode...Ok.
CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping 02
Booting processor 1/1 ip 4000
Total of 1 processors activated (4505.83 BogoMIPS).



uname -a:

Linux homebase 2.6.25-ARCH #1 SMP PREEMPT Fri May 16 14:52:43 CEST 2008 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ AuthenticAMD GNU/Linux
This task depends upon

Closed by  Greg (dolby)
Tuesday, 17 June 2008, 10:51 GMT
Reason for closing:  Not a bug
Comment by Jan de Groot (JGC) - Saturday, 31 May 2008, 10:49 GMT
What are your hardware specs (mainboard, BIOS version, CPU socket) and can you attach a complete dmesg of your system?
Comment by Trevor Hooten (marathe25) - Sunday, 01 June 2008, 03:38 GMT
Dmesg attached.

CPU socket: AM2
Bios version: Phoenix 6.00 PG

I can't figure out a way to detect my mainboard type. My system came with zero documentation, and the manufacturer website is less than helpful. If you know of any way to detect my mainboard, I'd be happy to do it. Google failed to turn anything up for me. Thanks.
   dmesg (23.2 KiB)
Comment by Jan de Groot (JGC) - Sunday, 01 June 2008, 12:11 GMT
This is in your dmesg:
CPU #1 not responding - cannot use it.

So two CPUs are detected, but one isn't brought up because it isn't responding (BIOS or ACPI problems). Looking at the ACPI output, I found out your PC is an Acer, there's at least one more post of a user with fedora and xen that doesn't get the 2nd core working. Try googling on your specific acer model, maybe there's someone who got it working.
Comment by Faelar (Faelar) - Thursday, 12 June 2008, 11:55 GMT
AMD Athlon(tm) 64 X2 Dual Core Processor 4600+, both of the core work on Arch i686.
Comment by Glenn Matthys (RedShift) - Friday, 13 June 2008, 13:57 GMT
Check the BIOS for an option to disable core multi processing or similar options. Also search for MPS revision, make sure it is set to 1.4. In other words carefully check every BIOS setting.
Comment by Trevor Hooten (marathe25) - Saturday, 14 June 2008, 00:20 GMT
MPS revision is set to 1.4, no option to disable multi-core processing. From what I've turned up with Google, only the 4200+ is affected by this bug.
Comment by Glenn Matthys (RedShift) - Tuesday, 17 June 2008, 07:48 GMT
This is either a hardware bug or a bug in the upstream kernel. You should post this bug accordingly.

Loading...