From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 01:35:39 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 E4C0B16A41F for ; Sun, 20 Nov 2005 01:35:39 +0000 (GMT) (envelope-from craig@xfoil.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66DB043D70 for ; Sun, 20 Nov 2005 01:35:33 +0000 (GMT) (envelope-from craig@xfoil.gank.org) Received: by ion.gank.org (mail, from userid 1001) id 7111E2BF5B; Sat, 19 Nov 2005 19:35:33 -0600 (CST) Date: Sat, 19 Nov 2005 19:35:30 -0600 From: Craig Boston To: Tillman Hodgson Message-ID: <20051120013530.GA55161@nowhere> Mail-Followup-To: Craig Boston , Tillman Hodgson , FreeBSD -CURRENT References: <20051118213407.GD89507@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051118213407.GD89507@seekingfire.com> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD -CURRENT Subject: Re: Compaq ProLiant 1600 server freezes when detecting keyboard controller 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: Sun, 20 Nov 2005 01:35:40 -0000 On Fri, Nov 18, 2005 at 03:34:07PM -0600, Tillman Hodgson wrote: > In my case, I have a -current kernel from August 20th 2005 that > continues to boot properly. Subsequent kernels, including both Oct 20 > and Nov 17, fail to boot past the atkbdc point. It's an interesting > freeze in that cntrl-alt-del doesn't perform a reboot. The Aug 20 kernel > lines corresponding to that point look like this: > > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 I've seen this freeze on a couple of 1600s with 6.0-RELEASE. Does this system have multiple processors? If not, try changing the "OS Type" setting in the BIOS to "Other". That fixed it for me. I've had success with using Other for non-SMP kernels, and using the UnixWare 2.1 setting for SMP kernels. I didn't have to use this workaround on 5.4, but I'm not sure when it broke. ProLiants in general seem to be finicky beasts with BSD... I also noticed that 6.0 detects a phantom USB controller and when it attempts to allocate resources to it (and fails), the serial port redirection for the console dies. I can't prove that there isn't hardware on the board somewhere, but these boxes have no USB ports and there's no mention of it in the BIOS. Commenting out uhci from the kernel fixes the serial console. Craig