Date: Mon, 13 Sep 1999 04:27:58 -0700 (PDT) From: dima@server.ru To: freebsd-gnats-submit@freebsd.org Subject: kern/13721: There is no way to force system panic from console Message-ID: <19990913112758.6E37214D79@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 13721 >Category: kern >Synopsis: There is no way to force system panic from console >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Sep 13 04:30:00 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Dmitry Kazarov >Release: FreeBSD 3.3-RC >Organization: Server >Environment: >Description: Under some rare circumstances there is a real need to reboot system via kernel's panic from the system console. For example: if any process has ran out of memory nobody can login and even Ctrl-Alt-Del does not work and there is no way to find out source of the problem after cold boot. And if reboot is not disabled the panic will not decrease the system's security especially; where enabling kernel debugger is not acceptable. On Sun it is the only way to reboot the working system: OpenBoot prom on boot and reset commands at first checks whether Solaris is running and if it is running - calls its panic routine. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990913112758.6E37214D79>