From nobody  Tue Dec 16 01:39:30 1997
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
Subject: Screensaver continues operating after kernel panic
X-Send-Pr-Version: www-1.0

>Number:         5314
>Category:       kern
>Synopsis:       Screensaver continues operating after kernel panic
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Tue Dec 16 01:40:00 PST 1997
>Closed-Date:    Wed Feb 11 07:12:48 PST 1998
>Last-Modified:  Wed Feb 11 07:14:35 PST 1998
>Originator:     Kevin Day
>Release:        -current and 2.2.5-release
>Organization:
DragonData
>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:

>Release-Note:
>Audit-Trail:

From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To: toasty@dragondata.com
Cc: freebsd-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: kern/5314: Screensaver continues operating after kernel panic 
Date: Sun, 21 Dec 1997 15:27:12 +0900

 >>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 cr
 >ash-proof.
 [snip]
 
 Would you possibly apply the following patch to /sys/i386/isa/syscons.c
 and see if it works for you?
 
 Kazu
 yokota@freebsd.org
 
 --- syscons.c-1.242	Tue Dec  9 10:41:31 1997
 +++ syscons.c	Wed Dec 17 16:23:50 1997
 @@ -2152,7 +2152,7 @@
      }
  
      /* should we stop the screen saver? */
 -    if (mono_time.tv_sec <= scrn_time_stamp + scrn_blank_time)
 +    if (mono_time.tv_sec <= scrn_time_stamp + scrn_blank_time || panicstr)
  	if (scrn_blanked > 0)
              stop_scrn_saver(current_saver);
  
 @@ -2220,7 +2220,8 @@
  
      /* should we activate the screen saver? */
      if ((scrn_blank_time != 0) 
 -	    && (mono_time.tv_sec > scrn_time_stamp + scrn_blank_time))
 +	    && (mono_time.tv_sec > scrn_time_stamp + scrn_blank_time)
 +	    && (panicstr == NULL))
  	(*current_saver)(TRUE);
  
      timeout(scrn_timer, NULL, hz / 25);
 
State-Changed-From-To: open->closed 
State-Changed-By: yokota 
State-Changed-When: Wed Feb 11 07:12:48 PST 1998 
State-Changed-Why:  
Fix is in syscons.c v1.248, 3.0-CURRENT. 
>Unformatted:
