[Bug 1230418] New: [REGRESSION] laptop refuses to go to sleep and starts stuttering when battery is full
https://bugzilla.suse.com/show_bug.cgi?id=1230418 Bug ID: 1230418 Summary: [REGRESSION] laptop refuses to go to sleep and starts stuttering when battery is full Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: PC OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: screening-team-bugs@suse.de Reporter: pinchon.guillaume@gmail.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877263 --> https://bugzilla.suse.com/attachment.cgi?id=877263&action=edit System details I've had these issues a while back and it was fixed, but it's back ONCE AGAIN ! When I get my laptop out of its pouch I often find its battery is completely empty or it overheated itself to sleep! I also find myself having to reboot every time the battery gets fully charged because the CPU gets locked at 400Mhz (THIS WAS FIXED 3 OR 4 MONTH AGO) Sorry for the tone but this is becoming very frustrating, this issue comes back at random when the kernel is updated and is damaging for both the battery and the CPU/GPU. I feel like someone is pushing old code back into the main branch every time they're merging their work... For the love of god, I beg of you to do some testing on this bug on every update -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230418 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Normal -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230418 https://bugzilla.suse.com/show_bug.cgi?id=1230418#c1 --- Comment #1 from Stefan Hundhammer <shundhammer@suse.com> --- Without knowing exactly which model of laptop this is all about, nobody can even start doing anything about this. Please attach the output of 'hwinfo' and, if you have it installed, 'inxi'. And no, there is no way to test every bug against every hardware for every update. Do you have any idea how many different types of laptops there are out there? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230418 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pinchon.guillaume@gmail.com Flags| |needinfo?(pinchon.guillaume | |@gmail.com) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230418 https://bugzilla.suse.com/show_bug.cgi?id=1230418#c2 --- Comment #2 from Stefan Hundhammer <shundhammer@suse.com> --- And BTW yes, I saw your attachment, but the important part are the exact hardware components. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230418 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(pinchon.guillaume | |@gmail.com) | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230418 https://bugzilla.suse.com/show_bug.cgi?id=1230418#c6 --- Comment #6 from Stefan Hundhammer <shundhammer@suse.com> --- Over the weekend I had a problem which might or might not be related: bug #1230629 If your e1000e kernel module spits errors in the journal when you suspend or hibernate, check if the laptop REALLY went to sleep when you close the lid: The LED in the 'i' of the 'Thinkpad' logo should blink, not be solid on. If you have that problem, try 'sudo rmmod e1000e' before suspending. See bug #1230629 comment #7 for a more permanent workaround. The kernel developers are working on a real fix, though. But that whole problem might also be unrelated; just wanted to let you know. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230418 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs@suse.de |kernel-bugs@opensuse.org Component|Other |Kernel -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230418 https://bugzilla.suse.com/show_bug.cgi?id=1230418#c13 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com --- Comment #13 from Takashi Iwai <tiwai@suse.com> --- It's hard to say what prevents suspending. You can test the direct suspend by echo mem > /sys/power/state as root user. This skips the whole user-space side hooks and checks and triggers the kernel suspend. If this works, it means something in user-space causes the problem. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230418 https://bugzilla.suse.com/show_bug.cgi?id=1230418#c14 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby@suse.com --- Comment #14 from Jiri Slaby <jslaby@suse.com> --- (In reply to Guillaume Pinchon from comment #12)
UPDATE3: that's still not fixed, even with the latest stable kernel, switching to Fedora this distro is unusable.
Good luck then. Provided both fedora and opensuse follows the latest upstream, I wonder if it helped at all. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230418 https://bugzilla.suse.com/show_bug.cgi?id=1230418#c15 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #15 from Takashi Iwai <tiwai@suse.com> --- Closing as the reporter won't be able to test. Feel free to reopen if the problem persists with the latest TW release. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com