Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #81663 > unrolled thread
| Started by | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| First post | 2024-01-25 22:10 +0100 |
| Last post | 2024-01-27 10:10 +0100 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#1061521: linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend Salvatore Bonaccorso <carnil@debian.org> - 2024-01-25 22:10 +0100
Processed: Re: Bug#1061521: linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-01-25 22:10 +0100
Bug#1061521: linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend Antoine <debian@r2rien.net> - 2024-01-25 23:00 +0100
Bug#1061521: linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend Salvatore Bonaccorso <carnil@debian.org> - 2024-01-27 10:10 +0100
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2024-01-25 22:10 +0100 |
| Subject | Bug#1061521: linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend |
| Message-ID | <I0f8Z-5ysN-5@gated-at.bofh.it> |
Control: tags -1 + moreinfo On Thu, Jan 25, 2024 at 10:01:04PM +0100, r2rien wrote: > Package: linux-image-6.6.13-amd64 > Version: 6.6.13-1 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: debian@r2rien.net > > Resuming from suspend keyboard totally unresponsive, thus no sysrq, no tty to > the rescue, only power button. > Stuck in gdm3 login screen, > thus impossible to type password to unlock gnome-session > I tagged it as grave so people with apt-listbugs could be informed Please do provide some more information. Is this a regression from 6.6.11-1. In case yes, can you please try to bisect the changes in upstreams 6.6.11 to 6.6.13 so we can isolate which change causes it? When you resume from suspend, do you get anything logged in the kernel log, can you attach it here? Regards, Salvatore
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2024-01-25 22:10 +0100 |
| Subject | Processed: Re: Bug#1061521: linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend |
| Message-ID | <I0f8Z-5ysN-9@gated-at.bofh.it> |
| In reply to | #81663 |
Processing control commands: > tags -1 + moreinfo Bug #1061521 [linux-image-6.6.13-amd64] linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend Added tag(s) moreinfo. -- 1061521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061521 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | Antoine <debian@r2rien.net> |
|---|---|
| Date | 2024-01-25 23:00 +0100 |
| Message-ID | <I0fVn-5yLp-3@gated-at.bofh.it> |
| In reply to | #81663 |
[Multipart message — attachments visible in raw view] — view raw
On 1/25/24 22:08, Salvatore Bonaccorso wrote: > Is this a regression from 6.6.11-1 Yes > When you resume from suspend, do you get anything logged in the kernel log, > can you attach it here? As it was mixed with other upgrades from testing (libc6, grub, polkit mainly), for now I just rolled back from a backup, and did them incrementally ..to finish with only 6.6.13-1 which reproduced the issue. I rolled back again so now I need to update my backup and will then try getting some logs
[toc] | [prev] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2024-01-27 10:10 +0100 |
| Message-ID | <I0MRj-5TBn-1@gated-at.bofh.it> |
| In reply to | #81663 |
Hi Antoine,
On Fri, Jan 26, 2024 at 06:26:48PM +0100, Antoine wrote:
> On 1/25/24 22:08, Salvatore Bonaccorso wrote:
> > can you please try to bisect the changes in upstreams 6.6.11 to 6.6.13
> Hi, Before considering bisecting,
>
> > do you get anything logged in the kernel log, can you attach it here?
> As I further noticed that hibernate was working fine,
> I configured the power button to trigger it and isolate logs
> With same sequence: cold boot > login > suspend > resume > hibernate
> with both kernels on this dell xps13-9343/broadwell/i5/i915/xorg
> (delivered pre-installed with ubuntu 14.04 in 2015)
>
> Please find them attached (without systemd journals),
> so maybe you could identify a clue more than me,
> ..to evacuate any personal settings/configuration getting in the way
After looking at your report, I supsect this could be
https://lore.kernel.org/regressions/4eaf27ed-66a2-4aeb-a6b9-21e2b0455676@leemhuis.info/T/#ma73a2b47e9ecb7f4969f12b247cc48acb9c2e7d0
The patches have not land yet in mainline nor in the 6.6.y series. But
please read through it. If you have the spare cycles you could test
the two patches from Hans de Goede if they indeed fix your issue as
well.
Regards,
Salvatore
p.s.: As a minor side note, if you fill the rpeort wtih bugreport
against the kernel we additional information from the bugscripts
on hardware etc.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web