From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-1984384 ] soft lockup - CPU#5 stuck for 11s! [qemu-system-x86:4966]
Date: Wed, 04 Jun 2008 04:49:43 -0700 [thread overview]
Message-ID: <E1K3rUt-0001ZH-Rr@sc8-sf-web23.sourceforge.net> (raw)
Bugs item #1984384, was opened at 2008-06-04 13:49
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1984384&group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Rafal Wijata (ravpl)
Assigned to: Nobody/Anonymous (nobody)
Summary: soft lockup - CPU#5 stuck for 11s! [qemu-system-x86:4966]
Initial Comment:
I'm using kvm-69 running on
Linux 2.6.24.7-92.fc8 #1 SMP Wed May 7 16:26:02 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
kvm modules loaded from kvm-69 rather than kernel provided
My system almost freezed after I killed qemu process.
I saw many, many tasks in 'D' state, along with [reiserfs/?] tasks.
Normally I would consider it reiserfs bug(and maybe it is), but two things
- it happened after qemu process was killed(running with 6cpus, 6G memory, 16G hdd placed on reiserfs placed on 200M/s hdd)
- dmesg showed following messages(2 total), which suggest it stucked in kvm
BUG: soft lockup - CPU#5 stuck for 11s! [qemu-system-x86:4966]
CPU 5:
Modules linked in: ipt_REJECT nf_conntrack_ipv4 iptable_filter ip_tables kvm_intel(U) kvm(U) tun nfs lockd nfs_acl autofs4 coretemp hwmon fuse sunrpc bridge xt_tcpudp nf_conntrack_ipv6 xt_state nf_conntrack ip6t_REJECT ip6table_filter ip6_tables x_tables ipv6 cpufreq_ondemand acpi_cpufreq reiserfs ext2 dm_mirror dm_multipath dm_mod i5000_edac iTCO_wdt serio_raw pcspkr iTCO_vendor_support e1000 button edac_core i2c_i801 ata_piix i2c_core pata_acpi ata_generic sg usb_storage ahci libata shpchp 3w_9xxx sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd
Pid: 4966, comm: qemu-system-x86 Not tainted 2.6.24.7-92.fc8 #1
RIP: 0010:[<ffffffff8834b29e>] [<ffffffff8834b29e>] :kvm:rmap_remove+0x170/0x198
RSP: 0018:ffff8101f4df5bd8 EFLAGS: 00000246
RAX: 0000000000000002 RBX: ffff81004294af60 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000106 RDI: ffff8101770448c0
RBP: ffff8101ce0454d0 R08: ffffc20001b86030 R09: ffff8101d3587118
R10: 000000000019e7ea R11: ffff8101394dd9c0 R12: ffff8100240cece0
R13: 0000000000000000 R14: 000000000019e7ea R15: 0000000000000018
FS: 0000000000000000(0000) GS:ffff81021f049580(0000) knlGS:0000000000000000
CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
CR2: 00000000f7ff6000 CR3: 000000021b5e5000 CR4: 00000000000026e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
[<ffffffff8834b1dd>] :kvm:rmap_remove+0xaf/0x198
[<ffffffff8834b372>] :kvm:kvm_mmu_zap_page+0x8a/0x25e
[<ffffffff8834b9f3>] :kvm:free_mmu_pages+0x12/0x34
[<ffffffff8834bac9>] :kvm:kvm_mmu_destroy+0x1d/0x5e
[<ffffffff88346979>] :kvm:kvm_arch_vcpu_uninit+0x1d/0x38
[<ffffffff8834555b>] :kvm:kvm_vcpu_uninit+0x9/0x15
[<ffffffff88163aa8>] :kvm_intel:vmx_free_vcpu+0x74/0x84
[<ffffffff8834657b>] :kvm:kvm_arch_destroy_vm+0x69/0xb4
[<ffffffff88345538>] :kvm:kvm_vcpu_release+0x13/0x18
[<ffffffff810a35d4>] __fput+0xc2/0x18f
[<ffffffff810a0de7>] filp_close+0x5d/0x65
[<ffffffff8103b3df>] put_files_struct+0x66/0xc4
[<ffffffff8103c6f7>] do_exit+0x28c/0x76b
[<ffffffff8103cc55>] sys_exit_group+0x0/0xe
[<ffffffff81044163>] get_signal_to_deliver+0x3aa/0x3d8
[<ffffffff8100b359>] do_notify_resume+0xa8/0x732
[<ffffffff8126b7f6>] unlock_kernel+0x32/0x33
[<ffffffff881c01db>] :reiserfs:reiserfs_setattr+0x26e/0x27d
[<ffffffff810a1866>] do_truncate+0x70/0x79
[<ffffffff8100bf17>] sysret_signal+0x1c/0x27
[<ffffffff8100c1a7>] ptregscall_common+0x67/0xb0
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1984384&group_id=180599
next reply other threads:[~2008-06-04 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 11:49 SourceForge.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-04 12:19 [ kvm-Bugs-1984384 ] soft lockup - CPU#5 stuck for 11s! [qemu-system-x86:4966] SourceForge.net
2008-06-04 14:20 SourceForge.net
2008-06-04 14:33 SourceForge.net
2008-06-04 14:58 SourceForge.net
2008-06-04 15:08 SourceForge.net
2008-06-04 15:45 SourceForge.net
2009-08-10 12:27 SourceForge.net
2009-08-25 2:20 SourceForge.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1K3rUt-0001ZH-Rr@sc8-sf-web23.sourceforge.net \
--to=noreply@sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.