Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Mar 1999 09:11:57 -0500 (EST)
From:      Thomas David Rivers <rivers@dignus.com>
To:        bandi@cs.umn.edu, questions@FreeBSD.ORG
Cc:        bandi@mail.cs.umn.edu
Subject:   Re: console terminal for freebsd machines?
Message-ID:  <199903021411.JAA00379@lakes.dignus.com>
In-Reply-To: <199903012351.RAA02390@mega.cs.umn.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> 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 <break> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903021411.JAA00379>