Description of problem:After hibernating the box and power resumed, I cannot login and the screen is dead. Version-Release number of selected component (if applicable): Fedora 24 How reproducible: Happens every third or fourth time I hibernate box. Steps to Reproduce: 1. login to cinnamon screens, play ... 2. use power button to force hibernation 3. use power button to come back Actual results: Every 3rd or 4th time, screen comes back with clock showing same time as when I shutdown, NO password screen shows, and I cannot get one by pressing any keys. Expected results: Should get password screen and be able to re-new where I was. Additional info: Machine has 4 cpus and a graphics processor. Have not noticed this problem on another machine which has 2 cpus and no graphics processor BUT is used MUCH less. I believe I could login from the other machine using ssh, so if there is anything I can do to capture what is going on for documentation, please let me know. Currently the work around is to unplug and replug in the machine forcing a reboot. If this is the wrong component, please tell me how to find the right one for future reports.
It is possible that if I waited 30 minutes, it might come back but I never do.
Because you choose the wrong component, because Hibernate is a object/relational persistence and query service for Java, i close this bug
Gil, Thanks for all your help. I mentioned that I did not know how to find the component correctly. A smarter person might just have moved the bug to the right place and told me how (as I asked) to find the right place in the future. Perhaps someone smarter will know where to file this if I re-open as a cinnamon-session bug.
(In reply to Ray Holme from comment #3) > Gil, > > Thanks for all your help. I mentioned that I did not know how to find the > component correctly. A smarter person might just have moved the bug to the > right place and told me how (as I asked) to find the right place in the > future. > > Perhaps someone smarter will know where to file this if I re-open as a > cinnamon-session bug. I know knows that you are deficient in something .... maybe if you cared to learn anything more you could use google to determine the correct component, trying to get it with the RPM query Because you are ignorant you have chosen to back the wrong component
Without any logs I'm unable to help (You will have to google or ask on the forum on howto provide logging for the issue).
Also provide hardware specs and graphics driver info.
I can't reproduce the issue here on my T410 so the issue is in another system component (systemd, driver or whatever). Once you decide which component is responsible to reassign and remove me from the CC list.
OK this is a problem with "pm-utils" - someone else on the fedora forum was kind enough to point the direction. I have been using Unix for 35+ years and have not written kernel or utility code for 20 - so sorry I am not cognizant of where to report or which module is responsible unless obvious. Most of the support people are courteous and very kind when I don't know where to report - they re-direct instead of slapping. Calling someone ignorant reflects on the caller not so much as on the person being called. In any case, let me try to document more to the best of my ability. I am not sure where to get hardware information, but hopefully below does it Thank you Leigh. This is a DELL computer with 4 cpus This is from journalctl _ I think ACPI and EFI are to do with the monitor, but not sure - if not - please tell me WHAT to look for. kernel: efi: ACPI=0xc9e09000 ACPI 2.0=0xc9e09000 SMBIOS=0xca40d498 kernel: SMBIOS 2.7 present. kernel: DMI: Dell Inc. Inspiron 660/0XR1GT , BIOS A09 02/01/2013 kernel: Base memory trampoline at [ffff880000098000] 98000 size 24576 kernel: Console: colour dummy device 80x25 kernel: ACPI: Core revision 20160108 kernel: ACPI: 4 ACPI AML tables successfully acquired and loaded kernel: PM: Registering ACPI NVS region [mem 0xc9a78000-0xc9e17fff] (3801088 bytes) kernel: PM: Registering ACPI NVS region [mem 0xca4a9000-0xca4ebfff] (274432 bytes) I have seen this problem on this computer since Fedora 22 and it persists in 24. It does NOT occur on my second computer (wife's) which is also a Dell but has no graphics board and only 2 cpus. Also I CANNOT force this to occur. It is NOT consistent but happens with a frequency of it's own. It has happened 4 times in the last 5 days, but not for two weeks before that. I can ssh into this machine (when the monitor is dead) and gather any information that will help you all find the problem if you give me explicit directions on what to gather - I am used to using the terminal interface. I love Unix and Linux and am only trying to help the community. I did my best to document this and will do all I can to help. This morning was a rude surprise to me.
probably unrelated, but for the record: this machine had a problem with the systemd upgrade immediately after installation upon the cleanup from dnf of systemd, it hung hard killing the entire gnome/cinnamon interface; it had to be rebooted (plug pull) to get going I cannot find the bug in my list anymore (strange) or I would give the id the developer said something about "writing to a console" that was not there - I have not seen any systemd updates since then so I don't know if it was fixed (I update systemd first separately IN CASE) I did the install three times to make sure it was OK. I doubt this is related, but then again it might be
Pm-utils is deprecated by its upstream for a long time and it has been dropped from Fedora since f23. I.e. there is no pm-utils package in the f24. Please do not assign bugs to non-existent components. The hibernation is handled by systemd for a long time, but it's nothing more than just a wrapper over the kernel interface. I think that your problem is probably related to the X driver (as you wrote you can login to the machine via ssh) or it maybe also the kernel itself. Without more information it's hard to say. You didn't write which video driver you use. Please find out which video driver you use and reassign the bug to the xorg-x11-drv-YOURDRIVER (e.g. intel/ati/nouveau) component.
Jaroslav, Humble apologies - it is NOT easy to know which component to file against. The web pop-ups for filing do not match "sleep" or "power"; I was chastised for using "hibernate"; and someone on the fedora forum suggested pm-utils. As I have an open bug (cannot find it under "my bugs") for systemd, but I know it has not been fixed as there have been NO systemd postings since it was filed. Notes about that above in Comment 9, I highly suspect systemd does NOT like my graphics board. Anyway, I am not sure what the heck it is - if you have a better way to identify what it is, please let me know (I bought a refurb with this board which I could care less about as I don't do graphics bigtime). Here is some stuff from journalctl - I hope it tells you what you need. If not, tell me how to find it. Apologies as to volume, I don't know what helps and hopefully errored by giving too much. kernel: intel_rapl: Found RAPL domain package kernel: intel_rapl: Found RAPL domain core kernel: intel_rapl: Found RAPL domain uncore kernel: intel_rapl: RAPL package 0 domain package locked by BIOS /usr/libexec/gdm-x-session[1520]: (==) Matched intel as autoconfigured driver 2 /usr/libexec/gdm-x-session[1520]: (II) LoadModule: "intel" /usr/libexec/gdm-x-session[1520]: (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so /usr/libexec/gdm-x-session[1520]: (II) Module intel: vendor="X.Org Foundation" /usr/libexec/gdm-x-session[1520]: (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: /usr/libexec/gdm-x-session[1520]: (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 /usr/libexec/gdm-x-session[1520]: (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 /usr/libexec/gdm-x-session[1520]: (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300 /usr/libexec/gdm-x-session[1520]: (II) intel(G0): Using Kernel Mode Setting driver: i915, version 1.6.0 20151218 /usr/libexec/gdm-x-session[1520]: (--) intel(G0): Integrated Graphics Chipset: Intel(R) HD Graphics 2500 /usr/libexec/gdm-x-session[1520]: (--) intel(G0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx; using a maximum of 4 threads /usr/libexec/gdm-x-session[1520]: (==) intel(G0): Depth 24, (--) framebuffer bpp 32 /usr/libexec/gdm-x-session[1520]: (==) intel(G0): RGB weight 888 /usr/libexec/gdm-x-session[1520]: (==) intel(G0): Default visual is TrueColor /usr/libexec/gdm-x-session[1520]: (II) intel(G0): Output VGA1 has no monitor section /usr/libexec/gdm-x-session[1520]: (II) intel(G0): Enabled output VGA1 /usr/libexec/gdm-x-session[1520]: (II) intel(G0): Output HDMI1 has no monitor section /usr/libexec/gdm-x-session[1520]: (II) intel(G0): Enabled output HDMI1 /usr/libexec/gdm-x-session[1520]: (II) intel(G0): Output DP1 has no monitor section /usr/libexec/gdm-x-session[1520]: (II) intel(G0): Enabled output DP1 /usr/libexec/gdm-x-session[1520]: (--) intel(G0): Using a maximum size of 256x256 for hardware cursors /usr/libexec/gdm-x-session[1520]: (II) intel(G0): Output VIRTUAL1 has no monitor section /usr/libexec/gdm-x-session[1520]: (II) intel(G0): Enabled output VIRTUAL1 /usr/libexec/gdm-x-session[1520]: (==) intel(G0): TearFree disabled /usr/libexec/gdm-x-session[1520]: (==) intel(G0): DPI set to (96, 96) /usr/libexec/gdm-x-session[1520]: (II) intel(G0): SNA initialized with Ivybridge (gen7, gt1) backend /usr/libexec/gdm-x-session[1520]: (==) intel(G0): Backing store enabled /usr/libexec/gdm-x-session[1520]: (==) intel(G0): Silken mouse enabled /usr/libexec/gdm-x-session[1520]: (II) intel(G0): HW Cursor enabled /usr/libexec/gdm-x-session[1520]: (II) intel(G0): RandR 1.2 enabled, ignore the following RandR disabled message. /usr/libexec/gdm-x-session[1520]: (==) intel(G0): DPMS enabled /usr/libexec/gdm-x-session[1520]: (==) intel(G0): Display hotplug detection enabled /usr/libexec/gdm-x-session[1520]: (II) intel(G0): [DRI2] Setup complete /usr/libexec/gdm-x-session[1520]: (II) intel(G0): [DRI2] DRI driver: i965 /usr/libexec/gdm-x-session[1520]: (II) intel(G0): [DRI2] VDPAU driver: va_gl /usr/libexec/gdm-x-session[1520]: (II) intel(G0): direct rendering: DRI2 DRI3 enabled /usr/libexec/gdm-x-session[1520]: (II) intel(G0): hardware support for Present enabled kernel: perf_event_intel: PMU erratum BJ122, BV98, HSD29 workaround disabled, HT off
Thanks for info, from the log it seems it's Intel. Reassigning to the Intel video driver for the start as it should correctly wakeup with the video correcly running.
Just let me know if you need more information, and, if getting is not obvious, how to get it for you. Thanks for your help.
*** Bug 1404717 has been marked as a duplicate of this bug. ***
I don't know if this problem is of interest to anyone besides myself. I do NOT know if hardware is causing it and have no way to know. I would be happy to conduct tests as this occurs at least 1/3 of the time that I put this machine to sleep.
For the record, this occurs VERY regularly (about every 2nd time). I am almost tempted to force a HALT and not even try to Sleep. This does not happen on my 2nd computer (wife's) which does not have a graphics processor and 2 less cpuS.
I don't know if things changed due to hardware fixing itself or new release, but I have NOT seen this problem in many days and have had many returns from sleep. I am hoping someone fixed it and we can just close this - hoping it will not raise it's ugly (sleepy) little head again. Feel free to close it or leave open - as you wish.
This has not happened in the last two weeks over a myriad of sleeps. Some OS update fixed it.