Bug#991967: linux-src 4.19.194-3 breaks Xen Dom0 powerdown and reboot
On Sat, 7 Aug 2021 08:40:14 +0200 Salvatore Bonaccorso
<carnil@debian.org> wrote:
> Control: tags -1 + moreinfo
>
> Hi,
>
> On Fri, Aug 06, 2021 at 11:50:54AM -0700, Elliott Mitchell wrote:
> > Package: src:linux
> > Version: 4.19.194-3
> > Control: affects -1 src:xen
> >
> > SSIA. Previous versions of 4.19 had no issues (4.19.181-1 according to
> > notes), but this cropped up with 4.19.194-3 (-1 and -2 weren't tested).
> >
> > When a Xen domain 0 tries to reboot or powerdown the computer, it hangs
> > with the display off, but the power supply is active.
> >
> > I'm rebuilding from source, so I imagine this also effects
> > linux-image-4.19.0-17-amd64.
>
> Can you please try to bisect which commit introduced the issue? Does
> it affect as well current upstream 4.19.201?
>
> Regards,
> Salvatore
>
>
Dear Salvatore,
As you have noticed, much more information about this bug
has been added to this bug report, but the original reporter
is of the opinion that much of that new information concerns
a bug related to but distinct from the bug he reported. Both
bugs have the same symptom: dom0 does not power down
when shutting down the system, and it is clear that both
bugs are related to x86 acpi code in either the Linux kernel
or in the Xen hypervisor. But I cannot reproduce his original
bug which occurred in Linux 4.19.194-3 on Xen-4.11 from buster.
I have only seen the bug in Xen-4.14 for bullseye, and I always
see it with Xen-4.14 regardless of the Linux kernel version.
As far as I can tell, another participant in this bug report
has reproduced the behavior I am seeing, but not the behavior
the original reporter is seeing:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991967#54
Would you endorse the original reporter's belief that there are
two distinct bugs being discussed here? If so, I would be inclined
to report the bug I am seeing as a distinct but related bug in the
bullseye version of src:xen. Otherwise, I respectfully ask that
you reclassify this as a bug in src:xen, since the original reporter
has not been able to identify a commit in src:linux that caused
the bug and no one has been able to reproduce the bug on
Xen-4.11/Linux-4.19.194-3.
Regards,
Chuck Zmudzinski
Reply to: