All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	Chan-yeol Park <chanyeol.park@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Johan Hedberg <johan.hedberg@intel.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2014-11-07
Date: Tue, 18 Nov 2014 15:34:59 +0200	[thread overview]
Message-ID: <20141118133459.GB27428@node.dhcp.inet.fi> (raw)
In-Reply-To: <20141107092754.GA6995@t440s.lan>

On Fri, Nov 07, 2014 at 11:27:54AM +0200, Johan Hedberg wrote:
> Chan-yeol Park (1):
>       Bluetooth: Fix hci_sync missing wakeup interrupt

Look like this commit causes problem for me:

[    2.018671] ------------[ cut here ]------------
[    2.022836] WARNING: CPU: 2 PID: 109 at /home/kas/git/public/linux/kernel/sched/core.c:7323 __might_sleep+0xbd/0xd0()
[    2.023166] Freeing unused kernel memory: 944K (ffff880001b14000 - ffff880001c00000)
[    2.030362] do not call blocking ops when !TASK_RUNNING; state=1 set at [<ffffffff819ab67b>] __hci_req_sync+0x7b/0x2a0
[    2.034193] Modules linked in:
[    2.036133] CPU: 2 PID: 109 Comm: kworker/u17:0 Not tainted 3.18.0-rc4-next-20141117-07404-g9dad2ab6df8b #66
[    2.036383] Freeing unused kernel memory: 1404K (ffff8800020a1000 - ffff880002200000)
[    2.038940] Hardware name: LENOVO 3460CC6/3460CC6, BIOS G6ET93WW (2.53 ) 02/04/2013
[    2.040233] Workqueue: hci0 hci_power_on
[    2.041517]  ffffffff81f51d50 ffff8800d3ecfb28 ffffffff81afc316 0000000000000000
[    2.042811]  ffff8800d3ecfb78 ffff8800d3ecfb68 ffffffff810fc11a ffff880000000000
[    2.042812]  ffffffff81f52a28 000000000000026d 0000000000000000 ffff8800d3ec9200
[    2.042813] Call Trace:
[    2.042818]  [<ffffffff81afc316>] dump_stack+0x4c/0x6e
[    2.042821]  [<ffffffff810fc11a>] warn_slowpath_common+0x8a/0xc0
[    2.042823]  [<ffffffff810fc196>] warn_slowpath_fmt+0x46/0x50
[    2.042825]  [<ffffffff819ab67b>] ? __hci_req_sync+0x7b/0x2a0
[    2.042827]  [<ffffffff819ab67b>] ? __hci_req_sync+0x7b/0x2a0
[    2.042830]  [<ffffffff811295ed>] __might_sleep+0xbd/0xd0
[    2.042832]  [<ffffffff81b04b8f>] mutex_lock_nested+0x2f/0x450
[    2.042835]  [<ffffffff81b0812b>] ? _raw_spin_unlock+0x2b/0x50
[    2.042837]  [<ffffffff81131db0>] ? wake_up_process+0x50/0x50
[    2.042840]  [<ffffffff813b9ea1>] __create_file+0x71/0x2c0
[    2.042842]  [<ffffffff813ba10f>] debugfs_create_file+0x1f/0x30
[    2.042844]  [<ffffffff819ac461>] hci_dev_do_open+0x431/0xa70
[    2.042846]  [<ffffffff8111a72c>] ? process_one_work+0x13c/0x810
[    2.042847]  [<ffffffff819ad2b1>] hci_power_on+0x31/0x1e0
[    2.042849]  [<ffffffff8111a7c8>] process_one_work+0x1d8/0x810
[    2.042850]  [<ffffffff8111a72c>] ? process_one_work+0x13c/0x810
[    2.042851]  [<ffffffff8111b2db>] worker_thread+0x6b/0x4b0
[    2.042852]  [<ffffffff8111b270>] ? init_pwq+0xf0/0xf0
[    2.042854]  [<ffffffff81120ef9>] kthread+0x119/0x130
[    2.042855]  [<ffffffff8112923d>] ? finish_task_switch+0x4d/0x140
[    2.042857]  [<ffffffff81120de0>] ? kthread_create_on_node+0x240/0x240
[    2.042859]  [<ffffffff81b08cfc>] ret_from_fork+0x7c/0xb0
[    2.042861]  [<ffffffff81120de0>] ? kthread_create_on_node+0x240/0x240
[    2.042863] ---[ end trace 3a40e80ec4ca7159 ]---

-- 
 Kirill A. Shutemov

  parent reply	other threads:[~2014-11-18 13:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07  9:27 pull request: bluetooth-next 2014-11-07 Johan Hedberg
2014-11-11 21:35 ` John W. Linville
2014-11-18 13:34 ` Kirill A. Shutemov [this message]
2014-11-18 18:09   ` Johan Hedberg
2014-11-19  8:18     ` Chan-yeol Park
2014-11-19  8:20     ` Chan-yeol Park
2014-11-19 11:06     ` Kirill A. Shutemov
2014-11-19 11:17       ` Johan Hedberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141118133459.GB27428@node.dhcp.inet.fi \
    --to=kirill@shutemov.name \
    --cc=chanyeol.park@samsung.com \
    --cc=johan.hedberg@intel.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.