==System Environment== -------------------------- Regression: yes, bisect later Non-working platforms: BDW ==kernel== -------------------------- nightly-2015-01-28/70438b51bdd44180b83f10591c3bdc1832d11dc2 ==Bug detailed description== -------------------------- Some times resume from S4 state will lost the processes which are running before, seems the machine was reboot rather than resume from S4. This issue have about 20% chance to reproduce. ==Reproduce steps== ---------------------------- 1.xinit& 2.echo disk > /sys/power/state 3.press the power botton to resume. 4.check if xinit is still running.
This is not a regression. No good commit was found when I tried to select 1-2 commits in every month from Sep last year to Jan this year.
As usual for suspend/resume issues, could you check if this can be reproduced when booting with the nomodeset kernel parameter?
(In reply to Imre Deak from comment #2) > As usual for suspend/resume issues, could you check if this can be > reproduced when booting with the nomodeset kernel parameter? root@x-bdw05:~# cat /proc/cmdline BOOT_IMAGE=kernels//nightly_parents/2015_02_06/drm-intel-nightly/75ce8af7223f8b8554e2566d0c48d9fb844f0e3e/bzImage_x86_64 root=/dev/sda3 drm.debug=0xe i915.modeset=0 hostname=x-bdw05 modules_path=kernels//nightly_parents/2015_02_06/drm-intel-nightly/75ce8af7223f8b8554e2566d0c48d9fb844f0e3e/modules_x86_64/lib/modules/3.19.0-rc7_drm-intel-nightly_75ce8a_20150206+ acpi_rsdp=0xac7e1014 i915.modeset was set to 0. issue still exist.
(In reply to Ding Heng from comment #3) > (In reply to Imre Deak from comment #2) > > As usual for suspend/resume issues, could you check if this can be > > reproduced when booting with the nomodeset kernel parameter? > > root@x-bdw05:~# cat /proc/cmdline > BOOT_IMAGE=kernels//nightly_parents/2015_02_06/drm-intel-nightly/ > 75ce8af7223f8b8554e2566d0c48d9fb844f0e3e/bzImage_x86_64 root=/dev/sda3 > drm.debug=0xe i915.modeset=0 hostname=x-bdw05 > modules_path=kernels//nightly_parents/2015_02_06/drm-intel-nightly/ > 75ce8af7223f8b8554e2566d0c48d9fb844f0e3e/modules_x86_64/lib/modules/3.19.0- > rc7_drm-intel-nightly_75ce8a_20150206+ acpi_rsdp=0xac7e1014 > > i915.modeset was set to 0. issue still exist. Ok, so this is not our bug (at least at this point). I suggest opening a bug at bugzilla.kernel.org under the Power Management component, attaching a dmesg log taken with the initcall_debug kernel parameter and using serial or net console. If possible you could try narrowing down the issue by disabling drivers, starting perhaps with the one initcall_debug shows as a culprit. If you manage to get the dmesg log, you could also send a report to lkml referencing this and the bugzilla.kernel.org bugzilla ticket.
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.