Bug 1050142

Summary: [abrt] WARNING: CPU: 0 PID: 180 at drivers/gpu/drm/qxl/qxl_ttm.c:418 qxl_sync_obj_wait+0x172/0x1f0 [qxl]()
Product: [Fedora] Fedora Reporter: L.L.Robinson <junk>
Component: kernelAssignee: Dave Airlie <airlied>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: alcamie, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mmilata, nixbugz, phil_g
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d6912938b4ee9f77722d879b6047d36c165ecc92
Whiteboard: abrt_hash:4878f214c7d6fb3fe81634412c73c54c59585715
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1051456 (view as bug list) Environment:
Last Closed: 2014-12-10 15:00:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: dmesg
none
dmesg none

Description L.L.Robinson 2014-01-08 17:50:35 UTC 
Description of problem:
Trying to use spice-vdagent in Fedora 20. 

Additional info:
reporter:       libreport-2.1.9
WARNING: CPU: 0 PID: 180 at drivers/gpu/drm/qxl/qxl_ttm.c:418 qxl_sync_obj_wait+0x172/0x1f0 [qxl]()
sync obj 301 still has outstanding releases 0 0 0 4096 1
Modules linked in: virtio_blk qxl drm_kms_helper ttm drm virtio_pci virtio_ring virtio i2c_core ata_generic pata_acpi
CPU: 0 PID: 180 Comm: plymouthd Not tainted 3.11.10-301.fc20.x86_64 #1
Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2007
 0000000000000009 ffff88003b7bd798 ffffffff816441db ffff88003b7bd7e0
 ffff88003b7bd7d0 ffffffff8106715d 0000000000000001 ffff88003b5b9eb0
 0000000000000001 ffff88003b5b9ec8 0000000000000000 ffff88003b7bd830
Call Trace:
 [<ffffffff816441db>] dump_stack+0x45/0x56
 [<ffffffff8106715d>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff810671cc>] warn_slowpath_fmt+0x4c/0x50
 [<ffffffff81648313>] ? schedule_hrtimeout_range+0x13/0x20
 [<ffffffffa00bde82>] qxl_sync_obj_wait+0x172/0x1f0 [qxl]
 [<ffffffff812a7eca>] ? symhash+0x1a/0x60
 [<ffffffffa00a770e>] ttm_bo_wait+0x8e/0x180 [ttm]
 [<ffffffffa00a8fda>] ttm_bo_evict+0x4a/0x330 [ttm]
 [<ffffffffa00a93f0>] ttm_mem_evict_first+0x130/0x190 [ttm]
 [<ffffffffa00a9701>] ttm_bo_mem_space+0x2b1/0x360 [ttm]
 [<ffffffffa00a9b0a>] ttm_bo_move_buffer+0xaa/0x130 [ttm]
 [<ffffffffa00a9c1a>] ttm_bo_validate+0x8a/0x100 [ttm]
 [<ffffffffa00a9e66>] ttm_bo_init+0x1d6/0x430 [ttm]
 [<ffffffffa00bfdf9>] qxl_bo_create+0x159/0x1e0 [qxl]
 [<ffffffffa00bfb60>] ? qxl_fbdev_qobj_is_fb+0x30/0x30 [qxl]
 [<ffffffffa00c11e7>] qxl_alloc_bo_reserved+0x37/0xb0 [qxl]
 [<ffffffffa00c20ce>] qxl_image_alloc_objects+0xae/0x140 [qxl]
 [<ffffffffa00c2a62>] qxl_draw_dirty_fb+0x132/0x440 [qxl]
 [<ffffffff816473e2>] ? mutex_lock+0x12/0x2f
 [<ffffffffa00bbfb9>] qxl_framebuffer_surface_dirty+0x79/0xa0 [qxl]
 [<ffffffffa004e610>] drm_mode_dirtyfb_ioctl+0xe0/0x190 [drm]
 [<ffffffffa003e122>] drm_ioctl+0x512/0x640 [drm]
 [<ffffffff811bac7d>] do_vfs_ioctl+0x2dd/0x4b0
 [<ffffffff8104cf01>] ? pvclock_tsc_khz+0x31/0x40
 [<ffffffff811baed1>] SyS_ioctl+0x81/0xa0
 [<ffffffff816533d9>] system_call_fastpath+0x16/0x1b
Comment 1 L.L.Robinson 2014-01-08 17:50:42 UTC 
Created attachment 847284 [details]
File: dmesg
Comment 2 Martin Milata 2014-01-10 11:48:31 UTC 
*** Bug 1051479 has been marked as a duplicate of this bug. ***
Comment 3 Justin M. Forbes 2014-05-21 19:39:03 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.14.4-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.
Comment 4 Nik Zbugz 2014-06-12 05:25:30 UTC 
Created attachment 907946 [details]
dmesg

The X server is still collapsing under KDE in Fedora 20 3.14.5-200.x86_64.  There were 2 KDE users on different virtual consoles, only one died.

As well as the duplicate bug 1051479 mentioned above, bugs bug 1058056 and bug 1038275 look very similar, as do the closed bugs bug 1044214 and bug 970022.
Comment 5 Justin M. Forbes 2014-11-13 16:00:17 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.
Comment 6 Justin M. Forbes 2014-12-10 15:00:13 UTC 
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.