From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"George Bonser" <george@gator.com>
Cc: "Linux Kernel Development" <linux-kernel@vger.kernel.org>
Subject: Re: Linux console at boot
Date: Tue, 12 Feb 2002 10:14:36 -0500 [thread overview]
Message-ID: <003f01c1b3d7$fd1755b0$5601010a@prefect> (raw)
In-Reply-To: <Pine.GSO.4.21.0202120950480.12840-100000@vervain.sonytel.be>
----- Original Message -----
From: "Geert Uytterhoeven" <geert@linux-m68k.org>
To: "George Bonser" <george@gator.com>
Cc: "Linux Kernel Development" <linux-kernel@vger.kernel.org>
Sent: Tuesday, February 12, 2002 3:52 AM
Subject: Re: Linux console at boot
> On Thu, 24 Jan 2002, George Bonser 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).
> >
> > This is an Intel unit using the standard console (not serial console).
> > pre7 will not boot but pre6 boots every time.
>
> On Amiga (m68k and PPC) we have a `debug=mem' option that will write all
kernel
> messages to a 256 KiB block (marked with a magic number) of Chip RAM. If
the
> system crashes early, you can reboot into AmigaOS and run a special
utility
> that finds the 256 KiB block (Chip RAM is not completely erased on reboot)
and
> extracts the messages.
Also, printk already writes (appends) to a smaller-but-sufficiently-large
buffer - log_buf. When debugging early boot crashes, I frequently look up
the address of log_buf in System.map and dump that area of memory from my
boot monitor or JTAG prompt.
Regards,
Brad
next prev parent reply other threads:[~2002-02-12 15:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 5:05 Linux console at boot 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
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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='003f01c1b3d7$fd1755b0$5601010a@prefect' \
--to=brad@ltc.com \
--cc=geert@linux-m68k.org \
--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