From owner-freebsd-current@freebsd.org Mon Nov 30 13:10:55 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B974E47BE4A for ; Mon, 30 Nov 2020 13:10:55 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4Cl5Fq2CzTz3M3b for ; Mon, 30 Nov 2020 13:10:55 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id 4C1E547BC42; Mon, 30 Nov 2020 13:10:55 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4BE5A47BBB5 for ; Mon, 30 Nov 2020 13:10:55 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Cl5Fq1Vrqz3MCb for ; Mon, 30 Nov 2020 13:10:54 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-wm1-x32e.google.com with SMTP id g185so17059223wmf.3 for ; Mon, 30 Nov 2020 05:10:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=tfd/O6/V9HInb5cXO3vGzI0uHvnsLudP+lbuNiBT4s8=; b=tbhRrp31Ti1Qt8xh1J8oqqeLEqaeC1wxK5BZVKqD7x2tNt8UdXaCMvKd6aUo/WleCA YxTeybsBzWWO7H/A6GJYPXh9Px9T5lMJ+3npMdJSvN/JWYxthxxENy/VbNM+pCXvHMpi tffz5NIGFTy0WQ5uqDB3ePVi0hTtgLz6fRTG7dBSShaMB+LoYSA79wwqbyMhf0Yrd3Oh xOxJsVHmqadC1B5GE0yZzf/5rF/Y5JYF4D6iyMY72xk1thN54By537Aa+1gl6nQSTtKU qPMG2ven1pmeTzIYC6raCIt/dz7temNssGvtjXczI97zSa/5ZBMtMB0RZ4Crm5blXbkB 5Ymg== X-Gm-Message-State: AOAM533bU4nY9lNidxKLigoHkeFiWwE0SvQ4AkR8yWZLWHYfA3brjpZB 91sHXCTfGYvrEG7UlQBSC4QEqjDIXmsZCFpgpFl+/mDLvY4= X-Google-Smtp-Source: ABdhPJxc9bxG5VL+BH9BiwNvSGaB5GP1HnInvEVUfEJGH1aEb3977cFZhNh2egaLQ04jC1M0qr/ZM4BzmL9BRpBX+Ac= X-Received: by 2002:a7b:c012:: with SMTP id c18mr23382118wmb.10.1606741852746; Mon, 30 Nov 2020 05:10:52 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a5d:4d47:0:0:0:0:0 with HTTP; Mon, 30 Nov 2020 05:10:51 -0800 (PST) In-Reply-To: References: From: Mateusz Guzik Date: Mon, 30 Nov 2020 14:10:51 +0100 Message-ID: Subject: Re: Laptop exhibits erratic responsiveness To: current@freebsd.org, Mateusz Guzik Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4Cl5Fq1Vrqz3MCb X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2020 13:10:55 -0000 On 11/30/20, David Wolfskill wrote: > On Sun, Nov 29, 2020 at 03:20:15PM +0100, Mateusz Guzik wrote: >> On 11/29/20, David Wolfskill 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 >> ... >> >> According to the data you got the entire kernel "freezes" every 11-12 >> seconds. So something way off is going on there. >> >> Given that the bug seems to be reproducible I think it would be best >> if you just bisected to the offending commit. >> >> -- >> Mateusz Guzik > > 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). > As a sanity check, does the issue manifest itself if you build a GENERIC-NODEBUG kernel? -- Mateusz Guzik