-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HLT crash in run-367615 #41741
Comments
A new Issue was created by @missirol Marino Missiroli. @Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign hlt I let others assign to other groups, if needed. |
New categories assigned: hlt @missirol,@Martin-Grunewald you have been requested to review this Pull request/Issue and eventually sign? Thanks |
assign reconstruction FYI @cms-sw/tracking-pog-l2 |
New categories assigned: reconstruction @mandrenguyen,@clacaputo you have been requested to review this Pull request/Issue and eventually sign? Thanks |
I'm tempted to interpret the stack trace such that the stack got corrupted. Maybe valgrind might reveal something? |
In run-367615 (pp collisions), DAQ reported 1 CMSSW crash at HLT (release:
CMSSW_13_0_5_patch1
). The link to the corresponding HLT elog is here.The available stack trace is attached (f3mon_run367615.txt). A piece of stack trace which is possibly relevant is in [1].
The corresponding error-stream files are available, but first attempts to reproduce the crashes offline failed (tried on Hilton machine). The recipe used for those failed attempts is adapted in [2] to be valid for
lxplus
andlxplus-gpu
.FYI: @cms-sw/hlt-l2 @silviodonato @fwyzard @mzarucki @trtomei
[1]
[2]
The text was updated successfully, but these errors were encountered: