Date: Sun, 29 Nov 2020 11:04:46 -0500 From: Ryan Stone <rysto32@gmail.com> To: David Wolfskill <david@catwhisker.org>, Jonathan Looney <jonlooney@gmail.com>, FreeBSD Current <current@freebsd.org> Subject: Re: Laptop exhibits erratic responsiveness Message-ID: <CAFMmRNwo12zPRu7tkSJw56ng-%2Bcp4Zifattrx5WRszOJai_GNA@mail.gmail.com> In-Reply-To: <X8OsLaVToS1V1zoX@albert.catwhisker.org> References: <X8JVn/PIPuLzsWuQ@albert.catwhisker.org> <CADrOrms8fmf9asttPw%2B4B%2BKL7A4svAKx0dDHSuDnEVvxGWiX0Q@mail.gmail.com> <X8OsLaVToS1V1zoX@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 29, 2020 at 9:12 AM David Wolfskill <david@catwhisker.org> wrote: > OK, and demonstrated some long RTTs about every 11 packets or so, but we > see thing come to a screeching halt with: > > ... > 64 bytes from 172.16.8.13: icmp_seq=534 ttl=63 time=0.664 ms > lockstat: dtrace_status(): Abort due to systemic unresponsiveness > 64 bytes from 172.16.8.13: icmp_seq=535 ttl=63 time=9404.383 ms > > and we get no lockstat output. :-/ I believe that if you run lockstat with the additional "-x destructive" option, it will disable the responsiveness test (the option does sound scary but it will not have any other potentially destructive effect)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNwo12zPRu7tkSJw56ng-%2Bcp4Zifattrx5WRszOJai_GNA>