Path: csiph.com!1.us.feeder.erje.net!2.eu.feeder.erje.net!feeder.erje.net!fu-berlin.de!news.servidellagleba.it!bofh.it!news.nic.it!robomod From: Salvatore Bonaccorso Newsgroups: linux.debian.bugs.dist,linux.debian.kernel Subject: Bug#1064041: linux-image-6.1.0-18-amd64: Resuming from suspend keyboard unresponsive (but sysrq OK , touchpad OK) on dell latitude 3340 Date: Sun, 03 Mar 2024 16:30:01 +0100 Message-ID: References: X-Original-To: Jacques , 1064041@bugs.debian.org X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Sun Mar 3 15:27:09 2024 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: 0.191 Reply-To: Salvatore Bonaccorso , 1064041@bugs.debian.org Resent-To: debian-bugs-dist@lists.debian.org Resent-Cc: Debian Kernel Team X-Debian-Pr-Message: followup 1064041 X-Debian-Pr-Package: src:linux X-Debian-Pr-Keywords: upstream X-Debian-Pr-Source: linux MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Debian-User: carnil X-Debian-Message: from BTS X-Mailing-List: archive/latest/1825676 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 28 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sun, 3 Mar 2024 16:25:54 +0100 X-Original-Message-ID: X-Original-References: <170807667481.210048.13063210679527343596.reportbug@bruyere.home.gwalarn.eu> <170807667481.210048.13063210679527343596.reportbug@bruyere.home.gwalarn.eu> <87aab32f-f16f-465a-bcd9-8ab0cae9f8fa@gwalarn.eu> <170807667481.210048.13063210679527343596.reportbug@bruyere.home.gwalarn.eu> <87aab32f-f16f-465a-bcd9-8ab0cae9f8fa@gwalarn.eu> Xref: csiph.com linux.debian.bugs.dist:1188923 linux.debian.kernel:82000 Hi Jacques, On Sun, Mar 03, 2024 at 10:14:33AM +0100, Jacques wrote: > Hi Salvatore > > Le 01/03/2024 à 13:39, Salvatore Bonaccorso a écrit : > > Would it be possible to try the most recent upstream kernel in 6.1.y > > series (soon 6.1.80, or at least 6.1.79) to see if the issue is fixed > > there? > > With the upstream kernel 6.1.80 the issue is well fixed. > > > > > Secondly, would you be able to bisect the upstream changes between > > 6.1.69 and 6.1.76 to determine the introducing commit? > > I will upload the kernels , compile, try and report the results when > finished Ok that is great to hear. So firstmost: Then this iwill be fixed in the next upload for bookworm, as we do a rebase to at least 6.1.80. Alternatively if we know which was the fixing commit that would be helpful as well now, since we know 6.1.80 fixes the issue. Otherwise we simply close later once the upload has happened. Regards, Salvatore