[Pkg-xen-devel] [admin] [BUG] task jbd2/xvda4-8:174 blocked for more than 120 seconds.

[Samuel Thibault]

Hello,

Hans van Kranenburg, le ven. 08 févr. 2019 20:18:44 +0100, a ecrit:
> Upstream mailing list is at:
>   xen-devel at lists.xenproject.org

Apparently it didn't get the mails, I guess because it's subscriber-only
posting? I have now forwarded the mails.

> Apparently,
>   xen at packages.debian.org
> results in a message to
>   pkg-xen-devel at lists.alioth.debian.org

Yes, since that's the maintainer of the package.

> On 2/8/19 6:13 PM, Samuel Thibault wrote:
> > 
> > Sacha, le ven. 08 févr. 2019 18:00:22 +0100, a ecrit:
> >> On  Debian GNU/Linux 9.7 (stretch) amd64, we have a bug on the last Xen
> >> Hypervisor version:
> >>
> >>     xen-hypervisor-4.8-amd64 4.8.5+shim4.10.2+xsa282
> > 
> > (Read: 4.8.5+shim4.10.2+xsa282-1+deb9u11)
> > 
> >> The rollback on the previous package version corrected the problem:
> >>
> >>     xen-hypervisor-4.8-amd64 4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10
> 
> Since this is the first message arriving about this in my inbox, can you
> explain what "the problem" is?

I have forwarded the original mail: all VM I/O get stuck, and thus the
VM becomes unusable.

> > (Only the hypervisor needed to be downgraded to fix the issue)
> > 
> >> The errors are on the domU a frozen file system until a kernel panic.
> 
> Do you have a reproducable case that shows success with the previous Xen
> hypervisor package and failure with the new one, while keeping all other
> things the same?

We have a production system which gets to hang within about a day. We
don't know what exactly triggers the issue.

> This seems like an upstream thing, because for 4.8, the Debian package
> updates are almost exclusively shipping upstream stable udpates.

Ok.

Samuel