From owner-freebsd-proliant@FreeBSD.ORG Sat Mar 28 08:36:53 2009 Return-Path: Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D91CD106566B for ; Sat, 28 Mar 2009 08:36:53 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 9223C8FC18 for ; Sat, 28 Mar 2009 08:36:53 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1LnTRX-000LA5-0D; Sat, 28 Mar 2009 10:59:03 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: "Marc G. Fournier" In-reply-to: <20090328024247.Y47574@hub.org> References: <20090328024247.Y47574@hub.org> Comments: In-reply-to "Marc G. Fournier" message dated "Sat, 28 Mar 2009 02:51:48 -0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Mar 2009 10:59:02 +0300 From: Danny Braniss Message-ID: Cc: freebsd-stable@freebsd.org, freebsd-proliant@freebsd.org Subject: Re: ALT_BREAK_TO... + ILO ... missing something in config ... X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Mar 2009 08:36:54 -0000 > > Due to an issue I'm having with 7.x, and trying to track it down, I spent > tonight getting my server setup to allow my to break into the debugger > when it hangs, and hopefully dump core ... > > But, although I *think* I've got it all, I'm obviously missing something, > as it isn't breaking ... > > First ... I'm running a proliant server, and when I connect via SSH to ILO > on that machine, and type 'vsp', I get a shell as I expect, I can type, > etc ... when I reboot the machine, I get the opening splash screen with > the 7(?) options (normal boot, single user mode, etc, etc) ... but I get > nothing between that and the login prompt ... first sign of a problem, > maybe? > not realy, you at least have confirmation that you are talking correctly via the serial port. Till this point boot is using the BIOS routines to talk via the serial port. Later, the kernel tries to use it's routines/knowledge of the serial port. > Next, the easy question ... what is the key stroke to issue when one has > ALT_BREAK_TO_DEBUGGER is set in the kernel? I thought it was CR ~ ^b ... > is that correct? I'm using putty to connect via ssh, if that makes a > difference ... I've also tried using the browser interface into ilo / vsp, > same lack of a result ... unless the serial port is setup as console, check if /boot/device.hints has: hint.sio.0.flags="0x10" escaping to the debugger is not caught. btw, Jeremy Chadwick had a nice explanation, but I lost the URL. > > Beyond adding sio device driver to my kernel, I've also got: > > options ALT_BREAK_TO_DEBUGGER > options KDB > options DDB > > Missing a kernel option maybe? > > I have the following in /boot/loader.conf: > > comconsole_speed="9600" > console="vidconsole,comconsole" # A comma separated list of console(s) > boot_multicons="-D" # -D: Use multiple consoles > boot_serial="-h" # -h: Use serial console > > So ... eithe rI don't have it enabled like I think, or I'm doing the wrong > key stroke ... or ... > > Thx > you are very close!, but each hardware/bios needs a different solution :-( danny