From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: bluetooth in v4.13-rc1: lock init missing somewhere?
Date: Fri, 21 Jul 2017 10:55:51 +0200 [thread overview]
Message-ID: <20170721085551.GA22993@amd> (raw)
Hi!
Is bluetooth expected to work on n900?
It looks like lock init is missing somewhere:
[ 402.901031] of_get_named_gpiod_flags: parsed
'bluetooth-wakeup-gpios' property of node
'/ocp at 68000000/serial at 4806c000/bluetooth[0]' - status (0)
[ 403.042022] BUG: rwlock bad magic on CPU#0, kworker/u3:0/3898,
c34b8848
[ 403.042053] CPU: 0 PID: 3898 Comm: kworker/u3:0 Tainted: G W
4.13.0-rc1-12941-g013595c-dirty #92
[ 403.042083] Hardware name: Nokia RX-51 board
[ 403.042114] Workqueue: hci0 hci_power_on
[ 403.042205] [<c010d5dc>] (unwind_backtrace) from [<c010ae18>]
(show_stack+0x10/0x14)
[ 403.042327] [<c010ae18>] (show_stack) from [<c0154d74>]
(do_raw_read_lock+0x20/0x2c)
[ 403.042358] [<c0154d74>] (do_raw_read_lock) from [<c04ea070>]
(hci_uart_tx_wakeup+0x14/0x84)
[ 403.042419] [<c04ea070>] (hci_uart_tx_wakeup) from [<bf00089c>]
(nokia_setup+0x210/0x640 [hci_nokia])
[ 403.042449] [<bf00089c>] (nokia_setup [hci_nokia]) from
[<c04ea6fc>] (hci_uart_setup+0x7c/0x15c)
[ 403.042480] [<c04ea6fc>] (hci_uart_setup) from [<c063c1a0>]
(hci_dev_do_open+0x420/0x5a0)
[ 403.042510] [<c063c1a0>] (hci_dev_do_open) from [<c063db40>]
(hci_power_on+0x30/0x228)
[ 403.042541] [<c063db40>] (hci_power_on) from [<c013ad5c>]
(process_one_work+0x10c/0x330)
[ 403.042572] [<c013ad5c>] (process_one_work) from [<c013b120>]
(worker_thread+0x168/0x498)
[ 403.042602] [<c013b120>] (worker_thread) from [<c014035c>]
(kthread+0x10c/0x148)
[ 403.042633] [<c014035c>] (kthread) from [<c01076b8>]
(ret_from_fork+0x14/0x3c)
root at n900:/my/modules#
If I put the driver built-in, firmware loading failed. But I can't get
it to "hciconfig up" phase even with driver being modular. .. that
worked at one point IIRC.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170721/a6e56968/attachment.sig>
next reply other threads:[~2017-07-21 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 8:55 Pavel Machek [this message]
2017-07-21 9:57 ` bluetooth in v4.13-rc1: lock init missing somewhere? Marcel Holtmann
2017-07-21 11:10 ` Pavel Machek
2017-07-21 11:25 ` Marcel Holtmann
2017-07-23 8:26 ` Pavel Machek
2017-07-23 18:44 ` Marcel Holtmann
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=20170721085551.GA22993@amd \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).