From: Keith Owens <kaos@ocs.com.au>
To: "George Bonser" <george@gator.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux console at boot
Date: Sat, 26 Jan 2002 21:32:45 +1100 [thread overview]
Message-ID: <20849.1012041165@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Thu, 24 Jan 2002 21:05:45 -0800." <CHEKKPICCNOGICGMDODJKEPAGBAA.george@gator.com>
On Thu, 24 Jan 2002 21:05:45 -0800,
"George Bonser" <george@gator.com> wrote:
>Is there any way to stop the console scrolling during boot? My reason
>for this is I am trying to troubleshoot a boot problem with
>2.4.18-pre7 and I would like to give a more useful report than "it
>won't boot" but the screen outputs information every few seconds and I
>can't "freeze" the display so I can copy down the initial error(s).
Serial console is the best. If you can't do that, add a delay after
each set of console output. Tweak 100000000 to get a suitable delay.
Index: 17.1/kernel/printk.c
--- 17.1/kernel/printk.c Tue, 11 Dec 2001 09:58:50 +1100 kaos (linux-2.4/j/48_printk.c 1.1.2.2.7.1.2.3 644)
+++ 17.1(w)/kernel/printk.c Sat, 26 Jan 2002 21:30:53 +1100 kaos (linux-2.4/j/48_printk.c 1.1.2.2.7.1.2.3 644)
@@ -373,6 +373,7 @@ static void call_console_drivers(unsigne
}
}
_call_console_drivers(start_print, end, msg_level);
+ { int i; for (i = 0; i < 100000000; ++i) ; }
}
static void emit_log_char(char c)
next prev parent reply other threads:[~2002-01-26 10:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 5:05 George Bonser
2002-01-25 6:06 ` M. Edward Borasky
2002-01-25 6:27 ` George Bonser
2002-01-25 13:46 ` Kenneth MacDonald
2002-01-26 5:51 ` Timothy Covell
2002-01-25 5:54 ` George Bonser
2002-01-25 5:59 ` Brendan J Simon
2002-01-26 7:13 ` Timothy Covell
2002-01-26 10:32 ` Keith Owens [this message]
2002-01-26 20:34 ` George Bonser
2002-01-26 22:04 ` George Bonser
2002-02-12 8:52 ` Geert Uytterhoeven
2002-02-12 15:14 ` Bradley D. LaRonde
2002-02-12 15:25 Alexander Sandler
2002-02-12 15:33 ` Davidovac Zoran
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=20849.1012041165@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=george@gator.com \
--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
all inboxes | Powered by JetHome®