mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Jan Beulich <jbeulich@novell.com>, Dave Jones <davej@redhat.com>,
	Jesper Juhl <jesper.juhl@gmail.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] i386: fix one case of stuck dwarf2 unwinder II
Date: Sun, 6 Aug 2006 03:11:56 -0400	[thread overview]
Message-ID: <200608060314_MC3-1-C73C-AEAE@compuserve.com> (raw)

In-Reply-To: <200608060805.06821.ak@suse.de>

On Sun, 6 Aug 2006 08:05:06 +0200, Andi Kleen wrote:

> Hmm, actually I applied it but then I had doubts it actually 
> works -- I think you don't need _stext but the code before
> the first call in head. Since head.S doesn't do a call
> that's probably start_kernel

But head.S does do a call (on i386 but not x86_64 AFAICT):

| #ifdef CONFIG_SMP
|        movb ready, %cl
|        movb $1, ready
|        cmpb $0,%cl
|        je 1f                   # the first CPU calls start_kernel
|                                # all other CPUs call initialize_secondary
|        call initialize_secondary
|        jmp L6
| 1:
| #endif /* CONFIG_SMP */
|        call start_kernel
| L6:
|        jmp L6                  # main should never return here, but
|                                # just in case, we know what happens.

And the backtraces I saw ended up at L6:

| DWARF2 unwinder stuck at 0xc0100210

System.map on i386 SMP says:

| c0100210 t L6

-- 
Chuck


             reply	other threads:[~2006-08-06  7:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-06  7:11 Chuck Ebbert [this message]
2006-08-06 14:04 ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2006-08-06 16:09 Chuck Ebbert
2006-08-07  8:00 ` Jan Beulich
2006-08-07  8:04   ` Andi Kleen
2006-08-15 10:33     ` Jan Beulich
2006-08-15 10:47       ` Andi Kleen
2006-08-15 10:54         ` Jan Beulich
2006-08-06  5:00 [patch] i386: fix one case of stuck dwarf2 unwinder Chuck Ebbert
2006-08-06  6:05 ` [patch] i386: fix one case of stuck dwarf2 unwinder II Andi Kleen

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=200608060314_MC3-1-C73C-AEAE@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=jbeulich@novell.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.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

Powered by JetHome