From: Martin Pool <mbp@sourcefrog.net>
To: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: KDB in the mainstream 2.4.x kernels?
Date: Wed, 13 Aug 2003 14:40:31 +1000 [thread overview]
Message-ID: <pan.2003.08.13.04.40.27.59654@sourcefrog.net> (raw)
In-Reply-To: m3smp3y38y.fsf@averell.firstfloor.org
On Fri, 18 Jul 2003 22:43:57 +0200, Andi Kleen wrote:
> KDB is usually not useful for debugging hangs on desktop boxes (and even
> many servers) because you have usually X running. When the machine crashes
> and goes in KDB you cannot see the text output and debug anything. I
> learned to type "go<return>" blind when I had still an KDB aware kernel,
> but it's not very useful overall.
Perhaps in the case where the console is on a vt, kdb could try to
switch to the right vc before presenting its prompt? I realize calling into
the vc code might be risky but it seems like there's not much to lose.
(If you do have a bug in say the agp driver then you need a serial
console...) If it works, you'll be able to debug and continue.
It could even set the colors to white on blue. :-)
--
Martin
next prev parent reply other threads:[~2003-08-13 4:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aJIn.3mj.15@gated-at.bofh.it>
2003-07-18 20:43 ` KDB in the mainstream 2.4.x kernels? Andi Kleen
2003-07-19 0:31 ` linas
2003-07-19 0:57 ` Andi Kleen
2003-07-20 12:55 ` Keith Owens
2003-07-20 13:31 ` David S. Miller
2003-07-20 22:27 ` Keith Owens
2003-07-21 15:06 ` Andi Kleen
2003-07-29 19:44 ` Robin Holt
2003-08-13 4:40 ` Martin Pool [this message]
2003-08-13 11:04 ` Andi Kleen
2003-08-25 12:16 ` Greg Stark
2003-08-25 16:23 ` Andi Kleen
2003-08-26 13:39 ` Greg Stark
2003-08-27 13:49 ` Alan Cox
2003-08-30 10:35 ` Pavel Machek
2003-09-02 20:40 Tolentino, Matthew E
-- strict thread matches above, loose matches on Subject: below --
2003-08-28 17:08 Tolentino, Matthew E
2003-08-28 20:24 ` Alan Cox
2003-07-18 20:06 linas
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=pan.2003.08.13.04.40.27.59654@sourcefrog.net \
--to=mbp@sourcefrog.net \
--cc=ak@muc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.