Comment # 17 on bug 926594 from Jan Beulich

(In reply to lynda t from comment #16)
> Could you please consider not constantly inflaming discussions with your "I
> have no idea why you ...".

I'm sorry if this came over offending. To me, opening a 2nd bug for the same
issue looks like spamming bugzilla. (In fact, even if it wasn't you who opened
the first one we'd expect you to look for bugs matching your problem before
opening a new one.) Plus you report the problem against a Xen version not in
any openSUSE release, i.e. apart from this being a firmware bug (and hence you
rather needing to push your hardware vendor for a firmware update) I don't
think it is a valid expectation for us to have a workaround for you available
immediately. For such expectations I think you'd need to pay for a SLE support
contract.

> I opened it to make the backport request separately from this issue.
> 
> First, it seemed more efficient.  It proved to be, as Charles quickly and
> politely addressed it.  Case closed.
> 
> And it was eminently clear that YOU weren't going to do a thing about it
> here.

This is clearly wrong: I _am_ doing things to help this, just perhaps in a way
not visible to you. As the upstream stable tree maintainer, I am making sure
that 4.5.1 will have the change (unless a regression would be found with it),
and that it will get released in as timely a manner as possible. Considering
all of the above, this necessarily means that you either have to be a little
patient, or apply the workaround on your own until an official update is
available.