All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	kernel list <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Suspected regression in "x86: extend e820 ealy_res support 32bit"
Date: Wed, 21 May 2008 23:01:01 +0100	[thread overview]
Message-ID: <48349B9D.1000501@goop.org> (raw)
In-Reply-To: <86802c440805211335q27334ba1g32a43fb1c0498b9b@mail.gmail.com>

Yinghai Lu wrote:
> On Wed, May 21, 2008 at 11:19 AM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>   
>> I'm seeing a crash in current x86.git tip/auto-latest when booting under
>> Xen.  The crash is rather early, but it's in __alloc_bootmem_core() in the
>> final memset clear.  Apparently the allocator is returning a bad page.
>>
>> This points to changes in the setup of the bootmem allocator, and the
>> changes "x86: extend e820 ealy_res support 32bit" make to
>> arch/x86/kernel/setup_32.c:setup_bootmem_allocator() looks like the most
>> likely suspect.  Unfortunately its a rather large patch which is not easy to
>> revert, so I haven't actually confirmed this yet.
>>     
>
>
> thanks. please check the attached patch
>   

Thanks for the quick response.  I definitely confirmed that "x86: extend 
e820 ealy_res support 32bit" is the source of the regression, and 
reverting the change makes the system bootable under Xen. (My previous 
reversion failed because I didn't actually have the x86.git changes 
applied :-/)

This patch generates the warning:

      CC      arch/x86/kernel/setup_32.o
    /home/jeremy/hg/xen/paravirt/linux/arch/x86/kernel/setup_32.c: In
    function ‘setup_arch’:
    /home/jeremy/hg/xen/paravirt/linux/arch/x86/kernel/setup_32.c:580:
    warning: ‘bootmap_size’ is used uninitialized in this function

but I think it's just that the panic() message still uses it before its 
assigned.

Hm, and it also fails to fix the problem.  I'm still seeing the virtual 
machine crash in the same way.

Thanks,
    J

  reply	other threads:[~2008-05-21 22:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <483467CD.90401@goop.org>
2008-05-21 20:35 ` Suspected regression in "x86: extend e820 ealy_res support 32bit" Yinghai Lu
2008-05-21 22:01   ` Jeremy Fitzhardinge [this message]
2008-05-21 22:40     ` Yinghai Lu
2008-05-21 23:23       ` Jeremy Fitzhardinge
2008-05-22  1:43         ` Yinghai Lu
2008-05-21 23:14   ` Johannes Weiner
2008-05-21 23:23     ` 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=48349B9D.1000501@goop.org \
    --to=jeremy@goop.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.