Weird build errors only on 3rd core of quad core CPU
Pieter de Goeje
pieter at degoeje.nl
Thu Jan 28 01:48:06 UTC 2010
On Thursday 28 January 2010 01:54:01 Erich Dollansky wrote:
> On 28 January 2010 am 06:54:13 Pieter de Goeje wrote:
> > I am suspecting a broken CPU, but am not sure.
> it really looks like.
> Are you sure it is a quad core and not just a triple core?
It definitely identifies itself as a quadcore in dmesg (the text matches what
it said on the box): AMD Athlon(tm) II X4 620. I don't think the hacks which
activate the 4th core on a triple core can alter that information.
CPU: AMD Athlon(tm) II X4 620 Processor (2600.02-MHz K8-class CPU)
Origin = "AuthenticAMD" Id = 0x100f52 Stepping = 2
TSC: P-state invariant
real memory = 2147483648 (2048 MB)
avail memory = 1795858432 (1712 MB)
ACPI APIC Table: <120909 APIC1901>
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
cpu2 (AP): APIC ID: 2
cpu3 (AP): APIC ID: 3
> As already mentioned, you should check the stepping the software
> tells you but also what is actually written onto the CPU itself.
> Try to get the CPU exchanged and see what happens then.
I suppose that's the only way... hopefully I can convince the shop I bought it
from that it is broken.
> > These commands:
> > cd /usr/ports/sysutils/hal
> > cpuset -c -l 2 make
> > Will always result in errors, for example this one:
> > gmake: *** No rule to make target `@MAINTAINER_MODE_TRUE@',
> > needed by `config.h.in'. Stop.
> > *** Error code 1
> > Sometimes the error occurs in a different place. When I check
> > the input files, they are indeed broken. Gcc stops because of
> > syntax errors for example.
> > The configure process always completes, but apparently it
> > creates broken files. When I run make on any other core, it
> > always completes successfully: cpuset -c -l 0,1,3 make
> > I've checked with script that the output of the build process
> > is exactly the same, up until the error occurs. I've also tried
> > to run cpuburn on that core, but it didn't find any problem.
> > It's really weird that system is otherwise very stable.
> > What do you guys think the problem is?
> > CPU is AMD Athlon II X4 620. Running FreeBSD 8-STABLE/amd64.
> > I've also tried -CURRENT, but it didn't help.
> > Thanks!
> > --
> > Pieter
> > _______________________________________________
> > freebsd-questions at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to
> > "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions