From owner-freebsd-current@FreeBSD.ORG Tue Sep 20 00:55:49 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DF2E16A41F for ; Tue, 20 Sep 2005 00:55:49 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB49443D45 for ; Tue, 20 Sep 2005 00:55:46 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id j8K0tYHW029519; Mon, 19 Sep 2005 18:55:34 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <432F5E10.7080406@samsco.org> Date: Mon, 19 Sep 2005 18:55:44 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Wilkinson, Alex" References: <20050920004358.GA76462@squash.dsto.defence.gov.au> In-Reply-To: <20050920004358.GA76462@squash.dsto.defence.gov.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: current@freebsd.org Subject: Re: Broken MP table detected ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2005 00:55:49 -0000 Wilkinson, Alex wrote: > Can anyone tell me what the following means, and how to fix it: > > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2 > APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 > > - aW It means that you need to use 6.0 instead of 5.x =-) It represents the old way that we connected the timecounters, which apparently isn't well supported with newer amd64 boards. 6.0 solves this problem by using a better supported mechanism. Scott