lkml.org 
[lkml]   [2003]   [Aug]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
Date
From
SubjectRe: KDB in the mainstream 2.4.x kernels?
On Wed, Aug 13, 2003 at 02:40:31PM +1000, Martin Pool wrote:
> 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.

Only the X server can switch away, because only it knows how
to talk to the graphic chipset. And running user space here is
far too risky.

It's possible when the resolutions are controlled by the kernel
in fbcon. That's the case on linux/ppc and you can indeed debug on
top of an X server there. But it's unlikely to happen for linux/x86, the
xfree86 people don't want to move parts of their drivers into the kernel.

-Andi

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

\
 
 \ /
  Last update: 2005-03-22 13:47    [W:0.119 / U:1.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site