From owner-freebsd-questions@FreeBSD.ORG Thu Jan 28 01:48:06 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B944106568B for ; Thu, 28 Jan 2010 01:48:06 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from mx.utwente.nl (mx3.utsp.utwente.nl [130.89.2.14]) by mx1.freebsd.org (Postfix) with ESMTP id C5E6F8FC17 for ; Thu, 28 Jan 2010 01:48:05 +0000 (UTC) Received: from nox.student.utwente.nl (nox.student.utwente.nl [130.89.165.91]) by mx.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id o0S1lwHH008058; Thu, 28 Jan 2010 02:47:59 +0100 From: Pieter de Goeje To: Erich Dollansky Date: Thu, 28 Jan 2010 02:47:58 +0100 User-Agent: KMail/1.9.10 References: <201001272354.14384.pieter@degoeje.nl> <201001280854.03215.erich@ovitrap.com> In-Reply-To: <201001280854.03215.erich@ovitrap.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201001280247.58686.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact icts.servicedesk@utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-SpamScore: s X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: freebsd-questions@freebsd.org Subject: Re: Weird build errors only on 3rd core of quad core CPU X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2010 01:48:06 -0000 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=0x178bfbff Features2=0x802009 AMD Features=0xee500800 AMD Features2=0x37ff 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-unsubscribe@freebsd.org"