From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
regressions@lists.linux.dev, xen-devel@lists.xenproject.org,
iommu@lists.linux.dev, Robert Beckett <bob.beckett@collabora.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Matthew Auld <matthew.auld@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: i915 "GPU HANG", bisected to a2daa27c0c61 "swiotlb: simplify swiotlb_max_segment"
Date: Tue, 18 Oct 2022 14:01:40 +0200 [thread overview]
Message-ID: <Y06VthUrV6PjOcJH@mail-itl> (raw)
In-Reply-To: <20221018082413.GA25785@lst.de>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
On Tue, Oct 18, 2022 at 10:24:13AM +0200, Christoph Hellwig wrote:
> On Tue, Oct 18, 2022 at 05:52:16AM +0200, Marek Marczykowski-Górecki wrote:
> > not only) when using IGD in Xen PV dom0. After not very long time Xorg
> > crashes, and dmesg contain messages like this:
> >
> > i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:01fffbfe, in Xorg [5337]
> > i915 0000:00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rcs0
> > i915 0000:00:02.0: [drm] Xorg[5337] context reset due to GPU hang
>
> <snip>
>
> > I tried reverting just this commit on top of 6.0.x, but the context
> > changed significantly in subsequent commits, so after trying reverting
> > it together with 3 or 4 more commits I gave up.
> >
> > What may be an important detail, the system heavily uses cross-VM shared
> > memory (gntdev) to map window contents from VMs. This is Qubes OS, and
> > it uses Xen 4.14.
>
> Can you try the patch below?
Yes, this seems to help.
And since this is a PV domain, with Jan proposed change it should work
too. Intuitively this indeed should be PV-only thing (as was forcing
swiotlb before).
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-10-18 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 3:52 i915 "GPU HANG", bisected to a2daa27c0c61 "swiotlb: simplify swiotlb_max_segment" Marek Marczykowski-Górecki
2022-10-18 8:24 ` Christoph Hellwig
2022-10-18 8:57 ` Jan Beulich
2022-10-18 11:02 ` Christoph Hellwig
2022-10-18 14:21 ` Jan Beulich
2022-10-18 14:33 ` Christoph Hellwig
2022-10-18 14:53 ` Juergen Gross
2022-10-18 14:55 ` Christoph Hellwig
2022-10-18 12:01 ` Marek Marczykowski-Górecki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y06VthUrV6PjOcJH@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=anshuman.khandual@arm.com \
--cc=bob.beckett@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=jani.nikula@linux.intel.com \
--cc=jgross@suse.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=konrad.wilk@oracle.com \
--cc=matthew.auld@intel.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=regressions@lists.linux.dev \
--cc=rodrigo.vivi@intel.com \
--cc=sstabellini@kernel.org \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox