It appears the driver is having difficulty finding the USB device. I don't know if it is a driver issue, or the USB hardware in the computer is getting flakey, or ??? I doubt it is the URI. What is the vintage of the computer, and how long has it been in operation? Is this a new "feature" that has appeared after years of use, or is this a new build exhibiting this from the get go? I wonder if the computer is logically moving the USB device. When this occurs, what are the results of executing lsusb at the Linux command line after exiting the CLI> prompt? Does it find the URI, and at the address shown in the error (4-1)? (lsusb will have two leading zeros... e.g 004-001) Thanks, Bob kk6ecm Sent from iPad

On Oct 2, 2014, at 4:18 AM, Steve Denbow <kd8biw@gmail.com> wrote:

Good morning!

My node uses a DMK URI and occasionally the green LED stops flashing and turns on steady. This is the error I get from the CLI. If I restart Asterisk, it seems OK for awhile again until the same thing happens. Rebooting the box makes no difference, still does it from time to time. It has been happening more frequently as of late (almost daily now).

Any ideas or fixes? Thanks!

[Oct 2 01:05:18] ERROR[3118]: chan_usbradio.c:2627 usbradio_read: HID process has died or something!! -- Hungup 'Zap/pseudo-41043279' -- Hungup 'Zap/pseudo-374722952' -- Hungup 'Zap/pseudo-2080343069' -- Hungup 'Zap/pseudo-1121828992' -- Hungup 'Zap/pseudo-926314953' -- Hungup 'Zap/pseudo-678940705' [Oct 2 01:05:19] WARNING[3108]: app_rpt.c:21882 rpt_master: rpt_thread restarted on node 29912 -- Re-Loading config for repeater 29912 -- rpt (Rx) initiating call to Radio/usb29912 on Radio/usb29912 == Set device 4-1 to usb29912 [Oct 2 01:05:19] WARNING[7607]: chan_usbradio.c:1728 hidthread: Loaded parameters from usbradio_tune_usb29912.conf for device usb29912 . [Oct 2 01:05:19] WARNING[7607]: chan_usbradio.c:2276 setformat: Unable to re-open DSP device 1 (usb29912): Device or resource busy == Set device 4-1 to usb29912

-- Steve Denbow | KD8BIW Ohio 220 Group (419)606-5774 Mobile kd8biw@gmail.com www.kd8biw.com

_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

Steve, You did not say what hardware/software you were using. This is a problem that has shown up in the BBB (v1.1) and has been discussed at length. In preparing for a 1.2 release we found several problems with the Acid (and Asterisk) code which could cause this. Without going into a long explanation there are timing problems in the code that were always there and have shown up in the BBB because it has no real HW clock. There was also an issue in simpleusb that caused unrecoverable HID errors with USB failures. The timing problems are much less likely to show up on a PC with rather small timing changes on a ntp update they could occur. The source of your problem could be many things from SW to noise on the USB (RFI,EMI, PS spikes etc.) The URI and USB are susceptible to this kind of interference. Many of us run medium to high power HF and that often is what causes it. Another major cause is power or ground loops that spike back into the USB. Turning off or on a power supply to you node radio is a good example. There have been many discussion about putting ferrites on the input and output lines of the URI and cleaning up PS issues. It is important to try and get rid of HW problems as much as possible but the final fix is to make the system completely recoverable in the event this happens. Be aware of what might be going on or has changed in your setup when the problem occurs. One test you can make on a functioning system (uri green light flashing) is pull the USB cable from the URI wait a few seconds and plug it back in. If the flashing green does not recover then your SW would not be able to recover from the USB disruptions. Let us know what HW/SW you are using and how that test went? I believe we have eliminated most if not all of the problems that would cause the USB to not reset in the upcoming 1.2 BBB release. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Thu, 2 Oct 2014 07:18:34 -0400 From: kd8biw@gmail.com To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] HID Died Good morning! My node uses a DMK URI and occasionally the green LED stops flashing and turns on steady. This is the error I get from the CLI. If I restart Asterisk, it seems OK for awhile again until the same thing happens. Rebooting the box makes no difference, still does it from time to time. It has been happening more frequently as of late (almost daily now). Any ideas or fixes? Thanks! [Oct 2 01:05:18] ERROR[3118]: chan_usbradio.c:2627 usbradio_read: HID process has died or something!! -- Hungup 'Zap/pseudo-41043279' -- Hungup 'Zap/pseudo-374722952' -- Hungup 'Zap/pseudo-2080343069' -- Hungup 'Zap/pseudo-1121828992' -- Hungup 'Zap/pseudo-926314953' -- Hungup 'Zap/pseudo-678940705'[Oct 2 01:05:19] WARNING[3108]: app_rpt.c:21882 rpt_master: rpt_thread restarted on node 29912 -- Re-Loading config for repeater 29912 -- rpt (Rx) initiating call to Radio/usb29912 on Radio/usb29912 == Set device 4-1 to usb29912[Oct 2 01:05:19] WARNING[7607]: chan_usbradio.c:1728 hidthread: Loaded parameters from usbradio_tune_usb29912.conf for device usb29912 .[Oct 2 01:05:19] WARNING[7607]: chan_usbradio.c:2276 setformat: Unable to re-open DSP device 1 (usb29912): Device or resource busy == Set device 4-1 to usb29912 -- Steve Denbow | KD8BIWOhio 220 Group(419)606-5774 Mobilekd8biw@gmail.comwww.kd8biw.com _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.