Project

General

Profile

Bug #21163

Individual reconfiguration of single BR sometimes causes a crash of that BR

Added by Kurt Biery 8 months ago. Updated 12 days ago.

Status:
Remission
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
10/16/2018
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Co-Assignees:
Duration:

Description

At protoDUNE, folks have noticed that the mysterious crashes of WIB BoardReaders at begin-run (Start) time are sometimes correlated with a second configuration of that BR.

Basically what happens is that the Configure step works for all of the BRs, EBs, etc, except for one BR (because of an issue with the upstream electronics). The user picks the single troublesome BR in the RunControl GUI and sends a second Configure command to that single BR, which works. But, when the subsequent Begin Run is attempted, that BR crashes.


Related issues

Related to artdaq - Idea #21164: A simple-test-config that has configure-only BRs might be useful to help mimic protoDUNE-like systemsNew2018-10-16

History

#1 Updated by Eric Flumerfelt 8 months ago

Question:
Does clicking on configure again send another "initialize" XMLRPC command, or does it send a "reinitialize"? "reinitialize" currently has no implementation in BoardReaderCore, it simply logs a message and returns true.

Also, I think that we should add generator_ptr_.reset(nullptr); at BoardReaderCore.cc:128.

#2 Updated by Kurt Biery 8 months ago

The truthful answer is 'I don't know', but I strongly suspect that it is a second Init command, rather than a re-init.

#3 Updated by Eric Flumerfelt 8 months ago

  • Related to Idea #21164: A simple-test-config that has configure-only BRs might be useful to help mimic protoDUNE-like systems added

#4 Updated by Eric Flumerfelt 13 days ago

  • Status changed from New to Remission

This issue has not reoccurred in 8 months, and we have direct evidence that sending multiple initialize transitions to BoardReaders works as expected.

#5 Updated by Eric Flumerfelt 12 days ago

As part of my investigation of this Issue, I created artdaq:feature/21163_BoardReaderCore_Reinitialize, which lets the reinitialize and soft_initialize methods of BoardReaderCore simply call initialize.

#6 Updated by Eric Flumerfelt 12 days ago

Also found during investigation: problems with destructing Graphite metric when it never was connected, and problems with File metric trying to lock a mutex during destruction. These have been fixed on artdaq-utilities:bugfix/21163_MetricCrashes.



Also available in: Atom PDF