All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
	"Eric Rannaud" <eric.rannaud@gmail.com>,
	"Andrew Morton" <akpm@osdl.org>,
	"Linus Torvalds" <torvalds@osdl.org>,
	"Chandra Seetharaman" <sekharan@us.ibm.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	nagar@watson.ibm.com
Subject: Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
Date: Wed, 4 Oct 2006 12:52:48 +0200	[thread overview]
Message-ID: <200610041252.48721.ak@suse.de> (raw)
In-Reply-To: <45239A38.76E4.0078.0@novell.com>


> >> > [  138.751306]  [<ffffffff8021ecc0>] search_extable+0x40/0x70
> >
> >After here the unwinder seems to become a bit and it shouldn't print
> >multiple entries. Jan any ideas why?
> 
> Not without raw stack contents.

I suppose those are lost in time. 

Unfortunately lockdep doesn't even print stack contents because it doesn't
save them.
 
> >Proposed patch appended. Jan, what do you think?
> 
> As said above - I thought we added zero-termination already.

For head.S but not for kernel_thread I think. At least I can't
find any existing code for kernel_thread().

-Andi

  reply	other threads:[~2006-10-04 10:53 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-30 19:20 BUG-lockdep and freeze (was: Arrr! Linux 2.6.18) Eric Rannaud
2006-09-30 19:49 ` Peter Zijlstra
2006-09-30 20:23   ` Linus Torvalds
2006-09-30 20:57   ` Eric Rannaud
2006-09-30 19:54 ` Linus Torvalds
2006-09-30 20:21   ` Al Viro
2006-09-30 20:28     ` Linus Torvalds
2006-09-30 20:30   ` Andi Kleen
2006-09-30 20:47     ` Linus Torvalds
2006-09-30 20:49       ` Ingo Molnar
2006-09-30 21:11         ` Linus Torvalds
2006-09-30 21:25           ` Ingo Molnar
2006-09-30 21:57           ` Andi Kleen
2006-09-30 22:09             ` BUG-lockdep and freeze (was: Arrr! Linux 2.6.18) II Andi Kleen
2006-09-30 22:19               ` Eric Rannaud
2006-09-30 22:24                 ` Andi Kleen
2006-09-30 22:54             ` BUG-lockdep and freeze (was: Arrr! Linux 2.6.18) Linus Torvalds
2006-10-04  9:21           ` Jan Beulich
2006-10-04 15:12             ` Linus Torvalds
2006-09-30 21:43     ` Eric Rannaud
2006-09-30 22:03       ` Andi Kleen
2006-09-30 21:56     ` Linus Torvalds
2006-09-30 22:02       ` Andi Kleen
2006-09-30 22:10         ` Ingo Molnar
2006-09-30 22:23           ` Andi Kleen
2006-09-30 22:55         ` Linus Torvalds
2006-09-30 22:59           ` Linus Torvalds
2006-09-30 23:56           ` Andi Kleen
2006-10-01  0:25             ` Linus Torvalds
2006-10-01  0:51               ` Linus Torvalds
2006-10-01  9:27                 ` Andi Kleen
2006-10-04  9:25     ` Jan Beulich
2006-10-04 10:52       ` Andi Kleen [this message]
2006-10-04 11:58         ` Jan Beulich
2006-10-04 12:03           ` Andi Kleen
2006-10-04 12:10             ` Jan Beulich
2006-09-30 20:43   ` Linus Torvalds
2006-10-04  9:15   ` Jan Beulich
2006-09-30 20:13 ` Andrew Morton
2006-09-30 20:52   ` Eric Rannaud
2006-09-30 21:04     ` Andrew Morton
2006-09-30 22:00       ` Eric Rannaud
2006-09-30 22:05         ` Ingo Molnar
2006-10-01  0:59           ` Eric Rannaud

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=200610041252.48721.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=eric.rannaud@gmail.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nagar@watson.ibm.com \
    --cc=sekharan@us.ibm.com \
    --cc=torvalds@osdl.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 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.