System Environment: -------------------------- Platform: Haswell Mobile kernel (drm-intel-testing)d1b2b826f0969182f055d11c991f90fdc6a4924a Bug detailed description: ----------------------------- System hung while resuming from S3, This bug only occurs on -testing, it can not reproduce on -next-queued(commit d538bbdfde34028b5c5b0ba92b3c2096c5afb82c) and -fixes(commit 52e1e223456e3aa747e9932f95948381f04b3b26). added option "no_console_suspend", netconsole hasn't any output. Reproduce steps: ---------------------------- 1. remove I915 modules and add kernel cmdline option "no_console_suspend" in /boot/grub2/grub.cfg 2. echo mem > /sys/power/state 3. press power button to resume
(In reply to comment #0) > System Environment: > -------------------------- > Platform: Haswell Mobile > kernel (drm-intel-testing)d1b2b826f0969182f055d11c991f90fdc6a4924a > > > Bug detailed description: > ----------------------------- > System hung while resuming from S3, > > This bug only occurs on -testing, it can not reproduce on > -next-queued(commit d538bbdfde34028b5c5b0ba92b3c2096c5afb82c) and > -fixes(commit 52e1e223456e3aa747e9932f95948381f04b3b26). So the bug is already fixed..? Do we know which commit caused the bug and which one fixed it? Thanks, Paulo
(In reply to comment #1) > (In reply to comment #0) > > System Environment: > > -------------------------- > > Platform: Haswell Mobile > > kernel (drm-intel-testing)d1b2b826f0969182f055d11c991f90fdc6a4924a > > > > > > Bug detailed description: > > ----------------------------- > > System hung while resuming from S3, > > > > This bug only occurs on -testing, it can not reproduce on > > -next-queued(commit d538bbdfde34028b5c5b0ba92b3c2096c5afb82c) and > > -fixes(commit 52e1e223456e3aa747e9932f95948381f04b3b26). > > So the bug is already fixed..? > > Do we know which commit caused the bug and which one fixed it? > > Thanks, > Paulo It's hard to bisect which commit caused the bug and which on fixed it. I tried on latest -nightly(commit aabd627ec77463dc9c064ce2735ef71f48a2ec94), still can not reproduce this bug. thanks.
Since the bug doesn't happen either with -fixed or -next-queued, I guess we consider it as fixed. Closing bug.
Verify the bug due to it doesn't happen either with -fixed or -next-queued.
Closing old verified.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.