On Tue, Jun 24, 2014 at 11:38:44AM -0600, David Ahern wrote: > On 6/24/14, 10:57 AM, Stanislav Fomichev wrote: > >On Tue, Jun 24, 2014 at 01:10:22PM +0400, Stanislav Fomichev wrote: > >>>hum, got this when trying: > >>> > >>>[jolsa@krava perf]$ sudo ./perf timechart record -I > >>>^C[ perf record: Woken up 2 times to write data ] > >>>[ perf record: Captured and wrote 1.071 MB perf.data (~46806 samples) ] > >>>[jolsa@krava perf]$ ./perf timechart > >>>Invalid previous event (non-zero)! > >>>0x113f80 [0x8]: failed to process type: 68 > > I see this kind of message a lot, but typically in high event use cases > (e.g., 100+MB files in a run of a few seconds). I usually increase the map > size (-m 4096) and/or bump the priority of perf (-r1) and re-run the test.
maybe we dont need to fail in this case.. seems like it should not be hard to detect, wanr and recover? ;-) jirka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
