From owner-freebsd-questions@FreeBSD.ORG Thu Nov 27 14:10:22 2008 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 53E3C1065674 for ; Thu, 27 Nov 2008 14:10:22 +0000 (UTC) (envelope-from rock_on_the_web@comcen.com.au) Received: from mail.unitedinsong.com.au (202-172-126-254.cpe.qld-1.comcen.com.au [202.172.126.254]) by mx1.freebsd.org (Postfix) with ESMTP id 084128FC1F for ; Thu, 27 Nov 2008 14:10:21 +0000 (UTC) (envelope-from rock_on_the_web@comcen.com.au) Received: from [192.168.0.175] (unknown [192.168.0.175]) by mail.unitedinsong.com.au (Postfix) with ESMTP id 72BEA407A for ; Fri, 28 Nov 2008 00:10:54 +1000 (EST) From: Da Rock To: freebsd-questions@freebsd.org In-Reply-To: References: <1227792354.3603.21.camel@laptop1.herveybayaustralia.com.au> Content-Type: text/plain Date: Fri, 28 Nov 2008 00:10:42 +1000 Message-Id: <1227795042.3603.26.camel@laptop1.herveybayaustralia.com.au> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) Content-Transfer-Encoding: 7bit Subject: Re: APIC error 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, 27 Nov 2008 14:10:22 -0000 On Thu, 2008-11-27 at 14:32 +0100, Ivan Voras wrote: > Da Rock wrote: > > > I know the system is failing because I'm getting usb enumeration errors > > (something that has come up twice before on dying systems, and has > > disappeared as soon as I bought a new one), plus acpi errors in the form > > of being unable to attach device data. > > > > I understand this software unable to cope with interrupts at the cpu, > > and can mean hardware failure or bad software. But given my hardware > > issues I'm fairly certain its the former. My biggest question is where? > > How does it come up with something like that? > > > > Can anyone shed some light on the details of this? I'll be greatful for > > whatever I can get- information is power after all. > > This is too little information for general troubleshooting, except if > someone has encountered this exact problem before. > > From your description, especially since you're suggesting a hardware > failure, it could be anything from BIOS or BIOS "CMOS" error (or > battery) to real hardware problems in the conductors to the buses. > Would this be in the cpu itself or in the mainboard (best guess)? If its the cpu it could be from overheating (could the cpu alone cause all these errors?), but mainboard would mean an inherent communication problem wouldn't it? This really is a hardware issue any way you look at it I know, but a better understanding of what is going on might clarify what we're up against here... cheers guys :)