public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk>
To: Casey Dahlin <cjdahlin@ncsu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Overriding X on panic
Date: Sat, 25 Nov 2006 16:09:54 +0000	[thread overview]
Message-ID: <20061125160954.239e0d7e@localhost.localdomain> (raw)
In-Reply-To: <1164434093.10503.2.camel@localhost.localdomain>

On Sat, 25 Nov 2006 00:54:53 -0500
Casey Dahlin <cjdahlin@ncsu.edu> wrote:

> Linus did say that he would do anything within reason to help desktop
> linux forward, and frankly a big step forward would be to get error
> messages to the user. What might be some safe options for overriding,
> switching away from, killing, or otherwise disposing of the X server
> when an unrecoverable Oops is about to occur on the TTY?

Assuming frame buffer support is present in the kernel you need an ioctl
that specifies the frame buffer depth/layout so the kernel can print
correctly on it. At that point most of the time you'll get the report out
- more than trying to mode switch probably.

Send patches

Alan

  parent reply	other threads:[~2006-11-25 16:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-25  5:54 Overriding X on panic Casey Dahlin
2006-11-25  8:32 ` Arjan van de Ven
2006-11-25 16:10   ` Alan
2006-11-26  2:48     ` Matthew Garrett
2006-11-26  8:18     ` Arjan van de Ven
2006-11-26 14:22       ` Alan
2006-11-26 22:19         ` Dave Airlie
2006-11-26 22:42           ` D. Hazelton
2006-11-29 13:57           ` Pavel Machek
2006-11-25 16:09 ` Alan [this message]
2006-11-26 12:40   ` James Courtier-Dutton

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=20061125160954.239e0d7e@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=cjdahlin@ncsu.edu \
    --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