Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-44948

User process fault: interruption code 003b ilc:2 in libmutter-cogl-8.so.0.0.0[3ff8bc80000+8e000]; pyanaconda.errors.ExitError: gnome-kiosk exited on signal 11

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • rhel-9.5
    • rhel-9.5
    • mesa
    • mesa-24.1.0-3.el9
    • None
    • Critical
    • rhel-sst-gpu
    • 17
    • 19
    • 1
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • s390x
    • None

      What were you trying to do that didn't work?

      VNC installation on s390x is failing with a traceback:

      12:27:06,393 CRT exception: Traceback (most recent call last):
        File "/usr/lib64/python3.9/site-packages/gi/_ossighelper.py", line 92, in signal_notify
          def signal_notify(source, condition):
        File "/usr/lib64/python3.9/site-packages/pyanaconda/core/process_watchers.py", line 117, in _sigchld_handler
          cls._raise_exit_error(exit_statuses)
        File "/usr/lib64/python3.9/site-packages/pyanaconda/core/process_watchers.py", line 81, in _raise_exit_error
          raise ExitError(", ".join(exn_message))
      pyanaconda.errors.ExitError: gnome-kiosk exited on signal 11
      

      Error in journalctl:

      User process fault: interruption code 003b ilc:2 in libmutter-cogl-8.so.0.0.0[3ff8bc80000+8e000]
      Failing address: 0000000000000000 TEID: 0000000000000800
      Fault in primary space mode while using user ASCE.
      AS:0000000082d481c7 R3:0000000000000024 
      CPU: 1 PID: 2791 Comm: gnome-kiosk Not tainted 5.14.0-467.el9.s390x #1
      Hardware name: IBM 3931 LA1 400 (KVM/Linux)
      User PSW : 0705000180000000 000003ff8bcc9980
                 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:0 PM:0 RI:0 EA:3  
      User GPRS: 0000000000000022 0000000000000000 0000000000000000 0000000000000008
                 000002aa00000000 0000000000000022 000002aa238be3e0 000003ffc5777cc8
                 000003ff8bcb5080 000002aa238be3e0 0000000000000000 000002aa238c7c20
                 000003ff8e02ef68 000003ff8e040ac0 000003ff8bcc99c8 000003ffc5777a00
      User Code: 000003ff8bcc9972: b90400b2                lgr        %r11,%r2 
                 000003ff8bcc9976: a7840024                brc        8,000003ff8bcc99be
                #000003ff8bcc997a: e310b0880004        lg        %r1,136(%r11)
                >000003ff8bcc9980: 58101008                l        %r1,8(%r1)
                 000003ff8bcc9984: a71e0001                chi        %r1,1    
                 000003ff8bcc9988: a7740013                brc        7,000003ff8bcc99ae
                 000003ff8bcc998c: e310b0900004        lg        %r1,144(%r11) 
                 000003ff8bcc9992: ebbff0f80004        lmg        %r11,%r15,248(%r15)
      Last Breaking-Event-Address:
       [<000003ff8bcc99c8>] 0x3ff8bcc99c8
      

      The problem started in compose RHEL-9.5.0-20240621.6, last working compose was RHEL-9.5.0-20240616.55. mesa was updated in the 20240621.6 compose: mesa-23.3.3-1.el9 -> mesa-24.1.0-2.el9.

      Note that there is also a mesa problem on RHEL-10/s390x (RHEL-40876), just in case it's the same issue here.

      Please provide the package NVR for which bug is seen:

      RHEL-9.5.0-20240623.4
      mesa-24.1.0-2.el9

      How reproducible:

      Always on s390x

      Steps to reproduce

      1. Start NVC installation on s390x
      2. Connect via a VNC viewer

      Expected results

      Able to continue with a graphical installation.

      Actual results

      Anaconda traceback.

              rh-ee-jexposit Jose Exposito Quintana
              jstodola@redhat.com Jan Stodola
              David Airlie David Airlie
              Peter Kopec Peter Kopec
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: