[lkml]   [2000]   [Sep]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [DOC] Debugging early kernel hangs
On Sat, 23 Sep 2000 12:42:13 +0200, 
Benjamin Herrenschmidt <> wrote:
>However, there's still a huge gap between the last progress() message and
>availability of the frame buffer device. The simple console has the
>advantage of outputing existing printk messages. (basically, it's a
>console using prom_printf).

Something I forgot to mention about debugging using screen writes. If
the problem is caused by incorrect compiler output then even printk can
fail. Not because the C code is wrong but because the generated
assembler is wrong. Writing direct to screen memory is as simple as it
gets and gives the compiler little or no chance to get it wrong.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

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