Comment 3 for bug 1892546
Revision history for this message
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
------- Comment From <email address hidden> 2020-08-24 12:34 EDT-------
(In reply to comment #24)
> It looks like the patch just got submitted to upstream (and landed in a
> staging tree); but we usually need to wait for it's upstream acceptance - at
> least to Torvalds tree or linux-next (to be sure that the patch is stable,
> reviewed and community accepted).
Understood, but is it possible to get a one-off/test kernel in the interim? We have cloud customer for whom this problem is causing intermittent outages.
>
> Am I got it right reading that this happens on PowerVM DLPARs, controlled by
> PowerVC?
Correct, but the problem isn't limited to that scenario. It can be recreated on any PowerVM LPAR, but hvcs is generally not used outside of PowerVC setups and as such that is where this got exposed.
------- Comment From <email address hidden> 2020-08-24 12:37 EDT-------
(In reply to comment #25)
> I saw that the tag 'targetmileston
> as affected release. Is this the only affected Ubuntu release?
This is the LTS that PowerVC uses, but as mentioned previously this issue effects all PowerVM LPARs should someone choose to use hvcs so it is desirable in any other releases that support PowerVM.