chan_usbradio.c error
I periodically experience the following error on the RPi3 with DIAL (/var/log/asterisk/messages). Any clues? The repeater uses a URIx, and the Linux address for the USB is the same as devstr= in usbradio_tune_usb.conf ERROR[537] chan_usbradio.c: HID process has died or something!! [Nov 12 13:17:07] NOTICE[538] chan_usbradio.c: Assigned USB device 1-1.2:1.0 to usbradio channel usb [Nov 12 13:17:07] WARNING[538] chan_usbradio.c: Loaded parameters from usbradio_tune_usb.conf for device usb . [Nov 12 13:17:07] WARNING[537] chan_usbradio.c: Possibly stuck USB read channel. [usb] [Nov 12 13:17:07] WARNING[537] chan_usbradio.c: Nope, USB read channel [usb] wasn't stuck after all. [Nov 12 13:38:16] ERROR[537] chan_usbradio.c: HID process has died or something!! [Nov 12 13:38:16] WARNING[520] app_rpt.c: rpt_thread restarted on node <# redacted> The 21 min delay from the prior message is typical. After the error, it restarts asterisk, and the startup macro reconnects the repeater. Thanks, Bob k6ecm
Bob, I got the "Died or something" error before in the past. I laughed for days after I saw that, programmers got jokes! The issue with mine was the USB hardware in the computer was failing. I have no idea what, but something was. It "Died or something!" Not really sure what that error really meant, I took the DOM (flash memory module with 40 pin header instead of USB, I was using a neoware thin client computer with Limey Linux) and put the DOM in another machine, attached the URi and all was well. Gotta love cryptic errors! ~Benjamin, KB9LFZ On Sun, 2017-11-12 at 14:24 -0800, Bob wrote:
I periodically experience the following error on the RPi3 with DIAL (/var/log/asterisk/messages). Any clues? The repeater uses a URIx, and the Linux address for the USB is the same as devstr= in usbradio_tune_usb.conf
ERROR[537] chan_usbradio.c: HID process has died or something!!
[Nov 12 13:17:07] NOTICE[538] chan_usbradio.c: Assigned USB device 1- 1.2:1.0 to usbradio channel usb [Nov 12 13:17:07] WARNING[538] chan_usbradio.c: Loaded parameters from usbradio_tune_usb.conf for device usb . [Nov 12 13:17:07] WARNING[537] chan_usbradio.c: Possibly stuck USB read channel. [usb] [Nov 12 13:17:07] WARNING[537] chan_usbradio.c: Nope, USB read channel [usb] wasn't stuck after all. [Nov 12 13:38:16] ERROR[537] chan_usbradio.c: HID process has died or something!! [Nov 12 13:38:16] WARNING[520] app_rpt.c: rpt_thread restarted on node <# redacted>
The 21 min delay from the prior message is typical. After the error, it restarts asterisk, and the startup macro reconnects the repeater.
Thanks, Bob k6ecm
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.o rg/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.
Was it “ERROR[535] chan_usbradio.c: HID process has died or something!!” Bob Sent from iPad
On Nov 15, 2017, at 9:03 PM, Benjamin Naber <Benjamin@Project23D.com> wrote:
Bob,
I got the "Died or something" error before in the past. I laughed for days after I saw that, programmers got jokes!
The issue with mine was the USB hardware in the computer was failing. I have no idea what, but something was. It "Died or something!"
Not really sure what that error really meant, I took the DOM (flash memory module with 40 pin header instead of USB, I was using a neoware thin client computer with Limey Linux) and put the DOM in another machine, attached the URi and all was well.
Gotta love cryptic errors!
~Benjamin, KB9LFZ
On Sun, 2017-11-12 at 14:24 -0800, Bob wrote: I periodically experience the following error on the RPi3 with DIAL (/var/log/asterisk/messages). Any clues? The repeater uses a URIx, and the Linux address for the USB is the same as devstr= in usbradio_tune_usb.conf
ERROR[537] chan_usbradio.c: HID process has died or something!!
[Nov 12 13:17:07] NOTICE[538] chan_usbradio.c: Assigned USB device 1- 1.2:1.0 to usbradio channel usb [Nov 12 13:17:07] WARNING[538] chan_usbradio.c: Loaded parameters from usbradio_tune_usb.conf for device usb . [Nov 12 13:17:07] WARNING[537] chan_usbradio.c: Possibly stuck USB read channel. [usb] [Nov 12 13:17:07] WARNING[537] chan_usbradio.c: Nope, USB read channel [usb] wasn't stuck after all. [Nov 12 13:38:16] ERROR[537] chan_usbradio.c: HID process has died or something!! [Nov 12 13:38:16] WARNING[520] app_rpt.c: rpt_thread restarted on node <# redacted>
The 21 min delay from the prior message is typical. After the error, it restarts asterisk, and the startup macro reconnects the repeater.
Thanks, Bob k6ecm
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.o rg/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.
App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
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" 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.
I do not recall the error code, but it did have the message verbatim "Died or something!" and I *was* using usbradio. Before I swapped the DOM and URi to another machine, I was a bit stubborn and reset the box - a lot. It seemed be alive and well for what seemed to be able 12 hours. Sometimes it was less. No idea what the shortest time was, all I remember is SSH and "reboot now" and leaving for work. Getting home eight hours later, sometimes the node would be fine, other times the heartbeat LED on the URI was flashing *really* fast, or just plain off. And the machine in dmesg said "USB blah blah blah, Died or something!" Maybe the damn old hardware just had a (kernel) panic attack! pun intended. ....more thoughts......... I would like to make the suggestion, unless extenuating circumstances prevent it, is make the transition to simpleusb. I did not want to do it either, as I was a stubborn idiot, but I did actually like the fact I did not have to perform extra usbradio-tune- menu steps, ie getting the RX audio level to precisely-around 27000 to make the DSP happy. Also, while others may have gotten ctcssfrom=dsp to work, but radio hardware just does a better job at CTCSS, and does not require extra work to make it... work. I figure for that case, and some others, why have a computer do analog stuff when analog hardware does it infinitely better? ~Benjamin, KB9LFZ On Wed, 2017-11-15 at 21:18 -0700, Bob Pyke wrote:
Was it “ERROR[535] chan_usbradio.c: HID process has died or something!!”
Bob
Sent from iPad
On Nov 15, 2017, at 9:03 PM, Benjamin Naber <Benjamin@Project23D.com> wrote:
Bob,
I got the "Died or something" error before in the past. I laughed for days after I saw that, programmers got jokes!
The issue with mine was the USB hardware in the computer was failing. I have no idea what, but something was. It "Died or something!"
Not really sure what that error really meant, I took the DOM (flash memory module with 40 pin header instead of USB, I was using a neoware thin client computer with Limey Linux) and put the DOM in another machine, attached the URi and all was well.
Gotta love cryptic errors!
~Benjamin, KB9LFZ
On Sun, 2017-11-12 at 14:24 -0800, Bob wrote:
I periodically experience the following error on the RPi3 with DIAL (/var/log/asterisk/messages). Any clues? The repeater uses a URIx, and the Linux address for the USB is the same as devstr= in usbradio_tune_usb.conf ERROR[537] chan_usbradio.c: HID process has died or something!! [Nov 12 13:17:07] NOTICE[538] chan_usbradio.c: Assigned USB device 1- 1.2:1.0 to usbradio channel usb [Nov 12 13:17:07] WARNING[538] chan_usbradio.c: Loaded parameters from usbradio_tune_usb.conf for device usb . [Nov 12 13:17:07] WARNING[537] chan_usbradio.c: Possibly stuck USB read channel. [usb] [Nov 12 13:17:07] WARNING[537] chan_usbradio.c: Nope, USB read channel [usb] wasn't stuck after all. [Nov 12 13:38:16] ERROR[537] chan_usbradio.c: HID process has died or something!! [Nov 12 13:38:16] WARNING[520] app_rpt.c: rpt_thread restarted on node <# redacted> The 21 min delay from the prior message is typical. After the error, it restarts asterisk, and the startup macro reconnects the repeater. Thanks, Bob k6ecm _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-use rs To unsubscribe from this list please visit http://lists.allstarli nk.o rg/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.
App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
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" 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.
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.o rg/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.
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. Thanks Bob Sent from iPad
On Nov 15, 2017, at 9:41 PM, Benjamin Naber <Benjamin@Project23D.com> wrote:
I do not recall the error code, but it did have the message verbatim "Died or something!" and I *was* using usbradio.
Before I swapped the DOM and URi to another machine, I was a bit stubborn and reset the box - a lot. It seemed be alive and well for what seemed to be able 12 hours. Sometimes it was less. No idea what the shortest time was, all I remember is SSH and "reboot now" and leaving for work. Getting home eight hours later, sometimes the node would be fine, other times the heartbeat LED on the URI was flashing *really* fast, or just plain off. And the machine in dmesg said "USB blah blah blah, Died or something!"
Maybe the damn old hardware just had a (kernel) panic attack! pun intended.
....more thoughts......... I would like to make the suggestion, unless extenuating circumstances prevent it, is make the transition to simpleusb.
I did not want to do it either, as I was a stubborn idiot, but I did actually like the fact I did not have to perform extra usbradio-tune- menu steps, ie getting the RX audio level to precisely-around 27000 to make the DSP happy.
Also, while others may have gotten ctcssfrom=dsp to work, but radio hardware just does a better job at CTCSS, and does not require extra work to make it... work.
I figure for that case, and some others, why have a computer do analog stuff when analog hardware does it infinitely better?
~Benjamin, KB9LFZ
On Wed, 2017-11-15 at 21:18 -0700, Bob Pyke wrote: Was it “ERROR[535] chan_usbradio.c: HID process has died or something!!”
Bob
Sent from iPad
On Nov 15, 2017, at 9:03 PM, Benjamin Naber <Benjamin@Project23D.com> wrote:
Bob,
I got the "Died or something" error before in the past. I laughed for days after I saw that, programmers got jokes!
The issue with mine was the USB hardware in the computer was failing. I have no idea what, but something was. It "Died or something!"
Not really sure what that error really meant, I took the DOM (flash memory module with 40 pin header instead of USB, I was using a neoware thin client computer with Limey Linux) and put the DOM in another machine, attached the URi and all was well.
Gotta love cryptic errors!
~Benjamin, KB9LFZ
On Sun, 2017-11-12 at 14:24 -0800, Bob wrote: I periodically experience the following error on the RPi3 with DIAL (/var/log/asterisk/messages). Any clues? The repeater uses a URIx, and the Linux address for the USB is the same as devstr= in usbradio_tune_usb.conf ERROR[537] chan_usbradio.c: HID process has died or something!! [Nov 12 13:17:07] NOTICE[538] chan_usbradio.c: Assigned USB device 1- 1.2:1.0 to usbradio channel usb [Nov 12 13:17:07] WARNING[538] chan_usbradio.c: Loaded parameters from usbradio_tune_usb.conf for device usb . [Nov 12 13:17:07] WARNING[537] chan_usbradio.c: Possibly stuck USB read channel. [usb] [Nov 12 13:17:07] WARNING[537] chan_usbradio.c: Nope, USB read channel [usb] wasn't stuck after all. [Nov 12 13:38:16] ERROR[537] chan_usbradio.c: HID process has died or something!! [Nov 12 13:38:16] WARNING[520] app_rpt.c: rpt_thread restarted on node <# redacted> The 21 min delay from the prior message is typical. After the error, it restarts asterisk, and the startup macro reconnects the repeater. Thanks, Bob k6ecm _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-use rs To unsubscribe from this list please visit http://lists.allstarli nk.o rg/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.
App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
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" 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.
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.o rg/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.
App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
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" 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.
Same here, brand new DIAL build on all new hardware, GM300, RIM Maxtrac dongle, Pi 3B. I didn't even think to look for this error until I read this thread, and sure enough it "died or something" too. Danny K5CG
From: "Bob Pyke" <k6ecm1@gmail.com> To: "Users of Asterisk app_rpt" <app_rpt-users@lists.allstarlink.org> Sent: Wednesday, November 15, 2017 10:55:23 PM Subject: Re: [App_rpt-users] chan_usbradio.c error
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.
Thanks Bob
Sent from iPad
On Nov 15, 2017, at 9:41 PM, Benjamin Naber <Benjamin@Project23D.com> wrote:
I do not recall the error code, but it did have the message verbatim "Died or something!" and I *was* using usbradio.
Before I swapped the DOM and URi to another machine, I was a bit stubborn and reset the box - a lot. It seemed be alive and well for what seemed to be able 12 hours. Sometimes it was less. No idea what the shortest time was, all I remember is SSH and "reboot now" and leaving for work. Getting home eight hours later, sometimes the node would be fine, other times the heartbeat LED on the URI was flashing *really* fast, or just plain off. And the machine in dmesg said "USB blah blah blah, Died or something!"
Maybe the damn old hardware just had a (kernel) panic attack! pun intended.
....more thoughts......... I would like to make the suggestion, unless extenuating circumstances prevent it, is make the transition to simpleusb.
I did not want to do it either, as I was a stubborn idiot, but I did actually like the fact I did not have to perform extra usbradio-tune- menu steps, ie getting the RX audio level to precisely-around 27000 to make the DSP happy.
Also, while others may have gotten ctcssfrom=dsp to work, but radio hardware just does a better job at CTCSS, and does not require extra work to make it... work.
I figure for that case, and some others, why have a computer do analog stuff when analog hardware does it infinitely better?
~Benjamin, KB9LFZ
On Wed, 2017-11-15 at 21:18 -0700, Bob Pyke wrote: Was it “ERROR[535] chan_usbradio.c: HID process has died or something!!”
Bob
Sent from iPad
On Nov 15, 2017, at 9:03 PM, Benjamin Naber <Benjamin@Project23D.com> wrote:
Bob,
I got the "Died or something" error before in the past. I laughed for days after I saw that, programmers got jokes!
The issue with mine was the USB hardware in the computer was failing. I have no idea what, but something was. It "Died or something!"
Not really sure what that error really meant, I took the DOM (flash memory module with 40 pin header instead of USB, I was using a neoware thin client computer with Limey Linux) and put the DOM in another machine, attached the URi and all was well.
Gotta love cryptic errors!
~Benjamin, KB9LFZ
On Sun, 2017-11-12 at 14:24 -0800, Bob wrote: I periodically experience the following error on the RPi3 with DIAL (/var/log/asterisk/messages). Any clues? The repeater uses a URIx, and the Linux address for the USB is the same as devstr= in usbradio_tune_usb.conf ERROR[537] chan_usbradio.c: HID process has died or something!! [Nov 12 13:17:07] NOTICE[538] chan_usbradio.c: Assigned USB device 1- 1.2:1.0 to usbradio channel usb [Nov 12 13:17:07] WARNING[538] chan_usbradio.c: Loaded parameters from usbradio_tune_usb.conf for device usb . [Nov 12 13:17:07] WARNING[537] chan_usbradio.c: Possibly stuck USB read channel. [usb] [Nov 12 13:17:07] WARNING[537] chan_usbradio.c: Nope, USB read channel [usb] wasn't stuck after all. [Nov 12 13:38:16] ERROR[537] chan_usbradio.c: HID process has died or something!! [Nov 12 13:38:16] WARNING[520] app_rpt.c: rpt_thread restarted on node <# redacted> The 21 min delay from the prior message is typical. After the error, it restarts asterisk, and the startup macro reconnects the repeater. Thanks, Bob k6ecm _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-use rs To unsubscribe from this list please visit http://lists.allstarli nk.o rg/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.
App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
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" 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.
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.o rg/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.
App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
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" 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.
App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
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" 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.
participants (4)
-
Benjamin Naber -
Bob -
Bob Pyke
-
K5CG