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: Tue, 30 Mar 2010 00:21:34 +0200 [thread overview]
Message-ID: <20100329222132.GB12254@nowhere> (raw)
In-Reply-To: <20100329.150253.11262563.davem@davemloft.net>
On Mon, Mar 29, 2010 at 03:02:53PM -0700, David Miller wrote:
> From: Frederic Weisbecker <fweisbec@gmail.com>
> Date: Mon, 29 Mar 2010 23:28:42 +0200
>
> > It's a Niagara 2 based one.
>
> Strange, that's what I do all of my main sparc64 kernel
> work on too. I've never seen these spurious 'as' crashes.
>
> Hmmmm, what does "ldd /usr/bin/as" give you?
>
> Thanks.
$ 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)
The last kernel I know that don't have such problems is 2.6.31-rc6
May be I should bisect?
next prev parent reply other threads:[~2010-03-29 22:21 UTC|newest]
Thread overview: 17+ 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-29 2:02 ` David Miller
2010-03-29 3:23 ` Frederic Weisbecker
2010-03-29 19:56 ` David Miller
2010-03-29 20:09 ` David Miller
2010-03-29 20:49 ` Frederic Weisbecker
2010-03-29 21:01 ` David Miller
2010-03-29 21:11 ` Frederic Weisbecker
2010-03-29 21:19 ` David Miller
2010-03-29 21:28 ` Frederic Weisbecker
2010-03-29 22:02 ` David Miller
2010-03-29 22:21 ` Frederic Weisbecker [this message]
2010-03-29 22:32 ` David Miller
2010-04-01 9:06 ` Frederic Weisbecker
2010-04-01 8:09 ` David Miller
2010-04-01 9:38 ` Frederic Weisbecker
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=20100329222132.GB12254@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox