linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
To: David Lang <dlang@digitalinsight.com>
Cc: Dave Jones <davej@redhat.com>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	linux-kernel@vger.kernel.org
Subject: Re: oops pauser.
Date: Thu, 5 Jan 2006 20:41:40 -0500	[thread overview]
Message-ID: <20060106014140.GG5516@filer.fsl.cs.sunysb.edu> (raw)
In-Reply-To: <Pine.LNX.4.62.0601051722110.973@qynat.qvtvafvgr.pbz>

On Thu, Jan 05, 2006 at 05:24:01PM -0800, David Lang wrote:
> On Thu, 5 Jan 2006, Dave Jones wrote:
> 
> >> (*) If the oops is longer than 25 lines, ... you can't even use 
> >scrollback
> >> because scrollback is cleared when you change consoles. X runs by default
> >> on tty7, and the kernel dumps it somewhere else. (And even if it dumped 
> >to
> >> tty7 directly, you would not see it.)
> >
> >What to do about oopses whilst in X has been the subject of much
> >head-scratching for years now.  It's come up at least at the
> >last two kernel summits, and I'll hazard a guess it'll come up
> >again this year.  The amount of work necessary to make it all
> >work on both kernel side and X side isn't unsubstantial however,
> >so I wouldn't count on it working too soon.
> 
> hmm, if you can hope that someone will grab a camera to report an oops, 
> how about them grabbing a tape recorder/mp3 recorder to record audio from 
> the speaker. it's not fast, but you don't have that much data to output, 
> do it in morse (with the audio explination of what's going to happen 
> first)

There is a patch somewhere that uses the keyboard lights to "display" panics,
and a comment that the PC speaker implementation is left up to the reader :)

It shouldn't be hard do, then all you need is just one printk telling the user
to record it :)

Jeff.

  reply	other threads:[~2006-01-06  1:41 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-05  4:52 oops pauser Dave Jones
2006-01-05  6:10 ` oops pauser. / boot_delayer Randy.Dunlap
2006-01-05  7:30   ` Bernd Eckenfels
2006-01-05  8:07     ` Jan Engelhardt
2006-01-06  1:28       ` David Lang
2006-01-06  5:36         ` Dave Jones
2006-01-06  7:00           ` David Lang
2006-01-08 13:21           ` Pavel Machek
2006-01-08 19:30             ` Josef Sipek
2006-01-08 23:08               ` Pavel Machek
2006-01-08 23:39                 ` Josef Sipek
2006-01-06  7:36         ` Jan Engelhardt
2006-01-06  8:33           ` David Lang
2006-01-05  9:25     ` Grant Coady
2006-01-05 15:31       ` Mark Lord
2006-01-05 15:38         ` Avishay Traeger
2006-01-05 19:15           ` Mark Lord
2006-01-05 11:11     ` Dave Jones
2006-01-07 21:44       ` Kurtis D. Rader
2006-01-07 21:48         ` Arjan van de Ven
2006-01-07 22:00           ` Kurtis D. Rader
2006-01-08 23:29           ` David Lang
2006-01-07 22:27         ` Bernd Eckenfels
2006-01-05  8:15 ` oops pauser Jan Engelhardt
2006-01-05 10:33   ` Dave Jones
2006-01-05 11:05     ` Jan Engelhardt
2006-01-05 12:05       ` Keith Owens
2006-01-05 15:17       ` Jesper Juhl
2006-01-05 13:46     ` Kurt Wall
2006-01-06  1:24     ` David Lang
2006-01-06  1:41       ` Josef Sipek [this message]
2006-01-08 13:38     ` Ville Herva
2006-01-08 13:53       ` Randy.Dunlap
2006-01-08 19:35         ` Jan Engelhardt
2006-01-09  1:43           ` Randy.Dunlap
2006-01-08 19:40         ` Grant Coady
2006-01-09  1:45           ` Randy.Dunlap
2006-01-09 16:15             ` Jan Engelhardt
2006-01-09 16:25               ` Ville Herva
2006-01-09 16:39               ` Randy.Dunlap
2006-01-05 13:37 ` Alan Cox
2006-01-05 20:52   ` Dave Jones
2006-01-06 13:31     ` Alan Cox
2006-01-06 20:33       ` Dave Jones
2006-01-06 15:22     ` Pavel Machek
2006-01-06 19:06       ` Jan Engelhardt
2006-01-06 22:34         ` Pavel Machek
2006-01-06 22:48       ` Dave Jones
2006-01-05 13:58 ` Avishay Traeger
2006-01-05 20:54   ` Dave Jones
2006-01-06  0:19   ` Josef Sipek
2006-01-06  1:12     ` Bernd Eckenfels
2006-01-06  1:35       ` Josef Sipek
2006-01-06  2:21         ` Bernd Eckenfels
2006-01-05 14:39 ` Kyle McMartin
2006-01-09 18:43 ` Console debugging wishlist was: " Andi Kleen
2006-01-10 20:25   ` Jan Engelhardt
2006-01-10 20:29     ` Josef Sipek
2006-01-10 20:44       ` Jan Engelhardt
2006-01-10 22:54         ` Josef Sipek
2006-01-10 20:46       ` Andi Kleen
2006-01-10 20:45     ` Andi Kleen
2006-01-10 21:06       ` Jan Engelhardt
2006-01-10 21:18         ` Andi Kleen
2006-01-10 21:30           ` Jan Engelhardt
2006-01-11 12:24     ` Antonino A. Daplas
2006-01-11 12:31       ` Andi Kleen
2006-01-11 13:05         ` Antonino A. Daplas
2006-01-11 13:17           ` Andi Kleen
2006-01-11 13:43             ` Antonino A. Daplas
2006-01-11 13:51               ` Andi Kleen
2006-01-11 18:34           ` Jan Engelhardt
     [not found] <5rvok-5Sr-1@gated-at.bofh.it>
     [not found] ` <5ryvR-2aN-5@gated-at.bofh.it>
     [not found]   ` <5rAHn-5kc-9@gated-at.bofh.it>
2006-01-06  5:52     ` Robert Hancock
2006-01-06  7:06       ` Jan Engelhardt
2006-01-06  7:47         ` Randy.Dunlap
2006-01-06  8:58         ` Dave Jones

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=20060106014140.GG5516@filer.fsl.cs.sunysb.edu \
    --to=jsipek@fsl.cs.sunysb.edu \
    --cc=davej@redhat.com \
    --cc=dlang@digitalinsight.com \
    --cc=jengelh@linux01.gwdg.de \
    --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;
as well as URLs for NNTP newsgroup(s).