Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
I found some postings about the issue on the internet at different other places, but I can't remember anymore, where it was. Many repliers stated, that it's caused by hardware or cabling. In my case, when the USB cable is too long, the issue occured. But it also occured on some specific devices without having a longer cable installed. So, I proceeded searching, and found the solution: Babble interrupts occur, when EMI (electromagnetic interference) occurs. I was able to solve my issue by inserting an actively powered USB hub into the line. But others also mentioned, that the issue can also be solved by installing a ferrite core on both sides of the USB cable, as close to the plug as possible. If you don't know, what a ferrite core is, please see here: https://www.google.com/search?q=ferrite+corenum=40tbm=ischtbo=usource=univsa=Xved=0CDoQsARqFQoTCOu63pCTh8YCFWcW2wodeUsAsgbiw=1680bih=930 If your device is powered externally, you sould also set ferrite cores onto the power cable, also as much close to the ends as you can. The ferrite cores will damp EMI to a level, where Babble interrupt error doesn't occur anymore. Proper shielding of the USB cable you're using is absolutely mandatory, to avoid interference. So I also highly recommend to use high quality cabling. 2015-06-11 7:18 GMT+02:00, Sina Chou sinacl...@gmail.com: update information 4.1.0-rc7-bone7, use usb webcam logitech c920 to take pictures. Babble interrupt issues still exist.. The following is the part of dmesg while having the issue [ 349.815873] musb-hdrc musb-hdrc.1.auto: Babble [ 349.820659] musb-hdrc: setup fifo_mode 4 [ 349.820706] musb-hdrc: 28/31 max ep, 16384/16384 memory [ 349.821331] usb 1-1: USB disconnect, device number 2 [ 349.848235] [ cut here ] [ 349.848320] WARNING: CPU: 0 PID: 1666 at fs/sysfs/group.c:224 sysfs_remove_group+0x55/0x60() [ 349.848391] sysfs group c0a3cfcc not found for kobject 'event0' [ 349.848408] Modules linked in: usb_f_acm u_serial usb_f_ecm g_multi usb_f_mass_storage usb_f_rndis u_ether libcomposite snd_usb_audio snd_hwdep snd_usbmidi_lib snd_seq_midi snd_seq_midi_event snd_rawmidi snd_pcm snd_seq snd_seq_device snd_timer evdev snd uvcvideo videobuf2_vmalloc videobuf2_memops soundcore videobuf2_core ti_am335x_adc kfifo_buf industrialio tda998x tilcdc omap_aes omap_sham ti_am335x_tsc omap_rng drm_kms_helper rng_core ti_am335x_tscadc uio_pdrv_genirq leds_gpio uio [ 349.848747] CPU: 0 PID: 1666 Comm: v4l2grab Not tainted 4.1.0-rc6-bone6 #1 [ 349.848769] Hardware name: Generic AM33XX (Flattened Device Tree) [ 349.848850] [c0012741] (unwind_backtrace) from [c0010941] (show_stack+0x11/0x14) [ 349.848917] [c0010941] (show_stack) from [c002cfab] (warn_slowpath_common+0x57/0x84) [ 349.849026] [c002cfab] (warn_slowpath_common) from [c002d043] (warn_slowpath_fmt+0x23/0x2c) [ 349.849079] [c002d043] (warn_slowpath_fmt) from [c01336a5] (sysfs_remove_group+0x55/0x60) [ 349.849133] [c01336a5] (sysfs_remove_group) from [c03cd4e9] (device_del+0x2d/0x16c) [ 349.849204] [c03cd4e9] (device_del) from [bf8e20df] (evdev_disconnect+0x16/0x3c [evdev]) [ 349.849286] [bf8e20df] (evdev_disconnect [evdev]) from [c0475ec1] (__input_unregister_device+0x65/0xe4) [ 349.849329] [c0475ec1] (__input_unregister_device) from [c0476033] (input_unregister_device+0x2f/0x58) [ 349.849469] [c0476033] (input_unregister_device) from [bf8bb2c5] (uvc_status_cleanup+0x2c/0x30 [uvcvideo]) [ 349.849602] [bf8bb2c5] (uvc_status_cleanup [uvcvideo]) from [bf8b41e3] (uvc_delete+0xe/0xd0 [uvcvideo]) [ 349.849695] [bf8b41e3] (uvc_delete [uvcvideo]) from [bf8b436f] (uvc_release+0x2e/0x30 [uvcvideo]) [ 349.849771] [bf8b436f] (uvc_release [uvcvideo]) from [c049cbfd] (v4l2_device_release+0x89/0xac) [ 349.849814] [c049cbfd] (v4l2_device_release) from [c03ccf9f] (device_release+0x23/0x60) [ 349.849860] [c03ccf9f] (device_release) from [c033caed] (kobject_cleanup+0x51/0x11c) [ 349.849899] [c033caed] (kobject_cleanup) from [c049bab3] (v4l2_release+0x37/0x54) [ 349.849938] [c049bab3] (v4l2_release) from [c00ee631] (__fput+0x65/0x144) [ 349.849994] [c00ee631] (__fput) from [c003d561] (task_work_run+0x69/0x90) [ 349.850036] [c003d561] (task_work_run) from [c002e58d] (do_exit+0x22d/0x6dc) [ 349.850071] [c002e58d] (do_exit) from [c002ea91] (do_group_exit+0x2d/0x6c) [ 349.850108] [c002ea91] (do_group_exit) from [c002eae1] (__wake_up_parent+0x1/0x18) [ 349.850131] ---[ end trace e9fbe6cf6b19f635 ]--- [ 349.859582] [ cut here ] [ 349.859658] WARNING: CPU: 0 PID: 1666 at fs/sysfs/group.c:224 sysfs_remove_group+0x55/0x60() [ 349.859681] sysfs group c0a3cfcc not found for kobject 'input0' [ 349.859699] Modules linked in: usb_f_acm u_serial usb_f_ecm g_multi usb_f_mass_storage usb_f_rndis u_ether libcomposite snd_usb_audio snd_hwdep snd_usbmidi_lib snd_seq_midi snd_seq_midi_event snd_rawmidi snd_pcm snd_seq snd_seq_device
[beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
update information 4.1.0-rc7-bone7, use usb webcam logitech c920 to take pictures. Babble interrupt issues still exist.. The following is the part of dmesg while having the issue [ 349.815873] musb-hdrc musb-hdrc.1.auto: Babble [ 349.820659] musb-hdrc: setup fifo_mode 4 [ 349.820706] musb-hdrc: 28/31 max ep, 16384/16384 memory [ 349.821331] usb 1-1: USB disconnect, device number 2 [ 349.848235] [ cut here ] [ 349.848320] WARNING: CPU: 0 PID: 1666 at fs/sysfs/group.c:224 sysfs_remove_group+0x55/0x60() [ 349.848391] sysfs group c0a3cfcc not found for kobject 'event0' [ 349.848408] Modules linked in: usb_f_acm u_serial usb_f_ecm g_multi usb_f_mass_storage usb_f_rndis u_ether libcomposite snd_usb_audio snd_hwdep snd_usbmidi_lib snd_seq_midi snd_seq_midi_event snd_rawmidi snd_pcm snd_seq snd_seq_device snd_timer evdev snd uvcvideo videobuf2_vmalloc videobuf2_memops soundcore videobuf2_core ti_am335x_adc kfifo_buf industrialio tda998x tilcdc omap_aes omap_sham ti_am335x_tsc omap_rng drm_kms_helper rng_core ti_am335x_tscadc uio_pdrv_genirq leds_gpio uio [ 349.848747] CPU: 0 PID: 1666 Comm: v4l2grab Not tainted 4.1.0-rc6-bone6 #1 [ 349.848769] Hardware name: Generic AM33XX (Flattened Device Tree) [ 349.848850] [c0012741] (unwind_backtrace) from [c0010941] (show_stack+0x11/0x14) [ 349.848917] [c0010941] (show_stack) from [c002cfab] (warn_slowpath_common+0x57/0x84) [ 349.849026] [c002cfab] (warn_slowpath_common) from [c002d043] (warn_slowpath_fmt+0x23/0x2c) [ 349.849079] [c002d043] (warn_slowpath_fmt) from [c01336a5] (sysfs_remove_group+0x55/0x60) [ 349.849133] [c01336a5] (sysfs_remove_group) from [c03cd4e9] (device_del+0x2d/0x16c) [ 349.849204] [c03cd4e9] (device_del) from [bf8e20df] (evdev_disconnect+0x16/0x3c [evdev]) [ 349.849286] [bf8e20df] (evdev_disconnect [evdev]) from [c0475ec1] (__input_unregister_device+0x65/0xe4) [ 349.849329] [c0475ec1] (__input_unregister_device) from [c0476033] (input_unregister_device+0x2f/0x58) [ 349.849469] [c0476033] (input_unregister_device) from [bf8bb2c5] (uvc_status_cleanup+0x2c/0x30 [uvcvideo]) [ 349.849602] [bf8bb2c5] (uvc_status_cleanup [uvcvideo]) from [bf8b41e3] (uvc_delete+0xe/0xd0 [uvcvideo]) [ 349.849695] [bf8b41e3] (uvc_delete [uvcvideo]) from [bf8b436f] (uvc_release+0x2e/0x30 [uvcvideo]) [ 349.849771] [bf8b436f] (uvc_release [uvcvideo]) from [c049cbfd] (v4l2_device_release+0x89/0xac) [ 349.849814] [c049cbfd] (v4l2_device_release) from [c03ccf9f] (device_release+0x23/0x60) [ 349.849860] [c03ccf9f] (device_release) from [c033caed] (kobject_cleanup+0x51/0x11c) [ 349.849899] [c033caed] (kobject_cleanup) from [c049bab3] (v4l2_release+0x37/0x54) [ 349.849938] [c049bab3] (v4l2_release) from [c00ee631] (__fput+0x65/0x144) [ 349.849994] [c00ee631] (__fput) from [c003d561] (task_work_run+0x69/0x90) [ 349.850036] [c003d561] (task_work_run) from [c002e58d] (do_exit+0x22d/0x6dc) [ 349.850071] [c002e58d] (do_exit) from [c002ea91] (do_group_exit+0x2d/0x6c) [ 349.850108] [c002ea91] (do_group_exit) from [c002eae1] (__wake_up_parent+0x1/0x18) [ 349.850131] ---[ end trace e9fbe6cf6b19f635 ]--- [ 349.859582] [ cut here ] [ 349.859658] WARNING: CPU: 0 PID: 1666 at fs/sysfs/group.c:224 sysfs_remove_group+0x55/0x60() [ 349.859681] sysfs group c0a3cfcc not found for kobject 'input0' [ 349.859699] Modules linked in: usb_f_acm u_serial usb_f_ecm g_multi usb_f_mass_storage usb_f_rndis u_ether libcomposite snd_usb_audio snd_hwdep snd_usbmidi_lib snd_seq_midi snd_seq_midi_event snd_rawmidi snd_pcm snd_seq snd_seq_device snd_timer evdev snd uvcvideo videobuf2_vmalloc videobuf2_memops soundcore videobuf2_core ti_am335x_adc kfifo_buf industrialio tda998x tilcdc omap_aes omap_sham ti_am335x_tsc omap_rng drm_kms_helper rng_core ti_am335x_tscadc uio_pdrv_genirq leds_gpio uio [ 349.859968] CPU: 0 PID: 1666 Comm: v4l2grab Tainted: GW 4.1.0-rc6-bone6 #1 [ 349.859989] Hardware name: Generic AM33XX (Flattened Device Tree) [ 349.860066] [c0012741] (unwind_backtrace) from [c0010941] (show_stack+0x11/0x14) [ 349.860131] [c0010941] (show_stack) from [c002cfab] (warn_slowpath_common+0x57/0x84) [ 349.860173] [c002cfab] (warn_slowpath_common) from [c002d043] (warn_slowpath_fmt+0x23/0x2c) [ 349.860212] [c002d043] (warn_slowpath_fmt) from [c01336a5] (sysfs_remove_group+0x55/0x60) [ 349.860264] [c01336a5] (sysfs_remove_group) from [c03cd4e9] (device_del+0x2d/0x16c) [ 349.860309] [c03cd4e9] (device_del) from [c0476033] (input_unregister_device+0x2f/0x58) [ 349.860503] [c0476033] (input_unregister_device) from [bf8bb2c5] (uvc_status_cleanup+0x2c/0x30 [uvcvideo]) [ 349.860704] [bf8bb2c5] (uvc_status_cleanup [uvcvideo]) from [bf8b41e3] (uvc_delete+0xe/0xd0 [uvcvideo]) [ 349.860797] [bf8b41e3] (uvc_delete [uvcvideo]) from [bf8b436f] (uvc_release+0x2e/0x30 [uvcvideo]) [ 349.860925] [bf8b436f] (uvc_release [uvcvideo]) from [c049cbfd] (v4l2_device_release+0x89/0xac) [
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Hi there. My experience is different, namely that power on the hub is not essential to alleviate babble interrupts. I've seen lots of babble using a specific device (GNS-5890 ADS-B receiver from http://www.gns-gmbh.com/index.php?id=238L=1) when hooked up directly to the BBB USB host port, but adding a non-powered hub or a non-powered USB-extender between device and host makes the babble interrupts that lock up the musb controller go away. Babble does still occur according to the kernel log but apparently no unrecoverable ones. There has been some development on the musb kernel driver after the one referenced below by Ravi Babu, particularly George Cherian has done a series of patches implementing use of new babble prevention/diagnostic features in recent silicon revisions that seem to have fixed a lot of issues. The latest v7 of his Add support for SW babble Control series is at http://thread.gmane.org/gmane.linux.usb.general/111365. There is a lot of background information about babble in the threads of these patches for the curious and courageous of you ;). How and if the patch has progressed into mainline or BBB kernels I havn't checked (but my guess is they haven't at all), and I haven't come around testingit myself yet because our production systems run fine with the hub-workaround. Mikkel Den onsdag den 21. januar 2015 kl. 08.30.19 UTC+1 skrev zoli1...@googlemail.com: I can confirm, that the issue can be solved by inserting an active USB hub (externally powered). Am Freitag, 12. Dezember 2014 14:52:50 UTC+1 schrieb vervaeke...@gmail.com : Try to use an USB hub with external power. This solved my problem. On Saturday, August 9, 2014 4:38:14 AM UTC+2, shad...@gmail.com wrote: Anyone know about the patch referenced here? Or any other workaround to make USB usable on BBB? http://comments.gmane.org/gmane.linux.usb.general/87138 http://www.google.com/url?q=http%3A%2F%2Fcomments.gmane.org%2Fgmane.linux.usb.general%2F87138sa=Dsntz=1usg=AFQjCNE5-dk-0FfHzNfrrjrTQdcE7WfpCQ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Anyone know about the patch referenced here? Or any other workaround to make USB usable on BBB? http://comments.gmane.org/gmane.linux.usb.general/87138 -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
I've seen the babble interrupt on all of the kernels I have tried. 3.8, 3.12, and 3.14. I have also seen a lot of vbus errors during the boot process. Could the heart of the problem be the fact that the power filter capacitor is of lower capacitance than is recommended by the USB 2.0 spec? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Do you by any chance know in what revision the babble interrupt problem was fixed? Was it only fixed in 3.12 or also in other trees (e.g. 3.8)? Op dinsdag 13 mei 2014 17:19:42 UTC+2 schreef cody: What version of the 3.12 kernel do you have? The latest version of the 3.12 kernel should have a patch that fixes that problem. On Tue, May 13, 2014 at 8:04 AM, Renato Riolino renato.n...@gmail.com javascript: wrote: Hi! I'm having this same issue with my BeagleBone Black. I have an USB keyboard connected direct on the beagle's usb port and I'm using ubuntu 13.04 with kernel 3.12. After some random amount of time, the keyboard stop working and the only thing I see on dmesg is: CAUTION: musb: Babble Interrupt Occurred If I remove keyboard, nothing appears on dmesg and even with the keyboard removed, if I do a lsusb it still shows up as been connected. The only way to get it working again is doing a full reboot. I've already tried to do things like: echo 'on' /sys/bus/usb/devices/usb1/power/control on rc.local and to make a script that keeps on a infinite loop doing a cat on /proc/bus/usb/xxx/yyy, but the problem persist. Thanks Renato Em sábado, 31 de agosto de 2013 12h42min09s UTC-3, jez...@gmail.com escreveu: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Hi! I'm having this same issue with my BeagleBone Black. I have an USB keyboard connected direct on the beagle's usb port and I'm using ubuntu 13.04 with kernel 3.12. After some random amount of time, the keyboard stop working and the only thing I see on dmesg is: CAUTION: musb: Babble Interrupt Occurred If I remove keyboard, nothing appears on dmesg and even with the keyboard removed, if I do a lsusb it still shows up as been connected. The only way to get it working again is doing a full reboot. I've already tried to do things like: echo 'on' /sys/bus/usb/devices/usb1/power/control on rc.local and to make a script that keeps on a infinite loop doing a cat on /proc/bus/usb/xxx/yyy, but the problem persist. Thanks Renato Em sábado, 31 de agosto de 2013 12h42min09s UTC-3, jez...@gmail.com escreveu: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
My kernel is: 3.12.3-00082-g6cf1f10-dirty I tried kernel 3.13 and 3.14 but they didn't worked for me because I need capemanager. Thanks Em terça-feira, 13 de maio de 2014 12h19min42s UTC-3, cody escreveu: What version of the 3.12 kernel do you have? The latest version of the 3.12 kernel should have a patch that fixes that problem. On Tue, May 13, 2014 at 8:04 AM, Renato Riolino renato.n...@gmail.comjavascript: wrote: Hi! I'm having this same issue with my BeagleBone Black. I have an USB keyboard connected direct on the beagle's usb port and I'm using ubuntu 13.04 with kernel 3.12. After some random amount of time, the keyboard stop working and the only thing I see on dmesg is: CAUTION: musb: Babble Interrupt Occurred If I remove keyboard, nothing appears on dmesg and even with the keyboard removed, if I do a lsusb it still shows up as been connected. The only way to get it working again is doing a full reboot. I've already tried to do things like: echo 'on' /sys/bus/usb/devices/usb1/power/control on rc.local and to make a script that keeps on a infinite loop doing a cat on /proc/bus/usb/xxx/yyy, but the problem persist. Thanks Renato Em sábado, 31 de agosto de 2013 12h42min09s UTC-3, jez...@gmail.comescreveu: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
On Tue, May 13, 2014 at 11:38 AM, Renato Riolino renato.neocor...@gmail.com wrote: My kernel is: 3.12.3-00082-g6cf1f10-dirty I tried kernel 3.13 and 3.14 but they didn't worked for me because I need capemanager. No one is really support the capemgr in v3.12.x, nor does it really work. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Very strange, because I have capemanager working here: ubuntu@arm:~$ uname -a Linux arm 3.12.3-00082-g6cf1f10-dirty #1 SMP Fri Dec 6 11:44:27 BRST 2013 armv7l armv7l armv7l GNU/Linux ubuntu@arm:~$ cat /sys/devices/bone_capemgr.6/slots 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 5: ff:P-O-L Override Board Name,00A0,Override Manuf,NEO-UART0 6: ff:P-O-L Override Board Name,00A0,Override Manuf,NEO-UART1-485 7: ff:P-O-L Override Board Name,00A0,Override Manuf,NEO-UART2 8: ff:P-O-L Override Board Name,00A0,Override Manuf,NEO-UART3 9: ff:P-O-L Override Board Name,00A0,Override Manuf,NEO-UART4 10: ff:P-O-L Override Board Name,00A0,Override Manuf,NEO-UART5 ubuntu@arm:~$ dmesg | grep capemgr [0.00] Kernel command line: console= fixrtc capemgr.enable_partno=NEO-UART0,NEO-UART1-485,NEO-UART2,NEO-UART3,NEO-UART4,NEO-UART5 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait [0.184969] bone-capemgr bone_capemgr.6: Baseboard: 'A335BNLT,0A5C,3313BBBK0501' [0.184996] bone-capemgr bone_capemgr.6: compatible-baseboard=ti,beaglebone-black [0.222939] bone-capemgr bone_capemgr.6: slot #0: No cape found [0.262936] bone-capemgr bone_capemgr.6: slot #1: No cape found [0.302934] bone-capemgr bone_capemgr.6: slot #2: No cape found [0.342933] bone-capemgr bone_capemgr.6: slot #3: No cape found [0.342977] bone-capemgr bone_capemgr.6: slot #4: specific override [0.343004] bone-capemgr bone_capemgr.6: bone: Using override eeprom data at slot 4 [0.343020] bone-capemgr bone_capemgr.6: slot #4: 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G' [0.343102] bone-capemgr bone_capemgr.6: enabled_partno part_number 'NEO-UART0', version 'N/A' [0.343114] bone-capemgr bone_capemgr.6: slot #5: generic override [0.343126] bone-capemgr bone_capemgr.6: bone: Using override eeprom data at slot 5 [0.343141] bone-capemgr bone_capemgr.6: slot #5: 'Override Board Name,00A0,Override Manuf,NEO-UART0' [0.343207] bone-capemgr bone_capemgr.6: enabled_partno part_number 'NEO-UART1-485', version 'N/A' [0.343220] bone-capemgr bone_capemgr.6: slot #6: generic override [0.343231] bone-capemgr bone_capemgr.6: bone: Using override eeprom data at slot 6 [0.343247] bone-capemgr bone_capemgr.6: slot #6: 'Override Board Name,00A0,Override Manuf,NEO-UART1-485' [0.343307] bone-capemgr bone_capemgr.6: enabled_partno part_number 'NEO-UART2', version 'N/A' [0.343320] bone-capemgr bone_capemgr.6: slot #7: generic override [0.343331] bone-capemgr bone_capemgr.6: bone: Using override eeprom data at slot 7 [0.343346] bone-capemgr bone_capemgr.6: slot #7: 'Override Board Name,00A0,Override Manuf,NEO-UART2' [0.343414] bone-capemgr bone_capemgr.6: enabled_partno part_number 'NEO-UART3', version 'N/A' [0.343429] bone-capemgr bone_capemgr.6: slot #8: generic override [0.343442] bone-capemgr bone_capemgr.6: bone: Using override eeprom data at slot 8 [0.343457] bone-capemgr bone_capemgr.6: slot #8: 'Override Board Name,00A0,Override Manuf,NEO-UART3' [0.343529] bone-capemgr bone_capemgr.6: enabled_partno part_number 'NEO-UART4', version 'N/A' [0.343542] bone-capemgr bone_capemgr.6: slot #9: generic override [0.343554] bone-capemgr bone_capemgr.6: bone: Using override eeprom data at slot 9 [0.343569] bone-capemgr bone_capemgr.6: slot #9: 'Override Board Name,00A0,Override Manuf,NEO-UART4' [0.343630] bone-capemgr bone_capemgr.6: enabled_partno part_number 'NEO-UART5', version 'N/A' [0.343643] bone-capemgr bone_capemgr.6: slot #10: generic override [0.343655] bone-capemgr bone_capemgr.6: bone: Using override eeprom data at slot 10 [0.343670] bone-capemgr bone_capemgr.6: slot #10: 'Override Board Name,00A0,Override Manuf,NEO-UART5' [0.344028] bone-capemgr bone_capemgr.6: loader: before slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [0.344044] bone-capemgr bone_capemgr.6: loader: check slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [0.344128] bone-capemgr bone_capemgr.6: loader: before slot-5 NEO-UART0:00A0 (prio 0) [0.344141] bone-capemgr bone_capemgr.6: loader: check slot-5 NEO-UART0:00A0 (prio 0) [0.344222] bone-capemgr bone_capemgr.6: loader: before slot-6 NEO-UART1-485:00A0 (prio 0) [0.344236] bone-capemgr bone_capemgr.6: loader: check slot-6 NEO-UART1-485:00A0 (prio 0) [0.344315] bone-capemgr bone_capemgr.6: loader: before slot-7 NEO-UART2:00A0 (prio 0) [0.344330] bone-capemgr bone_capemgr.6: loader: check slot-7 NEO-UART2:00A0 (prio 0) [0.344405] bone-capemgr bone_capemgr.6: loader: before slot-8 NEO-UART3:00A0 (prio 0) [0.344418] bone-capemgr bone_capemgr.6: loader: check slot-8 NEO-UART3:00A0 (prio 0) [0.344496] bone-capemgr bone_capemgr.6: loader: before slot-9 NEO-UART4:00A0 (prio 0) [0.344509] bone-capemgr bone_capemgr.6: loader: check slot-9 NEO-UART4:00A0 (prio 0) [0.344548] bone-capemgr bone_capemgr.6: initialized OK. [0.347060] bone-capemgr
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
On Tue, May 13, 2014 at 12:06 PM, Renato Riolino renato.neocor...@gmail.com wrote: Very strange, because I have capemanager working here: It works fine with the usarts, but lcd/spi/pwm it blows up pretty quickly.. If all you need is the usarts, we have a custom dtb for v3.14.x for you. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
I use a LCD connected via gpio ( setting the gpio pins thru /sys/class/gpio ) and a DS1307 realtime clock via i2c. Do they work too on kernel 3.14? Could you point me to the 3.14 kernel and the custom dtb for usart? I need all usarts availables and UART1 needs to be 485. []'s Renato Em terça-feira, 13 de maio de 2014 14h08min49s UTC-3, RobertCNelson escreveu: On Tue, May 13, 2014 at 12:06 PM, Renato Riolino renato.n...@gmail.com javascript: wrote: Very strange, because I have capemanager working here: It works fine with the usarts, but lcd/spi/pwm it blows up pretty quickly.. If all you need is the usarts, we have a custom dtb for v3.14.x for you. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
On Tue, May 13, 2014 at 12:20 PM, Renato Riolino
renato.neocor...@gmail.com wrote:
I use a LCD connected via gpio ( setting the gpio pins thru /sys/class/gpio
) and a DS1307 realtime clock via i2c.
Do they work too on kernel 3.14? Could you point me to the 3.14 kernel and
the custom dtb for usart? I need all usarts availables and UART1 needs to
be 485.
So the best i can do today on 3.14/3.15 would be:
#include am335x-boneblack.dts
uart1 {
pinctrl-names = default;
pinctrl-0 = uart1_pins;
status = okay;
};
uart2 {
pinctrl-names = default;
pinctrl-0 = uart2_pins;
status = okay;
};
uart4 {
pinctrl-names = default;
pinctrl-0 = uart4_pins;
status = okay;
};
So 2/5 of what you need, so don't switch yet.
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Ulf, does your kernel patch interrupt data streams? In other words, for example, if I'm running a webcam and I hotplug another device, will data transfers from the webcam be affected? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
The following codes can workaround that... #!/bin/sh echo on /sys/bus/usb/devices/usb1/power/control while [ 1 ]; do cat /dev/bus/usb/001/001 /dev/null sleep 5 cat /dev/bus/usb/001/002 /dev/null sleep 5 done On Saturday, August 31, 2013 11:42:09 PM UTC+8, jez...@gmail.com wrote: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
I am getting this same issue on my new BBB running ubuntu saucy 13.10. My FTDI peripheral loads up and works fine for ahile, but then the babble interrupt inevitably comes, and nothing I do can allow the system to recover. Is there anything I can change to be able to recover from this without hard rebooting the system (Only thing that fixes it right now)? I have also tried these commands where usb 1-1 is the port in question on my system: echo '1-1' |sudo tee /sys/bus/usb/drivers/usb/unbind echo '1-1' |sudo tee /sys/bus/usb/drivers/usb/bind and it seems to be trying to reset, but it fails with error -110. Any ideas what that might be? Transcript of dmesg when I try to debug it and reset the usb port after Babble Interrupt: [12624.364551] musb_host_rx 1717: Rx interrupt with no errors or packet! [12633.120879] CAUTION: musb: Babble Interrupt Occurred [42284.311147] usb 1-1: unregistering interface 1-1:1.0 [42284.318828] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [42284.319153] ftdi_sio 1-1:1.0: device disconnected [42284.319505] usb 1-1: usb_disable_device nuking non-ep0 URBs [42289.318728] usb 1-1: tee timed out on ep0out len=0/0 [42294.243524] usb 1-1: usb_probe_device [42294.243594] usb 1-1: configuration #1 chosen from 1 choice [42299.242612] usb 1-1: tee timed out on ep0out len=0/0 [42299.242711] usb 1-1: can't set config #1, error -110 On Saturday, August 31, 2013 8:42:09 AM UTC-7, jez...@gmail.com wrote: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Den tisdagen den 24:e december 2013 kl. 01:03:16 UTC+1 skrev Brent: Ok, got it. I need to contribute to try it out. Here is my problem, and I would like to hear if this solves it. I have a hub that uses the SMSC 2512 hub chip (USB2512QFN36). Mass storage devices work as long as it's inserted at power up. Any hot plugging after boot will not work. Does your kernel fix this problem? What I find with the standard kernel, is that if You have a hub inserted at boot time, you can hot-plug stuff using the hub. If you remove the hub then you have to reset the device. If you have a device inserted at boot, it is detected and is functional. If you remove it after the boot and reinsert it, it is no longer detected. For some devices, removal will crash the kernel within a minute. With my patched kernel, I can remove hub and / or devices and have them be detected and functional after boot, and can do this multiple times. Tested with a mouse, keyboard, USB Serial and Hub. Also, I have some other items in the kernel that I need enabled. If I contribute $50 or $125 I only get whatever you built into your kernel... right? Could I give you my .config and you build it? My idea was $50 will get you a root file system without source. $100 will get you the rootfs, and then you get an Angstrom layer which builds the kernel with the patches after the end of the campaign. You can start with the binary, and if you want source, chip in another $100 later, but this will be more expensive than getting the $100 perk. Obviously, once someone get the source, they have every right to publish it according to the GPL, including the right not to ship it. I will proably do that myself at some stage, so the perks essentially buys you time. The $125 is my hourly rate for any extra work, so you need to select an option above, and then an additional $125. 1 extra hour should be sufficient for rebuilding the kernel. On Mon, Dec 23, 2013 at 6:33 PM, APRichelieu apric...@gmail.com wrote: Den måndagen den 23:e december 2013 kl. 20:26:20 UTC+1 skrev Brent: Where do I go to get Ulf's kernel? I would like to test but I don't know where to look. Is there a patch somewhere that I missed? Check The http://igg.me link in your post. On Monday, December 9, 2013 5:57:56 PM UTC-5, bko...@scanimetrics.com wrote: I've also put in $125 and must say that I haven't had any troubles since using Ulf's kernel. Thanks Ulf On Monday, December 2, 2013 1:53:39 PM UTC-7, Philippe Laurent wrote: I've ponied up for the $125 donation. Gotta have this running right. On Mon, Dec 2, 2013 at 7:23 AM, APRichelieu apric...@gmail.com wrote: Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? I set up a crowd-funding project on http://igg.me/at/eMagii/x/5581172 for people that wants to have USB host hot-plugging on the Beaglebone Black -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -brent -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
On Dec 24, 2013 2:04 AM, APRichelieu aprichel...@gmail.com wrote: Den tisdagen den 24:e december 2013 kl. 01:03:16 UTC+1 skrev Brent: Ok, got it. I need to contribute to try it out. Here is my problem, and I would like to hear if this solves it. I have a hub that uses the SMSC 2512 hub chip (USB2512QFN36). Mass storage devices work as long as it's inserted at power up. Any hot plugging after boot will not work. Does your kernel fix this problem? What I find with the standard kernel, is that if You have a hub inserted at boot time, you can hot-plug stuff using the hub. If you remove the hub then you have to reset the device. If you have a device inserted at boot, it is detected and is functional. If you remove it after the boot and reinsert it, it is no longer detected. For some devices, removal will crash the kernel within a minute. With my patched kernel, I can remove hub and / or devices and have them be detected and functional after boot, and can do this multiple times. Tested with a mouse, keyboard, USB Serial and Hub. Also, I have some other items in the kernel that I need enabled. If I contribute $50 or $125 I only get whatever you built into your kernel... right? Could I give you my .config and you build it? My idea was $50 will get you a root file system without source. 'Without source' go read the GPL again... $100 will get you the rootfs, and then you get an Angstrom layer which builds the kernel with the patches after the end of the campaign. You can start with the binary, and if you want source, chip in another $100 later, but this will be more expensive than getting the $100 perk. Obviously, once someone get the source, they have every right to publish it according to the GPL, including the right not to ship it. I will proably do that myself at some stage, so the perks essentially buys you time. The $125 is my hourly rate for any extra work, so you need to select an option above, and then an additional $125. 1 extra hour should be sufficient for rebuilding the kernel. On Mon, Dec 23, 2013 at 6:33 PM, APRichelieu apric...@gmail.com wrote: Den måndagen den 23:e december 2013 kl. 20:26:20 UTC+1 skrev Brent: Where do I go to get Ulf's kernel? I would like to test but I don't know where to look. Is there a patch somewhere that I missed? Check The http://igg.me link in your post. On Monday, December 9, 2013 5:57:56 PM UTC-5, bko...@scanimetrics.comwrote: I've also put in $125 and must say that I haven't had any troubles since using Ulf's kernel. Thanks Ulf On Monday, December 2, 2013 1:53:39 PM UTC-7, Philippe Laurent wrote: I've ponied up for the $125 donation. Gotta have this running right. On Mon, Dec 2, 2013 at 7:23 AM, APRichelieu apric...@gmail.com wrote: Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? I set up a crowd-funding project on http://igg.me/at/eMagii/x/5581172 for people that wants to have USB host hot-plugging on the Beaglebone Black -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -brent -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Den tisdagen den 24:e december 2013 kl. 14:18:26 UTC+1 skrev RobertCNelson: On Dec 24, 2013 2:04 AM, APRichelieu apric...@gmail.com wrote: Den tisdagen den 24:e december 2013 kl. 01:03:16 UTC+1 skrev Brent: Ok, got it. I need to contribute to try it out. Here is my problem, and I would like to hear if this solves it. I have a hub that uses the SMSC 2512 hub chip (USB2512QFN36). Mass storage devices work as long as it's inserted at power up. Any hot plugging after boot will not work. Does your kernel fix this problem? What I find with the standard kernel, is that if You have a hub inserted at boot time, you can hot-plug stuff using the hub. If you remove the hub then you have to reset the device. If you have a device inserted at boot, it is detected and is functional. If you remove it after the boot and reinsert it, it is no longer detected. For some devices, removal will crash the kernel within a minute. With my patched kernel, I can remove hub and / or devices and have them be detected and functional after boot, and can do this multiple times. Tested with a mouse, keyboard, USB Serial and Hub. Also, I have some other items in the kernel that I need enabled. If I contribute $50 or $125 I only get whatever you built into your kernel... right? Could I give you my .config and you build it? My idea was $50 will get you a root file system without source. 'Without source' go read the GPL again... A lot of products ship equipment with binaries only, but they must make an offer to ship the source to anyone receiving a binary as well, which I do. It is possible to charge for both binaries and sources according to the GPL. The amount is up to the vendor. There is actually a possible violation of the GPL since you should not charge more for the source code, than for the binary. Only discovered tt fter the campaign was set up and if anyone complains, I will settle that directly in a GPL compliant way. Cannot change the deal right now, due to the rules of IndieGoGo. Anyway, if I release the source after the campaign, then that settles everything. $100 will get you the rootfs, and then you get an Angstrom layer which builds the kernel with the patches after the end of the campaign. You can start with the binary, and if you want source, chip in another $100 later, but this will be more expensive than getting the $100 perk. Obviously, once someone get the source, they have every right to publish it according to the GPL, including the right not to ship it. I will proably do that myself at some stage, so the perks essentially buys you time. The $125 is my hourly rate for any extra work, so you need to select an option above, and then an additional $125. 1 extra hour should be sufficient for rebuilding the kernel. On Mon, Dec 23, 2013 at 6:33 PM, APRichelieu apric...@gmail.com wrote: Den måndagen den 23:e december 2013 kl. 20:26:20 UTC+1 skrev Brent: Where do I go to get Ulf's kernel? I would like to test but I don't know where to look. Is there a patch somewhere that I missed? Check The http://igg.me link in your post. On Monday, December 9, 2013 5:57:56 PM UTC-5, bko...@scanimetrics.com wrote: I've also put in $125 and must say that I haven't had any troubles since using Ulf's kernel. Thanks Ulf On Monday, December 2, 2013 1:53:39 PM UTC-7, Philippe Laurent wrote: I've ponied up for the $125 donation. Gotta have this running right. On Mon, Dec 2, 2013 at 7:23 AM, APRichelieu apric...@gmail.com wrote: Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? I set up a crowd-funding project on http://igg.me/at/eMagii/x/5581172 for people that wants to have USB host hot-plugging on the Beaglebone Black
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Den tisdagen den 24:e december 2013 kl. 17:42:02 UTC+1 skrev Brent: I don't have any problem with your hourly rate, but I'm not confident your patched kernel will fix my problem. Here's why... I bought the SMSC evaluation kit for the 2512 chip that supports two downstream ports. I plug it into the BBB and it recognizes it. Any mass storage device that I have plugged in at boot works just fine. If I unplug the device and plug it back in to the hub while running, I get the Babble Interrupt error. The babble Interrupt may still occur, but so far the devices still seems to be detected on a patched kernel. Before sending anything, I should probably test locally. If it doesnt work, then there may be other things that need to change in the driver. If it does work, I would be happy to test your devkit. Live in Stockholm, Sweden. I've read that devices plugged into hubs work just fine, but it's definitely not the case for me and the SMSC 2512 chip. Where are you located at? I'm tempted to send you one of my SMSC evaluation kits and have you try it on your end. On Tue, Dec 24, 2013 at 3:04 AM, APRichelieu apric...@gmail.com wrote: Den tisdagen den 24:e december 2013 kl. 01:03:16 UTC+1 skrev Brent: Ok, got it. I need to contribute to try it out. Here is my problem, and I would like to hear if this solves it. I have a hub that uses the SMSC 2512 hub chip (USB2512QFN36). Mass storage devices work as long as it's inserted at power up. Any hot plugging after boot will not work. Does your kernel fix this problem? What I find with the standard kernel, is that if You have a hub inserted at boot time, you can hot-plug stuff using the hub. If you remove the hub then you have to reset the device. If you have a device inserted at boot, it is detected and is functional. If you remove it after the boot and reinsert it, it is no longer detected. For some devices, removal will crash the kernel within a minute. With my patched kernel, I can remove hub and / or devices and have them be detected and functional after boot, and can do this multiple times. Tested with a mouse, keyboard, USB Serial and Hub. Also, I have some other items in the kernel that I need enabled. If I contribute $50 or $125 I only get whatever you built into your kernel... right? Could I give you my .config and you build it? My idea was $50 will get you a root file system without source. $100 will get you the rootfs, and then you get an Angstrom layer which builds the kernel with the patches after the end of the campaign. You can start with the binary, and if you want source, chip in another $100 later, but this will be more expensive than getting the $100 perk. Obviously, once someone get the source, they have every right to publish it according to the GPL, including the right not to ship it. I will proably do that myself at some stage, so the perks essentially buys you time. The $125 is my hourly rate for any extra work, so you need to select an option above, and then an additional $125. 1 extra hour should be sufficient for rebuilding the kernel. On Mon, Dec 23, 2013 at 6:33 PM, APRichelieu apric...@gmail.com wrote: Den måndagen den 23:e december 2013 kl. 20:26:20 UTC+1 skrev Brent: Where do I go to get Ulf's kernel? I would like to test but I don't know where to look. Is there a patch somewhere that I missed? Check The http://igg.me link in your post. On Monday, December 9, 2013 5:57:56 PM UTC-5, bko...@scanimetrics.com wrote: I've also put in $125 and must say that I haven't had any troubles since using Ulf's kernel. Thanks Ulf On Monday, December 2, 2013 1:53:39 PM UTC-7, Philippe Laurent wrote: I've ponied up for the $125 donation. Gotta have this running right. On Mon, Dec 2, 2013 at 7:23 AM, APRichelieu apric...@gmail.com wrote: Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? I set up a crowd-funding project
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Where do I go to get Ulf's kernel? I would like to test but I don't know where to look. Is there a patch somewhere that I missed? On Monday, December 9, 2013 5:57:56 PM UTC-5, bko...@scanimetrics.com wrote: I've also put in $125 and must say that I haven't had any troubles since using Ulf's kernel. Thanks Ulf On Monday, December 2, 2013 1:53:39 PM UTC-7, Philippe Laurent wrote: I've ponied up for the $125 donation. Gotta have this running right. On Mon, Dec 2, 2013 at 7:23 AM, APRichelieu apric...@gmail.com wrote: Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? I set up a crowd-funding project on http://igg.me/at/eMagii/x/5581172 for people that wants to have USB host hot-plugging on the Beaglebone Black -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Den måndagen den 23:e december 2013 kl. 20:26:20 UTC+1 skrev Brent: Where do I go to get Ulf's kernel? I would like to test but I don't know where to look. Is there a patch somewhere that I missed? Check The http://igg.me link in your post. On Monday, December 9, 2013 5:57:56 PM UTC-5, bko...@scanimetrics.com wrote: I've also put in $125 and must say that I haven't had any troubles since using Ulf's kernel. Thanks Ulf On Monday, December 2, 2013 1:53:39 PM UTC-7, Philippe Laurent wrote: I've ponied up for the $125 donation. Gotta have this running right. On Mon, Dec 2, 2013 at 7:23 AM, APRichelieu apric...@gmail.com wrote: Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? I set up a crowd-funding project on http://igg.me/at/eMagii/x/5581172 for people that wants to have USB host hot-plugging on the Beaglebone Black -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Ok, got it. I need to contribute to try it out. Here is my problem, and I would like to hear if this solves it. I have a hub that uses the SMSC 2512 hub chip (USB2512QFN36). Mass storage devices work as long as it's inserted at power up. Any hot plugging after boot will not work. Does your kernel fix this problem? Also, I have some other items in the kernel that I need enabled. If I contribute $50 or $125 I only get whatever you built into your kernel... right? Could I give you my .config and you build it? On Mon, Dec 23, 2013 at 6:33 PM, APRichelieu aprichel...@gmail.com wrote: Den måndagen den 23:e december 2013 kl. 20:26:20 UTC+1 skrev Brent: Where do I go to get Ulf's kernel? I would like to test but I don't know where to look. Is there a patch somewhere that I missed? Check The http://igg.me link in your post. On Monday, December 9, 2013 5:57:56 PM UTC-5, bko...@scanimetrics.comwrote: I've also put in $125 and must say that I haven't had any troubles since using Ulf's kernel. Thanks Ulf On Monday, December 2, 2013 1:53:39 PM UTC-7, Philippe Laurent wrote: I've ponied up for the $125 donation. Gotta have this running right. On Mon, Dec 2, 2013 at 7:23 AM, APRichelieu apric...@gmail.com wrote: Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? I set up a crowd-funding project on http://igg.me/at/eMagii/x/5581172 for people that wants to have USB host hot-plugging on the Beaglebone Black -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -brent -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
I've also put in $125 and must say that I haven't had any troubles since using Ulf's kernel. Thanks Ulf On Monday, December 2, 2013 1:53:39 PM UTC-7, Philippe Laurent wrote: I've ponied up for the $125 donation. Gotta have this running right. On Mon, Dec 2, 2013 at 7:23 AM, APRichelieu apric...@gmail.comjavascript: wrote: Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? I set up a crowd-funding project on http://igg.me/at/eMagii/x/5581172 for people that wants to have USB host hot-plugging on the Beaglebone Black -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? I set up a crowd-funding project on http://igg.me/at/eMagii/x/5581172 for people that wants to have USB host hot-plugging on the Beaglebone Black -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
I've ponied up for the $125 donation. Gotta have this running right. On Mon, Dec 2, 2013 at 7:23 AM, APRichelieu aprichel...@gmail.com wrote: Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? I set up a crowd-funding project on http://igg.me/at/eMagii/x/5581172 for people that wants to have USB host hot-plugging on the Beaglebone Black -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
I have two thumb drives same manufacture, different models. One drive I can insert and it mounts just fine with a udev rule. I can take that drive in and out as many times as I like and it always mounts and unmounts. The other drive will lock up the Host, I can reset it by reading \dev\bus\usb\001\001 file. Curious why one drive works all the time and the other fails, I put an Oscilloscope on the USB host Power P3-p1, noticed a small voltage 250mv sag when inserting the drive that always works, the drive that always fails has a dip of 1V. I placed a 10V 150uF Tantalum capacitor between U8 Pins 6,7 8 and ground to stiffen up the rail. now both drives work without fail. Hope this helps. troy On Saturday, August 31, 2013 8:42:09 AM UTC-7, jez...@gmail.com wrote: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Ulf, many thanks for the mention. If I hit the last brick wall, I'll hire you to make the fix available. Meanwhile, some interesting developments. Curious about the grounding conversation, I removed the BBB from the metal case in which it was enclosed, and placed it on a non-conductive mat. Powered it on with the scanner attached, and it works as it should. BUT, I have not had the Babble Interrupt issue again. Even handling the bare board, the USB wire, the scanner, all of which might have triggered the interrupt before, the scanner continues to work. After 2 days, and still no interruption, I power-cycled the BBB, and again, it has run perfectly with no interruptions for another 2 days, even with the continued attempts to cause the interrupts to occur. By now, I would have had easily a dozen Babble Interrupts with the metal case. I'm going to restore the ondemand startup script and power control settings to 'normal' and continue testing. On Saturday, November 16, 2013 12:39:56 AM UTC-5, Ulf Samuelsson wrote: Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? Work as an independent linux consultant, and I think I can fix this problem. Offered TI to do this, but they said it would be fixed in 3.12, so no interest. Well, 3.12 is here and no fix as far as I can see in the code. I estimate 2 days work to fix with testing. /ulf -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? Work as an independent linux consultant, and I think I can fix this problem. Offered TI to do this, but they said it would be fixed in 3.12, so no interest. Well, 3.12 is here and no fix as far as I can see in the code. I estimate 2 days work to fix with testing. /ulf -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Bummer, despite all of the research, the musb: Babble Interrrupt issue continues to plague. In the hopes that there's a hardware dev out there listening. The board I'm using is A5C. On Saturday, August 31, 2013 11:42:09 AM UTC-4, jez...@gmail.com wrote: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
In my case I have a cape that connects via USB (besides the usual headers). And I have a TP on VBUS, sometimes just inserting a tester on the test point generates a Babble Interrupt. Mine isn't properly grounded. You can always check the governor and cpu frequency with: juanjo@balin:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand juanjo@balin:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq 30 On Monday, November 4, 2013 12:12:53 PM UTC-3, Philippe Laurent wrote: A few more updates. I've read in a number of other locations that this might be due to a grounding issue or a power draw issue. Starting with tackling the power draw issue, it appears that the system bus outputs different power to the USB device depending on its CPU throttling status. The lower the CPU speed, the (slightly) lower the USB output. Still using Ubuntu 13.04, I've removed both the S99ondemand startup script from the rc2.d folder, as well as placed the line echo 'on' | tee /sys/bus/usb/devices/usb1/power/control in the /etc/rc.local script (no quotes) to try and mitigate the issue. The former, from what I understand, keeps the CPU running at full speed, and does not let it slow down based on demand, the latter works to keep USB power on to the port at all times, rather than letting the BBB decide whether to power it off/on. At this point, the BBB has not thrown any more Babble errors through multiple power off/on events, nor through any extensive scanning or quiet time. Of note, there may also be some merit in the grounding issue, as walking across the floor and then touching the BBB case will occasionally cause the Babble issue to appear and the Symbol device to power off. The device is connected to a DC power supply, but there is no grounding plug with the brick, so it stands to reason that the device is not grounded. Hope this helps someone... although I'm sure that at this point I have no concrete solutions to the problem. On Saturday, November 2, 2013 12:32:03 PM UTC-4, Philippe Laurent wrote: Crap. On third reboot (full power off/on), the device is experiencing the same musb: Babble Interrupt error as before. So... this is a hardware issue? The BBB is powered by a separate adapter (not USB), so power shouldn't be the problem. On Friday, November 1, 2013 1:13:09 PM UTC-4, Philippe Laurent wrote: I resolved my issue by installing and using Ubuntu 13.04 on the BBB. It's been up and running the python scanning script for over 24 hours, which is roughly 23 hours longer than it has before. I used the instructions at http://shrkey.com/setting-up-beaglebone-black-to-boot-off-the-microsd-card/to get the installation squared away. On Wednesday, October 30, 2013 9:51:30 AM UTC-4, Bekir Bahadir wrote: Same problem here. Im also willing to pay for a solution Am Samstag, 31. August 2013 17:42:09 UTC+2 schrieb jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
A few more updates. I've read in a number of other locations that this might be due to a grounding issue or a power draw issue. Starting with tackling the power draw issue, it appears that the system bus outputs different power to the USB device depending on its CPU throttling status. The lower the CPU speed, the (slightly) lower the USB output. Still using Ubuntu 13.04, I've removed both the S99ondemand startup script from the rc2.d folder, as well as placed the line echo 'on' | tee /sys/bus/usb/devices/usb1/power/control in the /etc/rc.local script (no quotes) to try and mitigate the issue. The former, from what I understand, keeps the CPU running at full speed, and does not let it slow down based on demand, the latter works to keep USB power on to the port at all times, rather than letting the BBB decide whether to power it off/on. At this point, the BBB has not thrown any more Babble errors through multiple power off/on events, nor through any extensive scanning or quiet time. Of note, there may also be some merit in the grounding issue, as walking across the floor and then touching the BBB case will occasionally cause the Babble issue to appear and the Symbol device to power off. The device is connected to a DC power supply, but there is no grounding plug with the brick, so it stands to reason that the device is not grounded. Hope this helps someone... although I'm sure that at this point I have no concrete solutions to the problem. On Saturday, November 2, 2013 12:32:03 PM UTC-4, Philippe Laurent wrote: Crap. On third reboot (full power off/on), the device is experiencing the same musb: Babble Interrupt error as before. So... this is a hardware issue? The BBB is powered by a separate adapter (not USB), so power shouldn't be the problem. On Friday, November 1, 2013 1:13:09 PM UTC-4, Philippe Laurent wrote: I resolved my issue by installing and using Ubuntu 13.04 on the BBB. It's been up and running the python scanning script for over 24 hours, which is roughly 23 hours longer than it has before. I used the instructions at http://shrkey.com/setting-up-beaglebone-black-to-boot-off-the-microsd-card/to get the installation squared away. On Wednesday, October 30, 2013 9:51:30 AM UTC-4, Bekir Bahadir wrote: Same problem here. Im also willing to pay for a solution Am Samstag, 31. August 2013 17:42:09 UTC+2 schrieb jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Crap. On third reboot (full power off/on), the device is experiencing the same musb: Babble Interrupt error as before. So... this is a hardware issue? The BBB is powered by a separate adapter (not USB), so power shouldn't be the problem. On Friday, November 1, 2013 1:13:09 PM UTC-4, Philippe Laurent wrote: I resolved my issue by installing and using Ubuntu 13.04 on the BBB. It's been up and running the python scanning script for over 24 hours, which is roughly 23 hours longer than it has before. I used the instructions at http://shrkey.com/setting-up-beaglebone-black-to-boot-off-the-microsd-card/to get the installation squared away. On Wednesday, October 30, 2013 9:51:30 AM UTC-4, Bekir Bahadir wrote: Same problem here. Im also willing to pay for a solution Am Samstag, 31. August 2013 17:42:09 UTC+2 schrieb jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Same problem here. Im also willing to pay for a solution Am Samstag, 31. August 2013 17:42:09 UTC+2 schrieb jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Ditto here, application/solutions developer skills, not driver/kernel stuff. This 'CAUTION: musb: Babble Interrupt Occurred' error is an unfortunate deal-breaker for me, and that's a real shame considering that we were going to deploy ~28+ of these for our factory automation needs. The form-factor is a tremendous asset, and it's ability to leverage python and external resources is spot-on. Would easily pay for a solution to get this resolved. On Monday, October 28, 2013 8:44:43 PM UTC-4, Brent wrote: Not surprised. I've had all sorts of problems with USB when using a hub chip. It all seems to point to a software/driver glitch. I really wish I could help out to fix it, but I'm more of an application developer. On Oct 28, 2013 8:33 PM, p...@ideos.com javascript: wrote: I've got the same 'CAUTION: musb: Babble Interrupt Occurred' error in dmesg. Running the latest Angstrom on the Black with a Symbol DS457 attached. On Thursday, October 24, 2013 2:17:01 AM UTC-4, Rune wrote: That's what I'm running, so then maybe that's not the answer :) Any other ideas as to why the USB drops out? Regards, Rune On Thursday, 24 October 2013 00:05:01 UTC+2, RobertCNelson wrote: On Wed, Oct 23, 2013 at 5:01 PM, Rune B. Kalleberg gre...@gmail.com wrote: Have you confirmed that this patch works? That patch was first enabled with the 3.8.13-bone28 release.. I'm running Debian Wheezy and getting the same issue myself. Wifi dongle drops out and will not come back up unless i power cycle. Would this kernel fix work with Debian? Or just Anstrom? I often get another message as well: [92458.978265] CAUTION: musb: Babble Interrupt Occurred [92459.049531] gadget: high-speed config #1: Multifunction with RNDIS These two almost always travel in pairs. Sometimes multiples of them will appear. Running an rtl819cu wifi chipset. The one adafruit sells. Btw, as long as you are not using any capes, you can also give v3.12-rc6 a try as usb seems to be working a lot better with these wifi devices.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
I've got the same 'CAUTION: musb: Babble Interrupt Occurred' error in dmesg. Running the latest Angstrom on the Black with a Symbol DS457 attached. On Thursday, October 24, 2013 2:17:01 AM UTC-4, Rune wrote: That's what I'm running, so then maybe that's not the answer :) Any other ideas as to why the USB drops out? Regards, Rune On Thursday, 24 October 2013 00:05:01 UTC+2, RobertCNelson wrote: On Wed, Oct 23, 2013 at 5:01 PM, Rune B. Kalleberg gre...@gmail.com wrote: Have you confirmed that this patch works? That patch was first enabled with the 3.8.13-bone28 release.. I'm running Debian Wheezy and getting the same issue myself. Wifi dongle drops out and will not come back up unless i power cycle. Would this kernel fix work with Debian? Or just Anstrom? I often get another message as well: [92458.978265] CAUTION: musb: Babble Interrupt Occurred [92459.049531] gadget: high-speed config #1: Multifunction with RNDIS These two almost always travel in pairs. Sometimes multiples of them will appear. Running an rtl819cu wifi chipset. The one adafruit sells. Btw, as long as you are not using any capes, you can also give v3.12-rc6 a try as usb seems to be working a lot better with these wifi devices.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Not surprised. I've had all sorts of problems with USB when using a hub chip. It all seems to point to a software/driver glitch. I really wish I could help out to fix it, but I'm more of an application developer. On Oct 28, 2013 8:33 PM, p...@ideos.com wrote: I've got the same 'CAUTION: musb: Babble Interrupt Occurred' error in dmesg. Running the latest Angstrom on the Black with a Symbol DS457 attached. On Thursday, October 24, 2013 2:17:01 AM UTC-4, Rune wrote: That's what I'm running, so then maybe that's not the answer :) Any other ideas as to why the USB drops out? Regards, Rune On Thursday, 24 October 2013 00:05:01 UTC+2, RobertCNelson wrote: On Wed, Oct 23, 2013 at 5:01 PM, Rune B. Kalleberg gre...@gmail.com wrote: Have you confirmed that this patch works? That patch was first enabled with the 3.8.13-bone28 release.. I'm running Debian Wheezy and getting the same issue myself. Wifi dongle drops out and will not come back up unless i power cycle. Would this kernel fix work with Debian? Or just Anstrom? I often get another message as well: [92458.978265] CAUTION: musb: Babble Interrupt Occurred [92459.049531] gadget: high-speed config #1: Multifunction with RNDIS These two almost always travel in pairs. Sometimes multiples of them will appear. Running an rtl819cu wifi chipset. The one adafruit sells. Btw, as long as you are not using any capes, you can also give v3.12-rc6 a try as usb seems to be working a lot better with these wifi devices.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
That's what I'm running, so then maybe that's not the answer :) Any other ideas as to why the USB drops out? Regards, Rune On Thursday, 24 October 2013 00:05:01 UTC+2, RobertCNelson wrote: On Wed, Oct 23, 2013 at 5:01 PM, Rune B. Kalleberg gre...@gmail.comjavascript: wrote: Have you confirmed that this patch works? That patch was first enabled with the 3.8.13-bone28 release.. I'm running Debian Wheezy and getting the same issue myself. Wifi dongle drops out and will not come back up unless i power cycle. Would this kernel fix work with Debian? Or just Anstrom? I often get another message as well: [92458.978265] CAUTION: musb: Babble Interrupt Occurred [92459.049531] gadget: high-speed config #1: Multifunction with RNDIS These two almost always travel in pairs. Sometimes multiples of them will appear. Running an rtl819cu wifi chipset. The one adafruit sells. Btw, as long as you are not using any capes, you can also give v3.12-rc6 a try as usb seems to be working a lot better with these wifi devices.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Have you confirmed that this patch works? I'm running Debian Wheezy and getting the same issue myself. Wifi dongle drops out and will not come back up unless i power cycle. Would this kernel fix work with Debian? Or just Anstrom? I often get another message as well: [92458.978265] CAUTION: musb: Babble Interrupt Occurred [92459.049531] gadget: high-speed config #1: Multifunction with RNDIS These two almost always travel in pairs. Sometimes multiples of them will appear. Running an rtl819cu wifi chipset. The one adafruit sells. On Friday, 13 September 2013 04:43:27 UTC+2, Brent wrote: You could try this patch... it may help with the Babble Interrupt errors. I haven't tried it myself, but I hope to tomorrow. https://github.com/beagleboard/kernel/commit/46505ea7162720ee8805c8443bf7f10052b9ee7f On Friday, September 6, 2013 4:13:36 AM UTC-4, matt...@live.com wrote: Exactly same thing happen to me. USB sensor, beagleboneblack running for 10 days and today I found it in a 5h loop CAUTION: musb: Babble Interrupt Occurred, then it restart. Any ideas? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
On Wed, Oct 23, 2013 at 5:01 PM, Rune B. Kalleberg greb...@gmail.com wrote: Have you confirmed that this patch works? That patch was first enabled with the 3.8.13-bone28 release.. I'm running Debian Wheezy and getting the same issue myself. Wifi dongle drops out and will not come back up unless i power cycle. Would this kernel fix work with Debian? Or just Anstrom? I often get another message as well: [92458.978265] CAUTION: musb: Babble Interrupt Occurred [92459.049531] gadget: high-speed config #1: Multifunction with RNDIS These two almost always travel in pairs. Sometimes multiples of them will appear. Running an rtl819cu wifi chipset. The one adafruit sells. Btw, as long as you are not using any capes, you can also give v3.12-rc6 a try as usb seems to be working a lot better with these wifi devices.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
