From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 29 09:47:25 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 70321106566C for ; Wed, 29 Feb 2012 09:47:25 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 056E88FC19 for ; Wed, 29 Feb 2012 09:47:24 +0000 (UTC) Received: from OctaHexa64-MkII (HPQuadro64.dmpriest.net.uk [62.13.130.30]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3) with ESMTP id q1T9lMdg005694 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Wed, 29 Feb 2012 09:47:23 GMT Date: Wed, 29 Feb 2012 09:47:24 +0000 From: Karl Pielorz To: Sean Bruno Message-ID: <7A0E0A12E1F9691864D4607C@OctaHexa64-MkII> In-Reply-To: <1330454834.3092.7.camel@powernoodle-l7.corp.yahoo.com> References: <21EB76F692ED4215A70037FC@OctaHexa64-MkII> <1330454834.3092.7.camel@powernoodle-l7.corp.yahoo.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-hackers@freebsd.org Subject: Re: SuperMicro IPMI keyboard - fails for 'mountroot>' prompt under FreeBSD 9-R... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Feb 2012 09:47:25 -0000 --On 28 February 2012 10:47 -0800 Sean Bruno wrote: > Can you dump the full dmesg on boot? I've noted that shared ethernet > devices and IPMI seem to conflict. Expecially if the kernel is > explicity turning off the ethernet device becuase its not configured. > > Sean Sure - rather than clutter the list with wrapped / unwrapped lines, you can find it here: If you need me to try anything / further info, let me know. This machine is in our staging area at the moment - it's not in production yet. The RAID shows as degraded during boot as it'd only just been setup (and the machine hadn't been idle for long enough when booted yet to finish rebuilding - think it finished at the bottom of the dmesg output, just incase you were wondering :) Regards, -Karl