From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 9 14:58:41 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01FA0106566B for ; Wed, 9 Dec 2009 14:58:41 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityhosting.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id 9B4078FC16 for ; Wed, 9 Dec 2009 14:58:40 +0000 (UTC) Received: from [127.0.0.1] ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Wed, 9 Dec 2009 09:58:35 -0500 X-WatchGuard-Mail-Exception: Allow Message-ID: <4B1FBBFD.3080301@greatbaysoftware.com> Date: Wed, 09 Dec 2009 10:02:21 -0500 From: Charles Owens MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <4AF2E837.2080705@greatbaysoftware.com> In-Reply-To: <4AF2E837.2080705@greatbaysoftware.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-WatchGuard-AntiVirus: part scanned. clean action=allow X-ME-Bayesian: 0.000000 Subject: Re: kern/139654: CD-boot failure on newer IBM server X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Dec 2009 14:58:41 -0000 Charles Owens wrote: > Hello, > > As detailed in the PR, we are unable to get FreeBSD (7.1) to boot with > an IBM System x3250 M2 server. I'm not sure what steps to take next, > and would greatly appreciate assistance. > > We've also submitted kern/139653 which deal with different hardware (HP) > and is not quite as critical (very poor performance, as opposed to > complete failure)... any suggestions with this also welcome. > > PR links: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/139654 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/139653 Tying up this loose thread... PR kern/139654 turns out to be duplicate of kern/103602. Patch in PR from Alexander Motin (mav@) appears to resolve our issue (works fine in 7.1 but must be applied by hand). Our thanks to him for his generous support. Charles Owens Great Bay Software, Inc.