Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • A apertis-issues
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

🔴 v2022.5 entered Hard Code Freeze, changes will not be accepted • schedule

🔴 v2023.1 entered Hard Code Freeze, changes will not be accepted • schedule

🟠 v2024dev2 entered Soft Code Freeze/Hard Feature Freeze, only bug fixes will be accepted • schedule

  • infrastructure
  • apertis-issues
  • Issues
  • #319
Closed
Open
Issue created May 09, 2023 by Benani Sagar Kishore@sagarDeveloper

Kernel failure observed on rebooting UpSquared board

Affected images versions

  • not relevant (explain why)
  • see the table below (list the *architecture and build id of the tested images in the appropriate cells)
Deployment Type v2021 v2022 v2023 v2024dev1
apt minimal/fixedfunction
ostree minimal/fixedfunction
apt target/hmi 20230509.0015
ostree target/hmi
apt basesdk
apt sdk
apt nfs
apt lxc
apt image-builder
apt package-source-builder

To find the build id and the variant type you can:

  • derive it from the image name
    • for instance, with the apertis_ostree_v2022pre-fixedfunction-amd64-uefi_20211031.0425.img.gz image the build id is 20211031.0425, the variant is fixedfunction the deployment type is ostree
  • obtain it from /etc/os-release using the BUILD_ID and VARIANT_ID keys

Unaffected images versions

  • Observed on UpSquared boards

Testcase

n/a

Steps to reproduce

Flash the above image on a UPSquared board Wait for the hmi to come up reboot the board by entering $sudo reboot on the terminal

Expected result

image should reboot normally

Actual result

Shell prompt comes up and the target does not reboot

Reproducibility

How often the issue is hit when repeating the test and changing nothing (same device, same image, etc.)?

Put the ✅ in the most appropriate entry:

  1. always

Impact of bug

High

Attachments

kernellogs.txt

Root cause

describe in one line what caused the issue to give a hint to product teams whether they may be impacted or not

Outcomes

TBD

Management data

This section is for management only, it should be the last one in the description.

/cc @andrunko @em @sagar @sudarshan @wlozano

Phabricator link: https://phabricator.apertis.org/T9698

Edited May 09, 2023 by Apertis CI robot
Assignee
Assign to
Time tracking
Apertis Website Terms of Use Privacy Policy