Bug 1066590 - ACPI: Error installing CMOS-RTC region handler
Summary: ACPI: Error installing CMOS-RTC region handler
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-18 16:52 UTC by Orion Poplawski
Modified: 2014-12-05 23:00 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-05 23:00:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Outputs of "journalctl -alfxm -o verbose --system --user" around the bug (across a period of 15 minutes) (574.60 KB, text/plain)
2014-08-03 15:36 UTC, Mihai Maruseac
no flags Details

Description Orion Poplawski 2014-02-18 16:52:08 UTC
Description of problem:

On resume from sleep we see:

Feb 18 00:12:06 palila kernel: [31436.609320] PM: resume of devices complete after 2915.246 msecs
Feb 18 00:12:06 palila kernel: [31436.610084] Restarting tasks ... done.
Feb 18 00:12:06 palila systemd: Time has been changed
Feb 18 00:12:06 palila kernel: [31436.639264] ACPI: Error installing CMOS-RTC region handler
Feb 18 00:12:06 palila kernel: [31436.642618] video LNXVIDEO:00: Restoring backlight state
Feb 18 00:12:06 palila kernel: [31436.662116] ACPI: Error installing CMOS-RTC region handler

Version-Release number of selected component (if applicable):
3.13.3-201.fc20.x86_64

How reproducible:
Every time

Dell Inspiron 1470, BIOS A04 (Seems up to date)

Comment 1 Manmathan Kumarathurai 2014-05-08 18:24:40 UTC
I have the above problem resulting in laptop failing to restore from hibernation. It starts a fresh session without restoring previous gnome desktop session. Also see: https://ask.fedoraproject.org/en/question/39280/hibernation-problem-acpi-error-installing-cmos-rtc-region-handler/

Comment 2 Justin M. Forbes 2014-05-21 19:39:22 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.14.4-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 3 Orion Poplawski 2014-05-30 15:12:03 UTC
Still present with 3.14.4-200.fc20.

Comment 4 Neil 2014-08-01 06:38:36 UTC
Still present with 3.15.6-200.fc20

Comment 5 Mihai Maruseac 2014-08-03 15:36:15 UTC
Created attachment 923635 [details]
Outputs of "journalctl -alfxm -o verbose --system --user" around the bug (across a period of 15 minutes)

Still present with 3.15.7-200.fc20

I get the message when I close the lid to start the suspend process. Then the suspend doesn't get through, it seems the CPU is in a soft-lockup state. When I try to resume the session (after 1, 5, 10, 15, 20, 30 minutes -- always the same behavior) I am locked outside the GUI but I can use the virtual terminals on Ctrl-Alt-F2 (though I cannot start another GUI instance).

I am attaching systemd logs obtained by running

> journalctl -alfxm -o verbose --system --user > /data/logs

using the default settings in /etc/systemd/journald.conf on a freshly booted-up system with only a Gnome Terminal opened (which runs only that command). No default start applications so I only have what Gnome starts up with beside this terminal.

I'll be posting as comments parts of the logs that I find strange/revealing clues:

1. lid closed at 10:15:03.074687

ACPI: Error installing CMOS-RTC region handler
i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
ivb_uncore 0000:00:00.0: no hotplug settings from platform
<info> sleep requested (sleeping: no  enabled: yes)
<info> sleeping or disabling...
ivb_uncore 0000:00:00.0: using default PCI settings
pcieport 0000:00:01.0: no hotplug settings from platform
nouveau 0000:01:00.0: no hotplug settings from platform
i915 0000:00:02.0: no hotplug settings from platform

(and so on for a whole bunch of modules)

2. system state suspend entered at 10:15:06.407293

Suspending system...
Started Sendmail Mail Transport Client.

(why does it start now?)

PM: Syncing filesystems ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.007 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.097 seconds) done.
PM: Entering mem sleep

(last message at 10:15:10.312354)

sd 1:0:0:0: [sda] Synchronizing SCSI cache
sd 1:0:0:0: [sda] Stopping disk

3. nouveau kicks in at 10:15:10.312984 (exactly after previous message)

nouveau  [     DRM] suspending display...
nouveau  [     DRM] unpinning framebuffer(s)...
nouveau  [     DRM] evicting buffers...
nouveau  [     DRM] waiting for kernel channels to go idle...
nouveau  [     DRM] suspending client object trees...
nouveau  [     DRM] suspending kernel object tree...
nouveau E[   PDISP][0000:01:00.0][0xc000907c][ffff880035c3b500] fini: 0xc2061088
nouveau E[   PDISP][0000:01:00.0][0xc000907c][ffff880035c3b500] failed suspend, -16

(10:15:10.313175)

nouveau E[     DRM] 0xd1500000:0xd15c7c00 suspend failed with -16
nouveau E[     DRM] 0xdddddddd:0xd1500000 suspend failed with -16
nouveau E[     DRM] 0xffffffff:0xdddddddd suspend failed with -16
nouveau E[     DRM] 0xffffffff:0xffffffff suspend failed with -16
nouveau  [     DRM] resuming display...

(why?)

pci_pm_suspend(): nouveau_pmops_suspend+0x0/0xb0 [nouveau] returns -16
dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -16
PM: Device 0000:01:00.0 failed to suspend async: error -16
PM: Some devices failed to suspend, or early wake event detected

4. And now it starts resuming even though by now I'm not watching it anymore (10:15:10.313549 is 7 seconds past the lid close event). Then it goes back to sleep (10:15:13.934626 : PM: Preparing system for standby sleep), tries to stop nouveau again and panics (10:15:16.627695 13 seconds already)

