MarkyMark2015
Posts: 10
Joined: Tue Mar 25, 2014 6:08 am

Rediclious debug from libusb

Sun Mar 15, 2015 7:45 pm

Hi All,

I've recompiled one of my apps on raspberry pi 2 and upgraded the OS. Before this libusb was quiet. Now when I run it up there is a ton of debug messages produced.

Is there a problem? Or a switch to turn this off? Or indeed is there a problem with the driver on a multi-cpu machine?

I've posted and extract below - it's not doing the apps performance any favours

Many Thanks

Mark
  • libusb: 9.938220 debug [libusb_handle_events_timeout_completed] another thread is doing event handling
    libusb: 9.938325 debug [handle_events] poll() returned 0
    libusb: 9.938431 debug [libusb_handle_events_timeout_completed] doing our own event handling
    libusb: 9.938514 debug [handle_events] poll() 3 fds with timeout in 60000ms
    libusb: 9.938596 debug [handle_events] poll() returned 1
    libusb: 9.938677 debug [reap_for_handle] urb type=2 status=0 transferred=0
    libusb: 9.938753 debug [handle_control_completion] handling completion status 0
    libusb: 9.938830 debug [disarm_timerfd]
    libusb: 9.938902 debug [usbi_handle_transfer_completion] transfer 0x6f7240e4 has callback 0x72433c70
    libusb: 9.938977 debug [ctrl_transfer_cb] actual_length=0
    libusb: 9.939068 debug [libusb_handle_events_timeout_completed] doing our own event handling
    libusb: 9.939141 debug [handle_events] poll() 3 fds with timeout in 1ms
    libusb: 9.940161 debug [libusb_submit_transfer] arm timerfd for timeout in 5000ms (first in line)
    libusb: 9.940274 debug [libusb_handle_events_timeout_completed] another thread is doing event handling
    libusb: 9.940383 debug [handle_events] poll() returned 0
    libusb: 9.940497 debug [libusb_handle_events_timeout_completed] doing our own event handling
    libusb: 9.940588 debug [handle_events] poll() 3 fds with timeout in 60000ms
    libusb: 9.940670 debug [handle_events] poll() returned 1
    libusb: 9.940751 debug [reap_for_handle] urb type=2 status=0 transferred=10
    libusb: 9.940840 debug [handle_control_completion] handling completion status 0
    libusb: 9.940913 debug [disarm_timerfd]
    libusb: 9.940967 debug [usbi_handle_transfer_completion] transfer 0x6f7240e4 has callback 0x72433c70
    libusb: 9.941041 debug [ctrl_transfer_cb] actual_length=10
    libusb: 9.941182 debug [libusb_handle_events_timeout_completed] doing our own event handling
    libusb: 9.941221 debug [handle_events] poll() 3 fds with timeout in 1ms
    libusb: 9.941275 debug [libusb_submit_transfer] arm timerfd for timeout in 5000ms (first in line)
    libusb: 9.941455 debug [libusb_handle_events_timeout_completed] another thread is doing event handling
    libusb: 9.941776 debug [handle_events] poll() returned 1
    libusb: 9.941887 debug [reap_for_handle] urb type=2 status=0 transferred=12
    libusb: 9.941950 debug [handle_control_completion] handling completion status 0
    libusb: 9.942004 debug [disarm_timerfd]
    libusb: 9.942063 debug [usbi_handle_transfer_completion] transfer 0x6f7240e4 has callback 0x72433c70
    libusb: 9.942138 debug [ctrl_transfer_cb] actual_length=12
    libusb: 9.942207 debug [libusb_handle_events_timeout_completed] doing our own event handling
    libusb: 9.942236 debug [handle_events] poll() 3 fds with timeout in 1ms
    libusb: 9.943400 debug [libusb_submit_transfer] arm timerfd for timeout in 5000ms (first in line)
    libusb: 9.943530 debug [libusb_handle_events_timeout_completed] another thread is doing event handling
    libusb: 9.943405 debug [handle_events] poll() returned 0
    libusb: 9.943739 debug [libusb_handle_events_timeout_completed] doing our own event handling
    libusb: 9.943821 debug [handle_events] poll() 3 fds with timeout in 60000ms
    libusb: 9.943903 debug [handle_events] poll() returned 1
    libusb: 9.943980 debug [reap_for_handle] urb type=2 status=0 transferred=10
    libusb: 9.944053 debug [handle_control_completion] handling completion status 0
    libusb: 9.944125 debug [disarm_timerfd]
    libusb: 9.944180 debug [usbi_handle_transfer_completion] transfer 0x6f7240e4 has callback 0x72433c70
    libusb: 9.944252 debug [ctrl_transfer_cb] actual_length=10
    libusb: 9.944369 debug [libusb_release_interface] interface 0
    libusb: 9.944499 debug [libusb_close]
    libusb: 9.944584 debug [usbi_remove_pollfd] remove fd 21
    libusb: 9.944680 debug [libusb_unref_device] destroy device 1.5
    libusb: 9.951863 debug [libusb_exit]
    libusb: 9.951980 debug [usbi_remove_pollfd] remove fd 3
    libusb: 9.952103 debug [usbi_remove_pollfd] remove fd 5

