From owner-freebsd-current@freebsd.org Fri Sep 11 23:24:48 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 A41663E94E7 for ; Fri, 11 Sep 2020 23:24:48 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (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 4BpBg36xdTz41Tm for ; Fri, 11 Sep 2020 23:24:47 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ot1-x336.google.com with SMTP id o8so2050873otl.4 for ; Fri, 11 Sep 2020 16:24:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Av25KoPF15OUExfLvTuw7F277QYeJ81eJko0bxlmS94=; b=BW1N9NrU8hs8h87taYEpcQ5EnBf6+4h/f9c+h9niCEWDxEgsHsl0l8H2Le7Me2ejwx ufhojs3YcTt6gbhcqRQtP4pAlJM7bBy1ugapuvFgmgf1ZDcw7DLVNbnOYpfLrkteXpRv rPFGFlnGogDoEGYdpIO20TZ1CnD8LI3xxYirLO61SlnEPsOpe+mw/yzkf+iwh1BrAcAX 5y6m5IVYu1A/V61l3dvCKLvwIsXyKD8julnhaw1kAojhHf/+deyyd575N4lQgCCHsHZD FM/heHgrqkD8kOLd2NRz09DJDrU7i2luhaTjjk2UKgkCsqpySnw2Qm5qcef5mcdsyfAr KMPQ== X-Gm-Message-State: AOAM5319QxdoQjEU/0/sXUiRn/od5Cs84Icji4XTfZaBWHLqbzeu/kiY /FDkNm98Zm9+Mo7UkLpUZZts92JlNrzqO51BMdGLcrwo/BFlSg== X-Google-Smtp-Source: ABdhPJzxKe65RKfAbPsCmpWdh08E8uO7gXh+EaY059o6q4HhCxpwFTg/8Y5JsXRnNChVOFrIcfqFV7XUZMMDKmnz2BM= X-Received: by 2002:a9d:202b:: with SMTP id n40mr922990ota.93.1599866686050; Fri, 11 Sep 2020 16:24:46 -0700 (PDT) MIME-Version: 1.0 References: <000001d68808$f1801fb0$d4805f10$@gmail.com> <000201d68811$ba37f7e0$2ea7e7a0$@gmail.com> In-Reply-To: <000201d68811$ba37f7e0$2ea7e7a0$@gmail.com> From: Kevin Oberman Date: Fri, 11 Sep 2020 16:24:28 -0700 Message-ID: Subject: Re: Livelock on recent current To: driesm.michiels@gmail.com Cc: =?UTF-8?Q?Jan_Kokem=C3=BCller?= , FreeBSD Current X-Rspamd-Queue-Id: 4BpBg36xdTz41Tm X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.32 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.69)[-0.686]; FREEMAIL_TO(0.00)[gmail.com]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.95)[-0.951]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-0.98)[-0.982]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::336:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current]; FREEMAIL_CC(0.00)[gmail.com,freebsd.org] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 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: Fri, 11 Sep 2020 23:24:48 -0000 On Fri, Sep 11, 2020 at 1:01 AM wrote: > > > On 09.09.20 06:18, Kevin Oberman wrote: > > > > I am seeing a problem since I moved to current on my laptop this > week. > > > > It's odd as it is linked to the keyboard. As long as the keyboard is > > > > active, everything is fine, but if the keyboard is not used, after a > > > > few minutes, it locks up and gets very hot. The system may be busy > > > > or idle. The system seems completely locked. It does not respond in > > > > the network and the display, X or just vt is frozen. The only factor > > > > is use > > of the > > > keyboard. > > > > I'm actually very happy someone else ran into this too! I have a Lenovo > T490 > > (azerty edition, yeah I known ...) I found it incredible hard to > describe, > but i > > have the exact same problem. > > I categorized it as "random system freezes", but now that you say its > related to > > keyboard interaction it makes sense when I observe the lock. > > > > System locks up when it happens and the fan ramps up AFTER the dead lock. > > I'm pretty sure the getting "hot" symptom is caused by the deadlock and > not a > > symptom of the deadlock. > > Maybe a very important factor, the issue is not present in STABLE-12, I > downgraded previous week to verify this. > > > > > > > > > Reminds me of this bug: > > > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225341 > > > > I am also using a non default keyboard layout, as described in the bug > above. > > I'll probably try the patch in the coming weekend to see if it helps. > > > > > > > > I've been experiencing similar hangs when that timer in atkbd is > enabled. > > It > > > doesn't seem to happen in the default keyboard configuration, though. > > > > > > -Jan I'm happy to see that I am not crazy! This is mostly anecdotal. The freezes have occurred regularly, without question, but the details are not statistically verified. This is based on my perceptions. The only things I am really sure of is that the system is unusable on head and runs well on 12.1-Release. This system has a rather new Intel GPU, the Comet Lake, and is only supported on head with drm-devel-kmod, so moving back to 12.1 is not an option. I am curious what processor is on the T490. I am using the default keyboard layout. On terminal sessions (vt), when the keyboard is idle. I have had the system run for a couple of hours or longer with no problems. To get bigger ports to build, I usually switch to another vty and keep that one fairly busy. It will freeze when no vty is active, but as long as any is active every minute or less. I have had freezes in under a minute, but rarely. Moving on to other possibly related (or not) issues: When running on X (MATE), it may freeze whether the keyboard is active or not. OTOH, it seems to freeze less often. I've had X lock up mid-word but also run for 15 or more minutes. It eventually does freeze, but I don't think I've ever gone more than 10 minutes on an idle keyboard without a freeze without X running. Switching to a vty and keeping it fairly active still seems to keep the system alive while X is being used. X is performing very poorly. If the processors are busy, say by building a port, screen updates are very slow, often pausing for several seconds. Expose events seem to often redraw all windows which is very annoying. Several times I thought the system was frozen only to suddenly have the screen update and everything be normal, again. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683