Cannot flash multiple devices with fastboot

Hello Tyler, thanks for your report.

I guarded the data-intensive fastboot calls (flash and boot) with flock
to avoid this problem. I am hoping we won't need that for the "small"
commands.

Could you try the branch at lp:~terceiro/lava-dispatcher/fastboot-flock
and let me know if it works for you?

--
Antonio Terceiro
Software Engineer - Linaro
http://www.linaro.org

Hello Antonio,

I am new to brz (coming from git) I have local development setup for the
dispatcher at this point. How, in bzr can I merge your fastboot-flock
branch on top of my local dispatcher changes? Once I get the code pulled I
should be able to test it right away. Thanks for your help.

Tyler

On Thu, Jan 31, 2013 at 8:32 AM, Antonio Terceiro <
<email address hidden>> wrote:

> Hello Tyler, thanks for your report.
>
> I guarded the data-intensive fastboot calls (flash and boot) with flock
> to avoid this problem. I am hoping we won't need that for the "small"
> commands.
>
> Could you try the branch at lp:~terceiro/lava-dispatcher/fastboot-flock
> and let me know if it works for you?
>
> --
> Antonio Terceiro
> Software Engineer - Linaro
> http://www.linaro.org
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1110622
>
> Title:
> Cannot flash multiple devices with fastboot
>
> Status in LAVA Dispatcher:
> New
>
> Bug description:
> Steps to reproduce:
>
> 1) Connect two Galaxy Nexus devices to LAVA server
>
> 2) Make sure units are in fastboot mode with boot partition erased.
>
> 3) Schedule two of these jobs:
> http://bazaar.launchpad.net/~terceiro/+junk/lava-dev/view/head:/jobs
> /nexus-boot-test.json
>
> 4) This should make the jobs run at approximately the same time, which
> will cause fastboot flashing to occur on both devices concurrently.
>
> 5) At this point fastboot hangs, and I get a flood of these messages
> in dmesg:
>
> usb 1-5: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt 128 rq 6 len
> 256 ret -71
>
> Thinking this might be a USB driver issues, I have tried this on three
> different machines, same result. Even build and installed the 3.6 and
> 3.7 kernels, no dice there.
>
> After all of this I think I need to put some resource protection on
> fastboot binary
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/lava-dispatcher/+bug/1110622/+subscriptions
>

On 01/31, Tyler Baker wrote:
> Hello Antonio,
>
> I am new to brz (coming from git) I have local development setup for the
> dispatcher at this point. How, in bzr can I merge your fastboot-flock
> branch on top of my local dispatcher changes? Once I get the code pulled I
> should be able to test it right away. Thanks for your help.

Tyler - bzr is quite different from git in how this is done. The easiest
way would be this:

1) make a new copy of this branch: bzr branch ....
2) go to /srv/lava/instances/<your instance>/code/current/local
3) remove the symlink to your current dispatcher branch
4) create a symlink to this new dispatcher branch
5) go to /srv/lava/instances/<your instance>/code/current
6) run ./bin/buildout

Ok I will try this ASAP. Thanks for all the help.

On Thu, Jan 31, 2013 at 9:48 AM, Andy Doan <email address hidden>wrote:

> On 01/31, Tyler Baker wrote:
> > Hello Antonio,
> >
> > I am new to brz (coming from git) I have local development setup for the
> > dispatcher at this point. How, in bzr can I merge your fastboot-flock
> > branch on top of my local dispatcher changes? Once I get the code pulled
> I
> > should be able to test it right away. Thanks for your help.
>
> Tyler - bzr is quite different from git in how this is done. The easiest
> way would be this:
>
> 1) make a new copy of this branch: bzr branch ....
> 2) go to /srv/lava/instances/<your instance>/code/current/local
> 3) remove the symlink to your current dispatcher branch
> 4) create a symlink to this new dispatcher branch
> 5) go to /srv/lava/instances/<your instance>/code/current
> 6) run ./bin/buildout
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1110622
>
> Title:
> Cannot flash multiple devices with fastboot
>
> Status in LAVA Dispatcher:
> New
>
> Bug description:
> Steps to reproduce:
>
> 1) Connect two Galaxy Nexus devices to LAVA server
>
> 2) Make sure units are in fastboot mode with boot partition erased.
>
> 3) Schedule two of these jobs:
> http://bazaar.launchpad.net/~terceiro/+junk/lava-dev/view/head:/jobs
> /nexus-boot-test.json
>
> 4) This should make the jobs run at approximately the same time, which
> will cause fastboot flashing to occur on both devices concurrently.
>
> 5) At this point fastboot hangs, and I get a flood of these messages
> in dmesg:
>
> usb 1-5: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt 128 rq 6 len
> 256 ret -71
>
> Thinking this might be a USB driver issues, I have tried this on three
> different machines, same result. Even build and installed the 3.6 and
> 3.7 kernels, no dice there.
>
> After all of this I think I need to put some resource protection on
> fastboot binary
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/lava-dispatcher/+bug/1110622/+subscriptions
>

Looks like it didn't fix the issue :\

[ 8728.084120] usb 2-3.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
128 rq 6 len 254 ret -110
[ 8728.136114] usb 2-6.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
128 rq 6 len 254 ret -110
[ 8729.188123] usb 2-3.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
128 rq 6 len 254 ret -110
[ 8729.240114] usb 2-6.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
128 rq 6 len 254 ret -110
[ 8730.292122] usb 2-3.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
128 rq 6 len 254 ret -110
[ 8730.344114] usb 2-6.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
128 rq 6 len 254 ret -110
[ 8731.396121] usb 2-3.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
128 rq 6 len 254 ret -110
[ 8731.448114] usb 2-6.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
128 rq 6 len 254 ret -110
lava@Volcano:~/lava_files/lava-dispatcher_old/lava_dispatcher/device$ sudo
fastboot devices
???????????? fastboot
???????????? fastboot
0151686C0601301E fastboot
0155F7FA10017008 fastboot

On Thu, Jan 31, 2013 at 10:05 AM, forcedinductionz <
<email address hidden>> wrote:

> Ok I will try this ASAP. Thanks for all the help.
>
>
> On Thu, Jan 31, 2013 at 9:48 AM, Andy Doan <email address hidden>wrote:
>
>> On 01/31, Tyler Baker wrote:
>> > Hello Antonio,
>> >
>> > I am new to brz (coming from git) I have local development setup for the
>> > dispatcher at this point. How, in bzr can I merge your fastboot-flock
>> > branch on top of my local dispatcher changes? Once I get the code
>> pulled I
>> > should be able to test it right away. Thanks for your help.
>>
>> Tyler - bzr is quite different from git in how this is done. The easiest
>> way would be this:
>>
>> 1) make a new copy of this branch: bzr branch ....
>> 2) go to /srv/lava/instances/<your instance>/code/current/local
>> 3) remove the symlink to your current dispatcher branch
>> 4) create a symlink to this new dispatcher branch
>> 5) go to /srv/lava/instances/<your instance>/code/current
>> 6) run ./bin/buildout
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1110622
>>
>> Title:
>> Cannot flash multiple devices with fastboot
>>
>> Status in LAVA Dispatcher:
>> New
>>
>> Bug description:
>> Steps to reproduce:
>>
>> 1) Connect two Galaxy Nexus devices to LAVA server
>>
>> 2) Make sure units are in fastboot mode with boot partition erased.
>>
>> 3) Schedule two of these jobs:
>> http://bazaar.launchpad.net/~terceiro/+junk/lava-dev/view/head:/jobs
>> /nexus-boot-test.json
>>
>> 4) This should make the jobs run at approximately the same time, which
>> will cause fastboot flashing to occur on both devices concurrently.
>>
>> 5) At this point fastboot hangs, and I get a flood of these messages
>> in dmesg:
>>
>> usb 1-5: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt 128 rq 6 len
>> 256 ret -71
>>
>> Thinking this might be a USB driver issues, I have tried this on three
>> different machines, same result. Even build and installed the 3.6 and
>> 3.7 kernels, no dice there.
>>
>> After all of this I think I need to put some resource protect...

Looks like the fix is to flock ever fastboot call.

On Thu, Jan 31, 2013 at 12:16 PM, forcedinductionz <
<email address hidden>> wrote:

> Looks like it didn't fix the issue :\
>
> [ 8728.084120] usb 2-3.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
> 128 rq 6 len 254 ret -110
> [ 8728.136114] usb 2-6.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
> 128 rq 6 len 254 ret -110
> [ 8729.188123] usb 2-3.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
> 128 rq 6 len 254 ret -110
> [ 8729.240114] usb 2-6.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
> 128 rq 6 len 254 ret -110
> [ 8730.292122] usb 2-3.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
> 128 rq 6 len 254 ret -110
> [ 8730.344114] usb 2-6.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
> 128 rq 6 len 254 ret -110
> [ 8731.396121] usb 2-3.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
> 128 rq 6 len 254 ret -110
> [ 8731.448114] usb 2-6.2: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt
> 128 rq 6 len 254 ret -110
> lava@Volcano:~/lava_files/lava-dispatcher_old/lava_dispatcher/device$
> sudo fastboot devices
> ???????????? fastboot
> ???????????? fastboot
> 0151686C0601301E fastboot
> 0155F7FA10017008 fastboot
>
>
>
> On Thu, Jan 31, 2013 at 10:05 AM, forcedinductionz <
> <email address hidden>> wrote:
>
>> Ok I will try this ASAP. Thanks for all the help.
>>
>>
>> On Thu, Jan 31, 2013 at 9:48 AM, Andy Doan <email address hidden>wrote:
>>
>>> On 01/31, Tyler Baker wrote:
>>> > Hello Antonio,
>>> >
>>> > I am new to brz (coming from git) I have local development setup for
>>> the
>>> > dispatcher at this point. How, in bzr can I merge your fastboot-flock
>>> > branch on top of my local dispatcher changes? Once I get the code
>>> pulled I
>>> > should be able to test it right away. Thanks for your help.
>>>
>>> Tyler - bzr is quite different from git in how this is done. The easiest
>>> way would be this:
>>>
>>> 1) make a new copy of this branch: bzr branch ....
>>> 2) go to /srv/lava/instances/<your instance>/code/current/local
>>> 3) remove the symlink to your current dispatcher branch
>>> 4) create a symlink to this new dispatcher branch
>>> 5) go to /srv/lava/instances/<your instance>/code/current
>>> 6) run ./bin/buildout
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1110622
>>>
>>> Title:
>>> Cannot flash multiple devices with fastboot
>>>
>>> Status in LAVA Dispatcher:
>>> New
>>>
>>> Bug description:
>>> Steps to reproduce:
>>>
>>> 1) Connect two Galaxy Nexus devices to LAVA server
>>>
>>> 2) Make sure units are in fastboot mode with boot partition erased.
>>>
>>> 3) Schedule two of these jobs:
>>> http://bazaar.launchpad.net/~terceiro/+junk/lava-dev/view/head:/jobs
>>> /nexus-boot-test.json
>>>
>>> 4) This should make the jobs run at approximately the same time, which
>>> will cause fastboot flashing to occur on both devices concurrently.
>>>
>>> 5) At this point fastboot hangs, and I get a flood of these messages
>>> in dmesg:
>>>
>>> usb 1-5: usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt 128 rq 6 len
>>> 256 ret -71
>>...