amdgpu panics

Matthias Andree matthias.andree at gmx.de
Mon Apr 6 09:55:37 UTC 2020


Am 06.04.20 um 11:19 schrieb Grzegorz Junka:
>
> Sorry, what discrepancy do you mean? How does FreeBSD build the
> drm-fbsd12.0-kmod on the FreeBSD pkg build server if not with
> poudriere? Does it have any specific configuration I don't know about,
> e.g. null mounted /usr/src to the host?

The discrepancy between GENERIC and possibly between build host and
with-Vega64 computer and your VENUS configuration.


> Is it even possible to build a poudriere package with a non-generic
> kernel configuration in the poudriere jail?
> What if I create the poudriere build jail from the kernel / world I
> built on the host? Is that possible?

I guess it is feasible, because you can use an arbitrarily modified copy
instead of /usr/src, but I have never tried that.

GENERIC does ship with quite a lot of modules, so that's not a reason.


> I can but I have more than one desktop and I don't want to recompile
> everything from sources on each one. That's why I have a central build
> server. Tell me how I should configure the build server to build the
> packages and/or kernel and/or world in a way that the graphics stack
> expects it to be build and it would be solved.
>
> Or what you are really saying is that if someone wants to use the new
> drm graphics stack they HAVE TO recompile (a) kernel, (b) firmware,
> (c) amdgpu from sources on the host every time?

I thought you'd established that binary packages don't work for you, and
in your previous post, there was writing about a nondefault kernel
configuration named VENUS.

Consequentially, I am saying let's reduce the number of variables first
so you might at some point have a working baseline which you can record
exactly, and then you can feed back to your build server so you have a
way of tracing where things break. Assuming that the amdgpu module works
at all. Poudriere packages are built against default binary packaged
kernels you'd normally get, say, from freebsd-update obtaining
12.1-RELEASE, and since you mentioned a local/customized/changed kernel
configuration, binary packages are out of the question.

Note that "some vega10" module will be from gpu-firmware-kmod.

I am not sure how current https://wiki.freebsd.org/Graphics#AMD_Graphics
is... and if suppressing efifb might be required.




More information about the freebsd-ports mailing list