From: Frederic Weisbecker <fweisbec@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [BUG] fault while using perf callchains in sparc64
Date: Thu, 01 Apr 2010 08:06:41 +0000 [thread overview]
Message-ID: <20100401090608.GD5207@nowhere> (raw)
In-Reply-To: <20100329.153208.190256896.davem@davemloft.net>
On Mon, Mar 29, 2010 at 03:32:08PM -0700, David Miller wrote:
> From: Frederic Weisbecker <fweisbec@gmail.com>
> Date: Tue, 30 Mar 2010 00:21:34 +0200
>
> > $ ldd /usr/bin/as
> > libopcodes-2.18.0.20080103.so => /usr/lib/libopcodes-2.18.0.20080103.so (0xf7ec4000)
> > libbfd-2.18.0.20080103.so => /usr/lib/libbfd-2.18.0.20080103.so (0xf7e14000)
> > libc.so.6 => /lib/libc.so.6 (0xf7ca0000)
> > /lib/ld-linux.so.2 (0xf7efc000)
>
> Ok, same here.
>
> > The last kernel I know that don't have such problems is 2.6.31-rc6
> > May be I should bisect?
>
> Hmmm, since you know a good and bad point, yes a bisect
> might be the best way to proceed here.
>
> It might be quicker if you first test 2.6.32 and 2.6.33
> and then use the results of that to guide your bisect.
>
> Anyways, if you narrow it down to a commit I should be
> able to fix this quickly.
>
> Thanks!
I actually can't. It works well on a backup 2.6.31-rc6 kernel
but when I build a new one of this same version, the problem
happens again. And I don't have the config of the one that works
(and no /proc/config.gz as well).
So I suspect this is something that happens with some specific
configs only.
Anyway, once I get more clues about this, I'll tell you.
Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Frederic Weisbecker <fweisbec@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [BUG] fault while using perf callchains in sparc64
Date: Thu, 1 Apr 2010 11:06:11 +0200 [thread overview]
Message-ID: <20100401090608.GD5207@nowhere> (raw)
In-Reply-To: <20100329.153208.190256896.davem@davemloft.net>
On Mon, Mar 29, 2010 at 03:32:08PM -0700, David Miller wrote:
> From: Frederic Weisbecker <fweisbec@gmail.com>
> Date: Tue, 30 Mar 2010 00:21:34 +0200
>
> > $ ldd /usr/bin/as
> > libopcodes-2.18.0.20080103.so => /usr/lib/libopcodes-2.18.0.20080103.so (0xf7ec4000)
> > libbfd-2.18.0.20080103.so => /usr/lib/libbfd-2.18.0.20080103.so (0xf7e14000)
> > libc.so.6 => /lib/libc.so.6 (0xf7ca0000)
> > /lib/ld-linux.so.2 (0xf7efc000)
>
> Ok, same here.
>
> > The last kernel I know that don't have such problems is 2.6.31-rc6
> > May be I should bisect?
>
> Hmmm, since you know a good and bad point, yes a bisect
> might be the best way to proceed here.
>
> It might be quicker if you first test 2.6.32 and 2.6.33
> and then use the results of that to guide your bisect.
>
> Anyways, if you narrow it down to a commit I should be
> able to fix this quickly.
>
> Thanks!
I actually can't. It works well on a backup 2.6.31-rc6 kernel
but when I build a new one of this same version, the problem
happens again. And I don't have the config of the one that works
(and no /proc/config.gz as well).
So I suspect this is something that happens with some specific
configs only.
Anyway, once I get more clues about this, I'll tell you.
Thanks.
next prev parent reply other threads:[~2010-04-01 8:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 4:34 [BUG] fault while using perf callchains in sparc64 Frederic Weisbecker
2010-03-28 4:34 ` Frederic Weisbecker
2010-03-29 2:02 ` David Miller
2010-03-29 2:02 ` David Miller
2010-03-29 3:23 ` Frederic Weisbecker
2010-03-29 3:23 ` Frederic Weisbecker
2010-03-29 19:56 ` David Miller
2010-03-29 19:56 ` David Miller
2010-03-29 20:09 ` David Miller
2010-03-29 20:09 ` David Miller
2010-03-29 20:49 ` Frederic Weisbecker
2010-03-29 20:49 ` Frederic Weisbecker
2010-03-29 21:01 ` David Miller
2010-03-29 21:01 ` David Miller
2010-03-29 21:11 ` Frederic Weisbecker
2010-03-29 21:11 ` Frederic Weisbecker
2010-03-29 21:19 ` David Miller
2010-03-29 21:19 ` David Miller
2010-03-29 21:28 ` Frederic Weisbecker
2010-03-29 21:28 ` Frederic Weisbecker
2010-03-29 22:02 ` David Miller
2010-03-29 22:02 ` David Miller
2010-03-29 22:21 ` Frederic Weisbecker
2010-03-29 22:21 ` Frederic Weisbecker
2010-03-29 22:32 ` David Miller
2010-03-29 22:32 ` David Miller
2010-04-01 8:06 ` Frederic Weisbecker [this message]
2010-04-01 9:06 ` Frederic Weisbecker
2010-04-01 8:09 ` David Miller
2010-04-01 8:09 ` David Miller
2010-04-01 8:46 ` Frederic Weisbecker
2010-04-01 9:38 ` Frederic Weisbecker
2010-04-01 9:02 ` David Miller
2010-04-01 9:02 ` David Miller
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=20100401090608.GD5207@nowhere \
--to=fweisbec@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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 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.