On 9/3/23, Graham Perrin <grahamper...@gmail.com> wrote: > On 03/09/2023 17:55, Mateusz Guzik wrote: >> On 9/3/23, Graham Perrin <grahamper...@gmail.com> wrote: >>> On 02/09/2023 18:31, Mateusz Guzik wrote: >>>> On 9/2/23, Graham Perrin<grahamper...@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 >>> >> Post your "sysctl -a" somewhere. >> > sysctl-a-2023-09-03-18-22.txt added to the MEGA folder is complete, > including TSLOG-related lines. > > Alternatively, tslog under > <https://bsd-hardware.info/?probe=d240fba8b7#Logs> is automatically > pruned to exclude such lines. Hopefully not excessively pruned. > > TSLOG is one of three things in a Git stash that I apply before most > builds, <https://reviews.freebsd.org/P601>. >
Sorry mate, neglected to specify: collect sysctl -a once you run into the problem. Once I look at that I'm probably going to ship some debug patches to narrow it down. -- Mateusz Guzik <mjguzik gmail.com>
