public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "H. Peter Anvin" <hpa@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Luca Tettamanti <kronos.it@gmail.com>,
	linux-kernel@vger.kernel.org, mingo@redhat.com,
	Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: [2.6.27] overlapping early reservations [was: early exception - lockdep related?]
Date: Sat, 6 Sep 2008 15:41:18 +0200	[thread overview]
Message-ID: <20080906134118.GD4910@elte.hu> (raw)
In-Reply-To: <48C19415.9060108@kernel.org>


* H. Peter Anvin <hpa@kernel.org> wrote:

> Peter Zijlstra wrote:
>> On Fri, 2008-09-05 at 21:17 +0200, Luca Tettamanti wrote:
>>> On Thu, Sep 4, 2008 at 10:51 PM, Luca Tettamanti <kronos.it@gmail.com> wrote:
>>>> On Thu, Sep 4, 2008 at 4:25 PM, Peter Zijlstra <peterz@infradead.org> wrote:
>>>>> Sadly your config just boots, albeit not to userspace due to missing
>>>>> drivers.
>>>> Yes, I managed to boot it with qemu... I tried kgdb - without luck -
>>>> kernel dies too early.
>>>> I also managed to get a stack trace :D
>>>>
>>>> http://img151.imageshack.us/my.php?image=tracedm1.jpg
>>>>
>>>> It seems that lockdep is an innocent bystander... the kernel died with
>>>> panic() in __reserve_early, and then took another exception while
>>>> printing the panic (I guess).
>>>> Will add further debug stuff to see wtf is going on.
>>> Hum, kernel says:
>>>
>>> http://img177.imageshack.us/my.php?image=overlappingus2.jpg
>>>
>>> Overlapping early reservations b98000-eff266 RAMDISK to 200000-d09cf7
>>> TEXT DATA BSS
>>>
>>> It would appear that the initramfs is overlapping the kernel itself,
>>> is the boot loader (LILO) doing something stupid?
>>
>> Suppose it is, lets ask hpa..
>>
>
> It definitely looks like it.

yeah. Kernel is loaded at the standard 2MB physical, and goes up to 
13.6MB physical. That's a tad large at 11.6 MB but still valid.

ramdisk image goes from 11.6 MB to 14.9 MB - roughly standard size. That 
overlaps 2 MB into the kernel image so we have to panic. LILO should 
have loaded the ramdisk somewhere else. (or should have aborted the boot 
if it cannot do that)

We could perhaps print a prominent warning, delay the boot for 5 seconds 
or so via mdelay(5000) and simply not load the ramdisk if this happens? 
The kernel is obviously still functional - and such a large vmlinuz 
likely has all the built-in drivers to boot up to user-space - the lack 
of the ramdisk does not necessarily hurt .

	Ingo

  parent reply	other threads:[~2008-09-06 13:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05 19:17 [2.6.27] overlapping early reservations [was: early exception - lockdep related?] 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 [this message]
2008-09-06 16:14       ` Yinghai Lu
     [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         ` Bodo Eggert
2008-09-08  4:26           ` H. Peter Anvin
2008-09-08 14:30           ` Ingo Molnar

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=20080906134118.GD4910@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@kernel.org \
    --cc=kronos.it@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yhlu.kernel@gmail.com \
    /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