From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Initrd and 2.6.33 curious behaviour
Date: Sat, 22 May 2010 10:46:37 +0100 [thread overview]
Message-ID: <20100522094637.GA954@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <87fx1k46qg.fsf@free.fr>
On Sat, May 22, 2010 at 11:37:43AM +0200, Robert Jarzmik wrote:
> Or alternatively, is there a clever way of storing some data relative to
> reserve_bootmem_node() or __reserve() to be printed at the tail of kernel log
> (ie. in do_mounts_rd()) which would help me investigate ?
You could boot with 'quiet' so that the kernel shuts up most of the
noisy kernel messages.
next prev parent reply other threads:[~2010-05-22 9:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 20:27 Initrd and 2.6.33 curious behaviour Robert Jarzmik
2010-05-21 20:43 ` Russell King - ARM Linux
2010-05-22 9:36 ` Robert Jarzmik
2010-05-22 9:37 ` Robert Jarzmik
2010-05-22 9:46 ` Russell King - ARM Linux [this message]
2010-05-23 0:23 ` Robert Jarzmik
2010-05-23 9:01 ` Russell King - ARM Linux
2010-05-23 10:09 ` Robert Jarzmik
2010-05-24 19:22 ` Robert Jarzmik
2010-05-27 12:00 ` Robert Jarzmik
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=20100522094637.GA954@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).