[<prev] [next>] [day] [month] [year] [list]
Message-ID: <1419313020.26403.54.camel@intel.com>
Date: Tue, 23 Dec 2014 13:37:00 +0800
From: Huang Ying <ying.huang@...el.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Michal Hocko <mhocko@...e.cz>, LKML <linux-kernel@...r.kernel.org>,
LKP ML <lkp@...org>
Subject: [LKP] [sched] WARNING: CPU: 0 PID: 232 at kernel/sched/core.c:7193
__might_sleep+0x6f/0xa9()
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git since-3.18
commit 407bf4d3b56d3d36920a401cd88691f3f6c093cc ("sched: Debug nested sleeps")
I think this is expected behavior, some migh_sleep warning show in dmesg.
+------------------------------------------------------------------+------------+------------+
| | 6866a948ce | 407bf4d3b5 |
+------------------------------------------------------------------+------------+------------+
| boot_successes | 9 | 0 |
| boot_failures | 9 | 30 |
| Out_of_memory:Kill_process | 9 | |
| backtrace:do_mount | 2 | |
| backtrace:compat_SyS_mount | 2 | |
| Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes | 2 | |
| backtrace:vfs_read | 2 | |
| backtrace:SyS_read | 2 | |
| backtrace:do_sys_open | 1 | |
| backtrace:compat_SyS_open | 1 | |
| backtrace:do_fork | 4 | |
| backtrace:SyS_clone | 4 | |
| WARNING:at_drivers/block/floppy.c:#schedule_bh() | 1 | |
| backtrace:do_execve_common | 3 | |
| backtrace:compat_SyS_execve | 3 | |
| WARNING:at_kernel/sched/core.c:#__might_sleep() | 0 | 30 |
| backtrace:rfcomm_run | 0 | 29 |
+------------------------------------------------------------------+------------+------------+
[ 32.821749] Bluetooth: RFCOMM TTY layer initialized
[ 32.823450] Bluetooth: RFCOMM socket layer initialized
[ 32.825557] ------------[ cut here ]------------
[ 32.826714] WARNING: CPU: 0 PID: 232 at kernel/sched/core.c:7193 __might_sleep+0x6f/0xa9()
[ 32.829296] do not call blocking ops when !TASK_RUNNING; state=1 set at [<ffffffff82bebfe5>] rfcomm_run+0x122/0x1005
[ 32.831873] Modules linked in:
[ 32.832928] CPU: 0 PID: 232 Comm: krfcommd Not tainted 3.18.0 #1922
[ 32.834668] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 32.835998] 0000000000000009 ffff88000b26bc58 ffffffff82d5df90 00000000001cf5b0
[ 32.838613] ffff88000b26bca8 ffff88000b26bc98 ffffffff810c7209 ffffea00002702b8
[ 32.840983] ffffffff810e65d1 ffffffff8386bf13 000000000000026d 0000000000000000
[ 32.843919] Call Trace:
[ 32.844787] [<ffffffff82d5df90>] dump_stack+0x4e/0x68
[ 32.846210] [<ffffffff810c7209>] warn_slowpath_common+0xa2/0xbc
[ 32.847591] [<ffffffff810e65d1>] ? __might_sleep+0x6f/0xa9
[ 32.849319] [<ffffffff810c7269>] warn_slowpath_fmt+0x46/0x48
[ 32.850673] [<ffffffff82beb264>] ? rfcomm_session_add+0x2b/0xdd
[ 32.852680] [<ffffffff82bebfe5>] ? rfcomm_run+0x122/0x1005
[ 32.854011] [<ffffffff82bebfe5>] ? rfcomm_run+0x122/0x1005
[ 32.855356] [<ffffffff810e65d1>] __might_sleep+0x6f/0xa9
[ 32.856845] [<ffffffff82bebec3>] ? rfcomm_check_accept+0x8b/0x8b
[ 32.858291] [<ffffffff82d7f713>] mutex_lock_nested+0x2f/0x3e4
[ 32.859663] [<ffffffff8111e4b7>] ? init_timer_key+0x97/0xd2
[ 32.861321] [<ffffffff82bebec3>] ? rfcomm_check_accept+0x8b/0x8b
[ 32.862735] [<ffffffff82bec02a>] rfcomm_run+0x167/0x1005
[ 32.864414] [<ffffffff82d7db35>] ? __schedule+0x3f5/0x5e4
[ 32.865881] [<ffffffff82bebec3>] ? rfcomm_check_accept+0x8b/0x8b
[ 32.867790] [<ffffffff810e030e>] kthread+0xe0/0xe8
[ 32.869022] [<ffffffff82d81f3e>] ? _raw_spin_unlock_irq+0x2d/0x3e
[ 32.870951] [<ffffffff810e022e>] ? __kthread_parkme+0xad/0xad
[ 32.872632] [<ffffffff82d8297c>] ret_from_fork+0x7c/0xb0
[ 32.873934] [<ffffffff810e022e>] ? __kthread_parkme+0xad/0xad
[ 32.875531] ---[ end trace a2de474b76db3d65 ]---
[ 32.876812] Bluetooth: RFCOMM ver 1.11
Thanks,
Fengguang
View attachment "config-3.18.0-00114-g407bf4d" of type "text/plain" (139420 bytes)
View attachment ".dmesg" of type "text/plain" (45851 bytes)
_______________________________________________
LKP mailing list
LKP@...ux.intel.com
Powered by blists - more mailing lists