nouveau  [     DRM] suspending display...
nouveau  [     DRM] unpinning framebuffer(s)...
------------[ cut here ]------------
WARNING: CPU: 2 PID: 2815 at drivers/gpu/drm/nouveau/nouveau_bo.c:358 nouveau_bo_unpin+0x120/0x130 [nouveau]()
Modules linked in: rfcomm ip6t_rpfilter ppdev parport_pc parport fuse vmw_vsock_vmci_transport vsock vmw_vmci ip6t_REJECT xt_conntrack bnep ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel rtsx_pci_ms acer_wmi sparse_keymap iTCO_wdt snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ghash_clmulni_intel snd_hda_intel snd_hda_controller snd_hda_codec iTCO_vendor_support snd_hwdep memstick arc4 microcode iwldvm mac80211 rtsx_pci_sdmmc
mmc_core snd_seq btusb snd_seq_device snd_pcm iwlwifi snd_timer bluetooth joydev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev rtsx_pci serio_raw media lpc_ich cfg80211 mei_me mfd_core i2c_i801 mei thinkpad_acpi shpchp snd soundcore rfkill tpm_tis tpm binfmt_misc nouveau i915 mxm_wmi ttm r8169 i2c_algo_bit mii drm_kms_helper drm i2c_core wmi video
CPU: 2 PID: 2815 Comm: kworker/u16:69 Not tainted 3.15.7-200.fc20.x86_64 #1
Hardware name: LENOVO 33543XG/33543XG, BIOS H3ET29WW(1.12) 06/01/2012
Workqueue: events_unbound async_run_entry_fn
Workqueue: events_unbound async_run_entry_fn
 0000000000000000 00000000716cf494 ffff88009f2abc18 ffffffff816ef92e
 0000000000000000 ffff88009f2abc50 ffffffff8108933d ffff8800a0112000
 ffff880127a7c380 ffff88003667c170 ffff88003667c000 ffff880127a7c000
Call Trace:
 [<ffffffff816ef92e>] dump_stack+0x45/0x56
 [<ffffffff8108933d>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff8108946a>] warn_slowpath_null+0x1a/0x20
 [<ffffffffa02678a0>] nouveau_bo_unpin+0x120/0x130 [nouveau]
 [<ffffffffa027331e>] nouveau_display_suspend+0x5e/0xd0 [nouveau]
 [<ffffffffa0260e67>] nouveau_do_suspend+0x157/0x2b0 [nouveau]
 [<ffffffffa0260ffe>] nouveau_pmops_suspend+0x3e/0xb0 [nouveau]
 [<ffffffff8138fa76>] pci_pm_suspend+0x76/0x140
 [<ffffffff8138fa00>] ? pci_pm_freeze+0xf0/0xf0
 [<ffffffff81469499>] dpm_run_callback+0x49/0xa0
 [<ffffffff81469f6b>] __device_suspend+0xfb/0x2b0
 [<ffffffff8146a27f>] async_suspend+0x1f/0xa0
 [<ffffffff810b26b9>] async_run_entry_fn+0x39/0x120
 [<ffffffff810a4af6>] process_one_work+0x176/0x430
 [<ffffffff810a578b>] worker_thread+0x11b/0x3a0
 [<ffffffff810a5670>] ? rescuer_thread+0x3b0/0x3b0
 [<ffffffff810ac528>] kthread+0xd8/0xf0
 [<ffffffff810ac450>] ? insert_kthread_work+0x40/0x40
 [<ffffffff816ff8bc>] ret_from_fork+0x7c/0xb0
 [<ffffffff810ac450>] ? insert_kthread_work+0x40/0x40
---[ end trace 43b620e62abf118d ]---

Then it goes through the same cycle as in previous point.

5. suspend module fails to start at 10:15:22.037441 (19 seconds now)

Failed to start Suspend.
Dependency failed for Suspend.
Unit systemd-suspend.service entered failed state.
Stopping Sleep.
Stopped target Sleep.
Operation finished.

(and now NetworkManager comes back in -- I suspect because the suspend failed and the system is coming back alive)

<info> wake requested (sleeping: yes  enabled: yes)
...

6. Lid opened at 10:30:54.953261

I get the same messages as in 1. But in a never-ending loop, they keep on repeating while I'm stuck out of GUI (though I can access virtual terminals and I do that at 10:31:39.916019)

7. telinit 6 at 10:33:11.595876 requested by user :)

No other errors show up. Sadly, the previous session is lost (in this case it was empty anyway).

Comment 6 Stuart Rogers 2014-08-18 16:53:11 UTC
This bug is still happening for me on kernel 3.15.10-200.fc20.x86_64 and I suspect is the reason hibernate will not resume but always boot normally. Does not seem to cause any other problems I've noticed yet. May also explain why my messages from boot are an hour ahead of actual system time!

Comment 7 nterry 2014-08-19 19:28:13 UTC
I have this issue with 3.15.10-200.fc20.x86_64 on an HP dv6-6173cl laptop.  However I just tried hibernating, which I don't normally do, and it worked fine.  As yet I have seen no effects apart from the message on boot.

Comment 8 Neil 2014-09-11 21:42:28 UTC
Still present on kernel 3.15.10-201.fc20.x86_64

Comment 9 Justin M. Forbes 2014-11-13 16:01:09 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.

Comment 10 Orion Poplawski 2014-12-05 23:00:17 UTC
I'm not seeing this any more.


Note You need to log in before you can comment on or make changes to this bug.