Bug 1048328 - [abrt] WARNING: CPU: 0 PID: 56 at drivers/gpu/drm/drm_mm.c:578 drm_mm_takedown+0x2e/0x30 [drm]()
Summary: [abrt] WARNING: CPU: 0 PID: 56 at drivers/gpu/drm/drm_mm.c:578 drm_mm_takedow...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 20
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:c3646cd4c0cfe4949bd2a38d7fc...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-03 18:06 UTC by neuberg.tomas
Modified: 2015-06-29 14:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 14:08:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (72.28 KB, text/plain)
2014-01-03 18:06 UTC, neuberg.tomas
no flags Details

Description neuberg.tomas 2014-01-03 18:06:21 UTC
Additional info:
reporter:       libreport-2.1.10
WARNING: CPU: 0 PID: 56 at drivers/gpu/drm/drm_mm.c:578 drm_mm_takedown+0x2e/0x30 [drm]()
Memory manager not clean during takedown.
Modules linked in: ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw i8k arc4 x86_pkg_temp_thermal coretemp kvm_intel iwldvm iTCO_wdt kvm iTCO_vendor_support snd_hda_codec_hdmi dell_wmi mac80211 sparse_keymap crct10dif_pclmul crc32_pclmul snd_hda_codec_conexant crc32c_intel ghash_clmulni_intel dell_laptop snd_hda_intel dcdbas snd_hda_codec iwlwifi snd_hwdep snd_seq microcode joydev snd_seq_device cfg80211 i2c_i801 serio_raw snd_pcm snd_page_alloc lpc_ich snd_timer r8169 mfd_core snd rfkill mii soundcore mei_me mei shpchp wmi nfsd auth_rpcgss nfs_acl lockd sunrpc radeon i915 i2c_algo_bit drm_kms_helper ttm drm i2c_core video
CPU: 0 PID: 56 Comm: kworker/0:1 Not tainted 3.12.5-302.fc20.x86_64 #1
Hardware name: Dell Inc. Vostro 3560/0C05GV, BIOS A13 11/15/2012
Workqueue: kacpi_hotplug hotplug_event_work
 0000000000000009 ffff88025372ba40 ffffffff81662d11 ffff88025372ba88
 ffff88025372ba78 ffffffff810691dd ffff880095c0de40 ffff880095cfcaf8
 ffff880253abf048 ffffffffa02a9100 ffff880253535028 ffff88025372bad8
Call Trace:
 [<ffffffff81662d11>] dump_stack+0x45/0x56
 [<ffffffff810691dd>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff8106924c>] warn_slowpath_fmt+0x4c/0x50
 [<ffffffffa00d86e3>] ? ttm_bo_man_takedown+0x43/0x70 [ttm]
 [<ffffffffa003bf9e>] drm_mm_takedown+0x2e/0x30 [drm]
 [<ffffffffa00d86d3>] ttm_bo_man_takedown+0x33/0x70 [ttm]
 [<ffffffffa00d3871>] ttm_bo_clean_mm+0x51/0x80 [ttm]
 [<ffffffffa01ae96d>] radeon_ttm_fini+0xbd/0x180 [radeon]
 [<ffffffffa01af3c2>] radeon_bo_fini+0x12/0x20 [radeon]
 [<ffffffffa01f91c3>] evergreen_fini+0xa3/0xd0 [radeon]
 [<ffffffffa0193cae>] radeon_device_fini+0x3e/0x120 [radeon]
 [<ffffffffa0195b1d>] radeon_driver_unload_kms+0x3d/0x60 [radeon]
 [<ffffffffa0037863>] drm_put_dev+0x63/0x180 [drm]
 [<ffffffffa019206d>] radeon_pci_remove+0x1d/0x20 [radeon]
 [<ffffffff8133bfdb>] pci_device_remove+0x3b/0xb0
 [<ffffffff813ff89f>] __device_release_driver+0x7f/0xf0
 [<ffffffff813ff933>] device_release_driver+0x23/0x30
 [<ffffffff813ff0c8>] bus_remove_device+0x108/0x180
 [<ffffffff813fb995>] device_del+0x135/0x1d0
 [<ffffffff81335b64>] pci_stop_bus_device+0x94/0xa0
 [<ffffffff81335c52>] pci_stop_and_remove_bus_device+0x12/0x20
 [<ffffffff813508e7>] trim_stale_devices+0x67/0xf0
 [<ffffffff81350d36>] acpiphp_check_bridge+0x86/0xd0
 [<ffffffff81351b6a>] hotplug_event+0x10a/0x250
 [<ffffffff811941bd>] ? kmem_cache_free+0x1cd/0x1e0
 [<ffffffff813716e4>] ? acpi_os_execute_deferred+0x2d/0x32
 [<ffffffff81351cd7>] hotplug_event_work+0x27/0x70
 [<ffffffff810835f6>] process_one_work+0x176/0x430
 [<ffffffff8108422b>] worker_thread+0x11b/0x3a0
 [<ffffffff81084110>] ? rescuer_thread+0x350/0x350
 [<ffffffff8108b0d0>] kthread+0xc0/0xd0
 [<ffffffff8108b010>] ? insert_kthread_work+0x40/0x40
 [<ffffffff81671cbc>] ret_from_fork+0x7c/0xb0
 [<ffffffff8108b010>] ? insert_kthread_work+0x40/0x40

Comment 1 neuberg.tomas 2014-01-03 18:06:29 UTC
Created attachment 845037 [details]
File: dmesg

Comment 2 Fedora End Of Life 2015-05-29 10:18:39 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 2015-06-29 14:08:22 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.