mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Grant Coady <gcoady.lk@gmail.com>
Cc: Andi Kleen <ak@suse.de>, Dmitry Torokhov <dtor@insightbb.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH-mm] i8042: activate panic blink only in X
Date: Tue, 5 Sep 2006 01:03:58 +0200	[thread overview]
Message-ID: <20060904230358.GC1614@rhlx01.fht-esslingen.de> (raw)
In-Reply-To: <ri9pf258l1q51kgsjs4u90sjp9581djjgs@4ax.com>

Hi,

On Tue, Sep 05, 2006 at 08:29:09AM +1000, Grant Coady wrote:
> If possible, kill the console blank timer too?  (dunno if you have).
> 
> Example: Oops screen on 2.4 recently I paged up to where the fault 
> started, the screen blanker kicked in while I was hand copying info 
> and wiped previous screens :(  Caused significant delay in working 
> out what the issue was (slackware-10.2 2.4.33.1 glibc nptl boo-boo).
> 
> Is it safe / easy to do on oops/panic?

It should be as easy as e.g. doing a

int system_oopsed __read_mostly = 0;

if (!system_oopsed)
    blank();

in the timer handler as opposed to painfully deregistering the whole handler
in the critical system state after an OOPS.
A funny side effect is that this way even improves system stability
after OOPS, since the blanking (which doesn't happen then)
might bomb, too ;)

Andreas Mohr

  reply	other threads:[~2006-09-04 23:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-03  3:20 Dmitry Torokhov
2006-09-03 13:20 ` Grant Coady
2006-09-04 14:58 ` Andi Kleen
2006-09-04 22:29   ` Grant Coady
2006-09-04 23:03     ` Andreas Mohr [this message]
2006-09-05  0:16       ` Grant Coady
2006-09-21  4:07     ` Dmitry Torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060904230358.GC1614@rhlx01.fht-esslingen.de \
    --to=andi@rhlx01.fht-esslingen.de \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=dtor@insightbb.com \
    --cc=gcoady.lk@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®