Bug 903243 - [abrt] BUG: soft lockup - CPU#0 stuck for 24s! [khugepaged:32]
Summary: [abrt] BUG: soft lockup - CPU#0 stuck for 24s! [khugepaged:32]
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5d79cd30cc4e3fb0b48de8bd0a5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-23 14:51 UTC by Frank Murphy
Modified: 2013-04-22 14:26 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-04-22 14:26:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (78.96 KB, text/plain)
2013-01-23 14:51 UTC, Frank Murphy
no flags Details

Description Frank Murphy 2013-01-23 14:51:49 UTC
Additional info:
BUG: soft lockup - CPU#0 stuck for 24s! [khugepaged:32]
Modules linked in: nfsv3 nfs_acl nfsv4 auth_rpcgss nfs dns_resolver fscache 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 8139too virtio_balloon 8139cp mii i2c_piix4 i2c_core uinput dm_crypt virtio_blk
CPU 0 
Pid: 32, comm: khugepaged Not tainted 3.7.2-201.fc18.x86_64 #1 Bochs Bochs
RIP: 0010:[<ffffffff810bbc6a>]  [<ffffffff810bbc6a>] generic_exec_single+0x8a/0xc0
RSP: 0018:ffff880115f5dba8  EFLAGS: 00000202
RAX: 00000000000008fd RBX: fffffe0000000000 RCX: 0000000000000012
RDX: 00000000000008fb RSI: 00000000000000fb RDI: 0000000000000282
RBP: ffff880115f5dbe8 R08: ffff88011fd14740 R09: 0000000000000080
R10: 0000000000000014 R11: 0000000000000000 R12: 00000be4ee356441
R13: 00000002ffffffff R14: 0000000000000000 R15: 0000000000000002
FS:  0000000000000000(0000) GS:ffff88011fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007ff0419ff000 CR3: 0000000117032000 CR4: 00000000000007f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process khugepaged (pid: 32, threadinfo ffff880115f5c000, task ffff880118e9ae40)
Stack:
 0000000000000282 ffff88011fd14740 0000000000000000 0000000000000001
 0000000000000000 ffffffff81cdc490 ffffffff8104c780 ffff8801170c0e70
 ffff880115f5dc58 ffffffff810bbd72 ffffc90000607000 0000000000000282
Call Trace:
 [<ffffffff8104c780>] ? do_flush_tlb_all+0x60/0x60
 [<ffffffff810bbd72>] smp_call_function_single+0xd2/0x170
 [<ffffffff8104c780>] ? do_flush_tlb_all+0x60/0x60
 [<ffffffff810bc12c>] smp_call_function_many+0x22c/0x260
 [<ffffffff8104c780>] ? do_flush_tlb_all+0x60/0x60
 [<ffffffff8104c87e>] native_flush_tlb_others+0x2e/0x30
 [<ffffffff8104c95c>] flush_tlb_mm_range+0x6c/0x240
 [<ffffffff8116a1c7>] pmdp_clear_flush+0x57/0x90
 [<ffffffff8118f6ab>] ? mem_cgroup_newpage_charge+0x4b/0xb0
 [<ffffffff81186972>] khugepaged+0xe42/0x1630
 [<ffffffff81082590>] ? wake_up_bit+0x40/0x40
 [<ffffffff81185b30>] ? khugepaged_defrag_store+0x70/0x70
 [<ffffffff81081c80>] kthread+0xc0/0xd0
 [<ffffffff81010000>] ? ftrace_raw_event_xen_mmu_flush_tlb_others+0x50/0xe0
 [<ffffffff81081bc0>] ? kthread_create_on_node+0x120/0x120
 [<ffffffff8163da2c>] ret_from_fork+0x7c/0xb0
 [<ffffffff81081bc0>] ? kthread_create_on_node+0x120/0x120
Code: f9 23 00 48 8b 45 c0 4c 89 ff 48 89 c6 e8 3f 95 57 00 48 3b 5d c8 74 31 45 85 f6 75 0e 0f 1f 40 00 eb 10 66 0f 1f 44 00 00 f3 90 <41> f6 44 24 20 01 75 f6 48 8b 5d d8 4c 8b 65 e0 4c 8b 6d e8 4c

Comment 1 Frank Murphy 2013-01-23 14:51:55 UTC
Created attachment 685971 [details]
File: dmesg

Comment 2 Josh Boyer 2013-04-03 17:01:18 UTC
Are you still seeing this one on 3.8.x?

Comment 3 Josh Boyer 2013-04-22 14:26:19 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.


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