[Mesa-dev] Error: unsupported relocations
bas at basnieuwenhuizen.nl
Sun Jun 2 11:01:23 UTC 2019
On Sun, Jun 2, 2019 at 12:41 PM James Harvey <jamespharvey20 at gmail.com> wrote:
> On Sat, Jun 1, 2019 at 10:56 PM Jan Vesely <jan.vesely at rutgers.edu> wrote:
> > On Sat, 2019-06-01 at 18:21 -0400, James Harvey wrote:
> > > On Sat, Jun 1, 2019 at 6:19 PM James Harvey <jamespharvey20 at gmail.com> wrote:
> > > > On Tue, Feb 19, 2019 at 7:52 PM james harvey <jamespharvey20 at gmail.com> wrote:
> > > > > Commit 9baacf3f is: "radeonsi: Refuse to accept code with unhandled
> > > > > relocations".
> > > > >
> > > > > This has broken ImageMagick for many people using AMD graphics cards.
> > > > > See https://github.com/ImageMagick/ImageMagick/issues/1366
> > > > >
> > > > > ImageMagick responded: "It looks like this error message is created by
> > > > > the mesa driver. I have no idea what causes this message and if there
> > > > > is anything what we could do to prevent this from happening."
> > > > >
> > > > > And, hasn't responded back for requests for what additional
> > > > > information I could tell mesa.
> > > > >
> > > > > I see the mesa commit is to prevent GPU hangs, so I'm all for the commit.
> > > > >
> > > > > I'm just asking what would need to be done by who to get ImageMagick
> > > > > working again, using opencl-mesa. Using opencl-amd has been a
> > > > > workaround for some people. Not sure if this is something mesa just
> > > > > hasn't implemented that opencl-amd has, or if it's something
> > > > > ImageMagick needs to do differently.
> > > >
> > > > Ping? Mesa + ImageMagick convert is broken, affecting lots of people,
> > > > but neither project is saying anything.
> > >
> > > Sorry all, please reply to this post rather than the last. Copy-paste
> > > failure of email addresses of people listed in mesa patch, fixed.
> > sorry I missed the previous email. The issues has been discussed at
> > .
> > tldr; the referenced mesa commit prevents GPU hangs/crashes caused by
> > changes in LLVM.
> > longer story:
> > AMDGPU llvm backend used to inline all function calls until llvm-6.
> > llvm-6+ uses functions calls and issues relocations for each function
> > invocation. unhandled relocations lead to GPU hangs/crashes.
> > either clover/mesa needs to handle relocations, or LLVM needs to stop
> > using relocations for internal symbols (they are not needed).
> > I've neither time, nor energy, nor access to hw, to fix things up
> > every time AMD changes break something in clover, and nobody else has
> > stepped up.
> > moreover, mesa made it clear that volunteer contributions and needs
> > are inferior to corporate stakeholders (not even worth CI cycles).
> > thus, clover on amd gpus is in damage mitigation mode; errors are
> > better than crashes, crashes are better than hangs.
> > Chances are that clover over NIR will work before the current issues
> > are fixed.
> > regards,
> > Jan
> No problem at all! Truly, thanks for your time on the project. I've
> had enough run-ins with AMD's frequent breakage as just an end user.
> Can't imagine how much worse it is for you and all mesa dev's.
> So, for people running amdgpu and wanting to run ImageMagick convert
> who get this error... Does this mean there is something ImageMagick
> could change to prevent the error? Or, in the meantime, is the only
> option to install the amdgpu-pro opencl userspace driver with
> ImageMagick? (The pro opencl driver can be extracted from amdgpu-pro
> as a whole, and ran on top of the free amdgpu driver., without the
> rest of amdgpu-pro installed - see Arch Linux AUR package opencl-amd.)
So, does imagemagick actually need OpenCL? If not, you can probably
also uninstall you mesa opencl distro package?
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
More information about the mesa-dev