Bug 896437 - [abrt] BUG: soft lockup - CPU#0 stuck for 22s! [umount.nfs:25967]
Summary: [abrt] BUG: soft lockup - CPU#0 stuck for 22s! [umount.nfs:25967]
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: nfs-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3bf91fd033e84a4639fe352a244...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-17 10:10 UTC by Frank Murphy
Modified: 2013-04-22 14:24 UTC (History)
5 users (show)

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


Attachments (Terms of Use)
File: dmesg (57.81 KB, text/plain)
2013-01-17 10:10 UTC, Frank Murphy
no flags Details

Description Frank Murphy 2013-01-17 10:10:41 UTC
Additional info:
BUG: soft lockup - CPU#0 stuck for 22s! [umount.nfs:25967]
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 8139too microcode 8139cp i2c_piix4 i2c_core virtio_balloon mii uinput dm_crypt virtio_blk
CPU 0 
Pid: 25967, comm: umount.nfs Not tainted 3.7.2-201.fc18.x86_64 #1 Bochs Bochs
RIP: 0010:[<ffffffff8113232a>]  [<ffffffff8113232a>] find_get_pages+0x7a/0x1c0
RSP: 0018:ffff880116ad1bc8  EFLAGS: 00000246
RAX: ffff8800b14f3a78 RBX: 0000000000000297 RCX: 0000000000000900
RDX: ffff8800b14f3968 RSI: 0000000000000001 RDI: ffffea0002118a5c
RBP: ffff880116ad1c38 R08: 0000000000000000 R09: 00000000000008ff
R10: 0000000000000210 R11: 0000000000000000 R12: 0000000000000000
R13: ffff88011fc16ef0 R14: ffffea0002116f80 R15: 002000000000000c
FS:  00007fb052a7f840(0000) GS:ffff88011fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007f8f6c939000 CR3: 0000000117a15000 CR4: 00000000000007f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process umount.nfs (pid: 25967, threadinfo ffff880116ad0000, task ffff8800b19cae40)
Stack:
 ffff8800d21536a8 00000000ffffffff 00000000000008dc ffff8800d21536b0
 0000000016ad1c08 00000000000008dd 0000000000000900 ffffea0002116fa0
 ffff880116ad1c38 ffff880116ad1c88 ffffffffffffffff ffff8800d21536a8
Call Trace:
 [<ffffffff8113cb02>] pagevec_lookup+0x22/0x30
 [<ffffffff8113ec50>] truncate_inode_pages_range+0xe0/0x4b0
 [<ffffffff8113f0a5>] truncate_inode_pages+0x15/0x20
 [<ffffffffa015e33f>] nfs_evict_inode+0x1f/0x40 [nfs]
 [<ffffffff811ae372>] evict+0xa2/0x1a0
 [<ffffffff812fb55c>] ? __list_del_entry+0x2c/0xd0
 [<ffffffff811ae4ae>] dispose_list+0x3e/0x60
 [<ffffffff811aef57>] evict_inodes+0xb7/0x100
 [<ffffffff811971f3>] generic_shutdown_super+0x53/0xe0
 [<ffffffff81197316>] kill_anon_super+0x16/0x30
 [<ffffffffa01603a4>] nfs_kill_super+0x24/0x40 [nfs]
 [<ffffffff81197697>] deactivate_locked_super+0x57/0x80
 [<ffffffff8119822e>] deactivate_super+0x4e/0x70
 [<ffffffff811b29b7>] mntput_no_expire+0xd7/0x130
 [<ffffffff811b3996>] sys_umount+0x76/0x390
 [<ffffffff8163dad9>] system_call_fastpath+0x16/0x1b
Code: 91 00 00 00 0f 1f 44 00 00 48 8b 1a 48 85 db 74 63 f6 c3 03 0f 85 b1 00 00 00 41 f7 86 44 e0 ff ff 00 ff ff 07 0f 85 c6 00 00 00 <44> 8b 43 1c 45 85 c0 74 d5 41 8d 70 01 48 8d 7b 1c 44 89 c0 f0

Comment 1 Frank Murphy 2013-01-17 10:10:46 UTC
Created attachment 680115 [details]
File: dmesg

Comment 2 Josh Boyer 2013-04-01 20:53:41 UTC
Seems your guest locked up trying to unmount an NFS share?

Did you happen to suspend and resume the host machine, or take it's network down?

Comment 3 Frank Murphy 2013-04-01 21:27:19 UTC
(In reply to comment #2)
> Seems your guest locked up trying to unmount an NFS share?

No nfs share, unless 9p is nfs under the hood?
http://www.linux-kvm.org/page/9p_virtio

> 
> Did you happen to suspend and resume the host machine, 

Don't use suspend or hibernate.

or take it's network
> down?

It may be this
On the host eth0 and eth1 are bond0 mode 6.
May have jumped from eth0 to eth1?

Comment 4 Josh Boyer 2013-04-03 16:12:41 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > Seems your guest locked up trying to unmount an NFS share?
> 
> No nfs share, unless 9p is nfs under the hood?
> http://www.linux-kvm.org/page/9p_virtio

I don't think it is.  Your backtrace is clearly from NFS though, so it must have been active somehow.

If this is recreatable, can you provide the output of /proc/self/mounts from the guest?

Comment 5 Josh Boyer 2013-04-22 14:24:03 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.