From: Ingo Molnar <mingo@elte.hu>
To: Bodo Eggert <7eggert@gmx.de>
Cc: Luca Tettamanti <kronos.it@gmail.com>,
"H. Peter Anvin" <hpa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [2.6.27] overlapping early reservations [was: early exception - lockdep related?]
Date: Mon, 8 Sep 2008 16:30:03 +0200 [thread overview]
Message-ID: <20080908143003.GB10580@elte.hu> (raw)
In-Reply-To: <E1KcNQE-0001Le-8P@be1.7eggert.dyndns.org>
* Bodo Eggert <7eggert@gmx.de> wrote:
> Ingo Molnar <mingo@elte.hu> wrote:
>
> > In any case it would make sense to turn that particular overlap
> > situation into a warning message and disable initrd decompress - and
> > try to boot with whatever is built-in the kernel.
>
> If I explicitely tell my system to load a ramdisk, ignoring it is a
> bug.
we dont really ignore it - we detect that it got corrupted by the
bootloader. (it got overwritten by the kernel image - information has
been destroyed irrevocably)
how we react to that breakage we detect is up to debate: it's fine to
try to continue (presumably a huge vmlinux means it has all the drivers
already) - and if a system relies on an initrd it wont get fast in
bootup anyway.
that's why i suggested to print a warning, do a 5 seconds delay after
that warning via mdelay(5000) so that the user has a chance to notice
what is wrong, and then try to continue. Panicking is just as fine.
Ingo
next prev parent reply other threads:[~2008-09-08 14:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b8P0N-3Dp-11@gated-at.bofh.it>
[not found] ` <b8PaB-3Or-23@gated-at.bofh.it>
[not found] ` <b8Q6x-51x-11@gated-at.bofh.it>
[not found] ` <b961C-rW-9@gated-at.bofh.it>
[not found] ` <b97qL-26L-15@gated-at.bofh.it>
2008-09-07 16:47 ` [2.6.27] overlapping early reservations [was: early exception - lockdep related?] Bodo Eggert
2008-09-08 4:26 ` H. Peter Anvin
2008-09-08 14:30 ` Ingo Molnar [this message]
2008-09-05 19:17 Luca Tettamanti
2008-09-05 19:25 ` Peter Zijlstra
2008-09-05 20:18 ` H. Peter Anvin
2008-09-06 13:20 ` Luca Tettamanti
2008-09-06 14:51 ` Ingo Molnar
2008-09-06 16:06 ` Yinghai Lu
2008-09-08 17:54 ` Luca Tettamanti
2008-09-08 18:04 ` Yinghai Lu
2008-09-08 19:14 ` Luca Tettamanti
2008-09-08 19:35 ` Yinghai Lu
2008-09-08 20:00 ` Luca Tettamanti
2008-09-08 20:46 ` Yinghai Lu
2008-09-08 21:25 ` Luca Tettamanti
2008-09-08 22:32 ` Yinghai Lu
2008-09-09 21:48 ` Luca Tettamanti
2008-09-06 17:20 ` Luca Tettamanti
2008-09-06 17:25 ` Ingo Molnar
2008-09-06 17:29 ` Luca Tettamanti
2008-09-06 13:41 ` Ingo Molnar
2008-09-06 16:14 ` Yinghai Lu
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=20080908143003.GB10580@elte.hu \
--to=mingo@elte.hu \
--cc=7eggert@gmx.de \
--cc=hpa@kernel.org \
--cc=kronos.it@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@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