From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7AEE3213E99; Wed, 7 May 2025 11:35:12 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.70.183.195 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1746617715; cv=none; b=kpN6JDIJgyeZEBPvPv0EUdsM3NzDbdxxJupWvoDUR8q7buWvIiDCYTVQ5GIclchigudlCPzQN4STTtB77tLoWAiFTYhZPLNsa2E7RZM0ISmBQlhpUcnwDto1qIamXQCD3WTvQW+Mu6ChfgwlSwTWIyu7R2b1C6iso4bEH0WUJT4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1746617715; c=relaxed/simple; bh=Bia5pMdePjytLko+tRK5Sv9EEfnx1da7vCY/S3XH60E=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=dAUZ1h73kUYowWLb747iUHhEAleshGISYuFlTQ7uzsSQhJWEueRhm/loL4NMJ6tTMzqDdcut5UGh1/WqjByuTU9rgWfC/GMjkgiv5Cm/WOtNj2VqTTlBfe/8tPmSCeaWgkl/N+F+xV/aIuF0yKFmO2hLyH4FEhZF9y6tpMQHmYA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com; spf=pass smtp.mailfrom=bootlin.com; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b=YNqmXnx6; arc=none smtp.client-ip=217.70.183.195 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=bootlin.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b="YNqmXnx6" Received: by mail.gandi.net (Postfix) with ESMTPSA id 49A111FCED; Wed, 7 May 2025 11:35:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=gm1; t=1746617705; 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=6MSE+eVszmhNdpPjpe2nSaOQmxzMdKmvHwgXnaWWTl8=; b=YNqmXnx6C+sI3i61bKhaXglR4/kx973n6ku8Vh97Fnv+1Y7ixaW3lnUdNsoRpZUv6VpD4n 6RiiVW/yvGNRBhC8uQkmHvVsVKp47InE8dbegKu2b0wbixt5WBODI0Mwa6JXtbWwrKxntb /taTa8qnuiaJdLCat0i048dWAI3KaMCxl5/r/Bw0wAY1RB8xpUAAa0P18TOlRYSNwhjMX/ YSjU/PIf7ArUrgSND8ibs3r8LptoWf3mxHy42IvdUPy4Lv7p4jpR7kzllfcGza9qLFwiSp oRen+CuFWKU80YfaaBTaYze8yJ42yCbGlFmie7Yc7m9gG8cykEUCOi4M8FwZiw== Date: Wed, 7 May 2025 15:32:36 +0200 From: Maxime Chevallier To: "Russell King (Oracle)" Cc: Linus Torvalds , Andrew Lunn , Woojung Huh , Vladimir Oltean , Heiner Kallweit , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Dmitry Torokhov , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [BUG] Stuck key syndrome (was: Re: [PATCH net-next v2] net: dsa: microchip: Add SGMII port support to KSZ9477 switch) Message-ID: <20250507153236.5303be86@fedora.home> In-Reply-To: References: <20250507000911.14825-1-Tristram.Ha@microchip.com> <20250507094449.60885752@fedora.home> <20250507105457.25a3b9cb@fedora.home> Organization: Bootlin X-Mailer: Claws Mail 4.3.1 (GTK 3.24.43; x86_64-redhat-linux-gnu) Precedence: bulk X-Mailing-List: linux-input@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-GND-State: clean X-GND-Score: -100 X-GND-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddvkeeijeehucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuifetpfffkfdpucggtfgfnhhsuhgsshgtrhhisggvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvvefukfgjfhhoofggtgfgsehtjeertdertddvnecuhfhrohhmpeforgigihhmvgcuvehhvghvrghllhhivghruceomhgrgihimhgvrdgthhgvvhgrlhhlihgvrhessghoohhtlhhinhdrtghomheqnecuggftrfgrthhtvghrnhepgeevledtvdevueehhfevhfelhfekveeftdfgiedufeffieeltddtgfefuefhueeknecukfhppedvrgdtvdemkeeggedtmehfhedtsgemfedvheemrgeigeefmedufheiugemfhgvrgegmeegsgduieenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpedvrgdtvdemkeeggedtmehfhedtsgemfedvheemrgeigeefmedufheiugemfhgvrgegmeegsgduiedphhgvlhhopehfvgguohhrrgdrhhhomhgvpdhmrghilhhfrhhomhepmhgrgihimhgvrdgthhgvvhgrlhhlihgvrhessghoohhtlhhinhdrtghomhdpnhgspghrtghpthhtohepudefpdhrtghpthhtoheplhhinhhugiesrghrmhhlihhnuhigrdhorhhgrdhukhdprhgtphhtthhopehtohhrvhgrlhgusheslhhinhhugidqfhhouhhnuggrthhiohhnrdhorhhgpdhrtghpthhtoheprghnughrvgifsehluhhnn hdrtghhpdhrtghpthhtohepfihoohhjuhhnghdrhhhuhhesmhhitghrohgthhhiphdrtghomhdprhgtphhtthhopeholhhtvggrnhhvsehgmhgrihhlrdgtohhmpdhrtghpthhtohephhhkrghllhifvghithdusehgmhgrihhlrdgtohhmpdhrtghpthhtohepuggrvhgvmhesuggrvhgvmhhlohhfthdrnhgvthdprhgtphhtthhopegvughumhgriigvthesghhoohhglhgvrdgtohhm X-GND-Sasl: maxime.chevallier@bootlin.com Hi Russell, On Wed, 7 May 2025 10:59:21 +0100 "Russell King (Oracle)" wrote: > On Wed, May 07, 2025 at 10:23:17AM +0100, Russell King (Oracle) wrote: > > [Sorry for going off topic here - changed the Cc list, added Linus, > > changed the subject.] > > > > On Wed, May 07, 2025 at 10:54:57AM +0200, Maxime Chevallier wrote: > > > On Wed, 7 May 2025 09:31:48 +0100 > > > "Russell King (Oracle)" wrote: > > > > [rest of the email got deleted because Linux / X11 / KDE got confused > > > > about the state the backspace key and decided it was going to be > > > > continuously pressed and doing nothing except shutting the laptop > > > > down would stop it.] > > > > > > Funny how I have the same exact issue on my laptop as well... > > > > I've had the "stuck key" behaviour with the HP Pavilion 15-au185sa > > laptop I had previously (normally with ctrl-F keys). However, hitting > > ctrl/shift/alt would stop it. > > > > This is the first time I've seen the behaviour with the Carbon X1 > > laptop, but this was way more severe. No key would stop it. Trying to > > move the focus using the trackpad/nipple had any effect. Meanwhile > > the email was being deleted one character at a time. So I shut the > > laptop lid causing it to suspend, and wondered what to do... on > > re-opening the laptop, it didn't restart and is back to normal. > > > > This suggests that the entire input subsystem in the software stack > > collapsed just after the backspace key was pressed, and Xorg never > > saw the key-release event. So Xorg duitifully did its key-repeat > > processing, causing the email to be deleted one character at a time. > > > > The problem is, not only did this destroy the email reply, but it > > also destroyed my train of thought for the reply as well through > > the panic of trying to stop the entire email being deleted. > > > > I don't think this is a hardware issue - I think there's a problem > > in the input handling somewhere in the stack of kernel, Xorg, > > whatever multiple input libraries make up modern systems, and KDE. > > > > I did check the logs. Nothing in the kernel messages that suggests > > a problem. Nothing in Xorg's logs (which are difficult to tie up > > because it doesn't use real timestamps that one can relate to real > > time.) There's no longer any ~/.xsession-errors logfile for logging > > the stuff below Xorg. > > > > I'm running Debian Stable here - kernel 6.1.0-34-amd64, X.Org X Server > > 1.21.1.7, KDE Plasma (5.27.5, frameworks 5.103.0, QT 5.15.8). > > I'll also add that The Carbon X1, being a laptop, its built-in keyboard > uses the i8042: > > [ 1.698156] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12 > [ 1.698543] i8042: Warning: Keylock active > [ 1.700170] serio: i8042 KBD port at 0x60,0x64 irq 1 > [ 1.700174] serio: i8042 AUX port at 0x60,0x64 irq 12 > [ 1.700271] mousedev: PS/2 mouse device common for all mice > [ 1.702951] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 > > I don't have the HP laptop with me to check what that was using. > > The mysterious thing is "Keylock active" - clearly it isn't because I > can write this email typing on that very keyboard. However, I wonder > if it needs i8042_unlock=1 to set I8042_CTR_IGNKEYLOCK. > > Unfortunately, it's probably going to take a year on the Carbon X1 > to work out if this makes any difference. > > > Anyone else seeing this kind of behaviour - if so, what are you > > using? It just happened to me as I was typing this very email (key 'd' got stuck, nothing could un-stick it, couldn't move the mouse cursor but mouse-click events did work, had to suspend/resume the laptop to fix that) Got the same "Keylock active" warning at boot : [ 0.916750] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 [ 0.917210] i8042: Warning: Keylock active [ 0.920087] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 0.920090] serio: i8042 AUX port at 0x60,0x64 irq 12 Nothing in the kernel logs when the key got stuck. Laptop is a Dell XPS 15 9510, Running Fedora 41 but I saw this issue before, kernel 6.14.4-200.fc41.x86_64, Wayland-based, Gnome 47. Hopefully this helps a bit narrowing this down, I have a fairly different userspace stack and kernel version, but we do have the same driver involved and same keylock warning... Maxime