Your message dated Thu, 24 Apr 2025 14:57:02 +0200
with message-id <aao1hrqsg1bua...@eldamar.lan>
and subject line Re: Bug#988688: workaround for bug 988688 - disable security
chip
has caused the Debian Bug report #988688,
regarding linux-source-5.10: Lenovo ThinkPad Yoga 260 fails to suspend and
resume
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
988688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-source-5.10
Severity: important
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Maintainer,
I got the LENOVO ThinkPad Yoga 260 and installed bullseye with Debian Installer
Bullseye RC 1.
However, when I try to suspend, it doesn't work.
The LED on the power button is flashing slowly in the suspended state, but LEDs
such as his FnLk on the keyboard remain lit.
(It stayed the same even after one night)
There is no response when I press the power button to resume.
In this case, it seems that there is no choice but to press and hold the power
supply to turn off the power.
I tried it.
* Switch from Wayland to Xorg
* Update to the latest BIOS
* Initialize the BIOS
Even if I tried these, the operation did not change.
After that, when I self-built Linux Kernel 5.12.4 and started it with this,
both suspend and resume worked fine.
When I searched the Web, Suspend seemed to work in the previous Debian, so it
seems that it stopped working at some point.
- -- System Information:
Debian Release: 11.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-source-5.10 depends on:
ii binutils 2.35.2-2
ii xz-utils 5.2.5-2
Versions of packages linux-source-5.10 recommends:
ii bc 1.07.1-2+b2
ii bison 2:3.7.5+dfsg-1
ii flex 2.6.4-8
ii gcc 4:10.2.1-1
ii libc6-dev [libc-dev] 2.31-11
pn linux-config-5.10 <none>
ii make 4.3-4.1
Versions of packages linux-source-5.10 suggests:
pn libncurses-dev | ncurses-dev <none>
ii pkg-config 0.29.2-1
pn qtbase5-dev <none>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEnD7FJy/9r4Ayia3kOYwJzFcuUywFAmCi8jkACgkQOYwJzFcu
UywamBAAn3TLqp3psPR+WR/wncpgaTnKJhrTw1Oozcojtff0ibMraQ2Ig8e4HSWu
u8fY9BwZz8Zq3TQRIPMlhy/Fvj60OajrjEKx57ML09/Cme9ViLnX38ZpsJKgz5rP
D5YeUHEnnFr4NfkNs9EHpEGIRh2YqU70DuraTJoVbASh7ynRhFI8MADgyVaGB3Ru
OehVjiZMmdHAyCEcf6uu+ayykd70uJfMfjfPJaXX8AMkOZyRDb5Hv4uJ0f01jRVW
cFiq80z9oe5KXYHtJJvP12OPQQ9xRQBX4GFDUcN/WdehCn+CSMdInBkHcCIxemkU
/fvUXcIzxUCiIZuZuCnREQfnHvBF8ZVMjKhR5wTKqLO2Vo34dnlit1eMQA63FNE1
en12QXH+CWSAF3u/PkaGBTWjte8StoYzyYbH5Gr+1GQVsqld5USoztKl1ICZEn3H
isjyO8JmSzIRqwx+JmDMlI99GFZ6CVAmagU/EVhHJW3DPCUvuxJRpNCWsvoGyJzu
lMyMv5Vd2QSK/Ka4L3rvGR95lNVOHxnjtVlWax3y1L71mBnSgHn0wD3u49tEN5tc
1SjOTfTb3qd6NXUd4TfL4xHPb3UuhXWwpZvvYYITzmC4H+fHQOgAntXCkmPSS97l
QQN1jBHxpU3MqwI3aOgM/FqCVH9t+CU272dOjoYjDMtCxDUziT4=
=mifK
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Hi Jonathan,
On Sat, Mar 22, 2025 at 02:20:49PM +0100, Salvatore Bonaccorso wrote:
> Hi Jonathan,
>
> On Fri, Mar 07, 2025 at 10:18:46PM +0000, Jonathan Dowland wrote:
> > There are some related reports in Ubuntu. Note that for a while, Ubuntu
> > kernels worked where Debian ones did not, but modern Ubuntu kernels have
> > stopped working.
> >
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970290
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963802
> >
> > The workarounds there (disable security chip in BIOS) work for me on
> > 6.12.12-1.
> >
> > Since the 22.04-era kernel worked without the workaround, I have some hope
> > we can figure out why (what did Ubuntu include in that kernel that Debian
> > didn't? What did they take out between then and 24.10? What's the
> > intersection
> > of those two sets?)
>
> BTH, I do not think its worth given the amount of open bugs we have
> for src:linux and htis seems quite hardware dependent, for which we
> need anyway much help from an affected user. That is, is you feel
> strong about the issue still beeing adressed you might try to "bisect"
> where things have changed in Ubuntu kernel and isolate the change
> where that happened that it is now not working as well on them.
>
> And then once it's isolated verify again a most recent version as
> possible and report it upstream.
>
> Please do not get me wrong, hopefully I could make the position for us
> clear. I just do not see what we could do here.
Accordingly going to close now the bug. If you feel though strongly
taht it is not okay please *do* reopen, but in that case we really
would need your help for the above.
Regards,
Salvtore
--- End Message ---
