From owner-freebsd-bugs  Tue Dec 16 01:40:03 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id BAA11692
          for bugs-outgoing; Tue, 16 Dec 1997 01:40:03 -0800 (PST)
          (envelope-from owner-freebsd-bugs)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id BAA11685;
          Tue, 16 Dec 1997 01:40:01 -0800 (PST)
          (envelope-from gnats)
Resent-Date: Tue, 16 Dec 1997 01:40:01 -0800 (PST)
Resent-Message-Id: <199712160940.BAA11685@hub.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@FreeBSD.ORG, toasty@dragondata.com
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id BAA11607;
          Tue, 16 Dec 1997 01:39:30 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199712160939.BAA11607@hub.freebsd.org>
Date: Tue, 16 Dec 1997 01:39:30 -0800 (PST)
From: toasty@dragondata.com
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: kern/5314: Screensaver continues operating after kernel panic
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         5314
>Category:       kern
>Synopsis:       Screensaver continues operating after kernel panic
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Tue Dec 16 01:40:00 PST 1997
>Last-Modified:
>Originator:     Kevin Day
>Organization:
DragonData
>Release:        -current and 2.2.5-release
>Environment:
multiple machines
>Description:
After a kernel panic, the screensaver isn't de-activated. It's somewhat common, unfortunately, that the machine will be unable to automatically reboot after a kernel panic. However, the code for running the screensaver seems pretty crash-proof.
It would be a great feature to deactivate the screensaver completely, and keep it off, after a kernel panic. Walking past a machine, if I see the screensaver running, I assume it's ok...
>How-To-Repeat:
Force a kernel panic, but don't allow it to reboot. (this seems to happen most when it locks up during the disk sync stage, or with a SMP kernel, when it's stuck in the wrong processor, and can't get back to cpu #0 to reboot)
>Fix:

>Audit-Trail:
>Unformatted: