Bug 1392142 - [abrt] general protection fault in ttm_dma_unpopulate [ttm]
Summary: [abrt] general protection fault in ttm_dma_unpopulate [ttm]
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 24
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:5b2f8b346199dea36b8c1b2adcb...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-05 07:06 UTC by hlfqdhj
Modified: 2017-08-08 19:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 19:08:41 UTC
Type: ---


Attachments (Terms of Use)
File: dmesg (63.60 KB, text/plain)
2016-11-05 07:06 UTC, hlfqdhj
no flags Details

Description hlfqdhj 2016-11-05 07:06:38 UTC
Additional info:
reporter:       libreport-2.7.2
general protection fault: 0000 [#1] SMP
Modules linked in: fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter xt_conntrack ip_set nfnetlink ebtable_broute bridge stp llc ebtable_nat ip6table_security ip6table_mangle ip6table_raw ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 iptable_security iptable_mangle iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic coretemp snd_hda_intel snd_hda_codec snd_hda_core kvm irqbypass snd_hwdep iTCO_wdt crct10dif_pclmul snd_seq crc32_pclmul snd_seq_device ghash_clmulni_intel mei_me iTCO_vendor_support
 intel_cstate intel_uncore mei snd_pcm snd_timer snd ppdev intel_rapl_perf i2c_i801 lpc_ich soundcore i2c_smbus shpchp wmi parport_pc parport tpm_tis tpm_tis_core video tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc amdkfd amd_iommu_v2 radeon i2c_algo_bit drm_kms_helper ttm drm crc32c_intel serio_raw r8169 mii fjes
CPU: 2 PID: 9663 Comm: kworker/2:2 Not tainted 4.8.4-200.fc24.x86_64 #1
Hardware name: LENOVO QiTianM4550-N000/ , BIOS FCKT61AUS 11/05/2014
Workqueue: events ttm_bo_delayed_workqueue [ttm]
task: ffff8af0d97dbd00 task.stack: ffff8af0d9444000
RIP: 0010:[<ffffffffc006224d>]  [<ffffffffc006224d>] ttm_dma_unpopulate+0x23d/0x330 [ttm]
RSP: 0018:ffff8af0d9447cc8  EFLAGS: 00010287
RAX: ffffbcd70f022000 RBX: ffff8af0d95126c0 RCX: ffff8af21499c2d0
RDX: 0000000000000082 RSI: bcffea0005d1d400 RDI: ffff8af0d9512720
RBP: ffff8af0d9447d00 R08: ffff8af1cbfec928 R09: 0000000000000001
R10: ffff8af20f934000 R11: 0000000000000000 R12: afff8af0d7d6dfc0
R13: ffff8af210c0a0c0 R14: 0000000000000083 R15: ffff8af1cbfec868
FS:  0000000000000000(0000) GS:ffff8af21ec80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff7c3d16000 CR3: 000000021381d000 CR4: 00000000001406e0
Stack:
 ffff8af1cbfec928 ffff8af210c0a0c0 ffff8af0d95126c0 ffff8af1cbfec928
 ffff8af0d95126c0 ffff8af20f934740 ffff8af1cbfec868 ffff8af0d9447d30
 ffffffffc013f6e0 ffff8af0d95126c0 ffff8af1cbfec928 ffff8af210c0a900
Call Trace:
 [<ffffffffc013f6e0>] radeon_ttm_tt_unpopulate+0x120/0x130 [radeon]
 [<ffffffffc0058f2e>] ttm_tt_unpopulate+0x4e/0x60 [ttm]
 [<ffffffffc0058f8f>] ttm_tt_destroy+0x4f/0x60 [ttm]
 [<ffffffffc005956e>] ttm_bo_cleanup_memtype_use+0x2e/0x70 [ttm]
 [<ffffffffc005a556>] ttm_bo_cleanup_refs_and_unlock+0x86/0x180 [ttm]
 [<ffffffffa20ded73>] ? pick_next_task_fair+0x113/0x4c0
 [<ffffffffc005a7c7>] ttm_bo_delayed_delete+0x177/0x210 [ttm]
 [<ffffffffc005a87b>] ttm_bo_delayed_workqueue+0x1b/0x40 [ttm]
 [<ffffffffa20baa34>] process_one_work+0x184/0x430
 [<ffffffffa20bad2e>] worker_thread+0x4e/0x480
 [<ffffffffa20bace0>] ? process_one_work+0x430/0x430
 [<ffffffffa20bace0>] ? process_one_work+0x430/0x430
 [<ffffffffa20c0bc8>] kthread+0xd8/0xf0
 [<ffffffffa280277f>] ret_from_fork+0x1f/0x40
 [<ffffffffa20c0af0>] ? kthread_worker_fn+0x180/0x180
Code: 8b 45 d0 45 31 f6 4c 8d 78 14 4c 89 ff e8 7c 02 7a e2 e9 86 fe ff ff 4c 8b 63 60 48 8d 7b 60 4c 39 e7 0f 84 51 fe ff ff 45 31 f6 <49> 8b 74 24 18 48 8b 43 18 44 89 f2 41 83 c6 01 48 89 34 d0 4d 
RIP  [<ffffffffc006224d>] ttm_dma_unpopulate+0x23d/0x330 [ttm]
 RSP <ffff8af0d9447cc8>

Potential duplicate: bug 1218427

Comment 1 hlfqdhj 2016-11-05 07:06:57 UTC
Created attachment 1217538 [details]
File: dmesg

Comment 2 Fedora End Of Life 2017-07-25 23:46:27 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 Fedora  'version'
of '24'.

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

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 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, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-08-08 19:08:41 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.