From: Rob R. <rob...@gm...> - 2012-04-04 23:58:53
|
The new FPGA image did not help. I compiled the monotonic-test branch, which gives me no errors when running. On the main branch I still get: transceiver: ERR 3033262912 UHDDevice.cpp:770:recv_async_msg: Packet time was too late or too early at 0.165587 sec. Apr 4 19:49:16 vonnegut transceiver: ERR 3033262912 UHDDevice.cpp:770:recv_async_msg: Packet time was too late or too early at 0.165654 sec. Apr 4 19:49:20 vonnegut transceiver: ERR 3033262912 UHDDevice.cpp:770:recv_async_msg: An internal send buffer has emptied at 4.34265 sec. ... I see no errors corresponding to monotonic time. Is this a different issue then? Rob On Wed, Apr 4, 2012 at 4:47 PM, Ben Hilburn <ben...@et...> wrote: > Arghyadip - > > Thanks for trying the new images and getting back to us. Have you tried > Tom's branch yet? > > "Please try this branch and post the log output. Don't bother testing > it with a handset because nothing is transmitted. Receive burst > processing is disabled too. The idea is to cut transceiver down to > (almost) a bare receive loop and see if the timestamp errors persist. > > git clone -b monotonic-test git://github.com/ttsou/openbts-p2.8.git > " > > Cheers, > Ben > ---------------------------- > Ben Hilburn <http://goo.gl/5DdZ3> @ Ettus Research, LLC<http://www.ettus.com/> > > > > On Wed, Apr 4, 2012 at 1:16 PM, Arghyadip Paul <arg...@gm...>wrote: > >> Hi Ben, >> >> The newest fpga/firmware does not help. >> >> Logs: >> ------- >> OpenBTS> ALERT 3053259632 UHDDevice.cpp:612:check_rx_md_err: UHD: Loss >> of monotonic time >> ALERT 3053259632 UHDDevice.cpp:613:check_rx_md_err: Current time: >> 4.95721, Previous time: 5.19495 >> ALERT 3053259632 UHDDevice.cpp:612:check_rx_md_err: UHD: Loss of >> monotonic time >> ALERT 3053259632 UHDDevice.cpp:613:check_rx_md_err: Current time: >> 5.05081, Previous time: 5.19495 >> ALERT 3053259632 UHDDevice.cpp:612:check_rx_md_err: UHD: Loss of >> monotonic time >> ALERT 3053259632 UHDDevice.cpp:613:check_rx_md_err: Current time: >> 5.14628, Previous time: 5.19495 >> ALERT 3053259632 UHDDevice.cpp:741:writeSamples: UHD: Device send timed >> out >> ALERT 3053259632 UHDDevice.cpp:742:writeSamples: UHD: Version >> 003.004.000-24-g8630807c >> ALERT 3053259632 UHDDevice.cpp:743:writeSamples: UHD: Unrecoverable >> error, exiting... >> EMERG 3069496176 OpenBTS.cpp:131:startTransceiver: Transceiver quit >> with status 65280. Exiting. >> >> >> On Tue, Apr 3, 2012 at 4:41 PM, Ben Hilburn <ben...@et...> >> wrote: >> > We just pushed a new FPGA image for the B100 that fixes something >> regarding >> > packet handling. >> > >> > Will anyone having this issue please try this and let us know if it has >> any >> > effect? >> > >> > http://files.ettus.com/binaries/master_images/ >> > >> > If it doesn't work, will you please follow Tom's instructions above so >> we >> > can track this down? >> > >> > " >> > Please try this branch and post the log output. Don't bother testing >> > it with a handset because nothing is transmitted. Receive burst >> > processing is disabled too. The idea is to cut transceiver down to >> > (almost) a bare receive loop and see if the timestamp errors persist. >> > >> > git clone -b monotonic-test git://github.com/ttsou/openbts-p2.8.git >> > " >> > >> > Cheers, >> > Ben >> > ---------------------------- >> > Ben Hilburn @ Ettus Research, LLC >> > >> > >> > >> > On Mon, Apr 2, 2012 at 11:11 AM, Thomas Tsou <tt...@vt...> wrote: >> >> >> >> Hi Rob, >> >> >> >> On Sat, Mar 31, 2012 at 5:32 AM, Rob Rhinehart >> >> <rob...@gm...> wrote: >> >> > Mar 31 05:25:20 vonnegut transceiver: ERR 3034041152 >> >> > UHDDevice.cpp:770:recv_async_msg: Packet time was too late or too >> early >> >> > at >> >> > 20.4277 sec. >> >> > Mar 31 05:25:20 vonnegut transceiver: ERR 3034041152 >> >> > UHDDevice.cpp:770:recv_async_msg: Packet time was too late or too >> early >> >> > at >> >> > 20.4278 sec. >> >> >> >> Thanks for providing feedback to this issue. Can you confirm that you >> >> are seeing the following critical errors? >> >> >> >> check_rx_md_err: UHD: Loss of monotonic time >> >> check_rx_md_err: Current time: 4.95721, Previous time: 5.19495 >> >> check_rx_md_err: UHD: Loss of monotonic time >> >> check_rx_md_err: Current time: 5.05081, Previous time: 5.19495 >> >> check_rx_md_err: UHD: Loss of monotonic time >> >> check_rx_md_err: Current time: 5.14628, Previous time: 5.19495 >> >> >> >> > I compiled and ran the 'monotonic' branch. The error is now gone. I >> am >> >> > new >> >> > to the USRP and would like to help debug the issue. What are the next >> >> > steps? >> >> >> >> Also to clarify, was this the 'monotonic' or 'monotonic-test' branch? >> >> >> >> Thomas >> > >> > >> > >> > >> ------------------------------------------------------------------------------ >> > Better than sec? Nothing is better than sec when it comes to >> > monitoring Big Data applications. Try Boundary one-second >> > resolution app monitoring today. Free. >> > http://p.sf.net/sfu/Boundary-dev2dev >> > _______________________________________________ >> > Openbts-discuss mailing list >> > Ope...@li... >> > https://lists.sourceforge.net/lists/listinfo/openbts-discuss >> > >> >> >> >> -- >> Arghyadip Paul >> Graduate Student >> Department of Computer Science >> University of California Santa Barbara >> Santa Barbara , CA 93106 USA >> > > > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > > |