Bug 1034147 - [abrt] BUG: unable to handle kernel paging request at ffffffffa006b77d
Summary: [abrt] BUG: unable to handle kernel paging request at ffffffffa006b77d
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:a13b2ab381a6d9b217fdd48a9df...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-25 10:47 UTC by collura
Modified: 2015-06-30 12:27 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 12:27:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (63.09 KB, text/plain)
2013-11-25 10:47 UTC, collura
no flags Details

Description collura 2013-11-25 10:47:02 UTC
Description of problem:
firefox was loading

Additional info:
reporter:       libreport-2.1.9
BUG: unable to handle kernel paging request at ffffffffa006b77d
IP: [<ffffffffa010cef9>] cik_vm_set_page+0x2c9/0x430 [radeon]
PGD 1c0f067 PUD 1c10063 PMD 194368067 PTE 193f68161
Oops: 0003 [#1] SMP 
Modules linked in: fuse xt_CHECKSUM tun nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE bnep ip6t_REJECT bluetooth xt_conntrack 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 amd_freq_sensitivity snd_hda_codec_conexant kvm snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep snd_seq arc4 snd_seq_device rtl8188ee rtl_pci rtlwifi mac80211 cfg80211 crc32_pclmul toshiba_acpi snd_pcm crc32c_intel sparse_keymap snd_page_alloc ghash_clmulni_intel rfkill snd_timer alx mdio joydev snd shpchp wmi microcode fam15h_power i2c_piix4 k10temp edac_core edac_mce_amd soundcore acpi_cpufreq serio_raw video mperf binfmt_misc radeon i2c_algo_bit drm_kms_helper ttm drm i2c_core
CPU: 0 PID: 531 Comm: Xorg Not tainted 3.11.9-300.fc20.x86_64 #1
Hardware name: TOSHIBA Satellite L75D-A/Larne, BIOS 1.10 05/16/2013
task: ffff88018632c4a0 ti: ffff8801848d6000 task.ti: ffff8801848d6000
RIP: 0010:[<ffffffffa010cef9>]  [<ffffffffa010cef9>] cik_vm_set_page+0x2c9/0x430 [radeon]
RSP: 0018:ffff8801848d7bb8  EFLAGS: 00010246
RAX: 0000000000000060 RBX: ffff8801848d7c68 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff8801848d7c10 R08: 0000000000000001 R09: 000000000007ffff
R10: 0000000000000000 R11: ffffffffa006b77d R12: 0000000000000001
R13: 000000000043e6e8 R14: 0000000000001000 R15: 0000000000000000
FS:  00007f28c13b1700(0000) GS:ffff88019ec00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffa006b77d CR3: 0000000186298000 CR4: 00000000000407f0
Stack:
 00000000ffffffdd 0000000000000000 0000000000016ee0 ffff880193820000
 ffff8801848d7c10 ffffffff00000001 0000000000001000 ffff8801862c3980
 00000000000062de ffff880193820000 000000000043e6e8 ffff8801848d7d08
Call Trace:
 [<ffffffffa009fb24>] radeon_vm_bo_update_pte+0x2b4/0x5d0 [radeon]
 [<ffffffffa006b77d>] ? ttm_bo_wait+0xfd/0x180 [ttm]
 [<ffffffffa006c37e>] ? ttm_bo_release+0x18e/0x260 [ttm]
 [<ffffffffa009fe8e>] radeon_vm_bo_rmv+0x4e/0x90 [radeon]
 [<ffffffffa00b0273>] radeon_gem_object_close+0xe3/0x100 [radeon]
 [<ffffffffa0015bc9>] drm_gem_handle_delete+0xb9/0x150 [drm]
 [<ffffffffa0016218>] drm_gem_close_ioctl+0x28/0x30 [drm]
 [<ffffffffa0014122>] drm_ioctl+0x512/0x640 [drm]
 [<ffffffff81161d2c>] ? tlb_flush_mmu.part.47+0x4c/0x90
 [<ffffffff8116a743>] ? unmap_region+0xd3/0x110
 [<ffffffff8116a428>] ? vma_gap_callbacks_rotate+0x18/0x30
 [<ffffffff8116a7e3>] ? remove_vma+0x63/0x70
 [<ffffffff811bac2d>] do_vfs_ioctl+0x2dd/0x4b0
 [<ffffffff811bae81>] SyS_ioctl+0x81/0xa0
 [<ffffffff81653399>] system_call_fastpath+0x16/0x1b
Code: 8b 75 b0 0f 85 fe 00 00 00 e9 e5 fe ff ff 0f 1f 40 00 48 89 f7 41 89 f2 48 c1 ef 20 8b 4b 08 4c 8b 5b 18 44 8d 61 01 44 89 63 08 <41> c7 04 8b 0c 00 00 00 8b 4b 08 4c 8b 5b 18 44 8d 61 01 44 89 
RIP  [<ffffffffa010cef9>] cik_vm_set_page+0x2c9/0x430 [radeon]
 RSP <ffff8801848d7bb8>
CR2: ffffffffa006b77d

Comment 1 collura 2013-11-25 10:47:23 UTC
Created attachment 828590 [details]
File: dmesg

Comment 2 Fedora End Of Life 2015-05-29 09:50:56 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 Jaroslav Reznik 2015-06-30 12:27:44 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.