-
Notifications
You must be signed in to change notification settings - Fork 566
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenCL on BeagleBoard X15 #102
Comments
@gtortone sorry, haven't worked on this issue this week. Been working on work-arounds for the bbgw wlan0 fun-ness. For v4.1.x, yes opencl had a lot of messages dumpped to the kernel, you can ignore them.. For the v4.1.x -> v4.4.x transition some things are still broken, and when i tested the last TI sdk for the x15, the opencl speed up was only 0.8x vs, the 3x->4x we saw in v4.1.x I've noticed quite a few opencl updates coming across the ti mailing list, so it might be working again. (just need to find a free moment) REgards, |
@gtortone there's a new build: Can you dl and test: http://software-dl.ti.com/processor-sdk-linux/esd/AM57X/latest/index_FDS.html run the opencl-mpp opencl demo, it'll compare the Dual A15's vs the DSP's If it's back in the 2x/3x speed up range, i'll start porting the stuff over again.. Regards, |
Hi, i am wondering the same the same thing. Their results are:
and
I'm not sure wether this displays an increase or decrease in speedup compared to the cpu. dgemm supports your findings of a 0.8x speedup but i'm not sure what to make of matmpy's result. -Shim edit: formatting |
commit 5cdb0ef upstream. In case USB disconnect happens at the moment transmitting workqueue is in progress the underlying interface may be gone causing a NULL pointer dereference. Add synchronization of the workqueue destruction with the detach implementation in core so that the transmitting workqueue is stopped during detach before the interfaces are removed. Fix following Oops: Unable to handle kernel NULL pointer dereference at virtual address 00000008 pgd = 9e6a802d [00000008] *pgd=00000000 Internal error: Oops: 5 [beagleboard#1] PREEMPT SMP ARM Modules linked in: nf_log_ipv4 nf_log_common xt_LOG xt_limit iptable_mangle xt_connmark xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter ip_tables x_tables usb_f_mass_storage usb_f_rndis u_ether usb_serial_simple usbserial cdc_acm brcmfmac brcmutil smsc95xx usbnet ci_hdrc_imx ci_hdrc ulpi usbmisc_imx 8250_exar 8250_pci 8250 8250_base libcomposite configfs udc_core CPU: 0 PID: 7 Comm: kworker/u8:0 Not tainted 4.19.23-00076-g03740aa-dirty beagleboard#102 Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree) Workqueue: brcmf_fws_wq brcmf_fws_dequeue_worker [brcmfmac] PC is at brcmf_txfinalize+0x34/0x90 [brcmfmac] LR is at brcmf_fws_dequeue_worker+0x218/0x33c [brcmfmac] pc : [<7f0dee64>] lr : [<7f0e4140>] psr: 60010093 sp : ee8abef0 ip : 00000000 fp : edf38000 r10: ffffffed r9 : edf38970 r8 : edf3800 r7 : edf3e970 r6 : 00000000 r5 : ede69000 r4 : 00000000 r3 : 00000a97 r2 : 00000000 r1 : 0000888e r0 : ede69000 Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment none Control: 10c5387d Table: 7d03c04a DAC: 00000051 Process kworker/u8:0 (pid: 7, stack limit = 0x24ec3e04) Stack: (0xee8abef0 to 0xee8ac000) bee0: ede69000 00000000 ed56c3e0 7f0e4140 bf00: 00000001 00000000 edf3800 edf3e99c ed56c3e0 80d03d00 edfea43a edf3e970 bf20: ee809880 ee804200 ee971100 00000000 edf3e974 00000000 ee804200 80135a70 bf40: 80d03d00 ee804218 ee809880 ee809894 ee804200 80d03d00 ee804218 ee8aa000 bf60: 00000088 80135d5c 00000000 ee829f00 ee829dc0 00000000 ee809880 80135d30 bf80: ee829f1c ee873eac 00000000 8013b1a0 ee829dc0 8013b07c 00000000 00000000 bfa0: 00000000 00000000 00000000 801010e8 00000000 00000000 00000000 00000000 bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000 [<7f0dee64>] (brcmf_txfinalize [brcmfmac]) from [<7f0e4140>] (brcmf_fws_dequeue_worker+0x218/0x33c [brcmfmac]) [<7f0e4140>] (brcmf_fws_dequeue_worker [brcmfmac]) from [<80135a70>] (process_one_work+0x138/0x3f8) [<80135a70>] (process_one_work) from [<80135d5c>] (worker_thread+0x2c/0x554) [<80135d5c>] (worker_thread) from [<8013b1a0>] (kthread+0x124/0x154) [<8013b1a0>] (kthread) from [<801010e8>] (ret_from_fork+0x14/0x2c) Exception stack(0xee8abfb0 to 0xee8abff8) bfa0: 00000000 00000000 00000000 00000000 bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 Code: e1530001 0a000007 e3560000 e1a00005 (05942008) ---[ end trace 079239dd31c86e90 ]--- Signed-off-by: Piotr Figiel <p.figiel@camlintechnologies.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Please re-open if still an issue with our current Debian images: |
Hi,
I'm trying to use OpenCL with AM57xx-EVM (BeagleBoard X15 board) and with a recent kernel (e.g. 4.4.21-ti-r45) it does not work; after loading of cmemk module each OpenCL example fails with:
root@arm:/usr/share/ti/examples/opencl/simple# ./simple
Unable to allocate OCL MSMC memory from 0x40500000
(kernel 4.4.21-ti-r45 U-Boot load am57xx-beagle-x15-revb1 device tree but I don't know if this is correct)
Reading BeagleBoard X15 wiki I realized that OpenCL needs linux kernel: 4.1.10-ti-r23/4.1.10-ti-rt-r23 or greater from the v4.1.x-ti branch then I installed 4.1.10-ti-r23 but U-Boot did not find am57xx-beagle-x15-revb1 device tree and after forced U-Boot to load am57xx-beagle-x15.dtb (I don't know if this is correct)
OpenCL examples work but sometime in dmesg i found this:
It is possible to know a working combination of kernel release and device tree to work with OpenCL without any issues ?
Thanks a lot
The text was updated successfully, but these errors were encountered: