Re: [RFC/PATCH-mm] i8042: activate panic blink only in X

[Grant Coady]

On 04 Sep 2006 16:58:33 +0200, Andi Kleen <ak@xxxxxxx> wrote:

>Dmitry Torokhov <dtor@xxxxxxxxxxxxx> writes:
>
>> Hi,
>> 
>> Here is an attempt to make panicblink only active in X so there is a
>> chance of keyboard still working after panic in text console. Any reason
>> why is should not be done this way?
>> 
>
>Looks good to me.
>
>Of course it would be even better to fix the panic stuff to not disrupt scrollback,
>but short of that it's a good idea.
>
>-Andi (original panic blink author)

I'd like to have panic blink and also be able to Shft-Up to previous 
console screens.  

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?

Grant.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/