Bug 1933637 - [kickstart test failure] - all tests failing with kernel:Call Trace: qxl_bo_unref+0x31/0x50 [qxl]
Summary: [kickstart test failure] - all tests failing with kernel:Call Trace: qxl_bo_u...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-01 10:27 UTC by Radek Vykydal
Modified: 2022-12-13 15:18 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:18:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
virt-install.log from failing kickstart-test (50.56 KB, text/plain)
2021-03-01 10:27 UTC, Radek Vykydal
no flags Details

Description Radek Vykydal 2021-03-01 10:27:05 UTC
Created attachment 1759919 [details]
virt-install.log from failing kickstart-test

All our kickstart test (using apparently qxl video) are failing with Call Trace in attached log.

23:04:43,034 WARNING kernel:------------[ cut here ]------------
23:04:43,035 WARNING kernel:WARNING: CPU: 0 PID: 135 at drivers/gpu/drm/ttm/ttm_bo.c:512 ttm_bo_release+0x4f9/0x5c0 [ttm]
23:04:43,035 WARNING kernel:Modules linked in: scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common isst_if_common nfit libnvdimm rapl joydev i2c_i801 pcspkr i2c_smbus lpc_ich virtio_balloon fuse zram loop nls_utf8 isofs rfkill qxl drm_ttm_helper ttm drm_kms_helper cec drm crct10dif_pclmul crc32_pclmul crc32c_intel 8021q garp mrp stp llc ghash_clmulni_intel serio_raw virtio_net virtio_console net_failover failover qemu_fw_cfg sunrpc sha256_ssse3 dm_crypt trusted dm_round_robin dm_multipath linear raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 iscsi_ibft squashfs cramfs be2iscsi bnx2i cnic uio cxgb4i cxgb4 tls cxgb3i cxgb3 mdio libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi edd
23:04:43,035 WARNING kernel:CPU: 0 PID: 135 Comm: kworker/0:2 Tainted: G        W        --------- ---  5.12.0-0.rc0.20210225gitc03c21ba6f4e.160.fc35.x86_64 #1
23:04:43,035 WARNING kernel:Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-2.fc32 04/01/2014
23:04:43,035 WARNING kernel:Workqueue: events qxl_gc_work [qxl]
23:04:43,035 WARNING kernel:RIP: 0010:ttm_bo_release+0x4f9/0x5c0 [ttm]
23:04:43,035 WARNING kernel:Code: ff 48 8b bd d0 fe ff ff b9 30 75 00 00 31 d2 be 01 00 00 00 e8 08 42 39 e1 48 8b 45 e0 e9 fb fe ff ff 4c 89 e8 e9 f3 fe ff ff <0f> 0b c7 85 94 00 00 00 00 00 00 00 48 8b 3c 24 48 8d 75 08 31 d2
23:04:43,035 WARNING kernel:RSP: 0018:ffffa5e84025fd78 EFLAGS: 00010202
23:04:43,035 WARNING kernel:RAX: 0000000000000001 RBX: 0000000000000002 RCX: 00000000000020ec
23:04:43,035 WARNING kernel:RDX: ffff89d838c1a9c0 RSI: ffffffffc058c1a0 RDI: ffff89d83f8b0e50
23:04:43,035 WARNING kernel:RBP: ffff89d7d2990e68 R08: 0000000000000001 R09: 0000000000000001
23:04:43,035 WARNING kernel:R10: 0000000000003106 R11: 0000000000000000 R12: ffff89d7d2ae1600
23:04:43,036 WARNING kernel:R13: ffff89d83c348e90 R14: ffff89d7d2990ed0 R15: ffff89d7d2ae1400
23:04:43,036 WARNING kernel:FS:  0000000000000000(0000) GS:ffff89d838c00000(0000) knlGS:0000000000000000
23:04:43,036 WARNING kernel:CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
23:04:43,036 WARNING kernel:CR2: 00007fcb6ae796f0 CR3: 00000000128e4004 CR4: 0000000000770ef0
23:04:43,036 WARNING kernel:DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
23:04:43,036 WARNING kernel:DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
23:04:43,036 WARNING kernel:PKRU: 55555554
23:04:43,036 WARNING kernel:Call Trace:
23:04:43,036 WARNING kernel: qxl_bo_unref+0x31/0x50 [qxl]
23:04:43,036 WARNING kernel: qxl_release_free_list+0x52/0xa0 [qxl]
23:04:43,036 WARNING kernel: qxl_release_free+0x76/0xe0 [qxl]
23:04:43,036 WARNING kernel: qxl_garbage_collect+0xba/0x160 [qxl]
23:04:43,036 WARNING kernel: process_one_work+0x2b0/0x5e0
23:04:43,036 WARNING kernel: worker_thread+0x55/0x3c0
23:04:43,036 WARNING kernel: ? process_one_work+0x5e0/0x5e0
23:04:43,036 WARNING kernel: kthread+0x13a/0x150
23:04:43,036 WARNING kernel: ? __kthread_bind_mask+0x60/0x60
23:04:43,036 WARNING kernel: ret_from_fork+0x22/0x30
23:04:43,037 WARNING kernel:irq event stamp: 409509
23:04:43,037 WARNING kernel:hardirqs last  enabled at (409515): [<ffffffffa1169e0b>] console_unlock+0x4fb/0x620
23:04:43,037 WARNING kernel:hardirqs last disabled at (409520): [<ffffffffa1169d56>] console_unlock+0x446/0x620
23:04:43,037 WARNING kernel:softirqs last  enabled at (409354): [<ffffffffa1e01182>] asm_call_irq_on_stack+0x12/0x20
23:04:43,037 WARNING kernel:softirqs last disabled at (409337): [<ffffffffa1e01182>] asm_call_irq_on_stack+0x12/0x20
23:04:43,037 WARNING kernel:---[ end trace 9f0ffaabd04afb5e ]---
23:04:43,037 WARNING kernel:------------[ cut here ]------------

Comment 1 Radek Vykydal 2021-03-01 12:29:43 UTC
Workaround in kickstart tests (using virtio) : https://github.com/rhinstaller/kickstart-tests/pull/491

Comment 2 Radek Vykydal 2021-03-02 07:47:43 UTC
NOTE: the test is killed because of the Call Trace detected. It is possible that normal installation succeeds.

Comment 4 Ben Cotton 2021-08-10 12:53:21 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

Comment 5 Ben Cotton 2022-11-29 16:53:02 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Ben Cotton 2022-12-13 15:18:49 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.