... ignore it for now; I ran some other profiling and then when I
tried schedgraph.d again, it started spitting out events for that CPU.
I'll file a PR if I see it happen more often.
On 26 January 2015 at 12:05, Adrian Chadd <adr...@freebsd.org> wrote:
> I'm having problems with Ryan's schedgraph.d script
> It runs fine, but if a CPU core is 100% busy, I get zero scheduler
> events logged from it. Said core is doing around 30,000 syscalls a
> second, around 250,000 context switches and 125,000 interrupt sa
> second - but whilst it's doing this, I get zero events from dtrace for
> said CPU.
> Has anyone hit this kind of situation before?
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"