this post was submitted on 05 Jul 2025
378 points (98.5% liked)

linuxmemes

26099 readers
1164 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    • Β 

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    378
    I give up (sh.itjust.works)
    submitted 3 days ago by [email protected] to c/[email protected]
    42 comments fedilink hide all child comments
     

    Absolutely nothing in journalctl, dmesg, etc 😭

    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 22 points 3 days ago* (last edited 3 days ago) (6 children)

    The easiest way to find something that could help is journalctl -r --boot=-1 after rebooting your laptop. These options will display all of the entries in reverse chronological order, starting from when you powered the computer off. When you find something complaining about waking from suspend, just look up that entry in a search engine. This method helped me many times, mostly with amdgpu bugs in the kernel fucking with my system.

    Edit:

    Absolutely nothing in journalctl, dmesg, etc 😭

    Woops, didn't read that. dmesg only keeps track of everything from the last boot, so unless you used SSH to remote into your laptop while it tried wake from suspend, you wouldn't see anything anyways. journalctl on its own vomits out a metric fuckton of entries, but it does persist across reboots. If you use my aforementioned options or something like journalctl | grep suspend, it might be easier to find something

    [–] [email protected] 10 points 3 days ago* (last edited 3 days ago) (5 children)

    That's the issue. The journal just... stops the moment it enters suspend. I now even have an alias for that specific purpose. No one seems to have this issue online.

    Jul 05 20:58:59 main systemd[1]: session-4.scope: Unit now frozen-by-parent.
Jul 05 20:58:59 main systemd[1]: user-995.slice: Unit now frozen-by-parent.
Jul 05 20:58:59 main systemd[1]: user.slice: Unit now frozen.
Jul 05 20:58:59 main systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Jul 05 20:58:59 main systemd-sleep[82780]: Successfully froze unit 'user.slice'.
Jul 05 20:58:59 main systemd-sleep[82780]: Performing sleep operation 'suspend'...
Jul 05 20:58:59 main kernel: PM: suspend entry (deep)
(END)

    I appreciate your help though. Someday, I'll get it fixed.

    [–] [email protected] 20 points 3 days ago (3 children)

    Based on the information given in logs + the rest of the thread thus far, I'd assume the problem either lies in a kernel bug or the laptops' firmware, BIOS. The logs claim the system successfully going into S3 (deep) sleep. It's possible for the affected laptops to have broken S3 suspend behavior.

    A few things that might be worth checking include seeing if other sleep modes (s2idle) are available and testing them, checking for BIOS updates, and checking for Linux/generic suspend options within the BIOS.

    [–] [email protected] 6 points 3 days ago (1 children)

    Didn't a lot of laptops completely remove S3 sleep in favor of S0 sleep

    [–] [email protected] 5 points 2 days ago

    Some modern laptops have completely removed support for S3 sleep, as well as some still include it but clearly never tested it. I have seen multiple OEMs that have S3 sleep "available" but with the Windows installation utilizing S0 by default. If such OEMs are lazy (which a lot of them are), they just won't bother to properly test the functionality as long as the default OS configuration they ship works. Same kind of deal now with how many OEMs (mostly used to) ship non-standard ACPI implementations that required extra drivers in Windows to function (or would just not work correctly under Linux).

    load more comments (1 replies)
    load more comments (2 replies)
    load more comments (2 replies)