From owner-freebsd-acpi@FreeBSD.ORG Fri Dec 30 07:38:43 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C004716A434; Fri, 30 Dec 2005 07:38:43 +0000 (GMT) (envelope-from paketix@bluewin.ch) Received: from mail29.bluewin.ch (mail29.bluewin.ch [195.186.18.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44FF143D49; Fri, 30 Dec 2005 07:38:43 +0000 (GMT) (envelope-from paketix@bluewin.ch) Received: from mssazhb-int.msg.bluewin.ch (172.21.1.181) by mail29.bluewin.ch (Bluewin 7.2.069.1) id 43A92893001A16CF; Fri, 30 Dec 2005 07:38:42 +0000 Received: from [195.186.18.72] by mssazhb-int.msg.bluewin.ch with HTTP; Fri, 30 Dec 2005 07:38:38 +0000 Date: Fri, 30 Dec 2005 08:38:38 +0100 Message-ID: <4392C11D000CA114@mssazhb-int.msg.bluewin.ch> In-Reply-To: <200512291130.14606.jhb@freebsd.org> From: paketix@bluewin.ch To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Mailer: Bluewin WebMail / BlueMail Cc: Subject: Re: dl580g3/amd64: [ACPI] 6.0-RELEASE will not boot with ACPI enabled X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2005 07:38:45 -0000 >-- Original-Nachricht -- >From: John Baldwin >To: freebsd-acpi@freebsd.org >Subject: Re: dl580g3/amd64: [ACPI] 6.0-RELEASE will not boot with ACPI enabled >Date: Thu, 29 Dec 2005 11:30:13 -0500 >Cc: paketix@bluewin.ch > > >On Wednesday 28 December 2005 04:06 am, paketix@bluewin.ch wrote: >> if booted with 6.0-RELEASE (amd64) the system hangs >> if booted with 5.4-RELEASE (amd64) the system boots just fine >> disabling acpi on 6.0-RELEASE helps but it seems that using SMP will not >> be possible after that >> it seems to be an issue related to the pci cards - if if remove all cards >> the system boots well using 6.0-RELEASE >> >> please find all the logs (boot -v; sysctl; acpidump) at >> http://mypage.bluewin.ch/poe/ >> >> system description: >> hp dl580g3 >> dual proc xeon 3ghz >> 4gb ram >> smart array 6i >> 5 fiber optic dual port pci-x cards (intel) >> 1 rj45 quad port pci-x card (intel) >> >> please let me know if further information/patch-testing is needed >> local access to the machines is possible until mid of january - one machine >> runs 5.4-RELEASE the other one 6.0-RELEASE >> hope somebody has the time to have a look at it >> >> regards, pat > >Try enabling SMP by building an SMP kernel. I think I know what this issue >is >and might have a possible fix that's not in HEAD yet. On some Intel >motherboards, when an OS uses a certain delivery mode for interrupts >(LOWPRIO, which FreeBSD currently uses), the chipset sends all interrupts >to >cpu3 (htt cpu on 2nd processor), but with a UP kernel that CPU isn't started > >up and listening for interrupts. It seems that when you use LOWPRIO Intel's > >chipset _ignores_ the programmed destination and sends interrupts to CPU >3. >Even if you program the Irq to go to CPU 2, it still sends it to CPU 3. >I'm >not sure why 5.4 is not seeing the same issue. However, several people have > >reported that on 6.0 they have to enable SMP if they use the apic to boot. > >-- >John Baldwin <>< http://www.FreeBSD.org/~jhb/ >"Power Users Use the Power to Serve" = http://www.FreeBSD.org hi john thanks for your feedback! i created a smp kernel from RELENG_6_0 this morning and tested it on the dl580g3 with acpi enabled - but still the same behaviour... ...the system boots and hangs somewhere after initializing the nics please find the new logs (smp kernel config and boot -v) at http://mypage.bluewin.ch/poe/