NB: there was a typo in the first patch ("garauntee", line 127), but we
can fix that whenever.
I had the same issue as Xiaofan with the stress test on my ARM/Linux
platform, which this set of patch sorted.
Also, 4d099d08a99aff38c72e393d7eef94b6436d39f8 solved the issue I had
reported earlier w
Hi,
On 06/14/2013 04:34 PM, Nathan Hjelm wrote:
> Sorry for the mistake. Don't know why I didn't catch that earlier.
Well my patch is wrong too, besides adding the pthread_join, I
instinctively swapped the location of the pthread_cancel and
the udev_monitor_unref(udev_monitor); call, thinking tha
Sorry for the mistake. Don't know why I didn't catch that earlier.-NathanOn Jun 14, 2013, at 07:48 AM, Hans de Goede wrote:Hi, On 06/14/2013 02:43 PM, Xiaofan Chen wrote: > On Fri, Jun 14, 2013 at 5:59 PM, Hans de Goede wrote: >> Hmm, ok, error 11 is EAGAIN, so indeed you're
Hi,
On 06/14/2013 02:43 PM, Xiaofan Chen wrote:
> On Fri, Jun 14, 2013 at 5:59 PM, Hans de Goede wrote:
>> Hmm, ok, error 11 is EAGAIN, so indeed you're running out of some resource.
>>
>> Can you give the attached patch a try please ?
>>
>
> Great. Your patch fixed the issues I have under Ubuntu
On Fri, Jun 14, 2013 at 5:59 PM, Hans de Goede wrote:
> Hmm, ok, error 11 is EAGAIN, so indeed you're running out of some resource.
>
> Can you give the attached patch a try please ?
>
Great. Your patch fixed the issues I have under Ubuntu Linux.
--
Xiaofan
---
Hi,
On 06/14/2013 11:31 AM, Xiaofan Chen wrote:
On Fri, Jun 14, 2013 at 4:08 PM, Hans de Goede wrote:
Hmm, as Nathan has already pointed out this is caused by pthread_create
failing. I think you may be running out of resources and/or hitting
a ulimit.
This may also be related to the udev fd n
On Thu, Jun 13, 2013 at 11:00 PM, Nathan Hjelm wrote:
> ??? It looks like it is failing on pthread_create. That doesn't seem right.
> Can you run under valgrind and see if anything obvious is wrong? I will test
> in a Linux VM when I get home and see if I can reproduce the problem there.
Here are
On Fri, Jun 14, 2013 at 4:08 PM, Hans de Goede wrote:
> Hmm, as Nathan has already pointed out this is caused by pthread_create
> failing. I think you may be running out of resources and/or hitting
> a ulimit.
>
> This may also be related to the udev fd not being non-blocking issue
> Chris Dickens
Hi,
On 06/13/2013 03:57 PM, Xiaofan Chen wrote:
> On Thu, Jun 13, 2013 at 9:20 PM, Toby Gray wrote:
>> On 13/06/13 14:07, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 06/13/2013 02:41 PM, Xiaofan Chen wrote:
stress test failed with the latest git tree.
1.0.15 release works fine.
mc
??? It looks like it is failing on pthread_create. That doesn't seem right. Can you run under valgrind and see if anything obvious is wrong? I will test in a Linux VM when I get home and see if I can reproduce the problem there.-NathanOn Jun 13, 2013, at 08:53 AM, Xiaofan Chen wrote:On Thu, Jun 13
On Thu, Jun 13, 2013 at 10:02 PM, Xiaofan Chen wrote:
> On Thu, Jun 13, 2013 at 9:57 PM, Xiaofan Chen wrote:
>> The error seems to be related to udev.
>>
>> libusbx: error [linux_udev_start_event_monitor] could not create linux
>> hotplug event thread
>> libusbx: error [op_init] error starting ho
On Thu, Jun 13, 2013 at 9:57 PM, Xiaofan Chen wrote:
> The error seems to be related to udev.
>
> libusbx: error [linux_udev_start_event_monitor] could not create linux
> hotplug event thread
> libusbx: error [op_init] error starting hotplug event monitor
> Failed to init libusb: -99
>
> Enclosed
On Thu, Jun 13, 2013 at 9:20 PM, Toby Gray wrote:
> On 13/06/13 14:07, Hans de Goede wrote:
>> Hi,
>>
>> On 06/13/2013 02:41 PM, Xiaofan Chen wrote:
>>> stress test failed with the latest git tree.
>>> 1.0.15 release works fine.
>>>
>>> mcuee@ubuntu1304vm:~/Desktop/build/libusbx$ ./tests/stress
>>
On 13/06/13 14:07, Hans de Goede wrote:
> Hi,
>
> On 06/13/2013 02:41 PM, Xiaofan Chen wrote:
>> stress test failed with the latest git tree.
>> 1.0.15 release works fine.
>>
>> mcuee@ubuntu1304vm:~/Desktop/build/libusbx$ ./tests/stress
>> Starting test run: init_and_exit...
>> Failed to init libus
Hi,
On 06/13/2013 02:41 PM, Xiaofan Chen wrote:
> stress test failed with the latest git tree.
> 1.0.15 release works fine.
>
> mcuee@ubuntu1304vm:~/Desktop/build/libusbx$ ./tests/stress
> Starting test run: init_and_exit...
> Failed to init libusb on iteration 382: -99
> Failure (1)
> Starting te
2013/6/13 Xiaofan Chen :
> stress test failed with the latest git tree.
> 1.0.15 release works fine.
>
> mcuee@ubuntu1304vm:~/Desktop/build/libusbx$ ./tests/stress
> Starting test run: init_and_exit...
> Failed to init libusb on iteration 382: -99
> Failure (1)
I can't reproduce the problem here (
stress test failed with the latest git tree.
1.0.15 release works fine.
mcuee@ubuntu1304vm:~/Desktop/build/libusbx$ ./tests/stress
Starting test run: init_and_exit...
Failed to init libusb on iteration 382: -99
Failure (1)
Starting test run: get_device_list...
Failed to init libusb: -99
Failure (1
17 matches
Mail list logo