<html><body><div style="font-family: tahoma,new york,times,serif; font-size: 12pt; color: #000000"><div>Same here, brand new DIAL build on all new hardware, GM300, RIM Maxtrac dongle, Pi 3B.</div><div><br data-mce-bogus="1"></div><div> I didn't even think to look for this error until I read this thread, and sure enough it "died or something" too.</div><div><br></div><div data-marker="__SIG_PRE__"><div>Danny<br></div><div><div style="color: #000000; font-family: tahoma, 'new york', times, serif; font-size: 12pt; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;" data-mce-style="color: #000000; font-family: tahoma, 'new york', times, serif; font-size: 12pt; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;">K5CG</div></div><div><br></div></div><br><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><blockquote style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Bob Pyke" <k6ecm1@gmail.com><br><b>To: </b>"Users of Asterisk app_rpt" <app_rpt-users@lists.allstarlink.org><br><b>Sent: </b>Wednesday, November 15, 2017 10:55:23 PM<br><b>Subject: </b>Re: [App_rpt-users] chan_usbradio.c error<br></blockquote></div><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;">Yup. Experiencing the same thing with the latest DIAL using usbradio. I may try simpleusb, but am concerned about delays. I sent this forward to the list a few days ago, and have not heard anything. Something is up with the latest DIAL.<br><br>Thanks<br>Bob<br><br>Sent from iPad<br><br><br>> On Nov 15, 2017, at 9:41 PM, Benjamin Naber <Benjamin@Project23D.com> wrote:<br>> <br>> I do not recall the error code, but it did have the message verbatim <br>> "Died or something!" and I *was* using usbradio.<br>> <br>> Before I swapped the DOM and URi to another machine, I was a bit<br>> stubborn and reset the box - a lot. It seemed be alive and well for<br>> what seemed to be able 12 hours. Sometimes it was less. No idea what<br>> the shortest time was, all I remember is SSH and "reboot now" and<br>> leaving for work. Getting home eight hours later, sometimes the node<br>> would be fine, other times the heartbeat LED on the URI was flashing<br>> *really* fast, or just plain off. And the machine in dmesg said "USB<br>> blah blah blah, Died or something!"<br>> <br>> Maybe the damn old hardware just had a (kernel) panic attack! pun<br>> intended.<br>> <br>> ....more thoughts.........<br>> I would like to make the suggestion, unless extenuating circumstances<br>> prevent it, is make the transition to simpleusb.<br>> <br>> I did not want to do it either, as I was a stubborn idiot, but I did<br>> actually like the fact I did not have to perform extra usbradio-tune-<br>> menu steps, ie getting the RX audio level to precisely-around 27000 to<br>> make the DSP happy.<br>> <br>> Also, while others may have gotten ctcssfrom=dsp to work, but radio<br>> hardware just does a better job at CTCSS, and does not require extra<br>> work to make it... work.<br>> <br>> I figure for that case, and some others, why have a computer do analog<br>> stuff when analog hardware does it infinitely better?<br>> <br>> ~Benjamin, KB9LFZ<br>> <br>> <br>> <br>>> On Wed, 2017-11-15 at 21:18 -0700, Bob Pyke wrote:<br>>> Was it “ERROR[535] chan_usbradio.c: HID process has died or<br>>> something!!”<br>>> <br>>> Bob<br>>> <br>>> Sent from iPad<br>>> <br>>> <br>>> On Nov 15, 2017, at 9:03 PM, Benjamin Naber <Benjamin@Project23D.com><br>>> wrote:<br>>> <br>>>> Bob,<br>>>> <br>>>> I got the "Died or something" error before in the past. I laughed<br>>>> for<br>>>> days after I saw that, programmers got jokes!<br>>>> <br>>>> The issue with mine was the USB hardware in the computer was<br>>>> failing. I<br>>>> have no idea what, but something was. It "Died or something!"<br>>>> <br>>>> Not really sure what that error really meant, I took the DOM (flash<br>>>> memory module with 40 pin header instead of USB, I was using a<br>>>> neoware<br>>>> thin client computer with Limey Linux) and put the DOM in another<br>>>> machine, attached the URi and all was well.<br>>>> <br>>>> Gotta love cryptic errors!<br>>>> <br>>>> ~Benjamin, KB9LFZ<br>>>> <br>>>> <br>>>>> On Sun, 2017-11-12 at 14:24 -0800, Bob wrote:<br>>>>> I periodically experience the following error on the RPi3 with<br>>>>> DIAL<br>>>>> (/var/log/asterisk/messages). Any clues? The repeater uses a<br>>>>> URIx,<br>>>>> and the<br>>>>> Linux address for the USB is the same as devstr= in<br>>>>> usbradio_tune_usb.conf<br>>>>> ERROR[537] chan_usbradio.c: HID process has died or something!!<br>>>>> [Nov 12 13:17:07] NOTICE[538] chan_usbradio.c: Assigned USB<br>>>>> device 1-<br>>>>> 1.2:1.0<br>>>>> to usbradio channel usb<br>>>>> [Nov 12 13:17:07] WARNING[538] chan_usbradio.c: Loaded parameters<br>>>>> from<br>>>>> usbradio_tune_usb.conf for device usb .<br>>>>> [Nov 12 13:17:07] WARNING[537] chan_usbradio.c: Possibly stuck<br>>>>> USB<br>>>>> read<br>>>>> channel. [usb]<br>>>>> [Nov 12 13:17:07] WARNING[537] chan_usbradio.c: Nope, USB read<br>>>>> channel [usb]<br>>>>> wasn't stuck after all.<br>>>>> [Nov 12 13:38:16] ERROR[537] chan_usbradio.c: HID process has<br>>>>> died or<br>>>>> something!!<br>>>>> [Nov 12 13:38:16] WARNING[520] app_rpt.c: rpt_thread restarted on<br>>>>> node <#<br>>>>> redacted><br>>>>> The 21 min delay from the prior message is typical. After the<br>>>>> error,<br>>>>> it<br>>>>> restarts asterisk, and the startup macro reconnects the repeater.<br>>>>> Thanks,<br>>>>> Bob<br>>>>> k6ecm<br>>>>> _______________________________________________<br>>>>> App_rpt-users mailing list<br>>>>> App_rpt-users@lists.allstarlink.org<br>>>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-use<br>>>>> rs<br>>>>> To unsubscribe from this list please visit http://lists.allstarli<br>>>>> nk.o<br>>>>> rg/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the<br>>>>> bottom of the page. Enter your email address and press the<br>>>>> "Unsubscribe or edit options button"<br>>>>> You do not need a password to unsubscribe, you can do it via<br>>>>> email<br>>>>> confirmation. If you have trouble unsubscribing, please send a<br>>>>> message to the list detailing the problem. <br>>>> _______________________________________________<br>>>> App_rpt-users mailing list<br>>>> App_rpt-users@lists.allstarlink.org<br>>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users<br>>>> <br>>>> To unsubscribe from this list please visit http://lists.allstarlink<br>>>> .org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the<br>>>> bottom of the page. Enter your email address and press the<br>>>> "Unsubscribe or edit options button"<br>>>> You do not need a password to unsubscribe, you can do it via email<br>>>> confirmation. If you have trouble unsubscribing, please send a<br>>>> message to the list detailing the problem.<br>>> <br>>> _______________________________________________<br>>> App_rpt-users mailing list<br>>> App_rpt-users@lists.allstarlink.org<br>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users<br>>> <br>>> To unsubscribe from this list please visit http://lists.allstarlink.o<br>>> rg/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the<br>>> bottom of the page. Enter your email address and press the<br>>> "Unsubscribe or edit options button"<br>>> You do not need a password to unsubscribe, you can do it via email<br>>> confirmation. If you have trouble unsubscribing, please send a<br>>> message to the list detailing the problem. <br>> _______________________________________________<br>> App_rpt-users mailing list<br>> App_rpt-users@lists.allstarlink.org<br>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users<br>> <br>> To unsubscribe from this list please visit http://lists.allstarlink.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"<br>> 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.<br>_______________________________________________<br>App_rpt-users mailing list<br>App_rpt-users@lists.allstarlink.org<br>http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users<br><br>To unsubscribe from this list please visit http://lists.allstarlink.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"<br>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.<br></blockquote></div></div></body></html>