Public bug reported:
Decription:
KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was
issued, while it should report a 'busy' condition until the CPU is really
started.
The patches to fix this have already been picked for jammy/master-next:
812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART"
435d17955519 "KVM: s390: Add a routine for setting userspace CPU state"
4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling"
For Ubuntu 20.04 the focal/master-next already contains:
d74b0d2d38d3 KVM: s390: Clarify SIGP orders versus STOP/RESTART
so we additionally need the following two upstream commits in focal
67cf68b6a5cc KVM: s390: Add a routine for setting userspace CPU state
8eeba194a32e KVM: s390: Simplify SIGP Set Arch handling
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-196454 severity-high
targetmilestone-inin---
** Tags added: architecture-s39064 bugnameltc-196454 severity-high
targetmilestone-inin---
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962578
Title:
[UBUNTU 20.04] Fix SIGP processing (KVM: s390)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962578/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
