Date: Sun, 3 Sep 2023 17:02:56 +0100 From: Graham Perrin <grahamperrin@gmail.com> To: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: kernel 100% CPU Message-ID: <23c596e7-d710-c17d-a4e7-b21c99a4fe00@gmail.com> In-Reply-To: <CAGudoHEhNG2e2J7Cb2w0EKZ7p_cdq0hie_s67AHCj7x8hfw8SA@mail.gmail.com> References: <95e9f65b-58c4-ef3a-a5d1-b794179e4252@gmail.com> <CAGudoHG%2B4wT-MCP=zE4VqdJYJwTKSLf8GfARvQbGwKZw%2Bz8F_g@mail.gmail.com> <d2e5951a-7c6c-f450-eacc-d8e4f6446118@gmail.com> <CAGudoHEhNG2e2J7Cb2w0EKZ7p_cdq0hie_s67AHCj7x8hfw8SA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/09/2023 18:31, Mateusz Guzik wrote: > On 9/2/23, Graham Perrin<grahamperrin@gmail.com> wrote: >> … I began the trace /after/ the issue became observable. >> Will it be more meaningful to begin a trace and then reproduce the issue >> (before the trace ends)? >> >> … > Looks like you have a lot of unrelated traffic in there. > > … Instead, <https://mega.nz/folder/dQdgXK4K#Eb-uC02fT63eweQWWwD8TA>; the two files from 09:21 this morning. Are these useful? Before this run of DTrace, I quit Firefox and other applications that might be causing noise (and the OS has been restarted since my last run of poudriere-bulk(8)). dtrace -x stackframes=100 -n 'profile-997 /arg0/ { @[stack()] = count(); } tick-60s { exit(0); }' -o out.kern_stacks
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23c596e7-d710-c17d-a4e7-b21c99a4fe00>