Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • C cmsgemos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 81
    • Issues 81
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cmsgemonline
  • gem-daq
  • cmsgemos
  • Issues
  • #161

Closed
Open
Created Feb 12, 2021 by Camilla Galloni@cgalloniOwner

Memhub semaphore preventing recovery

Summary

The current software implementation of the recovery might fail because of the semaphore being occupied by previously running applications that failed, for which the semaphore is not released.

In fact, using the old legacy recovery procedure with manual mpoke of the registers to load the oh firmware worked fine. In the development case, we had to cancel the file /dev/shm/sem.memhub.gem in the stuck amc.

What is the expected correct behavior?

the recovery should work.

Assignee
Assign to
Time tracking