I'd like to know if I'm the only one hitting this issue or not. Basically, I've installed Ubuntu versions 12.04 through 13.04 on this system, as well as just now Debian Wheezy just to make sure I'm not hitting a fluke on any of them.
I'm using kb2kskype.py with my b2k telbox device I've always used with Skype before, but now on this system it seems to run for a few hours and then lock the system up solid...I have to pull the plug or hold the power button in to kill it.
The last few lines (all at the same timestamp) in syslog are:
Nov 13 21:36:33 usbb2k_api[]: Yealink device found on bus 002
Nov 13 21:36:33 kernel: [] yealink: urb_irq_callback - urb status -108
Nov 13 21:36:33 kernel: [] yealink: urb_ctl_callback - usb_submit_urb failed -2
Nov 13 21:36:33 usbb2k_api[]: USB device B2Kv2 [0x57d] initialized
Nov 13 21:36:33 usbb2k_api[]: CMD server started
Nov 13 21:36:33 usbb2k_api[]: USB server started
I don't know that those are the final steps my system takes before it locks up, but those are the last lines written to the log.
Any ideas?
I'd been running this same piece of equipment fine on my prior server, but it died so I have been forced into an upgrade to the latest kernel and distros now...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did find this article: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570532 , which makes it appear that there were some serious issues with the kernel yealink support in the past (2010), but I haven't seen an issue until just this past week when I had to rebuild my system.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I added 'blacklist yealink' to /etc/modprobe.d/blacklist.conf and rebooted. Now on connecting the device I see in /var/log/syslog only messages from the usbb2k_api driver:
Yealink device found on bus 002
USB device B2Kv2 [0x57d] initialized
CMD server started
USB server started
I'll keep an eye on it now and see if it keeps running okay. Thanks!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Blacklisting the yealink module seems to have completely fixed my issue! My phones have worked perfectly and NO freezes or lockups of any sort have occurred! (Previously it locked up after an hour or less!)
Thanks, Simon! :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
(Sorry if this ends up as a double post!)
I'd like to know if I'm the only one hitting this issue or not. Basically, I've installed Ubuntu versions 12.04 through 13.04 on this system, as well as just now Debian Wheezy just to make sure I'm not hitting a fluke on any of them.
I'm using kb2kskype.py with my b2k telbox device I've always used with Skype before, but now on this system it seems to run for a few hours and then lock the system up solid...I have to pull the plug or hold the power button in to kill it.
The last few lines (all at the same timestamp) in syslog are:
Nov 13 21:36:33 usbb2k_api[]: Yealink device found on bus 002
Nov 13 21:36:33 kernel: [] yealink: urb_irq_callback - urb status -108
Nov 13 21:36:33 kernel: [] yealink: urb_ctl_callback - usb_submit_urb failed -2
Nov 13 21:36:33 usbb2k_api[]: USB device B2Kv2 [0x57d] initialized
Nov 13 21:36:33 usbb2k_api[]: CMD server started
Nov 13 21:36:33 usbb2k_api[]: USB server started
I don't know that those are the final steps my system takes before it locks up, but those are the last lines written to the log.
Any ideas?
I'd been running this same piece of equipment fine on my prior server, but it died so I have been forced into an upgrade to the latest kernel and distros now...
I did find this article: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570532 , which makes it appear that there were some serious issues with the kernel yealink support in the past (2010), but I haven't seen an issue until just this past week when I had to rebuild my system.
This software doesn't use that module and infact you need to get rid of it to work properly.
Have you blacklisted the yealink kernel module ?
edit /etc/modprobe.d/blacklist and add
blacklist yealink
save and reboot
Let me know if that works.
Last edit: Simon_6162 2013-11-14
I added 'blacklist yealink' to /etc/modprobe.d/blacklist.conf and rebooted. Now on connecting the device I see in /var/log/syslog only messages from the usbb2k_api driver:
I'll keep an eye on it now and see if it keeps running okay. Thanks!!
Blacklisting the yealink module seems to have completely fixed my issue! My phones have worked perfectly and NO freezes or lockups of any sort have occurred! (Previously it locked up after an hour or less!)
Thanks, Simon! :)
That's good news.
Simon