Date: Mon, 30 Nov 2020 04:45:55 -0800 From: David Wolfskill <david@catwhisker.org> To: Mateusz Guzik <mjguzik@gmail.com> Cc: current@freebsd.org Subject: Re: Laptop exhibits erratic responsiveness Message-ID: <X8Tpg1P%2BXQc7iTNJ@albert.catwhisker.org> In-Reply-To: <CAGudoHHevDxuvwLO2QMrMNfvG0vWSU=v9gHLbH0eMFDt8p0FWg@mail.gmail.com> References: <X8JVn/PIPuLzsWuQ@albert.catwhisker.org> <CADrOrms8fmf9asttPw%2B4B%2BKL7A4svAKx0dDHSuDnEVvxGWiX0Q@mail.gmail.com> <X8OsLaVToS1V1zoX@albert.catwhisker.org> <CAGudoHHevDxuvwLO2QMrMNfvG0vWSU=v9gHLbH0eMFDt8p0FWg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--ENSCgXiFNPZM3e6F Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 29, 2020 at 03:20:15PM +0100, Mateusz Guzik wrote: > On 11/29/20, David Wolfskill <david@catwhisker.org> wrote: > > On Sat, Nov 28, 2020 at 10:47:57AM -0500, Jonathan Looney wrote: > >> FWIW, I would try running lockstat on the box. (My supposition is that > >> the > >> delay is due to a lock. That could be incorrect. Lockstat may provide > >> some > >> clue as to whether this is a line of inquiry worth pursuing.) > >> .... > > > > Thanks (again), Jonathan. > > > > So... I did that (during this morning's daily upgrade cycle); the > > results may be "of interest" to some. > ... > > http://www.catwhisker.org/~david/FreeBSD/head/lockstat/README > ... >=20 > According to the data you got the entire kernel "freezes" every 11-12 > seconds. So something way off is going on there. >=20 > Given that the bug seems to be reproducible I think it would be best > if you just bisected to the offending commit. >=20 > --=20 > Mateusz Guzik <mjguzik gmail.com> I had thought that the issue arose (as noted in my initial message) around 09 Nov, which was the day that my daily update on head went from r367484 to r367517. So for my inital attempt at a "before the breakage" kernel (& world), I "updated" sources to r367444, as I had updated to that revision on 07 Nov. Testing (again, via "ping albert") still showed most RTTs around 0.600 ms, but (around) every 11th packet, I would see an RTT in the 400 - 650 ms range -- around a factor of 1000(ish). So while I was not seeing RTTs in excess of 68 seconds (as I did at least one time for the initial message), I believe(d) that the underlying issue still existed at r367444. Lather, rinse, repeat -- for: * r367484 (from 08 Nov) * r367243 (from 01 Nov) * r366312 (from 01 Oct) * r363759 (from 01 Aug) At this point, I was questioning many assumptions, so I cleared /usr/obj completely and then updated back to r368143... and the issue remained. (The laptop was quite busy yesterday.) I definitely do NOT see anything like this running stable/12 (presently at r368181). I will try some experiments with another laptop (a newer one, for which the built-in mouse is detected weirdly, making it annoying to use for me -- but I can still ping from it). 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. --ENSCgXiFNPZM3e6F Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE4owz2QxMJyaxAefyQLJg+bY2PckFAl/E6YNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUy OEMzM0Q5MEM0QzI3MjZCMTAxRTdGMjQwQjI2MEY5QjYzNjNEQzkACgkQQLJg+bY2 PcnAFAf/dGX09t6WqOBtK6mBs79PQcPiG+W5CpT14ZcBiVcmEg+ooUOAEfYdvvnA FD/Uxge1OPiN32Ezh5yNAz+hgfy23wPe8oLW9H1xOsJ2HoXnrmBrlycdniyXfsvB dKYDg6VfbEcbE9p5iVSTeYTOxz40n9iriD2SrunpiwFIvEhrCsCBhK0Y/rgrI6e+ lGN/Y6lQOwmiX3aZFj6t8LmPcgQ8HnTaemybtQ7gLC7UjfYSpODwcV8AlLeNoYKS 8pJGbEG+KEuJ59dn3aGqk6EG/oc6ylrWgRQCNkitPul6KzpTYMJ6mNXFJ0j5hVMN djM1V3msW+2/KbU6di7ugkfkm307Nw== =Vt8d -----END PGP SIGNATURE----- --ENSCgXiFNPZM3e6F--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?X8Tpg1P%2BXQc7iTNJ>