From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxim Levitsky Subject: Lokdep messages during resume from disk Date: Wed, 03 Feb 2010 18:31:34 +0200 Message-ID: <1265214694.18521.3.camel@maxim-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: linux-pm List-Id: linux-pm@vger.kernel.org Hi, Since now, my notebook finally have the ability to do hibernate reliably, I want to report this, probably cosmetic issue. This lockdep message shows up always in the kernel that does the resume. [ 3.111118] Freezing user space processes ... (elapsed 0.01 seconds) done. [ 3.130340] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [ 3.150375] PM: Reading hibernation image. [ 3.160309] PM: Loading image data pages (128548 pages) ... done [ 14.385776] PM: Read 514192 kbytes in 11.22 seconds (45.82 MB/s) [ 14.385867] PM: Image successfully loaded [ 14.386838] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 14.470597] ata_piix 0000:00:1f.1: PCI INT A disabled [ 14.470997] PM: quiesce of devices complete after 84.232 msecs [ 14.472289] PM: late quiesce of devices complete after 1.200 msecs [ 14.472399] Suspending EC transactions [ 14.472850] Disabling non-boot CPUs ... [ 14.591472] CPU 1 is now offline [ 14.591555] lockdep: fixing up alternatives. [ 14.591646] SMP alternatives: switching to UP code [ 14.598663] [ 14.598665] ============================================= [ 14.598824] [ INFO: possible recursive locking detected ] [ 14.598911] 2.6.33-rc5-wl #37 [ 14.598987] --------------------------------------------- [ 14.599074] resume/1066 is trying to acquire lock: [ 14.599170] (s_active){++++.+}, at: [] sysfs_addrm_finish+0x43/0x70 [ 14.599483] [ 14.599485] but task is already holding lock: [ 14.599656] (s_active){++++.+}, at: [] sysfs_get_active_two+0x45/0x60 [ 14.599967] [ 14.599969] other info that might help us debug this: [ 14.600008] 6 locks held by resume/1066: [ 14.600008] #0: (&buffer->mutex){+.+.+.}, at: [] sysfs_write_file+0x44/0x170 [ 14.600008] #1: (s_active){++++.+}, at: [] sysfs_get_active_two+0x45/0x60 [ 14.600008] #2: (s_active){++++.+}, at: [] sysfs_get_active_two+0x27/0x60 [ 14.600008] #3: (pm_mutex/1){+.+.+.}, at: [] software_resume+0x34/0x210 [ 14.600008] #4: (cpu_add_remove_lock){+.+.+.}, at: [] cpu_maps_update_begin+0x17/0x20 [ 14.600008] #5: (cpu_hotplug.lock){+.+.+.}, at: [] cpu_hotplug_begin+0x2c/0x60 [ 14.600008] [ 14.600008] stack backtrace: [ 14.600008] Pid: 1066, comm: resume Not tainted 2.6.33-rc5-wl #37 [ 14.600008] Call Trace: [ 14.600008] [] __lock_acquire+0xf40/0x1d00 [ 14.600008] [] ? add_lock_to_list+0x5a/0xe0 [ 14.600008] [] ? lockdep_init_map+0x5e/0x5b0 [ 14.600008] [] lock_acquire+0x9b/0x160 [ 14.600008] [] ? sysfs_addrm_finish+0x43/0x70 [ 14.600008] [] sysfs_deactivate+0xd7/0x130 [ 14.600008] [] ? sysfs_addrm_finish+0x43/0x70 [ 14.600008] [] sysfs_addrm_finish+0x43/0x70 [ 14.600008] [] sysfs_remove_dir+0x88/0xd0 [ 14.600008] [] kobject_del+0x16/0x40 [ 14.600008] [] kobject_release+0x6e/0x240 [ 14.600008] [] ? kobject_release+0x0/0x240 [ 14.600008] [] kref_put+0x37/0x70 [ 14.600008] [] kobject_put+0x27/0x60 [ 14.600008] [] cacheinfo_cpu_callback+0xa2/0xdb [ 14.600008] [] notifier_call_chain+0x47/0x90 [ 14.600008] [] raw_notifier_call_chain+0x16/0x20 [ 14.600008] [] _cpu_down+0x140/0x2e0 [ 14.600008] [] disable_nonboot_cpus+0xb0/0x120 [ 14.600008] [] hibernation_restore+0xa5/0x130 [ 14.600008] [] software_resume+0x1ef/0x210 [ 14.600008] [] resume_store+0xb4/0xc0 [ 14.600008] [] kobj_attr_store+0x17/0x20 [ 14.600008] [] sysfs_write_file+0xe6/0x170 [ 14.600008] [] vfs_write+0xb8/0x1a0 [ 14.600008] [] sys_write+0x51/0x90 [ 14.600008] [] system_call_fastpath+0x16/0x1b [ 14.605822] Task events/1 (pid = 10) is on cpu 1 (state = 1, flags = 84208040) [ 14.605940] Task kblockd/1 (pid = 142) is on cpu 1 (state = 1, flags = 84208040) <6>[ 3060.213061] PM: Restoring platform NVS memory Everything works fine now though. Best regards, Maxim Levitsky