Good day all,
Been working on a hashpipe with a pipeline of network, transposition and
then disk-dump threads. We have 24 data-buffers that we rotate through.
An inconsistent (happens after various amounts of time) crash occurs with
this printout:
-----------------------------------------------------
Tue Dec 15 17:37:19 2020 : Error (hashpipe_databuf_set_filled): semctl
error [Invalid argument]
Tue Dec 15 17:37:19 2020 : Error (hashpipe_databuf_wait_free_timeout):
semop error [Invalid argument]
semop: Invalid argument
Tue Dec 15 17:37:19 2020 : Error (hpguppi_atasnap_pktsock_thread): error
waiting for free databuf [Invalid argument]
Tue Dec 15 17:37:19 2020 : Error (hashpipe_databuf_set_free): semctl error
[Invalid argument]
Tue Dec 15 17:37:19 2020 : Error (hashpipe_databuf_wait_filled_timeout):
semop error [Invalid argument]
semop: Invalid argument
Tue Dec 15 17:37:19 2020 : Error (hpguppi_atasnap_pkt_to_FTP_transpose):
error waiting for input buffer, rv: -2 [Invalid argument]
-----------------------------------------------------------
If this looks at all familiar to anyone then let's tackle the issue at this
juncture. If not, then there is a little more to tell!
Other times an error is caught but no full printout from hashpipe_error()
is made:
Code calls:
++++++++++++++++++++++++++++
hpguppi_databuf_data(struct hpguppi_input_databuf *d, int block_id) {
if(block_id < 0 || d->header.n_block < block_id) {
hashpipe_error(__FUNCTION__,
"block_id %s out of range [0, %d)",
block_id, d->header.n_block);
return NULL;
....
++++++++++++++++++++++++++++
Printout:
============
Tue Dec 15 17:37:19 2020 : Error
(hpguppi_databuf_data)~/src/hpguppi_daq/src:
============
Only once have I seen the above printout complete showing that
d->header.n_block = -23135124... Which indicates some deep rooted rot
somewhere.
I have made some small changes that have gotten us past the occurrence of
this issue. I'll be retracing the differences to find the critical fix. At
that point I'll share.
Kind Regards,
Ross
--
You received this message because you are subscribed to the Google Groups
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/bd10cd82-63d1-4d3b-bf4e-78903471df59n%40lists.berkeley.edu.
