Linux: Bluetooth and Dual Shock 3 Playstation Remote will crash System.

If you can post the whole of the crash dump - down to the "---[ end trace ..." if possible - then it might just help to debug this.

Hey @pelwell ,

Working on getting this now. First time I've created a crash dump so I might be a bit, working on acquiring the prerequisite knowledge.

I was thinking that you could just include more of the output in /var/log/syslog. I've never tried to get a crash dump for a kernel crash, and I'm not sure it would work.

That's sort of my thinking as well. It seems that IO simply stops when this occurs. Not sure if I can pipe it out the serial when this happens or not, but I'm looking into that.

In the meantime I'll get more information from /var/log/syslog and post it here as soon as I get home.

Alternatively, if you can provoke it with the text console visible (Ctrl-Alt-F1, Ctrl-Alt-F7 to get back to the desktop) then adding framebuffer_height=2160 to config.txt may allow you get the whole backtrace onto the screen where you can photograph it.

Generally it happens with emulators open and me actively using the game pad, but I'm going to try that and mash on the buttons furiously while copying some files in the background and see what happens.

I'm having trouble reproducing this error and being able to capture the trace. I can only seem to get it to happen when emulation station is actively doing something, witch stops me from looking at the text console.

Having the same issue here, also unable to get any trace other than the one previously mentioned.

The system only seems to freeze when displaying something heavier than a TTY on screen, I've had these freezes occur while watching video on kodi, playing some games with emulationstation or working with something on a xfce session but never when looking at a TTY, even if something heavy is running in the background.

I did once get only a partial bluetooth fail while attempting to trigger the freeze:

Mar 30 01:53:08 PIPPLWARE dbus[429]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Mar 30 01:53:08 PIPPLWARE systemd[4992]: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: Permission denied
Mar 30 01:53:08 PIPPLWARE systemd[1]: bluetooth.service: main process exited, code=exited, status=203/EXEC
Mar 30 01:53:08 PIPPLWARE systemd[1]: Failed to start Bluetooth service.
Mar 30 01:53:08 PIPPLWARE systemd[1]: Unit bluetooth.service entered failed state.
Mar 30 01:53:33 PIPPLWARE dbus[429]: [system] Failed to activate service 'org.bluez': timed out

Another thing of note is that the bluetooth service often fails to start once before actually starting during system startup.

I'm pretty sure i have the exact same problem, but mine is triggered from a nodejs-program, therefore i'm in the console when it happens, and thus i have logs. I hope they help:

[ 1299.902456] Bluetooth: hci0 unexpected SMP command 0x02 from c8:0f:10:28:ab:51
[ 1300.037106] Bluetooth: hci0 unexpected SMP command 0x03 from c8:0f:10:28:ab:51
[ 1300.292100] Bluetooth: hci0 unexpected SMP command 0x04 from c8:0f:10:28:ab:51
[ 1300.697121] Bluetooth: hci0 unexpected SMP command 0x06 from c8:0f:10:28:ab:51
[ 1300.925752] Bluetooth: hci0: Frame reassembly faild (-84)
[ 1300.931428] Bluetooth: hci0 unexpected SMP command 0x07 from c8:0f:10:28:ab:51
[ 1301.111148] Unable to handle kernel paging request at virtual address ffffffc8
[ 1301.118563] pgd = 80004000
[ 1301.121372] [ffffffc8] *pgd=3dffa821, *pte=00000000, *ppte=00000000
[ 1301.127833] Internal error: Oops: 17 [#1] SMP ARM

Entering kdb (current=0xbbcb6d40, pid 367) on processor 0 Oops: (null)
due to oops @ 0x07f3c8c20
CPU: 0 PID: 367 Comm: kworker/0:3 Not tainted 4.1.20-v7+ #867
Hardware name: BCM2709
Workqueue: events flush_to_ldisc
task: bbcb6d40 ti: b9db4000 task.ti: b9db4000
PC is at h4_recv_buf+0x34/0x22c [hci_uart]
LR is at h4_recv+0x50/0x98 [hci_uart]
pc : [<7f3c8c20>]    lr : [<7f3c8e68>]    psr: a0000013
sp : b9db5e38  ip : b9db5e68  fp : b9db5e64
r10: 00000008  r9 : 00000008  r8 : bb22d000
r7 : 7f3ca194  r6 : bb067c6c  r5 : 00000003  r4 : ffffffac
r3 : 00000008  r2 : bb067c6c  r1 : ffffffac  r0 : bb22d000
Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
Control: 10c5383d  Table: 3bf4406a  DAC: 00000015
CPU: 0 PID: 367 Comm: kworker/0:3 Not tainted 4.1.20-v7+ #867
Hardware name: BCM2709
Workqueue: events flush_to_ldisc
[<800185e0>] (unwind_backtrace) from [<80013f48>] (show_stack+0x20/0x24)
[<80013f48>] (show_stack) from [<80572ddc>] (dump_stack+0xd4/0x118)
[<80572ddc>] (dump_stack) from [<80010d18>] (show_regs+0x1c/0x20)
[<80010d18>] (show_regs) from [<800b4a70>] (kdb_main_loop+0x3ec/0x800)

There it just stops. but i have a longer log from a previous crash that seems to have the same cause:

[  156.026986] Bluetooth: hci0: Frame reassembly faild (-84)
[  156.060272] Bluetooth: hci0 unexpected SMP command 0x07 from c8:0f:10:28:af:c1
Entering kdb (current=0xbc77cac0, pid 96) on processor 0 Oops: (null)
due to oops @ 0x07f3c8c20
CPU: 0 PID: 96 Comm: kworker/0:2 Not tainted 4.1.20-v7+ #867
Hardware name: BCM2709
Workqueue: events flush_to_ldisc
task: bc77cac0 ti: bbf7c000 task.ti: bbf7c000
PC is at h4_recv_buf+0x34/0x22c [hci_uart]
LR is at h4_recv+0x50/0x98 [hci_uart]
pc : [<7f3c2c20>]    lr : [<7f3c2e68>]    psr: a0000013
sp : bbf7de38  ip : bbf7de68  fp : bbf7de64
r10: 0000000a  r9 : 0000000a  r8 : b9de0000
r7 : 7f3c4191  r6 : bb1eb8db  r5 : 00000003  r4 : ffffffac
r3 : 0000000a  r2 : bb1eb8db  r1 : ffffffac  r0 : b9de0000
Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
Control: 10c5383d  Table: 39c3806a  DAC: 00000015
CPU: 0 PID: 96 Comm: kworker/0:2 Not tainted 4.1.20-v7+ #867
Hardware name: BCM2709
Workqueue: events flush_to_ldisc
[<800185e0>] (unwind_backtrace) from [<80013f48>] (show_stack+0x20/0x24)
[<80013f48>] (show_stack) from [<80572ddc>] (dump_stack+0xd4/0x118)
[<80572ddc>] (dump_stack) from [<80010d18>] (show_regs+0x1c/0x20)
[<80010d18>] (show_regs) from [<800b4a70>] (kdb_main_loop+0x3ec/0x800)
more> [<800b4a70>] (kdb_main_loop) from [<800b796c>] (kdb_stub+0x2c4/0x510)
[<800b796c>] (kdb_stub) from [<800ad360>] (kgdb_cpu_enter+0x480/0x838)
[<800ad360>] (kgdb_cpu_enter) from [<800ad974>] (kgdb_handle_exception+0x104/0x218)
[<800ad974>] (kgdb_handle_exception) from [<80017aec>] (kgdb_notify+0x40/0x90)
[<80017aec>] (kgdb_notify) from [<80044cd4>] (notifier_call_chain+0x54/0x94)
[<80044cd4>] (notifier_call_chain) from [<80044eec>] (notify_die+0x48/0x54)
[<80044eec>] (notify_die) from [<80014064>] (die+0x118/0x43c)
[<80014064>] (die) from [<80571c48>] (__do_kernel_fault.part.0+0x74/0x8
[<80571c48>] (__do_kernel_fault.part.0) from [<80578bd4>] (do_page_fault+0x28c/0x398)
[<80578bd4>] (do_page_fault) from [<800091e8>] (do_DataAbort+0x48/0xc4)
[<800091e8>] (do_DataAbort) from [<8057811c>] (__dabt_svc+0x3c/0x60)
Exception stack(0xbbf7ddf0 to 0xbbf7de38)
dde0:                                     b9de0000 ffffffac bb1eb8db 0000000a
de00: ffffffac 00000003 bb1eb8db 7f3c4194 b9de0000 0000000a 0000000a bbf7de64
de20: bbf7de68 bbf7de38 7f3c2e68 7f3c2c20 a0000013 ffffffff
[<8057811c>] (__dabt_svc) from [<7f3c2c20>] (h4_recv_buf+0x34/0x22c [hci_uart])
[<7f3c2c20>] (h4_recv_buf [hci_uart]) from [<7f3c2e68>] (h4_recv+0x50/0x98 [hci_uart])
[<7f3c2e68>] (h4_recv [hci_uart]) from [<7f3c20f0>] (hci_uart_tty_receive+0x74/0xb0 [hci_uart])
[<7f3c20f0>] (hci_uart_tty_receive [hci_uart]) from [<80358b48>] (flush_to_ldisc+0x190/0x1a0)
more> [<80358b48>] (flush_to_ldisc) from [<8003e0b8>] (process_one_work+0x154/0x458)
[<8003e0b8>] (process_one_work) from [<8003e410>] (worker_thread+0x54/0x500)
[<8003e410>] (worker_thread) from [<80043bec>] (kthread+0xec/0x104)
[<80043bec>] (kthread) from [<8000faf8>] (ret_from_fork+0x14/0x3c)

[0]kdb> _

I was careful, but the logs may contain errors, because i had to transcribe them by hand
EDIT: fixed some transcription-errors

I am having a similar problem with bluetooth and a Nexus6P device connecting. After pairing the Nexus 6P with blueman and other bluetooth tools, the raspberry pi immediately freezes. Leaving it for ten minutes results in no response, however, I have no logs.

I'm having a similar issue with a Logitech bluetooth mouse. If there is an intensive process going on, moving the mouse would often freeze the entire OS.

I'm new to Linux world. What are the steps I can do to provide debug info here?

Is there an instability issue with Bluetooth hardware on rpi3? Or is this a bug in software?

Bluetooth throughput is limited on Pi3 because of a lack of flow control signals to BT modem. The Bluetooth H5 protocol is supposed to handle packet loss, but the current BT modem firmware does not work with the BlueZ stack in H5 mode.

Is this issue perhaps related to this? https://github.com/raspberrypi/firmware/issues/553

How can we make this issue actionable?

It's open and on this bug list, so will be looked at when time allows. Depends on the impact of the issues and the number of people it affects.

Depends on the impact of the issues

For the record, all my bluetooth devices trigger this crash.

Also, as I was googling, I've seen several people reporting "system freeze" with the PS3 bluetooth controller (example http://blog.petrockblock.com/forums/topic/problems-getting-ps3-controller-to-work-properly/#post-119899 and https://www.reddit.com/r/RetroPie/comments/4aoojj/pi3_crashing_with_kernel_474079425_internal_error/)

If there's anything I can do to get a better log, or try a patch, I'd be happy to help.

I just wanted to add that I am having the same issue. I have a Pi3 with a fresh RP3.6 and just started using PS3 DS3 controllers through BT yesterday and almost instantly started seeing the freezes. If I change out the PS3 controller and use a wired 360, I have no issues at all.

(no crash with a bluetooth dongle)

We'll get in a DS3 and have a go. Can you say what extra configuration is required beyond pairing and trusing, and perhaps recommend a test application if necessary?

I can see three potential outcomes:
1) If this crash turns out to be due to a bug/incompatibility in the Linux Bluetooth stack then we have a chance of fixing it.
2) If it is a bug/incompatibility in the Broadcom firmware then it becomes much harder to get a fix.
3) If it is due to data loss going through the UART then it may be improved by H5 support, which is somewhere between 1 and 2 in tractability.

All I did was install the required files for the PS3 controllers through the RP-setup and sync.

I also had it freeze pretty much everywhere in ES. Most of the times I could get it to happen while in a game and bringing up the RAGUI and while sitting in there, it would happen.

I have a spare BT dongle that I will try out tonight as I would like to use the DS3 controllers.

Also having this issue with onboard Bluetooth and clone dualshock 3 controller (Shanwan) connected via sixad.

It happen sporadically and under different emulators / roms. When it hangs, system can't be interrupted via keyboard, SSH sessions break and pi stips responding to pings

We'll get in a DS3 and have a go. Can you say what extra configuration is required beyond pairing and trusing, and perhaps recommend a test application if necessary?

Linux retropie 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux
No special configuration. I run PSP games. After a minute or so of playing, freeze.

@paulrouget How did you disable the on board BT so you could use you own?

dtoverlay=pi3-disable-bt?

@paulrouget How did you disable the on board BT so you could use you own?

I was reporting what I've found in other forums:

I plugged in a CSR 4.0 bluetooth USB button and am using bluetooth without a hitch - so it seems the issue is with the onboard bluetooth.

I can confirm that I put dtoverlay=pi3-disable-bt in my config.txt and used a USB BT dongle, I played for hours last night without any issues. I soon as I reverted back and tried, I got a freeze with 5 mins.

I'm also seeing this issue with the onboard BT:
[Apr13 16:55] Bluetooth: hci0: Frame reassembly failed (-84)
[ +0.000152] Unable to handle kernel paging request at virtual address ffffffc8
[ +0.007510] pgd = 80004000
[ +0.002857] [ffffffc8] *pgd=2effa821, *pte=00000000, *ppte=00000000
[ +0.006553] Internal error: Oops: 17 [#1] SMP ARM

Hopefully the PS3 driver gets fixed sooner than later, as I don't have a BT dongle to use :/

I can confirm that using a bluetooth dongle solves it for me. On-board bluetooth means a freeze within a few minutes, dongle has allowed me to play for hours with no problems. I didn't have to change any text file to disable the pi3 bluetooth, just plugging in a dongle alone seemed to work.

I don't know if more crash dumps will help, but here they are:

[  380.219390] Unable to handle kernel paging request at virtual address ffffffc8
[  380.228822] pgd = 80004000
[  380.233051] [ffffffc8] *pgd=2effa821, *pte=00000000, *ppte=00000000
[  380.241212] Internal error: Oops: 17 [#1] SMP ARM
[  380.247696] Modules linked in: hidp bnep hci_uart btbcm bluetooth brcmfmac snd_usb_audio brcmutil cfg80211 snd_usbmidi_lib snd_hwdep snd_rawmidi snd_seq_device rfkill evdev bcm2835_gpiomem bcm2835_rng uio_pdrv_genirq uio snd_bcm2835 snd_pcm snd_timer snd joydev uinput fuse ipv6
[  380.277738] CPU: 0 PID: 4 Comm: kworker/0:0 Not tainted 4.1.19-v7+ #858
[  380.287198] Hardware name: BCM2709
[  380.293683] Workqueue: events flush_to_ldisc
[  380.300995] task: ad901140 ti: ad91c000 task.ti: ad91c000
[  380.309521] PC is at h4_recv_buf+0x34/0x22c [hci_uart]
[  380.317860] LR is at h4_recv+0x50/0x98 [hci_uart]
[  380.325840] pc : [<7f37fc20>]    lr : [<7f37fe68>]    psr: a0000013
[  380.325840] sp : ad91de38  ip : ad91de68  fp : ad91de64
[  380.344050] r10: 00000011  r9 : 00000011  r8 : ad315000
[  380.352813] r7 : 7f381194  r6 : ad0fbca5  r5 : 00000003  r4 : ffffffac
[  380.363117] r3 : 00000011  r2 : ad0fbca5  r1 : ffffffac  r0 : ad315000
[  380.373280] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
[  380.384694] Control: 10c5383d  Table: 2aeb006a  DAC: 00000015
[  380.394601] Process kworker/0:0 (pid: 4, stack limit = 0xad91c210)
[  380.404993] Stack: (0xad91de38 to 0xad91e000)
[  380.413849] de20:                                                       00000011 00000011
[  380.426617] de40: a9c55400 aae0bac0 aae0bd80 ad0a9004 ad0a9000 00000011 ad91de8c ad91de68
[  380.439493] de60: 7f37fe68 7f37fbf8 7f381194 00000003 a9c55400 ad381000 aae0bac0 ad0fbc00
[  380.452647] de80: ad91deac ad91de90 7f37f0f0 7f37fe24 00000011 00000011 ad381000 ad0a9014
[  380.466025] dea0: ad91dee4 ad91deb0 80358e48 7f37f088 ad91df0c ad91dec0 80573e14 ad896380
[  380.479569] dec0: ad0a9004 aefb4080 aefb7f00 00000000 ad896380 00000000 ad91df24 ad91dee8
[  380.492998] dee0: 8003e0b8 80358cc4 aefb4080 aefb4094 ad91c000 00000008 ad896380 aefb4080
[  380.506584] df00: ad896398 aefb4094 ad91c000 00000008 ad896380 aefb4080 ad91df5c ad91df28
[  380.520465] df20: 8003e410 8003df70 aefb4214 80822900 00000000 00000000 ad894c00 ad896380
[  380.534561] df40: 8003e3bc 00000000 00000000 00000000 ad91dfac ad91df60 80043bec 8003e3c8
[  380.548828] df60: ad91df94 00000000 8004a880 ad896380 00000000 00000000 ad91df78 ad91df78
[  380.562945] df80: 00000000 00000000 ad91df88 ad91df88 ad894c00 80043b00 00000000 00000000
[  380.576929] dfa0: 00000000 ad91dfb0 8000faf8 80043b0c 00000000 00000000 00000000 00000000
[  380.590854] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[  380.605278] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 55555555 55555555
[  380.619668] [<7f37fc20>] (h4_recv_buf [hci_uart]) from [<7f37fe68>] (h4_recv+0x50/0x98 [hci_uart])
[  380.634601] [<7f37fe68>] (h4_recv [hci_uart]) from [<7f37f0f0>] (hci_uart_tty_receive+0x74/0xb0 [hci_uart])
[  380.650364] [<7f37f0f0>] (hci_uart_tty_receive [hci_uart]) from [<80358e48>] (flush_to_ldisc+0x190/0x1a0)
[  380.666024] [<80358e48>] (flush_to_ldisc) from [<8003e0b8>] (process_one_work+0x154/0x458)
[  380.680568] [<8003e0b8>] (process_one_work) from [<8003e410>] (worker_thread+0x54/0x500)
[  380.695006] [<8003e410>] (worker_thread) from [<80043bec>] (kthread+0xec/0x104)
[  380.708777] [<80043bec>] (kthread) from [<8000faf8>] (ret_from_fork+0x14/0x3c)
[  380.722754] Code: e59b7004 e59b5008 0a00002d e3540000 (11d431bc) 
[  380.735827] ---[ end trace 831fb3fed9cab54d ]---
[  380.747637] Unable to handle kernel paging request at virtual address ffffffec
[  380.747640] pgd = 80004000
[  380.747652] [ffffffec] *pgd=2effa821, *pte=00000000, *ppte=00000000
[  380.747660] Internal error: Oops: 17 [#2] SMP ARM
[  380.747704] Modules linked in: hidp bnep hci_uart btbcm bluetooth brcmfmac snd_usb_audio brcmutil cfg80211 snd_usbmidi_lib snd_hwdep snd_rawmidi snd_seq_device rfkill evdev bcm2835_gpiomem bcm2835_rng uio_pdrv_genirq uio snd_bcm2835 snd_pcm snd_timer snd joydev uinput fuse ipv6
[  380.747714] CPU: 0 PID: 4 Comm: kworker/0:0 Tainted: G      D         4.1.19-v7+ #858
[  380.747716] Hardware name: BCM2709
[  380.747729] task: ad901140 ti: ad91c000 task.ti: ad91c000
[  380.747746] PC is at kthread_data+0x18/0x20
[  380.747758] LR is at wq_worker_sleeping+0x1c/0xe0
[  380.747764] pc : [<8004432c>]    lr : [<8003f284>]    psr: 00000193
[  380.747764] sp : ad91db78  ip : ad91db88  fp : ad91db84
[  380.747767] r10: 2e7b1000  r9 : ad90142c  r8 : 808240a4
[  380.747770] r7 : 80803580  r6 : 80803580  r5 : ad901140  r4 : 00000000
[  380.747773] r3 : 00000000  r2 : 00000000  r1 : 00000000  r0 : ad901140
[  380.747781] Flags: nzcv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment user
[  380.747784] Control: 10c5383d  Table: 2aeb006a  DAC: 00000015
[  380.747787] Process kworker/0:0 (pid: 4, stack limit = 0xad91c210)
[  380.747791] Stack: (0xad91db78 to 0xad91e000)
[  380.747796] db60:                                                       ad91db9c ad91db88
[  380.747801] db80: 8003f284 80044320 aefb4580 ad901140 ad91dbec ad91dba0 80574048 8003f274
[  380.747808] dba0: 800781ac 80077e7c ad91dc04 ad91dbb8 80028030 80078194 00000000 807ff240
[  380.747813] dbc0: ad910964 ad91c000 ad91d98c ad91dc10 ad9013a8 00000001 00000001 ad900000
[  380.747819] dbe0: ad91dc04 ad91dbf0 80574324 80573c30 0420806c ad901140 ad91dc44 ad91dc08
[  380.747825] dc00: 80029c60 805742e4 ad91dc34 8082edd4 ad91dc10 ad91dc10 80827ad4 8088c2c4
[  380.747831] dc20: 60000113 80827ad4 0000000b 7f37fc24 00000001 7f37fc22 ad91dccc ad91dc48
[  380.747836] dc40: 800141a0 800294cc ad91c210 0000000b 00000000 80684768 00000008 00000000
[  380.747841] dc60: 00000000 80827ad4 6506dad0 37623935 20343030 62393565 38303035 30613020
[  380.747847] dc80: 32303030 33652064 30303435 28203030 34643131 63623133 80002029 805721ec
[  380.747852] dca0: 806c84c8 ffffffc8 00000017 ad91ddf0 00000000 ad901140 00000011 00000011
[  380.747860] dcc0: ad91dce4 ad91dcd0 80571f28 80013f58 ad91ddf0 ffffffc8 ad91dd3c ad91dce8
[  380.747865] dce0: 80578e94 80571ec0 00009319 00000000 ad91dd24 ad91dd00 80055910 80307a50
[  380.747871] dd00: 00000001 ad901188 aefb45c0 a9d5b9c8 a9d5b9c8 80828084 00000017 80578c08
[  380.747876] dd20: ffffffc8 ad91ddf0 00000011 00000011 ad91ddec ad91dd40 800091e8 80578c14
[  380.747882] dd40: 86d3ff2a 00000058 80055d80 a9d5b980 aefb45c0 a9d5b9c8 ad901188 808240a4
[  380.747887] dd60: aefb4580 80822dc8 ad91dde4 ad91dd78 8005b788 80058c98 00000000 00000000
[  380.747893] dd80: aefb45c0 808240a4 80803580 80044cd4 a5628018 a5628000 ad91ddcc 80803580
[  380.747900] dda0: 00000000 ad17d080 aefb4580 00000001 ad91dde4 ad91ddc0 8004a880 800d4d94
[  380.747905] ddc0: aefb4580 7f37fc20 a0000013 7f37fc20 a0000013 ffffffff ad91de24 ad315000
[  380.747912] dde0: ad91de64 ad91ddf0 805783dc 800091ac ad315000 ffffffac ad0fbca5 00000011
[  380.747919] de00: ffffffac 00000003 ad0fbca5 7f381194 ad315000 00000011 00000011 ad91de64
[  380.747924] de20: ad91de68 ad91de38 7f37fe68 7f37fc20 a0000013 ffffffff 00000011 00000011
[  380.747930] de40: a9c55400 aae0bac0 aae0bd80 ad0a9004 ad0a9000 00000011 ad91de8c ad91de68
[  380.747935] de60: 7f37fe68 7f37fbf8 7f381194 00000003 a9c55400 ad381000 aae0bac0 ad0fbc00
[  380.747941] de80: ad91deac ad91de90 7f37f0f0 7f37fe24 00000011 00000011 ad381000 ad0a9014
[  380.747947] dea0: ad91dee4 ad91deb0 80358e48 7f37f088 ad91df0c ad91dec0 80573e14 ad896380
[  380.747953] dec0: ad0a9004 aefb4080 aefb7f00 00000000 ad896380 00000000 ad91df24 ad91dee8
[  380.747959] dee0: 8003e0b8 80358cc4 aefb4080 aefb4094 ad91c000 00000008 ad896380 aefb4080
[  380.747964] df00: ad896398 aefb4094 ad91c000 00000008 ad896380 aefb4080 ad91df5c ad91df28
[  380.747972] df20: 8003e410 8003df70 aefb4214 80822900 00000000 00000000 ad894c00 ad896380
[  380.747979] df40: 8003e3bc 00000000 00000000 00000000 ad91dfac ad91df60 80043bec 8003e3c8
[  380.747985] df60: ad91df94 00000000 8004a880 ad896380 00000000 00000000 ad91df78 ad91df78
[  380.747991] df80: 00000001 00010001 ad91df88 ad91df88 ad894c00 80043b00 00000000 00000000
[  380.747996] dfa0: 00000000 ad91dfb0 8000faf8 80043b0c 00000000 00000000 00000000 00000000
[  380.748003] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[  380.748008] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 55555555 55555555
[  380.748025] [<8004432c>] (kthread_data) from [<8003f284>] (wq_worker_sleeping+0x1c/0xe0)
[  380.748040] [<8003f284>] (wq_worker_sleeping) from [<80574048>] (__schedule+0x424/0x6b4)
[  380.748049] [<80574048>] (__schedule) from [<80574324>] (schedule+0x4c/0xa4)
[  380.748058] [<80574324>] (schedule) from [<80029c60>] (do_exit+0x7a0/0xa38)
[  380.748072] [<80029c60>] (do_exit) from [<800141a0>] (die+0x254/0x43c)
[  380.748084] [<800141a0>] (die) from [<80571f28>] (__do_kernel_fault.part.0+0x74/0x84)
[  380.748095] [<80571f28>] (__do_kernel_fault.part.0) from [<80578e94>] (do_page_fault+0x28c/0x398)
[  380.748102] [<80578e94>] (do_page_fault) from [<800091e8>] (do_DataAbort+0x48/0xc4)
[  380.748109] [<800091e8>] (do_DataAbort) from [<805783dc>] (__dabt_svc+0x3c/0x60)
[  380.748112] Exception stack(0xad91ddf0 to 0xad91de38)
[  380.748116] dde0:                                     ad315000 ffffffac ad0fbca5 00000011
[  380.748121] de00: ffffffac 00000003 ad0fbca5 7f381194 ad315000 00000011 00000011 ad91de64
[  380.748126] de20: ad91de68 ad91de38 7f37fe68 7f37fc20 a0000013 ffffffff
[  380.748142] [<805783dc>] (__dabt_svc) from [<7f37fc20>] (h4_recv_buf+0x34/0x22c [hci_uart])
[  380.748154] [<7f37fc20>] (h4_recv_buf [hci_uart]) from [<7f37fe68>] (h4_recv+0x50/0x98 [hci_uart])
[  380.748164] [<7f37fe68>] (h4_recv [hci_uart]) from [<7f37f0f0>] (hci_uart_tty_receive+0x74/0xb0 [hci_uart])
[  380.748175] [<7f37f0f0>] (hci_uart_tty_receive [hci_uart]) from [<80358e48>] (flush_to_ldisc+0x190/0x1a0)
[  380.748187] [<80358e48>] (flush_to_ldisc) from [<8003e0b8>] (process_one_work+0x154/0x458)
[  380.748196] [<8003e0b8>] (process_one_work) from [<8003e410>] (worker_thread+0x54/0x500)
[  380.748203] [<8003e410>] (worker_thread) from [<80043bec>] (kthread+0xec/0x104)
[  380.748213] [<80043bec>] (kthread) from [<8000faf8>] (ret_from_fork+0x14/0x3c)
[  380.748219] Code: e24cb004 e52de004 e8bd4000 e59032c0 (e5130014) 
[  380.748225] ---[ end trace 831fb3fed9cab54e ]---
[  380.748227] Fixing recursive fault but reboot is needed!

Hopefully related, i've been able to trigger what appears to the be the same thing by playing music from an iPhone to the Pi 3 onboard BT via Bluetooth A2DP.

Sitting idle at an empty desktop it will play several songs no problem.
While still playing, within seconds of starting another task on the pi, it becomes unresponsive to input.

I just want to add that I see the same system freezes with a Sony PS4 Wireless DualShock 4 Controller.

On the other hand, connecting my simple Anker Bluetooth Keyboard A7726 doesn`t seem to trigger the bug.

Not that I think it would matter but I upgraded to Retropie 3.7 and still had the same issue.

@BaDvs3viL this will probably effect all distros until the kernel or firmware is upgraded.

Has anyone a tutorial to make a bluetooth dongle works on PI3? 1. Disable the internal bluetooth etc ..
Thanks

To disable onboard Pi3 Bluetooth
sudo nano /boot/config.txt (this opens the config file which you will need to modify with the command below)

Add to the end of the file
dtoverlay=pi3-disable-bt

Done. But the dongle does not work yet and it works perfect in pi2.
Some bluezman or another driver?
Thanks

Probably getting a bit off topic here, but likely need to install pi-bluetooth:

https://www.reddit.com/r/RetroPie/comments/4d5hcf/how_to_setup_8bitdo_nes30_fc30_pro_controllers_on/

It works! I added in rc.local "sixad --start &" and it worked!

Do you think the setting're ok?
Important information (is a clone GARSIA).
Thank you for your help!

@mauruco This is a bug report section, not an "how to" do something. If you don't know how to setup a BT dongle use the apropriate forums. You are spamming everyone interested in getting this bug fixed.

Can confirm my PI3 B locks up while using onboard BT under RetroPie 3.7 ( raspbian ) with BOTH authentic PS3 DS controllers as well as the Garsia PS3 DS clone controllers. Disabled onboard BT and all runs fine with a BT USB dongle ( Inateck BTA-BC4B6 ). Watching this issue with great interest. Whole reason I got a PI3 was for onboard BT for my controllers. GLA

I can officially report that the freeze only happens when playing N64 or PSX games. I sat there and played all other systems with no issue.

Only play with SNES & MAME here and locks up within 1 to 5 minutes every time.

I have the same issue with NES

On Saturday, April 23, 2016, cjbnorg [email protected] wrote:

Only play with SNES & MAME here and locks up within 1 to 5 minutes every
time.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-213762770

I am having the same issue with SNES and 8bitdo wireless controllers on a Pi3. Locks up within 5 to 8 minutes typically. I would be willing to pay a .5 BTC bug bounty on this one since it is affecting my niece and I's ability to game together on weekends. Thanks.

Same here. My 8bitdo controller is also causing my pi 3 to freeze. It's not just ps3 controllers.

Side note; I'm glad people are linking others to my how-to for the 8Bitdo controllers on reddit!

I'm seeing the same thing with my RPI3 and PS3 controller.

Another crash dump with RPI3, Retropie and PS3 connected via bluetooth.

[23131.768726] Unable to handle kernel paging request at virtual address ffffffc8
[23131.776103] pgd = 80004000
[23131.778886] [ffffffc8] *pgd=2effa821, *pte=00000000, *ppte=00000000
[23131.785363] Internal error: Oops: 17 [#1] SMP ARM
[23131.790128] Modules linked in: evdev hidp bnep hci_uart btbcm bluetooth brcmfmac brcmutil cfg80211 rfkill bcm2835_gpiomem bcm2835_rng uio_pdrv_genirq uio snd_bcm2835 snd_pcm snd_timer snd joydev uinput fuse ipv6
[23131.809224] CPU: 0 PID: 6716 Comm: kworker/0:0 Not tainted 4.1.19-v7+ #858
[23131.816189] Hardware name: BCM2709
[23131.819637] Workqueue: events flush_to_ldisc
[23131.823962] task: aa4cb3c0 ti: aa7f8000 task.ti: aa7f8000
[23131.829436] PC is at h4_recv_buf+0x34/0x22c [hci_uart]
[23131.834641] LR is at h4_recv+0x50/0x98 [hci_uart]
[23131.839405] pc : [<7f32bc20>]    lr : [<7f32be68>]    psr: a0000013
[23131.839405] sp : aa7f9e38  ip : aa7f9e68  fp : aa7f9e64
[23131.851041] r10: 00000008  r9 : 00000008  r8 : ad103000
[23131.856332] r7 : 7f32d194  r6 : aa420834  r5 : 00000003  r4 : ffffffac
[23131.862946] r3 : 00000008  r2 : aa420834  r1 : ffffffac  r0 : ad103000
[23131.869560] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
[23131.876966] Control: 10c5383d  Table: 2a7f406a  DAC: 00000015
[23131.882785] Process kworker/0:0 (pid: 6716, stack limit = 0xaa7f8210)
[23131.889312] Stack: (0xaa7f9e38 to 0xaa7fa000)
[23131.893722] 9e20:                                                       00000008 00000008
[23131.902012] 9e40: ac594580 ac7c4200 ac7c4840 ada8a004 ada8a000 00000008 aa7f9e8c aa7f9e68
[23131.910302] 9e60: 7f32be68 7f32bbf8 7f32d194 00000003 ac594580 ad3d4000 ac7c4200 aa420800
[23131.918591] 9e80: aa7f9eac aa7f9e90 7f32b0f0 7f32be24 00000008 00000008 ad3d4000 ada8a014
[23131.926880] 9ea0: aa7f9ee4 aa7f9eb0 80358e48 7f32b088 aa7f9f0c aa7f9ec0 80573e14 aa599680
[23131.935169] 9ec0: ada8a004 aefb4080 aefb7f00 00000000 aa599680 00000000 aa7f9f24 aa7f9ee8
[23131.943459] 9ee0: 8003e0b8 80358cc4 aefb4080 aefb4094 aa7f8000 00000008 aa599680 aefb4080
[23131.951749] 9f00: aa599698 aefb4094 aa7f8000 00000008 aa599680 aefb4080 aa7f9f5c aa7f9f28
[23131.960038] 9f20: 8003e410 8003df70 8003e3bc 80822900 00000000 00000000 ac63c5c0 aa599680
[23131.968328] 9f40: 8003e3bc 00000000 00000000 00000000 aa7f9fac aa7f9f60 80043bec 8003e3c8
[23131.976617] 9f60: aa7f9f94 00000000 8004a880 aa599680 00000000 00000000 aa7f9f78 aa7f9f78
[23131.984906] 9f80: 00000000 00000000 aa7f9f88 aa7f9f88 ac63c5c0 80043b00 00000000 00000000
[23131.993196] 9fa0: 00000000 aa7f9fb0 8000faf8 80043b0c 00000000 00000000 00000000 00000000
[23132.001485] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[23132.009774] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
[23132.018083] [<7f32bc20>] (h4_recv_buf [hci_uart]) from [<7f32be68>] (h4_recv+0x50/0x98 [hci_uart])
[23132.027170] [<7f32be68>] (h4_recv [hci_uart]) from [<7f32b0f0>] (hci_uart_tty_receive+0x74/0xb0 [hci_uart])
[23132.037048] [<7f32b0f0>] (hci_uart_tty_receive [hci_uart]) from [<80358e48>] (flush_to_ldisc+0x190/0x1a0)
[23132.046752] [<80358e48>] (flush_to_ldisc) from [<8003e0b8>] (process_one_work+0x154/0x458)
[23132.055133] [<8003e0b8>] (process_one_work) from [<8003e410>] (worker_thread+0x54/0x500)
[23132.063338] [<8003e410>] (worker_thread) from [<80043bec>] (kthread+0xec/0x104)
[23132.070750] [<80043bec>] (kthread) from [<8000faf8>] (ret_from_fork+0x14/0x3c)
[23132.078072] Code: e59b7004 e59b5008 0a00002d e3540000 (11d431bc) 
[23132.084329] ---[ end trace 501092e1c3e7ed97 ]---
[23132.089321] Unable to handle kernel paging request at virtual address ffffffec
[23132.096655] pgd = 80004000
[23132.096666] [ffffffec] *pgd=2effa821, *pte=00000000, *ppte=00000000
[23132.096673] Internal error: Oops: 17 [#2] SMP ARM
[23132.096711] Modules linked in: evdev hidp bnep hci_uart btbcm bluetooth brcmfmac brcmutil cfg80211 rfkill bcm2835_gpiomem bcm2835_rng uio_pdrv_genirq uio snd_bcm2835 snd_pcm snd_timer snd joydev uinput fuse ipv6
[23132.096720] CPU: 0 PID: 6716 Comm: kworker/0:0 Tainted: G      D         4.1.19-v7+ #858
[23132.096722] Hardware name: BCM2709
[23132.096732] task: aa4cb3c0 ti: aa7f8000 task.ti: aa7f8000
[23132.096741] PC is at kthread_data+0x18/0x20
[23132.096750] LR is at wq_worker_sleeping+0x1c/0xe0
[23132.096754] pc : [<8004432c>]    lr : [<8003f284>]    psr: 00000193
[23132.096754] sp : aa7f9b78  ip : aa7f9b88  fp : aa7f9b84
[23132.096757] r10: 2e7b1000  r9 : aa4cb6ac  r8 : 808240a4
[23132.096759] r7 : 80803580  r6 : 80803580  r5 : aa4cb3c0  r4 : 00000000
[23132.096762] r3 : 00000000  r2 : 00000000  r1 : 00000000  r0 : aa4cb3c0
[23132.096770] Flags: nzcv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment user
[23132.096772] Control: 10c5383d  Table: 2a7f406a  DAC: 00000015
[23132.096775] Process kworker/0:0 (pid: 6716, stack limit = 0xaa7f8210)
[23132.096778] Stack: (0xaa7f9b78 to 0xaa7fa000)
[23132.096782] 9b60:                                                       aa7f9b9c aa7f9b88
[23132.096787] 9b80: 8003f284 80044320 aefb4580 aa4cb3c0 aa7f9bec aa7f9ba0 80574048 8003f274
[23132.096793] 9ba0: 800781ac 80077e7c aa7f9c04 aa7f9bb8 80028030 80078194 00000000 807ff240
[23132.096799] 9bc0: aa77f824 aa7f8000 aa7f998c aa7f9c10 aa4cb628 00000001 00000001 ad900000
[23132.096804] 9be0: aa7f9c04 aa7f9bf0 80574324 80573c30 0420806c aa4cb3c0 aa7f9c44 aa7f9c08
[23132.096809] 9c00: 80029c60 805742e4 aa7f9c34 8082edd4 aa7f9c10 aa7f9c10 80827ad4 8088c2c4
[23132.096815] 9c20: 60000113 80827ad4 0000000b 7f32bc24 00000001 7f32bc22 aa7f9ccc aa7f9c48
[23132.096820] 9c40: 800141a0 800294cc aa7f8210 0000000b 00000000 80684768 00000008 00000000
[23132.096826] 9c60: 00000000 80827ad4 6506dad0 37623935 20343030 62393565 38303035 30613020
[23132.096833] 9c80: 32303030 33652064 30303435 28203030 34643131 63623133 80002029 805721ec
[23132.096838] 9ca0: 806c84c8 ffffffc8 00000017 aa7f9df0 00000000 aa4cb3c0 00000008 00000008
[23132.096844] 9cc0: aa7f9ce4 aa7f9cd0 80571f28 80013f58 aa7f9df0 ffffffc8 aa7f9d3c aa7f9ce8
[23132.096849] 9ce0: 80578e94 80571ec0 00000001 00000000 00000000 00000000 ad899a40 00000000
[23132.096855] 9d00: 00000fd4 00000000 00000000 00000000 00000000 80828084 00000017 80578c08
[23132.096860] 9d20: ffffffc8 aa7f9df0 00000008 00000008 aa7f9dec aa7f9d40 800091e8 80578c14
[23132.096866] 9d40: 00000000 00000400 00000000 00000000 00000000 00000001 00000000 00000000
[23132.096871] 9d60: ffffffff 807ff2f8 2e7b1000 ad899a40 ad89a680 00000002 00000000 80822dc8
[23132.096877] 9d80: aa7f9e4c aa7f9d90 8005a580 80059aa8 80053498 80803580 00000002 aefb02f8
[23132.096882] 9da0: 00000000 00000000 ad89a680 aefb4984 aa7f9dd4 80803580 00000000 800d4ec0
[23132.096888] 9dc0: 80822900 7f32bc20 a0000013 7f32bc20 a0000013 ffffffff aa7f9e24 ad103000
[23132.096893] 9de0: aa7f9e64 aa7f9df0 805783dc 800091ac ad103000 ffffffac aa420834 00000008
[23132.096899] 9e00: ffffffac 00000003 aa420834 7f32d194 ad103000 00000008 00000008 aa7f9e64
[23132.096904] 9e20: aa7f9e68 aa7f9e38 7f32be68 7f32bc20 a0000013 ffffffff 00000008 00000008
[23132.096910] 9e40: ac594580 ac7c4200 ac7c4840 ada8a004 ada8a000 00000008 aa7f9e8c aa7f9e68
[23132.096915] 9e60: 7f32be68 7f32bbf8 7f32d194 00000003 ac594580 ad3d4000 ac7c4200 aa420800
[23132.096921] 9e80: aa7f9eac aa7f9e90 7f32b0f0 7f32be24 00000008 00000008 ad3d4000 ada8a014
[23132.096926] 9ea0: aa7f9ee4 aa7f9eb0 80358e48 7f32b088 aa7f9f0c aa7f9ec0 80573e14 aa599680
[23132.096932] 9ec0: ada8a004 aefb4080 aefb7f00 00000000 aa599680 00000000 aa7f9f24 aa7f9ee8
[23132.096938] 9ee0: 8003e0b8 80358cc4 aefb4080 aefb4094 aa7f8000 00000008 aa599680 aefb4080
[23132.096944] 9f00: aa599698 aefb4094 aa7f8000 00000008 aa599680 aefb4080 aa7f9f5c aa7f9f28
[23132.096949] 9f20: 8003e410 8003df70 8003e3bc 80822900 00000000 00000000 ac63c5c0 aa599680
[23132.096954] 9f40: 8003e3bc 00000000 00000000 00000000 aa7f9fac aa7f9f60 80043bec 8003e3c8
[23132.096960] 9f60: aa7f9f94 00000000 8004a880 aa599680 00000000 00000000 aa7f9f78 aa7f9f78
[23132.096965] 9f80: 00000001 00010001 aa7f9f88 aa7f9f88 ac63c5c0 80043b00 00000000 00000000
[23132.096970] 9fa0: 00000000 aa7f9fb0 8000faf8 80043b0c 00000000 00000000 00000000 00000000
[23132.096975] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[23132.096980] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
[23132.096993] [<8004432c>] (kthread_data) from [<8003f284>] (wq_worker_sleeping+0x1c/0xe0)
[23132.097006] [<8003f284>] (wq_worker_sleeping) from [<80574048>] (__schedule+0x424/0x6b4)
[23132.097018] [<80574048>] (__schedule) from [<80574324>] (schedule+0x4c/0xa4)
[23132.097029] [<80574324>] (schedule) from [<80029c60>] (do_exit+0x7a0/0xa38)
[23132.097040] [<80029c60>] (do_exit) from [<800141a0>] (die+0x254/0x43c)
[23132.097051] [<800141a0>] (die) from [<80571f28>] (__do_kernel_fault.part.0+0x74/0x84)
[23132.097062] [<80571f28>] (__do_kernel_fault.part.0) from [<80578e94>] (do_page_fault+0x28c/0x398)
[23132.097069] [<80578e94>] (do_page_fault) from [<800091e8>] (do_DataAbort+0x48/0xc4)
[23132.097075] [<800091e8>] (do_DataAbort) from [<805783dc>] (__dabt_svc+0x3c/0x60)
[23132.097078] Exception stack(0xaa7f9df0 to 0xaa7f9e38)
[23132.097082] 9de0:                                     ad103000 ffffffac aa420834 00000008
[23132.097087] 9e00: ffffffac 00000003 aa420834 7f32d194 ad103000 00000008 00000008 aa7f9e64
[23132.097091] 9e20: aa7f9e68 aa7f9e38 7f32be68 7f32bc20 a0000013 ffffffff
[23132.097106] [<805783dc>] (__dabt_svc) from [<7f32bc20>] (h4_recv_buf+0x34/0x22c [hci_uart])
[23132.097121] [<7f32bc20>] (h4_recv_buf [hci_uart]) from [<7f32be68>] (h4_recv+0x50/0x98 [hci_uart])
[23132.097130] [<7f32be68>] (h4_recv [hci_uart]) from [<7f32b0f0>] (hci_uart_tty_receive+0x74/0xb0 [hci_uart])
[23132.097141] [<7f32b0f0>] (hci_uart_tty_receive [hci_uart]) from [<80358e48>] (flush_to_ldisc+0x190/0x1a0)
[23132.097152] [<80358e48>] (flush_to_ldisc) from [<8003e0b8>] (process_one_work+0x154/0x458)
[23132.097161] [<8003e0b8>] (process_one_work) from [<8003e410>] (worker_thread+0x54/0x500)
[23132.097168] [<8003e410>] (worker_thread) from [<80043bec>] (kthread+0xec/0x104)
[23132.097175] [<80043bec>] (kthread) from [<8000faf8>] (ret_from_fork+0x14/0x3c)
[23132.097181] Code: e24cb004 e52de004 e8bd4000 e59032c0 (e5130014) 
[23132.097187] ---[ end trace 501092e1c3e7ed98 ]---
[23132.097190] Fixing recursive fault but reboot is needed!

@diogomsantos It is good to know that a bluetooth dongle solves the problem and also how to do it.
I am also interested in the problem and mentioned it in several places.
Relax and try to contribute to the cause. Complaining does not help.

@mauruco This is not a forum.
The fact that using a BT dongle is a workaround for this problem was already well known, and spread all over the internet. It was also already mentioned here earlier.
But this not a how to workaround the issue, this is for fixing the issue in the RPi 3 internal BT chip.
And what I did till now to the "cause", was something helpful, and that was pointing some people to this issue, people who was able to post kernel logs.
So do you realize that your posts don't help nobody, and you did nothing to fix the issue ?
It is just spam. Keep this on topic.

@diogomsantos I do not know what your problem boy. Just try to be constructive. People also look for workarrounds and found this place! Everyone has understood your message. OK? Have a nice day.

Where are the logs kept that show the error(s)?

Has anybody tried a 4.4 kernel yet to see if that fixes the issue?

https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=144087

I don't even see a mention of bluetooth there ^

Bluetooth doesn't need to be mentioned there, these are the instructions on how to upgrade to a 4.4 kernel. There is a high likelihood a lot of patches and improvements have been done for the Bluetooth drivers in the new kernel version. All the crash logs here seem to be from a 4.1 kernel.

What is in there is a note about Device Tree:

"Notes:
Device tree is required for 4.4 kernel. Settings like "dtoverlay=" to disable device tree will cause failure to boot."

So, safe to assume that current configs that disable onboard bt would cause issues?

"dtoverlay=pi3-disable-bt"

Why would you think that? What is the connection?

And FYI, for Foundation kernels the device_tree= setting is now ignored.

@Prindle19 : I think they are talking about "device_tree=" here, as pelwell pointed out.

Btw, to revert to an earlier version:

1) Find the sha hash here: https://github.com/Hexxeh/rpi-firmware/commits/master
2) sudo rpi-update

For instance, to revert to 4.1.19 use the following hash: 6e8b794818e06f50724774df3b1d4c6be0b5708c

To clear things up, I already upgraded to the latest 4.4 kernel branch (https://github.com/Hexxeh/rpi-firmware) and no matter which kernel is in place, I always see the same behavior:

Connecting my PS4 controller to the integrated bluetooth controller -> the system always freezes within minutes.

Connecting my PS4 controller to an usb bluetooth stick while the internal bluetooth controller still is active -> no freezes at all

Connecting my PS4 controller to an usb bluetooth stick while the internal bluetooth controller is deactivated (dtoverlay=pi3-disable-bt-overlay in /boot/config.txt) -> no freezes at all

Ok, that's disappointing. With my PS3 controller connected to bluetooth, I can play N64 games for hours without issues. But as soon as I play a PSX game, it locks up within several minutes. I guess separate bluetooth dongle is the way to go for now. If a new kernel doesn't fix the issue, it will probably not be fixed anytime soon. The only hope right now is that someone stumbles across a patch for the issue and merges it into the rpi kernel.

Ok, so I upgraded to this version here, and I have been playing several hours of SNES/N64 games without a single lockup. Have not been playing much PSX games though, that was the only one where it used to lock up for me.

If you want to try it out and see if it helps you, run 'sudo rpi-update 15ffab5493d74b12194e6bfc5bbb1c0f71140155'.

Did you determine what's different about it?

I can play n64 games for quite awhile before anything happens. It's PSX games that do it for me.

It's a much newer kernel (4.1 -> 4.4), so thousands of things will have
changed.

No clue why PSX causes it to happen more rapidly than N64, must have something to do with the emulator.

On Sun, May 8, 2016 at 6:30 PM, FreakyBigFoot [email protected]
wrote:

Did you determine what's different about it?

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-217750141

I'll give this a try in the next few days. Thanks!

I can play n64 games for quite awhile before anything happens. It's PSX games that do it for me.

I get the lock-ups with every emulator i've tried within a couple of minutes. I'll give the new kernel a try tonight if I can figure out the curl-ssl cert error i'm getting.

Sounds good. I'm hoping a couple people could update to test and verify. Unfortunately I gave my pi3 to a friend and won't have another until Wednesday.

For anybody getting ssl cert error, the only way to work around it I have found is by disabling
the cert check for rpi-update as follows:

1) Edit /usr/bin/rpi-update and add -k flag to all occurrences of curl,
e.g."sudo sed -i 's/curl/curl -k/g' /usr/bin/rpi-update"
2) Run rpi-update without self update, e.g. "sudo UPDATE_SELF=0 rpi-update
"

EDIT: Fix typo (SELF_UPDATE)

On Mon, May 9, 2016 at 8:52 AM, kyserthehun [email protected]
wrote:

I can play n64 games for quite awhile before anything happens. It's PSX
games that do it for me.

I get the lock-ups with every emulator i've tried within a couple of
minutes. I'll give the new kernel a try tonight if I can figure out the
curl-ssl cert error i'm getting.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-217855520

i've tested it with kernel 4.4. After about 15 minutes i started to get wifi-problems, but the pi hasn't locked up for me. i can't definitly say that this bluetooth bug is fixed, but it's definlty better than before

Ah, thanks Konradsa. I've been fooling with this for a couple of days now and google wasn't helping. If anyone is still having problems after following his instructions.

"sudo SELF_UPDATE=0
is flip-flopped 'sudo update_self=0' ;)

I'll report back on the controller issue tonight.

I tried the 4.4 kernel, no blue tooth at all. Reverted back to 4.1 still
no onboard Bluetooth. So that got broken somehow.

If I put my USB BT adapter back in it works fine.

I did remove the device tree setting I had in config.txt to be sure the
onboard wasn't disabled.

Bummer
On May 9, 2016 10:42 AM, "kyserthehun" [email protected] wrote:

Ah, thanks Konradsa. I've been fooling with this for a couple of days now
and google wasn't helping. If anyone is still having problems after
following his instructions.

"sudo SELF_UPDATE=0
is flip-flopped 'sudo update_self=0' ;)

I'll report back on the controller issue tonight.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-217884127

Bluetooth, audio, etc. all works fine for me. Make sure you are using this version here:
"sudo UPDATE_SELF=0 rpi-update 15ffab5493d74b12194e6bfc5bbb1c0f71140155"

Yes, I did use the same Hash, as well as when reverting, I used the revert
hash posted earlier.

Not a big deal, just reporting what happened to me. :) This is retropie
3.6 i'm using.

On Mon, May 9, 2016 at 3:40 PM, konradsa [email protected] wrote:

Bluetooth, audio, etc. all works fine for me. Make sure you use try the
right version:
"sudo UPDATE_SELF=0 rpi-update 6e8b794818e06f50724774df3b1d4c6be0b5708c"

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-217967032

Played around an hour or so with the new kernel and a PS3 controller connected through the onboard bluetooth. No issues for me. Played SNES and PSX without a lock-up. Pi-Hole seems to be working well so no issues with the LAN. Can't comment on WiFi.

I see a bunch of the following messages in the log file now:

[111588.504688] Bluetooth: hci0: Frame reassembly failed (-84)

Didn't see those before, I assume this is what used to crash the old
kernel, but maybe with the newer kernel it keeps chugging along now without
crashing.
On May 9, 2016 10:22 PM, "kyserthehun" [email protected] wrote:

Played around an hour or so with the new kernel and a PS3 controller
connected through the onboard bluetooth. No issues for me. Played SNES and
PSX without a lock-up. Pi-Hole seems to be working well so no issues with
the LAN. Can't comment on WiFi.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-218042754

I think I can confirm that this issue is fixed for good in Linux 4.4 Kernel.

See here: diff

If you look closely, you can see line 195 was added in 4.4 which sets the buffer pointer to NULL if the reassembly error occurs. This prevents it from being treated as a valid buffer later on and causing a crash.

I updated and it froze wiithin 1 minute of playing PSX.

Can you run 'uname -a' and post the output here?
On May 10, 2016 6:18 PM, "FreakyBigFoot" [email protected] wrote:

I updated and it froze wiithin 1 minute of playing PSX.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-218308757

running retropie 3.7, updated to 4.4 kernel:

Linux retropie 4.4.9-v7+ #884 SMP Fri May 6 17:28:59 BST 2016 armv7l GNU/Linux

played fba, mame and super nes, all using an original DS3 controller and the onboard bluetooth for more than an hour

until now, no freezes!

I updated mine and when I 'uname -a' It says 'Linux retropie 4.1.19-v7+ #851 SMP Sat Mar 5 22:58:42 GMT 2016 armv7l GNU/Linux'

Did my update fail? When I try to update it says 'Your firmware is already up to date'.

@FreakyBigFoot You are still running the old version. You need to run this:
"sudo UPDATE_SELF=0 rpi-update 15ffab5493d74b12194e6bfc5bbb1c0f71140155"

EDIT: Hash fixed

@konradsa I did and now it says I'm up to date. Do I need to downgrade? Should I start from scratch?

dear konradsa, the correct version is

sudo UPDATE_SELF=0 rpi-update 15ffab5493d74b12194e6bfc5bbb1c0f71140155

6e8b794818e06f50724774df3b1d4c6be0b5708c is 4.1's

for 4.4 use 15ffab5493d74b12194e6bfc5bbb1c0f71140155

EDIT: corrected for 4.4 kernel. thanks @konradsa

@lufeig : You are right, copy and paste error. :-) You got one too actually.

"sudo UPDATE_SELF=0 rpi-update 15ffab5493d74b12194e6bfc5bbb1c0f71140155" should give you the right version

Woah these are very confusing. You've now listed sever. @lufeig said to do '6e8b794818e06f50724774df3b1d4c6be0b5708c'

@konradsa said to do '15ffab5493d74b12194e6bfc5bbb1c0f71140155'

I don't even know why I am using the long hashes, I should just be using the short ones. :-)

Anyways, you can see a list of all the commits here: https://github.com/Hexxeh/rpi-firmware/commits/master

15ffab5493d74b12194e6bfc5bbb1c0f71140155 is the correct one

@FreakyBigFoot, i amended my previous post.

as @konradsa said, i pasted the same 4.1 twice. sorry.

i hope everything is clear now. :-)

First of all thank you so much for narrowing this all down it's been driving me crazy. After disabling bluetooth it fixed all the crashes.
I am running:
Linux retropie 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux

I Ran: (as rpi-update is not installed)
sudo UPDATE_SELF=0 apt-get install 15ffab5493d74b12194e6bfc5bbb1c0f71140155

and:
sudo UPDATE_SELF=0 apt-get install 6e8b794818e06f50724774df3b1d4c6be0b5708c

I receive the error message: "Unable to locate package" on both commands.

You need to install rpi-update first by running 'sudo apt-get install
rpi-update'. Then follow the directions above.
On May 11, 2016 2:04 AM, "Alexander Indo" [email protected] wrote:

First of all thank you so much for narrowing this all done it's been
driving me crazy. After disabling bluetooth it fixed all the crashes.
I am running:
Linux retropie 4.1.19-v7+ #858
https://github.com/raspberrypi/linux/pull/858 SMP Tue Mar 15 15:56:00
GMT 2016 armv7l GNU/Linux

I Ran: (as rpi-update is not installed)
sudo UPDATE_SELF=0 apt-get install 15ffab5493d74b12194e6bfc5bbb1c0f71140155

and:
sudo UPDATE_SELF=0 apt-get install 6e8b794818e06f50724774df3b1d4c6be0b5708c

I receive the error message: "Unable to locate package" on both commands.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-218369777

Thanks to everyone for the information. I had to use a few post to get mine updated so I put it all in one here. I was running RP3.7 with K4.1

I first needed to install rpi-update...
"sudo apt-get install rpi-update"

Then I had to fix the SSL Cert error that happens when you try and update the K...
"sudo sed -i 's/curl/curl -k/g' /usr/bin/rpi-update"

I then update the K to 4.4...
"sudo UPDATE_SELF=0 rpi-update 15ffab5493d74b12194e6bfc5bbb1c0f71140155"

So far I have tried everything I could to get this to freeze as I have before and its working fine. I will keep testing.

Thanks everyone!!!

Update - Over 3 hours in with playing random games and whatnot I have not had one freeze.

I will try out rpi-update I guess I've steered away from it due to this conversation here: https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=58963

pablo808 wrote:
Only run rpi-update if you need the latest bleeding edit updates.

ShiftPlusOne wrote:
That's pretty much it. I would change that to "Only run rpi-update if you know you need a specific build of the firmware or if you were asked to do so by Dom."

Yes, apt-get upgrade WILL update your firmware to the latest stable version, and that MAY conflict with rpi-update. If you see something on the internet that says otherwise, it's probably outdated information.

Reloading a fresh install of 3.7 to see if I can get my ps3 controller to
connect.
Nothing would get it to work after the initial kernel change, buy that
could have been something else that did that.

I will report back.
On May 11, 2016 12:50 PM, "Alexander Indo" [email protected] wrote:

I will try out rpi-update I guess I've steered away from it due to this
conversation here:
https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=58963

pablo808 wrote:
Only run rpi-update if you need the latest bleeding edit updates.

ShiftPlusOne wrote:
That's pretty much it. I would change that to "Only run rpi-update if you
know you need a specific build of the firmware or if you were asked to do
so by Dom."

Yes, apt-get upgrade WILL update your firmware to the latest stable
version, and that MAY conflict with rpi-update. If you see something on the
internet that says otherwise, it's probably outdated information.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-218519761

@BaDvs3viL
Thank you!
Worked perfectly.
also solved a problem in kodi with "CCurlFile::FillBuffer - Failed: Could not connect to server(7)"
Cheers

I give up. I'm not sure why but I can't connect to my PS3 even with a
fresh flash. I could when i first got the pi3. Even wired it will get one
or two buttons then no response.

If I plug in my USB Orico CSR based BT adapter everything swtches over, and
works flawlessly on the fly.

So weird, maybe my pi3 has gone defective somehow. It doesn't show with
hciconfig unless i install pi-bluetooth, even then nothing will connect to
it.

Glad I bought this USB adapter now lol I'll just stick with it.

On Wed, May 11, 2016 at 2:47 PM, mauruco [email protected] wrote:

@BaDvs3viL https://github.com/BaDvs3viL
Thank you!
Worked perfectly.
also solved a problem in kodi with "CCurlFile::FillBuffer - Failed: Could
not connect to server(7)"
Cheers

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-218552921

I am sure I can speak for myself and others for saying a big huge "THANK YOU" to whomever fixed this issue. I have been waiting for this to be addressed since I bought my pi3 on release day. However, I would feel much more comfortable if this thread was "officially closed/marked as fixed" by who wrote the commits? Just a thought....again thanks for all of your hard work.

Just adding that I played some PSX Metal Gear on RetroPie 3.7 kernel 4.4, with no freezes or lockups, using my DS3 controllers connected to the RPi3 onboard Bluetooth

Thank you everyone!! 😄
Like many others, I've been struggling with this issue on my Pi3 since launch!
I hope I'm not jinxing it, but I've been running Mario 64 for over 40mins now with no freezing (touch wood) using @BaDvs3viL 's upgrade steps above.
Now hopefully my Pi3 can be the RetroGaming device I intended to use it for! 😉
Thanks again

My two cents worth - the steps, as I took them:

1. Did a sudo apt-get update && sudo apt-get upgrade to upgrade any software packages.
2. Did sudo sed -i 's/curl/curl -k/g' /usr/bin/rpi-update to get around some SSL certificate issue.
3. Did sudo UPDATE_SELF=0 rpi-update 15ffab5493d74b12194e6bfc5bbb1c0f71140155 to update the Pi to the revision 15ffab...
4. Rebooted, cos that usually fixes things

After that, no lockups after playing for an hour on the PSX emulator in RetroPie. Usually I wouldn't have gotten past the main menu or options screen of a game. Works with SNES, Genesis/Megadrive and N64 too.

So the evidence is pretty clear that this bug has been fixed in a newer kernel. Also the diff between old and new kernel clearly shows that it has been addressed:
diff between kernel 4.1 and 4.4

Not sure what should be done here with this issue. Nobody will probably backport this fix to 4.1 kernel and going to kernel 4.4 is clearly the way forward. However most people won't get that fix until Retropie updates its version.

Note: rpi-update is no longer needed.
sudo apt-get update && sudo apt-get dist-upgrade will get the 4.4 kernel now.
See: https://www.raspberrypi.org/blog/another-update-raspbian/

That is good news! :-)

On Fri, May 13, 2016 at 9:33 AM, popcornmix [email protected]
wrote:

Note: rpi-update is no longer needed.
sudo apt-get update && sudo apt-get dist-upgrade will get the 4.4 kernel
now.
See: https://www.raspberrypi.org/blog/another-update-raspbian/

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-219043671

Based On the fact this is fixed and people are having success, I'm going to close this issue.

Thanks for all the help everyone.

Word of warning, don't run sudo apt-get update && sudo apt-get dist-upgrade, you will lose bluetooth for good, just happened to me. There seem to be more underlying bluetooth changes in the latest raspbian update that break bluetooth for RetroPie.

Ok, I really hate being the guinea pig for you guys! ;-)

If you lose bluetooth after dist-upgrade, here is how to fix it:
Essentially, you need to downgrade pi-bluetooh from 0.1.1 to 0.1.0

1) wget http://archive.raspberrypi.org/debian/pool/main/p/pi-bluetooth/pi-bluetooth_0.1.0_armhf.deb
2) sudo dpkg -i pi-bluetooth_0.1.0_armhf.deb
3) Reboot

If that works for you, run sudo apt-mark hold pi-bluetooth to prevent it from being updated by accident.

Hope it saves you a lot of time and frustration

Another weird thing I noticed after the upgrade is that the system was only using the powersave governor, thereby severely slowing down performance of the system. If that happens to you too, then you can run sudo apt-get install cpufrequtils and reboot to fix it. The defaults it to the ondemand governor again.

EDIT: Fixed typo

That package should be cpufrequtils, you missed the 's'! Nice one though, you're our hero!

Still haven't been able to get a PS3 controller to pair. 3.6, 3.7, fixes
posted above, nothing works. It did at one time when I first installed
3.6, but i had the freezing so i've gotten a USB BT adapter since. My OCD
wants the on-board to work though :)

This is what I get with a fresh 3.7 Image:
After initial boot
apt-get update
apt-get dist-upgrade
wget
http://archive.raspberrypi.org/debian/pool/main/p/pi-bluetooth/pi-bluetooth_0.1.0_armhf.deb
sudo dpkg -i pi-bluetooth_0.1.0_armhf.deb
Reboot
Update RetroPie-Setup Script
Install PS3 drivers through menu.
Connect USB cable to controller, works fine in Emulation Station.
Disconnect USB and push PS button
_Crickets_

root@retropie:/home/pi# dmesg | grep Blue
[ 6.578766] Bluetooth: Core ver 2.21
[ 6.578850] Bluetooth: HCI device and connection manager initialized
[ 6.578866] Bluetooth: HCI socket layer initialized
[ 6.578877] Bluetooth: L2CAP socket layer initialized
[ 6.578906] Bluetooth: SCO socket layer initialized
[ 10.593502] Bluetooth: HCI UART driver ver 2.3
[ 10.593523] Bluetooth: HCI UART protocol H4 registered
[ 10.593533] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 10.593729] Bluetooth: HCI UART protocol BCM registered
[ 10.839018] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 10.839031] Bluetooth: BNEP filters: protocol multicast
[ 10.839045] Bluetooth: BNEP socket layer initialized
[ 13.956338] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 13.956361] Bluetooth: HIDP socket layer initialized

root@retropie:/home/pi# lsusb
Bus 001 Device 004: ID 1997:2433
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514
Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

root@retropie:/home/pi# hciconfig
hci0: Type: BR/EDR Bus: UART
BD Address: B8:27:EB:B8:14:CB ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:775 acl:0 sco:0 events:48 errors:0
TX bytes:1560 acl:0 sco:0 commands:48 errors:0

root@retropie:/home/pi# systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
Active: failed (Result: exit-code) since Sat 2016-05-14 13:48:04 UTC;
1min 6s ago
Docs: man:bluetoothd(8)
Process: 1461 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited,
status=203/EXEC)
Main PID: 1461 (code=exited, status=203/EXEC)

May 14 13:48:04 retropie systemd[1]: bluetooth.service: main process
exited, code=exited, status=203/EXEC
May 14 13:48:04 retropie systemd[1]: Failed to start Bluetooth service.
May 14 13:48:04 retropie systemd[1]: Unit bluetooth.service entered failed
state.
root@retropie:/home/pi#

The "systemctl status bluetooth.service" error may simply be because of
sixad, and be normal. But nothing I do will get the controller to pair. I
actually can't get it to pair with the USB BT adapter now either.

I've re-paired the controller to my actual PS3 and tried again to the pi
with nothing as a result as well. This should be working.

I'll reflash back to fresh 3.7 and go baby steps trying with the USB BT
adapter mixed in to be sure it still works as I go.

Any ideas?

On Sat, May 14, 2016 at 9:30 AM, greener2 [email protected] wrote:

That package should be cpufrequtils, you missed the 's'! Nice one though,
you're our hero!

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-219220465

I've started using hcidump to see what's actually going on. With the USB
BT adapter I can now get it connected no problem, dump looks fine.

When I try using the onboard, I do get events when runnning 'sixad --start'
but nothing from the controller in the events.

Seems the PS3 controller just doesn't like the onboard for some reason,
this is with 4.4.9-v7

More testing to come.

On Sat, May 14, 2016 at 10:16 AM, Kevin Smith [email protected] wrote:

Still haven't been able to get a PS3 controller to pair. 3.6, 3.7, fixes
posted above, nothing works. It did at one time when I first installed
3.6, but i had the freezing so i've gotten a USB BT adapter since. My OCD
wants the on-board to work though :)

This is what I get with a fresh 3.7 Image:
After initial boot
apt-get update
apt-get dist-upgrade
wget
http://archive.raspberrypi.org/debian/pool/main/p/pi-bluetooth/pi-bluetooth_0.1.0_armhf.deb
sudo dpkg -i pi-bluetooth_0.1.0_armhf.deb
Reboot
Update RetroPie-Setup Script
Install PS3 drivers through menu.
Connect USB cable to controller, works fine in Emulation Station.
Disconnect USB and push PS button
_Crickets_

root@retropie:/home/pi# dmesg | grep Blue
[ 6.578766] Bluetooth: Core ver 2.21
[ 6.578850] Bluetooth: HCI device and connection manager initialized
[ 6.578866] Bluetooth: HCI socket layer initialized
[ 6.578877] Bluetooth: L2CAP socket layer initialized
[ 6.578906] Bluetooth: SCO socket layer initialized
[ 10.593502] Bluetooth: HCI UART driver ver 2.3
[ 10.593523] Bluetooth: HCI UART protocol H4 registered
[ 10.593533] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 10.593729] Bluetooth: HCI UART protocol BCM registered
[ 10.839018] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 10.839031] Bluetooth: BNEP filters: protocol multicast
[ 10.839045] Bluetooth: BNEP socket layer initialized
[ 13.956338] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 13.956361] Bluetooth: HIDP socket layer initialized

root@retropie:/home/pi# lsusb
Bus 001 Device 004: ID 1997:2433
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514
Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

root@retropie:/home/pi# hciconfig
hci0: Type: BR/EDR Bus: UART
BD Address: B8:27:EB:B8:14:CB ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:775 acl:0 sco:0 events:48 errors:0
TX bytes:1560 acl:0 sco:0 commands:48 errors:0

root@retropie:/home/pi# systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
Active: failed (Result: exit-code) since Sat 2016-05-14 13:48:04 UTC;
1min 6s ago
Docs: man:bluetoothd(8)
Process: 1461 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited,
status=203/EXEC)
Main PID: 1461 (code=exited, status=203/EXEC)

May 14 13:48:04 retropie systemd[1]: bluetooth.service: main process
exited, code=exited, status=203/EXEC
May 14 13:48:04 retropie systemd[1]: Failed to start Bluetooth service.
May 14 13:48:04 retropie systemd[1]: Unit bluetooth.service entered failed
state.
root@retropie:/home/pi#

The "systemctl status bluetooth.service" error may simply be because of
sixad, and be normal. But nothing I do will get the controller to pair. I
actually can't get it to pair with the USB BT adapter now either.

I've re-paired the controller to my actual PS3 and tried again to the pi
with nothing as a result as well. This should be working.

I'll reflash back to fresh 3.7 and go baby steps trying with the USB BT
adapter mixed in to be sure it still works as I go.

Any ideas?

On Sat, May 14, 2016 at 9:30 AM, greener2 [email protected]
wrote:

That package should be cpufrequtils, you missed the 's'! Nice one
though, you're our hero!

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-219220465

Actually I really do give up, i'm not getting anything from the onboard at
all, no matter what kernel version or retropie version I use. Without
sixad I can pair my phone no problems with the onboard, it just doesn't
work with sixad.

On Sat, May 14, 2016 at 12:04 PM, Kevin Smith [email protected] wrote:

I've started using hcidump to see what's actually going on. With the USB
BT adapter I can now get it connected no problem, dump looks fine.

When I try using the onboard, I do get events when runnning 'sixad
--start' but nothing from the controller in the events.

Seems the PS3 controller just doesn't like the onboard for some reason,
this is with 4.4.9-v7

More testing to come.

On Sat, May 14, 2016 at 10:16 AM, Kevin Smith [email protected] wrote:

Still haven't been able to get a PS3 controller to pair. 3.6, 3.7, fixes
posted above, nothing works. It did at one time when I first installed
3.6, but i had the freezing so i've gotten a USB BT adapter since. My OCD
wants the on-board to work though :)

This is what I get with a fresh 3.7 Image:
After initial boot
apt-get update
apt-get dist-upgrade
wget
http://archive.raspberrypi.org/debian/pool/main/p/pi-bluetooth/pi-bluetooth_0.1.0_armhf.deb
sudo dpkg -i pi-bluetooth_0.1.0_armhf.deb
Reboot
Update RetroPie-Setup Script
Install PS3 drivers through menu.
Connect USB cable to controller, works fine in Emulation Station.
Disconnect USB and push PS button
_Crickets_

root@retropie:/home/pi# dmesg | grep Blue
[ 6.578766] Bluetooth: Core ver 2.21
[ 6.578850] Bluetooth: HCI device and connection manager initialized
[ 6.578866] Bluetooth: HCI socket layer initialized
[ 6.578877] Bluetooth: L2CAP socket layer initialized
[ 6.578906] Bluetooth: SCO socket layer initialized
[ 10.593502] Bluetooth: HCI UART driver ver 2.3
[ 10.593523] Bluetooth: HCI UART protocol H4 registered
[ 10.593533] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 10.593729] Bluetooth: HCI UART protocol BCM registered
[ 10.839018] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 10.839031] Bluetooth: BNEP filters: protocol multicast
[ 10.839045] Bluetooth: BNEP socket layer initialized
[ 13.956338] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 13.956361] Bluetooth: HIDP socket layer initialized

root@retropie:/home/pi# lsusb
Bus 001 Device 004: ID 1997:2433
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

root@retropie:/home/pi# hciconfig
hci0: Type: BR/EDR Bus: UART
BD Address: B8:27:EB:B8:14:CB ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:775 acl:0 sco:0 events:48 errors:0
TX bytes:1560 acl:0 sco:0 commands:48 errors:0

root@retropie:/home/pi# systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
Active: failed (Result: exit-code) since Sat 2016-05-14 13:48:04 UTC;
1min 6s ago
Docs: man:bluetoothd(8)
Process: 1461 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited,
status=203/EXEC)
Main PID: 1461 (code=exited, status=203/EXEC)

May 14 13:48:04 retropie systemd[1]: bluetooth.service: main process
exited, code=exited, status=203/EXEC
May 14 13:48:04 retropie systemd[1]: Failed to start Bluetooth service.
May 14 13:48:04 retropie systemd[1]: Unit bluetooth.service entered
failed state.
root@retropie:/home/pi#

The "systemctl status bluetooth.service" error may simply be because of
sixad, and be normal. But nothing I do will get the controller to pair. I
actually can't get it to pair with the USB BT adapter now either.

I've re-paired the controller to my actual PS3 and tried again to the pi
with nothing as a result as well. This should be working.

I'll reflash back to fresh 3.7 and go baby steps trying with the USB BT
adapter mixed in to be sure it still works as I go.

Any ideas?

On Sat, May 14, 2016 at 9:30 AM, greener2 [email protected]
wrote:

That package should be cpufrequtils, you missed the 's'! Nice one
though, you're our hero!

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-219220465

@KrS14 try removing the the ps3 controller config from the retrpie-setup menu and then re-install it should pair 1st controller however I found problem in being able to pair any additional controllers.

I'd recommend to wait a bit before updating.

After the raspbian update, bluetooth hardware is not recognized anymore here. See the comments here: https://www.raspberrypi.org/blog/another-update-raspbian/

Downgradding pi-bluetooth didn't help.

@paulrouget I just upgraded raspbian and downgraded pi-bluetooth and it worked for me! Did you try rebooting?

Removing previous PS3 config, downgrading pi-bluetooth and rebooting worked for me as well.

I can try from a state of nothing ever being attempted and it does pair.
No config present.
On May 15, 2016 5:02 PM, "BenjiZombie" [email protected] wrote:

Removing previous PS3 config, downgrading pi-bluetooth and rebooting
worked for me as well.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-219310333

Removing previous PS3 config

That might be the thing I haven't tried.

Anyway, I've reinstalled, and it works now.

If the fix for this bug is to work around it by downgrading, then it's not fixed and should be reopened.

If the fix for this bug is to work around it by downgrading, then it's not fixed and should be reopened.

It is fixed. Downgrading is not necessary at least on a fresh install.

If downgrading is necessary after an update, then I believe it's better to file a new issue (and maybe not in raspberrypi/linux) with STRs.

Downgrading will not be necessary on a fresh install, since that one uses
pi-bluetooth 0.1.0. But as soon as you run sudo apt dist-upgrade (or
upgrade via the retropie_setup menu) you will get the same problem again.

On Tue, May 17, 2016 at 12:03 AM, Paul Rouget [email protected]
wrote:

If the fix for this bug is to work around it by downgrading, then it's not
fixed and should be reopened.

It is fixed. Downgrading is not necessary at least on a fresh install.

If downgrading is necessary after an update, then I believe it's better to
file a new issue (and maybe not in raspberrypi/linux) with STRs.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-219614061

Ok I have fixed this without downgrading.
I was looking at this forum thread https://www.raspberrypi.org/forums/viewtopic.php?t=148305&p=976259

Ok the important part was this

After the 5/13/16 upgrade (incl. new 4.4.9 kernel) my pi3 Bluetooth stopped working. I narrowed it down to /dev/serial0 and /dev/serial1 were missing and hence the /lib/systemd/system/hciuart.service failed since it now uses "serial1" instead of "ttyAMA0" in previous releases.

This is the script snippet in question:
ExecStart=/usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow -

In a separate post - DirkS, indicated that these files were created by 99-com.rules which I did not have on my system.

Using apt-file I figured out that I was missing the raspberrypi-sys-mods package. Once I did an apt-get of the package Bluetooth is working again.

apt-file search 99-com.rules
raspberrypi-sys-mods: /etc/udev/rules.d/99-com.rules
apt-get install raspberrypi-sys-mods

1) update (via apt-get upgrade and apt-get dist-upgrade)
2) yes it was working well until the 5/13/16 update
3) n/a - I have it working now
4) n/a - I have it working now
5) n/a - I have it working now

This did no work for me because I forgot to choose replacing 99-com.rules when i did the installation.
So renamed may /etc/udev/rules.d/99-com.rules to 99-com.rules.bak then I used a text editor to create a new 99-com.rules. I then copied the 99-com.rules from here https://github.com/RPi-Distro/raspberrypi-sys-mods/blob/master/etc/udev/rules.d/99-com.rules .

Every thing works now.

I can confirm, apt-get install raspberrypi-sys-mods and selecting Y
during install fixed bluetooth for me, even with pi-bluetooth 0.1.1. Thanks!

Run sudo apt-mark unhold pi-bluetooth in case you put pi-bluetooth on
hold to keep it pinned at 0.1.0.

On Wed, May 18, 2016 at 9:03 PM, Dennisnuel [email protected]
wrote:

Ok I have fixed this without downgrading.
I was looking at this forum thread
https://www.raspberrypi.org/forums/viewtopic.php?t=148305&p=976259

Ok the important part was this

After the 5/13/16 upgrade (incl. new 4.4.9 kernel) my pi3 Bluetooth
stopped working. I narrowed it down to /dev/serial0 and /dev/serial1 were
missing and hence the /lib/systemd/system/hciuart.service failed since it
now uses "serial1" instead of "ttyAMA0" in previous releases.

This is the script snippet in question:
ExecStart=/usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow -

In a separate post - DirkS, indicated that these files were created by
99-com.rules which I did not have on my system.

Using apt-file I figured out that I was missing the raspberrypi-sys-mods
package. Once I did an apt-get of the package Bluetooth is working again.

apt-file search 99-com.rules
raspberrypi-sys-mods: /etc/udev/rules.d/99-com.rules
apt-get install raspberrypi-sys-mods

1) update (via apt-get upgrade and apt-get dist-upgrade)
2) yes it was working well until the 5/13/16 update
3) n/a - I have it working now
4) n/a - I have it working now
5) n/a - I have it working now

This did no work for me because I for got to choose replacing 99-com.rules
when i did the installation.
So renamed may /etc/udev/rules.d/99-com.rules to 99-com.rules.bak then I
used a text editor to create a new 99-com.rules. I then copied the
99-com.rules from here
https://github.com/RPi-Distro/raspberrypi-sys-mods/blob/master/etc/udev/rules.d/99-com.rules
.

Every thing works now.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/raspberrypi/linux/issues/1360#issuecomment-220201230

sameting. my hardware is AM4378, software is pybluez:

root@xxx:~/pybluez/examples/simple# python sdp-browse.py all
[18142.090865] Bluetooth: hci0: Frame reassembly failed (-84)
[18142.096799] Unable to handle kernel paging request at virtual address ffffffc8
[18142.104590] pgd = c0004000
...

I can do bluetoothctl scan,but when do pair the kernel crashed.