Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #71210
| From | Antoine Beaupré <anarcat@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#922666: confirmed bug report |
| Date | 2021-05-04 02:50 +0200 |
| Message-ID | <CaRq9-45Z-5@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <CauDf-7nL-1@gated-at.bofh.it> <Caztf-1Sg-1@gated-at.bofh.it> <CaRgt-42a-1@gated-at.bofh.it> <xt6s2-1cV-3@gated-at.bofh.it> <CaRgt-42a-1@gated-at.bofh.it> |
| Organization | Debian |
Cross-posted to 2 groups.
On 2021-05-03 20:27:26, Antoine Beaupré wrote:
[...]
> Interestingly, it seems that the machine indeed doesn't go to sleep: it
> loops over a failure to sleep and fills up syslog with errors as long as
> it's trying to sleep, pretty catastrophic, from a battery usage
> perspective.
>
> I attach the two logs and am continuing my investigation. User now
> reports situation is actually much worse than before the backports
> upgrade: at least 5.7 was intermittent, now the crash is systematic.
Relevant: booting into 4.19.132, from plain buster, doesn't reproduce
the above failure to suspend. The machine suspends fine, and resumes,
and the mouse even still works correctly.
I wonder if this is a regression introduced in backports. But I could
have sworn this was happening *before* I upgraded to the backported
kernels...
And here I was hoping that upgrading to bullseye might fix this, maybe
it would make things even worse because the old kernel wouldn't be
available anymore (although if it's an interoperability issue, then
maybe it would fix it, who knows nowadays...)
--
No animal has more liberty than the cat; but it buries the mess it
makes. The cat is the best anarchist. Until they learn that from the cat
I cannot respect them.
- For whom the bell tolls, Ernest Hemingway
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#922666: confirmed bug report Salvatore Bonaccorso <carnil@debian.org> - 2021-04-30 21:10 +0200
Processed: Re: Bug#922666: confirmed bug report "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-04-30 21:10 +0200
Processed: Re: Bug#922666: confirmed bug report "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-04-30 21:10 +0200
Bug#922666: confirmed bug report Tollef Fog Heen <tfheen@err.no> - 2021-04-30 21:40 +0200
Bug#922666: confirmed bug report Antoine Beaupré <anarcat@debian.org> - 2021-05-01 01:40 +0200
Bug#922666: confirmed bug report Salvatore Bonaccorso <carnil@debian.org> - 2021-05-01 08:10 +0200
Bug#922666: confirmed bug report Antoine Beaupré <anarcat@debian.org> - 2021-05-03 02:30 +0200
Bug#922666: confirmed bug report Salvatore Bonaccorso <carnil@debian.org> - 2021-05-03 07:40 +0200
Bug#922666: confirmed bug report Antoine Beaupré <anarcat@debian.org> - 2021-05-03 17:10 +0200
Bug#922666: confirmed bug report Antoine Beaupré <anarcat@debian.org> - 2021-05-04 02:50 +0200
Bug#922666: confirmed bug report Antoine Beaupré <anarcat@debian.org> - 2021-05-04 04:00 +0200
Bug#922666: confirmed bug report Antoine Beaupré <anarcat@debian.org> - 2021-05-04 21:20 +0200
csiph-web