From owner-freebsd-questions Tue Mar 2 6:15:43 1999 Delivered-To: freebsd-questions@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 3B56E14CE9 for ; Tue, 2 Mar 1999 06:15:32 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id JAA21798; Tue, 2 Mar 1999 09:12:03 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id JAA02326; Tue, 2 Mar 1999 09:11:58 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id JAA00379; Tue, 2 Mar 1999 09:11:57 -0500 (EST) Date: Tue, 2 Mar 1999 09:11:57 -0500 (EST) From: Thomas David Rivers Message-Id: <199903021411.JAA00379@lakes.dignus.com> To: bandi@cs.umn.edu, questions@FreeBSD.ORG Subject: Re: console terminal for freebsd machines? Cc: bandi@mail.cs.umn.edu In-Reply-To: <199903012351.RAA02390@mega.cs.umn.edu> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hello, > I appreciate any/all advice on this problem that I am > facing. I have a few freebsd boxes that run experimental software > that tends to make the OS lock up, and hoses it in a way that only > a reboot (or power cycle) from the console can bring it back to > life. > > For the sun hardware (running any OS), the solution is to > simply hook up the serial port to a console server, and reboot it from > there. > > Now it would be cool if such a solution exists for x86 hardware, > namely, a kind of boot monitor in non-volatile memory (EEPROM perhaps?) > that the OS can trip into, and which can communicate via the primary > (or a dedicated) serial port. Is this possible? (I have a EEPROM burner > and burning a PROM image is not a problem, if I can get hold off the > image). > > While that is the ideal solution, I am interested in what > others have done in a similar situation. I have thought about a remote > power strip and most likely will do this if there isnt another way. > Please email me or mail to the mailing-list. I'll summarize private > responses if there is interest. > > Finally, I apologize if this is a FAQ type of question. I looked through > various freebsd lists but could not find what I needed. > > Thanks-in-advance, > -vijay > [bandi@cs.umn.edu] > This *might* work for your needs... I've done a similar thing... 1) Set up your serial connection with the x86 machine. 2) Set up the boot process so that it forces a serial-console boot. 3) Config, build and install a kernel with DDB (the kernel debugger) When either a is seen on the serial line, or the kernel panics, you'll drop into the debugger... unless the panis is *so* disastrous that the machine is locked up hard... (not too likely.) That may be sufficient for your needs. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message