Bug 908250

Summary: [abrt] BUG: unable to handle kernel paging request at 000000008017003e
Product: [Fedora] Fedora Reporter: Frank Murphy <sysoutfran>
Component: kernelAssignee: fs-maint
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:70108c92e48cf6195a76fb9400a6c05656baf6f7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-22 14:40:32 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

Description Frank Murphy 2013-02-06 09:09:00 UTC 
Additional info:
BUG: unable to handle kernel paging request at 000000008017003e
IP: [<ffffffff812122bf>] ext4_release_file+0x1f/0xc0
PGD 0 
Oops: 0000 [#1] SMP 
Modules linked in: lockd sunrpc nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables microcode virtio_balloon 8139too i2c_piix4 i2c_core 8139cp mii uinput dm_crypt virtio_blk
CPU 0 
Pid: 1431, comm: xfce4-session Not tainted 3.7.5-201.fc18.x86_64 #1 Bochs Bochs
RIP: 0010:[<ffffffff812122bf>]  [<ffffffff812122bf>] ext4_release_file+0x1f/0xc0
RSP: 0018:ffff8800d88e1b98  EFLAGS: 00010246
RAX: 000000000ffff880 RBX: ffff8800d8918e70 RCX: 0000000180170002
RDX: ffffffff81821660 RSI: 0000000080170002 RDI: ffff8800d8918e70
RBP: ffff8800d88e1bb8 R08: 0000000000000000 R09: ffff88011b02b600
R10: 000000000000003c R11: 0000000000000000 R12: ffff8800d8918f20
R13: ffff880115b59cf8 R14: ffff880115b59720 R15: ffff880115ac9880
FS:  0000000000000000(0000) GS:ffff88011fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 000000008017003e CR3: 00000000d9f90000 CR4: 00000000000007f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process xfce4-session (pid: 1431, threadinfo ffff8800d88e0000, task ffff880115b59720)
Stack:
 ffff8800d8918e70 ffff880115b59cf8 ffff8800d8918e70 ffff8800d8918f20
 ffff8800d88e1bd8 ffffffff8115eb12 000000000000016e ffff880115ac9880
 ffff8800d88e1c88 ffffffff8116167d d104c9f9c68d23df ffff8800d9fad4d0
Call Trace:
 [<ffffffff8115eb12>] remove_vma+0x32/0x70
 [<ffffffff8116167d>] exit_mmap+0xed/0x170
 [<ffffffff8105baa3>] mmput+0x83/0xf0
 [<ffffffff8119ba85>] flush_old_exec+0x405/0x790
 [<ffffffff811e7ac3>] load_elf_binary+0x373/0x1aa0
 [<ffffffff8115b682>] ? get_user_pages+0x52/0x60
 [<ffffffff8119aed5>] ? copy_strings.isra.19+0x2b5/0x300
 [<ffffffff811e7750>] ? load_elf_library+0x240/0x240
 [<ffffffff8119b270>] search_binary_handler+0x130/0x330
 [<ffffffff8119c754>] do_execve_common.isra.23+0x464/0x530
 [<ffffffff8119c83b>] do_execve+0x1b/0x20
 [<ffffffff8119cb24>] sys_execve+0x54/0x80
 [<ffffffff8163e5d9>] stub_execve+0x69/0xc0
Code: 8b 49 58 e8 b4 2c f8 ff 5d c3 66 90 66 66 66 66 90 55 48 89 e5 41 54 53 48 89 fb 48 83 ec 10 48 8b 47 a0 48 c1 e8 24 a8 01 75 51 <f6> 46 3c 02 74 0b 8b 83 28 01 00 00 83 f8 01 74 58 48 8b 43 28 
RIP  [<ffffffff812122bf>] ext4_release_file+0x1f/0xc0
 RSP <ffff8800d88e1b98>
CR2: 000000008017003e
Comment 1 Frank Murphy 2013-02-06 09:09:05 UTC 
Created attachment 693805 [details]
File: dmesg
Comment 2 Josh Boyer 2013-04-03 18:05:09 UTC 
This is the third bug I've looked at today where your KVM/QEMU guest has had some odd issues.  Anyway, does your guest still see this with 3.8.x?
Comment 3 Josh Boyer 2013-04-22 14:40:32 UTC 
This bug is being closed with INSUFFICIENT_DATA as there has not been a
response in 2 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.