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.
Bug 1050034 - alloc_ioctl: failed to create gem
Summary: alloc_ioctl: failed to create gem
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: xorg-x11-drv-qxl
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Default Assignee for SPICE Bugs
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-08 16:20 UTC by Dr. David Alan Gilbert
Modified: 2015-01-02 15:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-02 15:37:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Dr. David Alan Gilbert 2014-01-08 16:20:08 UTC 
Description of problem:

At shutdown of a RHEL7 beta 1 guest - running Gnome desktop - it fell back to a text screen with:
[TTM] Illegal buffer object size
qxl 0000:00:02.0: object_init failed for (0m0x00000001)
[drm:qxl_gem_object_create] *ERROR* Failed to allocate GEM object (0, 1, 4096, -22)

scrolling past repeatedly; and wouldn't shutdown.

F20 virt-manager -> ssh->RHEL7 post-beta host->RHEL7 beta 1 guest

This might be the same as bug 1039063 but nothing interesting survived in the journal after reboot, no kernel oops etc.

Version-Release number of selected component (if applicable):

RHEL7-beta guest:
xorg-x11-drv-qxl-0.1.1-5.el7.x86_64
kernel 3.10.0-54.0.1.el7
spice-vdagent-0.14.0-5.el7.x86_64
spice-gtk3-0.20-6.el7.x86_64
spice-glib-0.20-6.el7.x86_64
spice-server-0.12.4-3.el7.x86_64

RHEL7-post-beta host:
qemu-kvm-1.5.3-30.el7.x86_64
spice-glib-0.20-6.el7.x86_64
spice-gtk3-0.20-6.el7.x86_64
spice-server-0.12.4-3.el7.x86_64


How reproducible:
Seen once, doesn't want to repeat.

Steps to Reproduce:
1. Graphical login to guest via virt-manager
2. Use for a while - just terminal, disk-utility - not much else
3. Click on name at top right, power-off, confirm the power-off

Actual results:
Stream of errors (see above)

Expected results:
Machine powers off.

Additional info:
Comment 2 Dave Airlie 2014-02-19 23:16:18 UTC 
did this keep happening?
Comment 3 Dr. David Alan Gilbert 2014-02-20 09:13:38 UTC 
I'd only seen it once in a bunch of RHEL7 runs, and I haven't used RHEL7 much since then.  I don't think there is much point in me explicitly testing for it because we don't know the original trigger.
Comment 6 Marc-Andre Lureau 2014-09-03 16:22:20 UTC 
there has been no reproducer for a long while. Not sure if we should close this bug as insufficient_data or currentrelease.
Note You need to log in before you can comment on or make changes to this bug.