Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • I infrastructure-maintenence
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Custom issue tracker
    • Custom issue tracker
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OSTC
  • infrastructure
  • infrastructure-maintenence
  • Issues
  • #45

Closed
Open
Created Feb 16, 2022 by Chase Qi@chase-qiReporter

Release serial by device path before serial connection

For serial connection, lava uses ser2net, but engineer may use cat, screen or minicom for debugging. When there is session left in the background, LAVA will fail to establish connection. Always release serial by device path first sound like a good improvement.

@artem.kondratiuk proposed to use sudo fuser -k <serial_path>. It is to be tested in LAVA. For this improvement, all related scripts and lava device configs should be updated.

Assignee
Assign to
Time tracking

| Privacy policy | Cookies policy | Intellectual Property Compliance Policy |