From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 16:06:57 2004 Return-Path: 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 C1FEF16A4CE for ; Tue, 16 Nov 2004 16:06:57 +0000 (GMT) Received: from imap.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E98643D2F for ; Tue, 16 Nov 2004 16:06:57 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from pcle2.cc.univie.ac.at (pcle2.cc.univie.ac.at [131.130.2.177]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id iAGG6oam215504 for ; Tue, 16 Nov 2004 17:06:52 +0100 Date: Tue, 16 Nov 2004 17:06:50 +0100 (CET) From: Lukas Ertl To: freebsd-current@FreeBSD.org Message-ID: <20041116170615.K92983@pcle2.cc.univie.ac.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: mx8 4248; Body=1 Fuz1=1 Fuz2=1 Subject: Problem with HP DL380 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 16:06:57 -0000 Hi, I'm having a rather specific problem with a -CURRENT from yesterday. My crashbox is an HP DL380 G3, with two Xeon processors, and one of the nice features of this box is the so called iLO service module, which offers remote console access via the net. Now, with the new kernel, this iLO remote console seems to lock up in the boot process at this point (from boot -v): acpi0: on motherboard acpi0: [MPSAFE] acpi0: Power Button (fixed) pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00141166) pcibios: BIOS version 2.10 AcpiOsDerivePciId: bus 0 dev 0 func 0 ACPI timer: 0/5 0/5 0/6 The boot process itself finishes fine, and the 'real' console also works as expected. It's just that iLO console that locks up. A kernel from Nov 4 doesn't show this behaviour, so I somehow don't believe it's a hardware problem. Anyone out there with such a machine who can confirm this behaviour? cheers, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/