From: Ingo Molnar <mingo@elte•hu>
To: Alexander Beregalov <a.beregalov@gmail•com>
Cc: linux-next@vger•kernel.org,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
tglx@linutronix•de, mingo@redhat•com, hpa@zytor•com
Subject: Re: next-0704: x86_64 panics on booting
Date: Fri, 4 Jul 2008 16:24:09 +0200 [thread overview]
Message-ID: <20080704142409.GA18824@elte.hu> (raw)
In-Reply-To: <a4423d670807040720o3e8e350ds5c13dfca8e8adc58@mail.gmail.com>
* Alexander Beregalov <a.beregalov@gmail•com> wrote:
> Hi
>
>
> Booting the kernel.
>
> Kernel alive
> Kernel really alive
> PANIC: early exception 0e rip 10:ffffffff80604f47 error 2 cr2 ffffffffff300000
>
> It is x86_64 SMP (opteron).
does the patch below fix it?
Ingo
-------------->
commit 181b3601a1a7d2ac3ace6b23cb3204450a4f9a27
Author: Jeremy Fitzhardinge <jeremy@goop•org>
Date: Sun Jun 29 20:02:44 2008 -0700
x86: setup_arch() && early_ioremap_init()
Looks like the setup.c unification missed the early_ioremap init from
the early_ioremap unification. Unconditionally call early_ioremap_init().
needed for "x86/paravirt: groundwork for 64-bit Xen support".
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix•com>
Cc: Nick Piggin <npiggin@suse•de>
Cc: Mark McLoughlin <markmc@redhat•com>
Cc: xen-devel <xen-devel@lists•xensource.com>
Cc: Eduardo Habkost <ehabkost@redhat•com>
Cc: Vegard Nossum <vegard.nossum@gmail•com>
Cc: Stephen Tweedie <sct@redhat•com>
Cc: Yinghai Lu <yhlu.kernel@gmail•com>
Signed-off-by: Ingo Molnar <mingo@elte•hu>
diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index fb318ed..caec79f 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -523,12 +523,13 @@ void __init setup_arch(char **cmdline_p)
memcpy(&boot_cpu_data, &new_cpu_data, sizeof(new_cpu_data));
pre_setup_arch_hook();
early_cpu_init();
- early_ioremap_init();
reserve_setup_data();
#else
printk(KERN_INFO "Command line: %s\n", boot_command_line);
#endif
+ early_ioremap_init();
+
ROOT_DEV = old_decode_dev(boot_params.hdr.root_dev);
screen_info = boot_params.screen_info;
edid_info = boot_params.edid_info;
next prev parent reply other threads:[~2008-07-04 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 14:20 next-0704: x86_64 panics on booting Alexander Beregalov
2008-07-04 14:24 ` Ingo Molnar [this message]
2008-07-04 14:53 ` Alexander Beregalov
2008-07-04 14:30 ` Stephen Rothwell
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=20080704142409.GA18824@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=a.beregalov@gmail$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@redhat$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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