On Sun, Nov 29, 2020 at 11:04:46AM -0500, Ryan Stone wrote: > On Sun, Nov 29, 2020 at 9:12 AM David Wolfskill <da...@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)
Thanks; the laptop is presently running head @r368143, building head @r367410 (which is gthe last point before the issues were observed, I think), so I have fired that up. Peace, david -- David H. Wolfskill da...@catwhisker.org "Make America Great Again," he said -- and THIS is what he did??!? See http://www.catwhisker.org/~david/publickey.gpg for my public key.
signature.asc
Description: PGP signature
