Bug#991967: #991967: Simply ACPI powerdown/reset issue?
On Sun, Sep 19, 2021 at 01:05:56AM -0400, Chuck Zmudzinski wrote:
> xen hypervisor version: 4.14.2+25-gb6a8c4f72d-2, amd64
>
> linux kernel version: 5.10.46-4 (the current amd64 kernel
> for bullseye)
>
> Boot system: EFI, not using secure boot, booting xen
> hypervisor and dom0 bullseye with grub-efi package for
> bullseye, and it boots the xen-4.14-amd64.gz file, not
> the xen-4.14-amd64.efi file.
> I also tested a buster dom0 with the 4.19 series kernel
> on the xen-4.14 hypervisor from bullseye and saw the
> problem, but I did not see the problem with either
> a buster (linux 4.19) or bullseye (linux 5.10) dom0 on
> the xen-4.11 hypervisor, so I think the problem is
> with the Debian version of the xen-4.14 hypervisor,
> not with src:linux.
You're referencing several software versions which are mismatches for
#991967. #991967 was observed with Xen 4.11 and Linux kernel 4.19.194-3,
but not Linux kernel 4.19.181.
The fact it correlates with a Linux kernel update rather strongly points
to the Linux kernel. I could believe the situation is partially the
fault of both though.
> I suspect the following patch is the culprit for problems
> shutting down on the amd64 architecture:
>
> 0030-xen-acpi-Rework-acpi_os_map_memory-and-acpi_os_unmap.patch
> This patch does affect amd64 acpi code, and is probably causing
> the problem on my amd64 system, so my build of the xen-4.14
> hypervisor without this patch fixed the problem.
Of the ones listed that is the only one which has any overlap with x86
code. The next reproduction step is `apt-get source xen &&
patch -p1 -R < 0030-xen-acpi-Rework-acpi_os_map_memory-and-acpi_os_unmap.patch
&& dpkg-buildpackage -b`. Then try with this to confirm that patch
is what does it.
Thing is that delta is rather small. I don't have a simulator, but that
is rather small to be the culprit.
> I think this bug should be re-classified as a bug in src:xen.
There could be a separate bug in src:xen, but that is not #991967.
> I also would inquire with the Debian Xen Team about why they
> are backporting patches from the upstream xen unstable
> branch into Debian's 4.14 package that is currently shipping
> on Debian stable (bullseye). IMHO, the aforementioned
> patches that are not in the stable 4.14 branch upstream
> should not be included in the xen package for Debian stable.
It was requested since someone trying to have Xen operational on a device
needed those for operation. Rather a lot of bugfix or very small
standalone feature patches get cherry-picked.
Presently I haven't been convinced this is a Xen bug (though it does
effect Xen installations).
Any chance you've got the tools to build and try a 5.5.0 or 5.10.0 Linux
kernel? I'm suspecting got incorrectly backported on the Linux side
(alternatively the Xen project seems a bit poor at keeping needed patches
in Linux).
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | ehem+sigmsg@m5p.com PGP 87145445 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
Reply to: