BeagleBone Black CAN Bus
If there is no Acknowledge for a CAN packet, so this can be considered like a transmission error. I'm afraid that it can be up to the CAN implementation how to handle this situation.

If you have a single CAN device, try to use either loopback mode or set a restart time:

ip link set can0 up type can bitrate 250000 loopback on


or

ip link set can0 up type can bitrate 250000 restart-ms 100


Note: BBB 3.8.x kernel apparently has a bug in CAN implementation. Sometimes there is kernel panic caused by CAN modules:

[ 2094.561511] BUG: scheduling while atomic: cansend/1996/0x40000100
[ 2094.568140] Modules linked in: vcan can_raw can g_multi libcomposite c_can_platform c_can can_dev mt7601Usta(O)
[ 2094.568332] [&lt;c00114f1&gt;] (unwind_backtrace+0x1/0x9c) from [&lt;c04cb7bd&gt;] (__schedule_bug+0x31/0x44)
[ 2094.568388] [&lt;c04cb7bd&gt;] (__schedule_bug+0x31/0x44) from [&lt;c04d0707&gt;] (__schedule+0x4df/0x574)
[ 2094.568446] [&lt;c04d0707&gt;] (__schedule+0x4df/0x574) from [&lt;c004eafb&gt;] (__cond_resched+0x1b/0x24)
[ 2094.568496] [&lt;c004eafb&gt;] (__cond_resched+0x1b/0x24) from [&lt;c04d07fb&gt;] (_cond_resched+0x23/0x2c)
[ 2094.568549] [&lt;c04d07fb&gt;] (_cond_resched+0x23/0x2c) from [&lt;c02cdea7&gt;] (__pm_runtime_resume+0x57/0x58)
[ 2094.568619] [&lt;c02cdea7&gt;] (__pm_runtime_resume+0x57/0x58) from [&lt;bf8c00d7&gt;] (c_can_get_berr_counter+0x16/0x3c [c_can])
[ 2094.568687] [&lt;bf8c00d7&gt;] (c_can_get_berr_counter+0x16/0x3c [c_can]) from [&lt;bf8c0287&gt;] (c_can_handle_state_change+0x1e/0x100 [c_can])
[ 2094.568752] [&lt;bf8c0287&gt;] (c_can_handle_state_change+0x1e/0x100 [c_can]) from [&lt;bf8c0719&gt;] (c_can_poll+0x14c/0x608 [c_can])
[ 2094.568811] [&lt;bf8c0719&gt;] (c_can_poll+0x14c/0x608 [c_can]) from [&lt;c0426671&gt;] (net_rx_action+0x69/0x138)


Some links where you can find some information regarding this problem
https://groups.google.com/forum/#!topic/beagleboard/JL6aSRc0b7E
http://lists.openwall.net/netdev/2013/11/27/64

Try to use another version of a kernel.