From nobody Sun Jul 14 19:00:18 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 4WMZR31f6gz5RBrW for ; Sun, 14 Jul 2024 19:00:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WMZR25X1Yz4fXj for ; Sun, 14 Jul 2024 19:00:30 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1030.google.com with SMTP id 98e67ed59e1d1-2c98b22638bso2477146a91.1 for ; Sun, 14 Jul 2024 12:00:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1720983629; x=1721588429; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=xEdbwMPvYwoDwkbyLnj3pw0l0WFCRjaOF4bNi0Of5Bk=; b=yoi+iyFQy5NWSgVFtUH8vB95Y+YJOYFqcZvU4jHtjyGPwSykWOyiIem4NL+yVa2ZFA nmrScBalrGpBaTlVdH9TJXq6tfhDYtnAEWW7WQaeAgIS3OnIE3QPV9TS9EAixiIvWfxh Ac0MKy5xMCNkcHsuDpEQqxv9jJesmxJVbhpOqLAP3r1EkBEXwQ3MpCphRHCB1DW1fBgZ H9e5rtnBJKWGLlykMwuApGUV3QeUNwsOfjzvdxrlxxxuUXYyLpR9ivUSm+K2nCpfJMbG 0nH0AgBI/N3iKjjaG99Jsp1yH6nI+HeXm3eW7lqPS5RroHEm+T6fvFuduAlbjY0pJ3f4 WnQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720983629; x=1721588429; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=xEdbwMPvYwoDwkbyLnj3pw0l0WFCRjaOF4bNi0Of5Bk=; b=J+72/dtU1qFeA4Fc3740LmQ6FTrl5xvWajAGKYaVf1hIB/SZcsrYwid6TWcYVsmLUx QK6X5fSc5jtanh0RFacqzcQzE9h+FGV5G+PERutLVkwt6Lcb9dNuzrMX+tm+qbiNggqC h3eToNx7kko/9JTnl4mZ4wiPfjlpuvsYDKSXSisUY6Am9cdsdBsg//vUFbeYd9cyqcyS PSQTk3P5muTUCoM9PAcMz4tC/5G23RDXwqsjCA3lY9KkTy6ChzrFBAzCjWkoeqAPHZov uAnduhrk3mT7io9mGMvqhgrgWMxKk7BefMuDHBEAABqdQ7jHbmaVM11a9r3pZCKryCaJ mneA== X-Forwarded-Encrypted: i=1; AJvYcCWW4/i4/XaayHaFP3ECCUN8CYma9u0iAq0K4Fml2vDddGQMe9MnQ3SQ0AdpvsAhyIx2MdBppmNNRMmTQKnHbhq5ocyRU09OMoX5/QU= X-Gm-Message-State: AOJu0Yzd5Ap4Lwcpj8F6O7Zxfz36p5c3QwRANTQBCU/aZhGiujYRom1Y cPf4TXUyu3VwRBlDUNZifxsXTZhPvmeMg8PUAyyX72wLGW3UemaGC8K7FtcEl7Xsf1tk/k6KoNE R5PrkPFcbO31JNmYVRS1WeBNhn3uS8QUX2EmWSEUaZxiZVX5G2QOqBQ== X-Google-Smtp-Source: AGHT+IHRpWcoKIwLD8xMIxvvXFCLBdJyi2UzScFNS9WBujTXOxBOxqD8rqYqqeSehErRBhIgYANe1ZfPl9kbcEiD/bc= X-Received: by 2002:a17:90b:1e12:b0:2c9:75a7:5c25 with SMTP id 98e67ed59e1d1-2cac509a7e2mr13054672a91.15.1720983629206; Sun, 14 Jul 2024 12:00:29 -0700 (PDT) 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 References: <0f378de3-7a20-4284-8cca-6c9ed2d0c55d@tilda.center> <8878ea2e-f91e-4cfd-8ddd-cc1d070eea32@tilda.center> <86cyngcdsr.fsf@peasant.bootbsd.com> In-Reply-To: <86cyngcdsr.fsf@peasant.bootbsd.com> From: Warner Losh Date: Sun, 14 Jul 2024 13:00:18 -0600 Message-ID: Subject: Re: Keyboard on laptop typing problem To: Dmitry Salychev Cc: =?UTF-8?B?R29yYW4gTWVracSH?= , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000e23227061d39b94d" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4WMZR25X1Yz4fXj --000000000000e23227061d39b94d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable M*ay*be try https://reviews.freebsd.org/D45554 and see if that works? Warner On Sun, Jul 14, 2024 at 7:18=E2=80=AFAM Dmitry Salychev w= rote: > > 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=3DV4Vse9T52s3EGSv4= 1FKM1iGw@mail.gmail.com/ > [2] > https://www.reddit.com/r/linuxhardware/comments/vdc6tz/comment/ijjjwah/ > > -- > https://wiki.freebsd.org/DmitrySalychev > > --000000000000e23227061d39b94d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Maybe try https://reviews.freebsd.org/D45554 and see if th= at works?

Warner

On Sun, Jul 14, 20= 24 at 7:18=E2=80=AFAM Dmitry Salychev <dsl@freebsd.org> wrote:

Goran Meki=C4=87 <meka@tilda.center> 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 l= etter
>>> 'c' (just for
>>> example) terminal first doesn't do anything for about a se= cond,
>>> then it prints
>>> multiple letters 'c' in a row. Is there any way to deb= ug 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. I= t'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, sec= ond
> 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<= br> >
> 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.<= br>
Regards,
Dmitry

[1]
htt= ps://lore.kernel.org/all/CAJZ5v0isLQVX3EqsokFthY5ka=3DV4Vse9T52s3EGSv41FKM1= iGw@mail.gmail.com/
[2] https://www.reddit.com/r/= linuxhardware/comments/vdc6tz/comment/ijjjwah/

--
https://wiki.freebsd.org/DmitrySalychev

--000000000000e23227061d39b94d--