MarkyMark2015
Posts: 10
Joined: Tue Mar 25, 2014 6:08 am

Re: Rediclious debug from libusb

Mon Mar 16, 2015 1:24 pm

This seems to be related to the libusb.

I downloaded from source (git clone https://github.com/libusb/libusb.git), compiled that an now the debuglogging has gone and normailty resumed.

Not sure how it go into that state.

Mark

KingPo
Posts: 3
Joined: Mon Jan 14, 2019 9:21 am

Re: Rediclious debug from libusb

Mon Jan 14, 2019 9:26 am

Hi There,

I'm facing the same issue, but as I'm new to Raspberry and Linux in generall I'm struggeling a bit with getting this solved.

I'm using an Pi Zero W with Raspian.
Finally I want to tran ANT+ Data (via an USB Stick). Finally this all works, but i got tons of "libusb: debug ...." Messages in the terminal and I have no clue how to disable this.

I searched the Web and I find out for me that it could be that during compiling process the Log needs to be disabled (also if this should be by default).


Can someone help me please out here? What information you else need from me.

Many Thanks in advance and regards
KingPo

User avatar
rpdom
Posts: 14682
Joined: Sun May 06, 2012 5:17 am
Location: Chelmsford, Essex, UK

Re: Rediclious debug from libusb

Mon Jan 14, 2019 10:00 am

Please start a new subject describing exactly what you want rather than following on to a four year old out-of-date subject.
Thank you.

KingPo
Posts: 3
Joined: Mon Jan 14, 2019 9:21 am

Re: Rediclious debug from libusb

Mon Jan 14, 2019 10:38 am

rpdom wrote:
Mon Jan 14, 2019 10:00 am
Please start a new subject describing exactly what you want rather than following on to a four year old out-of-date subject.
Thank you.
Thanks rpdom, expected it was better to repley on a thread having the same issue like mine....

Opened a new one for this now.

Thanks

fruitoftheloom
Posts: 20118
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: Rediclious debug from libusb

Mon Jan 14, 2019 10:58 am

KingPo wrote:
Mon Jan 14, 2019 10:38 am
rpdom wrote:
Mon Jan 14, 2019 10:00 am
Please start a new subject describing exactly what you want rather than following on to a four year old out-of-date subject.
Thank you.
Thanks rpdom, expected it was better to repley on a thread having the same issue like mine....

Opened a new one for this now.

Thanks

The Raspberry Pi Zero W was not available in 2015, neither was Raspbian Stretch !
adieu

Asus CS10 Chromebit / HP Envy 4500 Wireless Printer / Raspberry Pi Model 2B v1.1 / RealVNC Software...

User avatar
mahjongg
Forum Moderator
Forum Moderator
Posts: 11984
Joined: Sun Mar 11, 2012 12:19 am
Location: South Holland, The Netherlands

Re: Rediclious debug from libusb

Mon Jan 14, 2019 12:23 pm

Will delete this necro, as soon as a new thread is created.

Return to “Troubleshooting”