Skip to content
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

sys-kernel/coreos-sources: Backport Ampere EFI fix #890

Closed
wants to merge 1 commit into from

Conversation

jepio
Copy link
Member

@jepio jepio commented Jun 7, 2023

Backport Ampere EFI fix

There was a lockup issue with newer kernels on Ampere machines, a fix was merged before v6.1, but the fix is incomplete and the follow-up fix was not backported (because a file was renamed or because it was not marked for stable). Add the missing patch to our kernel for testing (and later submission to v6.1.y).

How to use

[ describe what reviewers need to do in order to validate this PR ]

Testing done

http://192.168.42.7:8080/job/container/job/test/11069/

  • Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)
  • Inspected CI output for image differences: /boot and /usr size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.

There was an lockup issue with newer kernels on Ampere machines, a fix was
merged and backported to v6.1, but the fix is incomplete and the follow-up fix
was not backported (because it was not marked for stable). Add the missing patch
to our kernel for testing (and later submission to v6.1.y).

Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
Copy link
Member

@dongsupark dongsupark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for figuring it out.
Let's add changelog, merge, and backport to Alpha 3619.

@jepio
Copy link
Member Author

jepio commented Jun 8, 2023

Hold on - this is queued for 6.1.33 (https://lore.kernel.org/stable/TY2PR01MB3788FA9EB3D8EAC669C3F623B750A@TY2PR01MB3788.jpnprd01.prod.outlook.com/T/#m3552b1fc1513dfee28fb18eaf7a6e5aa903b36d5), so if that comes out this week, let's just merge that instead.

@github-actions
Copy link

github-actions bot commented Jun 8, 2023

@dongsupark
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants