From owner-freebsd-questions@FreeBSD.ORG Thu Nov 27 13:25:35 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 97CFC1065679 for ; Thu, 27 Nov 2008 13:25:35 +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 4AD9D8FC1E for ; Thu, 27 Nov 2008 13:25:35 +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 6CBDA406C for ; Thu, 27 Nov 2008 23:26:06 +1000 (EST) From: Da Rock To: freebsd-questions@freebsd.org Content-Type: text/plain Date: Thu, 27 Nov 2008 23:25:54 +1000 Message-Id: <1227792354.3603.21.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: 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 13:25:35 -0000 This is occurring on a linux system, but from my investigations it wouldn't be limited to just this OS. Therefore, I come seeking wisdom from some real gurus... only kidding. But the collective experience here in sysadmin is greater than the experience of desktop users found on linux lists. I checked my dmesg today on a system which I know is failing, and found a message regarding an apic error on cpu1 00(40). The system is a dual core pentium. 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. For reference, this is an ASUS notebook which is only a few months old. I rang the warranty support and started telling them what was going wrong with it, but I was interrupted by the guy telling me that unless window$ was on it they weren't even going to touch it. Needless to say I told him to shove that philosophy where the sun don't shine, but I thought this was strange coming from a company which has pioneered the use of linux in the user range through the eeepc range... Fair enough if they want window$ but they can put it on and not waste my time further AND leave me without a machine to work with. What I can't work out is how they are going to be able to diagnose a problem like this easier with an OS which is a black box (almost). And their words were that they couldn't test the device properly without window$!