Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1525223[details]
Core dump of xorg-x11-server
Description of problem:
So far, this has been observed only on RHEL 8 Beta hosted on RHEVM. I have seen this issue on 2 of my RHEVM guest machines. The issue started after updating doing a complete system update. As soon as login attempt is made via GUI login screen, xorg crashes. I have seen 2 crash reasons in the captured abrt dumps :
Segmentation fault at address 0x0
Xorg killed by SIGABRT
Once xorg is crashed, login via GUI is not possible. Only ssh works.
Version-Release number of selected component (if applicable):
Both of the guest machines have similar packages as follows :
RHEL 8 Beta
4.18.0-60.el8.x86_64
# rpm -qa | grep -i xorg
xorg-x11-server-Xorg-1.20.3-4.el8.x86_64
abrt-addon-xorg-2.10.9-10.el8.x86_64
xorg-x11-drv-ati-18.1.0-1.el8.x86_64
xorg-x11-utils-7.5-28.el8.x86_64
xorg-x11-proto-devel-2018.4-1.el8.noarch
xorg-x11-drv-nouveau-1.0.15-4.el8.1.x86_64
xorg-x11-drv-evdev-2.10.6-2.el8.x86_64
xorg-x11-font-utils-7.5-40.el8.x86_64
xorg-x11-server-utils-7.7-27.el8.x86_64
xorg-x11-drv-qxl-0.1.5-9.el8.x86_64
xorg-x11-drv-wacom-serial-support-0.36.1-5.el8.x86_64
xorg-x11-drv-fbdev-0.5.0-2.el8.x86_64
xorg-x11-server-Xwayland-1.20.3-4.el8.x86_64
xorg-x11-drv-vmware-13.2.1-8.el8.x86_64
xorg-x11-server-common-1.20.3-4.el8.x86_64
xorg-x11-xkb-utils-7.7-27.el8.x86_64
xorg-x11-drv-libinput-0.28.0-2.el8.x86_64
xorg-x11-drv-wacom-0.36.1-5.el8.x86_64
xorg-x11-xinit-1.3.4-18.el8.x86_64
xorg-x11-drv-vesa-2.4.0-3.el8.x86_64
xorg-x11-xauth-1.0.9-12.el8.x86_64
xorg-x11-drv-intel-2.99.917-38.20180618.el8.x86_64
How reproducible:
Most likely it is reproducible. And so far, I have observed this on RHEVM guests only. It's not seen on the physical server. I have 2 guests hosted on Red Hat's internal RHEVM site (https://lab-rhevm.gsslab.pnq2.redhat.com) and on both of them, I could see the same issue.
Steps to Reproduce:
1. Install RHEL 8 Beta
2. Do a complete update of the server (# dnf update -y)
3. Try logging in via GUI login prompt
Actual results:
xorg crashes and the login fails. Login via ssh works.
Expected results:
xorg should not crash and the login should be successful.
Additional info:
I am attaching abrt dumps of 2 guests along with the messages snippet below.
We're running out of device memory in qxl:
Jan 31 07:40:37 rhevm8 kernel: [drm:qxl_gem_object_create [qxl]] *ERROR* Failed to allocate GEM object (7272960, 2, 4096, -12)
Jan 31 07:40:37 rhevm8 kernel: [drm:qxl_alloc_surf_ioctl [qxl]] *ERROR* qxl_alloc_surf_ioctl: failed to create gem ret=-12
This is apparently not getting caught, and then things go boom. Moving to the qxl driver.
Amount of memory configured:
> [ 2.064233] [drm] qxl: 16M of VRAM memory size
> [ 2.064234] [drm] qxl: 63M of IO pages memory ready (VRAM domain)
> [ 2.064234] [drm] qxl: 8M of Surface memory size
Seems that 4 displays is configured:
> Jan 31 07:40:37 rhevm8 /usr/libexec/gdm-x-session[25453]: (II) qxl(0): Output Virtual-0 connected
> Jan 31 07:40:37 rhevm8 /usr/libexec/gdm-x-session[25453]: (II) qxl(0): Output Virtual-1 disconnected
> Jan 31 07:40:37 rhevm8 /usr/libexec/gdm-x-session[25453]: (II) qxl(0): Output Virtual-2 disconnected
> Jan 31 07:40:37 rhevm8 /usr/libexec/gdm-x-session[25453]: (II) qxl(0): Output Virtual-3 disconnected
Needs more memory on configuration, see: https://www.spice-space.org/multiple-monitors.html
From comment #0> So far, this has been observed only on RHEL 8 Beta hosted on RHEVM. I have seen this issue on 2 of my RHEVM guest machine
On RHEVM configuration, you used to need to specify the correct guest type on VM creation, if you used RHEL 6 it would give you less memory than what you need in a RHEL 7 or RHEL 8 VM.
Can you confirm that you created this vm with the right settings?
Possibly DUP of bug 1520848 (see 33rd comment onward there)