Bug 201587
Summary: | S0ix: unable to enter S0ix - HP EliteBook Folio G1 (SKL) | ||
---|---|---|---|
Product: | Power Management | Reporter: | RussianNeuroMancer (russianneuromancer) |
Component: | Hibernation/Suspend | Assignee: | Rafael J. Wysocki (rjw) |
Status: | RESOLVED UNREPRODUCIBLE | ||
Severity: | normal | CC: | cynthiawilliams2944, duke, IdaWallace89, lenb, rui.zhang, wendy.wang |
Priority: | P1 | ||
Hardware: | Intel | ||
OS: | Linux | ||
Kernel Version: | 4.19.0 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | dmesg of Linux 4.19.0 with enabled pm_debug_messages |
Description
RussianNeuroMancer
2018-11-01 13:51:29 UTC
Just in case: suspend freeze was tested with powertop --auto-tune. Issue is still reproducible on Linux 5.0rc4 with this patches https://patchwork.kernel.org/patch/10714257/ Correction: Issue is still reproducible on Linux 5.0rc4 with this patches https://patchwork.kernel.org/project/platform-driver-x86/list/?series=74547 Have you tried Linux v5.4-rcx kernel recently? Both V5.3 and v5.4 merged improvement patches for S0ix, covering NVMe and EC components. If issue still can be reproduce with v5.4-rcx, please paste the outputs of /sys/kernel/debug/pmc_core Wendy, this issue is no longer reproducible with Linux 5.5. Is possible, could you please ask developers to look into https://gitlab.freedesktop.org/drm/intel/issues/347 ? It's two and half years old. The issue you've asked (https://gitlab.freedesktop.org/drm/intel/issues/347 ) is a gfx bug, in linux kernel, gfx bug discussion and debug should work on https://bugs.freedesktop.org/, how about reopen the issue and ask for the comments: https://bugs.freedesktop.org/show_bug.cgi?id=103229 if you see it still can be reproduced. > how about reopen the issue and ask for the comments: > https://bugs.freedesktop.org/show_bug.cgi?id=103229 if you see it still can > be reproduced. As I understand bugs.freedesktop.org is not longer relevant, as you can see for example here: https://bugs.freedesktop.org/describecomponents.cgi?product=DRI > Moved to https://gitlab.freedesktop.org/drm/intel Also as you can see in Comment 59 of https://bugs.freedesktop.org/show_bug.cgi?id=103229 I had to create new bugreport because original reporter don't answer anymore. My new bugreport already has been moved from old bugtracker https://bugs.freedesktop.org/show_bug.cgi?id=111201 to new bugtracker https://gitlab.freedesktop.org/drm/intel/issues/347 Unfortunate result of this back and forth with first bugreport (103229) second bugreport (111201) and third bugreport (347) is that all is happening is I re-test drm-tip and confirm that issue is not fixed for two and half years :( |