[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100401090608.GD5207@nowhere>
Date: Thu, 1 Apr 2010 11:06:11 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: David Miller <davem@...emloft.net>
Cc: linux-kernel@...r.kernel.org, sparclinux@...r.kernel.org
Subject: Re: [BUG] fault while using perf callchains in sparc64
On Mon, Mar 29, 2010 at 03:32:08PM -0700, David Miller wrote:
> From: Frederic Weisbecker <fweisbec@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists