Re: [casper] Problem when programming ROACH2

[David MacMahon]

Just to add some more details to the problems seen at NRAO, it turns out that 
some of the uBoot settings passed a "mem=" command line option to the Linux 
kernel, where  was actually greater than the amount of RAM available.  It 
seems that the memory allocator would not reclaim the memory used during BOF 
programming since it thought there was still plenty available.  When it went to 
use memory beyond the actual memory available, but within , the system 
would crash.  The fix we used at the time was to change  to  in the 
uBoot environment, where  was the actual memory available (or maybe we just 
did away with the "mem=" altogether?).

At any rate, I'm glad you got it working now!

Cheers,
Dave

> On Aug 10, 2018, at 08:48, John Ford  > wrote:
> 
> Hi Raimondo,
> 
> We saw this years ago at NRAO.  Marc is right about the solution.
> 
> John
> 
> On Fri, Aug 10, 2018 at 7:20 AM, Marc Welz  > wrote:
> As per previous email: Either start it again, or upgrade it
> 
> regards
> 
> marc
> 
> 
> On Fri, Aug 10, 2018 at 12:45 PM, Concu, Raimondo
> mailto:raimondo.co...@inaf.it>> wrote:
> > Hi Mark,
> >
> > Hi everyone,
> >
> > maybe you're right
> >
> > when the problem happens
> >
> > and i restart tcpborphserver3, the problem disappears.
> >
> > and this is the output:
> >
> > root@192:~# ps -ALL | grep tcp
> >   820   820 ?00:00:53 tcpborphserver3
> > root@192:~# kill 820
> > root@192:~#
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> >
> >
> >
> > Any suggestions?
> >
> > Thanks in advance
> > Raimondo
> >
> >
> > 2018-08-10 13:46 GMT+02:00 Marc Welz  > >:
> >>
> >> Hello
> >>
> >>
> >> The "raw unable\_to\_map\_file\_/dev/roach/mem:\_Cannot\_allocate\_memory"
> >> is the interesting line. I suspect you are running a slightly older
> >> version of the filesystem or romfs which had a bug where it didn't
> >> unmap the previous image, and so suffered address space exhaustion
> >> after a dozen or so programs. The quick way to solve this is to reboot
> >> occasionally, the long term solution is to program a newer 

Re: [casper] Problem when programming ROACH2

[Marc Welz]

Excellent!

regards

marc




On Mon, Aug 13, 2018 at 10:19 AM, Concu, Raimondo
 wrote:
> Hi Mark,
>
> I replaced tcpborphserver3 with tcpborphserver3-unmap.
>
> I have programmed the roach2 100 + 400 times ... without problems
>
> We had an old version of tcpborphserver3
>
> Now we have a SARDARA reconfigurable many times ;-) and then permanently
> offered to the astronomers at SRT ...
>
> Problem solved
>
> Thanks again!
>
> 2018-08-13 11:24 GMT+02:00 Concu, Raimondo :
>>
>> I meant between versions,
>>
>>  but I read that: "New tcpborphserver3: fixes unmap issue when programming
>> boffiles" ,
>>
>> could be our case.
>>
>> It is being tested ...
>>
>> 2018-08-13 10:59 GMT+02:00 Marc Welz :
>>>
>>> The one is a symbolic link to the other
>>>
>>> regards
>>>
>>> marc
>>>
>>>
>>> On Mon, Aug 13, 2018 at 8:56 AM, Raimondo Concu 
>>> wrote:
>>> > Yes Mark!
>>> >
>>> > I had already seen this link.
>>> >
>>> > What is the difference between tcpborphserver3 and
>>> > tcpborphserver3-unmap?
>>> >
>>> > Thank You!
>>> > Raimondo
>>> >
>>> > Il Lun 13 Ago 2018, 10:00 Marc Welz  ha scritto:
>>> >>
>>> >> On Fri, Aug 10, 2018 at 5:51 PM, John Ford  wrote:
>>> >> > That depends where the image lives.  If it is on an NFS mounted disk
>>> >> > somewhere, you have to install the new kernel and file system there.
>>> >> > If
>>> >> > on
>>> >> > the flash, you have to install it on the flash.
>>> >> >
>>> >> > THe latest stuff ought to be here (Marc is it so?)
>>> >>
>>> >> Hmm... those look like they are roach1 related.
>>> >>
>>> >> Rather have a look in
>>> >>
>>> >> https://github.com/ska-sa/roach2_nfs_uboot/
>>> >>
>>> >> In particular the executable boot/tcpborphserver3
>>> >>
>>> >> regards
>>> >>
>>> >> marc
>>> >>
>>> >> --
>>> >> You received this message because you are subscribed to the Google
>>> >> Groups
>>> >> "casper@lists.berkeley.edu" group.
>>> >> To unsubscribe from this group and stop receiving emails from it, send
>>> >> an
>>> >> email to casper+unsubscr...@lists.berkeley.edu.
>>> >> To post to this group, send email to casper@lists.berkeley.edu.
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups
>>> > "casper@lists.berkeley.edu" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send
>>> > an
>>> > email to casper+unsubscr...@lists.berkeley.edu.
>>> > To post to this group, send email to casper@lists.berkeley.edu.
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "casper@lists.berkeley.edu" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to casper+unsubscr...@lists.berkeley.edu.
>>> To post to this group, send email to casper@lists.berkeley.edu.
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To post to this group, send email to casper@lists.berkeley.edu.

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To post to this group, send email to casper@lists.berkeley.edu.

Re: [casper] Problem when programming ROACH2

[Concu, Raimondo]

Hi Mark,

I replaced tcpborphserver3 with tcpborphserver3-unmap.

I have programmed the roach2 100 + 400 times ... without problems

We had an old version of tcpborphserver3

Now we have a SARDARA reconfigurable many times ;-) and then permanently
offered to the astronomers at SRT ...

Problem solved

Thanks again!

2018-08-13 11:24 GMT+02:00 Concu, Raimondo :

> I meant between versions,
>
>  but I read that: "New tcpborphserver3: fixes unmap issue when programming
> boffiles" ,
>
> could be our case.
>
> It is being tested ...
>
> 2018-08-13 10:59 GMT+02:00 Marc Welz :
>
>> The one is a symbolic link to the other
>>
>> regards
>>
>> marc
>>
>>
>> On Mon, Aug 13, 2018 at 8:56 AM, Raimondo Concu 
>> wrote:
>> > Yes Mark!
>> >
>> > I had already seen this link.
>> >
>> > What is the difference between tcpborphserver3 and
>> tcpborphserver3-unmap?
>> >
>> > Thank You!
>> > Raimondo
>> >
>> > Il Lun 13 Ago 2018, 10:00 Marc Welz  ha scritto:
>> >>
>> >> On Fri, Aug 10, 2018 at 5:51 PM, John Ford  wrote:
>> >> > That depends where the image lives.  If it is on an NFS mounted disk
>> >> > somewhere, you have to install the new kernel and file system
>> there.  If
>> >> > on
>> >> > the flash, you have to install it on the flash.
>> >> >
>> >> > THe latest stuff ought to be here (Marc is it so?)
>> >>
>> >> Hmm... those look like they are roach1 related.
>> >>
>> >> Rather have a look in
>> >>
>> >> https://github.com/ska-sa/roach2_nfs_uboot/
>> >>
>> >> In particular the executable boot/tcpborphserver3
>> >>
>> >> regards
>> >>
>> >> marc
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> Groups
>> >> "casper@lists.berkeley.edu" group.
>> >> To unsubscribe from this group and stop receiving emails from it, send
>> an
>> >> email to casper+unsubscr...@lists.berkeley.edu.
>> >> To post to this group, send email to casper@lists.berkeley.edu.
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups
>> > "casper@lists.berkeley.edu" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an
>> > email to casper+unsubscr...@lists.berkeley.edu.
>> > To post to this group, send email to casper@lists.berkeley.edu.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "casper@lists.berkeley.edu" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to casper+unsubscr...@lists.berkeley.edu.
>> To post to this group, send email to casper@lists.berkeley.edu.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To post to this group, send email to casper@lists.berkeley.edu.

Re: [casper] Problem when programming ROACH2

[Concu, Raimondo]

I meant between versions,

 but I read that: "New tcpborphserver3: fixes unmap issue when programming
boffiles" ,

could be our case.

It is being tested ...

2018-08-13 10:59 GMT+02:00 Marc Welz :

> The one is a symbolic link to the other
>
> regards
>
> marc
>
>
> On Mon, Aug 13, 2018 at 8:56 AM, Raimondo Concu 
> wrote:
> > Yes Mark!
> >
> > I had already seen this link.
> >
> > What is the difference between tcpborphserver3 and tcpborphserver3-unmap?
> >
> > Thank You!
> > Raimondo
> >
> > Il Lun 13 Ago 2018, 10:00 Marc Welz  ha scritto:
> >>
> >> On Fri, Aug 10, 2018 at 5:51 PM, John Ford  wrote:
> >> > That depends where the image lives.  If it is on an NFS mounted disk
> >> > somewhere, you have to install the new kernel and file system there.
> If
> >> > on
> >> > the flash, you have to install it on the flash.
> >> >
> >> > THe latest stuff ought to be here (Marc is it so?)
> >>
> >> Hmm... those look like they are roach1 related.
> >>
> >> Rather have a look in
> >>
> >> https://github.com/ska-sa/roach2_nfs_uboot/
> >>
> >> In particular the executable boot/tcpborphserver3
> >>
> >> regards
> >>
> >> marc
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "casper@lists.berkeley.edu" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an
> >> email to casper+unsubscr...@lists.berkeley.edu.
> >> To post to this group, send email to casper@lists.berkeley.edu.
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "casper@lists.berkeley.edu" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to casper+unsubscr...@lists.berkeley.edu.
> > To post to this group, send email to casper@lists.berkeley.edu.
>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To post to this group, send email to casper@lists.berkeley.edu.
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To post to this group, send email to casper@lists.berkeley.edu.

Re: [casper] Problem when programming ROACH2

[Marc Welz]

The one is a symbolic link to the other

regards

marc


On Mon, Aug 13, 2018 at 8:56 AM, Raimondo Concu  wrote:
> Yes Mark!
>
> I had already seen this link.
>
> What is the difference between tcpborphserver3 and tcpborphserver3-unmap?
>
> Thank You!
> Raimondo
>
> Il Lun 13 Ago 2018, 10:00 Marc Welz  ha scritto:
>>
>> On Fri, Aug 10, 2018 at 5:51 PM, John Ford  wrote:
>> > That depends where the image lives.  If it is on an NFS mounted disk
>> > somewhere, you have to install the new kernel and file system there.  If
>> > on
>> > the flash, you have to install it on the flash.
>> >
>> > THe latest stuff ought to be here (Marc is it so?)
>>
>> Hmm... those look like they are roach1 related.
>>
>> Rather have a look in
>>
>> https://github.com/ska-sa/roach2_nfs_uboot/
>>
>> In particular the executable boot/tcpborphserver3
>>
>> regards
>>
>> marc
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "casper@lists.berkeley.edu" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to casper+unsubscr...@lists.berkeley.edu.
>> To post to this group, send email to casper@lists.berkeley.edu.
>
> --
> You received this message because you are subscribed to the Google Groups
> "casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To post to this group, send email to casper@lists.berkeley.edu.

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To post to this group, send email to casper@lists.berkeley.edu.

Re: [casper] Problem when programming ROACH2

[Marc Welz]

On Fri, Aug 10, 2018 at 5:51 PM, John Ford  wrote:
> That depends where the image lives.  If it is on an NFS mounted disk
> somewhere, you have to install the new kernel and file system there.  If on
> the flash, you have to install it on the flash.
>
> THe latest stuff ought to be here (Marc is it so?)

Hmm... those look like they are roach1 related.

Rather have a look in

https://github.com/ska-sa/roach2_nfs_uboot/

In particular the executable boot/tcpborphserver3

regards

marc

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To post to this group, send email to casper@lists.berkeley.edu.

Re: [casper] Problem when programming ROACH2

[Raimondo Concu]

Thank you John!

We use NFS procedure, but certainly an old version.

Cheers
Raimondo


Il 10 Ago 2018 19:52, "John Ford"  ha scritto:

That depends where the image lives.  If it is on an NFS mounted disk
somewhere, you have to install the new kernel and file system there.  If on
the flash, you have to install it on the flash.

THe latest stuff ought to be here (Marc is it so?)
https://casper.berkeley.edu/wiki/LatestVersions


To put it on NFS, here's some info...
https://casper.berkeley.edu/wiki/ROACH_NFS_guide

To put it on flash, try this:
https://casper.berkeley.edu/wiki/ROACH_kernel_uboot_update

It's been a while since I have done this, so...

Good luck!

You should browse the mailing list archive for more on how to do this.

John


On Fri, Aug 10, 2018 at 9:12 AM, Raimondo Concu 
wrote:

> Hi John,
>
> How do I update it?
>
> Thanks
> Raimondo
>
>
> Il Ven 10 Ago 2018, 17:48 John Ford  ha scritto:
>
>> Hi Raimondo,
>>
>> We saw this years ago at NRAO.  Marc is right about the solution.
>>
>> John
>>
>> On Fri, Aug 10, 2018 at 7:20 AM, Marc Welz  wrote:
>>
>>> As per previous email: Either start it again, or upgrade it
>>>
>>> regards
>>>
>>> marc
>>>
>>>
>>> On Fri, Aug 10, 2018 at 12:45 PM, Concu, Raimondo
>>>  wrote:
>>> > Hi Mark,
>>> >
>>> > Hi everyone,
>>> >
>>> > maybe you're right
>>> >
>>> > when the problem happens
>>> >
>>> > and i restart tcpborphserver3, the problem disappears.
>>> >
>>> > and this is the output:
>>> >
>>> > root@192:~# ps -ALL | grep tcp
>>> >   820   820 ?00:00:53 tcpborphserver3
>>> > root@192:~# kill 820
>>> > root@192:~#
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> >
>>> >
>>> >
>>> > Any suggestions?
>>> >
>>> > Thanks in advance
>>> > Raimondo
>>> >
>>> >
>>> > 2018-08-10 13:46 GMT+02:00 Marc Welz :
>>> >>
>>> >> Hello
>>> >>
>>> >>
>>> >> The "raw
>>> unable\_to\_map\_file\_/dev/roach/mem:\_Cannot\_allocate\_memory"
>>> >> is 

Re: [casper] Problem when programming ROACH2

[John Ford]

That depends where the image lives.  If it is on an NFS mounted disk
somewhere, you have to install the new kernel and file system there.  If on
the flash, you have to install it on the flash.

THe latest stuff ought to be here (Marc is it so?)
https://casper.berkeley.edu/wiki/LatestVersions


To put it on NFS, here's some info...
https://casper.berkeley.edu/wiki/ROACH_NFS_guide

To put it on flash, try this:
https://casper.berkeley.edu/wiki/ROACH_kernel_uboot_update

It's been a while since I have done this, so...

Good luck!

You should browse the mailing list archive for more on how to do this.

John


On Fri, Aug 10, 2018 at 9:12 AM, Raimondo Concu 
wrote:

> Hi John,
>
> How do I update it?
>
> Thanks
> Raimondo
>
>
> Il Ven 10 Ago 2018, 17:48 John Ford  ha scritto:
>
>> Hi Raimondo,
>>
>> We saw this years ago at NRAO.  Marc is right about the solution.
>>
>> John
>>
>> On Fri, Aug 10, 2018 at 7:20 AM, Marc Welz  wrote:
>>
>>> As per previous email: Either start it again, or upgrade it
>>>
>>> regards
>>>
>>> marc
>>>
>>>
>>> On Fri, Aug 10, 2018 at 12:45 PM, Concu, Raimondo
>>>  wrote:
>>> > Hi Mark,
>>> >
>>> > Hi everyone,
>>> >
>>> > maybe you're right
>>> >
>>> > when the problem happens
>>> >
>>> > and i restart tcpborphserver3, the problem disappears.
>>> >
>>> > and this is the output:
>>> >
>>> > root@192:~# ps -ALL | grep tcp
>>> >   820   820 ?00:00:53 tcpborphserver3
>>> > root@192:~# kill 820
>>> > root@192:~#
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> > roach VMA close
>>> > roach release mem called
>>> >
>>> >
>>> >
>>> > Any suggestions?
>>> >
>>> > Thanks in advance
>>> > Raimondo
>>> >
>>> >
>>> > 2018-08-10 13:46 GMT+02:00 Marc Welz :
>>> >>
>>> >> Hello
>>> >>
>>> >>
>>> >> The "raw unable\_to\_map\_file\_/dev/roach/mem:\_Cannot\_allocate\_
>>> memory"
>>> >> is the interesting line. I suspect you are running a slightly older
>>> >> version of the filesystem or romfs which had a bug where it 

Re: [casper] Problem when programming ROACH2

[Raimondo Concu]

Hi John,

How do I update it?

Thanks
Raimondo

Il Ven 10 Ago 2018, 17:48 John Ford  ha scritto:

> Hi Raimondo,
>
> We saw this years ago at NRAO.  Marc is right about the solution.
>
> John
>
> On Fri, Aug 10, 2018 at 7:20 AM, Marc Welz  wrote:
>
>> As per previous email: Either start it again, or upgrade it
>>
>> regards
>>
>> marc
>>
>>
>> On Fri, Aug 10, 2018 at 12:45 PM, Concu, Raimondo
>>  wrote:
>> > Hi Mark,
>> >
>> > Hi everyone,
>> >
>> > maybe you're right
>> >
>> > when the problem happens
>> >
>> > and i restart tcpborphserver3, the problem disappears.
>> >
>> > and this is the output:
>> >
>> > root@192:~# ps -ALL | grep tcp
>> >   820   820 ?00:00:53 tcpborphserver3
>> > root@192:~# kill 820
>> > root@192:~#
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> > roach VMA close
>> > roach release mem called
>> >
>> >
>> >
>> > Any suggestions?
>> >
>> > Thanks in advance
>> > Raimondo
>> >
>> >
>> > 2018-08-10 13:46 GMT+02:00 Marc Welz :
>> >>
>> >> Hello
>> >>
>> >>
>> >> The "raw
>> unable\_to\_map\_file\_/dev/roach/mem:\_Cannot\_allocate\_memory"
>> >> is the interesting line. I suspect you are running a slightly older
>> >> version of the filesystem or romfs which had a bug where it didn't
>> >> unmap the previous image, and so suffered address space exhaustion
>> >> after a dozen or so programs. The quick way to solve this is to reboot
>> >> occasionally, the long term solution is to program a newer version of
>> >> the romfs (in particular tcpborphserver)
>> >>
>> >> regards
>> >>
>> >> marc
>> >>
>> >>
>> >> On Fri, Aug 10, 2018 at 10:17 AM, Concu, Raimondo
>> >>  wrote:
>> >> > Hi Everyone,
>> >> >
>> >> > I have a problem when programming the board after a certain number of
>> >> > times
>> >> > (30 - 60),
>> >> >
>> >> > as you can see in the following log:
>> >> >
>> >> > DEBUG:katcp:Starting thread Thread-1
>> >> > 2018-08-10 11:04:15,203--client--DEBUG: Starting thread Thread-1
>> >> > DEBUG:katcp:#version alpha-6-g0b8dd54
>> >> > 2018-08-10 11:04:15,206--client--DEBUG: #version alpha-6-g0b8dd54
>> >> > 

Re: [casper] Problem when programming ROACH2

[John Ford]

Hi Raimondo,

We saw this years ago at NRAO.  Marc is right about the solution.

John

On Fri, Aug 10, 2018 at 7:20 AM, Marc Welz  wrote:

> As per previous email: Either start it again, or upgrade it
>
> regards
>
> marc
>
>
> On Fri, Aug 10, 2018 at 12:45 PM, Concu, Raimondo
>  wrote:
> > Hi Mark,
> >
> > Hi everyone,
> >
> > maybe you're right
> >
> > when the problem happens
> >
> > and i restart tcpborphserver3, the problem disappears.
> >
> > and this is the output:
> >
> > root@192:~# ps -ALL | grep tcp
> >   820   820 ?00:00:53 tcpborphserver3
> > root@192:~# kill 820
> > root@192:~#
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> > roach VMA close
> > roach release mem called
> >
> >
> >
> > Any suggestions?
> >
> > Thanks in advance
> > Raimondo
> >
> >
> > 2018-08-10 13:46 GMT+02:00 Marc Welz :
> >>
> >> Hello
> >>
> >>
> >> The "raw unable\_to\_map\_file\_/dev/roach/mem:\_Cannot\_allocate\_
> memory"
> >> is the interesting line. I suspect you are running a slightly older
> >> version of the filesystem or romfs which had a bug where it didn't
> >> unmap the previous image, and so suffered address space exhaustion
> >> after a dozen or so programs. The quick way to solve this is to reboot
> >> occasionally, the long term solution is to program a newer version of
> >> the romfs (in particular tcpborphserver)
> >>
> >> regards
> >>
> >> marc
> >>
> >>
> >> On Fri, Aug 10, 2018 at 10:17 AM, Concu, Raimondo
> >>  wrote:
> >> > Hi Everyone,
> >> >
> >> > I have a problem when programming the board after a certain number of
> >> > times
> >> > (30 - 60),
> >> >
> >> > as you can see in the following log:
> >> >
> >> > DEBUG:katcp:Starting thread Thread-1
> >> > 2018-08-10 11:04:15,203--client--DEBUG: Starting thread Thread-1
> >> > DEBUG:katcp:#version alpha-6-g0b8dd54
> >> > 2018-08-10 11:04:15,206--client--DEBUG: #version alpha-6-g0b8dd54
> >> > DEBUG:katcp:#build-state 2012-10-24T10:04:56
> >> > 2018-08-10 11:04:15,206--client--DEBUG: #build-state
> 2012-10-24T10:04:56
> >> > DEBUG:katcp:#version-connect katcp-library alpha-6-g0b8dd54
> >> > 2012-10-24T10:04:56
> >> > 2018-08-10 11:04:15,206--client--DEBUG: #version-connect katcp-library
> >> > 

Re: [casper] Problem when programming ROACH2

[Marc Welz]

As per previous email: Either start it again, or upgrade it

regards

marc


On Fri, Aug 10, 2018 at 12:45 PM, Concu, Raimondo
 wrote:
> Hi Mark,
>
> Hi everyone,
>
> maybe you're right
>
> when the problem happens
>
> and i restart tcpborphserver3, the problem disappears.
>
> and this is the output:
>
> root@192:~# ps -ALL | grep tcp
>   820   820 ?00:00:53 tcpborphserver3
> root@192:~# kill 820
> root@192:~#
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
> roach VMA close
> roach release mem called
>
>
>
> Any suggestions?
>
> Thanks in advance
> Raimondo
>
>
> 2018-08-10 13:46 GMT+02:00 Marc Welz :
>>
>> Hello
>>
>>
>> The "raw unable\_to\_map\_file\_/dev/roach/mem:\_Cannot\_allocate\_memory"
>> is the interesting line. I suspect you are running a slightly older
>> version of the filesystem or romfs which had a bug where it didn't
>> unmap the previous image, and so suffered address space exhaustion
>> after a dozen or so programs. The quick way to solve this is to reboot
>> occasionally, the long term solution is to program a newer version of
>> the romfs (in particular tcpborphserver)
>>
>> regards
>>
>> marc
>>
>>
>> On Fri, Aug 10, 2018 at 10:17 AM, Concu, Raimondo
>>  wrote:
>> > Hi Everyone,
>> >
>> > I have a problem when programming the board after a certain number of
>> > times
>> > (30 - 60),
>> >
>> > as you can see in the following log:
>> >
>> > DEBUG:katcp:Starting thread Thread-1
>> > 2018-08-10 11:04:15,203--client--DEBUG: Starting thread Thread-1
>> > DEBUG:katcp:#version alpha-6-g0b8dd54
>> > 2018-08-10 11:04:15,206--client--DEBUG: #version alpha-6-g0b8dd54
>> > DEBUG:katcp:#build-state 2012-10-24T10:04:56
>> > 2018-08-10 11:04:15,206--client--DEBUG: #build-state 2012-10-24T10:04:56
>> > DEBUG:katcp:#version-connect katcp-library alpha-6-g0b8dd54
>> > 2012-10-24T10:04:56
>> > 2018-08-10 11:04:15,206--client--DEBUG: #version-connect katcp-library
>> > alpha-6-g0b8dd54 2012-10-24T10:04:56
>> > DEBUG:katcp:#version-connect katcp-protocol 4.9-M
>> > 2018-08-10 11:04:15,207--client--DEBUG: #version-connect katcp-protocol
>> > 4.9-M
>> > DEBUG:katcp:#version-connect kernel 3.4.0-rc3+
>> > #14\_Tue\_May\_29\_17:05:02\_SAST\_2012
>> > 2018-08-10 11:04:15,207--client--DEBUG: #version-connect kernel
>> > 3.4.0-rc3+
>> > #14\_Tue\_May\_29\_17:05:02\_SAST\_2012
>> > DEBUG:katcp:?progdev 1024.bof
>> >
>> > 2018-08-10 11:04:16,206--client--DEBUG: ?progdev 1024.bof
>> >
>> > 

Re: [casper] Problem when programming ROACH2

[Concu, Raimondo]

Hi Mark,

Hi everyone,

maybe you're right

when the problem happens

and i restart tcpborphserver3, the problem disappears.

and this is the output:

root@192:~# ps -ALL | grep tcp
  820   820 ?00:00:53 tcpborphserver3
root@192:~# kill 820
root@192:~#
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called
roach VMA close
roach release mem called



Any suggestions?

Thanks in advance
Raimondo


2018-08-10 13:46 GMT+02:00 Marc Welz :

> Hello
>
>
> The "raw unable\_to\_map\_file\_/dev/roach/mem:\_Cannot\_allocate\_memory"
> is the interesting line. I suspect you are running a slightly older
> version of the filesystem or romfs which had a bug where it didn't
> unmap the previous image, and so suffered address space exhaustion
> after a dozen or so programs. The quick way to solve this is to reboot
> occasionally, the long term solution is to program a newer version of
> the romfs (in particular tcpborphserver)
>
> regards
>
> marc
>
>
> On Fri, Aug 10, 2018 at 10:17 AM, Concu, Raimondo
>  wrote:
> > Hi Everyone,
> >
> > I have a problem when programming the board after a certain number of
> times
> > (30 - 60),
> >
> > as you can see in the following log:
> >
> > DEBUG:katcp:Starting thread Thread-1
> > 2018-08-10 11:04:15,203--client--DEBUG: Starting thread Thread-1
> > DEBUG:katcp:#version alpha-6-g0b8dd54
> > 2018-08-10 11:04:15,206--client--DEBUG: #version alpha-6-g0b8dd54
> > DEBUG:katcp:#build-state 2012-10-24T10:04:56
> > 2018-08-10 11:04:15,206--client--DEBUG: #build-state 2012-10-24T10:04:56
> > DEBUG:katcp:#version-connect katcp-library alpha-6-g0b8dd54
> > 2012-10-24T10:04:56
> > 2018-08-10 11:04:15,206--client--DEBUG: #version-connect katcp-library
> > alpha-6-g0b8dd54 2012-10-24T10:04:56
> > DEBUG:katcp:#version-connect katcp-protocol 4.9-M
> > 2018-08-10 11:04:15,207--client--DEBUG: #version-connect katcp-protocol
> > 4.9-M
> > DEBUG:katcp:#version-connect kernel 3.4.0-rc3+
> > #14\_Tue\_May\_29\_17:05:02\_SAST\_2012
> > 2018-08-10 11:04:15,207--client--DEBUG: #version-connect kernel
> 3.4.0-rc3+
> > #14\_Tue\_May\_29\_17:05:02\_SAST\_2012
> > DEBUG:katcp:?progdev 1024.bof
> >
> > 2018-08-10 11:04:16,206--client--DEBUG: ?progdev 1024.bof
> >
> > DEBUG:katcp:#log info 1045321281687 raw attempting\_to\_program\_1024.
> bof
> > 2018-08-10 11:04:16,646--client--DEBUG: #log info 1045321281687 raw
> > attempting\_to\_program\_1024.bof
> > DEBUG:katcp:#log info 1045321281695 raw
> > attempting\_to\_program\_bitstream\_of\_19586188\_
> bytes\_to\_device\_/dev/roach/config
> > 2018-08-10 11:04:16,646--client--DEBUG: #log info 1045321281695 raw
> > attempting\_to\_program\_bitstream\_of\_19586188\_
>