Ubuntu
mesa package

gjs-console crashed with SIGSEGV in lookup_opcode_desc under X

Bug #1966502 reported by Eric Carvalho on 2022-03-25

58

This bug affects 8 people

Affects		Status	Importance	Assigned to	Milestone
	mesa (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

This crash happens when starting Gnome Extensions.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gjs 1.72.0-1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 25 14:08:33 2022
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2020-02-26 (757 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225.4)
ProcCmdline: /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Extensions
SegvAnalysis:
Segfault happened at: 0x7f312f6ecfeb: mov (%rdi),%edi
PC (0x7f312f6ecfeb) ok
source "(%rdi)" (0x000002a0) not located in a known VMA region (needed readable region)!
destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gjs
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
Title: gjs-console crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark
separator:

Tags:

Revision history for this message

Eric Carvalho (eric-carvalho) wrote on 2022-03-25:

#1

Dependencies.txt Edit (4.7 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (609 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (116.7 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (308 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (95.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Registers.txt Edit (982 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (8.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (80.7 KiB, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

Apport retracing service (apport) wrote on 2022-03-25:

#2

StacktraceTop:
lookup_opcode_desc(gfx_ver*, opcode_desc const**, unsigned int, unsigned int opcode_desc::*, intel_device_info const*, unsigned int) [clone .isra.0] (index_ver=0x2a0, index_descs=0x0, index_size=index_size@entry=84, key=key@entry=&opcode_desc::ir, k=k@entry=60, devinfo=<optimized out>, devinfo=<optimized out>) at ../src/intel/compiler/brw_eu.cpp:720
brw_opcode_desc (devinfo=<optimized out>, devinfo=<optimized out>, opcode=BRW_OPCODE_RNDZ) at ../src/intel/compiler/brw_eu.cpp:750
is_3src (devinfo=<optimized out>, devinfo=<optimized out>, opcode=BRW_OPCODE_RNDZ) at ../src/intel/compiler/brw_eu.h:1942
backend_instruction::is_3src (this=0x5630ee102870, devinfo=0x5630ecaafa00, this=0x5630ee102870, devinfo=0x5630ecaafa00) at ../src/intel/compiler/brw_shader.cpp:890
can_take_stride (devinfo=0x5630ecaafa00, stride=1, arg=0, dst_type=BRW_REGISTER_TYPE_F, inst=0x5630ee102870) at ../src/intel/compiler/brw_fs_copy_propagation.cpp:398

tags:

removed: need-amd64-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2022-03-28:

#3

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gjs (Ubuntu):
status:	New → Confirmed

Revision history for this message

Apport retracing service (apport) wrote on 2022-03-28:

#4

Stacktrace:
#0 0x00007f312f6ecfeb in use_surface.constprop.0 (ice=<optimized out>, batch=0x1, p_surf=0x54, writeable=<optimized out>, aux_usage=32561, access=IRIS_DOMAIN_RENDER_WRITE, is_read_surface=<optimized out>) at ../src/gallium/drivers/iris/iris_state.c:4825
         surf = 0x54
         res = 0x5630ecaafa00
         offset = 0
Backtrace stopped: Cannot access memory at address 0xa
StacktraceSource:
#0 0x00007f312f6ecfeb in use_surface.constprop.0 (ice=<optimized out>, batch=0x1, p_surf=0x54, writeable=<optimized out>, aux_usage=32561, access=IRIS_DOMAIN_RENDER_WRITE, is_read_surface=<optimized out>) at ../src/gallium/drivers/iris/iris_state.c:4825
   [Error: iris_state.c was not found in source tree]
StacktraceTop: use_surface.constprop.0 (ice=<optimized out>, batch=0x1, p_surf=0x54, writeable=<optimized out>, aux_usage=32561, access=IRIS_DOMAIN_RENDER_WRITE, is_read_surface=<optimized out>) at ../src/gallium/drivers/iris/iris_state.c:4825

Revision history for this message

Apport retracing service (apport) wrote on 2022-03-28: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (36.4 KiB, text/plain)

Changed in gjs (Ubuntu):
importance:	Undecided → Medium

Revision history for this message

Walter Garcia-Fontes (walter-garcia) wrote on 2022-03-29: Re: gjs-console crashed with SIGSEGV

#6

In my case Gnome Extensions works under Wayland but it crashes under Xorg.

Sebastien Bacher (seb128) on 2022-03-29

affects:	gjs (Ubuntu) → mesa (Ubuntu)
summary:	- gjs-console crashed with SIGSEGV + gjs-console crashed with SIGSEGV in lookup_opcode_desc under X

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.