From: Zilvinas Valinskas <zilvinas@wilibox.com>
To: "Hans-Jürgen Koch" <hjk@linutronix.de>
Cc: Esteban Fernandez <estfern@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Pausing kernel boot messages
Date: Mon, 27 Aug 2007 15:09:50 +0300 [thread overview]
Message-ID: <1188216590.5361.27.camel@zv.wilibox.com> (raw)
In-Reply-To: <200708271353.22665.hjk@linutronix.de>
Esteban,
Alternatively, read Documentation/networking/netconsole.txt. Might help
or might not. It depends when system is crashing.
On Mon, 2007-08-27 at 13:53 +0200, Hans-Jürgen Koch wrote:
> Am Montag 27 August 2007 13:21 schrieb Esteban Fernandez:
> > How do you pause the kernel boot messages ?
> >
> > ^S, Pause and Scroll lock do nothing and you can't Shift-Page-Up after a
> > kernel panic.
>
> These are functions of a shell (like bash), which you haven't got yet during
> kernel boot. You can read the kernel boot messages _after_ your system's up
> using dmesg etc.
> If you can't do that, e.g. because your kernel always hangs during boot, you
> could enable a serial console in your kernel and watch/log your kernel
> messages with a terminal program running on a different computer.
>
> Hans
>
> -
> 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/
next prev parent reply other threads:[~2007-08-27 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 11:21 Esteban Fernandez
2007-08-27 11:53 ` Hans-Jürgen Koch
2007-08-27 11:58 ` Andreas Schwab
2007-08-27 12:13 ` Hans-Jürgen Koch
2007-08-30 19:15 ` Jan Engelhardt
2007-08-27 12:09 ` Zilvinas Valinskas [this message]
2007-08-31 16:58 ` Chuck Ebbert
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=1188216590.5361.27.camel@zv.wilibox.com \
--to=zilvinas@wilibox.com \
--cc=estfern@gmail.com \
--cc=hjk@linutronix.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 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®