| Summary: | media-libs/mesa-20.2.0_rc2 fails to build with internal compiler error | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | contactopublico57 |
| Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | contactopublico57, jstein, sam, x11 |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build info in case the previous specific information did not come through
full build log build log mesa log with kernel 5.8.11 segfault |
||
|
Description
contactopublico57
2020-09-06 17:46:18 UTC
Thank you for the report. We need to have all information at hand before ticket assignment. That is why I ask you to * attach the logs and * attach the kernel config and * paste the emerge info as described on https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket Please reopen this ticket (Status:UNCONFIRMED) afterwards. Created attachment 659324 [details]
build info in case the previous specific information did not come through
Created attachment 661807 [details]
full build log
This failure to build continues with kernel 5.9-rc5
Note that I have attempted to supply all the information requested.
Reopened UNCONFIRMED.
Your full build log is not full at all, have all the actual errors and build progress removed. Please attach real full build log. Created attachment 662191 [details]
build log
please advise if this is not complete
> ../mesa-20.2.0-rc4/src/gallium/drivers/softpipe/sp_tex_sample.c: In function ‘sample_compare’:
> ../mesa-20.2.0-rc4/src/gallium/drivers/softpipe/sp_tex_sample.c:3862:1: internal compiler error: Segmentation fault
> 3862 | }
> | ^
Uh, the compiler is segfaulting. Does this really happen only with a particular kernel version? Is it reproduceable? Does it always happen in the same place?
This appears to be the same error/problem in the same place with 5.9-rc1, 5.9-rc2, and 5.9-rc5. Do not recall any problem with 5.8 or earlier.
ninja: build stopped: subcommand failed.
[31;01m*[0m ERROR: media-libs/mesa-20.2.0_rc2::gentoo failed (compile phase):
[31;01m*[0m ninja -v -j2 -l0 -C /var/tmp/portage/media-libs/mesa-20.2.0_rc2/work/mesa-20.2.0-rc2-abi_x86_64.amd64 failed
[31;01m*[0m
[31;01m*[0m Call stack:
[31;01m*[0m ebuild.sh, line 125: Called src_compile
[31;01m*[0m environment, line 4117: Called multilib-minimal_src_compile
[31;01m*[0m environment, line 2791: Called multilib_foreach_abi 'multilib-minimal_abi_src_compile'
[31;01m*[0m environment, line 3041: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile'
[31;01m*[0m environment, line 2726: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile'
[31;01m*[0m environment, line 2724: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_compile'
[31;01m*[0m environment, line 938: Called multilib-minimal_abi_src_compile
[31;01m*[0m environment, line 2785: Called multilib_src_compile
[31;01m*[0m environment, line 3261: Called meson_src_compile
[31;01m*[0m environment, line 2613: Called eninja '-C' '/var/tmp/portage/media-libs/mesa-20.2.0_rc2/work/mesa-20.2.0-rc2-abi_x86_64.amd64'
[31;01m*[0m environment, line 1771: Called die
[31;01m*[0m The specific snippet of code:
[31;01m*[0m "$@" || die "${nonfatal_args[@]}" "${*} failed"
[31;01m*[0m
[31;01m*[0m If you need support, post the output of `emerge --info '=media-libs/mesa-20.2.0_rc2::gentoo'`,
[31;01m*[0m the complete build log and the output of `emerge -pqv '=media-libs/mesa-20.2.0_rc2::gentoo'`.
[31;01m*[0m The complete build log is located at '/usr/portage/logs/media-libs:mesa-20.2.0_rc2:20200825-225356.log'.
[31;01m*[0m For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/mesa-20.2.0_rc2/temp/build.log'.
[31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/media-libs/mesa-20.2.0_rc2/temp/environment'.
[31;01m*[0m Working directory: '/var/tmp/portage/media-libs/mesa-20.2.0_rc2/work/mesa-20.2.0-rc2-abi_x86_64.amd64'
[31;01m*[0m S: '/var/tmp/portage/media-libs/mesa-20.2.0_rc2/work/mesa-20.2.0-rc2'
Try with an older kernel. What you pasted in comment #7 doesn't actually contain the error, so it's not clear to me if the same problem occurred. 5.9-rc1, rc2, rc5 fail
../mesa-20.2.0-rc4/src/gallium/drivers/softpipe/sp_tex_sample.c: In function ‘sample_compare’:
../mesa-20.2.0-rc4/src/gallium/drivers/softpipe/sp_tex_sample.c:3862:1: internal compiler error: Segmentation fault
3862 | }
| ^
Emerge also failed with ubuntu daily kernel build 5.9-rc6 as before:
during IPA pass: fnsummary
../mesa-20.2.0-rc4/src/gallium/drivers/softpipe/sp_tex_sample.c: In function ‘sample_compare’:
../mesa-20.2.0-rc4/src/gallium/drivers/softpipe/sp_tex_sample.c:3862:1: internal compiler error: Segmentation fault
3862 | }
| ^
--snip--
Mesa emerged with -gallium kernel flag:
USE="-gallium" sudo emerge mesa
>>> Verifying ebuild manifests
>>> Running pre-merge checks for media-libs/mesa-20.2.0_rc4
* Ignoring USE=vaapi since VIDEO_CARDS does not contain r600, radeonsi, or nouveau
* Ignoring USE=vdpau since VIDEO_CARDS does not contain r300, r600, radeonsi, or nouveau
* Ignoring USE=llvm since USE does not contain gallium
* Ignoring USE=vaapi since USE does not contain gallium
* Ignoring USE=vdpau since USE does not contain gallium
--snip--
sudo emerge mesa --info
Portage 3.0.8 (python 3.7.9-final-0, default/linux/amd64/17.1/systemd, gcc-10.1.0, glibc-2.32-r1, 5.9.0-rc5 x86_64)
System uname: Linux-5.9.0-rc5-x86_64-with-gentoo-2.7
--snip--
media-libs/mesa-20.2.0_rc4::gentoo was built with the following:
USE="X classic dri3 egl gbm gles2 (libglvnd) llvm vaapi vdpau wayland zstd -d3d9 -debug -gallium -gles1 -lm-sensors -opencl -osmesa (-selinux) -test -unwind -valgrind -vulkan -vulkan-overlay -xa -xvmc -zink" ABI_X86="(64) -32 (-x32)" VIDEO_CARDS="i915 i965 intel (-freedreno) -iris (-lima) -nouveau (-panfrost) -r100 -r200 -r300 -r600 -radeon -radeonsi (-v3d) (-vc4) -virgl (-vivante) -vmware"
FEATURES="sfperms binpkg-logs ebuild-locks preserve-libs usersync parallel-fetch usersandbox config-protect-if-modified fixlafiles news binpkg-docompress protect-owned nodoc ipc-sandbox unmerge-orphans pid-sandbox sandbox merge-sync candy xattr assume-digests unknown-features-warn userpriv qa-unresolved-soname-deps network-sandbox strict multilib-strict unmerge-logs binpkg-dostrip distlocks"
Okay, again, can you try with an older kernel? Like v5.8? You've said that it fails on 5.9-rcX and that's a surprising statement because usually kernel upgrades don't cause compiler segfaults. So, please try v5.8 or older so that we can confirm or reject the hypothesis that this is somehow kernel related. Created attachment 662680 [details]
mesa log with kernel 5.8.11 segfault
Great, thank you. As I suspected there's not a dependence on the kernel version. Please follow https://wiki.gentoo.org/wiki/Gcc-ICE-reporting-guide. gcc 9.3 compiles mesa without errors. 10.1 has now been superseded by 10.2 so there is no point in pursuing this matter with 10.1, now outdated. (In reply to contactopublico57 from comment #15) > gcc 9.3 compiles mesa without errors. > > 10.1 has now been superseded by 10.2 so there is no point in pursuing this > matter with 10.1, now outdated. Does 10.2 work for you? Then feel free to close the bug as OBSOLETE. |
