Date: Tue, 16 Dec 1997 01:39:30 -0800 (PST) From: toasty@dragondata.com To: freebsd-gnats-submit@FreeBSD.ORG Subject: kern/5314: Screensaver continues operating after kernel panic Message-ID: <199712160939.BAA11607@hub.freebsd.org> Resent-Message-ID: <199712160940.BAA11685@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712160939.BAA11607>