On 9/3/13 7:45 AM, David Ahern wrote:
On 9/3/13 7:24 AM, Adrian Hunter wrote:
On 03/09/13 15:50, David Ahern wrote:
Kernel version? Is your kernel side support there?
The kernel version is the same as the perf version i.e. 3.9
For me data was collected on 2.6.34 about a week ago. Processed
On 9/3/13 7:24 AM, Adrian Hunter wrote:
On 03/09/13 15:50, David Ahern wrote:
Kernel version? Is your kernel side support there?
The kernel version is the same as the perf version i.e. 3.9
For me data was collected on 2.6.34 about a week ago. Processed fine up to
the point of this patch get
On 03/09/13 15:50, David Ahern wrote:
> On 9/3/13 12:40 AM, Adrian Hunter wrote:
>> On 03/09/13 00:37, David Ahern wrote:
>>> Arnaldo/Adrian:
>>>
>>> Latest acme core tree fails to parse an existing data file:
>>>
>>> $ perf trace -i perf.data
>>> 0x16b8 [0x40]: failed to process type: 1
>>> Failed
On 9/3/13 12:40 AM, Adrian Hunter wrote:
On 03/09/13 00:37, David Ahern wrote:
Arnaldo/Adrian:
Latest acme core tree fails to parse an existing data file:
$ perf trace -i perf.data
0x16b8 [0x40]: failed to process type: 1
Failed to process events, error -22
I can't reproduce this. The follo
On 03/09/13 00:37, David Ahern wrote:
> Arnaldo/Adrian:
>
> Latest acme core tree fails to parse an existing data file:
>
> $ perf trace -i perf.data
> 0x16b8 [0x40]: failed to process type: 1
> Failed to process events, error -22
I can't reproduce this. The following works:
$ perf --v
Arnaldo/Adrian:
Latest acme core tree fails to parse an existing data file:
$ perf trace -i perf.data
0x16b8 [0x40]: failed to process type: 1
Failed to process events, error -22
git bisect traced it to:
$ git bisect bad
75562573bab35b129cfd342fc2bcf89da84a6644 is the first bad commit
commit 75
6 matches
Mail list logo
