Date: Sat, 28 Nov 2020 05:50:23 -0800 From: David Wolfskill <david@catwhisker.org> To: current@freebsd.org Subject: Laptop exhibits erratic responsiveness Message-ID: <X8JVn/PIPuLzsWuQ@albert.catwhisker.org>
next in thread | raw e-mail | index | archive | help
--48sZbCI1Kx/r2ZzT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I've delayed trying to send this, as I wasn't clear on how to express it -- and I had hoped that the problem would "go away" before I figured that part out: I first observed it around 09 Nov, which is when I updated the laptop (via in-place source upgrade, as usual) from r367484 to r367517. One of the issues I faced with respect to expressing the nature of the problem was "how to quantify" it. And as I was trying to get some work done on another machine, it ocurred to me that perhaps pinging that other machine might illustrate things adequately, so: g1-48(13.0-C)[17] ping albert PING albert.catwhisker.org (172.16.8.13): 56 data bytes 64 bytes from 172.16.8.13: icmp_seq=3D0 ttl=3D63 time=3D0.511 ms 64 bytes from 172.16.8.13: icmp_seq=3D1 ttl=3D63 time=3D0.667 ms 64 bytes from 172.16.8.13: icmp_seq=3D2 ttl=3D63 time=3D0.537 ms 64 bytes from 172.16.8.13: icmp_seq=3D3 ttl=3D63 time=3D0.618 ms 64 bytes from 172.16.8.13: icmp_seq=3D4 ttl=3D63 time=3D0.647 ms 64 bytes from 172.16.8.13: icmp_seq=3D5 ttl=3D63 time=3D0.538 ms 64 bytes from 172.16.8.13: icmp_seq=3D6 ttl=3D63 time=3D0.538 ms 64 bytes from 172.16.8.13: icmp_seq=3D7 ttl=3D63 time=3D0.543 ms 64 bytes from 172.16.8.13: icmp_seq=3D8 ttl=3D63 time=3D0.571 ms 64 bytes from 172.16.8.13: icmp_seq=3D9 ttl=3D63 time=3D0.500 ms 64 bytes from 172.16.8.13: icmp_seq=3D10 ttl=3D63 time=3D0.618 ms 64 bytes from 172.16.8.13: icmp_seq=3D11 ttl=3D63 time=3D0.548 ms 64 bytes from 172.16.8.13: icmp_seq=3D12 ttl=3D63 time=3D0.532 ms 64 bytes from 172.16.8.13: icmp_seq=3D13 ttl=3D63 time=3D0.532 ms 64 bytes from 172.16.8.13: icmp_seq=3D14 ttl=3D63 time=3D0.613 ms 64 bytes from 172.16.8.13: icmp_seq=3D15 ttl=3D63 time=3D0.593 ms 64 bytes from 172.16.8.13: icmp_seq=3D16 ttl=3D63 time=3D0.501 ms 64 bytes from 172.16.8.13: icmp_seq=3D17 ttl=3D63 time=3D0.630 ms 64 bytes from 172.16.8.13: icmp_seq=3D18 ttl=3D63 time=3D0.556 ms 64 bytes from 172.16.8.13: icmp_seq=3D19 ttl=3D63 time=3D0.566 ms 64 bytes from 172.16.8.13: icmp_seq=3D20 ttl=3D63 time=3D0.642 ms 64 bytes from 172.16.8.13: icmp_seq=3D21 ttl=3D63 time=3D0.611 ms 64 bytes from 172.16.8.13: icmp_seq=3D22 ttl=3D63 time=3D0.628 ms 64 bytes from 172.16.8.13: icmp_seq=3D23 ttl=3D63 time=3D92.473 ms 64 bytes from 172.16.8.13: icmp_seq=3D24 ttl=3D63 time=3D0.647 ms 64 bytes from 172.16.8.13: icmp_seq=3D25 ttl=3D63 time=3D0.483 ms 64 bytes from 172.16.8.13: icmp_seq=3D26 ttl=3D63 time=3D0.476 ms 64 bytes from 172.16.8.13: icmp_seq=3D27 ttl=3D63 time=3D0.561 ms 64 bytes from 172.16.8.13: icmp_seq=3D28 ttl=3D63 time=3D0.560 ms 64 bytes from 172.16.8.13: icmp_seq=3D29 ttl=3D63 time=3D0.599 ms 64 bytes from 172.16.8.13: icmp_seq=3D30 ttl=3D63 time=3D0.677 ms 64 bytes from 172.16.8.13: icmp_seq=3D31 ttl=3D63 time=3D0.563 ms 64 bytes from 172.16.8.13: icmp_seq=3D32 ttl=3D63 time=3D0.609 ms 64 bytes from 172.16.8.13: icmp_seq=3D33 ttl=3D63 time=3D0.558 ms 64 bytes from 172.16.8.13: icmp_seq=3D34 ttl=3D63 time=3D0.527 ms 64 bytes from 172.16.8.13: icmp_seq=3D35 ttl=3D63 time=3D0.610 ms 64 bytes from 172.16.8.13: icmp_seq=3D36 ttl=3D63 time=3D0.621 ms 64 bytes from 172.16.8.13: icmp_seq=3D37 ttl=3D63 time=3D0.501 ms 64 bytes from 172.16.8.13: icmp_seq=3D38 ttl=3D63 time=3D68482.244 ms 64 bytes from 172.16.8.13: icmp_seq=3D39 ttl=3D63 time=3D0.672 ms 64 bytes from 172.16.8.13: icmp_seq=3D40 ttl=3D63 time=3D0.635 ms 64 bytes from 172.16.8.13: icmp_seq=3D41 ttl=3D63 time=3D0.585 ms 64 bytes from 172.16.8.13: icmp_seq=3D42 ttl=3D63 time=3D0.629 ms 64 bytes from 172.16.8.13: icmp_seq=3D43 ttl=3D63 time=3D0.566 ms 64 bytes from 172.16.8.13: icmp_seq=3D44 ttl=3D63 time=3D0.641 ms 64 bytes from 172.16.8.13: icmp_seq=3D45 ttl=3D63 time=3D0.638 ms 64 bytes from 172.16.8.13: icmp_seq=3D46 ttl=3D63 time=3D0.645 ms 64 bytes from 172.16.8.13: icmp_seq=3D47 ttl=3D63 time=3D0.540 ms 64 bytes from 172.16.8.13: icmp_seq=3D48 ttl=3D63 time=3D0.487 ms 64 bytes from 172.16.8.13: icmp_seq=3D49 ttl=3D63 time=3D13.063 ms 64 bytes from 172.16.8.13: icmp_seq=3D50 ttl=3D63 time=3D0.567 ms 64 bytes from 172.16.8.13: icmp_seq=3D51 ttl=3D63 time=3D0.487 ms 64 bytes from 172.16.8.13: icmp_seq=3D52 ttl=3D63 time=3D0.428 ms 64 bytes from 172.16.8.13: icmp_seq=3D53 ttl=3D63 time=3D0.692 ms 64 bytes from 172.16.8.13: icmp_seq=3D54 ttl=3D63 time=3D0.605 ms 64 bytes from 172.16.8.13: icmp_seq=3D55 ttl=3D63 time=3D0.630 ms 64 bytes from 172.16.8.13: icmp_seq=3D56 ttl=3D63 time=3D0.561 ms 64 bytes from 172.16.8.13: icmp_seq=3D57 ttl=3D63 time=3D0.634 ms 64 bytes from 172.16.8.13: icmp_seq=3D58 ttl=3D63 time=3D0.571 ms 64 bytes from 172.16.8.13: icmp_seq=3D59 ttl=3D63 time=3D0.577 ms 64 bytes from 172.16.8.13: icmp_seq=3D60 ttl=3D63 time=3D0.592 ms 64 bytes from 172.16.8.13: icmp_seq=3D61 ttl=3D63 time=3D0.455 ms 64 bytes from 172.16.8.13: icmp_seq=3D62 ttl=3D63 time=3D0.585 ms 64 bytes from 172.16.8.13: icmp_seq=3D63 ttl=3D63 time=3D0.548 ms 64 bytes from 172.16.8.13: icmp_seq=3D64 ttl=3D63 time=3D0.443 ms 64 bytes from 172.16.8.13: icmp_seq=3D65 ttl=3D63 time=3D0.584 ms 64 bytes from 172.16.8.13: icmp_seq=3D66 ttl=3D63 time=3D0.592 ms ^C --- albert.catwhisker.org ping statistics --- 67 packets transmitted, 67 packets received, 0.0% packet loss round-trip min/avg/max/stddev =3D 0.428/1024.248/68482.244/8303.513 ms g1-48(13.0-C)[18]=20 Please note that no packets are dropped, and that most exhibit an RTT of around 0.6 ms, and that no packets are dropped -- which is ... good, as far as that goes. (The laptop is presently using a wired Ethernet (em0) link, as "wireless" doesn't play well with significant lags in response time, or so it appears to me.) But packet 23 shows a hint of something gone awry, and packet 38 ... something's gone walkabout, and is in no hurry to return. While the above "ping" was done during the upgrade from r368097 to r368119, I have observed similar effects when the machine was idle (but running head). I do NOT observe these effects when the machine is running stable/12 (also tracked/updated daily), nor have I seen the behavior on other machines (my build machine, which also tracks head and stable/12 daily; various machines at work, which generally track head about every 4 - 5 weeks). Any ideas for tracking this down? I have documented various aspects of what process I use to track/uodate the machines, the environment, and the history of the tracking: * http://www.catwhisker.org/~david/FreeBSD/upgrade.html * http://www.catwhisker.org/~david/FreeBSD/history/ Thanks! Peace, david --=20 David H. Wolfskill david@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. --48sZbCI1Kx/r2ZzT Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE4owz2QxMJyaxAefyQLJg+bY2PckFAl/CVZ9fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUy OEMzM0Q5MEM0QzI3MjZCMTAxRTdGMjQwQjI2MEY5QjYzNjNEQzkACgkQQLJg+bY2 PclHHQgAugzyOA5sdTF+R/1SLXOmsWNFwRvjATU6eYdQEzLq3xRqmpe8/kluXiiY XrI7zK1gJWVWfrfG31m1kEc7bHY7Z5Pv31/DKxFcIAZUYnnZXi5lk3csyVzgl/+S qoITjV0ZKx1uJeBNXmtoU2GMhm8FmckHF41Vlc+GPGPpWpbfIhhOMg/BUVm8Tk0B wDJR8etcJ6EKA6FWROog3Xkd1gBLjHgOebkEiMOTOIWOOkpt3Ao3GJc5T+Zn4dBe yqMXvjRJYxZLzFT0WzywtTxapS7Ggnb4LYLF0M/SZMRmFDSPtDFT0R5EKeeHvNLl tU+5FUv3NJ4+0Eu9/X+14MlLGqJWzg== =tEk3 -----END PGP SIGNATURE----- --48sZbCI1Kx/r2ZzT--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?X8JVn/PIPuLzsWuQ>