From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
Cc: Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Floating point exception by perf record
Date: Wed, 7 Apr 2010 07:38:55 -0300 [thread overview]
Message-ID: <20100407103855.GC3908@ghostprotocols.net> (raw)
In-Reply-To: <4BBC4318.1070702@dcl.info.waseda.ac.jp>
Em Wed, Apr 07, 2010 at 05:32:24PM +0900, Hitoshi Mitake escreveu:
> On 04/06/10 03:31, Arnaldo Carvalho de Melo wrote:
> > Em Sun, Apr 04, 2010 at 05:10:57PM +0900, Hitoshi Mitake escreveu:
> > [root@doppio ~]# perf lock report | head -3
> > Warning: Error: expected 'data' but read 'overwrite'
> > ID Name acquired contended
> total wait (ns) max wait (ns) min wait (ns)
> >
> > 0xffff8800029d4b28&q->lock 0 0 0
> 0 0
> > [root@doppio ~]#
> >
> > My system details:
> >
> > [root@doppio ~]# uname -a
> > Linux doppio.ghostprotocols.net 2.6.34-rc3-tip+ #1 SMP Mon Apr 5
> 13:49:42 BRT 2010 x86_64 x86_64 x86_64 GNU/Linux
> > [root@doppio ~]# rpm -q newt
> > newt-0.52.10-4.fc11.x86_64
> > [root@doppio ~]#
> >
> > No segfaults here :-\
> >
> > - Arnaldo
> >
>
> I tested perf lock trace and got a similar error (but different).
> % sudo ./perf lock trace
> Fatal: reading input file (size expected=3 received=0)
> It seems that perf.data is broken :( I'll search the cause.
Take a look at:
http://git.kernel.org/?p=linux/kernel/git/acme/linux-2.6.git;a=summary
"perf" branch, there is at least one fix there, the "overwrite" one.
- Arnaldo
next prev parent reply other threads:[~2010-04-07 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 8:10 Floating point exception by perf record Hitoshi Mitake
2010-04-05 18:31 ` Arnaldo Carvalho de Melo
2010-04-07 8:32 ` Hitoshi Mitake
2010-04-07 10:38 ` Arnaldo Carvalho de Melo [this message]
2010-04-08 6:46 ` Hitoshi Mitake
2010-04-08 7:29 ` Hitoshi Mitake
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=20100407103855.GC3908@ghostprotocols.net \
--to=acme@infradead.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=paulus@samba.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