http://bugzilla.suse.com/show_bug.cgi?id=926594 --- Comment #12 from Jan Beulich <jbeulich@suse.com> --- (In reply to lynda t from comment #11)
That's part of the problem -- I don't "see" any bug. There's no reference to a specific commit.
Not here, but I had mailed it to you in the list conversation: http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=c643fb110a51693e82a3...
I posted this ^^ as a Xen bug, correctly or not. That hasn't been changed by anyone. You've asked for Xen logs, and referenced a line in the Xen output. Then you've said the solution "is already in the upstream trees for 4.5.1:.
I have no idea what you're trying to get at. This is a firmware bug. Period. And there's no solution in Xen, just a workaround (to use another reboot method). -- You are receiving this mail because: You are on the CC list for the bug.