From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758668Ab3BFVFJ (ORCPT ); Wed, 6 Feb 2013 16:05:09 -0500 Received: from hydra.sisk.pl ([212.160.235.94]:53957 "EHLO hydra.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757301Ab3BFVFG (ORCPT ); Wed, 6 Feb 2013 16:05:06 -0500 From: "Rafael J. Wysocki" To: Artem Savkov Cc: cpufreq@vger.kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, Viresh Kumar Subject: Re: [BUG] cpufreq: sleeping function called from invalid context at kernel/workqueue.c:2811 Date: Wed, 06 Feb 2013 22:11:25 +0100 Message-ID: <1543919.ZBNJa64WB5@vostro.rjw.lan> User-Agent: KMail/4.9.5 (Linux/3.8.0-rc6; KDE/4.9.5; x86_64; ; ) In-Reply-To: <20130206202513.GA5626@thinkpad.lan> References: <20130206202513.GA5626@thinkpad.lan> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday, February 07, 2013 12:25:13 AM Artem Savkov wrote: > I get the following BUG on suspend using systemd-sleep(this doesn't > happen with pm-suspend). This seems to be introduced by some of the > Viresh's patches. Which branch from which day? Rafael > [ 94.908046] Disabling non-boot CPUs ... > [ 94.908416] BUG: sleeping function called from invalid context at kernel/workqueue.c:2811 > [ 94.908419] in_atomic(): 1, irqs_disabled(): 1, pid: 4038, name: systemd-sleep > [ 94.908421] 7 locks held by systemd-sleep/4038: > [ 94.908439] #0: (&buffer->mutex){......}, at: [] sysfs_write_file+0x29/0x100 > [ 94.908448] #1: (s_active#179){......}, at: [] sysfs_write_file+0x8d/0x100 > [ 94.908459] #2: (pm_mutex){......}, at: [] pm_suspend+0x40/0x1e0 > [ 94.908469] #3: (cpu_add_remove_lock){......}, at: [] cpu_maps_update_begin+0x14/0x20 > [ 94.908476] #4: (cpu_hotplug.lock){......}, at: [] cpu_hotplug_begin+0x22/0x50 > [ 94.908487] #5: (&per_cpu(cpu_policy_rwsem, cpu)){......}, at: [] lock_policy_rwsem_write+0x3d/0x70 > [ 94.908495] #6: (cpufreq_driver_lock){......}, at: [] __cpufreq_remove_dev.isra.10+0x26/0x270 > [ 94.908500] Pid: 4038, comm: systemd-sleep Not tainted 3.8.0-rc6-next-20130205+ #200 > [ 94.908501] Call Trace: > [ 94.908511] [] __might_sleep+0xe0/0x100 > [ 94.908518] [] flush_work+0x5f/0x230 > [ 94.908523] [] ? insert_work+0x50/0x50 > [ 94.908528] [] ? del_timer+0x47/0x70 > [ 94.908533] [] ? del_timer+0x47/0x70 > [ 94.908538] [] ? try_to_grab_pending+0xa8/0x120 > [ 94.908543] [] __cancel_work_timer+0x59/0x80 > [ 94.908548] [] cancel_delayed_work_sync+0x12/0x20 > [ 94.908555] [] cpufreq_governor_dbs+0x2cd/0x490 > [ 94.908561] [] od_cpufreq_governor_dbs+0x16/0x20 > [ 94.908565] [] __cpufreq_governor+0x41/0x100 > [ 94.908570] [] ? __cpufreq_remove_dev.isra.10+0x26/0x270 > [ 94.908575] [] __cpufreq_remove_dev.isra.10+0x56/0x270 > [ 94.908580] [] ? lock_policy_rwsem_write+0x3d/0x70 > [ 94.908589] [] cpufreq_cpu_callback+0x50/0x65 > [ 94.908596] [] notifier_call_chain+0x47/0x90 > [ 94.908606] [] __raw_notifier_call_chain+0x1e/0x30 > [ 94.908610] [] __cpu_notify+0x24/0x50 > [ 94.908615] [] _cpu_down+0x6d/0x250 > [ 94.908621] [] disable_nonboot_cpus+0x6c/0xf0 > [ 94.908625] [] suspend_devices_and_enter+0x175/0x2b0 > [ 94.908629] [] pm_suspend+0x1d7/0x1e0 > [ 94.908633] [] state_store+0x5d/0xb0 > [ 94.908638] [] ? pm_trace_dev_match_show+0x20/0x20 > [ 94.908644] [] kobj_attr_store+0x1b/0x30 > [ 94.908650] [] sysfs_write_file+0xa3/0x100 > [ 94.908655] [] ? sysfs_open_file+0x1f0/0x1f0 > [ 94.908662] [] vfs_write+0x88/0x140 > [ 94.908667] [] ? sysfs_open_file+0x1f0/0x1f0 > [ 94.908672] [] sys_write+0x47/0x90 > [ 94.908679] [] sysenter_do_call+0x12/0x2d > [ 94.911067] smpboot: CPU 1 is now offline > [ 94.915585] smpboot: CPU 2 is now offline > [ 94.917500] smpboot: CPU 3 is now offline > > > -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center.