mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: "Thomas Meyer" <thomas@m3y3r.de>,
	"Dmitry Adamushko" <dmitry.adamushko@gmail.com>,
	"the arch/x86 maintainers" <x86@kernel.org>,
	"Glauber Costa" <gcosta@redhat.com>,
	"Ingo Molnar" <mingo@elte.hu>
Subject: Re: -git: BUG: unable to handle kernel paging request at c0100248 [CPU hotplug]
Date: Sun, 27 Jul 2008 12:07:54 +0200	[thread overview]
Message-ID: <19f34abd0807270307p505568b8nf871162d89b002ef@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0807270255o1ff260a8ucb9d931905aa4947@mail.gmail.com>

On Sun, Jul 27, 2008 at 11:55 AM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
> Hi,
>
> Something broke CPU-hotplug _again_, here with a freshly built latest -git:
>
> BUG: unable to handle kernel paging request at c0100248

[snip]

> c067c3db:       c7 05 48 02 10 c0 f0    movl   $0xc067c9f0,0xc0100248
> c067c3e2:       c9 67 c0
>
> $ addr2line -e vmlinux -i c067c3db
> arch/x86/kernel/smpboot.c:859
> arch/x86/kernel/smpboot.c:993
>
> Hm... that doesn't really make sense, does it? It's this line:
>
>        initial_code = (unsigned long)start_secondary;
>
> ..but I don't see where the memory dereference comes from.

"initial_code" (0xc0100248) is in a .text section:

Idx Name          Size      VMA       LMA       File off  Algn
  0 .text.head    000003a1  c0100000  00100000  00001000  2**2
  1 .text         00583b8d  c01003b0  001003b0  000013b0  2**4

And I have CONFIG_DEBUG_RODATA=y. Maybe this was introduced in

commit e3f77edfc1d0beb7b10f9f31d9e39206f7dbef7b
Author: Glauber Costa <gcosta@redhat.com>
Date:   Wed May 28 12:57:02 2008 -0300

    x86: use initial_code for i386

    x86_64 jumps to whatever is written in "initial_code" symbol,
    instead of a fixed address. Do it for i386 too. It will allow us
    to integrate more of the smp boot code.

    Signed-off-by: Glauber Costa <gcosta@redhat.com>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>

?


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

  reply	other threads:[~2008-07-27 10:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-27  9:55 Vegard Nossum
2008-07-27 10:07 ` Vegard Nossum [this message]
2008-07-27 17:14 ` Dmitry Adamushko
2008-07-27 17:19   ` Vegard Nossum
2008-07-27 19:23     ` Thomas Gleixner
2008-07-27 19:35       ` Vegard Nossum
2008-07-27 19:40         ` Vegard Nossum
2008-07-28 18:34           ` Glauber Costa

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=19f34abd0807270307p505568b8nf871162d89b002ef@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=dmitry.adamushko@gmail.com \
    --cc=gcosta@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=thomas@m3y3r.de \
    --cc=x86@kernel.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

all inboxes | Powered by JetHome®