From: Mike Travis <travis@sgi.com>
To: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
Cc: sfr@canb.auug.org.au, Ingo Molnar <mingo@elte.hu>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: x86_64 does not boot in Qemu
Date: Thu, 01 May 2008 04:35:31 -0700 [thread overview]
Message-ID: <4819AB03.3030808@sgi.com> (raw)
In-Reply-To: <48191E75.70305@gmail.com>
Hi Dmitri,
There are 3 "fix" patches after this one (sorry about that).
http://marc.info/?l=linux-kernel&m=120941725114635&w=4
http://marc.info/?l=linux-kernel&m=120949583029044&w=4
http://marc.info/?l=linux-kernel&m=120956778620842&w=4
Checking out the "latest" sched/latest it appears though that the
entire patchset has been removed. I'll wait for Ingo's feedback
on what's up.
I will also try out your example test.
Thanks,
Mike
Dmitri Vorobiev wrote:
> Hi Stephen, Mike, Ingo,
>
> Starting from
>
>
> [dmitri.vorobiev@amber linux-2.6]$ git bisect good
> 66c38e394e8c178c806266bb213f1087cd182701 is first bad commit
> commit 66c38e394e8c178c806266bb213f1087cd182701
> Author: Mike Travis <travis@sgi.com>
> Date: Mon Apr 28 14:09:07 2008 -0700
>
> x86: remove static boot_cpu_pda array v2
>
> * Remove the boot_cpu_pda array and pointer table from the data section.
> Allocate the pointer table and array during init. do_boot_cpu()
> will reallocate the pda in node local memory and if the cpu is being
> brought up before the bootmem array is released (after_bootmem = 0),
> then it will free the initial pda. This will happen for all cpus
> present at system startup.
>
> This removes 512k + 32k bytes from the data section.
>
> For inclusion into sched-devel/latest tree.
>
> Based on:
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> + sched-devel/latest .../mingo/linux-2.6-sched-devel.git
>
> Signed-off-by: Mike Travis <travis@sgi.com>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
> <<<<
>
> the x86_64 kernel stopped booting for me. The symptom is that no output
> whatsoever is produced after the following command:
>
>
> qemu-0.9.1/bin/qemu-system-x86_64 image_64.raw \
> -kernel src/linux-2.6/arch/x86/boot/bzImage \
> -append "console=ttyS0 root=/dev/hda1 ro" -nographic \
> -redir tcp:2222::22 -m 512
>
> <<<<
>
> Qemu just hangs seemingly doing nothing. Normally, the usual boot log is
> displayed.
>
> Bisection on linux-next leads to the commit given above. Config attached.
>
> Thanks,
> Dmitri
>
next prev parent reply other threads:[~2008-05-01 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 1:35 linux-next: x86_64 does not boot in Qemu Dmitri Vorobiev
2008-05-01 11:35 ` Mike Travis [this message]
2008-05-03 18:16 ` 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=4819AB03.3030808@sgi.com \
--to=travis@sgi.com \
--cc=dmitri.vorobiev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
/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