From nobody Sun Jul 14 13:07:55 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WMQrW4spdz5Qc00 for ; Sun, 14 Jul 2024 13:18:35 +0000 (UTC) (envelope-from dsl@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WMQrW4KHnz4vLb; Sun, 14 Jul 2024 13:18:35 +0000 (UTC) (envelope-from dsl@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1720963115; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3sNR8ea+2rGceK78g/8tptp6DUMU5cHTE51TucWJN4Q=; b=qjVCddqRB9CmS2CS0WeSy3sbhHBSNNt3DggMwDKfOwQqW119bEqr10Qf7+M5f6/gmKqZ+S dxNSPECxQhEkKgGpwMCZrxjo3JMhRIMRNrm0VWQg4D7OBhFqi5haC2oJHPEyDvd5KSfXqP gh6OuRq6jk493Sr87gLHaH5883Xpetv99kbn/YBjyPN/i7qm/tdiNIFO7OMU/jKSteIux7 YlORaa4oxiynHGfe7caqCLwtZ8tXsZEaCpEEF8HSQaOR3bE/LIx+AvASWyHr4mItVpVO7S OuRn8ws33NgMWWcr4ZbH96W0vRfCVUzurXjDolGopgBVpGOjmhZJCcYyiekLLQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1720963115; a=rsa-sha256; cv=none; b=NBN3/K6eqcQqXHTAOQiVN8yqphEezageSr7pbAPca28GWkAOi8WExcyRWZDlfGICiMHFw+ t+eMfiZpg5RvGN5U3oloDc0xC9CXQcTxItEYdtNzODRZzODhcN2F/8Mvz2PgppU0g7ga3A 2VsxID+qUc/Hqas8GIPVDvZQuIQ8r34FKMmZ3gaD16wnkiMeg0UNqnTdQflF+BOXC/Egbo yg7fvsTFkwDw8UBrN/7/jU9gJ3O2vIJlNXL/R/lOtAuRsU1E9C/LptVP0+3v6Ou9BEm0zw Gi23dYDO9IvlpwzQp3CIJHeOFcqvZ0jd3DEvJANrlnM90sp5c5VM73sJBlbxpQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1720963115; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3sNR8ea+2rGceK78g/8tptp6DUMU5cHTE51TucWJN4Q=; b=cim0yDdHq69uq+BohKfK4nGdRn31PoMNFJg4kx4d+6YGmfJ/cDjeb4qDcrBpRBbW5ni6AG E3e2V5e9PHT2cClOXfhTTzUv0PxhSujqI6DC8HldbxlqlR3UmQa3RqUmr+269BGHK70Vmx xhw4Pg59Qyee6hFq3rGnXxlYoIsWcg3vooK07qWb1Wila1jDhdDbx7oRFuaBwg48DWX7+w oYNeBKAyV3LRNwOawGO6BR6pKOxqRQZ7/RE9pJ9cJCFyHpnEI3yKwm1LSv1sBtRuvAcvqG ClcDHHbz0OcYML5XQW2hz+Dk4u2yigGKU08ecFvQnXPpmNDTE/NQTgFZ3/YkDA== Received: from localhost (unknown [91.226.51.235]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: dsl) by smtp.freebsd.org (Postfix) with ESMTPSA id 4WMQrW1smCzZ2Y; Sun, 14 Jul 2024 13:18:35 +0000 (UTC) (envelope-from dsl@FreeBSD.org) References: <0f378de3-7a20-4284-8cca-6c9ed2d0c55d@tilda.center> <8878ea2e-f91e-4cfd-8ddd-cc1d070eea32@tilda.center> User-agent: mu4e 1.8.13; emacs 29.3 From: Dmitry Salychev To: Goran =?utf-8?Q?Meki=C4=87?= Cc: freebsd-current@freebsd.org Subject: Re: Keyboard on laptop typing problem Date: Sun, 14 Jul 2024 15:07:55 +0200 In-reply-to: <8878ea2e-f91e-4cfd-8ddd-cc1d070eea32@tilda.center> Message-ID: <86cyngcdsr.fsf@peasant.bootbsd.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Goran Meki=C4=87 writes: > On 7/13/24 18:18, Chris wrote: >> On 2024-07-13 15:23, Goran Meki=C4=87 wrote: >>> Hello, >>> >>> I have a laptop with a weird behaving keyboard. Under Linux >>> everything is fine, >>> but under FreeBSD it is out of sync. On single key stroke of letter >>> 'c' (just for >>> example) terminal first doesn't do anything for about a second, >>> then it prints >>> multiple letters 'c' in a row. Is there any way to debug this >>> behavior and why >>> it's happening? Any chance there's a known workaround? I don't know >>> what other >>> info would be useable, so if you can tell me what other than >>> usbconfig and pciconf >>> to look at, I'll be glad to. >> It would be very helpful to know what hardware you're using. It's >> otherwise very >> difficult to answer this sort of question. > > You can see that yesterday was the hottest day in my city ever. First, > I didn't manage to ask what I wanted: what info should I send, second > I sent the reply only to one person :facepalm: > > Anyway, I think the most condensed way to show the hardware is > https://bsd-hardware.info/?probe=3D3400ac8782 > > Regards, > meka IRQ override [1] which breaks active low IRQs on AMD Ryzen 6000+ systems might be the reason of your troubles. I don't know the exact place in the FreeBSD src/ to check whether the same override is implemented or not, but you'd try to patch ACPI tables yourself [2] till it is fixed. Regards, Dmitry [1] https://lore.kernel.org/all/CAJZ5v0isLQVX3EqsokFthY5ka=3DV4Vse9T52s3EGSv41F= KM1iGw@mail.gmail.com/ [2] https://www.reddit.com/r/linuxhardware/comments/vdc6tz/comment/ijjjwah/ --=20 https://wiki.freebsd.org/DmitrySalychev