Weird build errors only on 3rd core of quad core CPU
I am suspecting a broken CPU, but am not sure. 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Weird build errors only on 3rd core of quad core CPU
Pieter de Goeje wrote: I am suspecting a broken CPU, but am not sure. 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. As a test I just ran these two commands on my Athlon II 630 here, but running FreeBSD 8.0-RELEASE-p2 amd64 build. The make process ran directly to completion with no error. With overclocking too. Tried 4 runs, on each core. I'm not sure I recall all the details correctly without checking, but I thought there were some early samples or generations of these processors that were not the same as the final production releases. Something to do with being Phenom cores that had L3 cache disabled, being released as early engineering samples but the die of the final products is different with no L3 cache present from manufacturing. I'd check into the stepping and if it turns out not to be a final version get whoever you bought it from to replace it. It may not be the core itself, but bad L1/L2 cache. It's either that or the only other difference is you're running stable, and I'm not. But I'd suspect bad cache spots in L1/L2. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Weird build errors only on 3rd core of quad core CPU
Hi, 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? 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. Erich 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Weird build errors only on 3rd core of quad core CPU
On Thursday 28 January 2010 01:54:01 Erich Dollansky wrote: Hi, 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 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA, CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x802009SSE3,MON,CX16,POPCNT AMD Features=0xee500800SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM, 3DNow!+,3DNow! AMD Features2=0x37ffLAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch, OSVW,IBS,SKINIT,WDT 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. Erich 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
