Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #75661 > unrolled thread

Bug#1013180: linux-image-5.18.0-1-amd64: System doesn't go to sleep in 5.18.0-1 kernel

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1013180: linux-image-5.18.0-1-amd64: System doesn't go to sleep in 5.18.0-1 kernel Alexandr Podgorniy <sacled@scaledteam.ru> - 2022-06-18 16:40 +0200
    Bug#1013180: linux-image-5.18.0-1-amd64: System doesn't go to sleep in 5.18.0-1 kernel Diederik de Haas <didi.debian@cknow.org> - 2022-06-18 17:20 +0200
    Bug#1013180: Undelivered Mail Returned to Sender Diederik de Haas <didi.debian@cknow.org> - 2022-06-18 17:50 +0200
      Bug#1013180: Undelivered Mail Returned to Sender Ben Hutchings <ben@decadent.org.uk> - 2022-06-21 02:20 +0200
        Bug#1013180: Undelivered Mail Returned to Sender Ben Hutchings <ben@decadent.org.uk> - 2022-06-21 02:20 +0200
    Processed: Re: Bug#1013180: System doesn't go to sleep in  5.18.0-1 kernel "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-12-05 19:30 +0100
    Processed: Re: Bug#1013180: System doesn't go to sleep in  5.18.0-1 kernel "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-12-05 19:30 +0100
    Bug#1013180: System doesn't go to sleep in 5.18.0-1 kernel Diederik de Haas <didi.debian@cknow.org> - 2022-12-05 19:30 +0100
    Bug#1013180: System doesn't go to sleep in 5.18.0-1 kernel Diederik de Haas <didi.debian@cknow.org> - 2022-12-06 11:20 +0100
    Bug#1013180: marked as done (linux-image-5.18.0-1-amd64: System  doesn't go to sleep in 5.18.0-1 kernel) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-12-06 11:30 +0100

#75661 — Bug#1013180: linux-image-5.18.0-1-amd64: System doesn't go to sleep in 5.18.0-1 kernel

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>

[toc] | [next] | [standalone]

#75663

[Multipart message — attachments visible in raw view] — view raw

On Saturday, 18 June 2022 16:28:57 CEST Alexandr Podgorniy wrote:
> 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. 

This may be the same as #1012054 so please try if the problem is still present 
with the recently uploaded 5.18.5 version

> Dmesg shows some stacktrace-something after trying to sleep.

If it isn't fixed, sharing such info is expected. 

[toc] | [prev] | [next] | [standalone]

#75664 — Bug#1013180: Undelivered Mail Returned to Sender

[Multipart message — attachments visible in raw view] — view raw

On zaterdag 18 juni 2022 17:13:33 CEST you wrote:
> I'm sorry to have to inform you that your message could not
> be delivered to one or more recipients. It's attached below.
> 
> <sacled@scaledteam.ru>: host scaledteam.ru[81.30.221.145] said: 550 5.1.1
>     <sacled@scaledteam.ru>: Recipient address rejected: User unknown in
> local recipient table (in reply to RCPT TO command)

Close now or wait some days?

[toc] | [prev] | [next] | [standalone]

#75702 — Bug#1013180: Undelivered Mail Returned to Sender

[Multipart message — attachments visible in raw view] — view raw

On Sat, 2022-06-18 at 17:43 +0200, Diederik de Haas wrote:
> On zaterdag 18 juni 2022 17:13:33 CEST you wrote:
> > I'm sorry to have to inform you that your message could not
> > be delivered to one or more recipients. It's attached below.
> > 
> > <sacled@scaledteam.ru>: host scaledteam.ru[81.30.221.145] said: 550 5.1.1
> >     <sacled@scaledteam.ru>: Recipient address rejected: User unknown in
> > local recipient table (in reply to RCPT TO command)
> 
> Close now or wait some days?

Try changing the local part from "scaled" not "sacled".

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable
from a rigged demo.

[toc] | [prev] | [next] | [standalone]

#75703 — Bug#1013180: Undelivered Mail Returned to Sender

[Multipart message — attachments visible in raw view] — view raw

On Tue, 2022-06-21 at 02:08 +0200, Ben Hutchings wrote:
> On Sat, 2022-06-18 at 17:43 +0200, Diederik de Haas wrote:
> > On zaterdag 18 juni 2022 17:13:33 CEST you wrote:
> > > I'm sorry to have to inform you that your message could not
> > > be delivered to one or more recipients. It's attached below.
> > > 
> > > <sacled@scaledteam.ru>: host scaledteam.ru[81.30.221.145] said: 550 5.1.1
> > >     <sacled@scaledteam.ru>: Recipient address rejected: User unknown in
> > > local recipient table (in reply to RCPT TO command)
> > 
> > Close now or wait some days?
> 
> Try changing the local part from "scaled" not "sacled".

... from "sacled" to "scaled", even.

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable
from a rigged demo.

[toc] | [prev] | [next] | [standalone]

#77447 — Processed: Re: Bug#1013180: System doesn't go to sleep in 5.18.0-1 kernel

Processing control commands:

> tag -1 moreinfo
Bug #1013180 [src:linux] linux-image-5.18.0-1-amd64: System doesn't go to sleep in 5.18.0-1 kernel
Ignoring request to alter tags of bug #1013180 to the same tags previously set

-- 
1013180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013180
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#77448 — Processed: Re: Bug#1013180: System doesn't go to sleep in 5.18.0-1 kernel

Processing control commands:

> tag -1 moreinfo
Bug #1013180 [src:linux] linux-image-5.18.0-1-amd64: System doesn't go to sleep in 5.18.0-1 kernel
Added tag(s) moreinfo.

-- 
1013180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013180
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#77449 — Bug#1013180: System doesn't go to sleep in 5.18.0-1 kernel

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 moreinfo

On 5 Jul 2022 18:21:27 +0500 Alexandr Podgorniy <scaled@scaledteam.ru> wrote:
> I tried 5.18.0-2-amd64 kernel recently and noticed that it doesn't go to 
> sleep when Bluetooth mouse connected. Otherwise it's fine. Not tried 
> 5.18.5 yet.

FTR: 5.18.5 is 5.18.0-2 and if that didn't fix it, then it's a different issue.

What's the current status of this bug?
If the issue still occurs, do you have some logs/dmesg output you can share?

[toc] | [prev] | [next] | [standalone]

#77456 — Bug#1013180: System doesn't go to sleep in 5.18.0-1 kernel

[Multipart message — attachments visible in raw view] — view raw

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?

[toc] | [prev] | [next] | [standalone]

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

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web