[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1013180: marked as done (linux-image-5.18.0-1-amd64: System doesn't go to sleep in 5.18.0-1 kernel)



Your message dated Tue, 06 Dec 2022 11:22:43 +0100
with message-id <4795573.31r3eYUQgx@prancing-pony>
and subject line Re: Bug#1013180: System doesn't go to sleep in 5.18.0-1 kernel
has caused the Debian Bug report #1013180,
regarding linux-image-5.18.0-1-amd64: System doesn't go to sleep in 5.18.0-1 kernel
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 owner@bugs.debian.org
immediately.)


-- 
1013180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013180
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-5.18.0-1-amd64
Version: 5.18.0-1
Severity: normal
X-Debbugs-Cc: sacled@scaledteam.ru

Dear Maintainer, System doesn't go to sleep in 5.18.0-1 kernel, but it's fine
in 5.16 and 5.15. System tries to go to sleep, but then it wakes up
immidiately. Dmesg shows some stacktrace-something after trying to sleep.
Nvidia proprietary driver is installed on the system.


-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.0-0.bpo.4-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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-image-5.18.0-1-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.141
ii  kmod                                    29-1+b1
ii  linux-base                              4.9

Versions of packages linux-image-5.18.0-1-amd64 recommends:
ii  apparmor             3.0.4-2
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-5.18.0-1-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  grub-efi-amd64          2.06-3
pn  linux-doc-5.18          <none>

--- End Message ---
--- Begin Message ---
Version: 6.0.10-1

On dinsdag 6 december 2022 11:15:35 CET Diederik de Haas wrote:
> On maandag 5 december 2022 19:29:46 CET Alexandr Podgorniy wrote:
> > I don't know, but current 6.0.10-1 kernel works fine. Issue disappeared
> > after few updates, 5.19 kernel worked fine as far as i remember.
> 
> Can you find out the lowest kernel version in which it was fixed?
> Or would you rather just close the bug with 6.0.10-1?

It was the latter, thus closing with that version.

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply to: